
From moore@network-heretics.com  Sat Dec  1 06:40:06 2012
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 9F61611E8099 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 06:40:06 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mtcl5b7kDWIf for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 06:40:06 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 243A811E8097 for <ietf@ietf.org>; Sat,  1 Dec 2012 06:40:05 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 10AE621138 for <ietf@ietf.org>; Sat,  1 Dec 2012 09:40:04 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Sat, 01 Dec 2012 09:40:04 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=6mshKJr6P0qBENDssQoEhR Da134=; b=i6aqMjGoimxvT+TjyElTgGkYFKLsdNcMEY8nX2IMY9Zx71HytdYeYY VpqHR4BH8xtGG4D6pnPUsXbsHxEtLavvcJRArVYffv1X5+uAcQel+Uufl4nvsaft 5qNrkYkYnzTFmIF7j9OOHfkwh92Jw2AR3iSVbjvwpMZ+xYqk5aB2A=
X-Sasl-enc: cavHjPKLDBd9LzrptVRafR90TDVN+vwf3XbNi7ZeNsuV 1354372803
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6CF6D8E010B; Sat,  1 Dec 2012 09:40:03 -0500 (EST)
Message-ID: <50BA16C0.5060401@network-heretics.com>
Date: Sat, 01 Dec 2012 09:40:00 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <m2lidl5ntp.wl%randy@psg.com> <BB22CC86-F9B8-4727-BCA3-F617221944F2@gmail.com> <50B78102.1020705@dcrocker.net>
In-Reply-To: <50B78102.1020705@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: Sat, 01 Dec 2012 14:40:06 -0000

On 11/29/2012 10:36 AM, Dave Crocker wrote:
> F2f meetings are explicitly managed, with significant control of the 
> room.  Mailing list exchanges are typically not managed at all.
>
> Given the difference, it's not surprising that one proves more 
> productive than the other.

Please don't confuse "management" with "encouraging productivity". In 
Atlanta I witnessed several f2f WG meetings that were explicitly 
managed, and completely unproductive.

(Hint: anytime the vast majority of a f2f meeting is devoted to 
presentations, it's almost certainly useless.  Even if there were 
occasions when participants were asked to hum.)

Keith


From moore@network-heretics.com  Sat Dec  1 06:48:29 2012
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 9920C11E809A for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 06:48:29 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Up2ORQUGcOeL for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 06:48:29 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 11DB311E8097 for <ietf@ietf.org>; Sat,  1 Dec 2012 06:48:29 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 571E8207FE for <ietf@ietf.org>; Sat,  1 Dec 2012 09:48:28 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Sat, 01 Dec 2012 09:48:28 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=m3YEEFJR78cJPcq1n6HBGu XCQC4=; b=tsBG9n2vsy5fMJwTkF0HkoBdK0xjR1SQlVtD6FetmEjOE88Q/4DR4V buRS9fHG0jaDwSaXMFWfo+FhhNIZV0MGZgQjbHY9B/x4u2YAkuZoKbfBMS3swWk7 ZHhHOQUBotA+sYpcpqBlfqBFZgTWWEonRx5FW0E8LvwxJaqZdXDY4=
X-Sasl-enc: sqcb4WBbqROYJV74QShQMca6KuP6x93sBSUs5JNTeRB4 1354373307
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9AC6B4827B6; Sat,  1 Dec 2012 09:48:27 -0500 (EST)
Message-ID: <50BA18B8.3090306@network-heretics.com>
Date: Sat, 01 Dec 2012 09:48:24 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>	<CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com>
In-Reply-To: <50B7EA5D.2030803@qti.qualcomm.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: Sat, 01 Dec 2012 14:48:29 -0000

On 11/29/2012 06:06 PM, Pete Resnick wrote:
> On 11/29/12 3:45 PM, Lee Howard wrote:
>> I can't take notes while I'm standing up, facilitating discussion.
>
> Interesting. I am forced to (only somewhat facetiously) ask: Why are 
> *you* standing up, facilitating discussion, if you are the editor? 
> Shouldn't that be the chair's job? More seriously: Since we started 
> this PowerPoint/Comments-at-the-mic thing oh so many years ago, doing 
> document reviews in presentation form where the editor is the one 
> doing the slides has created this problem. Perhaps a better mode would 
> be for the editor to write up the list of open issues, have the chair 
> project them if need be, and the editor can get up to the mic with 
> explanations/questions as needed but otherwise remain seated so they 
> can jot down the notes they need. I think I've done something like 
> that a long time ago as an editor. Worth trying, I'd think.
+1

More generally, every time I go to IETF I'm appalled that working groups 
have gotten into the habit of filling the time with PowerPoint 
presentations.[*]   PowerPoint (and similar tools) should be used 
sparingly, if at all.   Most of the time, the projector should be off, 
or the screen blank.

The point of IETF meetings is to facilitate discussion, not to show 
things to people.

PowerPoint tells meeting participants to be passive, or that it's okay 
to take up space in the meeting room while browsing the web and not 
paying attention, not being engaged.  Both of these are detrimental to 
IETF work.

Keith

[*] And yes, I realize that this has been the case for over 10 years, 
but I remember when it was not the case.


From dcrocker@bbiw.net  Sat Dec  1 11:07:35 2012
Return-Path: <dcrocker@bbiw.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 850DE21E809E for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 11:07:35 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ifevQ8GAJ7vw for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 11:07:32 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5252E21E8039 for <ietf@ietf.org>; Sat,  1 Dec 2012 11:07:32 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB1J7PLL002350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Dec 2012 11:07:25 -0800
Message-ID: <50BA5565.80008@bbiw.net>
Date: Sat, 01 Dec 2012 11:07:17 -0800
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <50B8D979.1010203@dcrocker.net> <CAC4RtVAuN6eCZtmuTZveuRtqCK=RGHS51PfBu28BvQnax=dm6A@mail.gmail.com>
In-Reply-To: <CAC4RtVAuN6eCZtmuTZveuRtqCK=RGHS51PfBu28BvQnax=dm6A@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.17]); Sat, 01 Dec 2012 11:07:25 -0800 (PST)
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: Sat, 01 Dec 2012 19:07:35 -0000

On 11/30/2012 3:29 PM, Barry Leiba wrote:
>>> There is no formal process that involves "adopting" anything.
>>
>> If you mean that we haven't documented a/the formal process, you are
>> correct.  If you mean that the IETF has not moved towards rather formal
>> steps for explicitly adopting working group drafts, I disagree.
> ...
>> Today, there is typically explicit text in the charter about adoption or
>> there is explicit wg approval.
>
> Indeed: we always have the option of having the charter limit
> management options.


Barry, I think you are trying to make a very different point from the 
one I am trying to make.

I think you are trying to assert that there is flexibility while I am 
trying to assert that there is common practice.  These are not mutually 
exclusive points.

My point about a formal process having emerged is that a chair/wg 
wanting to adopt a document has a well-established set of common 
practice.  It's not well (or at all) documented, but it exists in how 
working groups typically do things.

I was not trying to comment on the degree to which that process is 
mandated.  I acknowledge that fully documenting common practice, to make 
it "official" formal process, must combine both lines of concern.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dhc@dcrocker.net  Sat Dec  1 11:23:09 2012
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 0EB5821F8D0C for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 11:23:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K5bGEipUxMCg for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 11:23:08 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE1621F8D0B for <ietf@ietf.org>; Sat,  1 Dec 2012 11:23:08 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB1JN5Ei003936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Dec 2012 11:23:08 -0800
Message-ID: <50BA5912.4010701@dcrocker.net>
Date: Sat, 01 Dec 2012 11:22:58 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Barely literate minutes
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <m2lidl5ntp.wl%randy@psg.com> <BB22CC86-F9B8-4727-BCA3-F617221944F2@gmail.com> <50B78102.1020705@dcrocker.net> <50BA16C0.5060401@network-heretics.com>
In-Reply-To: <50BA16C0.5060401@network-heretics.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.17]); Sat, 01 Dec 2012 11:23:08 -0800 (PST)
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: Sat, 01 Dec 2012 19:23:09 -0000

On 12/1/2012 6:40 AM, Keith Moore wrote:
> On 11/29/2012 10:36 AM, Dave Crocker wrote:
>> F2f meetings are explicitly managed, with significant control of the
>> room.  Mailing list exchanges are typically not managed at all.
>>
>> Given the difference, it's not surprising that one proves more
>> productive than the other.
>
> Please don't confuse "management" with "encouraging productivity". In
> Atlanta I witnessed several f2f WG meetings that were explicitly
> managed, and completely unproductive.
>
> (Hint: anytime the vast majority of a f2f meeting is devoted to
> presentations, it's almost certainly useless.  Even if there were
> occasions when participants were asked to hum.)


Please don't use individual exemplars to try to prove a general case.

The thread contained an assertion of /generally/ better exchanges f2f. 
I suggested some contributing factors in support of the claimed general 
case.

Many email exchanges go extremely well.  Many f2f go extremely poorly.

human behavior.  complicated.

group behavior.  more complicated.

belief is simplistic causes or outcomes would be silly.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From stephen.farrell@cs.tcd.ie  Sat Dec  1 12:12:57 2012
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 349A311E80A3 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 12:12:57 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uqqveKjbHNx0 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 12:12:56 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 31FD711E8099 for <ietf@ietf.org>; Sat,  1 Dec 2012 12:12:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9255EBE4D for <ietf@ietf.org>; Sat,  1 Dec 2012 20:12:32 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eH+CfwtoFcDV for <ietf@ietf.org>; Sat,  1 Dec 2012 20:12:28 +0000 (GMT)
Received: from [10.87.48.10] (unknown [86.41.7.179]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2514BBE49 for <ietf@ietf.org>; Sat,  1 Dec 2012 20:12:28 +0000 (GMT)
Message-ID: <50BA64AB.3010106@cs.tcd.ie>
Date: Sat, 01 Dec 2012 20:12:27 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Idea for a process experiment to reward running code...
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, 01 Dec 2012 20:12:57 -0000

Hi all,

I've just posted an idea [1] for a small process improvement.
If it doesn't seem crazy I'll try pursue it with the IESG as
an RFC 3933 process experiment. If its universally hated then
that's fine, it can die.

The IESG have seen (more-or-less) this already but it hasn't
be discussed, so this is just a proposal from me and has no
"official" status whatsoever.

Any comments, suggestions or better ideas are very welcome.
Feel free to send me comments off list for now, or on this
list I guess. If there's loads of email (always possible,
this being a process thing;-) we can move to some other list.

Regards,
Stephen.

[1] http://tools.ietf.org/id/draft-farrell-ft

From dhc@dcrocker.net  Sat Dec  1 12:36:37 2012
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 8A50321F85B1 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 12:36:37 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Adppy21nVRnS for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 12:36:37 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E39EE21F8570 for <ietf@ietf.org>; Sat,  1 Dec 2012 12:36:36 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB1KaTYc010470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Dec 2012 12:36:29 -0800
Message-ID: <50BA6A45.2000409@dcrocker.net>
Date: Sat, 01 Dec 2012 12:36:21 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 01 Dec 2012 12:36:29 -0800 (PST)
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: Sat, 01 Dec 2012 20:36:37 -0000

On 12/1/2012 12:12 PM, Stephen Farrell wrote:
>
> Hi all,
>
> I've just posted an idea [1] for a small process improvement.
> If it doesn't seem crazy I'll try pursue it with the IESG as
> an RFC 3933 process experiment. If its universally hated then
> that's fine, it can die.
>
> The IESG have seen (more-or-less) this already but it hasn't
> be discussed, so this is just a proposal from me and has no
> "official" status whatsoever.
>
> Any comments, suggestions or better ideas are very welcome.
> Feel free to send me comments off list for now, or on this
> list I guess. If there's loads of email (always possible,
> this being a process thing;-) we can move to some other list.


What actual problem is this trying to solve?  I see the reference to a 
'reward', but wasn't aware that there is a perceived problem needing 
incentive to solve.

In additional, the incentive you are proposing seems to be getting to 
Proposed perhaps a month or so quicker?  It's difficult to see that as 
being sufficient incentive for creating implementations that would not 
otherwise we created.

The tradeoff is, of course, less time for final review.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From melinda.shore@gmail.com  Sat Dec  1 13:00:39 2012
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 AEAE211E80A5 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 13:00:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S29dCYPRg0Bj for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 13:00:39 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0E50A11E8099 for <ietf@ietf.org>; Sat,  1 Dec 2012 13:00:39 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1112391pbc.31 for <ietf@ietf.org>; Sat, 01 Dec 2012 13:00:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=FsdBcsbRL3kpzQf6c4YH33JjxuT1ePcO92Xzvyuj/pw=; b=T+igZV/bk6MQV8MD0rC+P/UHZfQHANL093MCCnSv4M/6R8thYItMjvwtTe6m7forAy d46q76PoT3FD0GiLeUH0p3OfZnGRVzpW5PCqSstW1hVyFXRpymEqF5cWEXDqE677bRYP m6451dYF5Do+h7PxKcWCQYi95qT/RiWuOra4I08ScUm5zWMJVIP0xapQaCCmfDLGjDTv MzCQVlotZd0KB+e8LFRLOZTrgDafuCkBJ1fvBBX+5ZwgZ0/7nZDzuqHO0qJZgVMTVN2g K05FEKpEfQ29aX7yXfB30g+NgwBm5tc5HrCZV0X6ehh4vXyT828do7L4+do78CZKI+Th rskQ==
Received: by 10.66.87.167 with SMTP id az7mr13774878pab.69.1354395638806; Sat, 01 Dec 2012 13:00:38 -0800 (PST)
Received: from spandex.local (66-230-87-153-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.153]) by mx.google.com with ESMTPS id ug6sm5249867pbc.4.2012.12.01.13.00.37 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 01 Dec 2012 13:00:38 -0800 (PST)
Message-ID: <50BA6FF4.4030706@gmail.com>
Date: Sat, 01 Dec 2012 12:00:36 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net>
In-Reply-To: <50BA6A45.2000409@dcrocker.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: Sat, 01 Dec 2012 21:00:39 -0000

On 12/1/12 11:36 AM, Dave Crocker wrote:
> What actual problem is this trying to solve?  I see the reference to a
> 'reward', but wasn't aware that there is a perceived problem needing
> incentive to solve.

I gather this is one of those "everybody knows" problems, where
"everybody knows" that it takes what's perceived as too long to
get documents through the post-wglc/pre-publication process.  I
can see some value in parallelizing some processes.  I'd really
like to see AD review happen in parallel with working group last
call but I'm not sure that's possible given the already considerable
area direct workload.

There's probably some sort of sympathetic vibe running between
this document and recent discussion of nearly-cooked work being
brought to the IETF for standardization.  I think some sort of
variation on what Stephen's proposing is probably reasonable.
If somebody hasn't already documented how long it takes to get
through the various steps once a document is into wglc, it
would be worthwhile to start taking notes.

Melinda


From sm@resistor.net  Sat Dec  1 13:08:54 2012
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 0260321E80AD for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 13:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.667
X-Spam-Level: 
X-Spam-Status: No, score=-102.667 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HDkUAVjbq9hz for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 13:08:53 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC1E21E80AC for <ietf@ietf.org>; Sat,  1 Dec 2012 13:08:53 -0800 (PST)
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 qB1L7UCg003189; Sat, 1 Dec 2012 13:07:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354396054; bh=5vZ5cD5WvfW4WzmnnDcCU9qJuN/7/FM+isM7lf8oRiw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hZYovR0Mu9Bf05k4tfoYBeosJEHaVjxKLSSSL5v6OB8C6cZC2/0XHu7AeH3XmXxwQ h6ufUPSEyxrwE5Jb+5I5FGckGUXBq8KydCa5Fu9Sv52Sh4De0qL3ojRW1Zty7yPU+9 C01/UMzktmPx+YeeM8tSoUAAIpIjRF0N6SfjxRXA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354396054; i=@resistor.net; bh=5vZ5cD5WvfW4WzmnnDcCU9qJuN/7/FM+isM7lf8oRiw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NKzEbRAs3f1//e9stDlvJqLbquAqcjWdVc3LS4jLodgjV6lHrMeKqJIWwARJ1qS5L ADO2579IzSyGYfIrQmVG1tqi2vNrgbt1uDplstIvJI9viMDcY+68o28XgNP0W9B/LY gmsvuzbVwqtTzwc0LjbsHu92MJmrOGJh4sVyLo54=
Message-Id: <6.2.5.6.2.20121201123752.09384ef8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 01 Dec 2012 13:06:58 -0800
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: SM <sm@resistor.net>
Subject: Re: Idea for a process experiment to reward running code...
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie>
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, 01 Dec 2012 21:08:54 -0000

Hi Stephen,
At 12:12 01-12-2012, Stephen Farrell wrote:
>I've just posted an idea [1] for a small process improvement.
>If it doesn't seem crazy I'll try pursue it with the IESG as
>an RFC 3933 process experiment. If its universally hated then
>that's fine, it can die.

In Section 1:

   "The idea here is not to save the universe, nor to boil
    any oceans."

It's better to boil an ocean than to kill a fish.  :-)

   "1.  Working group last call (WGLC), IETF last call (IETF-LC) and Area
        Director (AD) review all run in parallel over the same two-week
        period."

You could skip the WGLC as you have the Last Call.

In Section 3:

   "2.  Where there are two or more WG chairs, all need to agree to fast-
        track processing."

That can be rolled into item 1.

Could you ask an AD to sponsor this draft and generate the Last Call?

Regards,
-sm

P.S. Make the draft experimental.  Add a one-year timer. 


From ynir@checkpoint.com  Sat Dec  1 13:22:25 2012
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 3707421F8B6E for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 13:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.367
X-Spam-Level: 
X-Spam-Status: No, score=-10.367 tagged_above=-999 required=5 tests=[AWL=0.232, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gv1pwsVN8YUf for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 13:22:24 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4ACF621F8B6A for <ietf@ietf.org>; Sat,  1 Dec 2012 13:22:24 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qB1LM2SJ010776; Sat, 1 Dec 2012 23:22:05 +0200
X-CheckPoint: {50BA74E2-2-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.14]) by IL-EX10.ad.checkpoint.com ([194.29.34.147]) with mapi id 14.02.0318.004; Sat, 1 Dec 2012 23:21:58 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: Idea for a process experiment to reward running code...
Thread-Topic: Idea for a process experiment to reward running code...
Thread-Index: AQHN0ABLDtHjWJVnsECZVQw96auh/5gERYOAgAAMu4A=
Date: Sat, 1 Dec 2012 21:21:56 +0000
Message-ID: <4613980CFC78314ABFD7F85CC30277210EDCF0BA@IL-EX10.ad.checkpoint.com>
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net>
In-Reply-To: <50BA6A45.2000409@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.250]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3355227CC4A40243B6C533B3B35BF6FA@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: Sat, 01 Dec 2012 21:22:25 -0000

On Dec 1, 2012, at 10:36 PM, Dave Crocker <dhc@dcrocker.net> wrote:

>=20
> What actual problem is this trying to solve?  I see the reference to a 'r=
eward', but wasn't aware that there is a perceived problem needing incentiv=
e to solve.
>=20

I think the problem is in the subject line. Documents go through working gr=
oups and the IETF proposing standards that have never been implemented, and=
 may never be implemented.

Why do they bother?  Maybe it looked like a good idea at the time. Maybe th=
ey want an RFC hoping to drive adoption. Maybe the want an RFC for their pe=
rsonal vanity, or to augment their LinkedIn profile.

Regardless of the reason, I agree that the IETF's resources are better spen=
t on stuff that will make it into running code. Not sure this is the right =
incentive, though. Waiting two more months, and probably making one extra r=
evision to the document seems to be a lower investment than actually implem=
enting (incentives only apply to people who would otherwise not implement t=
heir proposal)

Yoav



From dhc@dcrocker.net  Sat Dec  1 14:13:35 2012
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 EAE9E21F8B5D for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 14:13:35 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2chNJ4OE-Ih for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 14:13:35 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 73CDA21F8B5C for <ietf@ietf.org>; Sat,  1 Dec 2012 14:13:35 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB1MDYBc019500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Dec 2012 14:13:34 -0800
Message-ID: <50BA8106.6050503@dcrocker.net>
Date: Sat, 01 Dec 2012 14:13:26 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net> <50BA6FF4.4030706@gmail.com>
In-Reply-To: <50BA6FF4.4030706@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.17]); Sat, 01 Dec 2012 14:13:34 -0800 (PST)
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: Sat, 01 Dec 2012 22:13:36 -0000

On 12/1/2012 1:00 PM, Melinda Shore wrote:
> On 12/1/12 11:36 AM, Dave Crocker wrote:
>> What actual problem is this trying to solve?  I see the reference to a
>> 'reward', but wasn't aware that there is a perceived problem needing
>> incentive to solve.
>
> I gather this is one of those "everybody knows" problems, where
> "everybody knows" that it takes what's perceived as too long to
> get documents through the post-wglc/pre-publication process.


Yes.  Longstanding opinion held by many folk.  Might even be valid.

The problem is a failure to look carefully at wg lifecycle and consider 
where meaningful -- as opposed to 'appealing' -- improvements can be made.

At a minimum, any proposal for change should be expected to justify the 
specific problem it is claiming to solve -- that is, to establish the 
context that makes clear the problem is real and serious -- and that the 
proposed solution is also likely to have meaningful benefit.

I share the frustration about lengthy standardization, and particularly 
with delays at the end.  And certainly there is nothing wrong with 
adding parallelism where it makes sense.

However absent a consideration of the lifecycle, the current proposal is 
a random point change, quite possibly an example of looking for lost 
keys under a lamppost because that's where it's easiest to see.


> There's probably some sort of sympathetic vibe running between
> this document and recent discussion of nearly-cooked work being
> brought to the IETF for standardization.

rumblings of free-floating dis-ease, perhaps.  but are they really related?


> If somebody hasn't already documented how long it takes to get
> through the various steps once a document is into wglc, it
> would be worthwhile to start taking notes.

If a wg takes 2 years to get into wglc, a difference of a month doesn't 
matter, does it?  That's why I mean about total lifecycle.  Otherwise 
we're committing the classic system engineering error of inappropriate 
local optimization.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba.mailing.lists@gmail.com  Sat Dec  1 14:22:10 2012
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 6930F21E80AC for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 14:22:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzpY5moSZNSb for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 14:22:09 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 56F7E21E803F for <ietf@ietf.org>; Sat,  1 Dec 2012 14:22:09 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so1468809lbk.31 for <ietf@ietf.org>; Sat, 01 Dec 2012 14:22:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=kE4L6YlzWSmQx0hKJbSsT9qpeMjrO3o0/HSDwUGJdVI=; b=dUVr7GY8ivOeVUE59KJyUnmhIOIdRCMmwge7RI7B0KjZxxxtW5WgV9dCThZzFRMiff giptm+vhzoI3WaSMUjTpdQuFtI3jfyzxkFZXpMAylfAy5M4+l3pBvM4AFaQXGnOj29k4 3rOatPLati2rxQX1dqTIdtdh9whYjJaEbE/6K54gyxWp8KlG24DHImo6dW66EBq8P6Bi JkGaKH0VISze/URPgEyPamGHVlGiaP2hzyCkpiLEn/RtsRuyGZlKVe7FF4kvRn37c4kS zNR38bJJU7I0FrCEM/oZIExFhisU9YUkDrpZT0lWGEEWfFCqTq6s0W8G5bJ5lojLPvHc z8Ng==
MIME-Version: 1.0
Received: by 10.152.108.197 with SMTP id hm5mr5258302lab.45.1354400528301; Sat, 01 Dec 2012 14:22:08 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Sat, 1 Dec 2012 14:22:08 -0800 (PST)
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie>
Date: Sat, 1 Dec 2012 17:22:08 -0500
X-Google-Sender-Auth: JG7e_ZQkOCzJHrkT5uVJuphm10g
Message-ID: <CAC4RtVD0x3JsPR8qJ1BbVytU-yL96z-Sbr5hW9GetnEX-U3FQQ@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
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: Sat, 01 Dec 2012 22:22:10 -0000

> [1] http://tools.ietf.org/id/draft-farrell-ft

I have a serious problem with the premise of the proposal.

The short version is that if the process we're talking about is
useful, we should not shortcut it as a "reward" for anything.  And if
it's not useful, we should not be doing it, regardless of whether we
want to provide incentives or not.

In particular:

   1.  Working group last call (WGLC), IETF last call (IETF-LC) and Area
       Director (AD) review all run in parallel over the same two-week
       period.

Note that WGLC is not a part of our formal process, and that AD
Evaluation can take as little time as it takes for the responsible AD
to click the "Go directly to Last Call Requested" button in the
datatracker.  Therefore, making this step happen today is entirely up
to the working group chairs and the responsible AD.  Any chair who
thinks that a document has had enough review in the WG already can
send the document to the AD directly.  That chair can also ask the AD
to expedite her review and get Last Call started ASAP, and it's up to
the AD to decide whether that's appropriate.  We don't need a process
experiment for that.

That said, AD Evaluation often (VERY often) turns up things that would
otherwise come up in Last Call comments, including in directorate and
review team reviews.  It often corrects problems or gaps in the
protocol specification, issues with IANA requests, security issues,
and so on... which would take up a lot of other people's time as the
Last Call review goes on.  An AD who has been following the document
already might be happy going directly to Last Call Requested with just
a quick glance at the document (as I have with some documents), but
might have extensive comments about other documents, regardless of
whether there are implementations or not.

Kicking off Last Call is something that requires AD judgment, not some
sort of "reward" system.

   2.  Only comments that would be "DISCUSS-worthy" according to the
       IESG Discuss Criteria [DCRIT] need be handled during last call.
       Other comments can be handled or not, at the authors/editors
       discretion.

I'm puzzled by this.  First, a lot of things fall under the DISCUSS
criteria, but ADs decide not to give them DISCUSS status, depending
upon the situation.  I guess in item 3 you cover who decides this, but
as it's specified here it seems entirely too fluffy.  And it appears
to devalue the non-blocking comments more than they already are.
Again, if our process of making comments *of all sorts* has value,
then we shouldn't short-cut it.  It's already the case that the
responsible AD and the IESG as a whole get to decide which Last Call
comments "need to be handled" and which don't, so this really isn't a
process change either.  But I wouldn't want to say outright that
last-call comments that don't meet DISCUSS criterial will likely be
ignored in some "fast path" process that "rewards" a protocol for
having implementations.

   3.  After fast-track last-call, the document must either be returned
       to the WG, or else enter IESG review as soon as any changes
       required are made.  The relevant AD makes the decision as to
       whether changes are required and when those are completed
       sufficiently to move to the next stage.

This is no different to what we normally do: after Last Call ends, the
document goes into "Waiting for AD Go-Ahead" state, and the
responsible AD decides whether it's ready for IESG Evaluation or not.

I very strongly dislike the idea of saying that we'll "reward"
something by trimming (by a mere two or three weeks; what real value
does that have?) a process that we consider as adding value to our
documents.  And, again, if we think it doesn't add value, then let's
just do this as standard procedure, as we already can today, with no
process experiment at all.

Just tell all your WGCs that they can skip WGLC, and you'll send their
docs straight into Last Call as soon as you get them.

Barry

From stephen.farrell@cs.tcd.ie  Sat Dec  1 14:56:26 2012
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 97FE021F872C for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 14:56:26 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAPrwzAwGu8G for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 14:56:26 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id ED29C21F8702 for <ietf@ietf.org>; Sat,  1 Dec 2012 14:56:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 23B49BE4D; Sat,  1 Dec 2012 22:56:04 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DS8yW2Tohdv; Sat,  1 Dec 2012 22:56:03 +0000 (GMT)
Received: from [10.87.48.10] (unknown [86.42.22.137]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4AC3ABE49; Sat,  1 Dec 2012 22:56:03 +0000 (GMT)
Message-ID: <50BA8B03.7070002@cs.tcd.ie>
Date: Sat, 01 Dec 2012 22:56:03 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net> <50BA6FF4.4030706@gmail.com> <50BA8106.6050503@dcrocker.net>
In-Reply-To: <50BA8106.6050503@dcrocker.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Dec 2012 22:56:26 -0000

Hi Dave,

On 12/01/2012 10:13 PM, Dave Crocker wrote:
> 
> On 12/1/2012 1:00 PM, Melinda Shore wrote:
>> On 12/1/12 11:36 AM, Dave Crocker wrote:
>>> What actual problem is this trying to solve?  I see the reference to a
>>> 'reward', but wasn't aware that there is a perceived problem needing
>>> incentive to solve.
>>
>> I gather this is one of those "everybody knows" problems, where
>> "everybody knows" that it takes what's perceived as too long to
>> get documents through the post-wglc/pre-publication process.
> 
> 
> Yes.  Longstanding opinion held by many folk.  Might even be valid.
> 
> The problem is a failure to look carefully at wg lifecycle and consider
> where meaningful -- as opposed to 'appealing' -- improvements can be made.
> 
> At a minimum, any proposal for change should be expected to justify the
> specific problem it is claiming to solve -- 

Disagree. RFC 3933 says:

"A statement of the problem expected to be resolved is
      desirable but not required..."

There's a reason for that IMO - all proposed process changes seem
to generate *lots* of comment that there's a better problem to
solve elsewhere.

> that is, to establish the
> context that makes clear the problem is real and serious -- and that the
> proposed solution is also likely to have meaningful benefit.
> 
> I share the frustration about lengthy standardization, and particularly
> with delays at the end.  And certainly there is nothing wrong with
> adding parallelism where it makes sense.
> 
> However absent a consideration of the lifecycle, the current proposal is
> a random point change, quite possibly an example of looking for lost
> keys under a lamppost because that's where it's easiest to see.

You may be right, I don't make any claim that this is going to
be super-good. OTOH maybe this is worth trying to see if we like
it or not.

Cheers,
S.

>> There's probably some sort of sympathetic vibe running between
>> this document and recent discussion of nearly-cooked work being
>> brought to the IETF for standardization.
> 
> rumblings of free-floating dis-ease, perhaps.  but are they really related?
> 
> 
>> If somebody hasn't already documented how long it takes to get
>> through the various steps once a document is into wglc, it
>> would be worthwhile to start taking notes.
> 
> If a wg takes 2 years to get into wglc, a difference of a month doesn't
> matter, does it?  That's why I mean about total lifecycle.  Otherwise
> we're committing the classic system engineering error of inappropriate
> local optimization.
> 
> d/

From stephen.farrell@cs.tcd.ie  Sat Dec  1 15:04:58 2012
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 7F70821E80B7 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:04:58 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lXxoIi23iMNc for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:04:57 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 763F311E8099 for <ietf@ietf.org>; Sat,  1 Dec 2012 15:04:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7E785BE58; Sat,  1 Dec 2012 23:04:35 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j4EjQM1SJWry; Sat,  1 Dec 2012 23:04:34 +0000 (GMT)
Received: from [10.87.48.10] (unknown [86.42.22.137]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id EE29DBE53; Sat,  1 Dec 2012 23:04:33 +0000 (GMT)
Message-ID: <50BA8D01.1050508@cs.tcd.ie>
Date: Sat, 01 Dec 2012 23:04:33 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <CAC4RtVD0x3JsPR8qJ1BbVytU-yL96z-Sbr5hW9GetnEX-U3FQQ@mail.gmail.com>
In-Reply-To: <CAC4RtVD0x3JsPR8qJ1BbVytU-yL96z-Sbr5hW9GetnEX-U3FQQ@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Sat, 01 Dec 2012 23:04:58 -0000

On 12/01/2012 10:22 PM, Barry Leiba wrote:
>> [1] http://tools.ietf.org/id/draft-farrell-ft
> 
> I have a serious problem with the premise of the proposal.
> 
> The short version is that if the process we're talking about is
> useful, we should not shortcut it as a "reward" for anything.  

I disagree. The process is neither useful nor just a PITA. Its both,
depending on what document and point of view you pick. So yours is
a false dichotomy I think. And even the process now were useful 100%
of the time, shortcutting it might still be an improvement. So I just
don't think you have a winning argument based on logic.

> And if
> it's not useful, we should not be doing it, regardless of whether we
> want to provide incentives or not.
> 
> In particular:
> 
>    1.  Working group last call (WGLC), IETF last call (IETF-LC) and Area
>        Director (AD) review all run in parallel over the same two-week
>        period.
> 
> Note that WGLC is not a part of our formal process, 

Whatever. Its a reality.

> and that AD
> Evaluation can take as little time as it takes for the responsible AD
> to click the "Go directly to Last Call Requested" button in the
> datatracker.  

Or longer. Much longer sometimes if an AD is slow or
authors need to re-spin and are slow. Both happen.

I had meant to try measure that from Jari's data before shooting
the draft out but didn't get a chance. My bet is that if this
worked well, it might save about 6 weeks on average, for drafts
where its suitable. Or maybe more. We should see if we can get
some numbers though, I do agree with that.

But more blow-by-blow responses will only likely rathole us
here so I'll stop here for now. (But I'm happy to do send that
if you think its useful.)

What's wrong with doing the experiment and finding out if its
better, worse or not detectably different?

I, and I believe lots of us, do want to encourage running code
more than now. This is one attempt to help with that. Why not
try it and see?

S.

> Therefore, making this step happen today is entirely up
> to the working group chairs and the responsible AD.  Any chair who
> thinks that a document has had enough review in the WG already can
> send the document to the AD directly.  That chair can also ask the AD
> to expedite her review and get Last Call started ASAP, and it's up to
> the AD to decide whether that's appropriate.  We don't need a process
> experiment for that.
> 
> That said, AD Evaluation often (VERY often) turns up things that would
> otherwise come up in Last Call comments, including in directorate and
> review team reviews.  It often corrects problems or gaps in the
> protocol specification, issues with IANA requests, security issues,
> and so on... which would take up a lot of other people's time as the
> Last Call review goes on.  An AD who has been following the document
> already might be happy going directly to Last Call Requested with just
> a quick glance at the document (as I have with some documents), but
> might have extensive comments about other documents, regardless of
> whether there are implementations or not.
> 
> Kicking off Last Call is something that requires AD judgment, not some
> sort of "reward" system.
> 
>    2.  Only comments that would be "DISCUSS-worthy" according to the
>        IESG Discuss Criteria [DCRIT] need be handled during last call.
>        Other comments can be handled or not, at the authors/editors
>        discretion.
> 
> I'm puzzled by this.  First, a lot of things fall under the DISCUSS
> criteria, but ADs decide not to give them DISCUSS status, depending
> upon the situation.  I guess in item 3 you cover who decides this, but
> as it's specified here it seems entirely too fluffy.  And it appears
> to devalue the non-blocking comments more than they already are.
> Again, if our process of making comments *of all sorts* has value,
> then we shouldn't short-cut it.  It's already the case that the
> responsible AD and the IESG as a whole get to decide which Last Call
> comments "need to be handled" and which don't, so this really isn't a
> process change either.  But I wouldn't want to say outright that
> last-call comments that don't meet DISCUSS criterial will likely be
> ignored in some "fast path" process that "rewards" a protocol for
> having implementations.
> 
>    3.  After fast-track last-call, the document must either be returned
>        to the WG, or else enter IESG review as soon as any changes
>        required are made.  The relevant AD makes the decision as to
>        whether changes are required and when those are completed
>        sufficiently to move to the next stage.
> 
> This is no different to what we normally do: after Last Call ends, the
> document goes into "Waiting for AD Go-Ahead" state, and the
> responsible AD decides whether it's ready for IESG Evaluation or not.
> 
> I very strongly dislike the idea of saying that we'll "reward"
> something by trimming (by a mere two or three weeks; what real value
> does that have?) a process that we consider as adding value to our
> documents.  And, again, if we think it doesn't add value, then let's
> just do this as standard procedure, as we already can today, with no
> process experiment at all.
> 
> Just tell all your WGCs that they can skip WGLC, and you'll send their
> docs straight into Last Call as soon as you get them.
> 
> Barry
> 

From dhc@dcrocker.net  Sat Dec  1 15:14:09 2012
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 4845611E80CC for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:14:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZMYyEGSiEFO for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:14:08 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A9A0B11E80A5 for <ietf@ietf.org>; Sat,  1 Dec 2012 15:14:08 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB1NE5Kh026572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Dec 2012 15:14:05 -0800
Message-ID: <50BA8F36.9070501@dcrocker.net>
Date: Sat, 01 Dec 2012 15:13:58 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net> <50BA6FF4.4030706@gmail.com> <50BA8106.6050503@dcrocker.net> <50BA8B03.7070002@cs.tcd.ie>
In-Reply-To: <50BA8B03.7070002@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sat, 01 Dec 2012 15:14:06 -0800 (PST)
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: Sat, 01 Dec 2012 23:14:09 -0000

Stephen,

On 12/1/2012 2:56 PM, Stephen Farrell wrote:
>> At a minimum, any proposal for change should be expected to justify the
>> specific problem it is claiming to solve --
>
> Disagree. RFC 3933 says:
>
> "A statement of the problem expected to be resolved is
>        desirable but not required..."

The IETF has become a curious place.  This is twice in two days I've 
cited pragmatics and been taken for citing formal requirements. Believe 
it or not "should be expected" is pretty lousy language to invoke for 
citing formal organizational requirements.

IMO a proposal that does not justify itself with a clear statement of 
the problem, the seriousness of the problem, and a basis for believing 
that the proposed solution will matter is frankly not a very serious 
proposal.  It has done none of the hard work of distinguishing itself 
from myriad other, appealing proposals that might randomly be generated.

I do realize that IETF culture has come to enjoy making and pursuing 
proposals that satisfy none of these criteria.  That's why I've taken to 
noting that we use the word "experiment" to justify a failure to do 
adequate homework or be accountable for the outcome.  (Or even be able 
to measure the outcome.)


> There's a reason for that IMO - all proposed process changes seem
> to generate *lots* of comment that there's a better problem to
> solve elsewhere.

Stephen, what you seem to be saying is that it isn't reasonable to 
expect serious analysis in the formulation of a proposal, when it is put 
forward, because other folk might/will prefer a different -- and equally 
ill-formulated proposal?

It certainly is a pain to have to provide meaningful justification.

On the other hand, it's pretty irresponsible not to.


>> that is, to establish the
>> context that makes clear the problem is real and serious -- and that the
>> proposed solution is also likely to have meaningful benefit.
>>
>> I share the frustration about lengthy standardization, and particularly
>> with delays at the end.  And certainly there is nothing wrong with
>> adding parallelism where it makes sense.
>>
>> However absent a consideration of the lifecycle, the current proposal is
>> a random point change, quite possibly an example of looking for lost
>> keys under a lamppost because that's where it's easiest to see.
>
> You may be right, I don't make any claim that this is going to
> be super-good. OTOH maybe this is worth trying to see if we like
> it or not.

Maybe more cookies at breaks will produce better IETF work.

Maybe a posting limit of one message per day will produce better IETF work.

Maybe...

There's an infinite number of stray proposals any of us could formulate. 
  But they aren't free to pursue.

And relying on the whim of popular fashion -- oh, let's all follow 
today's pretty flashing proposal -- is mostly distracting from finding 
and fixing real, strategic issues.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From stephen.farrell@cs.tcd.ie  Sat Dec  1 15:21:41 2012
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 A7D7D21F869B for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:21:41 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXZCLdvKqOYN for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:21:41 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9DDB521F86A9 for <ietf@ietf.org>; Sat,  1 Dec 2012 15:21:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 91815BE58; Sat,  1 Dec 2012 23:21:18 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-ZG0BUQQLCF; Sat,  1 Dec 2012 23:21:17 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.31.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8A7ACBE53; Sat,  1 Dec 2012 23:21:17 +0000 (GMT)
Message-ID: <50BA90ED.9000202@cs.tcd.ie>
Date: Sat, 01 Dec 2012 23:21:17 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net> <50BA6FF4.4030706@gmail.com> <50BA8106.6050503@dcrocker.net> <50BA8B03.7070002@cs.tcd.ie> <50BA8F36.9070501@dcrocker.net>
In-Reply-To: <50BA8F36.9070501@dcrocker.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Dec 2012 23:21:41 -0000

On 12/01/2012 11:13 PM, Dave Crocker wrote:
> Stephen,
> 
> On 12/1/2012 2:56 PM, Stephen Farrell wrote:
>>> At a minimum, any proposal for change should be expected to justify the
>>> specific problem it is claiming to solve --
>>
>> Disagree. RFC 3933 says:
>>
>> "A statement of the problem expected to be resolved is
>>        desirable but not required..."
> 
> The IETF has become a curious place.  This is twice in two days I've
> cited pragmatics and been taken for citing formal requirements. Believe
> it or not "should be expected" is pretty lousy language to invoke for
> citing formal organizational requirements.
> 
> IMO a proposal that does not justify itself with a clear statement of
> the problem, the seriousness of the problem, and a basis for believing
> that the proposed solution will matter is frankly not a very serious
> proposal.  It has done none of the hard work of distinguishing itself
> from myriad other, appealing proposals that might randomly be generated.
> 
> I do realize that IETF culture has come to enjoy making and pursuing
> proposals that satisfy none of these criteria.  That's why I've taken to
> noting that we use the word "experiment" to justify a failure to do
> adequate homework or be accountable for the outcome.  (Or even be able
> to measure the outcome.)

IMO IETF culture has become too process-driven. And yes, I do
interpret your question (which is not unreasonable on its face)
to be saying that a justification is formally required.

My reluctance to get into this is based on an opinion that process
change proposals with more words attached tend to just not happen,
so fewer words is better. And I also think you and many others are
well placed to decide if you think this is a worthwhile change or
not, independent of any reasons for which I propose it. So I really
do think all the motivation text that'd be perfect fodder for
endless discussion is neither necessary nor useful here.

Cheers,
S.

>> There's a reason for that IMO - all proposed process changes seem
>> to generate *lots* of comment that there's a better problem to
>> solve elsewhere.
> 
> Stephen, what you seem to be saying is that it isn't reasonable to
> expect serious analysis in the formulation of a proposal, when it is put
> forward, because other folk might/will prefer a different -- and equally
> ill-formulated proposal?
> 
> It certainly is a pain to have to provide meaningful justification.
> 
> On the other hand, it's pretty irresponsible not to.
> 
> 
>>> that is, to establish the
>>> context that makes clear the problem is real and serious -- and that the
>>> proposed solution is also likely to have meaningful benefit.
>>>
>>> I share the frustration about lengthy standardization, and particularly
>>> with delays at the end.  And certainly there is nothing wrong with
>>> adding parallelism where it makes sense.
>>>
>>> However absent a consideration of the lifecycle, the current proposal is
>>> a random point change, quite possibly an example of looking for lost
>>> keys under a lamppost because that's where it's easiest to see.
>>
>> You may be right, I don't make any claim that this is going to
>> be super-good. OTOH maybe this is worth trying to see if we like
>> it or not.
> 
> Maybe more cookies at breaks will produce better IETF work.
> 
> Maybe a posting limit of one message per day will produce better IETF work.
> 
> Maybe...
> 
> There's an infinite number of stray proposals any of us could formulate.
>  But they aren't free to pursue.
> 
> And relying on the whim of popular fashion -- oh, let's all follow
> today's pretty flashing proposal -- is mostly distracting from finding
> and fixing real, strategic issues.
> 
> d/
> 

From melinda.shore@gmail.com  Sat Dec  1 15:52:03 2012
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 7DF4921E80EC for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:52:03 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rT2jx1AEQlFD for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 15:52:03 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 934F021E80B7 for <ietf@ietf.org>; Sat,  1 Dec 2012 15:51:58 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so1071885pad.31 for <ietf@ietf.org>; Sat, 01 Dec 2012 15:51:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=I4heWpVwgd+1Ku2nMoyj4jYu7Kb49ZswO1g8BLz0LKE=; b=yZ1/avJX6L/HITWYl+bxsPWhapq151gLYQMqPI9TJgtSHODMvZa4nzC4chhar+TPxe jM9fkgmY+Shl2/7YMg8d2sRaRlai3a9WMfGg1JjE5I7WSbWbHyJxzHAuI9+R0N+qtOQf /z7fBzsQECZqBnuUT4LIAEq/c1hjZMJysFik7qlfec8DekFigP2HddGWOGcD0zQgSAh7 8+r7JZuBunmBp4Uwu6JfqiDNuvBH9JbRUlnHztNIMQ64xgh8idP7FikJlSYqi7xzvs0t eEHbEgw08hSrIjnRTcEfcpuOUMfeihFhmSoakSsxXmyu7s1EP/NlodyLArWzmGMMEOP/ YWrQ==
Received: by 10.68.232.201 with SMTP id tq9mr17460933pbc.12.1354405918314; Sat, 01 Dec 2012 15:51:58 -0800 (PST)
Received: from spandex.local (66-230-87-153-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.153]) by mx.google.com with ESMTPS id l5sm5350754paz.14.2012.12.01.15.51.56 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 01 Dec 2012 15:51:57 -0800 (PST)
Message-ID: <50BA981B.9060505@gmail.com>
Date: Sat, 01 Dec 2012 14:51:55 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net> <50BA6FF4.4030706@gmail.com> <50BA8106.6050503@dcrocker.net> <50BA8B03.7070002@cs.tcd.ie> <50BA8F36.9070501@dcrocker.net> <50BA90ED.9000202@cs.tcd.ie>
In-Reply-To: <50BA90ED.9000202@cs.tcd.ie>
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, 01 Dec 2012 23:52:03 -0000

On 12/1/12 2:21 PM, Stephen Farrell wrote:
> My reluctance to get into this is based on an opinion that process
> change proposals with more words attached tend to just not happen,
> so fewer words is better.

I think that's actually a pretty terrible reason.  The goal is
not to get the proposal through, the goal is to improve
something.  That said, while I don't like change just for the
sake of change I think that change for the sake of betterment is
a very good thing indeed.  The main thing is that I've been trying
to figure out where the harm would be here and I haven't been
able to identify anything substantive.  I'd be good with giving
this a limited run and seeing how it goes.

Melinda


From barryleiba@gmail.com  Sat Dec  1 16:22:00 2012
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 06BA421E80FB for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 16:22:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9tjEz+b7ACFR for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 16:21:58 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5CF4E21E80B7 for <ietf@ietf.org>; Sat,  1 Dec 2012 16:21:54 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so883312vcb.31 for <ietf@ietf.org>; Sat, 01 Dec 2012 16:21:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=MJBb31ptwypUyeVe7SvovSkmdyDqL3cd/ui8F4bxk54=; b=xifPkYr8+AMOwLLXu/eKqELKsbEgi3fAYVbF5if3Y+IMIN1Spm/OQw0bH2hiylPPgf sm8Ca0tHpVPZQrtErqgXYZTn2hnm+VcIfEH3R28y8Zt4uxrqMfdgpaArhpNjAsrEVGMl nqcOm5Nui0VhLwTs9BxIJAw1PT8SD2KKSBfE04EgdxUU+xZmBS9NTCuhhJ7EyHY/3M0U IPJFikUO09VdRwaruHL0pQMuxfPgfej+J2q6K0llQQDiH5Tvafc+vFURogjpBqcaxjeD I07lfK1yc1s/JM4isn6SDzASgn6l9Y09kL6pSNq+8R4+uw1eiBhZBChge01mc8fNNxb2 CRvQ==
MIME-Version: 1.0
Received: by 10.220.119.196 with SMTP id a4mr4979798vcr.19.1354407713860; Sat, 01 Dec 2012 16:21:53 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Sat, 1 Dec 2012 16:21:53 -0800 (PST)
In-Reply-To: <50BA8D01.1050508@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie> <CAC4RtVD0x3JsPR8qJ1BbVytU-yL96z-Sbr5hW9GetnEX-U3FQQ@mail.gmail.com> <50BA8D01.1050508@cs.tcd.ie>
Date: Sat, 1 Dec 2012 19:21:53 -0500
X-Google-Sender-Auth: -P7xZVqji06Nqk71ikXvz5o6NwE
Message-ID: <CALaySJ+zoTJB_A9-ihZomYUggZ=_sYnNC0i651E4hszePi08Yw@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
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: Sun, 02 Dec 2012 00:22:00 -0000

>> I have a serious problem with the premise of the proposal.
>>
>> The short version is that if the process we're talking about is
>> useful, we should not shortcut it as a "reward" for anything.
>
> I disagree. The process is neither useful nor just a PITA. Its both,
> depending on what document and point of view you pick. So yours is
> a false dichotomy I think. And even the process now were useful 100%
> of the time, shortcutting it might still be an improvement. So I just
> don't think you have a winning argument based on logic.

Let me try saying it again, with different phrasing:
If, for any particular document, what you propose is the right way to
handle that document, that handling should not be handed out as a
"reward".  And if, for that document, this is *not* the right way to
handle it, it's a bad idea to do so anyway.

>>    1.  Working group last call (WGLC), IETF last call (IETF-LC) and Area
>>        Director (AD) review all run in parallel over the same two-week
>>        period.
>>
>> Note that WGLC is not a part of our formal process,
>
> Whatever. Its a reality.

No, Stephen, this isn't a "whatever".  You're proposing an experiment
for changing process.  I'm reminding you that what you're proposing is
not a change in formal process, but something you can do *right now*,
today, if you and a WGC want to.  Please don't dismiss that with
"Whatever."

>> and that AD
>> Evaluation can take as little time as it takes for the responsible AD
>> to click the "Go directly to Last Call Requested" button in the
>> datatracker.
>
> Or longer. Much longer sometimes if an AD is slow or
> authors need to re-spin and are slow. Both happen.

You're entirely missing the point: of *course* it *can* take longer.
My point is that it already doesn't have to, if the WGC and the
responsible AD agree that it shouldn't.

> What's wrong with doing the experiment and finding out if its
> better, worse or not detectably different?

Nothing: you didn't respond to my final sentence, which I'll repeat here:

>> Just tell all your WGCs that they can skip WGLC, and you'll send their
>> docs straight into Last Call as soon as you get them.

> I, and I believe lots of us, do want to encourage running code
> more than now. This is one attempt to help with that. Why not
> try it and see?

Because as a "reward" for claiming to have running code, I think it's
a terrible idea.  As a way of handling the process for documents where
it makes sense to, I think it's fine.  If you want the criteria for
your WGs to be "You have to have running code," knock yourself out.
Any other ADs who want to do it that way can join you.  If you want to
codify that for everyone, I think you need to do a lot more in the
line of criteria for adequate implementations, and so on.  If I spend
half a day knocking out some crappy untested code, is that good
enough?  If not, how much testing does it need?  I'm pretty sure we
don't want to go there.

Barry

From barryleiba@gmail.com  Sat Dec  1 16:27:44 2012
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 53E5B21E80A0 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 16:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NS99k2EUdPl for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 16:27:44 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C7C8121E8095 for <ietf@ietf.org>; Sat,  1 Dec 2012 16:27:43 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so885255vcb.31 for <ietf@ietf.org>; Sat, 01 Dec 2012 16:27:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nZA9QiwNo9tg/KRms6BfJr5Ot68yy9dkTjN/RJk8IUY=; b=iGnXbWVO0P3W47SpQT70eb8wrz596HKc/7AZ+aX53chA4RvZAdCkABEdnpgjIA6Xg+ YyaQvVKeRrCQDHGAirCi2vjYiNcG0e6nR7UC3SNcL6q1Cn1gDFtz/GPrfQq729ZLkL7q 5jtDqhe8Ya5tHRCt3VHIIVXfPZ1JcEJ7uhHI4GABJ2HRzB1ZUICRPFIO11hHYp8JT+ah M477DF/Y5ShhLrxobIcrtdFjh0aCUQBiqBTJvTeucq/9PfxAJniA3jp+AIyWSljVomf6 k0sEb2GATQRXGfF5rTYcltp67NURMPK6JmEs4XNR51zrj7EzE9fWlRbxGrkjmnddA4wE aANA==
MIME-Version: 1.0
Received: by 10.220.149.69 with SMTP id s5mr4983465vcv.23.1354408062118; Sat, 01 Dec 2012 16:27:42 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Sat, 1 Dec 2012 16:27:41 -0800 (PST)
In-Reply-To: <CALaySJ+zoTJB_A9-ihZomYUggZ=_sYnNC0i651E4hszePi08Yw@mail.gmail.com>
References: <50BA64AB.3010106@cs.tcd.ie> <CAC4RtVD0x3JsPR8qJ1BbVytU-yL96z-Sbr5hW9GetnEX-U3FQQ@mail.gmail.com> <50BA8D01.1050508@cs.tcd.ie> <CALaySJ+zoTJB_A9-ihZomYUggZ=_sYnNC0i651E4hszePi08Yw@mail.gmail.com>
Date: Sat, 1 Dec 2012 19:27:41 -0500
X-Google-Sender-Auth: mPx5sJ5yAh4wZdESMOYVG5njbsY
Message-ID: <CALaySJLhQ2pZzpezkvxbZSOGkrQ4pTBsxDdngE67eeaT-D2XMA@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
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: Sun, 02 Dec 2012 00:27:44 -0000

>> I, and I believe lots of us, do want to encourage running code
>> more than now. This is one attempt to help with that. Why not
>> try it and see?
>
> Because as a "reward" for claiming to have running code, I think it's
> a terrible idea.  As a way of handling the process for documents where
> it makes sense to, I think it's fine.  If you want the criteria for
> your WGs to be "You have to have running code," knock yourself out.

Oh, and I did forget one other thing I'd meant to say:
What, actually is the experiment?  It seems to me the experiment is to
see if this actually encourages more "running code", which means that
to have a meaningful experiment you'll need to be able to compare how
many protocol documents represent running code (for some definition of
that) *today*, and then look at the same thing again after we've been
doing this for a while.

Do you have any baseline measurements?

Barry

From hsantos@isdg.net  Sat Dec  1 16:47:21 2012
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 6A8601F0C69 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 16:47:21 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t-JCPaqNdPhS for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 16:47:20 -0800 (PST)
Received: from groups.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id D065C1F0C5C for <ietf@ietf.org>; Sat,  1 Dec 2012 16:47:11 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2049; t=1354409217; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=xo2egkmw1w0bjutFbXyGgYl02Z4=; b=pq9NpHto4zEHI0aphtb/ wHwlVFLGZ9ekbdSHfASqqpSw4bb6EWqkO3fqQmad2Ckp7PML665TaIbtUflmtt7l +c+oesENoriiICJVx6iLiMur77/o+nbrqvDHAsgLr+xaQt02sKWTQwIJqBEOXR+0 Qr/rBdpF+r1NLAuTuCN7loI=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 01 Dec 2012 19:46:57 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1840981055.8610.3948; Sat, 01 Dec 2012 19:46:56 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2049; t=1354408850; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=TAqC1Y1 m1zniKkRDA6GT6dIAKChoDcheTtY3CJ4nLKM=; b=Tl6tTqk10dJWRUH+TcepNyX AUprNOXJbPgAJ2JWaqo88udAf/0d93mdpdj/+MKAQfNKR/BA3WFKJ9L5bBhBPkMH 6hoG2T2hlkyMLHT4Bh+0WG+6fjjwxhXWJfi+7PXveRFQ9yq4lJKKOt3J8+LaTTNL kt2lHg/LUwBk3lsjHLKc=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 01 Dec 2012 19:40:50 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2439713585.10.5552; Sat, 01 Dec 2012 19:40:49 -0500
Message-ID: <50BAA518.1030208@isdg.net>
Date: Sat, 01 Dec 2012 19:47:20 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
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: Sun, 02 Dec 2012 00:47:21 -0000

This proposal sounds interesting but couldn't it run into conflicts 
when there are competition in running code?   Who's running code do 
you fast track?  How does it apply in the protocol updates area, i.e. 
BIS work?

This proposal and thread, similar to the recent others, all seem to be 
looking for endorsing methods for lack of a better term, "rubber 
stamping" and fast tracking work items, in particular when there are 
WG related barriers holding back the WG work item(s) production progress.

I personally do not have an issue with expediting work when the proper 
protocol engineering is done and the adequate engineering reviews are 
done, in fact, I depend on the IETF/IESG engineering do this work.  I 
depend on the long time wisdom and engineering judgment of the IETF 
leaders and reviewers to watch over sensitive engineering issues, 
including conflict of interest related matters.

In the end, we are talking about trusting the process.  If IETF 
participants, especially those who don't attend meetings and long 
participated remotely or via mailing list, lose faith in the WG 
process, these process change proposals may expedite IETF work, but 
they may also handicap the potential of a proposed standard, change 
and industry following.

--
HLS

Stephen Farrell wrote:
> Hi all,
> 
> I've just posted an idea [1] for a small process improvement.
> If it doesn't seem crazy I'll try pursue it with the IESG as
> an RFC 3933 process experiment. If its universally hated then
> that's fine, it can die.
> 
> The IESG have seen (more-or-less) this already but it hasn't
> be discussed, so this is just a proposal from me and has no
> "official" status whatsoever.
> 
> Any comments, suggestions or better ideas are very welcome.
> Feel free to send me comments off list for now, or on this
> list I guess. If there's loads of email (always possible,
> this being a process thing;-) we can move to some other list.
> 
> Regards,
> Stephen.
> 
> [1] http://tools.ietf.org/id/draft-farrell-ft
> 
> 

-- 
HLS



From hsantos@isdg.net  Sat Dec  1 18:19:08 2012
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 35EDE21E8095 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 18:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.138
X-Spam-Level: 
X-Spam-Status: No, score=-102.138 tagged_above=-999 required=5 tests=[AWL=-0.461, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Efe9DVZMyZWj for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 18:19:07 -0800 (PST)
Received: from mail.catinthebox.net (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 555C521E808C for <ietf@ietf.org>; Sat,  1 Dec 2012 18:19:06 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1102; t=1354414737; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=pEOm2yjvk2yCtEjBIxemycHWKRE=; b=g16XA3YQBl6B+h63Px1g oGqs4TN7Xn6Mu5E1mOSZVkdexm0K4u9u3W6OtsYPxS7cV9bics5iOquYGphs2crX szFQ6ZQuOSZY+woAFMzZbPvr0sR8K2xPWQGgjduy+pz8kt89ATsuYDYr5+T0x7FG 46aOUs4tPxj9lpuKHX4wulE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 01 Dec 2012 21:18:57 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1846501260.8610.3472; Sat, 01 Dec 2012 21:18:57 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1102; t=1354414369; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=QNQ8DV1 zAoUi/WVMVZhxSu5Vn1Zn4gZW2GzODRyPhn8=; b=MjETJEGAOe05EqDMSBQp2pm 9DYgYYx9q7r6UoMqfd1WWIpOwMCxiG1XXBBR5pvdmEBEVOTg+H6eGfpMHc2Fz9Jn ogN9TjsXdni8dw1E4WOA3Q2ENMPWHTnpzgyx9IZPzUZ4aRTq1bNgXYa4LSwtAA3g CjmYCnILOXz6Cme1T24A=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 01 Dec 2012 21:12:49 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2445232725.10.5756; Sat, 01 Dec 2012 21:12:48 -0500
Message-ID: <50BABAA9.9000900@isdg.net>
Date: Sat, 01 Dec 2012 21:19:21 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net>	<50BA6FF4.4030706@gmail.com> <50BA8106.6050503@dcrocker.net>	<50BA8B03.7070002@cs.tcd.ie> <50BA8F36.9070501@dcrocker.net>	<50BA90ED.9000202@cs.tcd.ie> <50BA981B.9060505@gmail.com>
In-Reply-To: <50BA981B.9060505@gmail.com>
Content-Type: text/plain; charset=UTF-8; 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: Sun, 02 Dec 2012 02:19:08 -0000

Melinda Shore wrote:
> On 12/1/12 2:21 PM, Stephen Farrell wrote:
>> My reluctance to get into this is based on an opinion that process
>> change proposals with more words attached tend to just not happen,
>> so fewer words is better.
> 
> I think that's actually a pretty terrible reason.  The goal is
> not to get the proposal through, the goal is to improve
> something.  That said, while I don't like change just for the
> sake of change I think that change for the sake of betterment is
> a very good thing indeed.  The main thing is that I've been trying
> to figure out where the harm would be here and I haven't been
> able to identify anything substantive.  I'd be good with giving
> this a limited run and seeing how it goes.

I would be more comfortable with the proposal if its applied only to 
new protocols, ideas, methods, etc.  The conflicts come when applying 
it to established standards, methods or BIS work.  While its possible 
to fast track the obvious, where there is potential issues, the 
proposal needs to be sensitive to fast tracking problematic issues.

-- 
HLS



From randy@qti.qualcomm.com  Sat Dec  1 21:52:57 2012
Return-Path: <randy@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 6862421F8A6C for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 21:52:57 -0800 (PST)
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.404, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iKjtyTvuNGQx for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 21:52:56 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8321A21F8A69 for <ietf@ietf.org>; Sat,  1 Dec 2012 21:52:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354426612; x=1385962612; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=v9AEgaNIkOxJn8NrUDA90PlkFBHgwMS9Xvd4v86VWw4=; b=xnco7PZbNY2n4nF6vNBXv01aGspCZtFuiPnNsDo1C5vY15PiTyNy2ei/ +f3TR0ZFnDWEtn1P12q1CgM8Zl0Bsc0QQ0MTRgaJnZsMPZHbea6HV8dTS VOCwKuVpQGV49MyNTfc9gWj/JDJo+5fY4P+486f6CZ7youwD3Z8LAy+Qd o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6913"; a="10066156"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 01 Dec 2012 21:36:50 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6913"; a="2945967"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Dec 2012 21:52:54 -0800
Received: from dhcp184-48-45-14.hroa.orl.wayport.net (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 1 Dec 2012 21:52:54 -0800
Message-ID: <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>
In-Reply-To: <50BA18B8.3090306@network-heretics.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com>
X-Mailer: Eudora for Mac OS X
Date: Sat, 1 Dec 2012 14:41:23 -0800
To: Keith Moore <moore@network-heretics.com>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Dec 2012 05:52:57 -0000

At 9:48 AM -0500 12/1/12, Keith Moore wrote:

>  On 11/29/2012 06:06 PM, Pete Resnick wrote:
>>  On 11/29/12 3:45 PM, Lee Howard wrote:
>>>  I can't take notes while I'm standing up, facilitating discussion.
>>
>>  Interesting. I am forced to (only somewhat facetiously) ask: Why 
>> are *you* standing up, facilitating discussion, if you are the 
>> editor? Shouldn't that be the chair's job? More seriously: Since 
>> we started this PowerPoint/Comments-at-the-mic thing oh so many 
>> years ago, doing document reviews in presentation form where the 
>> editor is the one doing the slides has created this problem. 
>> Perhaps a better mode would be for the editor to write up the list 
>> of open issues, have the chair project them if need be, and the 
>> editor can get up to the mic with explanations/questions as needed 
>> but otherwise remain seated so they can jot down the notes they 
>> need. I think I've done something like that a long time ago as an 
>> editor. Worth trying, I'd think.
>  +1
>
>  More generally, every time I go to IETF I'm appalled that working 
> groups have gotten into the habit of filling the time with 
> PowerPoint presentations.[*]   PowerPoint (and similar tools) 
> should be used sparingly, if at all.   Most of the time, the 
> projector should be off, or the screen blank.
>
>  The point of IETF meetings is to facilitate discussion, not to show 
> things to people.
>
>  PowerPoint tells meeting participants to be passive, or that it's 
> okay to take up space in the meeting room while browsing the web 
> and not paying attention, not being engaged.  Both of these are 
> detrimental to IETF work.
>
>  Keith
>
>  [*] And yes, I realize that this has been the case for over 10 
> years, but I remember when it was not the case.

When I started, WGs had projectors on, but were used as white boards, 
to facilitate discussion.  The editor or anyone wanting to discuss an 
issue would write out the topics on a transparent sheet of plastic 
and project it.  As the discussion developed, points would be written 
on it.  It seemed to work.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If you lend someone $20, and never see that person again,
it was probably worth it.

From randy@psg.com  Sat Dec  1 22:19:45 2012
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 8F8FC21F8F98 for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 22:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYjIU8hPQ2AE for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 22:19:45 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 319EF21F8F95 for <ietf@ietf.org>; Sat,  1 Dec 2012 22:19:45 -0800 (PST)
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 1Tf2tx-0004c0-K0; Sun, 02 Dec 2012 06:19:42 +0000
Date: Sun, 02 Dec 2012 15:19:40 +0900
Message-ID: <m2obidvuv7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
In-Reply-To: <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.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: 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: Sun, 02 Dec 2012 06:19:45 -0000

sadly, too many of us remember writing on scrolls of acetate.  i
imagine that some remember stone and chisels.

ok, just for a gedanken experiment of one extreme,

  o remove the projector.  [ omg!  how will we show the note hell? ]

  o if there is an active draft that *really* needs f2f discussion,
    allocate time to discussing it.  if it does not *clearly* need
    face-time, discuss it on the mailing list.

  o no one is at the mic in front because there is no mic in front.

  o if folk really need to see a diagram, that is why the $dieties
    invented laptops.  the few people who do not have laptops have
    those new-fangled tablet thingies.

  o if someone has not read the draft, stay seated and shut up.

  o if someone wants to float a new idea worth describing, then give
    them five or ten minutes on the agenda to ask others for input,
    no preso/ppt.

randy

---

Power corrupts; Powerpoint corrupts absolutely.  -- Vint Cerf

From melinda.shore@gmail.com  Sat Dec  1 22:29:50 2012
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 4383D21F8EBD for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 22:29:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7ZHfchlhZaTN for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 22:29:49 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7F60B21F8BEA for <ietf@ietf.org>; Sat,  1 Dec 2012 22:29:49 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so771220dae.31 for <ietf@ietf.org>; Sat, 01 Dec 2012 22:29:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=GYRM78P2hJ2V4NmIHjYl0qz2vq7YRmlF6b8LiXN/lPM=; b=T3FSR5nXvKgJFl2l7GVfk39LuGGuvAtbf+O4GqnL894zNyUIelcuVh0gFfEOd9lbuj gv2tAJ0GbOTWwGK697fViJeiYpFXC9gyTxi9S54rMrlzyi7QETkBJac08JVIxP2jnCzx Y04R+5qVOCTqe3lparL83NMHQC/4KEXZQMmmwsFWjt/21CWjkCCZSt0DRv8hyt+NwfE+ MJo1h9w/p6cdBBZm3Xa+H7Jkk0BlXsUpb5tVTLXwQ90HROkzpkK+VuoEJe9iA+CG56r0 YDwIiNuF6ELG5+bvXB0J92zfNRPGlg9rtvcGe5t8Wjf1SFJoIC5ok/8EeyhxhMBE0GfT Uj4w==
Received: by 10.68.197.68 with SMTP id is4mr18918912pbc.30.1354429789238; Sat, 01 Dec 2012 22:29:49 -0800 (PST)
Received: from spandex.local (66-230-87-153-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.87.153]) by mx.google.com with ESMTPS id sk1sm4645442pbc.0.2012.12.01.22.29.47 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 01 Dec 2012 22:29:48 -0800 (PST)
Message-ID: <50BAF558.5040805@gmail.com>
Date: Sat, 01 Dec 2012 21:29:44 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com>
In-Reply-To: <m2obidvuv7.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, 02 Dec 2012 06:29:50 -0000

On 12/1/12 9:19 PM, Randy Bush wrote:
> sadly, too many of us remember writing on scrolls of acetate.  i
> imagine that some remember stone and chisels.

At the last meeting, for my own stuff I went with the old one-slide
approach.  However, it did occur to me that by doing that the slide(s)
lost its archival value (slim as that may have been) for people not
in the room.  Anyway.

Not really sure what can be done about this - you can say "discussion,
not presentation" until you're blue in the face and the outcome of all
that will be a blue face but presentations during the meetings anyway.
Ultimately I expect it comes down to how individual chairs want to
run meetings.

Melinda


From randy@qti.qualcomm.com  Sat Dec  1 23:33:28 2012
Return-Path: <randy@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 B2ADC21F8EBC for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 23:33:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.424
X-Spam-Level: 
X-Spam-Status: No, score=-102.424 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTDfEfeTzlFs for <ietf@ietfa.amsl.com>; Sat,  1 Dec 2012 23:33:28 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1DB21F8EB3 for <ietf@ietf.org>; Sat,  1 Dec 2012 23:33:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354432643; x=1385968643; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=RPwcMebHfv2oB1QJoJ6Dbikji3z+QuKIby9SYaWzGdw=; b=ROEYl7VWD5FcRA73JRBHmHjtqD4nDanrS3OVcLBv19af6xdPGyEzK1UN PtIJ9v3bFjNAlysj+aRVhpALOIyCjFRWKwadsIe+dLl1YIaqQ111B3ZCl sR+zq87l3lDNkuHaCn2Go0wowe0aXD2iDmu6YlAJWBu/IPBrGqtJZEjVe I=;
X-IronPort-AV: E=McAfee;i="5400,1158,6913"; a="10070779"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 01 Dec 2012 23:17:22 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6913"; a="2877551"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 Dec 2012 23:33:27 -0800
Received: from dhcp184-48-45-14.hroa.orl.wayport.net (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sat, 1 Dec 2012 23:33:26 -0800
Message-ID: <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net>
In-Reply-To: <m2obidvuv7.wl%randy@psg.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com>
X-Mailer: Eudora for Mac OS X
Date: Sat, 1 Dec 2012 23:32:11 -0800
To: Randy Bush <randy@psg.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
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: Sun, 02 Dec 2012 07:33:28 -0000

At 3:19 PM +0900 12/2/12, Randy Bush wrote:

>    o if someone wants to float a new idea worth describing, then give
>      them five or ten minutes on the agenda to ask others for input,
>      no preso/ppt.

Seeing something visual can help people grasp what someone is saying.

>  Power corrupts; Powerpoint corrupts absolutely.  -- Vint Cerf

I love that quote of Vint's; it's been in my random sig tag file for *years*

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
A "gaffe" occurs not when a politician lies, but when he tells
the truth.
      -- Michael Kinsley

From moore@network-heretics.com  Sun Dec  2 00:07:44 2012
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 2E13821F8BC4 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 00:07:44 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eaoyE+z-ylkM for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 00:07:43 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 7333E21F8BBE for <ietf@ietf.org>; Sun,  2 Dec 2012 00:07:38 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E78E620B27 for <ietf@ietf.org>; Sun,  2 Dec 2012 03:07:32 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 02 Dec 2012 03:07:32 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=2iM51FZIz3XCi/Zw7br1o1 +C3s8=; b=t0iwe3C8vxb23b/DGqudtSPO7U0MOmoH4xnNE9c4Qhjf6a7CioYC1g jVKQpJCXb9mYb4NrToWojjX6sXZgUQv4JYBG0kiCbbnbfp28A77fMFvYfmh2uqEw TXqZkqAef206xQfHpFXCIvE675cpny3ABLus4ghBOPDJsi5dJQ+80=
X-Sasl-enc: /M0gp6NRB6ofC7xryS3SLlt1+GBDbBCosLvbtaXgzJQX 1354435652
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 4FF3648249F; Sun,  2 Dec 2012 03:07:32 -0500 (EST)
Message-ID: <50BB0C3F.9000008@network-heretics.com>
Date: Sun, 02 Dec 2012 03:07:27 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <50BAF558.5040805@gmail.com>
In-Reply-To: <50BAF558.5040805@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: Sun, 02 Dec 2012 08:07:44 -0000

On 12/02/2012 01:29 AM, Melinda Shore wrote:
> On 12/1/12 9:19 PM, Randy Bush wrote:
>> sadly, too many of us remember writing on scrolls of acetate.  i
>> imagine that some remember stone and chisels.
> At the last meeting, for my own stuff I went with the old one-slide
> approach.  However, it did occur to me that by doing that the slide(s)
> lost its archival value (slim as that may have been) for people not
> in the room.  Anyway.
>
> Not really sure what can be done about this - you can say "discussion,
> not presentation" until you're blue in the face and the outcome of all
> that will be a blue face but presentations during the meetings anyway.
> Ultimately I expect it comes down to how individual chairs want to
> run meetings.

I think that organizations sometimes get into habits of doing things 
regardless of whether those things work well.  And the habits sometimes 
become so entrenched that it's considered heresy to suggest that they be 
changed.   Even individual chairs might have a difficult time changing 
those habits for their own working groups.

Keith


From brian.e.carpenter@gmail.com  Sun Dec  2 00:27:51 2012
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 9AAC521F8FAF for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 00:27:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZSOllD3cQaOx for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 00:27:51 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id EE10021F8FAC for <ietf@ietf.org>; Sun,  2 Dec 2012 00:27:50 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so716866wey.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 00:27:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hnkCAFdqm/IwRSYrSwa14G4bzhom0D6KUH68uuTMZwo=; b=ZjceDH5d72C3VCf5gkLEeDmH+VjZ/S1iB5ZHevQm1SNPGsCOq3iEe/yvMw4b21qQ76 B5bySqwssmSVx6AuBlJhBkZLBrGXoYminvbYk/+wyj12dPNitHSiOQytCR/PSPvGBDI9 VfL3RDJAoCBkvvzWmMNEKVPqKE/a+6UWkl+anXXDNh+ZUDRT220RU6kyR30PaFZUl6oh nw2Kr7kWJ56Vu+8t1C7UnzFTepIUPEAUKRzqUbcT+Gb1hiOtHKb/h7Q961/dsR0RE/Za xdkmWsTD/JhRMdo+y7fjvrCPTCeJxvwzagnBz7JMnQcDAy1dA9O8HnBriy7CZ/4WIx/A IDjg==
Received: by 10.180.81.170 with SMTP id b10mr4560960wiy.16.1354436870067; Sun, 02 Dec 2012 00:27:50 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-29.as13285.net. [2.102.218.29]) by mx.google.com with ESMTPS id dw4sm6850379wib.1.2012.12.02.00.27.48 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 00:27:49 -0800 (PST)
Message-ID: <50BB10FF.6090105@gmail.com>
Date: Sun, 02 Dec 2012 08:27:43 +0000
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: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>	<CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>	<00c001cdce7a$d9fa6490$8def2db0$@asgard.org>	<50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com>	<p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>	<m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net>
In-Reply-To: <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net>
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: Sun, 02 Dec 2012 08:27:51 -0000

On 02/12/2012 07:32, Randall Gellens wrote:
> At 3:19 PM +0900 12/2/12, Randy Bush wrote:
> 
>>    o if someone wants to float a new idea worth describing, then give
>>      them five or ten minutes on the agenda to ask others for input,
>>      no preso/ppt.
> 
> Seeing something visual can help people grasp what someone is saying.

Yes. It escapes me why we would hamper ourselves by *not* using diagrams
to explain complicated new ideas. The first time. Not the second and
subsequent times; that's why we have proceedings.

It also escapes me why we would hamper ourselves by not projecting lists
of open issues. True, almost everyone has a little screen on their knee.
Mine is usually full of jabber sessions for clashing WG meetings, the
text currently under discussion, etc. I prefer to see the current
discussion item on the big screen.

We should also remember that in our community with very diverse ways
of pronouncing the English language, the words on the big screen are
sometimes better understood than the words spoken.

I do agree that the ability to write new stuff on the screen in real
time was a significant advantage of the old acetate sheet. That is
clumsy to do with PPT.

    Brian


From brian.e.carpenter@gmail.com  Sun Dec  2 00:41:37 2012
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 7337121F859E for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 00:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gfCXVm2UTv6H for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 00:41:37 -0800 (PST)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id C0F0721F8599 for <ietf@ietf.org>; Sun,  2 Dec 2012 00:41:36 -0800 (PST)
Received: by mail-wi0-f170.google.com with SMTP id hq7so518362wib.1 for <ietf@ietf.org>; Sun, 02 Dec 2012 00:41:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jxWS2rmKFOPa/32wDZBWTDPV6vdipV8kEjzBIh61aWg=; b=q8Bv9zq4Oijg0k3auCC7OXFb+xOq/3kKGxfkmKhxvPeYPluyPLr8NP75bQnUrvOWIC ERn0RNQFBxkBVTjVzOGmoTkdyTYN9xeeegFlDPdpUpSztTZ/bt26sRfPeyVyUqb3T7t1 tIVtNWzKdJNPJeBnrXmwQ4SONo6cgT66VL/yrdQyUoHb5kdQSdQwPiqdTg1QU7KZRZfD /fdRWBo2vzn+2GX40ogGjUft3xHnY3ra//gWyEevCPUlNzE4cSQ9vUPqHtu57biBuTsw sdpfKAxYXgMc/Mura6Z2lNUZS3qQFq7gOxwiCmTCnKL3ck9Q44JczMvBiXoTvRqcjrLL 6TuQ==
Received: by 10.216.226.75 with SMTP id a53mr2063814weq.41.1354437695643; Sun, 02 Dec 2012 00:41:35 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-29.as13285.net. [2.102.218.29]) by mx.google.com with ESMTPS id eu8sm5991035wib.1.2012.12.02.00.41.33 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 00:41:34 -0800 (PST)
Message-ID: <50BB1427.1070007@gmail.com>
Date: Sun, 02 Dec 2012 08:41:11 +0000
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: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
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: Sun, 02 Dec 2012 08:41:37 -0000

Another condition for a fast track must be the absence of
unresolved IPR disclosures. I can see a big risk here - that
someone will use the fast track procedure to game the IPR
disclosure rule. First, release your open source code, using
an open source licence that doesn't assert the absence of IPR.
Then, post the 00 draft and persuade an AD to fast track it.
(The draft assumes there is a WG involved, but the IETF process
does not require a WG.) Then, "discover" the IPR and disclose it.
All within 3 weeks.

   Brian

On 01/12/2012 20:12, Stephen Farrell wrote:
...
> [1] http://tools.ietf.org/id/draft-farrell-ft


From sm@resistor.net  Sun Dec  2 01:16:12 2012
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 D2A2921F887D for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 01:16:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.662
X-Spam-Level: 
X-Spam-Status: No, score=-102.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xb0B8WOqG9lA for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 01:16:11 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA6FA21F887C for <ietf@ietf.org>; Sun,  2 Dec 2012 01:16:05 -0800 (PST)
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 qB29Fwev010346; Sun, 2 Dec 2012 01:16:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354439762; bh=tceaFw06aaVvcbBRe1JZH16Rb4K2qG4Uxw9N3RRJLLY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lcY5rPy+N8eihGwBequwgtt0xSO7zHRF6Ea/BOMKth0Ezs37HKg44ltGlTBB9WGQg XKigHKFBjmYlqNpYaRH2HLzN00a/rHgmLm+3xbGsciehCn06Ss31P8r5YzNhdrdsWk pVx7TwSXy81z0Ds5QeRkkDukaow1I0RF7R0gAM0Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354439762; i=@resistor.net; bh=tceaFw06aaVvcbBRe1JZH16Rb4K2qG4Uxw9N3RRJLLY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HqG4ati9Z0QMLlFk7cK3oAq3xERZ9lybcxt7NoCPMOGHtmz8eAuSqGhEuH2dYBcKh mwqFycU4mgm6DGa1y4W+o5KQmzlrAML9a/aLcENQ28HpP7tA/gHBLhWp5RDP/UN7Y9 zTR5lvf4ZcteF0pqk3Ljky5ejEbS8POuXsSKQwTg=
Message-Id: <6.2.5.6.2.20121201232958.08f5e9c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 02 Dec 2012 01:01:22 -0800
To: Melinda Shore <melinda.shore@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
In-Reply-To: <50BAF558.5040805@gmail.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <50BAF558.5040805@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: Sun, 02 Dec 2012 09:16:12 -0000

Hi Melinda,
At 22:29 01-12-2012, Melinda Shore wrote:
>Not really sure what can be done about this - you can say "discussion,
>not presentation" until you're blue in the face and the outcome of all
>that will be a blue face but presentations during the meetings anyway.
>Ultimately I expect it comes down to how individual chairs want to
>run meetings.

Yes.

Powerpoint is intended 'for interpretation by a program that 
understands the data on the recipient's system.  Recipients need to 
understand that they are at the "mercy" of the sender, when receiving 
this type of data, since data will be executed on their system, and 
the security of their machines can be violated' [1].

These powerpoint presentations are good enough to keep people 
entertained for the duration of the session.  They mask the fact that 
there hasn't been any discussion of the issues on a mailing 
list.  Pete Resnick mentioned that "doing document reviews in 
presentation form where the editor is the one doing the slides has 
created this problem" [2].  This comes down to "we have seen others 
doing it and that's why we do it".

Regards,
-sm

1. http://www.ietf.org/assignments/media-types/application/vnd.ms-powerpoint
2. http://www.ietf.org/mail-archive/web/ietf/current/msg76080.html 


From moore@network-heretics.com  Sun Dec  2 05:41:12 2012
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 31EB021F8678 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 05:41:12 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C+OqGjwlKf2r for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 05:41:08 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id D303121F85E3 for <ietf@ietf.org>; Sun,  2 Dec 2012 05:41:07 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id F0A99207ED; Sun,  2 Dec 2012 08:41:04 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 02 Dec 2012 08:41:07 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=4n89xQU2U9LVWkEQvJeWKK fqG58=; b=IHGE2UucHrsUfe97cQmrtR7kpPtX4S1ww6Te/PASZLV6jMDZZARH3s TeZpEr2kOzarVOHhfrM5lKhEeMmZssogUdqXOvKbTU1P9koU/Io740zj9mT7mWvr mHp7VZ0NiWaUV0KaDBvTKZt94mxaL4W7Rap4D+WUW2PghxPApnk6w=
X-Sasl-enc: IYWGO4Jrj0E9iV2SsHQOewY6slbgAudzZWCBINP8ggsS 1354455664
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AFEB24827D6; Sun,  2 Dec 2012 08:41:03 -0500 (EST)
Message-ID: <50BB5A69.40107@network-heretics.com>
Date: Sun, 02 Dec 2012 08:40:57 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>	<CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>	<00c001cdce7a$d9fa6490$8def2db0$@asgard.org>	<50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com>	<p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>	<m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com>
In-Reply-To: <50BB10FF.6090105@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Randall Gellens <randy@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: Sun, 02 Dec 2012 13:41:12 -0000

On 12/02/2012 03:27 AM, Brian E Carpenter wrote:
> Yes. It escapes me why we would hamper ourselves by *not* using diagrams
> to explain complicated new ideas. The first time. Not the second and
> subsequent times; that's why we have proceedings.
>
> It also escapes me why we would hamper ourselves by not projecting lists
> of open issues. True, almost everyone has a little screen on their knee.
> Mine is usually full of jabber sessions for clashing WG meetings, the
> text currently under discussion, etc. I prefer to see the current
> discussion item on the big screen.
>
> We should also remember that in our community with very diverse ways
> of pronouncing the English language, the words on the big screen are
> sometimes better understood than the words spoken.
>
> I do agree that the ability to write new stuff on the screen in real
> time was a significant advantage of the old acetate sheet. That is
> clumsy to do with PPT.
>
>

I have no objection to using PPT to display diagrams or lists of open 
issues.  And I understand that PPT can be of aid to those (including me) 
who have trouble with understanding the diverse ways that English is 
spoken.

But I still maintain that there's something about PPT and similar tools 
that tend to degrade interaction rather than facilitate it, and that 
this is tremendously damaging to the way IETF working groups conduct 
their face-to-face sessions.

For example, PPT is much better at conveying short, bulleted lists than 
diagrams.   It's tedious to draw diagrams with PPT, and I suspect, with 
most similar tools.  Most computers still have keyboards which are good 
for inputing text, but most computers don't have an input stylus for 
drawing.  And it's much more time consuming to draw adequate drawings 
with a mouse or trackpad than to draw them on acetate with a pen.

For another, PPT's ability to rearrange slides actually makes it really 
good for working out the order of things to be presented. There's 
nothing at all wrong with using PPT in that way, as long as the slides 
aren't actually projected on the screen, and the speaker doesn't feel 
compelled to follow them closely.   (The PPT files could still be made 
available for download, even in advance, thus inviting participants to 
prepare their own questions and counterpoints in advance.)

Also, there's something about PPT that seems to encourage speakers to 
attempt to capture everything that's possibly relevant to a topic, and 
thus, to fill up all available time, leaving none for discussion.

Maybe this is why the best way that I've ever discovered to use PPT is 
to help me collect my thoughts and organize them into a logical sequence 
for presentation; then to identify the points which are best conveyed by 
drawing and to incorporate those drawings into the presentation; then to 
"hide" all or almost all of the text-only slides.

If we want to work effectively, we must not let our work habits be 
dictated by newer technology, especially when older and simpler 
technology works better.   If slide projectors, sheets of acetate, and 
appropriate pens are no longer readily available, perhaps we need to 
ship large dry-erase boards and markers for those to every meeting.

Keith

p.s. I certainly acknowledge the difficulty in understanding different 
dialects of English.  But it strikes me that part of the problem is the 
high level of ambient noise in the presentation environment, resulting 
in large part from having large numbers of people in the room who aren't 
paying (much) attention and who are each generating small amounts of 
noise, say by typing on laptops, or chatting quietly with those sitting 
near them.   This is just one way that people who are just "camping out" 
in a room distract from what is going on.


From stephen.farrell@cs.tcd.ie  Sun Dec  2 06:34:03 2012
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 4C88621F8414 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:34:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.459
X-Spam-Level: 
X-Spam-Status: No, score=-102.459 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R9SArV6yR9Xl for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:34:03 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id CFC4A21F8417 for <ietf@ietf.org>; Sun,  2 Dec 2012 06:34:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 2399ABE36; Sun,  2 Dec 2012 14:33:41 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DcIQZ3gQe0sS; Sun,  2 Dec 2012 14:33:40 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.31.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8DF3ABE35; Sun,  2 Dec 2012 14:33:40 +0000 (GMT)
Message-ID: <50BB66C4.70000@cs.tcd.ie>
Date: Sun, 02 Dec 2012 14:33:40 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <6.2.5.6.2.20121201123752.09384ef8@resistor.net>
In-Reply-To: <6.2.5.6.2.20121201123752.09384ef8@resistor.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Dec 2012 14:34:03 -0000

Hiya,

On 12/01/2012 09:06 PM, SM wrote:
> 
> Could you ask an AD to sponsor this draft and generate the Last Call?

Bit early yet. I'd like to know what folks think and hopefully
improve the thing via others' good ideas.

> 
> Regards,
> -sm
> 
> P.S. Make the draft experimental.  Add a one-year timer.

Done.
Ta,
S.


From stephen.farrell@cs.tcd.ie  Sun Dec  2 06:37:44 2012
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 B1C4821F8431 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.483
X-Spam-Level: 
X-Spam-Status: No, score=-102.483 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id adY2sWFHBRsb for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:37:40 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9379D21F8231 for <ietf@ietf.org>; Sun,  2 Dec 2012 06:37:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id DCA08BE38; Sun,  2 Dec 2012 14:37:18 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djLOo4B63QXL; Sun,  2 Dec 2012 14:37:14 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.31.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7EDA3BE36; Sun,  2 Dec 2012 14:37:14 +0000 (GMT)
Message-ID: <50BB679A.5070406@cs.tcd.ie>
Date: Sun, 02 Dec 2012 14:37:14 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BAA518.1030208@isdg.net>
In-Reply-To: <50BAA518.1030208@isdg.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Sun, 02 Dec 2012 14:37:44 -0000

Hi Hector,

On 12/02/2012 12:47 AM, Hector Santos wrote:
> This proposal sounds interesting but couldn't it run into conflicts when
> there are competition in running code?   Who's running code do you fast
> track?  How does it apply in the protocol updates area, i.e. BIS work?

Good point. I clarified that its just drafts heading to PS and
-bis drafts are just fine. (Might actually be well-suited for those,
and I'd not thought about that.)

> This proposal and thread, similar to the recent others, all seem to be
> looking for endorsing methods for lack of a better term, "rubber
> stamping" and fast tracking work items, in particular when there are WG
> related barriers holding back the WG work item(s) production progress.

Well, I'm after something where fast-track != rubber-stamp, but I
do agree that that's a hard balance to achieve. I'm not claiming that
this draft does achieve that balance, but such a balance is a goal.

Cheers,
S.

> 
> I personally do not have an issue with expediting work when the proper
> protocol engineering is done and the adequate engineering reviews are
> done, in fact, I depend on the IETF/IESG engineering do this work.  I
> depend on the long time wisdom and engineering judgment of the IETF
> leaders and reviewers to watch over sensitive engineering issues,
> including conflict of interest related matters.
> 
> In the end, we are talking about trusting the process.  If IETF
> participants, especially those who don't attend meetings and long
> participated remotely or via mailing list, lose faith in the WG process,
> these process change proposals may expedite IETF work, but they may also
> handicap the potential of a proposed standard, change and industry
> following.
> 
> -- 
> HLS
> 
> Stephen Farrell wrote:
>> Hi all,
>>
>> I've just posted an idea [1] for a small process improvement.
>> If it doesn't seem crazy I'll try pursue it with the IESG as
>> an RFC 3933 process experiment. If its universally hated then
>> that's fine, it can die.
>>
>> The IESG have seen (more-or-less) this already but it hasn't
>> be discussed, so this is just a proposal from me and has no
>> "official" status whatsoever.
>>
>> Any comments, suggestions or better ideas are very welcome.
>> Feel free to send me comments off list for now, or on this
>> list I guess. If there's loads of email (always possible,
>> this being a process thing;-) we can move to some other list.
>>
>> Regards,
>> Stephen.
>>
>> [1] http://tools.ietf.org/id/draft-farrell-ft
>>
>>
> 

From stephen.farrell@cs.tcd.ie  Sun Dec  2 06:42:27 2012
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 BBD8521F8B8A for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:42:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0-ZfESg1YxAp for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:42:23 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1968021F8697 for <ietf@ietf.org>; Sun,  2 Dec 2012 06:42:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 27802BE36; Sun,  2 Dec 2012 14:42:00 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izxhkF2CL79J; Sun,  2 Dec 2012 14:41:55 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.31.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C4767BE35; Sun,  2 Dec 2012 14:41:55 +0000 (GMT)
Message-ID: <50BB68B3.8040408@cs.tcd.ie>
Date: Sun, 02 Dec 2012 14:41:55 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BB1427.1070007@gmail.com>
In-Reply-To: <50BB1427.1070007@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Sun, 02 Dec 2012 14:42:27 -0000

Hi Brian,

On 12/02/2012 08:41 AM, Brian E Carpenter wrote:
> Another condition for a fast track must be the absence of
> unresolved IPR disclosures. I can see a big risk here - that
> someone will use the fast track procedure to game the IPR
> disclosure rule. First, release your open source code, using
> an open source licence that doesn't assert the absence of IPR.
> Then, post the 00 draft and persuade an AD to fast track it.
> (The draft assumes there is a WG involved, but the IETF process
> does not require a WG.) Then, "discover" the IPR and disclose it.
> All within 3 weeks.

Ah good point. This is only intended for WG documents, but the
late-IPR point is a good one nonetheless. I've added a sentence
saying any late-IPR declaration sends the draft back to the WG.
That's a potential DoS of course, but not a new one really.

Ta,
S.

> 
>    Brian
> 
> On 01/12/2012 20:12, Stephen Farrell wrote:
> ...
>> [1] http://tools.ietf.org/id/draft-farrell-ft
> 
> 

From john-ietf@jck.com  Sun Dec  2 06:45:14 2012
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 0E54421F83EF for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:45:14 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFuZKvagWTPY for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:45:13 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6232521F8484 for <ietf@ietf.org>; Sun,  2 Dec 2012 06:45:13 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TfAn5-000NiU-US; Sun, 02 Dec 2012 09:45:07 -0500
Date: Sun, 02 Dec 2012 09:45:04 -0500
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
Message-ID: <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com>
In-Reply-To: <50BB5A69.40107@network-heretics.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.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: Randall Gellens <randy@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: Sun, 02 Dec 2012 14:45:14 -0000

--On Sunday, December 02, 2012 08:40 -0500 Keith Moore
<moore@network-heretics.com> wrote:

> I have no objection to using PPT to display diagrams or lists
> of open issues.  And I understand that PPT can be of aid to
> those (including me) who have trouble with understanding the
> diverse ways that English is spoken.
> 
> But I still maintain that there's something about PPT and
> similar tools that tend to degrade interaction rather than
> facilitate it, and that this is tremendously damaging to the
> way IETF working groups conduct their face-to-face sessions.

Part of that, as both Randy's indirectly pointed out, is that we
lost something going from overhead projector transparencies to
PowerPoint (or PDF decks, etc.).  The former could be used to
facilitate a discussion by combining the best features of
previously-prepared outlines, diagrams, agendas, etc., with with
ability to for a speaker or chair mark up slides, or make new
ones, in real time.  By contrast, PowerPoint and those
projectors mostly permit only the "go forward" and "go back"
buttons.

> For example, PPT is much better at conveying short, bulleted
> lists than diagrams.   It's tedious to draw diagrams with PPT,
> and I suspect, with most similar tools.  Most computers still
> have keyboards which are good for inputing text, but most
> computers don't have an input stylus for drawing.  And it's
> much more time consuming to draw adequate drawings with a
> mouse or trackpad than to draw them on acetate with a pen.

Yes.  But I am less concerned about how long it takes to prepare
a presentation than I am about what goes on during the meeting
discussion.  If the diagrams are going into a PowerPoint
package, there is always the "draw with pencil, scan, and insert
into deck" possibility.

>...
> Also, there's something about PPT that seems to encourage
> speakers to attempt to capture everything that's possibly
> relevant to a topic, and thus, to fill up all available time,
> leaving none for discussion.

I think the same could be said for any outline that is prepared
before a meeting and made available to the audience.  Speakers
have to understand what they are (or should be) trying to do,
why the purpose of their presentations is (almost always) to
frame and stimulate discussion and not just to show the
speaker's mastery of the subject matter (and WG Chairs and
others need to reinforce that understanding).

>...
> If we want to work effectively, we must not let our work
> habits be dictated by newer technology, especially when older
> and simpler technology works better.   If slide projectors,
> sheets of acetate, and appropriate pens are no longer readily
> available, perhaps we need to ship large dry-erase boards and
> markers for those to every meeting.

They are still available.  Having dragged my own flip chart
easel (in a bag and checked as baggage) to a few meetings in
ancient times, I imagine all surviving ones of of those aren't
in museums either.  But rigs for cameras that are set up to be
pointed down onto sheets of paper on which drawings and notes
are being made are a lot more compact, compatible with the
projectors we are using already, and, like overhead
transparencies and PowerPoint-like decks, leave traces that can
easily be incorporated into minutes -- something that is less
feasible with any whiteboard technology we'd be likely to be
able to drag around.

best,
   john


From stephen.farrell@cs.tcd.ie  Sun Dec  2 06:48:47 2012
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 1B92121F87B1 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMcZavuziQjb for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:48:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0F80D21F86E4 for <ietf@ietf.org>; Sun,  2 Dec 2012 06:48:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C1251BE38; Sun,  2 Dec 2012 14:48:20 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 695SzV+CNl8i; Sun,  2 Dec 2012 14:48:20 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.31.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 250CBBE36; Sun,  2 Dec 2012 14:48:20 +0000 (GMT)
Message-ID: <50BB6A33.3000205@cs.tcd.ie>
Date: Sun, 02 Dec 2012 14:48:19 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <CAC4RtVD0x3JsPR8qJ1BbVytU-yL96z-Sbr5hW9GetnEX-U3FQQ@mail.gmail.com> <50BA8D01.1050508@cs.tcd.ie> <CALaySJ+zoTJB_A9-ihZomYUggZ=_sYnNC0i651E4hszePi08Yw@mail.gmail.com>
In-Reply-To: <CALaySJ+zoTJB_A9-ihZomYUggZ=_sYnNC0i651E4hszePi08Yw@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Sun, 02 Dec 2012 14:48:47 -0000

Hiya,

On 12/02/2012 12:21 AM, Barry Leiba wrote:
>> > I, and I believe lots of us, do want to encourage running code
>> > more than now. This is one attempt to help with that. Why not
>> > try it and see?

> Because as a "reward" for claiming to have running code, I think it's
> a terrible idea.  As a way of handling the process for documents where
> it makes sense to, I think it's fine.  

I don't get that distinction to be honest. Maybe we interpret the
word reward differently here. I'm using it with only positive
connotations but the scare quotes above seem to imply you're not.

> If you want the criteria for
> your WGs to be "You have to have running code," knock yourself out.
> Any other ADs who want to do it that way can join you.  If you want to
> codify that for everyone, 

I do. I want this to be something where WG chairs can take the
initiative (not ADs) and where IETF participants can hassle their
WG chairs to use this. So I don't want it to be an AD-driven
thing really.

> I think you need to do a lot more in the
> line of criteria for adequate implementations, and so on.  

Fair enough. Be interested in more on that.

> If I spend
> half a day knocking out some crappy untested code, is that good
> enough?  If not, how much testing does it need?  I'm pretty sure we
> don't want to go there.

Perhaps. As of now, I'm just saying that the WG chairs (all of 'em)
and the responsible AD need to accept that the code is ok for the
purpose. I think I can argue that that's enough, but would welcome
better ideas there or ideas about things they should take into
account that'd be worth including here.

Cheers,
S.


From moore@network-heretics.com  Sun Dec  2 06:53:35 2012
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 496C921F850C for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:53:35 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAh+ZuY5GS6c for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 06:53:31 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id C3BBF21F84EE for <ietf@ietf.org>; Sun,  2 Dec 2012 06:53:30 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6DCAD205FA; Sun,  2 Dec 2012 09:53:30 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 02 Dec 2012 09:53:30 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type; s=smtpout; bh=5uHG UF23B8mD1b4PzVWD5KxLcXQ=; b=CSwk6lI63RxnexHsA/hvO+axFkqMLiliS/tU 8dwUI3C0JWjFuP4OSHduQ00h9Hl/fNSL4lxVU4nZKVo8sfdLdgXYCxLU6rb1jKX3 q/dYeMmkCJVUii+qFakrKcBHSshed97nQ7Xrdu+Mx93cNpF0YLrJKaQYTMXNF7S5 n273gRo=
X-Sasl-enc: Z2L/NTARwwt+CNdEiUgE21OqJ8FUmGoWA6Rw3d0g4srY 1354460009
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 21E4448249F; Sun,  2 Dec 2012 09:53:29 -0500 (EST)
Message-ID: <50BB6B61.4040304@network-heretics.com>
Date: Sun, 02 Dec 2012 09:53:21 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com>
In-Reply-To: <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com>
Content-Type: multipart/alternative; boundary="------------010604030601030600080506"
Cc: Randall Gellens <randy@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: Sun, 02 Dec 2012 14:53:35 -0000

This is a multi-part message in MIME format.
--------------010604030601030600080506
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12/02/2012 09:45 AM, John C Klensin wrote:
> But rigs for cameras that are set up to be
> pointed down onto sheets of paper on which drawings and notes
> are being made are a lot more compact, compatible with the
> projectors we are using already, and, like overhead
> transparencies and PowerPoint-like decks, leave traces that can
> easily be incorporated into minutes -- something that is less
> feasible with any whiteboard technology we'd be likely to be
> able to drag around.
I'd love to see us adopt such technology and strongly encourage its use, 
while at the same time actively discouraging the use of these meeting 
slots for /presentations/ and instead treating them as /discussions/.

(Another way to put is that even if we provide such cameras in meetings 
along with colored pens and paper, we will continue to see PowerPoint 
being used as it is today unless there's a community-wide effort to 
change our entrenched habits.)

Keith


--------------010604030601030600080506
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 12/02/2012 09:45 AM, John C Klensin
      wrote:<br>
    </div>
    <blockquote cite="mid:17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com"
      type="cite">
      <pre wrap="">But rigs for cameras that are set up to be
pointed down onto sheets of paper on which drawings and notes
are being made are a lot more compact, compatible with the
projectors we are using already, and, like overhead
transparencies and PowerPoint-like decks, leave traces that can
easily be incorporated into minutes -- something that is less
feasible with any whiteboard technology we'd be likely to be
able to drag around.
</pre>
    </blockquote>
    I'd love to see us adopt such technology and strongly encourage its
    use, while at the same time actively discouraging the use of these
    meeting slots for <i>presentations</i> and instead treating them as
    <i>discussions</i>. <br>
    <br>
    (Another way to put is that even if we provide such cameras in
    meetings along with colored pens and paper, we will continue to see
    PowerPoint being used as it is today unless there's a community-wide
    effort to change our entrenched habits.)<br>
    <br>
    Keith<br>
    <br>
  </body>
</html>

--------------010604030601030600080506--

From stephen.farrell@cs.tcd.ie  Sun Dec  2 07:00:59 2012
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 AD2B921F8477 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 07:00:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsCuvJ--DtTP for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 07:00:59 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2596421F8457 for <ietf@ietf.org>; Sun,  2 Dec 2012 07:00:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 590D7BE38; Sun,  2 Dec 2012 15:00:37 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DWmnaZPkpyP; Sun,  2 Dec 2012 15:00:36 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.31.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id ABC6BBE36; Sun,  2 Dec 2012 15:00:36 +0000 (GMT)
Message-ID: <50BB6D0F.9010007@cs.tcd.ie>
Date: Sun, 02 Dec 2012 15:00:31 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BA6A45.2000409@dcrocker.net> <50BA6FF4.4030706@gmail.com> <50BA8106.6050503@dcrocker.net> <50BA8B03.7070002@cs.tcd.ie> <50BA8F36.9070501@dcrocker.net> <50BA90ED.9000202@cs.tcd.ie> <50BA981B.9060505@gmail.com>
In-Reply-To: <50BA981B.9060505@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Dec 2012 15:00:59 -0000

On 12/01/2012 11:51 PM, Melinda Shore wrote:
> On 12/1/12 2:21 PM, Stephen Farrell wrote:
>> My reluctance to get into this is based on an opinion that process
>> change proposals with more words attached tend to just not happen,
>> so fewer words is better.
> 
> I think that's actually a pretty terrible reason.  

Well, I think its an ok reason for not fully answering Dave's
question in this case, given the latitude offered by RFC 3933.
Tactical reticence like this would not be a reason to adopt
anything, I agree.

> The goal is
> not to get the proposal through, the goal is to improve
> something.  That said, while I don't like change just for the
> sake of change I think that change for the sake of betterment is
> a very good thing indeed.  The main thing is that I've been trying
> to figure out where the harm would be here and I haven't been
> able to identify anything substantive.  I'd be good with giving
> this a limited run and seeing how it goes.

Great.
S.

> 
> Melinda
> 
> 

From john-ietf@jck.com  Sun Dec  2 07:03:44 2012
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 E0AF321F8477 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 07:03:44 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LHYsu307w3zO for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 07:03:44 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DBBA021F8529 for <ietf@ietf.org>; Sun,  2 Dec 2012 07:03:31 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TfB4r-000Nkg-8S; Sun, 02 Dec 2012 10:03:29 -0500
Date: Sun, 02 Dec 2012 10:03:25 -0500
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
Message-ID: <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com>
In-Reply-To: <50BB6B61.4040304@network-heretics.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.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: Randall Gellens <randy@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: Sun, 02 Dec 2012 15:03:45 -0000

--On Sunday, December 02, 2012 09:53 -0500 Keith Moore
<moore@network-heretics.com> wrote:

>...
> (Another way to put is that even if we provide such cameras in
> meetings along with colored pens and paper, we will continue
> to see PowerPoint being used as it is today unless there's a
> community-wide effort to change our entrenched habits.)

Sure.  But it is the now-entrenched habits that are the problem.
The overuse of PowerPoint for purposes of which neither of us
approve is merely a symptom, not, IMO, a cause (even if it
reinforces the behaviors).

Anyone for incorporating a slide (!) into the Newcomer's
Presentation (!!) that says "a presentation in a f2f meeting
that makes extensive use of PowerPoint decks with many and/or
dense slides brands the presenter as either a newcomer, someone
who is trying to avoid an actual discussion, or a fool"?   :-(

   john


From moore@network-heretics.com  Sun Dec  2 07:12:23 2012
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 C66CE21F8529 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 07:12:22 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KmnsbNB60rux for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 07:12:16 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2320D21F8439 for <ietf@ietf.org>; Sun,  2 Dec 2012 07:12:16 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 8E5AC20C00; Sun,  2 Dec 2012 10:12:15 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 02 Dec 2012 10:12:15 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=EGJn5WTI0ayjyLkidfHw0D CviPg=; b=kCO1qAyZovlrb4i0H1bY4+jpogHGBBqnB5/gRK4ovnKdtMPOt6uruI PbnMAc8CCja6feJMRQL80yNfdykd8dahK+EcnKgP+PAr5hsDyg3midIPgAk7wxug b48tgDSby4CULHK/KZjMPE+ey3r2ezgxPfW4+unW0xIYOFhu6b8mY=
X-Sasl-enc: n6cWTgI7Pa1dQefBxFrM0+G+nyAQC7IAkkc9rN27vlG7 1354461135
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 79D5B8E0573; Sun,  2 Dec 2012 10:12:14 -0500 (EST)
Message-ID: <50BB6FC8.8040907@network-heretics.com>
Date: Sun, 02 Dec 2012 10:12:08 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com>
In-Reply-To: <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Randall Gellens <randy@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: Sun, 02 Dec 2012 15:12:23 -0000

On 12/02/2012 10:03 AM, John C Klensin wrote:
>
> --On Sunday, December 02, 2012 09:53 -0500 Keith Moore
> <moore@network-heretics.com> wrote:
>
>> ...
>> (Another way to put is that even if we provide such cameras in
>> meetings along with colored pens and paper, we will continue
>> to see PowerPoint being used as it is today unless there's a
>> community-wide effort to change our entrenched habits.)
> Sure.  But it is the now-entrenched habits that are the problem.
> The overuse of PowerPoint for purposes of which neither of us
> approve is merely a symptom, not, IMO, a cause (even if it
> reinforces the behaviors).
Agreed, though sometimes when changing habits it helps to focus 
attention on the most visible or tangible part of the habit.

It's always been possible, and will presumably remain possible, to build 
small PowerPoint decks that consist of only a few diagrams, to leave 
some blank slides in the middle of the deck for the purpose of typing in 
comments made at meetings, etc.  -- all for the purpose of facilitating 
discussion.  I wouldn't have a problem with PowerPoint being used in 
that way, though I suspect that it will be difficult for people to 
restrain themselves to using PowerPoint in that way as long as that's 
the tool that they're using.
>
> Anyone for incorporating a slide (!) into the Newcomer's
> Presentation (!!) that says "a presentation in a f2f meeting
> that makes extensive use of PowerPoint decks with many and/or
> dense slides brands the presenter as either a newcomer, someone
> who is trying to avoid an actual discussion, or a fool"?   :-(
Yes, but first we need to get existing WG chairs to say that to their 
participants, and to push back on people who continue to do use 
PowerPoint in that way in meetings.

Keith


From johnl@iecc.com  Sun Dec  2 08:26:46 2012
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 B326321F86CC for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 08:26:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.641
X-Spam-Level: 
X-Spam-Status: No, score=-105.641 tagged_above=-999 required=5 tests=[AWL=1.258, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jY7mUT47o+mo for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 08:26:46 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 8307621F84B5 for <ietf@ietf.org>; Sun,  2 Dec 2012 08:26:45 -0800 (PST)
Received: (qmail 88152 invoked from network); 2 Dec 2012 16:26:41 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 2 Dec 2012 16:26:41 -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:vbr-info; s=50bb8141.xn--hew.k1211; i=johnl@user.iecc.com; bh=ihGoNnHzzaGxGBtcEh087Zf90Ybb8nAExa2fj3jrB34=; b=nj7xbXP4aPekUKviqc/8CGYJalGIjthoJQcuVOx1EgwKDaVUWMqA2hR9a6SzZ9GURefrHOFzmkzPgnuus46jZJq6N0Ui8UUsZmhHB22kv7bN+kIAIMld4bqOYEgiIK9G3gXWKKojSrSajbyZKrQNP3rnBfQ7N1/feU9VH4iNXBs=
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:vbr-info; s=50bb8141.xn--hew.k1211; olt=johnl@user.iecc.com; bh=ihGoNnHzzaGxGBtcEh087Zf90Ybb8nAExa2fj3jrB34=; b=tBl9f8o4hEXqbHnevhD5Ail7fUstI8/kV0f2aqcCe+mCBT37Julh8FSodYMLeiIitgt/LbYGJvvb9Bc2RCEKfAeeYb4fvS5rnMxCBGOuHLL7KHyeoRXcFABhLLC9SYt5HleIKpqkmNTEAqpO5WnQD0hXwfBYpI/nXaZhAW3XPuU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 2 Dec 2012 16:26:19 -0000
Message-ID: <20121202162619.59866.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
In-Reply-To: <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: 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: Sun, 02 Dec 2012 16:26:46 -0000

>Anyone for incorporating a slide (!) into the Newcomer's
>Presentation (!!) that says "a presentation in a f2f meeting
>that makes extensive use of PowerPoint decks with many and/or
>dense slides brands the presenter as either a newcomer, someone
>who is trying to avoid an actual discussion, or a fool"?   :-(

No, just hand out copies of this:

http://www.edwardtufte.com/tufte/books_pp

-- 
Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. http://jl.ly

From sm@resistor.net  Sun Dec  2 08:37:42 2012
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 3E05F21F85C0 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 08:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.657
X-Spam-Level: 
X-Spam-Status: No, score=-102.657 tagged_above=-999 required=5 tests=[AWL=-0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-XtI36+PZ2u for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 08:37:41 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E85521F852D for <ietf@ietf.org>; Sun,  2 Dec 2012 08:37:41 -0800 (PST)
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 qB2Gba4A024271; Sun, 2 Dec 2012 08:37:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354466261; bh=gdamCHXbWVOkifwhqZwXKXSc27cJe7SG8rEwq7OSYUw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=P2X4RfzQoCdETytU6bjZq+WAeI46Mv3kBpjhIHnkpfny6OVxFZxMwFlpgS3a0m54n 5oeHAyG80jvp5A5dtwyaj9FCXVy7gyHsyidZPpOlej0giPXtNYCylkkFu5cI4X57ix FceVDg4Mgh5T7VS9bytSB2u+0sEieMrOQSGPe85U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354466261; i=@resistor.net; bh=gdamCHXbWVOkifwhqZwXKXSc27cJe7SG8rEwq7OSYUw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qijLvJMGAmnbZqFWp6YWVxPBBV7Icsdc1hlzkOi6ZAF2ThKCCp/dDk1USguwkAizs xVqPbt4wsIZ3fV+FM4ZqzC3qp2/lHbj2suuMG5LTjiOAR59tEMTaCwEH/ac0b63TiC yfiZi8kKXjYQ9qx+9tFwmy4vt/7m5ShugFasToXU=
Message-Id: <6.2.5.6.2.20121202073741.0ac80c68@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 02 Dec 2012 08:35:47 -0800
To: Keith Moore <moore@network-heretics.com>
From: SM <sm@resistor.net>
Subject: English spoken here (was: PowerPoint considered harmful)
In-Reply-To: <50BB5A69.40107@network-heretics.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.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: Sun, 02 Dec 2012 16:37:42 -0000

At 05:40 02-12-2012, Keith Moore wrote:
>p.s. I certainly acknowledge the difficulty in understanding 
>different dialects of English.  But it strikes me that part of the 
>problem is the high level of ambient noise

It is not about different dialects of English.  There are people in 
one part of the world who speak English.  There are people from other 
parts of the world which do not understand that English because of:

  (a) The way English is spoken

  (b) The speed at which English is spoken

  (c) The vocabulary used

The people face a high barrier for active participation at a 
meeting.  The one language that the two groups have in common is 
code.  There is also a barrier for participation on mailing lists as 
the people do not use email in the same way as the (North American) group.

Accommodating the group of people is not enough.  It is up to the 
group of people to say what they would like done to make the IETF 
easier for them.  It is up to the (North American) group to, if you 
excuse me, shut up and take what they say at face value instead of 
trying to prove them wrong.

Stephen Farrell wrote [1] the following:

   "Whatever. Its a reality."

Barry Leiba replied [2] that:

   'No, Stephen, this isn't a "whatever".  You're proposing an experiment
    for changing process.  I'm reminding you that what you're proposing is
    not a change in formal process, but something you can do *right now*,
    today, if you and a WGC want to.  Please don't dismiss that with
    "Whatever."'

Yes, I am using a bad example.  My excuse is that it is to illustrate 
the difference between two groups.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg76116.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg76120.html 


From jmh@joelhalpern.com  Sun Dec  2 09:19:56 2012
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 B517B21F85B4 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VnlR4tZ76u4f for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:19:56 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 247F021F85FF for <ietf@ietf.org>; Sun,  2 Dec 2012 09:19:55 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 081DFA6814 for <ietf@ietf.org>; Sun,  2 Dec 2012 09:19:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 87FA61C0D1A; Sun,  2 Dec 2012 09:19:51 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 7F8071C07B5; Sun,  2 Dec 2012 09:19:48 -0800 (PST)
Message-ID: <50BB8DA8.5070406@joelhalpern.com>
Date: Sun, 02 Dec 2012 12:19:36 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com>
In-Reply-To: <50BB6FC8.8040907@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Randall Gellens <randy@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: Sun, 02 Dec 2012 17:19:57 -0000

There is another unfortunate community habit that I have noticed.
It is, I believe, a consequence o their being simply too much stuff to 
look at.

If you have a working group that is considering new ideas (looking to 
recharter), you are more likely to get folks to read the draft, either 
before or shortly after the meeting, if you get a presentation slot in 
the meeting.  In particular, if the presentation sounds interesting, he 
odds of readership go up.

This is not discussion.  The odds of getting much discussion if the idea 
is competent are pretty low.  (I am putting aside the useful result 
where the participants go to the mike and bash the idea hard.  That at 
least is discussion, even if not the discussion the presenter wanted.) 
But it seems to be one of the few ways we have to get folks to pay 
attention.

Yours,
Joel

On 12/2/2012 10:12 AM, Keith Moore wrote:
> On 12/02/2012 10:03 AM, John C Klensin wrote:
>>
>> --On Sunday, December 02, 2012 09:53 -0500 Keith Moore
>> <moore@network-heretics.com> wrote:
>>
>>> ...
>>> (Another way to put is that even if we provide such cameras in
>>> meetings along with colored pens and paper, we will continue
>>> to see PowerPoint being used as it is today unless there's a
>>> community-wide effort to change our entrenched habits.)
>> Sure.  But it is the now-entrenched habits that are the problem.
>> The overuse of PowerPoint for purposes of which neither of us
>> approve is merely a symptom, not, IMO, a cause (even if it
>> reinforces the behaviors).
> Agreed, though sometimes when changing habits it helps to focus
> attention on the most visible or tangible part of the habit.
>
> It's always been possible, and will presumably remain possible, to build
> small PowerPoint decks that consist of only a few diagrams, to leave
> some blank slides in the middle of the deck for the purpose of typing in
> comments made at meetings, etc.  -- all for the purpose of facilitating
> discussion.  I wouldn't have a problem with PowerPoint being used in
> that way, though I suspect that it will be difficult for people to
> restrain themselves to using PowerPoint in that way as long as that's
> the tool that they're using.
>>
>> Anyone for incorporating a slide (!) into the Newcomer's
>> Presentation (!!) that says "a presentation in a f2f meeting
>> that makes extensive use of PowerPoint decks with many and/or
>> dense slides brands the presenter as either a newcomer, someone
>> who is trying to avoid an actual discussion, or a fool"?   :-(
> Yes, but first we need to get existing WG chairs to say that to their
> participants, and to push back on people who continue to do use
> PowerPoint in that way in meetings.
>
> Keith
>
>

From john-ietf@jck.com  Sun Dec  2 09:21:19 2012
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 A0FA521F881F for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:21:19 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTM9Ykg6c33U for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:21:19 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D675121F878D for <ietf@ietf.org>; Sun,  2 Dec 2012 09:21:18 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TfDE5-000NwA-7k; Sun, 02 Dec 2012 12:21:09 -0500
Date: Sun, 02 Dec 2012 12:21:05 -0500
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>
Subject: Re: English spoken here (was: PowerPoint considered harmful)
Message-ID: <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20121202073741.0ac80c68@resistor.net>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@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: 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: Sun, 02 Dec 2012 17:21:19 -0000

--On Sunday, December 02, 2012 08:35 -0800 SM <sm@resistor.net>
wrote:

> 
> It is not about different dialects of English.  There are
> people in one part of the world who speak English.  There are
> people from other parts of the world which do not understand
> that English because of:
> 
>   (a) The way English is spoken
> 
>   (b) The speed at which English is spoken
> 
>   (c) The vocabulary used

(d) Their reading-English is much better than their spoken
English and they have trouble keeping up even if (b) is quite
moderate.

> The people face a high barrier for active participation at a
> meeting.

But can be considerably aided in many cases by written material
(slides, summaries, or both) well in advance especially if those
material are also used at the meeting, thereby aiding
synchronization.

>...
> Accommodating the group of people is not enough.  It is up to
> the group of people to say what they would like done to make
> the IETF easier for them.  It is up to the (North American)
> group to, if you excuse me, shut up and take what they say at
> face value instead of trying to prove them wrong.

Sigh.  Some of the comments above are derived from exactly the
types of discussions you are trying to encourage.  Other parts
of it derive from trying to understand and participate in
presentations and discussions in languages in which I can sort
of get around but am not real-time fluent (while the issue in
the IETF is the set of languages, dialects, and pronunciations
we call "English", the problem isn't unique).  

Cultural styles also make some of the most affected parties less
likely to speak up for their specific needs on this list than
one might like.  That leaves the rest of us with a choice
between trying to synthesize from other conversations and
experiences and taking the position that, until the people with
the most severe versions of the problem speak up, there is no
problem.  I believe the latter would be unfortunate for many
reasons, not least of which is that better use of meeting time
and presentation aids/ materials would help those of us who are
native speakers as well.

>...

   john


From dhc@dcrocker.net  Sun Dec  2 09:42:28 2012
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 C6D4321F85FA for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:42:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7JLg-SK8cF-Y for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:42:28 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2A83421F85F4 for <ietf@ietf.org>; Sun,  2 Dec 2012 09:42:28 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB2HgRFx020484 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 2 Dec 2012 09:42:27 -0800
Message-ID: <50BB92FB.5040904@dcrocker.net>
Date: Sun, 02 Dec 2012 09:42:19 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>
In-Reply-To: <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 02 Dec 2012 09:42:28 -0800 (PST)
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, 02 Dec 2012 17:42:29 -0000

> But can be considerably aided in many cases by written material
> (slides, summaries, or both) well in advance especially if those
> material are also used at the meeting, thereby aiding
> synchronization.


This is a very specific matter of technique.

As I started doing more presentations outside the US or with mixed 
audiences, I was told that the challenge of slide content is to make it 
neither too terse nor too verbose.  Too terse imparts too little 
information for a reader who is using them to augment listening to the 
English.  Too verbose, of course, takes too much time to read for real-time.

In addition, slides often circulate later and need to have enough text 
to be useful without the speaker's commentary.

So I try to use "telegraphic" text that stands on its own.  That is, 
it's a terse as I can make it, while still making sense without my 
commentary.  (It turns out this also provides the opportunity to have 
the speaking commentary go beyond the slide text, since I can let the 
audience rely on the slides for key points.)

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Sun Dec  2 09:50:21 2012
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 536FB21F86A2 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:50:21 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RfIEhIOT-nIq for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:50:17 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4644821F84D5 for <ietf@ietf.org>; Sun,  2 Dec 2012 09:50:17 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TfDgD-000NyH-Ne; Sun, 02 Dec 2012 12:50:13 -0500
Date: Sun, 02 Dec 2012 12:50:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Keith Moore <moore@network-heretics.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
Message-ID: <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck.com>
In-Reply-To: <50BB8DA8.5070406@joelhalpern.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.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: Randall Gellens <randy@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: Sun, 02 Dec 2012 17:50:21 -0000

--On Sunday, December 02, 2012 12:19 -0500 "Joel M. Halpern"
<jmh@joelhalpern.com> wrote:

> There is another unfortunate community habit that I have
> noticed.
> It is, I believe, a consequence o their being simply too much
> stuff to look at.

Of course, having too much stuff to look at is ultimately a
consequence of the inability of the Steering Group to prioritize
and structure work enough (even if it means saying "no" to
reasonable, but less-important, proposals) that the number of
things people (and they) have to look at bears a reasonable
relationship to available time and resources. 

That really fundamental problem is one that restrictions on
PowerPoint or presentations, or even ideas about how to
fast-track some work, are not going to fix.  In fairness to the
IESG, it is also impossible for them to fix unless the community
is willing to support their saying "no" or "insufficient
resources" to some proposals for WGs or for work within WGs.
But, as long as they simply accept almost all proposals that
"someone wants to work on" and that are not obviously
technically stupid, there is no chance of knowing whether the
community would support pushing back on lower-priority work.

> If you have a working group that is considering new ideas
> (looking to recharter), you are more likely to get folks to
> read the draft, either before or shortly after the meeting, if
> you get a presentation slot in the meeting.  In particular, if
> the presentation sounds interesting, he odds of readership go
> up.
>...

Yes, but see above.

best,
   john


From moore@network-heretics.com  Sun Dec  2 09:51:15 2012
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 6E68921F86FD for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:51:15 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QAW+xN1T5rCc for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:51:14 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 2A05F21F85A7 for <ietf@ietf.org>; Sun,  2 Dec 2012 09:51:14 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AFFA4205E7 for <ietf@ietf.org>; Sun,  2 Dec 2012 12:51:13 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Sun, 02 Dec 2012 12:51:13 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=Tlbtudnco8sr8eQ+RNSh8I 8sKEU=; b=Q/bnxtT7HybXMQAF15qWQ99UrHi9+4Sr1fSlanJRYZB854st0+7aHP Kb8tchu8pS+fYABDZEqB5xqJgc1DSdJnP3kqSsdYSY52CAq2Bl+7Ru1KTdctL/ek reCZkRYu1CIq37mYqZK2hdhhqwKntnKCr49IXc+0yL4OZ2oiuTH/Y=
X-Sasl-enc: gc4BDhmKej8nd1PiJ3zXo2jtWThvhlmIFqVScLfQFMx1 1354470673
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E75238E056A; Sun,  2 Dec 2012 12:51:12 -0500 (EST)
Message-ID: <50BB950A.9000408@network-heretics.com>
Date: Sun, 02 Dec 2012 12:51:06 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net>
In-Reply-To: <50BB92FB.5040904@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: Sun, 02 Dec 2012 17:51:15 -0000

On 12/02/2012 12:42 PM, Dave Crocker wrote:
>> But can be considerably aided in many cases by written material
>> (slides, summaries, or both) well in advance especially if those
>> material are also used at the meeting, thereby aiding
>> synchronization.
>
>
> This is a very specific matter of technique.
>
> As I started doing more presentations outside the US or with mixed 
> audiences, I was told that the challenge of slide content is to make 
> it neither too terse nor too verbose.  Too terse imparts too little 
> information for a reader who is using them to augment listening to the 
> English.  Too verbose, of course, takes too much time to read for 
> real-time.
>
> In addition, slides often circulate later and need to have enough text 
> to be useful without the speaker's commentary.
>
> So I try to use "telegraphic" text that stands on its own.  That is, 
> it's a terse as I can make it, while still making sense without my 
> commentary.  (It turns out this also provides the opportunity to have 
> the speaking commentary go beyond the slide text, since I can let the 
> audience rely on the slides for key points.)

I think you're missing the point.   The core problem is the overuse of 
presentations, and presentation tools, for working group face to face 
meeting time which is better suited for discussion.

For those occasions when presentations are appropriate, or for "slides" 
that are provided as background material in advance of the discussion, 
the above is good advice.

Keith


From dhc@dcrocker.net  Sun Dec  2 09:57:55 2012
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 655ED21F86ED for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:57:55 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id USUwr2B0STyo for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:57:54 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B9E5621F8618 for <ietf@ietf.org>; Sun,  2 Dec 2012 09:57:54 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB2HvsCt020706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Dec 2012 09:57:54 -0800
Message-ID: <50BB9699.6070404@dcrocker.net>
Date: Sun, 02 Dec 2012 09:57:45 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com>
In-Reply-To: <50BB950A.9000408@network-heretics.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.17]); Sun, 02 Dec 2012 09:57:54 -0800 (PST)
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: Sun, 02 Dec 2012 17:57:55 -0000

On 12/2/2012 9:51 AM, Keith Moore wrote:
> I think you're missing the point.   The core problem is the overuse of
> presentations, and presentation tools, for working group face to face
> meeting time which is better suited for discussion.


stop blaming the tool.  focus on the folks doing the speaking.

tools can be used well or poorly.  technique matters, but what matters 
most is whether the speaker is saying useful things in useful ways.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From moore@network-heretics.com  Sun Dec  2 09:58:45 2012
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 B9D2421F86A2 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:58:45 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZrqfrZdJH-i for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 09:58:45 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 105B321F8634 for <ietf@ietf.org>; Sun,  2 Dec 2012 09:58:37 -0800 (PST)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B543F2079D for <ietf@ietf.org>; Sun,  2 Dec 2012 12:58:36 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 02 Dec 2012 12:58:36 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=YLZ9b7fjg84BG7Lro3/qwG Wcea4=; b=du2ZABdsh9GqPnLulnxXOI7n/zRGqbofYNJ1z2zgpIYQP2mHKQlB53 nH+kWAixzPmI2ctSHlx+mHhto83d6IhDsB9PZXXcmnqDBcyBtpCPQgpVvzqi9hHK tncHXfptRCSfrEOtjJaB8l4B1nF55Un+4V8RNoSLTMoezIPpnigPU=
X-Sasl-enc: Zgxp3oprLh8KtZCt/3uJlYwpsrnUnRdFknUp2ydJu4Z0 1354471116
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1392D48249F; Sun,  2 Dec 2012 12:58:35 -0500 (EST)
Message-ID: <50BB96C4.2080908@network-heretics.com>
Date: Sun, 02 Dec 2012 12:58:28 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com>
In-Reply-To: <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck.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: Sun, 02 Dec 2012 17:58:45 -0000

On 12/02/2012 12:50 PM, John C Klensin wrote:
>
> --On Sunday, December 02, 2012 12:19 -0500 "Joel M. Halpern"
> <jmh@joelhalpern.com> wrote:
>
>> There is another unfortunate community habit that I have
>> noticed.
>> It is, I believe, a consequence o their being simply too much
>> stuff to look at.
> Of course, having too much stuff to look at is ultimately a
> consequence of the inability of the Steering Group to prioritize
> and structure work enough (even if it means saying "no" to
> reasonable, but less-important, proposals) that the number of
> things people (and they) have to look at bears a reasonable
> relationship to available time and resources.
I'd add working group chairs (though I'm sure there are a few 
exceptions) to the list of those with an apparent inability to 
prioritize and structure work.   Or perhaps WGs should have to get 
approval from their supervising AD before they can take on new documents.

Keith


From moore@network-heretics.com  Sun Dec  2 10:06:12 2012
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 E32A821F859D for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:06:12 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0smPJKCm8S5 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:06:11 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id DC66C21F84D5 for <ietf@ietf.org>; Sun,  2 Dec 2012 10:06:07 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7E53D20B5D for <ietf@ietf.org>; Sun,  2 Dec 2012 13:06:07 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 02 Dec 2012 13:06:07 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=GsgCR9qEIeGK4N/02M3CsC RlbEk=; b=YZDVO0G81nmU9Jgh7NKyWQQmnUytMbhvdCHgseUxhQgwi7nsEFuo2/ HbkdIIAKBe0hRTWbPJCI3OIOh0Qb6/xs9S4OGUgVUvA6igCWubcB8FRh0gy5+e61 uYb51RD9wn4uTyfZqyw2Mt0vQt1wwmdG7UwG4ou5oY+YauW8HMgeU=
X-Sasl-enc: RkuAb7ePuGvaj0k3+NJwKBU83udC47mabifqzflS9E0a 1354471567
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id D59078E05D2; Sun,  2 Dec 2012 13:06:06 -0500 (EST)
Message-ID: <50BB9888.8080906@network-heretics.com>
Date: Sun, 02 Dec 2012 13:06:00 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net>
In-Reply-To: <50BB9699.6070404@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: Sun, 02 Dec 2012 18:06:13 -0000

On 12/02/2012 12:57 PM, Dave Crocker wrote:
>
>
> On 12/2/2012 9:51 AM, Keith Moore wrote:
>> I think you're missing the point.   The core problem is the overuse of
>> presentations, and presentation tools, for working group face to face
>> meeting time which is better suited for discussion.
>
>
> stop blaming the tool.  focus on the folks doing the speaking.
The tool is a big part of the problem.  The tool encourages a certain 
style of interaction that is generally inappropriate for face to face 
working group meetings.

Of course, strictly speaking, the focus is on the people who are using 
the tool, and more broadly, on using the habit and community expectation 
that keeps encouraging people to use a poorly suited tool.  But they're 
using the tool poorly precisely because it's very difficult to use that 
tool well for that purpose.   A different toolset, (e.g. pens and paper 
and overhead cameras coupled to projectors), would likely produce better 
results if that toolset did not encourage laziness in preparing 
materials to facilitate discussion.

Keith


From melinda.shore@gmail.com  Sun Dec  2 10:06:43 2012
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 E8CC921F86C4 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:06:43 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsZcg5PbM9Co for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:06:43 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6B80221F8687 for <ietf@ietf.org>; Sun,  2 Dec 2012 10:06:43 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so892096dae.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 10:06:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=PdkRBAvzCueBfCBmUoqRlgX0URot3rIxfyTDE+B9dJs=; b=TiuCwR692wMG79xVrJ+IxJul5CMqO6+js207+syiiZL1oYXcN8XkJvo1DCPAHF27N+ rU8mxfqKZ7004wZWYMG3DK6ylf9GJ1h/F9IenwnO82rftXi/PkxfhzE5hAZwSsdKdNJy kPJlbdCHGuaX4BKj9ju2+OCF3qmtsxDzV1L2bprENOuM7iA52ns2ftjvZF3jqXy5hofx ldNcqciuqYfh37zi+jP/iGvn50r0RvjIigFkHNoU/u3LaUfg+gKbpsxFUxd06vGINcPK eaGiWkCIwPVkdpvU1Dv0jIGylBqMBVir5IA/1a7wkwFJLOVnz29jOQifMiPCkTJIN4zG TTRg==
Received: by 10.68.232.2 with SMTP id tk2mr23001071pbc.92.1354471603145; Sun, 02 Dec 2012 10:06:43 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id nt5sm6620105pbb.59.2012.12.02.10.06.41 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 10:06:42 -0800 (PST)
Message-ID: <50BB98B0.2060100@gmail.com>
Date: Sun, 02 Dec 2012 09:06:40 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: PowerPoint considered harmful (was Re: Barely literate minutes)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com>
In-Reply-To: <50BB96C4.2080908@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: Sun, 02 Dec 2012 18:06:44 -0000

On 12/2/12 8:58 AM, Keith Moore wrote:
> I'd add working group chairs (though I'm sure there are a few 
> exceptions) to the list of those with an apparent inability to 
> prioritize and structure work.   Or perhaps WGs should have to get 
> approval from their supervising AD before they can take on new
> documents.

There's a whole nexus of connected issues here, I think, and what
a given person complains about depends on that person's pet peeves.
It seems to me that if we were better about moving work forward
between meetings (<- peeve!) meeting time wouldn't be chewed up
with presenting the current state of the work.  I think design
teams are a handy tool for keeping things moving and have the
side-effect of potentially improving meeting quality.  I'll be the
first to admit the possibility of abuse/things going wrong but
I think keeping work moving is one of the keys to solving this
problem.

I know the EDU team is working hard and has a tough task, but
I also wonder if improving however it is that we acculturate
newer participants might not help, as well.  I would guess that
if you polled meeting participants you'd get a majority of
respondents thinking that meetings are for presentation and
that meetings are used for document adoption and document
content decisions.

Melinda


From moore@network-heretics.com  Sun Dec  2 10:37:35 2012
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 BB71721F85D1 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:37:35 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-jorFh0rOgf for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:37:35 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id D4FFC21F85BC for <ietf@ietf.org>; Sun,  2 Dec 2012 10:37:34 -0800 (PST)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 573D220BE8 for <ietf@ietf.org>; Sun,  2 Dec 2012 13:37:34 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Sun, 02 Dec 2012 13:37:34 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=8XQe41zP2evFlaB4B6CQEt 4FJLA=; b=o3z6brZ51u+fTmHd5TjvQEY4A/ZLo2o9HlKCq+j0dSVCtrHfVrnqQg B1c7yDXdHJYINJh12/+ZyywKehKpyVbBGq4thBZWyPo4uS63Lp0QAaM7yJn9Bqty YVGayWf/xLk3H2fFqT+CxiJ0Im54IsHD704Q6Eki0O1RKcfC5VukE=
X-Sasl-enc: KpvjSgkO5IT0Ffaunz4j9TWslgOTtRcrw6Y/9HuWmK9t 1354473453
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 79464482651; Sun,  2 Dec 2012 13:37:33 -0500 (EST)
Message-ID: <50BB9FE6.5000000@network-heretics.com>
Date: Sun, 02 Dec 2012 13:37:26 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Presentation vs. Discussion sessions (was: PowerPoint considered harmful)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com> <50BB98B0.2060100@gmail.com>
In-Reply-To: <50BB98B0.2060100@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: Sun, 02 Dec 2012 18:37:35 -0000

On 12/02/2012 01:06 PM, Melinda Shore wrote:
> There's a whole nexus of connected issues here, I think, and what
> a given person complains about depends on that person's pet peeves.
> It seems to me that if we were better about moving work forward
> between meetings (<- peeve!) meeting time wouldn't be chewed up
> with presenting the current state of the work.
While I fully agree that most WGs could be better at moving work forward 
between meetings, I don't think it would solve the problem of face to 
face meeting time being filled up with presentations.

I suspect that most WG participants have difficulty keeping up with the 
traffic on their WGs' mailing lists for various reasons (too much 
"distraction" from normal work, the sad state of mail user agents, 
etc.). By forcing people to travel away from work, face-to-face meetings 
serve as useful interruptions from normal distractions and opportunities 
to catch up on IETF work.  If working groups moved forward even faster 
than they do now, that might actually be seen to increase the need for 
presentations at face-to-face meetings.

Occasionally I've wondered if IETF meetings should have "presentation" 
sessions separate from (and in advance of) "working" sessions.    The 
difference between the two types of session would be clearly indicated 
in the schedule.   The presentation sessions would be geared toward 
presenting an overview of current state of the proposals, including a 
summary of recent changes.   Perhaps participants would be allowed to 
ask questions for clarification, but discussion should be discouraged 
and any kind of polling of the room or other decision making would be 
forbidden.  The presentation meetings would therefore be optional for 
those who had kept up on the mailing list.   And presentations would be 
forbidden in discussion sessions.

I can imagine these being useful in several ways, e.g. in facilitating 
better cross-group and cross-area review.   People who were active 
participants in working groups could attend presentation sessions of 
other groups, without sacrificing their attendance in the discussion 
sessions of the groups in which they were active.

Perhaps roughly the first 2(?) days of an IETF meeting could be largely 
devoted to presentation sessions, and the remainder of the time to 
discussion sessions.    Having a strict allocation of time for each kind 
of session isn't so important as having the presentation sessions for a 
particular group well in advance of the discussion session for that group.

This is something that could be tried on a small scale, by a few working 
groups (say one in each area) before being widely adopted. It might 
help, however, to have explicit support for the idea in the tools that 
maintain and display the meeting schedules.

Keith


From melinda.shore@gmail.com  Sun Dec  2 10:41:50 2012
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 0EE5821F86D4 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:41:50 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k1kc3MlKwjab for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:41:49 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 956C121F8476 for <ietf@ietf.org>; Sun,  2 Dec 2012 10:41:49 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1391893pbc.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 10:41:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=f7O++d/0hxrYm/oiBGo0qQShHeoDOAdZ4ACTALzWvZM=; b=gMWNb9/xGqN4/xnHrjdyii3dEDVkyJPxDRR4EDDvCoLAV/sI9k0MfFMrDJ7AGvmHJS i7uVQ0f4Vo/4TeZ/y438PrQk4hN5CzQ4R057JPj3BYBHPBPZpsrmOEftkwPo9FYctTN5 fA8o6fhEAJS8YPXPHMataCpU1pjrPw0n2WNJ8zatIKNCvDmuQ5/SWohfT9ze2mM9v2SM rju/VF6tKYgIW2stq4/H97qmr0BK9Pqu+J3iLZBlpr9N7aZDNJLBajtN1+5EJG49Ev2x XKjAAeFPxzkicUKFT9AKEj4TEF2XNrYf2VtgCkdAdbl7W+ZMxX3Spd3WQSYP6EtBXViP bDoQ==
Received: by 10.68.252.228 with SMTP id zv4mr20772902pbc.134.1354473709414; Sun, 02 Dec 2012 10:41:49 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id ot5sm6661640pbb.29.2012.12.02.10.41.47 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 10:41:48 -0800 (PST)
Message-ID: <50BBA0EA.3070204@gmail.com>
Date: Sun, 02 Dec 2012 09:41:46 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Presentation vs. Discussion sessions
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com> <50BB98B0.2060100@gmail.com> <50BB9FE6.5000000@network-heretics.com>
In-Reply-To: <50BB9FE6.5000000@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: Sun, 02 Dec 2012 18:41:50 -0000

On 12/2/12 9:37 AM, Keith Moore wrote:
> Perhaps roughly the first 2(?) days of an IETF meeting could be largely
> devoted to presentation sessions, and the remainder of the time to
> discussion sessions.   

I think you'd end up with 2 days of presentation sessions and the
remainder of the meeting given over to presentation sessions.

Melinda



From randy@qti.qualcomm.com  Sun Dec  2 10:45:31 2012
Return-Path: <randy@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 7C45721F86D2 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:45:31 -0800 (PST)
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.158, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kl2C-Ai4jNJR for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:45:30 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id CF1E221F8776 for <ietf@ietf.org>; Sun,  2 Dec 2012 10:45:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1354472370; x=1386008370; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=AYquO4VItQMFLOX8VsHx5VT1dfJwkcSJfHWO9tAxacE=; b=ZVSNlbHhHmc3YsxcNtV1L8M/LNlQcVcN0uhfGGzuESToJIawWfdb46/c 3xA2j2jf6EpgWbbaT4capzWyw9BMhyylVSfX1DekorBZKJB1gDH2AopCJ pZE9Lf5jMgvDN0C57mm/1qwDsgzxdzf9mgWXDAvjTbeZmpjqY1g/7WNSr 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6914"; a="10110220"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 02 Dec 2012 10:19:30 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6914"; a="351111177"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 Dec 2012 10:45:30 -0800
Received: from dhcp184-48-45-14.hroa.orl.wayport.net (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 2 Dec 2012 10:45:29 -0800
Message-ID: <p0624060ecce1522d03de@dhcp184-48-45-14.hroa.orl.wayport.net>
In-Reply-To: <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com>  <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com>  <6.2.5.6.2.20121128023905.0afdcde0@resistor.net>  <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>  <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>  <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>  <00c001cdce7a$d9fa6490$8def2db0$@asgard.org>  <50B7EA5D.2030803@qti.qualcomm.com>  <50BA18B8.3090306@network-heretics.com>  <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>  <m2obidvuv7.wl%randy@psg.com>  <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net>  <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com>
X-Mailer: Eudora for Mac OS X
Date: Sun, 2 Dec 2012 10:45:28 -0800
To: John C Klensin <john-ietf@jck.com>, Keith Moore <moore@network-heretics.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: PowerPoint considered harmful (was Re: Barely  literate minutes)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
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, 02 Dec 2012 18:45:31 -0000

At 9:45 AM -0500 12/2/12, John C Klensin wrote:

>  But rigs for cameras that are set up to be
>  pointed down onto sheets of paper on which drawings and notes
>  are being made are a lot more compact, compatible with the
>  projectors we are using already, and, like overhead
>  transparencies and PowerPoint-like decks, leave traces that can
>  easily be incorporated into minutes

I like it this suggestion.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
People must not attempt to impose their own 'truth' on others.  The
right to profess the truth must always be upheld, but not in a way
that involves contempt for those who may think differently.
                                              --John Paul II, 1/1/91

From dhc@dcrocker.net  Sun Dec  2 10:47:28 2012
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 2643321F8430 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:47:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DfXIWt-u2hZh for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:47:27 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A66C721F841A for <ietf@ietf.org>; Sun,  2 Dec 2012 10:47:27 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB2IlQNt021298 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 2 Dec 2012 10:47:26 -0800
Message-ID: <50BBA236.9010603@dcrocker.net>
Date: Sun, 02 Dec 2012 10:47:18 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "'IETF discussion list'" <ietf@ietf.org>
Subject: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk>
In-Reply-To: <01a701cdcd81$7d365380$77a2fa80$@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.17]); Sun, 02 Dec 2012 10:47:27 -0800 (PST)
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, 02 Dec 2012 18:47:28 -0000

On 11/28/2012 8:00 AM, Adrian Farrel wrote:
> I led the discussion in the WG Chairs lunch at IETF 78 on this topic.
> Slides at http://wiki.tools.ietf.org/group/edu/wiki/IETF78#


Folks,

There is now an Internet Draft, based on Adrian's's slides, intended to 
document common practice in the adoption of working group drafts:

> Title:   Creating an IETF Working Group Draft
> Status:  http://datatracker.ietf.org/doc/draft-crocker-id-adoption
>
> Abstract:
>    The productive output of IETF working groups is documents, as
>    mandated by the working group's charter.  Working groups develop
>    these documents based on initial input of varying levels of maturity.
>    An initial working group draft might be a document already in wide
>    use, or it might be a blank sheet, wholly created by the workiing
>    group, or it might represent any level of maturity in between.  This
>    document discusses the process of creating formal working group
>    drafts that are targeted for publication.



Although it is not intended for a standards-track or bcp publication, it 
would be helpful to have discussion that moves the document to represent 
good agreement among the community.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From joelja@bogus.com  Sun Dec  2 10:48:39 2012
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 EA48A21F847B for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:48:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N+JVl4OKWFDE for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 10:48:39 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5C1F321F841A for <ietf@ietf.org>; Sun,  2 Dec 2012 10:48:39 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-207-206-4.hsd1.ca.comcast.net [98.207.206.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qB2ImbqF008407 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 2 Dec 2012 18:48:38 GMT (envelope-from joelja@bogus.com)
Message-ID: <50BBA21D.6090403@bogus.com>
Date: Sun, 02 Dec 2012 10:46:53 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com>
In-Reply-To: <50BB9888.8080906@network-heretics.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]); Sun, 02 Dec 2012 18:48:38 +0000 (UTC)
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, 02 Dec 2012 18:48:40 -0000

On 12/2/12 10:06 AM, Keith Moore wrote:
> On 12/02/2012 12:57 PM, Dave Crocker wrote:
>>
>>
>> On 12/2/2012 9:51 AM, Keith Moore wrote:
>>> I think you're missing the point.   The core problem is the overuse of
>>> presentations, and presentation tools, for working group face to face
>>> meeting time which is better suited for discussion.
>>
>>
>> stop blaming the tool.  focus on the folks doing the speaking.
> The tool is a big part of the problem.  The tool encourages a certain 
> style of interaction that is generally inappropriate for face to face 
> working group meetings.
>

We have non-native english speakers and remote participants both working 
at a disadvantage to follow the discussion in the room. We should make 
it harder for them by removing the pretext that the discussion is 
structured around material that they can review and follow along on? I 
don't think that's even remotely helpful.

> Of course, strictly speaking, the focus is on the people who are using 
> the tool, and more broadly, on using the habit and community 
> expectation that keeps encouraging people to use a poorly suited 
> tool.  But they're using the tool poorly precisely because it's very 
> difficult to use that tool well for that purpose.   A different 
> toolset, (e.g. pens and paper and overhead cameras coupled to 
> projectors), would likely produce better results if that toolset did 
> not encourage laziness in preparing materials to facilitate discussion.

> Keith
>


From moore@network-heretics.com  Sun Dec  2 11:15:24 2012
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 E387921F8734 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:15:24 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DQdEXtBhVPrg for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:15:24 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0964821F85B6 for <ietf@ietf.org>; Sun,  2 Dec 2012 11:15:24 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 682C32080E; Sun,  2 Dec 2012 14:15:23 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 02 Dec 2012 14:15:23 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type; s=smtpout; bh=xGzQ MTztzSIyTnt4wZlvFYiSpLY=; b=ZhUKxmiFnVQt+vIJUN1+KDLKYwgfgEbt129T NJnfYuhrV3uFI9krYJ0kTmNKT+TR4rmISWI2XTAmO0MLGrVkKe7Na+dJsdwuKc0F oAVsqLQlomYr2FGyeEM1hhvVgeB3DI+udU3xRxtJ96nzGAsIY5JONfN937GbnX6L o/wKDZw=
X-Sasl-enc: g0+2ZPNSVQoTC3ZCxCKTuIP029PZmspP4Cr+CppBf7SL 1354475722
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 5E8268E05CD; Sun,  2 Dec 2012 14:15:22 -0500 (EST)
Message-ID: <50BBA8C3.6040100@network-heretics.com>
Date: Sun, 02 Dec 2012 14:15:15 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com>
In-Reply-To: <50BBA21D.6090403@bogus.com>
Content-Type: multipart/alternative; boundary="------------070303040303080405020109"
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, 02 Dec 2012 19:15:25 -0000

This is a multi-part message in MIME format.
--------------070303040303080405020109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12/02/2012 01:46 PM, joel jaeggli wrote:
> We have non-native english speakers and remote participants both 
> working at a disadvantage to follow the discussion in the room. We 
> should make it harder for them by removing the pretext that the 
> discussion is structured around material that they can review and 
> follow along on? I don't think that's even remotely helpful.

In general, the purpose of those meetings is *discussion*, not 
presentation.   I'm all for exploring better ways to facilitate 
*discussion* among the diversity of IETF meeting attendees.  But our 
experience with use of previously-prepared PowerPoint presentations to 
facilitate *discussion* shows that use of that tool, in that way and for 
that purpose, is a miserable failure.

Of course I'd encourage speakers to make available for download 
summaries of the material to be discussed in advance of the meeting, for 
the benefit of non-native English speakers and others. PowerPoint (or 
better, PDF of material prepared in PowerPoint) seems like a reasonable 
format for that.

I also think it would be quite helpful to arrange for the topics 
discussed and points raised in the discussion to be displayed in the 
room in real time, as they are typed.   This would provide non-native 
speakers with visuals similar to what they see now with PowerPoint, but 
without the undesirable side-effect of coercing discussion time into 
presentations.   This would also reinforce the need for a minute-taker 
and help to keep the minute-takers honest.

(I doubt that PowerPoint is the best tool for this purpose, since it 
would be highly desirable to convey the same information, at the same 
time, to remote participants.)

Keith


--------------070303040303080405020109
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 12/02/2012 01:46 PM, joel jaeggli
      wrote:<br>
    </div>
    <blockquote cite="mid:50BBA21D.6090403@bogus.com" type="cite">We
      have non-native english speakers and remote participants both
      working at a disadvantage to follow the discussion in the room. We
      should make it harder for them by removing the pretext that the
      discussion is structured around material that they can review and
      follow along on? I don't think that's even remotely helpful.
      <br>
    </blockquote>
    <br>
    In general, the purpose of those meetings is <b>discussion</b>, not
    presentation.&nbsp;&nbsp; I'm all for exploring better ways to facilitate <b>discussion</b>
    among the diversity of IETF meeting attendees.&nbsp; But our experience
    with use of previously-prepared PowerPoint presentations to
    facilitate <b>discussion</b> shows that use of that tool, in that
    way and for that purpose, is a miserable failure.&nbsp; <br>
    <br>
    Of course I'd encourage speakers to make available for download
    summaries of the material to be discussed in advance of the meeting,
    for the benefit of non-native English speakers and others.
    PowerPoint (or better, PDF of material prepared in PowerPoint) seems
    like a reasonable format for that.&nbsp;&nbsp; <br>
    <br>
    I also think it would be quite helpful to arrange for the topics
    discussed and points raised in the discussion to be displayed in the
    room in real time, as they are typed.&nbsp;&nbsp; This would provide
    non-native speakers with visuals similar to what they see now with
    PowerPoint, but without the undesirable side-effect of coercing
    discussion time into presentations.&nbsp;&nbsp; This would also reinforce the
    need for a minute-taker and help to keep the minute-takers honest.<br>
    <br>
    (I doubt that PowerPoint is the best tool for this purpose, since it
    would be highly desirable to convey the same information, at the
    same time, to remote participants.)<br>
    <br>
    Keith<br>
    <br>
  </body>
</html>

--------------070303040303080405020109--

From moore@network-heretics.com  Sun Dec  2 11:18:21 2012
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 9DC2A21F8464 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:18:20 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7EoiOENb9vDD for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:18:15 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id F377421F843F for <ietf@ietf.org>; Sun,  2 Dec 2012 11:18:14 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A56C220EDD for <ietf@ietf.org>; Sun,  2 Dec 2012 14:18:14 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Sun, 02 Dec 2012 14:18:14 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=3+Bn55FC2xUzkqCzcVRew/ u3Ad0=; b=LXBMPOF0oFeoh9qDZbh6x6u/K5EV1dn3+Ydp+9qc9bupX4g3UHOmXJ Rd0lKqwOgtYETg4vOrDlvb9nCb3xY9d5qnOBIVKE42b7dcf/j6MZMg0FeMiBzFQt 9zccGTj24Y8giA5OYebP7LoJZkzizx7ddAgzr7wiEJu0I3SW0cAiU=
X-Sasl-enc: QfoksxMhGiCfdLBmCnwuTwB9P0t4G1inhd6FitIcwGt4 1354475894
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 136028E0573; Sun,  2 Dec 2012 14:18:13 -0500 (EST)
Message-ID: <50BBA96F.3080401@network-heretics.com>
Date: Sun, 02 Dec 2012 14:18:07 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Presentation vs. Discussion sessions
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com> <50BB98B0.2060100@gmail.com> <50BB9FE6.5000000@network-heretics.com> <50BBA0EA.3070204@gmail.com>
In-Reply-To: <50BBA0EA.3070204@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: Sun, 02 Dec 2012 19:18:21 -0000

On 12/02/2012 01:41 PM, Melinda Shore wrote:
> On 12/2/12 9:37 AM, Keith Moore wrote:
>> Perhaps roughly the first 2(?) days of an IETF meeting could be largely
>> devoted to presentation sessions, and the remainder of the time to
>> discussion sessions.
> I think you'd end up with 2 days of presentation sessions and the
> remainder of the meeting given over to presentation sessions.
>
In which case the ADs should fire the chairs on the spot.

Keith


From melinda.shore@gmail.com  Sun Dec  2 11:21:20 2012
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 E800321F8464 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:21:20 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4LYJuQXyY6s7 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:21:20 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7532A21F87A4 for <ietf@ietf.org>; Sun,  2 Dec 2012 11:21:20 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so1322702pad.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 11:21:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LdLJJqGBN5r5vKZxz0jaCe31zbVlUv8hT31hPhIMMwY=; b=baSnRfB5fqviskhSmcwblWAwlGqVgO1UbiKjqMzHCj0usWe7nCTPD18ZSTeCWRr++p VHDmH4Tqi9425OiVF/1LfmIpKIlHP41XMEMrT107BI+3qB2XBgg+gfvaJywdCZRPc0ut 1qk2e9CdTPCN9EGkfttUwLbz9qlOhgYleaqjo4mVeBe/NT+g+49DH1wIuKGfaBeDh3QD fhy2EEQYn2eGrSlHKCKwMH09gAehGqli/0/k/4ZYx/AD81la5wA4k2FTGdwdk1HOj29m ra/JRMR7Z7MKBOO5fHNTSs1tsL3Hsy8XHSvACGv9X7d9XmJah0T5qQ9hVgVK7rGA2QjD 5PtQ==
Received: by 10.68.209.170 with SMTP id mn10mr23470754pbc.11.1354476080236; Sun, 02 Dec 2012 11:21:20 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id os5sm6702684pbc.15.2012.12.02.11.21.18 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 11:21:19 -0800 (PST)
Message-ID: <50BBAA2D.70900@gmail.com>
Date: Sun, 02 Dec 2012 10:21:17 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Presentation vs. Discussion sessions
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com> <50BB98B0.2060100@gmail.com> <50BB9FE6.5000000@network-heretics.com> <50BBA0EA.3070204@gmail.com> <50BBA96F.3080401@network-heretics.com>
In-Reply-To: <50BBA96F.3080401@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: Sun, 02 Dec 2012 19:21:21 -0000

On 12/2/12 10:18 AM, Keith Moore wrote:
> On 12/02/2012 01:41 PM, Melinda Shore wrote:
>> I think you'd end up with 2 days of presentation sessions and the
>> remainder of the meeting given over to presentation sessions.
> In which case the ADs should fire the chairs on the spot.

If that's the solution to the presentation problem, then why not
apply it to chairs who mismanage meetings now, rather than creating
new processes/structures?

Melinda



From moore@network-heretics.com  Sun Dec  2 11:25:54 2012
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 7808521F8B5A for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:25:54 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pdSk5fogBrL4 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:25:53 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6005521F898C for <ietf@ietf.org>; Sun,  2 Dec 2012 11:25:53 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6A12F20EB9 for <ietf@ietf.org>; Sun,  2 Dec 2012 14:25:49 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Sun, 02 Dec 2012 14:25:49 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=YegI3jo3SfMOuHl6ElO3cA oUCEw=; b=jJi4UVsk30qiOP94HV6Flk8WC+Oc16GyP8xXtFqRnfrPQf4U5aZMXj ARUqk5rO3+oom87CBaxxW8gN7sInirlnW9KvxRQ+7ofA2n5nDdUAaws9krsH8Z0m c7oK252YWOXdRLPv9Zd7350KvO+WvBzMAIecxVY0I0PkYbP7eC3Y0=
X-Sasl-enc: OV7aHuf5nUNzbtzlO/hXmrDlXiu4w2Qx058wc11BmiQj 1354476348
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id ADCDE8E05D0; Sun,  2 Dec 2012 14:25:48 -0500 (EST)
Message-ID: <50BBAB36.3080605@network-heretics.com>
Date: Sun, 02 Dec 2012 14:25:42 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Presentation vs. Discussion sessions
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com> <50BB98B0.2060100@gmail.com> <50BB9FE6.5000000@network-heretics.com> <50BBA0EA.3070204@gmail.com> <50BBA96F.3080401@network-heretics.com> <50BBAA2D.70900@gmail.com>
In-Reply-To: <50BBAA2D.70900@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: Sun, 02 Dec 2012 19:25:54 -0000

On 12/02/2012 02:21 PM, Melinda Shore wrote:
> On 12/2/12 10:18 AM, Keith Moore wrote:
>> On 12/02/2012 01:41 PM, Melinda Shore wrote:
>>> I think you'd end up with 2 days of presentation sessions and the
>>> remainder of the meeting given over to presentation sessions.
>> In which case the ADs should fire the chairs on the spot.
> If that's the solution to the presentation problem, then why not
> apply it to chairs who mismanage meetings now, rather than creating
> new processes/structures?
It's pointless to tell people to stop doing what they're accustomed to 
doing, unless you give them a better way and let them experience that it 
works better.

As I pointed out earlier, this is something that can be tried on a small 
scale.  If it's not found to work well, there's little harm done.

Keith


From brian.e.carpenter@gmail.com  Sun Dec  2 11:28:07 2012
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 A923521F8744 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AlyuU+mDISbo for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 11:28:07 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id EC42321F8754 for <ietf@ietf.org>; Sun,  2 Dec 2012 11:28:06 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so876672wey.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 11:28:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=unPBc2QjnOoDuYn4Bw41u3/AymO0jMsPrzMI5fojmTA=; b=oeVMZr5gJXDlQ1WVahuohw1NCNBJ9zBWJ87sK2OGhCpTaqNcT98WETVWAT8ff/2uAE ZRm3J6iQ6aySS/m8cYHK/RyXnucjw4/kuxCfx2wzt8lnusV21f3Mg8I7a4U2zBblNP++ qXGXez5wuXjTt89dVXae3TltUR0uWbINo0AgNyEOSTrzxsC1HP/EtjMC+CY2Ux+gLhpM d0aJk6D+9mDz5jrA2wNJXTk74M/XIjCA27EGI5zFhEIxKkn1jYyKKgA9B9LtZ/57yG9b 6Lyixd8kQmrbZQjvKLltC8MX2Fko1gdyftDnBgQS8tUFU++3tLZbhZv7MJN2kZZu2CR5 g9lA==
Received: by 10.180.102.40 with SMTP id fl8mr6192783wib.22.1354476485920; Sun, 02 Dec 2012 11:28:05 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-29.as13285.net. [2.102.218.29]) by mx.google.com with ESMTPS id i6sm8093116wix.5.2012.12.02.11.28.04 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 11:28:04 -0800 (PST)
Message-ID: <50BBABBC.1050405@gmail.com>
Date: Sun, 02 Dec 2012 19:27:56 +0000
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: Acculturation [was Re: PowerPoint considered harmful]
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>	<CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>	<00c001cdce7a$d9fa6490$8def2db0$@asgard.org>	<50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com>	<p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>	<m2obidvuv7.wl%randy@psg.com>	<p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net>	<50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com>	<17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com>	<50BB6B61.4040304@network-heretics.com>	<3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com>	<50BB6FC8.8040907@network-heretics.com>	<50BB8DA8.5070406@joelhalpern.com>	<AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com>	<50BB96C4.2080908@network-heretics.com> <50BB98B0.2060100@gmail.com>
In-Reply-To: <50BB98B0.2060100@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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, 02 Dec 2012 19:28:07 -0000

On 02/12/2012 18:06, Melinda Shore wrote:
=2E..
> I know the EDU team is working hard and has a tough task, but
> I also wonder if improving however it is that we acculturate
> newer participants might not help, as well.  I would guess that
> if you polled meeting participants you'd get a majority of
> respondents thinking that meetings are for presentation and
> that meetings are used for document adoption and document
> content decisions.

We get exactly two shots at new participants: the newcomers
tutorial, and the newcomers reception, both on Sunday afternoon
(i.e. before some people even arrive). After that, they are in
the mix, and further acculturation happens in the WGs and
corridors (plus, no doubt, some extreme puzzlement in plenary).

The newbie presentation has about 68 slides. They include these words:

Working Groups
* this is where the IETF primarily get its work done
* most discussions on a WG mailing list
* face-to-face meetings focused on key issues (ideally)
	note: face-to-face meetings generally quite short
=2E..
* no defined membership
* just participants
* =E2=80=9CRough consensus and running code...=E2=80=9D
* no formal voting  (can not define the constituency)
	can do show of hands or hum - but no count
* does not require unanimity
* chair determines if there is consensus
* disputes resolved by discussion
* mailing list and face-to-face meetings
* final decisions must be verified on mailing list
  to ensure those not present at face-to-face are included
* but taking into account face-to-face discussion

A Working Group Session
* WGs only meet for a few hours at an IETF meeting
* most working group work is done on the WG mailing list
* often only specific unresolved issues are discussed at meetings
  so read the IDs and mailing list before the session

     Brian


From arturo.servin@gmail.com  Sun Dec  2 12:18:40 2012
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 E3F0821F8789 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:18:40 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6ez+bHFa3Qg for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:18:40 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5EC1121F873B for <ietf@ietf.org>; Sun,  2 Dec 2012 12:18:40 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id r1so329781ggn.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 12:18:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=lGa9KtSYKETjWSrC5bH2+Sf4KwftoiApzrg9w1uNqZQ=; b=Tb/xazSsEnuEd15LK2bhIrTeKAktdEebLOYjyuwzGzTwnywHr2/TyG/bLgpXSojm4r vw1n3erKS6VLFBMP20UW8yu8R0BCGDPs2R/w46pLcFX4FQPgHzZ+m6ba1GymzENN72+j v2WY7DHghOiS5fjwlBPp6LfUpJy4wXkWKKnwvIzJ5+XDNG1xC4d1xvC2Vkic4HA13hoX IMIi9EsLCeOMhjN5eYtJhiPw27uKb3vWAYwVsodvUH2//rFS9E/gSnU4JCOznyN9aL4c RA+lyKsOZjpgu8HQCrD4zpjl95gKQ215cGdiYuK22wC2Pp5UCJNQJv0FfL87TpCzSnDS hfxg==
Received: by 10.236.162.69 with SMTP id x45mr8406114yhk.111.1354479519824; Sun, 02 Dec 2012 12:18:39 -0800 (PST)
Received: from ?IPv6:2800:af:ba30:dce4:8d71:6412:72dd:2b46? ([2800:af:ba30:dce4:8d71:6412:72dd:2b46]) by mx.google.com with ESMTPS id s21sm11127876yhb.5.2012.12.02.12.18.37 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 12:18:38 -0800 (PST)
Message-ID: <50BBB79C.40106@gmail.com>
Date: Sun, 02 Dec 2012 18:18:36 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net>
In-Reply-To: <50BBA236.9010603@dcrocker.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: Sun, 02 Dec 2012 20:18:41 -0000

	In Section 2.1, I would add in specifically-inappropriate criteria:

	- Accept an I+D for the merely fact to have a more structured
discussion in the WG.

Regards
::as

On 02/12/2012 16:47, Dave Crocker wrote:
> 
> 
> On 11/28/2012 8:00 AM, Adrian Farrel wrote:
>> I led the discussion in the WG Chairs lunch at IETF 78 on this topic.
>> Slides at http://wiki.tools.ietf.org/group/edu/wiki/IETF78#
> 
> 
> Folks,
> 
> There is now an Internet Draft, based on Adrian's's slides, intended to
> document common practice in the adoption of working group drafts:
> 
>> Title:   Creating an IETF Working Group Draft
>> Status:  http://datatracker.ietf.org/doc/draft-crocker-id-adoption
>>
>> Abstract:
>>    The productive output of IETF working groups is documents, as
>>    mandated by the working group's charter.  Working groups develop
>>    these documents based on initial input of varying levels of maturity.
>>    An initial working group draft might be a document already in wide
>>    use, or it might be a blank sheet, wholly created by the workiing
>>    group, or it might represent any level of maturity in between.  This
>>    document discusses the process of creating formal working group
>>    drafts that are targeted for publication.
> 
> 
> 
> Although it is not intended for a standards-track or bcp publication, it
> would be helpful to have discussion that moves the document to represent
> good agreement among the community.
> 
> d/
> 

From melinda.shore@gmail.com  Sun Dec  2 12:21:57 2012
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 43F8E21F878B for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:21:57 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-JVJ3O6kTat for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:21:56 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id CE50621F8789 for <ietf@ietf.org>; Sun,  2 Dec 2012 12:21:56 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so1336573pad.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 12:21:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=9wXH1Y6PM12LkRjdBp3H4wY7UfKezje+oZOK2jxws4c=; b=mTrbr7xx99XPu36Y8HV8qkwUFJFgbl9KZAqFzh4pcfIHeoKJqggepap1IiHK0y0nXT QqZS6oDGqWbuJeJ6dkf2L/vKOtwGVzNIYehVfFqUhqfkQ4ojzIfgVLAKPIDTMTw4zYGs 50+mWTbj5J4EimT7np+QVcuHFi8yGBZqTth39Quk149rbCYs69Nhmpnkan4DC0uiFVJF Q0sxq0ZHVbCFHoAYrprj6gH48buShYlAwQOZL9qMr6MKq/m/y4xL8Uqe5QnFUiUAvg+c 2btCNVIZMZMSsMFeOzOANSLSPL5IXDqtlVLeyYEXni6/wsFKVM6WOOLcHeRtBh3PB2Hb RBxw==
Received: by 10.69.1.73 with SMTP id be9mr23769353pbd.116.1354479716636; Sun, 02 Dec 2012 12:21:56 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id mz10sm6756827pbc.37.2012.12.02.12.21.55 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 12:21:56 -0800 (PST)
Message-ID: <50BBB862.8090209@gmail.com>
Date: Sun, 02 Dec 2012 11:21:54 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com>
In-Reply-To: <50BBB79C.40106@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, 02 Dec 2012 20:21:57 -0000

On 12/2/12 11:18 AM, Arturo Servin wrote:
> 
> 	In Section 2.1, I would add in specifically-inappropriate criteria:
> 
> 	- Accept an I+D for the merely fact to have a more structured
> discussion in the WG.

I'm actually not sure about that.  It seems to me that in the past
we've had working group documents which were not intended for
publication, and I think they'd fall under this criterion.  I may
be misremembering.  At any rate I'm not sure I see the value in
ruling these out.

Melinda



From sm@resistor.net  Sun Dec  2 12:24:38 2012
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 533B521F87B9 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:24:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.653
X-Spam-Level: 
X-Spam-Status: No, score=-102.653 tagged_above=-999 required=5 tests=[AWL=-0.054, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pc72ldMr2BpI for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:24:37 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA7D21F87A4 for <ietf@ietf.org>; Sun,  2 Dec 2012 12:24:37 -0800 (PST)
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 qB2KOUS7022724; Sun, 2 Dec 2012 12:24:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354479874; bh=Fb6GsVZc2jfOIk7euhtoxj1e1rgg8+vQiILAJeCklgs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4nGlA0WEUsg378lSxVNCMxjIAez1jhvtsdSs80z4cGnYwHCQZTXE8YpLtnOkSYmpr CSrrDqqbKIHqoZJZrodawk6HQvXcr/Tsv/jD336eV7xWTQb1MosO1lmET1mrGAk+i8 +X8Q++Rw0JIKnG4h5VSxmGYPG5rXwaFOy1veg7T4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354479874; i=@resistor.net; bh=Fb6GsVZc2jfOIk7euhtoxj1e1rgg8+vQiILAJeCklgs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k3f8utFK9YRebsp+1btCC27BneZKdp561DuDZQE8dmf1UrrLBY88Ztb6YDN+kxUA7 KoKIX6bFQfGoot5h/coiu/Yv8V5CQbfFSIvVLWsG3LvSaLhtkLwgv+GjlS7ihNWaJJ BeX+c4OAWBGLntBjff9Y2J/OHSkXxlKKvGRYLY7Y=
Message-Id: <6.2.5.6.2.20121202110318.092ea5e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 02 Dec 2012 12:07:37 -0800
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: English spoken here (was: PowerPoint considered harmful)
In-Reply-To: <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.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: Sun, 02 Dec 2012 20:24:38 -0000

Hi John,
At 09:21 02-12-2012, John C Klensin wrote:
>(d) Their reading-English is much better than their spoken
>English and they have trouble keeping up even if (b) is quite
>moderate.

Yes.

>But can be considerably aided in many cases by written material
>(slides, summaries, or both) well in advance especially if those
>material are also used at the meeting, thereby aiding
>synchronization.

As a personal opinion I would say yes but I'll leave it to the 
consensus of the group.

>Cultural styles also make some of the most affected parties less
>likely to speak up for their specific needs on this list than
>one might like.  That leaves the rest of us with a choice

Probably.

Please note that I don't know the solution.

Regards,
-sm   


From arturo.servin@gmail.com  Sun Dec  2 12:25:38 2012
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 9611421F87BC for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:25:38 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YrbhoHCkC5YY for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:25:38 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1B0DC21F87A4 for <ietf@ietf.org>; Sun,  2 Dec 2012 12:25:38 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id r1so330246ggn.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 12:25:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=npGD5UjPfgPgbeD5yGJZajb82xQdFRII2ANwuxRA8as=; b=mJkowdCSGwnTx3lJoPuw6+CoC6fmDwpWQEeJk4qKdM7xWxX5lxa6Cas75qHbAUJane jDX564mXDpTHHxrPIB36Pspw33uV4QIA/MVDeWlQUz4wm/3dVuiEcFYZkF/f0HvZNXMA nIyTQFCD29A9gbaB4Cy7a3mokUrkLVZR9M6YGJBo23U68Yll1/CLfuzagfTbAJfnShpw xDy14F5jiHT3a+NbkDjMMKD3xuAHnXKUwpaDJFNve+99vPA7FsZfkP6R71HvavvN23S2 ZpdK5Mo2GStBAj7A/XHV+prC3pO1qM/xdZ7B/46YIH60pqE992dEakDoClXmczUXMSNv ehZQ==
Received: by 10.236.142.139 with SMTP id i11mr8318087yhj.24.1354479937714; Sun, 02 Dec 2012 12:25:37 -0800 (PST)
Received: from [192.168.1.133] (r186-48-220-228.dialup.adsl.anteldata.net.uy. [186.48.220.228]) by mx.google.com with ESMTPS id k49sm11124961yhj.13.2012.12.02.12.25.35 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 12:25:36 -0800 (PST)
Message-ID: <50BBB940.1020302@gmail.com>
Date: Sun, 02 Dec 2012 18:25:36 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com>
In-Reply-To: <50BBB862.8090209@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, 02 Dec 2012 20:25:38 -0000

	So it is ok to have bad ideas as I+D, possibly harmful for the Internet
just to have a structured discussion?

	
Regards,
as

On 02/12/2012 18:21, Melinda Shore wrote:
> On 12/2/12 11:18 AM, Arturo Servin wrote:
>>
>> 	In Section 2.1, I would add in specifically-inappropriate criteria:
>>
>> 	- Accept an I+D for the merely fact to have a more structured
>> discussion in the WG.
> 
> I'm actually not sure about that.  It seems to me that in the past
> we've had working group documents which were not intended for
> publication, and I think they'd fall under this criterion.  I may
> be misremembering.  At any rate I'm not sure I see the value in
> ruling these out.
> 
> Melinda
> 

From dhc@dcrocker.net  Sun Dec  2 12:32:37 2012
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 D5F6721F87BC for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:32:37 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35xMkadA09Hr for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:32:37 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB9C21F87B1 for <ietf@ietf.org>; Sun,  2 Dec 2012 12:32:37 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB2KWabK029001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 2 Dec 2012 12:32:37 -0800
Message-ID: <50BBBADC.2050309@dcrocker.net>
Date: Sun, 02 Dec 2012 12:32:28 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "'IETF discussion list'" <ietf@ietf.org>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net>
In-Reply-To: <50BBA236.9010603@dcrocker.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.17]); Sun, 02 Dec 2012 12:32:37 -0800 (PST)
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, 02 Dec 2012 20:32:37 -0000

On 12/2/2012 10:47 AM, Dave Crocker wrote:
> There is now an Internet Draft, based on Adrian's's slides, intended to
> document common practice in the adoption of working group drafts:
>
>> Title:   Creating an IETF Working Group Draft
>> Status:  http://datatracker.ietf.org/doc/draft-crocker-id-adoption


Many apologies.  In my haste, I submitted a version of the draft that 
was missing a number of important changes.

The latest version is now posted:

 > Filename:	 draft-crocker-id-adoption
 > Revision:	 01
...
 > Status:    http://datatracker.ietf.org/doc/draft-crocker-id-adoption


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Sun Dec  2 14:37:26 2012
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 8089121F88F0 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 14:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.649
X-Spam-Level: 
X-Spam-Status: No, score=-102.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mBML5D04FOB for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 14:37:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B602A21F88A6 for <ietf@ietf.org>; Sun,  2 Dec 2012 14:37:25 -0800 (PST)
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 qB2MbB9o017459; Sun, 2 Dec 2012 14:37:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354487837; bh=RvojTgK3N7ppCOvUd5m9SAQj9of8dx8tKu7ofOxhgMU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kaJni9mZDCq9fNQJ7VCQdvWfqbFVBUhU42ppLSeHqLfJ1+LdRfg3F8l9gENsqF7P2 ectdCNB6Q1XwG5hb/JJx/xWxJF7fJ5Z7NseudjbTniCFMg2nolEQFOzC2zT9RsbBsi LkmUVJWXXFzL/pqf3c9uDxi2WNzdsQzlLpmB2qps=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354487837; i=@resistor.net; bh=RvojTgK3N7ppCOvUd5m9SAQj9of8dx8tKu7ofOxhgMU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2hrvu4Re1yv6i0DWWxTY+naACynWtjQ/rGwERvFGOQScDZDU5weM4JBQmAq+wZ+WS dS/OzaIhTpuC2EwjJhbAYew+LCyxfbwiv+tGnQAg3ruDL+dbFBuzaZFI/c53K8uc3r 70Vcb1iB3RsxsfenWcoidsIGkS23b0CO2y8rW/U4=
Message-Id: <6.2.5.6.2.20121202130842.0a8266e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 02 Dec 2012 14:36:50 -0800
To: ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>, Adrian Farrel <adrian@olddog.co.uk>
From: SM <sm@resistor.net>
Subject: Re: Creating an IETF Working Group Draft
In-Reply-To: <50BBB940.1020302@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Arturo Servin <arturo.servin@gmail.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, 02 Dec 2012 22:37:26 -0000

At 12:25 02-12-2012, Arturo Servin wrote:
>         So it is ok to have bad ideas as I+D, possibly harmful for 
> the Internet
>just to have a structured discussion?

Yes.

I'll comment on draft-crocker-id-adoption-01.

Section 1 is fine.  I'll suggest not amending the BCP (see the last 
round of RFCs about IPR as an example).

In Section 1.1:

   "and Section 8.3 of [RFC4677]"

I suggest using the web page ( http://www.ietf.org/tao.html ).

In Section 2.1:

   "No formal specification for working group 'adoption' of a draft
    exists;"

Procedures may be a better fit.

   "*  What is the position of the working group chairs, concerning
       the draft?"

I suggest removing this from basic considerations to keep matters easy.

   "REMINDER:   Once a working group adopts a draft, the document is
       owned by the working group and can be changed however the working
       group decides, within the bounds of IETF process and the working
       group charter.  It is a responsibility of the working group chairs
       to ensure that document authors make modifications in accord with
       working group rough consensus."

 From the BCP:

   "The Document Editor is responsible for ensuring that the contents
    of the document accurately reflect the decisions that have been
    made by the working group."

I suggest rephrasing the last sentence reminder as:

   It is a responsibility of the document authors to make modifications in
   accord with working group rough consensus.

In Section 2.2:

  "and Section 5.2 of [RFC4677]"

See above comment about the Tao.

   "Thus, when it is not completely obvious what the opinion of the
    working group is, working group chairs should poll the working group
    to find out."

I'll highlight part of a comment [1] from Geoff Huston:

   'such expressions of disinterest in adopting the draft by some
    strange twist of logic are portrayed to point to "interest in
    discussing the document"'

If you use a poll it ends up as a 'yes/no'.  The problem zone is when 
there are valid arguments on both sides.  To put it simply there can 
always be a good reason not to adopt a draft (see thread at 
http://www.ietf.org/mail-archive/web/sidr/current/msg04922.html ).

You could treat the decision of adoption as secondary and have 
opinions about the "problem to be solved" as the primary intent.  You 
could then use the following:

   Is there strong working group support to work on the draft?

In my humble opinion it is important to tell the group up-front what 
is being decided.  I cannot think of text to suggest.

One of the problems is that there is an assumption that the text 
being adopted has consensus.  This leads to discussions about what 
text must be changed for the wg-00 version to be acceptable.  The 
adoption turns into a review of the draft.  There is ample time to 
produce changes as the WG will be working on the draft if it adopts it.

In Section 2.3 "Choosing Editors".

In Section 4:

   "I can't find an explicit description of Individual vs. Working
    group draft.  Some pages/docs imply the distinction, but not
    define it."

The Last Call is longer (see 
http://www.ietf.org/iesg/statement/ad-sponsoring-docs.html ).  It may 
be easier to drop Section 4 as the draft discusses about "IETF 
Working Group Draft".

Regards,
-sm

P.S. An I-D encourages the author to structure what he/she would like 
to communicate.

1. http://www.ietf.org/mail-archive/web/ietf/current/msg76053.html


From arturo.servin@gmail.com  Sun Dec  2 15:35:38 2012
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 1FFCA21F885B for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:35:38 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O6OPlO5Kou93 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:35:37 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 56B9821F885A for <ietf@ietf.org>; Sun,  2 Dec 2012 15:35:37 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id r1so345223ggn.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 15:35:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=2R7wYWV6sm56g3/YKZmRWWFdTgxSh3E3nzsIAJ/yi6s=; b=uNpNONo/5l7DOdZV1w8XLa/SOOnVMfCdUu1GsUT1w3XbppzBskNZrAyWxGe5TLVJpF 5l1Dx73eJeUkWrPhyTdrkZKJaJCV9/sSIkLjwevQzbf9MMjqcMM2NOu2o7VfVjocQmRD FpEEXy8/52KQssWi2UHgSp7KxcGJqNem/bsexN2JcXvbPGkRAVRb9QpFafNRxAdmau/w bRAcCjf9PkjA5ZaKC/7vuLiywMmfqJGTGMI8HiyW1xSmS30abuxBSoTpto81UwZCeaua robd1ZzoDHKKxFhZYXpFHP9V0RpqpUArKRriHgm0PwnBGJ2QyQgV52O6lVTrmTSmjB6r fE1A==
Received: by 10.236.52.198 with SMTP id e46mr8652816yhc.57.1354491336749; Sun, 02 Dec 2012 15:35:36 -0800 (PST)
Received: from ?IPv6:2800:af:ba30:deec:7c45:a2c0:b751:de2? ([2800:af:ba30:deec:7c45:a2c0:b751:de2]) by mx.google.com with ESMTPS id t14sm10259512anl.17.2012.12.02.15.35.33 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 15:35:35 -0800 (PST)
Message-ID: <50BBE5C3.7050802@gmail.com>
Date: Sun, 02 Dec 2012 21:35: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/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <6.2.5.6.2.20121202130842.0a8266e0@resistor.net>
In-Reply-To: <6.2.5.6.2.20121202130842.0a8266e0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, Arturo Servin <arturo.servin@gmail.com>, ietf@ietf.org, Dave Crocker <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: Sun, 02 Dec 2012 23:35:38 -0000

	Well, I think we shouldn't.

	I would prefer to have the I+D as non-wg item until we are sure that we
are willing to support it as RFC.


/as


On 02/12/2012 20:36, SM wrote:
> At 12:25 02-12-2012, Arturo Servin wrote:
>>         So it is ok to have bad ideas as I+D, possibly harmful for the
>> Internet
>> just to have a structured discussion?
> 
> Yes.

From randy@psg.com  Sun Dec  2 15:50:13 2012
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 B08B721F87EE for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:50:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.059,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYvhnOpRvBTs for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:50:13 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 439E921F8577 for <ietf@ietf.org>; Sun,  2 Dec 2012 15:50:09 -0800 (PST)
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 1TfJIV-00076B-U0; Sun, 02 Dec 2012 23:50:08 +0000
Date: Mon, 03 Dec 2012 08:50:06 +0900
Message-ID: <m2zk1wui8h.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Creating an IETF Working Group Draft
In-Reply-To: <50BBB940.1020302@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Dec 2012 23:50:13 -0000

> So it is ok to have bad ideas as I+D, possibly harmful for the Internet
> just to have a structured discussion?

and so that the chairs have the option of changing editorship to turn
them into good ideas.

randy

From randy@psg.com  Sun Dec  2 15:52:51 2012
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 13E6B21F887C for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMBxjdzuHtX8 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:52:50 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8E45821F8864 for <ietf@ietf.org>; Sun,  2 Dec 2012 15:52:50 -0800 (PST)
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 1TfJL0-00076Z-GV; Sun, 02 Dec 2012 23:52:42 +0000
Date: Mon, 03 Dec 2012 08:52:41 +0900
Message-ID: <m2y5hgui46.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Creating an IETF Working Group Draft
In-Reply-To: <50BBE5C3.7050802@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <6.2.5.6.2.20121202130842.0a8266e0@resistor.net> <50BBE5C3.7050802@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: SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Dec 2012 23:52:51 -0000

> I would prefer to have the I+D as non-wg item until we are sure that we
> are willing to support it as RFC.

i thought that was wglc.  but i am a dinosaur.

randy

From arturo.servin@gmail.com  Sun Dec  2 15:56:28 2012
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 C860F21F887C for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:56:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ymuXDZ4aNAA for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 15:56:28 -0800 (PST)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 47A9021F86CE for <ietf@ietf.org>; Sun,  2 Dec 2012 15:56:28 -0800 (PST)
Received: by mail-gh0-f172.google.com with SMTP id z22so347444ghb.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 15:56:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=jjoBbqdn4mHHuc5yPnUW4JjQOtDvNaudNG5k7C8KC/Q=; b=YGjhtrx65lhC3x5mQw1w8gpDv8mHhrCXAdwYFtRoUF9JE0WlEWepkJotAFBVwlhpbs WTI/6T5aKbLhkkLrbo+IhN5Cy1OkrHx3zDtgJifljRQQ0oCsIiEnCowp7Nb+uJUnsTyE VGf2pQ2g8Z+/yNAShZ90VLGAUxb7GZ//nYwy/qGol83CBdP1f5IBEP5MRVLJGQBh2Gae xgBVtWm0Wh7GO3LgQvOfHXEQHIp8tuikkQwbX9EhIsJtFqvNWBDoGkXjTgyGD1gFsV8n AMMZNQLo6V7gESTLj/hSpUzwW3pVffDMWz6h2L0At4WWldJnecB+teuJPa1/xDwXwOJD fyJg==
Received: by 10.236.161.233 with SMTP id w69mr8701292yhk.74.1354492587819; Sun, 02 Dec 2012 15:56:27 -0800 (PST)
Received: from [192.168.1.133] (r186-48-222-236.dialup.adsl.anteldata.net.uy. [186.48.222.236]) by mx.google.com with ESMTPS id u22sm11598712yhl.2.2012.12.02.15.56.25 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 15:56:26 -0800 (PST)
Message-ID: <50BBEAA7.3070600@gmail.com>
Date: Sun, 02 Dec 2012 21:56:23 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <m2zk1wui8h.wl%randy@psg.com>
In-Reply-To: <m2zk1wui8h.wl%randy@psg.com>
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, 02 Dec 2012 23:56:28 -0000

On 02/12/2012 21:50, Randy Bush wrote:
>> So it is ok to have bad ideas as I+D, possibly harmful for the Internet
>> just to have a structured discussion?
> and so that the chairs have the option of changing editorship to turn
> them into good ideas.
>
> randy
    That's is true. But I would prefer to accept a I+D as WG item until
we are sure that we are somehow committed to follow the path
described/proposed in the document. Accepting the document assuming that
chairs are going to turn bad ideas to good in my opinio is not good.

Regards
as

From arturo.servin@gmail.com  Sun Dec  2 16:05:06 2012
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 2F86421F88FF for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:05:05 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wEDsm8CTq5yF for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:05:04 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE2C21F8915 for <ietf@ietf.org>; Sun,  2 Dec 2012 16:04:59 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id r14so350208yen.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 16:04:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=AxDhQnShO7C4PXBCSbxTnUIly3VDd4LidwFPa4S5NAU=; b=J3pDWHGWXUQFi/wdcumjdmquuKkcKRur1DVGpYjOeHlqnqTmOqX/iX0rq98HGFoqDD ktUZyb9gQ6WR8LnxLDN46aI51s9EQNZjxu+aKywEkejLUwhOiTk1dE7fnb2P7AOtsrdu wk9S/C2JqmjqvfCYbJDScTwXknVYL4V1NbKuxfbohZHQ86yHxUyUtY9VLvpmgRmOF3Z2 bEg8/4uFt5Qpjt2vKGNRBp8bSR9EWLljb7R/5qDFXyiCmyM79AE8kxhFTARwo1hm8+3o 1T1N7FnWFuZ5ub7KN7CX88QSFFH3QZoKBEaUkYWdfVY/Bf38x6g/dq61uSE+eM8hE+Dz NLMQ==
Received: by 10.236.85.201 with SMTP id u49mr9033745yhe.6.1354493098966; Sun, 02 Dec 2012 16:04:58 -0800 (PST)
Received: from ?IPv6:2800:af:ba30:deec:7c45:a2c0:b751:de2? ([2800:af:ba30:deec:7c45:a2c0:b751:de2]) by mx.google.com with ESMTPS id t46sm11621158yhi.3.2012.12.02.16.04.56 (version=SSLv3 cipher=OTHER); Sun, 02 Dec 2012 16:04:58 -0800 (PST)
Message-ID: <50BBECA7.1010700@gmail.com>
Date: Sun, 02 Dec 2012 22:04:55 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <6.2.5.6.2.20121202130842.0a8266e0@resistor.net> <50BBE5C3.7050802@gmail.com> <m2y5hgui46.wl%randy@psg.com>
In-Reply-To: <m2y5hgui46.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 00:05:06 -0000

On 02/12/2012 21:52, Randy Bush wrote:
>> I would prefer to have the I+D as non-wg item until we are sure that we
>> are willing to support it as RFC.
> i thought that was wglc.  but i am a dinosaur.
>
> randy
    What I meant is that accepting the I+D as WG document clears the
path of the bad idea to become RFC somehow or at least to waste a lot of
time fighting against it.

    I have seen a lot of I+D that are discussed a lot and are never
accepted as WG items (even though the problem is in scope of the
charter) because it is a bad proposal according to consensus. Eventually
the idea dies. Which in my opinion is good (unless we accepted to
document why it is bad, but that is another history).

    Accepting an I+D as WG item just "because we need to discuss the
topic" or because of "a more structured discussion" would have brought a
lot of rejected ideas as WG documents.


Regards,
as

From randy@psg.com  Sun Dec  2 16:06:48 2012
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 45B4921F87EB for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:06:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NPHAXEJdGIzN for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:06:47 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 08C7921F87BC for <ietf@ietf.org>; Sun,  2 Dec 2012 16:06:40 -0800 (PST)
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 1TfJYQ-0007Br-SM; Mon, 03 Dec 2012 00:06:35 +0000
Date: Mon, 03 Dec 2012 09:06:33 +0900
Message-ID: <m2txs4uhh2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: Creating an IETF Working Group Draft
In-Reply-To: <50BBECA7.1010700@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <6.2.5.6.2.20121202130842.0a8266e0@resistor.net> <50BBE5C3.7050802@gmail.com> <m2y5hgui46.wl%randy@psg.com> <50BBECA7.1010700@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: SM <sm@resistor.net>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org, Adrian Farrel <adrian@olddog.co.uk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 00:06:48 -0000

> What I meant is that accepting the I+D as WG document clears the path
> of the bad idea to become RFC somehow or at least to waste a lot of
> time fighting against it.

we used to call that 'discussion' as opposed to ppt presentation.  and
discussion is what wgs were for, see other thread.

randy, who is way above his intended posting limit

From melinda.shore@gmail.com  Sun Dec  2 16:12:20 2012
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 EE01421F88FD for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:12:20 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avxT0-ts3ERX for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:12:20 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8567421F88F4 for <ietf@ietf.org>; Sun,  2 Dec 2012 16:12:20 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1472796pbc.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 16:12:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=DXXQC9qdGo9zNgg3og8NPcxVMxmamTVgNLSSoDGfzVE=; b=yBLaHEUQEqAS/jks1ogXrl4ytPBDu4ULoRMyb6nLEwB3BOtLMwFrF3G5Jlm5FAULlv CM/4NDXh4F0vWptWo9Esvpy3msZiexHB3oN3hhQot7wTrcQFdDJqWtvo+ZA8VLG8ASaJ hsZ419ifjFwguQVXD/Ny8XLjRXKE6OgGX3vVt2O6zhe4rZkpXTRtW1vAusOb2qtOg4sR W7KEgtd4LETa0jIO+AqIOWS/1qc7Veo6H6zpRPX83z0QwQVdW2TbCfI9JdhdgtSwlvIS KYRganPVlRQE3qO03PbV8iGYIWum9fIJokQF8LeUeDRLptOZChnWF3hvT+Z63MjLdA3f cprg==
Received: by 10.68.132.34 with SMTP id or2mr24681294pbb.133.1354493538547; Sun, 02 Dec 2012 16:12:18 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id pv8sm7000814pbc.26.2012.12.02.16.12.16 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 16:12:17 -0800 (PST)
Message-ID: <50BBEE5F.3060906@gmail.com>
Date: Sun, 02 Dec 2012 15:12:15 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@gmail.com>
In-Reply-To: <50BBEAA7.3070600@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: Mon, 03 Dec 2012 00:12:21 -0000

On 12/2/12 2:56 PM, Arturo Servin wrote:
>     That's is true. But I would prefer to accept a I+D as WG item until
> we are sure that we are somehow committed to follow the path
> described/proposed in the document. Accepting the document assuming that
> chairs are going to turn bad ideas to good in my opinio is not good.

A couple of points:  the main one is that I have absolutely no
idea where this "bad ideas" thing is coming from, because there
are a number of reasons why we wouldn't want to publish a document
other than that it contains bad ideas and I'm going to question
both your association of not-working-group drafts with bad ideas
and working group drafts with good ones ('cause, seriously, folks ...).

But the other one is that you seem to be using "working group
draft" and "working group item (deliverable?)" interchageably, and
I really don't think they're the same thing at all.

Melinda


From aservin@lacnic.net  Sun Dec  2 16:24:16 2012
Return-Path: <aservin@lacnic.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 AF33321F8908 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.406
X-Spam-Level: 
X-Spam-Status: No, score=-0.406 tagged_above=-999 required=5 tests=[AWL=-1.316, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_DIALUP=0.862, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aJ--5o6fInyW for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:24:16 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 23AD921F8903 for <ietf@ietf.org>; Sun,  2 Dec 2012 16:24:16 -0800 (PST)
Received: from [192.168.1.133] (r186-48-222-236.dialup.adsl.anteldata.net.uy [186.48.222.236]) by mail.lacnic.net.uy (Postfix) with ESMTP id 6E8ED30843C; Sun,  2 Dec 2012 22:24:02 -0200 (UYST)
Message-ID: <50BBF121.8050400@lacnic.net>
Date: Sun, 02 Dec 2012 22:24:01 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@gmail.com> <50BBEE5F.3060906@gmail.com>
In-Reply-To: <50BBEE5F.3060906@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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, 03 Dec 2012 00:24:16 -0000

	Perhaps I did, but I am talking about Working Group Drafts

"1.1.  What is a Working Group Draft?

   Documents under development in the IETF community are distributed as
   Internet Drafts (I-D).  Working groups use this mechanism for
   producing their official output, per Section 7.2 of [RFC2418] and
   Section 8.3 of [RFC4677] and [ID-Info].  The convention for
   identifying an I-D formally under the ownership of a working group is
   by the inclusion of "ietf" in the second field of the I-D filename
   and the working group name in the third field, per Section 7 of
   [ID-Guidelines].  That is:

                        draft-ietf-<wgname>-...

"

	from draft-crocker-id-adoption

/as

On 02/12/2012 22:12, Melinda Shore wrote:
> But the other one is that you seem to be using "working group
> draft" and "working group item (deliverable?)" interchageably, and
> I really don't think they're the same thing at all.

From melinda.shore@gmail.com  Sun Dec  2 16:26:27 2012
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 5A7E221F8876 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:26:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eu3tWFxsGd5G for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 16:26:26 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id DC9BC21F85D1 for <ietf@ietf.org>; Sun,  2 Dec 2012 16:26:26 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so1398150pad.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 16:26:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nVbqti6//8lH8aByWwN88+TYTY8DUZEBtc8jaFlle7E=; b=imB59g03vC7E1O0epXAZIRX+QR0FUd71+d7iZ2AN+o+MomWLXNsm35TV3029+ar+Ig aQ7PMN0BjNJi06m7hxVenOGszL9UHDjaCQWdpSKQeoj4QRMjzUaofpgvc4/vpybAgrI0 zIHSSFzlVurca5yTV2tH8GOi1eBXw/rRrliaQB+aH3hF8Rz+ntngJ7dG6M5kW/vNt37u SrN2dL/mP+mFKtR48rjRHuR+SDRGVZoftzcKaWjWub2A3KSdZ2DD32i3ezrPlr4DFhmr Ld7VKgLaJ6hT+R2PnKuX6LFhsQ6TncbyH9sBUEDx3BOGYHdScnVz7UFKu22Pvcv2/ayH gw7w==
Received: by 10.68.137.234 with SMTP id ql10mr24375768pbb.158.1354494386660; Sun, 02 Dec 2012 16:26:26 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id ty4sm7009411pbc.57.2012.12.02.16.26.24 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 16:26:26 -0800 (PST)
Message-ID: <50BBF1AF.3030408@gmail.com>
Date: Sun, 02 Dec 2012 15:26:23 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@gmail.com> <50BBEE5F.3060906@gmail.com> <50BBF121.8050400@lacnic.net>
In-Reply-To: <50BBF121.8050400@lacnic.net>
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: Mon, 03 Dec 2012 00:26:27 -0000

On 12/2/12 3:24 PM, Arturo Servin wrote:
> 	Perhaps I did, but I am talking about Working Group Drafts

So am I.  I have no problem with a working group adopting a document
as a tool in the development of their deliverables, either as a place
to keep notes or as a document with a separate editor to eventually
be folded into a deliverable.  You'll note that the text you cite
does not restrict working group drafts to deliverables.

Melinda



From joelja@bogus.com  Sun Dec  2 18:27:08 2012
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 8C3AA21F896C for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 18:27:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.31
X-Spam-Level: 
X-Spam-Status: No, score=-102.31 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eX1JD48KCnIF for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 18:27:08 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id DE77D21F896B for <ietf@ietf.org>; Sun,  2 Dec 2012 18:27:07 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-207-206-4.hsd1.ca.comcast.net [98.207.206.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qB32R6HJ012448 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 3 Dec 2012 02:27:07 GMT (envelope-from joelja@bogus.com)
Message-ID: <50BBC0A4.3090305@bogus.com>
Date: Sun, 02 Dec 2012 12:57:08 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20121128 Thunderbird/18.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com>
In-Reply-To: <50BBA8C3.6040100@network-heretics.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]); Mon, 03 Dec 2012 02:27:07 +0000 (UTC)
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, 03 Dec 2012 02:27:08 -0000

On 12/2/12 11:15 AM, Keith Moore wrote:
> On 12/02/2012 01:46 PM, joel jaeggli wrote:
>> We have non-native english speakers and remote participants both 
>> working at a disadvantage to follow the discussion in the room. We 
>> should make it harder for them by removing the pretext that the 
>> discussion is structured around material that they can review and 
>> follow along on? I don't think that's even remotely helpful.
>
> In general, the purpose of those meetings is *discussion*, not 
> presentation.   I'm all for exploring better ways to facilitate 
> *discussion* among the diversity of IETF meeting attendees.  But our 
> experience with use of previously-prepared PowerPoint presentations to 
> facilitate *discussion* shows that use of that tool, in that way and 
> for that purpose, is a miserable failure.
Since you and I attend a significant number of the same working groups 
we should have some shared experience, but I'm going to flat out 
disagree. It's possbile that we had completely different experiences in 
the same meetings, but I do firmly believe that slides are facilitatiing 
both the speakers coverage of the problems they're trying to address, 
and the participants dicussion of the problems enumerated.

As a chair one should be engaged in some editorial oversight of the 
contents of slides.
> Of course I'd encourage speakers to make available for download 
> summaries of the material to be discussed in advance of the meeting, 
> for the benefit of non-native English speakers and others. PowerPoint 
> (or better, PDF of material prepared in PowerPoint) seems like a 
> reasonable format for that.
>
the reflexive reference to a particular tool isn't a helpful point of 
this discussion imho... It doesn't matter to me what format the slides 
are in so long as these serve to structure the conversation. Powerpoint 
is a tool (and one I don't use), there are plently of others that can 
serve to get the point across.  If a state diagram benefits from 
animation, then you should pick the appropiate tool. whichever tool it 
is the assumption is that the output will be projected and potentially 
displayed remotely. The import conceit, imho is that the material is 
prepared prior to the meeting so that it can be distributed (and this 
may be the point of actual contention for you).
> I also think it would be quite helpful to arrange for the topics 
> discussed and points raised in the discussion to be displayed in the 
> room in real time, as they are typed.   This would provide non-native 
> speakers with visuals similar to what they see now with PowerPoint, 
> but without the undesirable side-effect of coercing discussion time 
> into presentations.   This would also reinforce the need for a 
> minute-taker and help to keep the minute-takers honest.
This is a meeting workflow change, I can think of several ways to 
approach it. as with note taking, jabber scribing and managing remote 
participants it requires someone to do the work (though it may overlap 
with one of the other activities).
>
> (I doubt that PowerPoint is the best tool for this purpose, since it 
> would be highly desirable to convey the same information, at the same 
> time, to remote participants.)
>
it would be helpful abstract the tool dicussion away from particular 
applications, at the heart of the problem, is not which text/media 
formatting application is used.
> Keith
>


From moore@network-heretics.com  Sun Dec  2 19:02:59 2012
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 9163E21F896B for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 19:02:59 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPt6pyvg9iOw for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 19:02:58 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 91E2321F8905 for <ietf@ietf.org>; Sun,  2 Dec 2012 19:02:58 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C65AC2103E; Sun,  2 Dec 2012 22:02:57 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Sun, 02 Dec 2012 22:02:57 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=VuYHPSkSLlduGwlGw9Wl6F Mc/bc=; b=AZ59JYDes/y2OexEUpI2FJHbJF8Qeb2m2qI2IJ3yWNCT+vKjj8GQ3o TFOnwiKojdfYsU0R/5E+SbNljhqk+jC3iiRN3J0Xq/hzru5VR2xwDmmkHSg5spbV UNYrVvPp21iO+y6PDK8xgYITbGs28jW7TIGnIIOdtqUDSWvVzjA9A=
X-Sasl-enc: VIGQ9DoG0WMGhvTYBwyT2JwiRTog9gdKKpgS1cVmx0Ss 1354503776
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A9CB4827CD; Sun,  2 Dec 2012 22:02:56 -0500 (EST)
Message-ID: <50BC1658.7070901@network-heretics.com>
Date: Sun, 02 Dec 2012 22:02:48 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com>
In-Reply-To: <50BBC0A4.3090305@bogus.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: Mon, 03 Dec 2012 03:02:59 -0000

On 12/02/2012 03:57 PM, joel jaeggli wrote:
> On 12/2/12 11:15 AM, Keith Moore wrote:
>> On 12/02/2012 01:46 PM, joel jaeggli wrote:
>>> We have non-native english speakers and remote participants both 
>>> working at a disadvantage to follow the discussion in the room. We 
>>> should make it harder for them by removing the pretext that the 
>>> discussion is structured around material that they can review and 
>>> follow along on? I don't think that's even remotely helpful.
>>
>> In general, the purpose of those meetings is *discussion*, not 
>> presentation.   I'm all for exploring better ways to facilitate 
>> *discussion* among the diversity of IETF meeting attendees.  But our 
>> experience with use of previously-prepared PowerPoint presentations 
>> to facilitate *discussion* shows that use of that tool, in that way 
>> and for that purpose, is a miserable failure.
> Since you and I attend a significant number of the same working groups 
> we should have some shared experience, but I'm going to flat out 
> disagree. It's possbile that we had completely different experiences 
> in the same meetings, but I do firmly believe that slides are 
> facilitatiing both the speakers coverage of the problems they're 
> trying to address, and the participants dicussion of the problems 
> enumerated.
>
I saw very little productive discussion happening in Atlanta in the vast 
majority of working group meetings which I attended.  True, there were 
times when people queued up at the microphones.  (though that's actually 
a pretty inefficient way to have a discussion.) The vast majority of the 
time in nearly every session I attended was occupied by speakers 
standing at the front of room in front of a screen of mostly text, and a 
room full of people who were mostly not paying attention.

(and when people did try to discuss things, the chairs kept trying to 
cut the lines short because they had more PRESENTATIONS to get 
through....arrgh.)

>> Of course I'd encourage speakers to make available for download 
>> summaries of the material to be discussed in advance of the meeting, 
>> for the benefit of non-native English speakers and others. PowerPoint 
>> (or better, PDF of material prepared in PowerPoint) seems like a 
>> reasonable format for that.
>>
> the reflexive reference to a particular tool isn't a helpful point of 
> this discussion imho...

I think people understand that I'm not talking specifically about a 
particular tool for creating presentations.   It doesn't matter which 
tool you use, the problem is the notion that meeting time should consist 
primarily (or even significantly) of presenters standing in front of a 
screen on which mostly-text is being displayed, and the content of what 
is being said closely corresponds to what is on the screen.   A related 
problem is that people are paying attention to the words on the screen 
which is distracting them from what is actually being said.    And 
because the bitrate of the information being presented is low, people 
tend to not pay much attention anyway, and they tend do things that 
further distract from the meeting.

"PowerPoint" is just a convenient one-word shorthand for this 
phenomenon.   The problem isn't the specific tool that's being used, but 
the phenomenon almost inherently comes with use of PowerPoint or any of 
several similar tools.   And everybody has seen it happen and associates 
it with the word PowerPoint.

What matters is that a lot of meeting time is being wasted by filling it 
up with presentations, and by trying to have discussions using media and 
techniques and habits that are better suited for presentations.  (though 
the idea that PowerPoint and similar tools even help to facilitate good 
presentations is itself pretty dubious.)

>> I also think it would be quite helpful to arrange for the topics 
>> discussed and points raised in the discussion to be displayed in the 
>> room in real time, as they are typed.   This would provide non-native 
>> speakers with visuals similar to what they see now with PowerPoint, 
>> but without the undesirable side-effect of coercing discussion time 
>> into presentations.   This would also reinforce the need for a 
>> minute-taker and help to keep the minute-takers honest.
> This is a meeting workflow change, I can think of several ways to 
> approach it. as with note taking, jabber scribing and managing remote 
> participants it requires someone to do the work (though it may overlap 
> with one of the other activities).

Of course.  And I'm not set on a particular approach; I just want to 
facilitate more effective discussion (and in a way that tries to 
accommodate those who have trouble understanding the speakers).

But I do suspect that somehow the job of typing something that appears 
immediately on the screen, might be more appealing than the job of 
taking minutes or being a Jabber scribe.   If one person typing could do 
an adequate job of all of the above, that would be nice, as we'd need 
fewer volunteers.
>>
>> (I doubt that PowerPoint is the best tool for this purpose, since it 
>> would be highly desirable to convey the same information, at the same 
>> time, to remote participants.)
>>
> it would be helpful abstract the tool dicussion away from particular 
> applications, at the heart of the problem, is not which text/media 
> formatting application is used.
I don't think you can completely divorce the discussion from mention of 
these tools and still have a useful discussion.

Keith


From joelja@bogus.com  Sun Dec  2 19:49:24 2012
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 0B11421F8920 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 19:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.413
X-Spam-Level: 
X-Spam-Status: No, score=-102.413 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zE4-njU4R8SQ for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 19:49:23 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 088C421F8967 for <ietf@ietf.org>; Sun,  2 Dec 2012 19:49:22 -0800 (PST)
Received: from Joels-MacBook-Pro.local (c-98-207-206-4.hsd1.ca.comcast.net [98.207.206.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qB33nKNL013359 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 3 Dec 2012 03:49:21 GMT (envelope-from joelja@bogus.com)
Message-ID: <50BC213B.8060602@bogus.com>
Date: Sun, 02 Dec 2012 19:49:15 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics! .com>
In-Reply-To: <50BC1658.7070901@network-heretics.com>
X-Enigmail-Version: 1.4.6
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, 03 Dec 2012 03:49:21 +0000 (UTC)
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, 03 Dec 2012 03:49:24 -0000

On 12/2/12 19:02 , Keith Moore wrote:\
>>
> I saw very little productive discussion happening in Atlanta in the vast
> majority of working group meetings which I attended.  True, there were
> times when people queued up at the microphones.  (though that's actually
> a pretty inefficient way to have a discussion.) 

I'm unclear on how we'd carry on a discussion without a floor management
discipline.

Shouting?

If the case is that you're in a room with 200 people and you have people
listening remotely, then fundamentally more discipline is required then
if you have 20 people around a table.


From randy@psg.com  Sun Dec  2 19:52:31 2012
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 B6E6A21F86D2 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 19:52:31 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dFehYlLBNhqA for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 19:52:31 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB9521F86A2 for <ietf@ietf.org>; Sun,  2 Dec 2012 19:52:31 -0800 (PST)
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 1TfN54-0008Ao-2b; Mon, 03 Dec 2012 03:52:30 +0000
Date: Mon, 03 Dec 2012 12:52:28 +0900
Message-ID: <m2sj7niygz.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel jaeggli <joelja@bogus.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
In-Reply-To: <50BC213B.8060602@bogus.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com> <50BC213B.8060602@bogus.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: 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: Mon, 03 Dec 2012 03:52:31 -0000

> I'm unclear on how we'd carry on a discussion without a floor management
> discipline.

i know it's a leap, but maybe presume people are adults

From moore@network-heretics.com  Sun Dec  2 20:04:57 2012
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 089C221F8993 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:04:57 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hX6El4DvK3RY for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:04:56 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 1E97921F899B for <ietf@ietf.org>; Sun,  2 Dec 2012 20:04:56 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 91F1B2105F; Sun,  2 Dec 2012 23:04:55 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Sun, 02 Dec 2012 23:04:55 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=/V0cDfPiXvqzOxtd5xyHCI KkaGM=; b=WQphFDSX6JoskoPcamew/cxQsobZjacKvmgkW6RI9sXRVhHLr0eRRf IwmmICvnuMJbhnWkYoj/z04MukY+E71ZQz2ecoMFwY9Txx4KVWX6hITCMceuLRxF 5FW0FTSlJCveA0OgnCbR+axTgHZ51pTX5tjqKbj/Op4MuAy71awbQ=
X-Sasl-enc: OlE8l3HHAPwgZ2RFUPQQE4B1NHlskhQTt6ZwQXwJQYrx 1354507495
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id BD63648264D; Sun,  2 Dec 2012 23:04:54 -0500 (EST)
Message-ID: <50BC24DE.4040409@network-heretics.com>
Date: Sun, 02 Dec 2012 23:04:46 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Joel jaeggli <joelja@bogus.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics! .com> <50BC213B.8060602@bogus .com>
In-Reply-To: <50BC213B.8060602@bogus.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: Mon, 03 Dec 2012 04:04:57 -0000

On 12/02/2012 10:49 PM, Joel jaeggli wrote:
> On 12/2/12 19:02 , Keith Moore wrote:\
>> I saw very little productive discussion happening in Atlanta in the vast
>> majority of working group meetings which I attended.  True, there were
>> times when people queued up at the microphones.  (though that's actually
>> a pretty inefficient way to have a discussion.)
> I'm unclear on how we'd carry on a discussion without a floor management
> discipline.

We used to do it fairly well in IETF, in the days before the rooms had 
(or needed) microphones.  We did it successfully in days when IETF 
meetings were about as big as they are now.

Unfortunately, when the microphones were introduced, chairs started 
insisting that people queue at the microphones in order to say 
something, and this helped considerably to degrade discussion.

> Shouting?

The discussions could indeed get lively.  But participants generally 
respected each other.   On the rare occasions when they didn't, the 
chairs could (and did) intervene.
> If the case is that you're in a room with 200 people and you have people
> listening remotely, then fundamentally more discipline is required then
> if you have 20 people around a table.

Perhaps.  But if the meeting rooms weren't such good places to sleep, 
read email, randomly browse, play Solitare, whatever, perhaps they 
wouldn't be so filled with mostly-inactive attendees.

Keith


From joelja@bogus.com  Sun Dec  2 20:05:32 2012
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 7A87921F899B for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:05:32 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYK0TkpGrcbp for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:05:32 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 509DD21F899E for <ietf@ietf.org>; Sun,  2 Dec 2012 20:05:30 -0800 (PST)
Received: from Joels-MacBook-Pro.local (c-98-207-206-4.hsd1.ca.comcast.net [98.207.206.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qB345T18013596 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 3 Dec 2012 04:05:29 GMT (envelope-from joelja@bogus.com)
Message-ID: <50BC2504.1000206@bogus.com>
Date: Sun, 02 Dec 2012 20:05:24 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com> <50BC213B.8060602@bogus.com> <m2sj7niygz.wl%randy@psg.com>
In-Reply-To: <m2sj7niygz.wl%randy@psg.com>
X-Enigmail-Version: 1.4.6
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, 03 Dec 2012 04:05:30 +0000 (UTC)
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: Mon, 03 Dec 2012 04:05:32 -0000

On 12/2/12 19:52 , Randy Bush wrote:
>> I'm unclear on how we'd carry on a discussion without a floor management
>> discipline.
> 
> i know it's a leap, but maybe presume people are adults

and that everyone of them has a microphone




From randy@psg.com  Sun Dec  2 20:08:55 2012
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 8C4C921F899B for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 tagged_above=-999 required=5 tests=[AWL=0.052,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AmC4Hn1TJ1Bo for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:08:55 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 358C521F8992 for <ietf@ietf.org>; Sun,  2 Dec 2012 20:08:55 -0800 (PST)
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 1TfNKv-0008D5-CF; Mon, 03 Dec 2012 04:08:53 +0000
Date: Mon, 03 Dec 2012 13:08:52 +0900
Message-ID: <m2pq2rixpn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joel jaeggli <joelja@bogus.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
In-Reply-To: <50BC2504.1000206@bogus.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com> <50BC213B.8060602@bogus.com> <m2sj7niygz.wl%randy@psg.com> <50BC2504.1000206@bogus.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: 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: Mon, 03 Dec 2012 04:08:55 -0000

>>> I'm unclear on how we'd carry on a discussion without a floor
>>> management discipline.
>> i know it's a leap, but maybe presume people are adults
> and that everyone of them has a microphone

so we build our meetings around the fears, will someone speak
unacceptably, will someone appeal, will someone pass gas in 
class?  next we can have the tsa screen people at the door.

can we please play the upside.  there is a high road, let's
take it.

randy

From joelja@bogus.com  Sun Dec  2 20:33:34 2012
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 5E12821F89E3 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:33:34 -0800 (PST)
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.111, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bx5uWagY175a for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:33:34 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id EBDE421F89D7 for <ietf@ietf.org>; Sun,  2 Dec 2012 20:33:33 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-207-206-4.hsd1.ca.comcast.net [98.207.206.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qB34XWhc013925 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 3 Dec 2012 04:33:33 GMT (envelope-from joelja@bogus.com)
Message-ID: <50BC2B96.9040702@bogus.com>
Date: Sun, 02 Dec 2012 20:33:26 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20121128 Thunderbird/18.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com> <50BC213B.8060602@bogus.com> <m2sj7niygz.wl%randy@psg.com> <50BC2504.1000206@bogus.com> <m2pq2rixpn.wl%randy@psg.com>
In-Reply-To: <m2pq2rixpn.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 03 Dec 2012 04:33:33 +0000 (UTC)
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: Mon, 03 Dec 2012 04:33:34 -0000

On 12/2/12 8:08 PM, Randy Bush wrote:
>>>> I'm unclear on how we'd carry on a discussion without a floor
>>>> management discipline.
>>> i know it's a leap, but maybe presume people are adults
>> and that everyone of them has a microphone
> so we build our meetings around the fears, will someone speak
> unacceptably, will someone appeal, will someone pass gas in
> class?  next we can have the tsa screen people at the door.
currently we don't do it that way (hand everyone a mic) because it's 
infeasable.  Oddly I have none of the above fears.
> can we please play the upside.  there is a high road, let's
> take it.

I thought I was. Mic discipline exists because, we have big rooms that require sound reinforcement, and remote participants and a recording. So if you're concerned about being heard, or hearing or the historical record, you should be in favor of it in general

I've never noted the existence of a mic line at an IETF precluding 
statements which I find disagreeable, so I have trouble imagining them 
being used for that purpose.
> randy
>


From dhc@dcrocker.net  Sun Dec  2 20:54:45 2012
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 F394021F89EA for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:54:44 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HGamjbjeY9ai for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 20:54:44 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F312821F89E9 for <ietf@ietf.org>; Sun,  2 Dec 2012 20:54:43 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB34shoT017724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 2 Dec 2012 20:54:43 -0800
Message-ID: <50BC308B.8030005@dcrocker.net>
Date: Sun, 02 Dec 2012 20:54:35 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com> <50BC213B.8060602@bogus.com> <m2sj7niygz.wl%randy@psg.com> <50BC2504.1000206@bogus.com> <m2pq2rixpn.wl%randy@psg.com>
In-Reply-To: <m2pq2rixpn.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Sun, 02 Dec 2012 20:54:43 -0800 (PST)
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, 03 Dec 2012 04:54:45 -0000

On 12/2/2012 8:08 PM, Randy Bush wrote:
>>>> I'm unclear on how we'd carry on a discussion without a floor
>>>> management discipline.
...
>>> people are adults
...
> ...there is a high road, let's
> take it.


A series of glib catch-phrases are certain not to facilitate meaningful 
discussion, any more than does treating the use of particular 
technologies as a problem.

The question put forward was serious and relevant.  It warrants serious 
response.

Microphones introduce a consideration to the process, but then so does 
the 'presence' of remote participants.  It's not that difficult to 
manage the room productively given these realities.  Chairs do it all 
the time.

The discipline they impose varies, but, for example, a per-participant, 
random interpretation in the style of "do whatever you think is the 
adult behavior" isn't one of the choices.  They /manage/ the process.

In very small scale, with a few active participants who share the same 
meeting management model, the chairs have a particularly easy time.  But 
let's not confuse that with an amorphous "act like adults" reference.

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From melinda.shore@gmail.com  Sun Dec  2 21:03:19 2012
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 84FA621F89F5 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 21:03:19 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v3hdBDJ5RMS8 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 21:03:17 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 84EAB21F86FA for <ietf@ietf.org>; Sun,  2 Dec 2012 21:03:17 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1596315pbc.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 21:03:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=JQq8QgiN6TzP34MisO2gAP9h77h088YnX6EXwS1dp4s=; b=P63773u0P3Hhnhv3OEOp+xiGYG32v1YKt5Xc4aOqdGWb5jK1ymsgDkZh8NpnlWIanW xbZdd2DgW3ovpfLpRkAtcdYGk3jxtiu3nYCWBCq3uNIBYwBPdyhEnSkKCBQB6fT5YpXz Wzdn0dYT8ZDLNoJb/mkrsHDQFmwLekWBhjTMDsqdMZO87SJE8CPUzdby+nb8As8RhAwN 4stCoB+xEXnQj4AY5EIBAoJWh6AY54lx7kDo6NUn5R8RvAkLBk76M3v/PiEPppq/mRLY c40inE0hllYXHRVuZnOpYwPamV9TTUXxaIb8TQS5uaLg19y3S+96UX1+KqlkE2wCNWrK 0VnQ==
Received: by 10.68.137.41 with SMTP id qf9mr26006329pbb.103.1354510997338; Sun, 02 Dec 2012 21:03:17 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id j8sm7375206paz.30.2012.12.02.21.03.14 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 21:03:16 -0800 (PST)
Message-ID: <50BC3290.3020903@gmail.com>
Date: Sun, 02 Dec 2012 20:03:12 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com> <50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com> <50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com> <50BC213B.8060602@bogus.com> <m2sj7niygz.wl%randy@psg.com> <50BC2504.1000206@bogus.com> <m2pq2rixpn.wl%randy@psg.com> <50BC308B.8030005@dcrocker.net>
In-Reply-To: <50BC308B.8030005@dcrocker.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: Mon, 03 Dec 2012 05:03:19 -0000

On 12/2/12 7:54 PM, Dave Crocker wrote:
> Microphones introduce a consideration to the process, but then so does
> the 'presence' of remote participants.  It's not that difficult to
> manage the room productively given these realities.  Chairs do it all
> the time.

This is off the topic at hand but I do think it's worthwhile
to circle back to one point in particular that Keith made, and
that's that it's kind of weird that we cut off discussion so
that we can proceed to the next presentation.  It's done all
the time (I've done it, myself) and while there's definitely
a sense that we need to cover the material we've said we're
going to cover in a meeting, why does breadth take priority
over depth?

Melinda



From duerst@it.aoyama.ac.jp  Sun Dec  2 22:01:10 2012
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 8C30121F8990 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 22:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.239
X-Spam-Level: 
X-Spam-Status: No, score=-100.239 tagged_above=-999 required=5 tests=[AWL=-0.449, 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+jcHK3j7HCF for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 22:01:09 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 4778A21F890F for <ietf@ietf.org>; Sun,  2 Dec 2012 22:01:08 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id qB3612uJ020688 for <ietf@ietf.org>; Mon, 3 Dec 2012 15:01:03 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 60ad_72e7_d1818b42_3d0e_11e2_a962_001d096c566a; Mon, 03 Dec 2012 15:01:02 +0900
Received: from [IPv6:::1] ([133.2.210.1]:42944) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S161B1E8> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 3 Dec 2012 15:01:03 +0900
Message-ID: <50BC401C.8020101@it.aoyama.ac.jp>
Date: Mon, 03 Dec 2012 15:01: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: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
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: Mon, 03 Dec 2012 06:01:10 -0000

One of the advantages of a standards organization such as the IETF is 
cross-concern review. For the IETF, one very strong cross-concern is 
security. Another one (also for my personally) is internationalization. 
Another, more vague one, is general architecture. Early running code is 
very often (not always) characterized by the fact that such 
cross-concerns are actively or passively ignored.

I had a look at your draft and checked for "security" and 
"internationalization", but only found the former, and not not in a 
discussion about how this proposal would make sure that cross-concerns 
are adequately addressed.

Regards,   Martin.

On 2012/12/02 5:12, Stephen Farrell wrote:
>
> Hi all,
>
> I've just posted an idea [1] for a small process improvement.
> If it doesn't seem crazy I'll try pursue it with the IESG as
> an RFC 3933 process experiment. If its universally hated then
> that's fine, it can die.
>
> The IESG have seen (more-or-less) this already but it hasn't
> be discussed, so this is just a proposal from me and has no
> "official" status whatsoever.
>
> Any comments, suggestions or better ideas are very welcome.
> Feel free to send me comments off list for now, or on this
> list I guess. If there's loads of email (always possible,
> this being a process thing;-) we can move to some other list.
>
> Regards,
> Stephen.
>
> [1] http://tools.ietf.org/id/draft-farrell-ft
>

From sm@resistor.net  Sun Dec  2 22:06:31 2012
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 37D7F21F8475 for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 22:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.646
X-Spam-Level: 
X-Spam-Status: No, score=-102.646 tagged_above=-999 required=5 tests=[AWL=-0.047, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wn2etjwp6W2K for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 22:06:30 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A97C21F847F for <ietf@ietf.org>; Sun,  2 Dec 2012 22:06:30 -0800 (PST)
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 qB366KRb009696; Sun, 2 Dec 2012 22:06:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354514785; bh=K4U8p5vNKXJ/6gin/anxRTqg9Q6XJL0W051uTb7lCAQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dfRuz9Z8FXptLQYiHtWqwgAZZRvy00IHUtYRyGNY77TyQcdghrmoZ0z+QX81b4Qmk AZdd2HX4gJmSNVW4QOPz2D0Wsx7ynz+/CIdXf4UvX4PpihK5+DmCVsPuFHSjBUXF3j 3JfzCMIVBRjOycIN+BVXPaVA9v2OADlAWu8kVQuM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354514785; i=@resistor.net; bh=K4U8p5vNKXJ/6gin/anxRTqg9Q6XJL0W051uTb7lCAQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CdNPga2KKT4bKxVDxXlUrSFmLGbRKC2k9Lz9+iAaA1YxLXDzUujwkFYiRhrRXNqHM H63rTz7KTH1hIulf3MWu80y3MSOk7VEFTX/F56aDQCa1OcHL/pUWjkKOaZwDSErzbV /y51LvUZNfF8tKgd56fhTgOG6wdT7vNCsUAI8AGE=
Message-Id: <6.2.5.6.2.20121202214413.0ad32bf0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 02 Dec 2012 22:05:06 -0800
To: Arturo Servin <arturo.servin@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Creating an IETF Working Group Draft (off-topic)
In-Reply-To: <50BBEAA7.3070600@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com> <m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@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: Mon, 03 Dec 2012 06:06:31 -0000

Hi Arturo,
At 15:56 02-12-2012, Arturo Servin wrote:
>described/proposed in the document. Accepting the document assuming that
>chairs are going to turn bad ideas to good in my opinio is not good.

My guess is that you will be approached to chair a WG at some point.

Regards,
-sm 


From stbryant@cisco.com  Mon Dec  3 00:07:01 2012
Return-Path: <stbryant@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 5B3B221F86C7 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 00:07:01 -0800 (PST)
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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgF8VfGS9KGA for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 00:07:00 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 1676621F86CE for <ietf@ietf.org>; Mon,  3 Dec 2012 00:06:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1600; q=dns/txt; s=iport; t=1354522020; x=1355731620; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WiPd+Y78MZccAwRjpqBnxdQ6Ua/bIomCN3gqBoSCecU=; b=fxRhCUDJ10r30CdnKq/KU4XPzzR1VraRIyUVGAXDHYcS5gKn66ybmq6i bUa32+nFx8gKWN6dVUdSCO6WCyztzhsAD3hk0YkR1bb17MZwaZwv/7fJ0 n40m4y66ECq6m57qW43onh97/fnp4MTPv6g61mt0VMzCiEE80h2IwJljz 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAGVdvFCQ/khR/2dsb2JhbABEwAAWc4IeAQEBBDhAARALGAkWDwkDAgECAUUGDQEHAQGIDAy+L4xAC4Q2A5YBgRyET4pcgnKBbA
X-IronPort-AV: E=McAfee;i="5400,1158,6914"; a="10096588"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 03 Dec 2012 08:06:58 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id qB386w69019964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Dec 2012 08:06:58 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id qB386tuR024358; Mon, 3 Dec 2012 08:06:56 GMT
Message-ID: <50BC5DA0.2030506@cisco.com>
Date: Mon, 03 Dec 2012 08:06:56 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 08:07:01 -0000

On 01/12/2012 20:12, Stephen Farrell wrote:
> Hi all,
>
> I've just posted an idea [1] for a small process improvement.
> If it doesn't seem crazy I'll try pursue it with the IESG as
> an RFC 3933 process experiment. If its universally hated then
> that's fine, it can die.
>
> The IESG have seen (more-or-less) this already but it hasn't
> be discussed, so this is just a proposal from me and has no
> "official" status whatsoever.
>
> Any comments, suggestions or better ideas are very welcome.
> Feel free to send me comments off list for now, or on this
> list I guess. If there's loads of email (always possible,
> this being a process thing;-) we can move to some other list.
>
> Regards,
> Stephen.
>
> [1] http://tools.ietf.org/id/draft-farrell-ft
>
I find this a worrying proposal.

In the just-in-time world that we live in, too much of the review is 
already tail driven. Reducing the time that people have to notice that a 
doc is up for final review and then clear enough time in their calendar 
against a myriad of other tasks makes it more likely that the quality of 
review will diminish and hence the quality of our documents will diminish.

I would hate for us to act like an SDO that regards publication 
milestones as crucial and ship the draft regardless of the state of the 
technical design.

I would also note that sometimes it just takes time during review to 
mull over the full implications of the design and to surface the issues. 
With the current scheme if you miss a problem in WGLC, you can raise it 
during IETF LC.

- Stewart





From tjc@ecs.soton.ac.uk  Mon Dec  3 01:49:50 2012
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 D3AAB21F88D4 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 01:49:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lu1I3EvuBKHh for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 01:49:49 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [152.78.68.146]) by ietfa.amsl.com (Postfix) with ESMTP id 8579621F88CD for <ietf@ietf.org>; Mon,  3 Dec 2012 01:49:49 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qB1JEe6F028935 for <ietf@ietf.org>; Sat, 1 Dec 2012 19:14:45 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk qB1JEe6F028935
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1354389353; bh=SULZ8sj0zfHqG+jqza6Nn8DBO3s=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=dG0MTeJ+WoWSt/s/oKaRQexyngfJeTsgySRBquOvAqf1SwBwFYOeYnFSwwE2roiHh szWi4iB2hb2GE76s+dRlkVIpQDEkArnPSL51XplcbjAL7zQdP7vXaset+wGqXAuIvE HdD3a22YMyXxZRyyJ8IONfzK2UalWelKqLSG304c=
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 oB0JDk0430627028vs ret-id none; Sat, 01 Dec 2012 19:14:45 +0000
Received: from [192.168.1.102] (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 qB1JCPEb012985 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 1 Dec 2012 19:12:26 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: "IETF work is done on the mailing lists"
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <6.2.5.6.2.20121129082748.09ea5878@resistor.net>
Date: Sat, 1 Dec 2012 19:12:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|f1fc2d5a44060084ca5e9de593eb013coB0JDk03tjc|ecs.soton.ac.uk|672570B6-AE5B-4C50-BB6A-EE8DCDEC6B44@ecs.soton.ac.uk>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <20121127231404.GC1941@verdi> <m2mwy26iud.wl%randy@psg.com> <50B63CA3.4040907@cisco.com> <D0EF612C-DFF5-4D16-BA96-F65204CC1CB2@apnic.net> <50B72DF9.9030901@cisco.com> <968CBBD9-D7B1-4F27-A596-81A0EDE9C504@neustar.biz> <6.2.5.6.2.20121129082748.09ea5878@resistor.net> <672570B6-AE5B-4C50-BB6A-EE8DCDEC6B44@ecs.soton.ac.uk>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=oB0JDk043062702800; tid=oB0JDk0430627028vs; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: qB1JEe6F028935
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 09:49:51 -0000

On 29 Nov 2012, at 18:51, SM <sm@resistor.net> wrote:

> Hi Ed,
> At 06:54 29-11-2012, Edward Lewis wrote:
>> Earlier in the thread I saw that someone expressed dismay that BOFs =
seem to be WG's that have already been meeting in secret.  I agree with =
that.  At the last meeting in Atlanta, I filled in sessions with BOFs =
and found that the ones I chose seemed as if they were already on the =
way to a predetermined solution.  Only one had a presentation trying to =
set up the problem to be solved, others just had detailed talks on draft =
solutions.  In one there was a complaint that the mail list wasn't very =
active - not a WG, a BOF!  Not very engaging.

The complaint about a quiet mail list may have been a comment I made at =
the mdnsext BoF.  The reason for that is that the guidance we have for =
holding a BoF (RFC 5434) recommends forming a public mail list a couple =
of months before the IETF meeting where the BoF is planned and to have =
substantive list discussion in advance of the BoF, which should help =
form a solid problem statement and draft charter.

>  Extensions of the Bonjour Protocol Suite (mdnsext) BoF
>=20
> The agenda [5] mentions "Goals of the BoF" with a link.  I don't =
recall whether any proposed solution was discussed.

Some views on potential solutions were made at the mic in the BoF.  But =
the draft that was presented was a requirements draft, not a solutions =
one. I'll speak to Ralph soon about moving this forward.=20

>> Bringing in baked work because there are multiple independent and =
non-interoperable solutions is what the IETF is all about.  Bringing in =
a baked specification just to get a stamp on it is not.

The former is a driver for mdnsext, i.e. a number of vendors producing =
potentially non-interoperable mDNS proxying solutions. I don't see a =
problem with the latter, especially if it documents something useful =
that is otherwise opaque.

Certainly some WG lists have a lot of traffic, and on lists it's easy =
for a small number of vocal people to dominate the discussion, which is =
less likely to happen face to face (where people have to queue and take =
turns).

Tim=

From stephen.farrell@cs.tcd.ie  Mon Dec  3 02:49:25 2012
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 7D45D21F85E2 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 02:49:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yELDfGmGNv59 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 02:49:24 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 704F721F8581 for <ietf@ietf.org>; Mon,  3 Dec 2012 02:49:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 85A00BE36; Mon,  3 Dec 2012 10:49:00 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grbrK-Y0PoUv; Mon,  3 Dec 2012 10:48:57 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 471FEBE50; Mon,  3 Dec 2012 10:48:57 +0000 (GMT)
Message-ID: <50BC839A.1070503@cs.tcd.ie>
Date: Mon, 03 Dec 2012 10:48:58 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com>
In-Reply-To: <50BC5DA0.2030506@cisco.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Mon, 03 Dec 2012 10:49:25 -0000

Hi Stewart,

On 12/03/2012 08:06 AM, Stewart Bryant wrote:
> On 01/12/2012 20:12, Stephen Farrell wrote:
>> Hi all,
>>
>> I've just posted an idea [1] for a small process improvement.
>> If it doesn't seem crazy I'll try pursue it with the IESG as
>> an RFC 3933 process experiment. If its universally hated then
>> that's fine, it can die.
>>
>> The IESG have seen (more-or-less) this already but it hasn't
>> be discussed, so this is just a proposal from me and has no
>> "official" status whatsoever.
>>
>> Any comments, suggestions or better ideas are very welcome.
>> Feel free to send me comments off list for now, or on this
>> list I guess. If there's loads of email (always possible,
>> this being a process thing;-) we can move to some other list.
>>
>> Regards,
>> Stephen.
>>
>> [1] http://tools.ietf.org/id/draft-farrell-ft
>>
> I find this a worrying proposal.

I hope I can convince you that its not.

> In the just-in-time world that we live in, too much of the review is
> already tail driven. 

I don't believe this touches on that at all (see below).

> Reducing the time that people have to notice that a
> doc is up for final review and then clear enough time in their calendar
> against a myriad of other tasks makes it more likely that the quality of
> review will diminish and hence the quality of our documents will diminish.

But this doesn't do that for IETF LC at all! Everyone
not involved in the WG gets just the same notice as now.

I guess I did assume that the chairs would not try surprise the
WG with this. I can add text along those lines.

So I don't think there's any bad effect here really.

> I would hate for us to act like an SDO that regards publication
> milestones as crucial and ship the draft regardless of the state of the
> technical design.

That's not at all what's proposed. Drafts still get worked
on in the WG and go through the same IESG evaluation and
IETF LC.

What I hope is different is that drafts taking this optional
approach are higher quality, being based on running code.

> I would also note that sometimes it just takes time during review to
> mull over the full implications of the design and to surface the issues.
> With the current scheme if you miss a problem in WGLC, you can raise it
> during IETF LC.

Sure. And everyone is free to keep using that of course. To try
this process you need to get the WG chairs and have a happy AD
and running code. Really, I don't see that this would lower the
quality of our output (considering some of the drafts we do see
that may never have running code), rather the opposite. And the
main danger here I suspect is that this never gets used.

Does that make you less worried?

Cheers,
S.


> 
> - Stewart
> 
> 
> 
> 
> 

From brian.e.carpenter@gmail.com  Mon Dec  3 03:02:27 2012
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 E1AC321F8690 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 03:02:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.541
X-Spam-Level: 
X-Spam-Status: No, score=-101.541 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LmODXhkeTR16 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 03:02:21 -0800 (PST)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id E90ED21F846B for <ietf@ietf.org>; Mon,  3 Dec 2012 03:02:20 -0800 (PST)
Received: by mail-wi0-f170.google.com with SMTP id hq7so1108366wib.1 for <ietf@ietf.org>; Mon, 03 Dec 2012 03:02:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Vgnygb91ydW2ILzXdoN+qH98OPjhIM7hUpRcIOynVH8=; b=ZYDyCgd49BZwrByZkZg7RKnT2VaG3utAmqtix0KMbbZYxgJCpuw/UreJjvGH6Z7m9k XHtPzHzYKuFT4sfTlu4+8xdB6EkgSNszRgj7Mv2VoQsOohs0OaofaA1saa/6qWm2wwbn B/yWQ/lKtenWUn+G/Jx9FlZZjo9utVeyi+1fC+afkVk7ER1hZFgEF3al9NBfOoHSIG4I Y7R94dpvBdHxLjouum+tevfKQKj3oVfEA/KrXJzDicjaagVOh8PDOpmm3oW8gvt9Tuhu PoapkZXndWNn7kOiPih00OMHv1QUyH3Tewnz0+EGusgv84uqSX7Cvme7ntPopFvsRAnz fuiw==
Received: by 10.181.11.234 with SMTP id el10mr8771456wid.7.1354532539769; Mon, 03 Dec 2012 03:02:19 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-71.as13285.net. [2.102.218.71]) by mx.google.com with ESMTPS id w5sm12016552wiz.10.2012.12.03.03.02.17 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 03:02:18 -0800 (PST)
Message-ID: <50BC86B7.1010706@gmail.com>
Date: Mon, 03 Dec 2012 11:02:15 +0000
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: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp>
In-Reply-To: <50BC401C.8020101@it.aoyama.ac.jp>
Content-Type: text/plain; charset=UTF-8
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: Mon, 03 Dec 2012 11:02:28 -0000

On 03/12/2012 06:01, Martin J. D=C3=BCrst wrote:
> One of the advantages of a standards organization such as the IETF is
> cross-concern review. For the IETF, one very strong cross-concern is
> security. Another one (also for my personally) is internationalization.=

> Another, more vague one, is general architecture. Early running code is=

> very often (not always) characterized by the fact that such
> cross-concerns are actively or passively ignored.

An excellent point. The fact that a hack works, and can be implemented,
does not alter the fact that it's a hack. This is the sort of thing that
cross-area review is supposed to look for. As a gen-art reviewer, I am
sometimes surprised by what gets through to Last Call in the regular
process - if the whole review process is squeezed down to a couple
of weeks, we will definitely miss cross-area issues.

Encouraging running code is a Good Thing. Publishing sloppy specification=
s
is a Bad Thing.

The Interop show network used to be a Very Good Thing. We've lost that,
though I was delighted to see some actual running code at Bits-n-Bytes
in Atlanta. More please. Maybe a prize for Best Demo?

   Brian

>=20
> I had a look at your draft and checked for "security" and
> "internationalization", but only found the former, and not not in a
> discussion about how this proposal would make sure that cross-concerns
> are adequately addressed.
>=20
> Regards,   Martin.
>=20
> On 2012/12/02 5:12, Stephen Farrell wrote:
>>
>> Hi all,
>>
>> I've just posted an idea [1] for a small process improvement.
>> If it doesn't seem crazy I'll try pursue it with the IESG as
>> an RFC 3933 process experiment. If its universally hated then
>> that's fine, it can die.
>>
>> The IESG have seen (more-or-less) this already but it hasn't
>> be discussed, so this is just a proposal from me and has no
>> "official" status whatsoever.
>>
>> Any comments, suggestions or better ideas are very welcome.
>> Feel free to send me comments off list for now, or on this
>> list I guess. If there's loads of email (always possible,
>> this being a process thing;-) we can move to some other list.
>>
>> Regards,
>> Stephen.
>>
>> [1] http://tools.ietf.org/id/draft-farrell-ft
>>
>=20


From brian.e.carpenter@gmail.com  Mon Dec  3 03:15:34 2012
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 C500F21F85D7 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 03:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.68
X-Spam-Level: 
X-Spam-Status: No, score=-101.68 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBxdqjffMXVY for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 03:15:31 -0800 (PST)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by ietfa.amsl.com (Postfix) with ESMTP id 87BBF21F86D1 for <ietf@ietf.org>; Mon,  3 Dec 2012 03:15:31 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id hm9so1100160wib.13 for <ietf@ietf.org>; Mon, 03 Dec 2012 03:15:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=sdYUU59wiDUbXKvcQXnVs9p9bgHpXIZ0YnxLKfQS6nI=; b=j2JZOrMjLjCkx7BTRBR/JvU86WT8WQXPONxuDdOnCnOy4olNF/XVe5t9geI9su5Xi+ 5/hMwRQeokue0NWsQuFQutrPHHqjJSm0iDRCl6+PAv9rfpKb61mkZEZjm+1oxnwcBDXO C0FaOuD5/2+YaNlwZxx54YZfk6AygGzUSMZXaIyIZCr7EXjw0GuIcAXmQonwisLkru7W ha+VUwuPLLhiy87OEvnIB+O00soSSN4JtUSZpT84sffcOKouHiTTibIt1fdXIHW6KhLi 0KJniQphp4Yp801rfWPrDdpEBBoIt/hRAvt55XZjS75GGJm7sX8r3fqOQE7F1m1j99Lz XMJA==
Received: by 10.216.227.197 with SMTP id d47mr1827089weq.83.1354533330392; Mon, 03 Dec 2012 03:15:30 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-71.as13285.net. [2.102.218.71]) by mx.google.com with ESMTPS id u6sm12077868wif.2.2012.12.03.03.15.28 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 03:15:29 -0800 (PST)
Message-ID: <50BC89D3.8030701@gmail.com>
Date: Mon, 03 Dec 2012 11:15:31 +0000
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: Arturo Servin <aservin@lacnic.net>
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>	<01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk>	<50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com>	<50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com>	<m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@gmail.com>	<50BBEE5F.3060906@gmail.com> <50BBF121.8050400@lacnic.net>
In-Reply-To: <50BBF121.8050400@lacnic.net>
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: Mon, 03 Dec 2012 11:15:34 -0000

On 03/12/2012 00:24, Arturo Servin wrote:
> 	Perhaps I did, but I am talking about Working Group Drafts
> 
> "1.1.  What is a Working Group Draft?
> 
>    Documents under development in the IETF community are distributed as
>    Internet Drafts (I-D).  

Melinda and/or Randy have said what I want to say, but as a factual
clarification to the draft, the above statement is only part of the
truth. Documents under development in the IRTF are distributed as
I-Ds, and so are documents about random subjects by random people,
especially those intended as independent submissions to the RFC Editor.
So a more complete statement is

 Documents under development inside or outside the IETF community are
 distributed as Internet Drafts (I-D).

    Brian


From stephen.farrell@cs.tcd.ie  Mon Dec  3 03:29:21 2012
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 D2AA121F8686 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 03:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.433
X-Spam-Level: 
X-Spam-Status: No, score=-101.433 tagged_above=-999 required=5 tests=[AWL=-1.134, BAYES_00=-2.599, MANGLED_EMAIL=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xa9gA0tglZTz for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 03:29:21 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 01B7221F85E2 for <ietf@ietf.org>; Mon,  3 Dec 2012 03:29:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 99878BE38; Mon,  3 Dec 2012 11:28:49 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m+VS1WeQXeDB; Mon,  3 Dec 2012 11:28:48 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 447FFBDCC; Mon,  3 Dec 2012 11:28:48 +0000 (GMT)
Message-ID: <50BC8CF1.8020700@cs.tcd.ie>
Date: Mon, 03 Dec 2012 11:28:49 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com>
In-Reply-To: <50BC86B7.1010706@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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, 03 Dec 2012 11:29:21 -0000

On 12/03/2012 11:02 AM, Brian E Carpenter wrote:
> On 03/12/2012 06:01, Martin J. Dürst wrote:
>> One of the advantages of a standards organization such as the IETF is
>> cross-concern review. For the IETF, one very strong cross-concern is
>> security. Another one (also for my personally) is internationalization.
>> Another, more vague one, is general architecture. Early running code is
>> very often (not always) characterized by the fact that such
>> cross-concerns are actively or passively ignored.

(Odd, I've not seen Martin's mail yet.)

> An excellent point. The fact that a hack works, and can be implemented,
> does not alter the fact that it's a hack. This is the sort of thing that
> cross-area review is supposed to look for. As a gen-art reviewer, I am
> sometimes surprised by what gets through to Last Call in the regular
> process - if the whole review process is squeezed down to a couple
> of weeks, we will definitely miss cross-area issues.

Fair enough. Those reviews (at least secdir ones) are supposed to
be done during IETF LC, but that doesn't always happen and I'm not
sure if the same timing applies to 'em all. I've added this:

        The timers associated with fast-track processing do increase the
        burden on cross-area review teams.  At present such reviews are
        supposed to be done during IETF LC, but some useful reviews are
        not received until after the end of IETF LC.  As is currently
        the case, the responsible AD and IESG will have to deal with
        such reviews as they are received.  A part of the experiment
        here will be to see if fast-track processing significantly
        impacts on these reviews.

> Encouraging running code is a Good Thing. Publishing sloppy specifications
> is a Bad Thing.

Sure. I guess I'd hope that we push back on sloppy specs as
usual, but that the running code might make that less likely,
or at least more likely to be just editorial.

Cheers,
S.

> 
> The Interop show network used to be a Very Good Thing. We've lost that,
> though I was delighted to see some actual running code at Bits-n-Bytes
> in Atlanta. More please. Maybe a prize for Best Demo?
> 
>    Brian
> 
>>
>> I had a look at your draft and checked for "security" and
>> "internationalization", but only found the former, and not not in a
>> discussion about how this proposal would make sure that cross-concerns
>> are adequately addressed.
>>
>> Regards,   Martin.
>>
>> On 2012/12/02 5:12, Stephen Farrell wrote:
>>>
>>> Hi all,
>>>
>>> I've just posted an idea [1] for a small process improvement.
>>> If it doesn't seem crazy I'll try pursue it with the IESG as
>>> an RFC 3933 process experiment. If its universally hated then
>>> that's fine, it can die.
>>>
>>> The IESG have seen (more-or-less) this already but it hasn't
>>> be discussed, so this is just a proposal from me and has no
>>> "official" status whatsoever.
>>>
>>> Any comments, suggestions or better ideas are very welcome.
>>> Feel free to send me comments off list for now, or on this
>>> list I guess. If there's loads of email (always possible,
>>> this being a process thing;-) we can move to some other list.
>>>
>>> Regards,
>>> Stephen.
>>>
>>> [1] http://tools.ietf.org/id/draft-farrell-ft
>>>
>>
> 
> 
> 

From john-ietf@jck.com  Mon Dec  3 04:30:04 2012
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 5474121F86D3 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 04:30:04 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aULt8gWB7Dc4 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 04:30:03 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id AB1DF21F8704 for <ietf@ietf.org>; Mon,  3 Dec 2012 04:30:03 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TfV9s-0000yk-L0; Mon, 03 Dec 2012 07:30:00 -0500
Date: Mon, 03 Dec 2012 07:29:55 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
Message-ID: <F7593F537812C4E15A63563F@JcK-HP8200.jck.com>
In-Reply-To: <50BC8CF1.8020700@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp>	<50BC86B7.1010706@gmail.com> <50BC8CF1.8020700@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-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, 03 Dec 2012 12:30:04 -0000

--On Monday, December 03, 2012 11:28 +0000 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>> Encouraging running code is a Good Thing. Publishing sloppy
>> specifications is a Bad Thing.
> 
> Sure. I guess I'd hope that we push back on sloppy specs as
> usual, but that the running code might make that less likely,
> or at least more likely to be just editorial.

Stephen,

I agree with Brian, but want to reinforce thinking about this a
little differently and in a way that may draw several other
sub-threads together.  The IETF is functioning here as a
standards body, not an certification body for implementability.
Knowing that something can be implemented, and implemented at
production quality, has traditionally been an IETF hallmark (and
hence part of Dave Clark's slogan) relative to other bodies who
have standardized the un-implementable.  IMO, when we approve
something as a Proposed Standard, it suggests that we have
evaluated and approved it along three quite separate dimensions:

	(1) Utility of the idea as something that should be
	implemented (or at least as a decent and reasonable way
	to do something)
	
	(2) Quality of the protocol and whether the
	specification adequately describes it.
	
	(3) Whether the specification can be implemented

Failures are possible on any of the three.  It is possible for a
well-specified and implementable idea to be utterly useless.  It
is possible to have a useful and well-designed protocol, with
implementations by insiders, to be so badly described that it is
unlikely that anyone else could figure out how to implement it.
It is, as Brian pointed out in his recent note, possibly to have
a hack-level implementation and/or one that doesn't work in the
edge cases.

Using any of those three in a way that enables shortcuts around
the other two puts us at risk or creating bad standards.  Even a
few bad standards could be used to hold the IETF up to ridicule
in ways that would weaken everything else that we do for a long
time... and the fact that we saw them as the result of a process
experience would be no protection at all.  Worse from the
standpoint of a speed-up procedure, someone's discovering a
problem after a hasty IESG approval could easily lead to an
appeal on the grounds that the process used did not allow for
adequate review, a result that would cost far more time than the
difference between the current and proposed procedure.

As others have pointed out, there are lots of other ways to
speed things up, most of which fall within the discretion of
individual WGs, ADs, and the IESG without any changes at all.
At least a few of them would involve "changes" back to what RFC
2026 already specifies, including treating Proposed Standards as
Proposed Standards, and eliminating, e.g., days or weeks or
post-IETF-Last-Call AD nitpicking over text in favor of
practicing the intent of the "no known technical defects" rule
of 2026 and letting the RFC Editor do their job.  But "you claim
to have done consideration 3, therefore you get to shortcut
considerations 1 and 2" should not be one of them.

best,
   john


From stephen.farrell@cs.tcd.ie  Mon Dec  3 05:43:10 2012
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 BF82421F8596 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.526
X-Spam-Level: 
X-Spam-Status: No, score=-102.526 tagged_above=-999 required=5 tests=[AWL=0.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wp5ZjS4QFZ8i for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:43:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id DDEA621F84C1 for <ietf@ietf.org>; Mon,  3 Dec 2012 05:43:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 31841BE3C; Mon,  3 Dec 2012 13:42:48 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eVdbql1GbptE; Mon,  3 Dec 2012 13:42:47 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 64809BE38; Mon,  3 Dec 2012 13:42:47 +0000 (GMT)
Message-ID: <50BCAC58.2050802@cs.tcd.ie>
Date: Mon, 03 Dec 2012 13:42:48 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp>	<50BC86B7.1010706@gmail.com> <50BC8CF1.8020700@cs.tcd.ie> <F7593F537812C4E15A63563F@JcK-HP8200.jck.com>
In-Reply-To: <F7593F537812C4E15A63563F@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Mon, 03 Dec 2012 13:43:10 -0000

Hi John,

On 12/03/2012 12:29 PM, John C Klensin wrote:
> 
> 
> --On Monday, December 03, 2012 11:28 +0000 Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
> 
>>> Encouraging running code is a Good Thing. Publishing sloppy
>>> specifications is a Bad Thing.
>>
>> Sure. I guess I'd hope that we push back on sloppy specs as
>> usual, but that the running code might make that less likely,
>> or at least more likely to be just editorial.
> 
> Stephen,
> 
> I agree with Brian, but want to reinforce thinking about this a
> little differently and in a way that may draw several other
> sub-threads together.  The IETF is functioning here as a
> standards body, not an certification body for implementability.
> Knowing that something can be implemented, and implemented at
> production quality, has traditionally been an IETF hallmark (and
> hence part of Dave Clark's slogan) relative to other bodies who
> have standardized the un-implementable.  IMO, when we approve
> something as a Proposed Standard, it suggests that we have
> evaluated and approved it along three quite separate dimensions:
> 
> 	(1) Utility of the idea as something that should be
> 	implemented (or at least as a decent and reasonable way
> 	to do something)
> 	
> 	(2) Quality of the protocol and whether the
> 	specification adequately describes it.
> 	
> 	(3) Whether the specification can be implemented
> 
> Failures are possible on any of the three.  It is possible for a
> well-specified and implementable idea to be utterly useless.  It
> is possible to have a useful and well-designed protocol, with
> implementations by insiders, to be so badly described that it is
> unlikely that anyone else could figure out how to implement it.
> It is, as Brian pointed out in his recent note, possibly to have
> a hack-level implementation and/or one that doesn't work in the
> edge cases.
> 
> Using any of those three in a way that enables shortcuts around
> the other two puts us at risk or creating bad standards.  Even a
> few bad standards could be used to hold the IETF up to ridicule
> in ways that would weaken everything else that we do for a long
> time... and the fact that we saw them as the result of a process
> experience would be no protection at all.  Worse from the
> standpoint of a speed-up procedure, someone's discovering a
> problem after a hasty IESG approval could easily lead to an
> appeal on the grounds that the process used did not allow for
> adequate review, a result that would cost far more time than the
> difference between the current and proposed procedure.
> 
> As others have pointed out, there are lots of other ways to
> speed things up, most of which fall within the discretion of
> individual WGs, ADs, and the IESG without any changes at all.
> At least a few of them would involve "changes" back to what RFC
> 2026 already specifies, including treating Proposed Standards as
> Proposed Standards, and eliminating, e.g., days or weeks or
> post-IETF-Last-Call AD nitpicking over text in favor of
> practicing the intent of the "no known technical defects" rule
> of 2026 and letting the RFC Editor do their job.  But "you claim
> to have done consideration 3, therefore you get to shortcut
> considerations 1 and 2" should not be one of them.

So are "hasty" and "shortcut" maybe pejorative ways of
saying that we cut out some of the "nitpicking" ;-)

Anyway, I'm not suggesting we forget #1 or #2 at all and
yes some or maybe all of what's proposed could already
be done but I think its notable that that is not being
done, so the proposal is a 3933 experiment to see if
putting some more emphasis on #3 will work or not.

So I do hope we run the experiment.

S.


> 
> best,
>    john
> 
> 
> 

From housley@vigilsec.com  Mon Dec  3 05:48:09 2012
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 833AB21F8583 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:48:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1v043wtWy58p for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:48:09 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 140F821F8581 for <ietf@ietf.org>; Mon,  3 Dec 2012 05:48:09 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D422A9A4003 for <ietf@ietf.org>; Mon,  3 Dec 2012 08:48:19 -0500 (EST)
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 StTKCd1R3L1F for <ietf@ietf.org>; Mon,  3 Dec 2012 08:48:03 -0500 (EST)
Received: from [192.168.10.65] (unknown [207.87.202.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 22AAE9A4001 for <ietf@ietf.org>; Mon,  3 Dec 2012 08:48:19 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: Creating an IETF Working Group Draft
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <50BC89D3.8030701@gmail.com>
Date: Mon, 3 Dec 2012 08:48:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F85F6C1-7CE7-4C14-9C98-7DA1F75AEA2C@vigilsec.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>	<01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk>	<50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com>	<50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com>	<m2zk1wui8h.wl%randy@psg.com> <50BBEAA7.3070600@gmail.com>	<50BBEE5F.3060906@gmail.com> <50BBF121.8050400@lacnic.net> <50BC89D3.8030701@gmail.com>
To: IETF <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: Mon, 03 Dec 2012 13:48:09 -0000

>> 	Perhaps I did, but I am talking about Working Group Drafts
>>=20
>> "1.1.  What is a Working Group Draft?
>>=20
>>   Documents under development in the IETF community are distributed =
as
>>   Internet Drafts (I-D). =20
>=20
> Melinda and/or Randy have said what I want to say, but as a factual
> clarification to the draft, the above statement is only part of the
> truth. Documents under development in the IRTF are distributed as
> I-Ds, and so are documents about random subjects by random people,
> especially those intended as independent submissions to the RFC =
Editor.
> So a more complete statement is
>=20
> Documents under development inside or outside the IETF community are
> distributed as Internet Drafts (I-D).

Even better:

The I-D repository is managed by the IETF Secretariat under the =
direction of the IESG, but the repository is used by the IETF, IRTF, =
IAB, and the broader Internet community to distribute documents.

Russ


From wesley.george@twcable.com  Mon Dec  3 05:53:25 2012
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 46C0221F8639 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.977
X-Spam-Level: 
X-Spam-Status: No, score=-0.977 tagged_above=-999 required=5 tests=[AWL=0.486,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m6uEU6-LbSDF for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:53:24 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id DF71721F85E2 for <ietf@ietf.org>; Mon,  3 Dec 2012 05:53:18 -0800 (PST)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,206,1355115600"; d="scan'208";a="481684907"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 03 Dec 2012 08:53:11 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Mon, 3 Dec 2012 08:53:18 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Melinda Shore <melinda.shore@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 3 Dec 2012 08:53:37 -0500
Subject: RE: Useful slide tex (was - Re: English spoken here)
Thread-Topic: Useful slide tex (was - Re: English spoken here)
Thread-Index: Ac3RE406ebxApz+4Rya/Vk14B4r99wAR7L2A
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338B42BE2@PRVPEXVS15.corp.twcable.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net>	<50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net>	<50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com>	<50BBA8C3.6040100@network-heretics.com> <50BBC0A4.3090305@bogus.com>	<50BC1658.7070901@network-heretics!.com> <50BC1658.7070901@network-heretics.com>	<50BC213B.8060602@bogus.com> <m2sj7niygz.wl%randy@psg.com>	<50BC2504.1000206@bogus.com> <m2pq2rixpn.wl%randy@psg.com>	<50BC308B.8030005@dcrocker.net> <50BC3290.3020903@gmail.com>
In-Reply-To: <50BC3290.3020903@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: Mon, 03 Dec 2012 13:53:25 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Melinda Shore
> it's kind of weird that we cut off discussion so that we can proceed to t=
he
> next presentation.  It's done all the time (I've done it, myself) and
> while there's definitely a sense that we need to cover the material
> we've said we're going to cover in a meeting, why does breadth take
> priority over depth?
>

[WEG] I think this requires making a judgment call between a ratholed discu=
ssion, or an impasse between two strongly held opinions vs. meaningful prog=
ress. Sometimes the former and the latter masquerade as each other and are =
therefore mishandled.

Again, comes down to how the meeting is structured - do you prioritize a se=
t of current drafts that need to have meaningful discussion, and accept the=
 fact that presentations on new work might lose their timeslots if discussi=
on runs long? I think that's an acceptable risk, especially since anyone wh=
o is technically on the agenda can build a presentation and have it be in t=
he proceedings so that people can review after the meeting. I know I had mo=
re than one meeting where there were many valuable presentations, and a lar=
ge number of them were added to the agenda with zero minutes allocated, so =
that they'd be ready if we had time to discuss them during the meeting once=
 the priority discussions were completed, but also so they'd be in the proc=
eedings when we didn't.

Wes George

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 wesley.george@twcable.com  Mon Dec  3 05:56:46 2012
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 E2E6C21F86A4 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:56:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.038
X-Spam-Level: 
X-Spam-Status: No, score=-1.038 tagged_above=-999 required=5 tests=[AWL=0.425,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EvHvh3cL9sZU for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:56:46 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id E2D2921F8668 for <ietf@ietf.org>; Mon,  3 Dec 2012 05:56:45 -0800 (PST)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,206,1355115600"; d="scan'208";a="481687074"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 03 Dec 2012 08:56:38 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Mon, 3 Dec 2012 08:56:45 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 3 Dec 2012 08:57:04 -0500
Subject: RE: Useful slide tex (was - Re: English spoken here)
Thread-Topic: Useful slide tex (was - Re: English spoken here)
Thread-Index: Ac3Qt8MtVtGe8KM+Rlu2iDenJc2azQAomf6w
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338B42BE8@PRVPEXVS15.corp.twcable.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com>	<59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net>	<50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com>
In-Reply-To: <50BB9888.8080906@network-heretics.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: Mon, 03 Dec 2012 13:56:47 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Keith Moore
  A different toolset, (e.g. pens and paper
> and overhead cameras coupled to projectors), would likely produce better
> results if that toolset did not encourage laziness in preparing
> materials to facilitate discussion.

[WEG] I don't know about anyone else here, but you do *not* want me to atte=
mpt to facilitate a discussion using freehand drawings and writing. My hand=
writing and drawing skill was bad before I discovered a keyboard, and years=
 of atrophy have made its usefulness approach zero as a meaningful method o=
f communication. You'd be better off with the aforementioned stone tablets =
and cuneiform in terms of understanding.

http://theoatmeal.com/blog/handwriting

And I echo what Dave said - quit blaming the tools and assuming that forcin=
g people to use tools they're not used to using will fix this. You have a v=
ery specific opinion of what an effective WG session should be like and wha=
t people should and should not be doing to facilitate such. Sounds like you=
 need to work with the EDU team to give a Sunday afternoon training session=
 entitled "how not to turn a WG session into a broadcast-only medium" possi=
bly with a section for WG chairs and a section for potential speakers.

Wes George

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 adrian@olddog.co.uk  Mon Dec  3 05:58:43 2012
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 DFC7021F86D2 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZlBZbbgyWcma for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 05:58:43 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 2335621F8668 for <ietf@ietf.org>; Mon,  3 Dec 2012 05:58:42 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id qB3DwfCi021968 for <ietf@ietf.org>; Mon, 3 Dec 2012 13:58:41 GMT
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 qB3DweIh021951 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Mon, 3 Dec 2012 13:58:41 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'IETF'" <ietf@ietf.org>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>	<01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk>	<50BBA236.9010603@dcrocker.net>	<50BBB79C.40106@gmail.com>	<50BBB862.8090209@gmail.com>	<50BBB940.1020302@gmail.com>	<m2zk1wui8h.wl%randy@psg.com>	<50BBEAA7.3070600@gmail.com>	<50BBEE5F.3060906@gmail.com>	<50BBF121.8050400@lacnic.net> <50BC89D3.8030701@gmail.com> <3F85F6C1-7CE7-4C14-9C98-7DA1F75AEA2C@vigilsec.com>
In-Reply-To: <3F85F6C1-7CE7-4C14-9C98-7DA1F75AEA2C@vigilsec.com>
Subject: RE: Creating an IETF Working Group Draft
Date: Mon, 3 Dec 2012 13:58:38 -0000
Message-ID: <01ca01cdd15e$4c055000$e40ff000$@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: AQJh66a/LNfCMvKWuQdcHBWtm9X2zgMwanJ9AUJICDYCfKkbwgIIvTmFAjnPdc4A2KcjfQGlx+YEAXxWZbQBCyqvBwJ6Y7zbAjKdulKWN71HEA==
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, 03 Dec 2012 13:58:44 -0000

We could certainly say this. It is a true statement.

However, the document is trying to talk about WG I-Ds, not to provide a general
description of everything the IETF and RFC Editor ever does.

Is it false to say:
   Documents under development in the IETF community are distributed as
   Internet Drafts (I-D).

In the context of this document, is it interesting to say:
  The I-D repository is managed by the IETF Secretariat under the direction of
the
  IESG, but the repository is used by the IETF, IRTF, IAB, and the broader
Internet
  community to distribute documents.

My answers are "No" and "No".

Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Russ
> Housley
> Sent: 03 December 2012 13:48
> To: IETF
> Subject: Re: Creating an IETF Working Group Draft
> 
> >> 	Perhaps I did, but I am talking about Working Group Drafts
> >>
> >> "1.1.  What is a Working Group Draft?
> >>
> >>   Documents under development in the IETF community are distributed as
> >>   Internet Drafts (I-D).
> >
> > Melinda and/or Randy have said what I want to say, but as a factual
> > clarification to the draft, the above statement is only part of the
> > truth. Documents under development in the IRTF are distributed as
> > I-Ds, and so are documents about random subjects by random people,
> > especially those intended as independent submissions to the RFC Editor.
> > So a more complete statement is
> >
> > Documents under development inside or outside the IETF community are
> > distributed as Internet Drafts (I-D).
> 
> Even better:
> 
> The I-D repository is managed by the IETF Secretariat under the direction of
the
> IESG, but the repository is used by the IETF, IRTF, IAB, and the broader
Internet
> community to distribute documents.
> 
> Russ


From dhc@dcrocker.net  Mon Dec  3 06:09:52 2012
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 35DFD21F8651 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:09:52 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r2EyRDPRI5wy for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:09:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C0B9221F8581 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:09:48 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB3E9ljt030776 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Dec 2012 06:09:47 -0800
Message-ID: <50BCB2A0.50305@dcrocker.net>
Date: Mon, 03 Dec 2012 06:09:36 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com>	<01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk>	<50BBA236.9010603@dcrocker.net>	<50BBB79C.40106@gmail.com>	<50BBB862.8090209@gmail.com>	<50BBB940.1020302@gmail.com>	<m2zk1wui8h.wl%randy@psg.com>	<50BBEAA7.3070600@gmail.com>	<50BBEE5F.3060906@gmail.com>	<50BBF121.8050400@lacnic.net> <50BC89D3.8030701@gmail.com> <3F85F6C1-7CE7-4C14-9C98-7DA1F75AEA2C@vigilsec.com> <01ca01cdd15e$4c055000$e40ff000$@olddog.co.uk>
In-Reply-To: <01ca01cdd15e$4c055000$e40ff000$@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.17]); Mon, 03 Dec 2012 06:09:48 -0800 (PST)
Cc: 'IETF' <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, 03 Dec 2012 14:09:52 -0000
X-List-Received-Date: Mon, 03 Dec 2012 14:09:52 -0000

On 12/3/2012 5:58 AM, Adrian Farrel wrote:
> We could certainly say this. It is a true statement.
>
> However, the document is trying to talk about WG I-Ds, not to provide a general
> description of everything the IETF and RFC Editor ever does.
...
> My answers are "No" and "No".

+1

The existing text was tailored to lay foundation for what comes next, 
not to provide a general introduction to I-Ds.  The suggested changes 
add unnecessary verbosity.  Anyone needing a 'complete' understanding of 
I-Ds can consult the offered citations.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba.mailing.lists@gmail.com  Mon Dec  3 06:25:18 2012
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 E8D8521F84E9 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:25:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zCXV0SBhL23y for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:25:18 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2692821F86C7 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:25:17 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so2462493lbk.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 06:25:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=y1P4fFCHkYTnNmHE0VdaEGI0jJkT+VviBqPKjxr4Dq4=; b=kC8C4ViXG+YF/zAgPKVD6tCfz39gYTq3Nly2Dzr74m/KA9lRNXj7pJgxbdbl7sn6hW XzkzRU9NgBfGgaU9OO9TNFWz1m+xmkNzVFpJSqHCTV6/v0u5M9KhKpsQPxqACecRxl+6 0mDMN6TjErMYnA0UOIg3fBQgnqOgJ/8vHu+o5F+5UgoqRpKarAI9CGMSk45TISxI+q0y B/Gg2+0JhAyGFpRE4NK0lVdsSEsvoR+xC0vFHa8lteFS0QaTCslaZimJ+firYXLRzEqz t84D9VgqwVKBnAIbASowULXO325aIXwk26vUO22srDEZnBKGUfQuJSB4ajIcu0fSTRW1 UlPA==
MIME-Version: 1.0
Received: by 10.112.32.101 with SMTP id h5mr4473540lbi.3.1354544716990; Mon, 03 Dec 2012 06:25:16 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Mon, 3 Dec 2012 06:25:16 -0800 (PST)
In-Reply-To: <50BC839A.1070503@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie>
Date: Mon, 3 Dec 2012 09:25:16 -0500
X-Google-Sender-Auth: Yrjr5buz-dpH_Ju81r9HE_Wm6NY
Message-ID: <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.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, 03 Dec 2012 14:25:19 -0000

> But this doesn't do that for IETF LC at all! Everyone
> not involved in the WG gets just the same notice as now.

This is true.

> What I hope is different is that drafts taking this optional
> approach are higher quality, being based on running code.

This is a stretch, and that *unprovable* assumption also bothers me.
We have lots of running code that implements specs badly.  We have
lots of running code that implements exactly what's in the spec and
misses everything that's missing (consider Martin's comment about
security and i18n).  We have lots of running code that doesn't
interoperate with other running code.  Your proposal specifically does
NOT require any testing of the running code, nor any interoperability
demonstrations (nor would I want it to).

Running code, when it's an organic part of the document development,
is undoubtedly a good thing -- it doesn't make everything right, but,
yes, it does do *some* spec validation and probably does help spec
quality.

But code that's written as part of a rote process, just to achieve
another check-box on the shepherd writeup and justify special handling
is not likely to provide any of those benefits.

Barry

From moore@network-heretics.com  Mon Dec  3 06:28:53 2012
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 BE75D21F85AA for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:28:53 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNQF+Ehjbbkt for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:28:52 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 595DE21F86C7 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:28:52 -0800 (PST)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B8CFB20A1A; Mon,  3 Dec 2012 09:28:50 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 03 Dec 2012 09:28:50 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=c7ipGyAwVLQhyCarlemHTJ O2VJk=; b=eqjJMz5lTv22MRptzu7zL6PwuStILPvv2J0pleILqTf4S8Vy2KzZyD Xt8PVYbiFcqdjdVC45TzhtdiZbT1+n6jFHKnGOju8PcgeJMwdqFS03fq5cNvgTn/ klACC/+bFk2h3BshIRuPuVPrhZXH1YGeuBWaayVPY+G5OLi1xAuyk=
X-Sasl-enc: 0IlgjkZW59WlO4JwQW7o5ODICLsxLH3rgqvhR4snNIn/ 1354544930
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9B98B8E0545; Mon,  3 Dec 2012 09:28:49 -0500 (EST)
Message-ID: <50BCB718.6000805@network-heretics.com>
Date: Mon, 03 Dec 2012 09:28:40 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net>	<50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <2671C6CDFBB59E47B64C10B3E0BD59230338B42BE8@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338B42BE8@PRVPEXVS15.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Dec 2012 14:28:54 -0000

On 12/03/2012 08:57 AM, George, Wes wrote:
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Keith Moore
>    A different toolset, (e.g. pens and paper
>> and overhead cameras coupled to projectors), would likely produce better
>> results if that toolset did not encourage laziness in preparing
>> materials to facilitate discussion.
> [WEG] I don't know about anyone else here, but you do *not* want me to attempt to facilitate a discussion using freehand drawings and writing. My handwriting and drawing skill was bad before I discovered a keyboard, and years of atrophy have made its usefulness approach zero as a meaningful method of communication. You'd be better off with the aforementioned stone tablets and cuneiform in terms of understanding.

Nothing would prevent you from preparing drawings in advance (even using 
PowerPoint, if you wished) and bringing them to the meeting on paper.   
And you could still annotate them with pens during the discussion if you 
found it useful to do so.   For that matter, nothing would prevent you 
from plugging your laptop into the projector, except perhaps the groans 
from the participants who might think you were about to start a 
presentation.

> And I echo what Dave said - quit blaming the tools and assuming that forcing people to use tools they're not used to using will fix this.
I've seen over and over again that the choice of tools significantly 
affects how people interact and the quality of their interaction, and 
I'm frankly amazed that others in IETF haven't seen this also.

And I don't really propose that people be forbidden to use PowerPoint.  
There will still be times when it's an appropriate tool, and 
hard-and-fast process rules can create as many problems as they solve.

But I do suggest that if someone is alloted a discussion session in an 
IETF WG meeting, that he should think twice before sitting down to use 
PowerPoint to crank out a deck of slides for it.

I also realize that people don't like to change the tools that they're 
accustomed to using.  But the whole point of this discussion is to 
encourage this community, and people in this community, to make better 
use of precious meeting time, have better discussions, produce better 
specifications, and to do so more quickly.  To the extent which our 
community's habits have contributed to poor use of meeting time and 
degraded the quality of discussion, it makes sense to reexamine those 
habits.  And use of PowerPoint is one of those habits which I believe 
should be reexamined.

> You have a very specific opinion of what an effective WG session should be like and what people should and should not be doing to facilitate such. Sounds like you need to work with the EDU team to give a Sunday afternoon training session entitled "how not to turn a WG session into a broadcast-only medium" possibly with a section for WG chairs and a section for potential speakers.
Years ago, my impression was that that Sunday training sessions were 
pretty much ignored by anyone experienced in the organization.  Is this 
still the case?

Keith



From stephen.farrell@cs.tcd.ie  Mon Dec  3 06:29:10 2012
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 93A0921F872C for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C7to3rUnpcSq for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:29:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id CA77E21F8705 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:29:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1BDE4BE38; Mon,  3 Dec 2012 14:28:47 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4oiZuepaFdI; Mon,  3 Dec 2012 14:28:46 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7D2E1BE33; Mon,  3 Dec 2012 14:28:46 +0000 (GMT)
Message-ID: <50BCB71F.4060205@cs.tcd.ie>
Date: Mon, 03 Dec 2012 14:28:47 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie> <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com>
In-Reply-To: <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.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, 03 Dec 2012 14:29:10 -0000

On 12/03/2012 02:25 PM, Barry Leiba wrote:
> Running code, when it's an organic part of the document development,
> is undoubtedly a good thing -- it doesn't make everything right, but,
> yes, it does do *some* spec validation and probably does help spec
> quality.

Fully agree. And this kind of experiment may encourage that
good thing some more. Or not. We'll not see if we don't try.
We may see if we do try. I think its worth trying. (That's
fairly obvious I guess:-)

S.

From barryleiba.mailing.lists@gmail.com  Mon Dec  3 06:36:25 2012
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 F0FEF21F843D for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9baZW0R4T+J6 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:36:25 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC5721F843A for <ietf@ietf.org>; Mon,  3 Dec 2012 06:36:24 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so2473856lbk.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 06:36:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8G1XLWhuJm+0z5UCj0XmyUwks8Tua6HhLepahGBRCcc=; b=wAPN5SyFfE1lujjpUcyh783SFEgZOq+5XUONwF/0DF2sqQKMnSj82OnVMGNa2CQE8x xHRu8kHU+S0+zmUCvFt+uwzNEL9/kCVSwJmfNLoYpkz7lPzGuiZZ57dGdxU1HJN6eo+4 2iMZaSKa91DFa+4CpJ0EV932aBbkbt8Zh67zUpToWHcml9vcNLywmc5jVF+4thX85vwD fcHgs5WoL+x6QdGTKqT31sRXIyz6LiZ7lXvCa1nvL3FVJ09dAtg9BUz2koZxCDHWPLvf 2ZrjKM3BOEwswlv2SHwUdJX+2S0iJvWwlkAWFXfNUXeXHMIv3K8bynddld4ZNrsvMnKM kybw==
MIME-Version: 1.0
Received: by 10.112.25.34 with SMTP id z2mr4362074lbf.125.1354545383959; Mon, 03 Dec 2012 06:36:23 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Mon, 3 Dec 2012 06:36:23 -0800 (PST)
In-Reply-To: <50BCB71F.4060205@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie> <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com> <50BCB71F.4060205@cs.tcd.ie>
Date: Mon, 3 Dec 2012 09:36:23 -0500
X-Google-Sender-Auth: V3dJheRGOHVLWvt0R3_t3wVpSDA
Message-ID: <CAC4RtVCg3w7Wtuau7dykC5QKCk9mg7Sz0UCeJ26VG1WB_ut7HQ@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.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, 03 Dec 2012 14:36:26 -0000

>> Running code, when it's an organic part of the document development,
>> is undoubtedly a good thing -- it doesn't make everything right, but,
>> yes, it does do *some* spec validation and probably does help spec
>> quality.
>
> Fully agree. And this kind of experiment may encourage that
> good thing some more. Or not. We'll not see if we don't try.
> We may see if we do try. I think its worth trying. (That's
> fairly obvious I guess:-)

Or we'll just waste time sticking in some side-process that isn't
necessary (all of this can already been done under current process,
with no experiment).  As I've said on the IESG list, I think this can
be far better done with an IESG statement that says that
implementation, testing, and deployment should be considered as we
(the community and the IESG) evaluate documents.  Then we just make
sure we facilitate the process instead of getting in the way of it.

That's a better promise than saying we'll cut out three or four weeks
of review time for a document that probably took 16 months to develop.

Barry

From elwynd@dial.pipex.com  Mon Dec  3 06:38:49 2012
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 3052021F8475 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:38:49 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hh+-5DJDHULY for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:38:48 -0800 (PST)
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 5BA3721F843A for <ietf@ietf.org>; Mon,  3 Dec 2012 06:38:48 -0800 (PST)
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 1TfXAK-0008Fr-FV; Mon, 03 Dec 2012 14:38:39 +0000
Subject: Re: Idea for a process experiment to reward running code...
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <50BC86B7.1010706@gmail.com>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Mon, 03 Dec 2012 14:38:45 +0000
Message-Id: <1354545525.11916.744.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
X-Spam-Score-a.painless.aa.net.uk: -4.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: Mon, 03 Dec 2012 14:38:49 -0000

Hi.

On Mon, 2012-12-03 at 11:02 +0000, Brian E Carpenter wrote:
> On 03/12/2012 06:01, Martin J. D=FCrst wrote:
> > One of the advantages of a standards organization such as the IETF is
> > cross-concern review. For the IETF, one very strong cross-concern is
> > security. Another one (also for my personally) is internationalization.
> > Another, more vague one, is general architecture. Early running code is
> > very often (not always) characterized by the fact that such
> > cross-concerns are actively or passively ignored.
>=20
> An excellent point. The fact that a hack works, and can be implemented,
> does not alter the fact that it's a hack. This is the sort of thing that
> cross-area review is supposed to look for. As a gen-art reviewer, I am
> sometimes surprised by what gets through to Last Call in the regular
> process - if the whole review process is squeezed down to a couple
> of weeks, we will definitely miss cross-area issues.

I also have the experience as a gen-art reviewer of seeing some pretty
awful pieces of work making through even to IESG review. =20

However, I don't think that a short last call cycle need necessarily
compromise cross-area review. There has always been the possibility for
authors or wg chairs to request a early gen-art review with a view to
checking out whether something is in good shape cross-area and for
non-specialists.  This facility is not much used (I think I have done 3
in 8 years on the gen-art team) but it is there, and I guess the team
could cope with a few more since it doesn't drastically alter the total
workload. So it would be entirely possible for a draft that might be
fast-tracked to get some early review.

Given that there is also open source code, reviewers have the chance to
take a look at that and see the degree of hackiness involved. =20

So I'd be for trying the experiment - and asking some cross-area
reviewers to take an early sniff.

Regards,
Elwyn

>=20
> Encouraging running code is a Good Thing. Publishing sloppy specification=
s
> is a Bad Thing.
>=20
> The Interop show network used to be a Very Good Thing. We've lost that,
> though I was delighted to see some actual running code at Bits-n-Bytes
> in Atlanta. More please. Maybe a prize for Best Demo?
>=20
>    Brian
>=20
> >=20
> > I had a look at your draft and checked for "security" and
> > "internationalization", but only found the former, and not not in a
> > discussion about how this proposal would make sure that cross-concerns
> > are adequately addressed.
> >=20
> > Regards,   Martin.
> >=20
> > On 2012/12/02 5:12, Stephen Farrell wrote:
> >>
> >> Hi all,
> >>
> >> I've just posted an idea [1] for a small process improvement.
> >> If it doesn't seem crazy I'll try pursue it with the IESG as
> >> an RFC 3933 process experiment. If its universally hated then
> >> that's fine, it can die.
> >>
> >> The IESG have seen (more-or-less) this already but it hasn't
> >> be discussed, so this is just a proposal from me and has no
> >> "official" status whatsoever.
> >>
> >> Any comments, suggestions or better ideas are very welcome.
> >> Feel free to send me comments off list for now, or on this
> >> list I guess. If there's loads of email (always possible,
> >> this being a process thing;-) we can move to some other list.
> >>
> >> Regards,
> >> Stephen.
> >>
> >> [1] http://tools.ietf.org/id/draft-farrell-ft
> >>
> >=20
>=20


From cabo@tzi.org  Mon Dec  3 06:40:57 2012
Return-Path: <cabo@tzi.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 6DA5E21F843D for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ORYxDwVIpUdi for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:40:56 -0800 (PST)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 46E7821F843A for <ietf@ietf.org>; Mon,  3 Dec 2012 06:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id qB3Edvr2004558; Mon, 3 Dec 2012 15:39:57 +0100 (CET)
Received: from [192.168.217.105] (p54893544.dip.t-dialin.net [84.137.53.68]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id E0CA924A; Mon,  3 Dec 2012 15:39:56 +0100 (CET)
Subject: Re: Idea for a process experiment to reward running code...
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com>
Date: Mon, 3 Dec 2012 15:39:55 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <011F7799-E011-4EC3-82C8-E7E6747C868C@tzi.org>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie> <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: Stewart Bryant <stbryant@cisco.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: Mon, 03 Dec 2012 14:40:57 -0000

On Dec 3, 2012, at 15:25, Barry Leiba <barryleiba@computer.org> wrote:

> But code that's written as part of a rote process, just to achieve
> another check-box on the shepherd writeup and justify special handling
> is not likely to provide any of those benefits.

+1.

As somebody who tends to think about security implications, the first =
thing that came to my mind when reading this was how this experiment =
would be used to game the system.  The results are so obvious I won't =
bother to write them down.

Society has a lot of experience with cases where, what used to be =
useful, but gameable indicators, are turned into measuring instruments =
with great effect.
Analogous to all these cases, I think the main effect of this proposal =
would be to destroy the remnant of usefulness that "running code" has in =
our current (living) process.

Gr=FC=DFe, Carsten


From elwynd@dial.pipex.com  Mon Dec  3 06:42:10 2012
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 EE87621F86C3 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:42:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VdHSXKNYlm0K for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:42:10 -0800 (PST)
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 769FB21F8475 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:42:10 -0800 (PST)
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 1TfXDf-0000We-5a; Mon, 03 Dec 2012 14:42:06 +0000
Subject: Re: Idea for a process experiment to reward running code...
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
In-Reply-To: <50BCB71F.4060205@cs.tcd.ie>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie> <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com> <50BCB71F.4060205@cs.tcd.ie>
Content-Type: text/plain
Date: Mon, 03 Dec 2012 14:42:13 +0000
Message-Id: <1354545733.11916.746.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: Barry Leiba <barryleiba@computer.org>, IETF-Discussion <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.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, 03 Dec 2012 14:42:11 -0000

On Mon, 2012-12-03 at 14:28 +0000, Stephen Farrell wrote:
> 
> On 12/03/2012 02:25 PM, Barry Leiba wrote:
> > Running code, when it's an organic part of the document development,
> > is undoubtedly a good thing -- it doesn't make everything right, but,
> > yes, it does do *some* spec validation and probably does help spec
> > quality.
> 
> Fully agree. And this kind of experiment may encourage that
> good thing some more. Or not. We'll not see if we don't try.
> We may see if we do try. I think its worth trying. (That's
> fairly obvious I guess:-)
> 
> S.

Another thing which it might help with is weeding out gratuitous
proliferation of options.

Regards,
Elwyn


From dhc@dcrocker.net  Mon Dec  3 06:45:59 2012
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 6BF8E21F8475 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:45:59 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1pCRjLDpHesO for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:45:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2C221F8444 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:45:58 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB3EjvjC031313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 3 Dec 2012 06:45:57 -0800
Message-ID: <50BCBB1A.5030400@dcrocker.net>
Date: Mon, 03 Dec 2012 06:45:46 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie> <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com> <50BCB71F.4060205@cs.tcd.ie> <CAC4RtVCg3w7Wtuau7dykC5QKCk9mg7Sz0UCeJ26VG1WB_ut7HQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCg3w7Wtuau7dykC5QKCk9mg7Sz0UCeJ26VG1WB_ut7HQ@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.17]); Mon, 03 Dec 2012 06:45:58 -0800 (PST)
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, 03 Dec 2012 14:45:59 -0000

On 12/3/2012 6:36 AM, Barry Leiba wrote:
> Or we'll just waste time sticking in some side-process that isn't
> necessary (all of this can already been done under current process,
> with no experiment).
...
> That's a better promise than saying we'll cut out three or four weeks
> of review time for a document that probably took 16 months to develop.


+10

d/

ps. given how creative human can be, in generating unintended 
consequences, an incentive to create running code /before/ going to 
Proposed could serve to /increase/ the barrier to standardization, by 
creating a perception that having running code is pragmatically required 
to get past the IESG.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba.mailing.lists@gmail.com  Mon Dec  3 06:50:42 2012
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 9F1DF21F8757 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:50:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWDrAZ1ZIXPm for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:50:42 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id AB5DC21F870D for <ietf@ietf.org>; Mon,  3 Dec 2012 06:50:41 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so2488282lbk.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 06:50:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=lNPncZIpytETQvg/nC6/cHWOyuag4NVfLw9pfIZ64yA=; b=q8k2ftSiCh6WLAvkBpmPEyknkcbxuipZD1msHYwrWRRhd2Wf+nN0lheXdfqjdqv6qs GuXn7AiY1++0v0SWJfvKUq3Uoda3p/sTAn5Dy/C7HB0nX0ZfbCbrKu9DSco326QBfE/p iaNsV0z5AKyWhw+CrI+UcKilQIkKQWxks+uI7psf8hopEGEKHItQcPj5Gs3FF667D8o8 Wp3OaUJS2a8qlkKyN5aO845PAY0oYIEEK7moVrHfpN6uVCOFIjljxW/6FpCvo1Zz3iiY MyhUSslDUruUNB6f1JPsWdsVEaQvV1TCppdONkRjksljaJXQiehw8iI6B1KJ3PwGTDtf yimA==
MIME-Version: 1.0
Received: by 10.112.100.195 with SMTP id fa3mr4536172lbb.38.1354546238821; Mon, 03 Dec 2012 06:50:38 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Mon, 3 Dec 2012 06:50:38 -0800 (PST)
In-Reply-To: <1354545525.11916.744.camel@mightyatom>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom>
Date: Mon, 3 Dec 2012 09:50:38 -0500
X-Google-Sender-Auth: 0Mk3Kz9E6PJ_0ZJaHox4hIMuHio
Message-ID: <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: IETF-Discussion <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: Mon, 03 Dec 2012 14:50:42 -0000

Elwyn says...

> However, I don't think that a short last call cycle need necessarily
> compromise cross-area review. There has always been the possibility for
> authors or wg chairs to request a early gen-art review with a view to
> checking out whether something is in good shape cross-area and for
> non-specialists.  This facility is not much used (I think I have done 3
> in 8 years on the gen-art team) but it is there, and I guess the team
> could cope with a few more since it doesn't drastically alter the total
> workload. So it would be entirely possible for a draft that might be
> fast-tracked to get some early review.

Do you really think it's likely that a chair who's trying to
fast-track a document will likely go out asking for early GenART,
SecDir, AppDir, and OpsDir reviews?

> Given that there is also open source code, reviewers have the chance to
> take a look at that and see the degree of hackiness involved.

This brings up something else that I've discussed with Stephen off list:

This proposal requires an *open source* implementation.  A robust set
of proprietary implementations, along with several interoperability
testing events, would not qualify.  But some untested open source that
someone knocked off in an afternoon would.  I find that odd.

I understand the desire to be able to inspect the implemented code,
but that would seem to rule out too many things, including stuff at
lower stack layers.  If the AD can look at the
implementations/deployments and talk with the implementors, the
openness of the source code is not an issue.  I'd be happy -- ecstatic
-- to have two or three proprietary, very-closed-source
implementations of most of the IMAP extensions, and have *no* need to
see the source code.  And I suspect that having shipping code in
routers is a good thing for validating new routing protocols, and also
suspect that we're not likely to be inspecting the source code of
those.

I'd really prefer if we'd talk about open source being desirable, but
not having it be necessary.

Barry

From stephen.farrell@cs.tcd.ie  Mon Dec  3 06:54:20 2012
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 A1D9221F8231 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.533
X-Spam-Level: 
X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uC1jaoa9iS8 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 06:54:18 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 17E8721F86C3 for <ietf@ietf.org>; Mon,  3 Dec 2012 06:54:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 39604BE51; Mon,  3 Dec 2012 14:53:56 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2fVmC9ptLcG; Mon,  3 Dec 2012 14:53:55 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 04129BE4D; Mon,  3 Dec 2012 14:53:54 +0000 (GMT)
Message-ID: <50BCBD04.40505@cs.tcd.ie>
Date: Mon, 03 Dec 2012 14:53:56 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com>
In-Reply-To: <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Mon, 03 Dec 2012 14:54:20 -0000

On 12/03/2012 02:50 PM, Barry Leiba wrote:
> I'd really prefer if we'd talk about open source being desirable, but
> not having it be necessary.

Yep. I got another comment to that effect as well.
I'll try address that (but that's not done yet).

FWIW, a working copy is available [1] that has a
bunch of changes resulting from comments already
received.

Cheers,
S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-ft.txt

From elwynd@dial.pipex.com  Mon Dec  3 07:15:33 2012
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 1E9B621F8639 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:15:33 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtXwuDUJHWna for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:15:32 -0800 (PST)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 912C521F846B for <ietf@ietf.org>; Mon,  3 Dec 2012 07:15:32 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1TfXk1-0006nd-Qt; Mon, 03 Dec 2012 15:15:29 +0000
Subject: Re: Idea for a process experiment to reward running code...
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Barry Leiba <barryleiba@computer.org>
In-Reply-To: <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com>
Content-Type: text/plain
Date: Mon, 03 Dec 2012 15:15:38 +0000
Message-Id: <1354547738.11916.762.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
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: Mon, 03 Dec 2012 15:15:33 -0000

Barry responded...

On Mon, 2012-12-03 at 09:50 -0500, Barry Leiba wrote:
> Elwyn says...
> 
> > However, I don't think that a short last call cycle need necessarily
> > compromise cross-area review. There has always been the possibility for
> > authors or wg chairs to request a early gen-art review with a view to
> > checking out whether something is in good shape cross-area and for
> > non-specialists.  This facility is not much used (I think I have done 3
> > in 8 years on the gen-art team) but it is there, and I guess the team
> > could cope with a few more since it doesn't drastically alter the total
> > workload. So it would be entirely possible for a draft that might be
> > fast-tracked to get some early review.
> 
> Do you really think it's likely that a chair who's trying to
> fast-track a document will likely go out asking for early GenART,
> SecDir, AppDir, and OpsDir reviews?
> 
A few do already.  But seriously, if the wg chair(s) actually have an
interest in the technology and feel there is a valid reason for getting
something decent out into the world quickly then they could well be
motivated to do just that.  If our wg chairs are really just
bureaucratic process minders then it's time we found some different
ones, but I don't think they are. Maybe this is just a plea for a bit
more parallel processing and a few less silos.

/Elwyn 


From barryleiba@gmail.com  Mon Dec  3 07:20:41 2012
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 AAA4121F87F1 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:20:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.975
X-Spam-Level: 
X-Spam-Status: No, score=-102.975 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drzEf22cg+B2 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:20:41 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE5621F87EF for <ietf@ietf.org>; Mon,  3 Dec 2012 07:20:40 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so2179074vcb.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 07:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=eqWetYtQ+WNR3PKn9aqohgpKxI88QZgaLx+4i9vzr38=; b=qlPmXjg/VnH9fmkEPq105XU3R8OZVm30pxoOrT6lvKX271wrKpTVggSPlfGRBEC2Nd +iRhxJV7udoWZMb3IEg2vCuKB3vLKrZR1t6r6Wpvc8E61eLBya5EItex+D+Iz5O80hFY sVnEjJeOdq0pK8qC1qDYGu8opcud8EPfdQ9AybNzwRC+blCgmTQ6d6nAs7FduQo1TUiz 8Q7PgxQGyAttJiaAffCLqoYzHg1izObyev9a3+OeH8y1KGJTaWzp0Z/oLSZJvlxT5n8B 5blpv/fgc6ykGn0oqKq/ReiP07o1TDwN4om5ubVCxIochhgCiqFF22Um55Tbd+bGAdh4 OtBw==
MIME-Version: 1.0
Received: by 10.220.16.4 with SMTP id m4mr8757034vca.43.1354548040062; Mon, 03 Dec 2012 07:20:40 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Mon, 3 Dec 2012 07:20:39 -0800 (PST)
In-Reply-To: <1354547738.11916.762.camel@mightyatom>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com> <1354547738.11916.762.camel@mightyatom>
Date: Mon, 3 Dec 2012 10:20:39 -0500
X-Google-Sender-Auth: 3FIfL5zbLXSRdOOdbxr0zL_mIjY
Message-ID: <CALaySJJwW11-RyBRMTNAV5MqF_KwBs+Fc2wjR7G4n6hRcoeM7g@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Elwyn Davies <elwynd@dial.pipex.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: Mon, 03 Dec 2012 15:20:42 -0000

>> Do you really think it's likely that a chair who's trying to
>> fast-track a document will likely go out asking for early GenART,
>> SecDir, AppDir, and OpsDir reviews?
>>
> A few do already.  But seriously, if the wg chair(s) actually have an
> interest in the technology and feel there is a valid reason for getting
> something decent out into the world quickly then they could well be
> motivated to do just that.

I agree.  I'm concerned that when the focus is on "fast-track", such
that someone is trying to trim a few weeks off a many-month process,
this could be even less likely.  But this is speculation; I have no
data.

> If our wg chairs are really just
> bureaucratic process minders then it's time we found some different
> ones, but I don't think they are. Maybe this is just a plea for a bit
> more parallel processing and a few less silos.

I don't think they are either, and I absolutely agree that we should
do more parallel processing and not put serial process in the way of
document handling.  That's never been at issue for me.

Barry

From loa@pi.nu  Mon Dec  3 07:23:24 2012
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2676021F885A for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:23:24 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQznDekNE6TZ for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:23:23 -0800 (PST)
Received: from mail.pi.nu (ns1.elverljung.se [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id A963A21F884A for <ietf@ietf.org>; Mon,  3 Dec 2012 07:23:22 -0800 (PST)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 7EF46820F2; Mon,  3 Dec 2012 16:23:18 +0100 (CET)
Message-ID: <50BCC3E4.4010106@pi.nu>
Date: Mon, 03 Dec 2012 16:23:16 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: comment on draft-crocker-id-adoption
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <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, 03 Dec 2012 15:23:24 -0000

Dave and Adrian,

I looked at section 1.1 of "What is a Working Group Draft?"

I find that the draft does not really answers that question. The draft
demonstrates how to recognize a wg draft in the IETF repository and it
also talks about the very common practice to keep the author/editor team
unchanged when the document is adopted as a working group document.
Though this strictly not necessary.

It also says that working groups use working group documents to
produce their official output.

While all this is true I think it would be more accurate to say that
"Working Group documents are documents where an IETF Working Group
exercise the revision control, i.e. other than editorial changes to
a Working Group document need to have a rough consensus by the Working
Group to be introduced."

/Loa
-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From hannes.tschofenig@gmx.net  Mon Dec  3 07:41:47 2012
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 99BAF21F86B1 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:41:47 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eryrF00H15Hz for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 07:41:47 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 7C0EE21F85B1 for <ietf@ietf.org>; Mon,  3 Dec 2012 07:41:46 -0800 (PST)
Received: (qmail invoked by alias); 03 Dec 2012 15:41:45 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.109]) [88.115.216.191] by mail.gmx.net (mp004) with SMTP; 03 Dec 2012 16:41:45 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19cO48nLJRco3G4eeDentEH7QOyf9+HmvHvx1LJgr zaIt+LBT6RCwK4
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Simplifying our processes: Conference Calls
Date: Mon, 3 Dec 2012 17:41:43 +0200
Message-Id: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 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, 03 Dec 2012 15:41:47 -0000

Hi all,=20

seeing all these discussions related to process improvements I just =
noticed one annoying thing related to working group conference calls.=20

It turns out that the IESG guidelines on that topic (see =
http://www.ietf.org/iesg/statement/interim-meetings.html) say the =
following:=20
"
* Conference calls and jabber sessions must be announced at least two =
weeks prior to the call or session, and the agenda must be published at =
least one week before call or session

* Announcement text must be sent to iesg-secretary@ietf.org
"

Having just scheduled conference calls for the OAuth mailing list I =
announced them on the OAuth WG mailing list (where I naively thought it =
belongs and forgot to re-read the IESG guidelines again).=20

Why do we need to announce conference calls (or Jabber chats) on the =
IETF announce mailing list? How likely is it that someone cares about a =
working group effort, does not subscribe to the WG mailing list, has not =
seen a poll about the date and time, and wants to participate in the =
conference call? To me - this seems rather unlikely.=20

Could we please change that?=20

Ciao
Hannes


From peter@akayla.com  Thu Nov 29 15:08:57 2012
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 E73E321F8ADD; Thu, 29 Nov 2012 15:08:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r79CYSuQzXdh; Thu, 29 Nov 2012 15:08:57 -0800 (PST)
Received: from p3plsmtpa06-02.prod.phx3.secureserver.net (p3plsmtpa06-02.prod.phx3.secureserver.net [173.201.192.103]) by ietfa.amsl.com (Postfix) with ESMTP id 339DA21F8A9B; Thu, 29 Nov 2012 15:08:56 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-02.prod.phx3.secureserver.net with  id Vb8v1k00A1huGat01b8v5g; Thu, 29 Nov 2012 16:08:56 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-14
Date: Thu, 29 Nov 2012 15:09:00 -0800
Message-ID: <002501cdce86$84f59940$8ee0cbc0$@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: Ac3OhkqJKVIPVc8hSRSzOY8nvjKAQg==
Content-Language: en-us
X-Mailman-Approved-At: Mon, 03 Dec 2012 07:46:24 -0800
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: Thu, 29 Nov 2012 23:08:58 -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-nfsv4-federated-fs-protocol-14
Reviewer: Peter Yee
Review Date: Nov-29-2012
IETF LC End Date: Oct-22-2012
IESG Telechat date: Nov-29-2012

Summary: This draft is basically ready for publication, but has a nit that
should be fixed before publication. [Ready with nits.]

All other corrections from the -13 review were accepted and the other
changes in the current version appear reasonable.

Major issues:

Minor issues:

Nits/editorial comments:

Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1"  in
"(see" and ")" for readability.
[This is my same suggestion from the previous review.  I won't mention it
again, I promise. :-) ]


From chuck.lever@oracle.com  Fri Nov 30 07:45:28 2012
Return-Path: <chuck.lever@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2690621F8B4D; Fri, 30 Nov 2012 07:45:28 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nZR4fd1i8NL9; Fri, 30 Nov 2012 07:45:27 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id 5D55D21F8B36; Fri, 30 Nov 2012 07:45:27 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id qAUFjGrL013266 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 30 Nov 2012 15:45:17 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id qAUFjGXB020212 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 30 Nov 2012 15:45:16 GMT
Received: from abhmt112.oracle.com (abhmt112.oracle.com [141.146.116.64]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id qAUFjFO6032269; Fri, 30 Nov 2012 09:45:15 -0600
Received: from moret.1015granger.net (/99.26.161.222) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 30 Nov 2012 07:45:15 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-14
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <002501cdce86$84f59940$8ee0cbc0$@akayla.com>
Date: Fri, 30 Nov 2012 10:45:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <08608853-52A1-443F-88CF-B550BD325B82@oracle.com>
References: <002501cdce86$84f59940$8ee0cbc0$@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1499)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
X-Mailman-Approved-At: Mon, 03 Dec 2012 07:46:24 -0800
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-nfsv4-federated-fs-protocol.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, 30 Nov 2012 15:45:28 -0000

On Nov 29, 2012, at 6:09 PM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at <
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd or AD before =
posting a
> new version of the draft.
>=20
> Document: draft-ietf-nfsv4-federated-fs-protocol-14
> Reviewer: Peter Yee
> Review Date: Nov-29-2012
> IETF LC End Date: Oct-22-2012
> IESG Telechat date: Nov-29-2012
>=20
> Summary: This draft is basically ready for publication, but has a nit =
that
> should be fixed before publication. [Ready with nits.]
>=20
> All other corrections from the -13 review were accepted and the other
> changes in the current version appear reasonable.
>=20
> Major issues:
>=20
> Minor issues:
>=20
> Nits/editorial comments:
>=20
> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1"  =
in
> "(see" and ")" for readability.
> [This is my same suggestion from the previous review.  I won't mention =
it
> again, I promise. :-) ]

Sorry we missed this before.  I'll work with Martin to see that this is =
addressed.

--=20
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





From mjethanandani@gmail.com  Fri Nov 30 09:03:20 2012
Return-Path: <mjethanandani@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 0D8FB21F8B91; Fri, 30 Nov 2012 09:03:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D+6WEfo7p65A; Fri, 30 Nov 2012 09:03:19 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 31E1121F8B67; Fri, 30 Nov 2012 09:03:19 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so287371dae.31 for <multiple recipients>; Fri, 30 Nov 2012 09:03:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=6ktjHCgE6fHmvkCp91eEKkKq/y9lvt3L9CvqJFkkLDA=; b=suvHF2VUbl4aOCMeiaGD/XWXNn8UTnyzFA7r0CflY2EJ3uDM+ctJKy/j04aSpQpwrg tuEan8Dh5SEIOSn/nA7Eh+NuuN2E7uE1WqV1mI+Ybw8LRkFW9x2i00zAReoSNHAN+9+2 EyRyhIYZdG5UdKSsUX2I6KudnRODl5jElAVdHDJ1ax5hCXIw8/iFInik+zbtyFTds1tp PPNQUIHEgyeDc7eR7+W1Q3bAKRq1lfKXUKPmedRLk3p7DM7SET467eDjcrFMkJNuIp4A 4EbG4802d8ySNiM9Oy6rTZtE8C46x6+7pdMSDkWgOnbb6WVoDXEfcDygVo+cSpkJ9ceS 6koQ==
Received: by 10.66.79.133 with SMTP id j5mr4675167pax.51.1354294998955; Fri, 30 Nov 2012 09:03:18 -0800 (PST)
Received: from [192.168.1.123] (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id a8sm3182035paz.18.2012.11.30.09.03.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 30 Nov 2012 09:03:18 -0800 (PST)
Subject: Re: Gen-ART LC Review of draft-ietf-karp-routing-tcp-analysis-05.txt
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-4-178157723
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com>
Date: Fri, 30 Nov 2012 09:03:15 -0800
Message-Id: <7B7C06EA-E5EB-4FD6-ADE6-1A8E38B11405@gmail.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com> <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com> <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com>
To: Ben Campbell <ben@nostrum.com>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Mon, 03 Dec 2012 07:46:24 -0800
Cc: draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org, "gen-art@ietf.org Review Team" <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: Fri, 30 Nov 2012 17:03:20 -0000

--Apple-Mail-4-178157723
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Ben,

See inline. If you are ok with these changes, I will go ahead and submit =
an updated version of the draft.

On Nov 25, 2012, at 5:56 PM, Mahesh Jethanandani wrote:

> Further trimming it to sections that require a response.
>=20
> On Nov 21, 2012, at 3:12 PM, Ben Campbell wrote:
>=20
>>=20
>>>>=20
>>>> *** Minor issues *** :
>>>>=20
>>>> -- section 2.2, last paragraph:
>>>>=20
>>>> The IKE mention lacks context. Do you mean to suggest IKE with =
IPSec? I assume so, but there's been no mention of IPSec so far.
>>>=20
>>> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>>>=20
>>> How about this?
>>>=20
>>> For point-to-point key management IKEv2[RFC5996] protocol provides =
...
>>=20
>> 5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?
>=20
> Added this sentence.
>=20
> Although IKEv2 is discussed as a component of IPsec, KMP can use just =
the mutual authentication and SA establishment portion of IKEv2.

This statement has been further modified to:

For point-to-point key management IKEv2 [RFC5996] provides for
 automated key exchange under a SA and can be used for a comprehensive
 Key Management Protocol (KMP) solution for routers.  IKEv2 can be used
 for both IPsec SAs [RFC4301] and other types of SAs. For example,=20
 Fibre Channel SAs  [RFC4595] are currently negotiated with IKEv2. Using
 IKEv2 to negotiate TCP-AO is a possible option.


>=20
>>=20
>>>=20
>>>>=20
>>>> *** Nits/editorial comments ***:
>>>>=20
>>>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>>>=20
>>> Found one unused reference and have removed it.
>>=20
>> Seems like there were more than one. =46rom IDNits:
>>=20
>>  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined
>>=20
>>  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
>>     reference was found in the text
>>=20
>>  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
>>     reference was found in the text
>>=20
>>  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)
>>=20
>>  -- Obsolete informational reference (is this intentional?): RFC 2409
>>     (Obsoleted by RFC 4306)
>>=20
>>  -- Obsolete informational reference (is this intentional?): RFC 3547
>>     (Obsoleted by RFC 6407)
>=20
> I have removed these unused references.
>=20
>>=20
>>>>=20
>>>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>>>=20
>>>> sentence fragment.
>>>=20
>>> Changed it to say:
>>>=20
>>> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>>>=20
>>=20
>> Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.
>>=20
>=20
> Changed it to:
>=20
> In addition, the recommendations in RFC 5961 should also be followed =
...

Mahesh Jethanandani
mjethanandani@gmail.com




--Apple-Mail-4-178157723
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Ben,<div><br></div><div>See inline. If you are ok with these changes, =
I will go ahead and submit an updated version of the =
draft.<div><br><div><div>On Nov 25, 2012, at 5:56 PM, Mahesh =
Jethanandani wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Further trimming it to sections =
that require a response.<div><br><div><div>On Nov 21, 2012, at 3:12 PM, =
Ben Campbell wrote:</div><br><blockquote =
type=3D"cite"><div><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Minor issues *** =
:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 2.2, last =
paragraph:<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">The IKE mention lacks context. =
Do you mean to suggest IKE with IPSec? I assume so, but there's been no =
mention of IPSec so far.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">No. It implies =
the use of IKEv2 protocol for performing mutual authentication and =
establishing SA. There is no suggestion of using IKE with =
IPSec.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">How about =
this?<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">For =
point-to-point key management IKEv2[RFC5996] protocol provides =
...<br></blockquote><br>5996 describes IKEv2 as a component of IPSec, =
and a key-management mechanism for ESP and AH SAs. Now, I won't claim to =
be an IKE expert by any extent, but I think that if you mean to use IKE =
_without_ IPSec it would be good to add a sentence or two pointing that =
out. Or is there some other reference that could be used that describes =
using IKEv2 for non-IPSec =
SAs?<br></div></blockquote><div><br></div>Added this =
sentence.</div><div><br></div><div><i>Although IKEv2 is discussed as a =
component of IPsec, KMP can use just the mutual authentication and SA =
establishment portion of =
IKEv2.</i></div></div></div></blockquote><div><br></div>This statement =
has been further modified to:</div><div><br></div><div><i>For =
point-to-point key management IKEv2 [RFC5996] provides =
for</i><div><i>&nbsp;automated key exchange under a SA and can be used =
for a comprehensive</i></div><div><i>&nbsp;Key Management Protocol (KMP) =
solution for routers. &nbsp;IKEv2 can be used</i></div><div><i>&nbsp;for =
both IPsec SAs [RFC4301] and other types of SAs. For =
example,&nbsp;</i></div><div><i>&nbsp;Fibre Channel&nbsp;SAs =
&nbsp;[RFC4595] are currently negotiated with IKEv2. =
Using</i></div><div><i>&nbsp;IKEv2 to negotiate TCP-AO is a possible =
option.</i></div></div><div><br></div><div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">*** Nits/editorial comments =
***:<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- IDNits indicates some unused =
and obsoleted references. Please =
check.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Found one =
unused reference and have removed it.<br></blockquote><br>Seems like =
there were more than one. =46rom IDNits:<br><br> &nbsp;=3D=3D Missing =
Reference: 'IRR' is mentioned on line 92, but not defined<br><br> =
&nbsp;=3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in the =
text<br><br> &nbsp;=3D=3D Unused Reference: 'RFC3547' is defined on line =
588, but no explicit<br> &nbsp;&nbsp;&nbsp;&nbsp;reference was found in =
the text<br><br> &nbsp;** Obsolete normative reference: RFC 2385 =
(Obsoleted by RFC 5925)<br><br> &nbsp;-- Obsolete informational =
reference (is this intentional?): RFC 2409<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC 4306)<br><br> &nbsp;-- =
Obsolete informational reference (is this intentional?): RFC 3547<br> =
&nbsp;&nbsp;&nbsp;&nbsp;(Obsoleted by RFC =
6407)<br></div></blockquote><div><br></div>I have removed these unused =
references.</div><div><br><blockquote type=3D"cite"><div><br><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">-- section 4, 2nd paragraph: "In =
addition Improving TCP=92s Robustness to Blind In-Window =
Attacks."<br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite">sentence =
fragment.<br></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Changed it to =
say:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">In addition, =
the recommendations in Improving TCP's Robustness to Blind In-Window =
Attacks<br></blockquote><blockquote type=3D"cite"><br></blockquote><br>Am =
I correct in assuming this merges with the following sentence? =
Otherwise, it's still a =
fragment.<br><br></div></blockquote><br></div><div>Changed it =
to:</div><div><br></div><div><i>In addition, the recommendations in RFC =
5961 should also be followed =
...</i></div></div></div></blockquote></div><br><div>
<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>Mahesh =
Jethanandani</div><div><a =
href=3D"mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><=
div><br></div></span><br class=3D"Apple-interchange-newline">
</div>
<br></div></div></body></html>=

--Apple-Mail-4-178157723--

From melinda.shore@gmail.com  Sun Dec  2 12:30:52 2012
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 78C3721F87BC for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:30:52 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UHtq2tRGPUYA for <ietf@ietfa.amsl.com>; Sun,  2 Dec 2012 12:30:52 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0F29E21F8769 for <ietf@ietf.org>; Sun,  2 Dec 2012 12:30:52 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1416765pbc.31 for <ietf@ietf.org>; Sun, 02 Dec 2012 12:30:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=r76cZqdgVAcskFSyqeGUolOJ6faYJKkvuujGtqF+hmY=; b=UIttS3rY8HZtcIdX//9LbnJvulZcQWtsLHUEnQlPXXNy3B22/8ZiXugTa9bidFK6d7 M0mLkaugnJc06dEbV7lIEokyytBfahjWHGtCpkMiTzxt0jJfrVgVhbN+czDFGTb2eAyL PNIIuruZLg2d8y1xuDwBpofKcpLnwfuA1XobhiNmNmpz+WMWfrnhgqj7FpY8stJwCu3U wcJWObdYSuGC5THMJmbaNFxhkVKMj7iWvJ/1YXLqD4Tignp2ySbFaIUvMEGooIU6Llq4 tPIJnzQsBBO7vcc4DBW5Mih8CgRTJ/MFpF2J1+5TQrXVJ3NbULJKP4dVv1NSGSoGOn7W J3nw==
Received: by 10.66.76.98 with SMTP id j2mr20420707paw.65.1354480251871; Sun, 02 Dec 2012 12:30:51 -0800 (PST)
Received: from spandex.local (66-230-86-19-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.19]) by mx.google.com with ESMTPS id uh10sm6766277pbc.35.2012.12.02.12.30.50 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 02 Dec 2012 12:30:51 -0800 (PST)
Message-ID: <50BBBA79.7050008@gmail.com>
Date: Sun, 02 Dec 2012 11:30:49 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Creating an IETF Working Group Draft
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <01a701cdcd81$7d365380$77a2fa80$@olddog.co.uk> <50BBA236.9010603@dcrocker.net> <50BBB79C.40106@gmail.com> <50BBB862.8090209@gmail.com> <50BBB940.1020302@gmail.com>
In-Reply-To: <50BBB940.1020302@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 03 Dec 2012 07:46:24 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 02 Dec 2012 20:30:52 -0000

On 12/2/12 11:25 AM, Arturo Servin wrote:
> 	So it is ok to have bad ideas as I+D, possibly harmful for the Internet
> just to have a structured discussion?

Who said that?

Melinda



From brian.e.carpenter@gmail.com  Mon Dec  3 08:07:23 2012
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 ACB5E21F8639 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.672
X-Spam-Level: 
X-Spam-Status: No, score=-101.672 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ES1VpLyfx7ta for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:07:22 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 0310C21F8599 for <ietf@ietf.org>; Mon,  3 Dec 2012 08:07:21 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id dr13so1272802wgb.13 for <ietf@ietf.org>; Mon, 03 Dec 2012 08:07:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=51vAV/ECqf8o8MlVdlQgS6mJv0F4sgAcsMidOQXTAlY=; b=CHlnUOiUZCEn8VkokWl3FNdCOJhIu3d3qwB0MjjziS/Q5gY+BNkeX61kZKGblV8Wjk pX2gzonO6ttlp+ob22tq2AWrXnnwesi08kwzK3WQxqZDdMxn5ZD2WYAItEqXIw1k+5nX d1A6TtrxqHmV+6BYCWkvkq2W6RwO1j/JUBJ0TcKKhAWkagrosd0VZbi8IRdq/7zlwBNQ 4pg1YUjKabTPfL/UUCBUjQjpe6UCS1lW/92Nty5qadPZTm4iuczjc8K2guOdcANITqzt fDu8js279Bmy4l8xpA3J0RY9HDEGNi08u6UpypiMtIFro2eluvmqIESLoD35oQPq11Wh FkDg==
Received: by 10.216.212.2 with SMTP id x2mr3601217weo.32.1354550833121; Mon, 03 Dec 2012 08:07:13 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-218-71.as13285.net. [2.102.218.71]) by mx.google.com with ESMTPS id s12sm11506279wik.11.2012.12.03.08.07.11 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 08:07:12 -0800 (PST)
Message-ID: <50BCCE1D.5070001@gmail.com>
Date: Mon, 03 Dec 2012 16:06:53 +0000
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: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: Simplifying our processes: Conference Calls
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
In-Reply-To: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org 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, 03 Dec 2012 16:07:23 -0000

On 03/12/2012 15:41, Hannes Tschofenig wrote:
> Hi all, 
> 
> seeing all these discussions related to process improvements I just noticed one annoying thing related to working group conference calls. 
> 
> It turns out that the IESG guidelines on that topic (see http://www.ietf.org/iesg/statement/interim-meetings.html) say the following: 
> "
> * Conference calls and jabber sessions must be announced at least two weeks prior to the call or session, and the agenda must be published at least one week before call or session
> 
> * Announcement text must be sent to iesg-secretary@ietf.org
> "
> 
> Having just scheduled conference calls for the OAuth mailing list I announced them on the OAuth WG mailing list (where I naively thought it belongs and forgot to re-read the IESG guidelines again). 
> 
> Why do we need to announce conference calls (or Jabber chats) on the IETF announce mailing list? How likely is it that someone cares about a working group effort, does not subscribe to the WG mailing list, has not seen a poll about the date and time, and wants to participate in the conference call? To me - this seems rather unlikely. 

The point is that we work in public, so the whole community should know.
I regularly attend WG meetings where I am not subscribed - it's one of the
side benefits of the week-long meetings - and who's to say that I might not
want to drop into OAuth too?

Suppose I happened to notice (I am making this up) that the foobar WG has
decided to use the IPv6 Flow Label for an unintended purpose? I'd like
to know if they are going to have a conf call, so that I can explain
RFC 6437 to them. Otherwise, I have no interest in foobar.

> Could we please change that? 

I hope not.

    Brian

> 
> Ciao
> Hannes
> 
> 

From hartmans@mit.edu  Mon Dec  3 08:21:14 2012
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 2B93021F8447 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:21:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.842
X-Spam-Level: 
X-Spam-Status: No, score=-102.842 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2+6wjWIGYco for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:21:13 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 9558F21F843A for <ietf@ietf.org>; Mon,  3 Dec 2012 08:21:13 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 8BEAD2003E; Mon,  3 Dec 2012 11:19:22 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3B9F8420E; Mon,  3 Dec 2012 11:21:12 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com> <50BCBD04.40505@cs.tcd.ie>
Date: Mon, 03 Dec 2012 11:21:12 -0500
In-Reply-To: <50BCBD04.40505@cs.tcd.ie> (Stephen Farrell's message of "Mon, 03 Dec 2012 14:53:56 +0000")
Message-ID: <tslmwxvayyv.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Barry Leiba <barryleiba@computer.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: Mon, 03 Dec 2012 16:21:14 -0000

>>>>> "Stephen" == Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:

    Stephen> On 12/03/2012 02:50 PM, Barry Leiba wrote:
    >> I'd really prefer if we'd talk about open source being desirable,
    >> but not having it be necessary.

    Stephen> Yep. I got another comment to that effect as well.  I'll
    Stephen> try address that (but that's not done yet).

For myself, I think the requirement for open-source is very good for
this experiment, or something like it.

People can examine the open-source implementation and consider the
question of whether the implementation explores enough of the edge cases
that a process short-cut is appropriate.  I think that's important in
this, so I'd be a lot more comfortable with this with an open-source
requirement.


From stephen.farrell@cs.tcd.ie  Mon Dec  3 08:23:19 2012
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 2018E21F87E7 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:23:19 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qPznwFxHYc4 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:23:18 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 98D6421F887D for <ietf@ietf.org>; Mon,  3 Dec 2012 08:23:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F0A14BE50; Mon,  3 Dec 2012 16:22:56 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oJMTe8ASSTNA; Mon,  3 Dec 2012 16:22:56 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 37810BE49; Mon,  3 Dec 2012 16:22:56 +0000 (GMT)
Message-ID: <50BCD1E1.3070407@cs.tcd.ie>
Date: Mon, 03 Dec 2012 16:22:57 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <CAC4RtVC1VhJjhdPNuzoE+BQcm-krm6=RLSxxsMp56GDVa3csnw@mail.gmail.com> <50BCBD04.40505@cs.tcd.ie> <tslmwxvayyv.fsf@mit.edu>
In-Reply-To: <tslmwxvayyv.fsf@mit.edu>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.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: Mon, 03 Dec 2012 16:23:19 -0000

On 12/03/2012 04:21 PM, Sam Hartman wrote:
>>>>>> "Stephen" == Stephen Farrell <stephen.farrell@cs.tcd.ie> writes:
> 
>     Stephen> On 12/03/2012 02:50 PM, Barry Leiba wrote:
>     >> I'd really prefer if we'd talk about open source being desirable,
>     >> but not having it be necessary.
> 
>     Stephen> Yep. I got another comment to that effect as well.  I'll
>     Stephen> try address that (but that's not done yet).
> 
> For myself, I think the requirement for open-source is very good for
> this experiment, or something like it.
> 
> People can examine the open-source implementation and consider the
> question of whether the implementation explores enough of the edge cases
> that a process short-cut is appropriate.  I think that's important in
> this, so I'd be a lot more comfortable with this with an open-source
> requirement.

Me too. But I guess others are concerned about that. Anyway, if/when
this gets an IETF LC, we can see if the wording's ok for folks.

Cheers,
S.

> 
> 
> 

From petithug@acm.org  Mon Dec  3 08:41:27 2012
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 7B52921F8593 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:41:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlAVGhQwRWK8 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:41:26 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD1321F854C for <ietf@ietf.org>; Mon,  3 Dec 2012 08:41:26 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:fca2:179c:bd27:c87e] (unknown [IPv6:2601:9:4b80:32:fca2:179c:bd27:c87e]) (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 BAE1C20193; Mon,  3 Dec 2012 16:41:24 +0000 (UTC)
Message-ID: <50BCD637.3030009@acm.org>
Date: Mon, 03 Dec 2012 08:41:27 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
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: Mon, 03 Dec 2012 16:41:27 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/01/2012 12:12 PM, Stephen Farrell wrote:
> 
> Hi all,
> 
> I've just posted an idea [1] for a small process improvement. If it doesn't
> seem crazy I'll try pursue it with the IESG as an RFC 3933 process
> experiment. If its universally hated then that's fine, it can die.
> 
> The IESG have seen (more-or-less) this already but it hasn't be discussed,
> so this is just a proposal from me and has no "official" status
> whatsoever.
> 
> Any comments, suggestions or better ideas are very welcome. Feel free to
> send me comments off list for now, or on this list I guess. If there's
> loads of email (always possible, this being a process thing;-) we can move
> to some other list.
> 
> Regards, Stephen.
> 
> [1] http://tools.ietf.org/id/draft-farrell-ft
> 

I support this idea, but I think that free software should also be considered
as part of this experiment (free software and open source are not synonymous).
 Using the acronym FOSS and defining it as Free or Open Source Software in the
document would achieve this.

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)

iQIcBAEBCAAGBQJQvNY2AAoJECnERZXWan7EWSgQAMoAw+QMXnpV6c98K7SN4R1x
lp9l2p8qVeTVNDEa/9X8j3Om/c9lUgR19KS+kdw9QYnLm3U7XbvRPwXP6DgAcyjy
gz3JUMvRcAZDU5V9BUhGK8p6nm6noUza1nMsuDhjQbmEPYm0YrlU6UH02WJXv3NS
Bbv+OGmnX+rGNde+bQ59S1ZAYld6Q7zXjKrbmK+22xV9fYCE/8Mgrs1yvYj2iTUn
O2Lw2GGMrbTt34hdvSy5ffP0VyuoicS8ajfvfhk7ki1jswUc3UUeMAgsIB/X28+2
xZ7zpncerlmrOJkiJx5263o4EXVbLtaEdCpLUMKPJuO+xh2S9UcgBjcuQFZDlv8S
lVBbHKTnotfCSq5SWqd5mo5O0qyfy+HWzMYhaHLvsln5ll9ShJJMpGlhuYgU8Pcs
uudqx/GtQTkAS18+YzT2KhG+E7qqGoLM6bseEuHGK/dCAZP+e4JdV2RPjpgAT/f+
Zac9xYti4ZqyFKRTRQqNYlzQU+ELcEUY69J5yMKlN/3FDlcbgAABDIQLJc6A0nC8
PpCngDab/VHsreikAmTl2WlGib4H/pHppdTtj73GqC14PmNwh/zf+v4RL18oH/ks
NTPsTovzvD+Rx+kU1ZL9YT2QMenfc5287T+coY4Fu0W6FoykA6CLGdB0R0x4RBI1
zg2pW36ZhtG0Ps6PtFut
=zieq
-----END PGP SIGNATURE-----

From stephen.farrell@cs.tcd.ie  Mon Dec  3 08:55:27 2012
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 F244821F84F5 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RJjcCbwml2w4 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 08:55:22 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A575621F8464 for <ietf@ietf.org>; Mon,  3 Dec 2012 08:55:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F3AE2BE36; Mon,  3 Dec 2012 16:54:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3qX7SoBZUX2z; Mon,  3 Dec 2012 16:54:56 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b] (unknown [IPv6:2001:770:10:203:60a5:f3d6:2e7e:4b]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DDC9CBE25; Mon,  3 Dec 2012 16:54:56 +0000 (GMT)
Message-ID: <50BCD962.3020007@cs.tcd.ie>
Date: Mon, 03 Dec 2012 16:54:58 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BCD637.3030009@acm.org>
In-Reply-To: <50BCD637.3030009@acm.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Mon, 03 Dec 2012 16:55:28 -0000

On 12/03/2012 04:41 PM, Marc Petit-Huguenin wrote:
> I support this idea, but I think that free software should also be considered
> as part of this experiment (free software and open source are not synonymous).
>  Using the acronym FOSS and defining it as Free or Open Source Software in the
> document would achieve this.

Fair point. OTOH, there are folks who want to not require open-source
too. For now, I'd gone with "ideally open-source." As I said to Sam,
let's deal with that, if need be, at IETF LC.

In the meantime, I've posted -01 [1] with a bunch of changes. Do let
me know if I forgot to ack someone and as before all comments
(inevitable, this being a process thing;-) are very welcome.

Thanks,
S.

[1] http://tools.ietf.org/html/draft-farrell-ft-01

From petithug@acm.org  Mon Dec  3 09:06:05 2012
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 2CFC021F8430 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 09:06:05 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zt-fCnDyeQLb for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 09:06:04 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id E0D9221F88EC for <ietf@ietf.org>; Mon,  3 Dec 2012 09:06:03 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:fca2:179c:bd27:c87e] (unknown [IPv6:2601:9:4b80:32:fca2:179c:bd27:c87e]) (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 C420920193; Mon,  3 Dec 2012 17:06:02 +0000 (UTC)
Message-ID: <50BCDBFE.3080701@acm.org>
Date: Mon, 03 Dec 2012 09:06:06 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.11) Gecko/20121122 Icedove/10.0.11
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BCD637.3030009@acm.org> <50BCD962.3020007@cs.tcd.ie>
In-Reply-To: <50BCD962.3020007@cs.tcd.ie>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
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: Mon, 03 Dec 2012 17:06:05 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/03/2012 08:54 AM, Stephen Farrell wrote:
> 
> On 12/03/2012 04:41 PM, Marc Petit-Huguenin wrote:
>> I support this idea, but I think that free software should also be
>> considered as part of this experiment (free software and open source are
>> not synonymous). Using the acronym FOSS and defining it as Free or Open
>> Source Software in the document would achieve this.
> 
> Fair point. OTOH, there are folks who want to not require open-source too.
> For now, I'd gone with "ideally open-source." As I said to Sam, let's deal
> with that, if need be, at IETF LC.

OK, but note that I will oppose for this experiment the use of software that
is not either available in source form or accompanied with a conformance test
suite.

> 
> In the meantime, I've posted -01 [1] with a bunch of changes. Do let me
> know if I forgot to ack someone and as before all comments (inevitable,
> this being a process thing;-) are very welcome.
> 
> Thanks, S.
> 
> [1] http://tools.ietf.org/html/draft-farrell-ft-01
> 


- -- 
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)

iQIcBAEBCAAGBQJQvNv6AAoJECnERZXWan7EV3QP/2Tv/rn7+GSwK2KkB3RsnS00
ryB5FH0drUdMr7c+TreHDXh/uR6HLYxB1Cg9rDd5CZQaSBQlTtwIKVUxMPOW805k
Uf3/xi8d3DpXVTmlesMtmbT/GeE7S0hJ3wf6LUwl4OkctX8GMDNuaONNudarl3Qt
sR+AJw8OU8KOFMqEn6fOqpLwY7OiQG3M6tuMwfNIm1Z0bHb/WAssF9l+J2ZTqq8L
AmJpHPql65WVSPck+jRnYyNtfnSkVCmCQ1y5cMeNoEnm5tkEt5oeinsvDwEAWBB3
5YzbUb+q72SCEyTbeVOrwTU1cBU/CKzOH+8r0ykK51KlZ1acYetwh31U4h1jDpHd
tNrwu1Z5wvKCa4b4dvzkiEBE83gAr6IGMDlPWNkEtotB1ZZd/MUpRNsSCzyivtl5
zr1rwpMY/5w6LljGO4jN4ZXKtXErFovEQpTc+bUz9K23WYyZMkARehXZLkbEvpb8
/MY1zGlgRSrGHr5Wn+k9egCeWqYjGNQedYpDcqWw7oQ5V956W+/AvKHo6jPGGweC
wpW3Hm+AWc3gPZ2pgYYt8dVScscWLo0qDWW4daHwAqu0rvge7PUB8aVagE72fQUn
fPEPhETD2QqZfXDeCtfNqOVS1/v+SYsAYxcGFYwu7NR51OROBkhMpWT5KDuaPp02
OPRv2MwPcsanVoQ1uNfY
=30oW
-----END PGP SIGNATURE-----

From wesley.george@twcable.com  Mon Dec  3 09:44:10 2012
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 D59C921F88E8 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 09:44:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.585
X-Spam-Level: 
X-Spam-Status: No, score=-0.585 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aufTcehJboBY for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 09:44:10 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4752F21F88DF for <ietf@ietf.org>; Mon,  3 Dec 2012 09:44:10 -0800 (PST)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,208,1355115600"; d="scan'208";a="462571665"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 03 Dec 2012 12:43:42 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Mon, 3 Dec 2012 12:43:53 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Keith Moore <moore@network-heretics.com>
Date: Mon, 3 Dec 2012 12:44:10 -0500
Subject: RE: Useful slide tex (was - Re: English spoken here)
Thread-Topic: Useful slide tex (was - Re: English spoken here)
Thread-Index: Ac3RYoSX4ctkgNGWR8yGk9XXKYeppwAGveDQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338B42EDB@PRVPEXVS15.corp.twcable.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net>	<50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <2671C6CDFBB59E47B64C10B3E0BD59230338B42BE8@PRVPEXVS15.corp.twcable.com> <50BCB718.6000805@network-heretics.com>
In-Reply-To: <50BCB718.6000805@network-heretics.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: "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, 03 Dec 2012 17:44:10 -0000

> From: Keith Moore [mailto:moore@network-heretics.com]

> Years ago, my impression was that that Sunday training sessions were
> pretty much ignored by anyone experienced in the organization.  Is this
> still the case?

[WEG] Depends on the subject matter. If they're all targeted at new attende=
es, it follows that no experienced attendees would be interested. At 5 year=
s in, I guess you could call me experienced in the organization, and I atte=
nded one during IETF84 about crypto and security.

Wes George

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 fred@cisco.com  Mon Dec  3 10:11:03 2012
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 D911021F8876 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 10:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.999
X-Spam-Level: 
X-Spam-Status: No, score=-109.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ex84+wYvQGk for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 10:11:03 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 29C9921F8848 for <ietf@ietf.org>; Mon,  3 Dec 2012 10:11:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1889; q=dns/txt; s=iport; t=1354558263; x=1355767863; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YgKNQdPC+pftb0h+sFLSPOgbfSJqaJMaOPTrZwHTFNs=; b=TV6gIYPtuBRwERrJGb5G15fCleIIQqWnfY41TgmAgSIT3Au4TIc9Jdse bRDqmIALdStPuHJ9No2vGpDOXg/jXDMDs1Jps5sQCF/nyx0Q+sWNK2/zz uzBFjCKDTgfWMKGYOeD4x9Nn61mT/4KzPoa3C0OvBvc+zBVFQOQZcknCz g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHPqvFCtJV2c/2dsb2JhbABEwAEWc4IeAQEBAwF5BQsCAQgiJDIlAgQODYgCBr5NjEAKg1ZhA6ZIgnKCIQ
X-IronPort-AV: E=McAfee;i="5400,1158,6915"; a="145819081"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 03 Dec 2012 18:11:02 +0000
Received: from xhc-aln-x09.cisco.com (xhc-aln-x09.cisco.com [173.36.12.83]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id qB3IB2Om025185 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Dec 2012 18:11:02 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.22]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.001; Mon, 3 Dec 2012 12:11:02 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Useful slide tex (was - Re: English spoken here)
Thread-Topic: Useful slide tex (was - Re: English spoken here)
Thread-Index: AQHN0LRxq5g+0sm6hUi2AHFsQnFfqpgGLmAAgAAB3ICAAAJOAIAAC2yAgAGITwA=
Date: Mon, 3 Dec 2012 18:11:01 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B6F5F2C@xmb-rcd-x09.cisco.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21D.6090403@bogus.com>
In-Reply-To: <50BBA21D.6090403@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.120]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <227DE9E24A1CE3488D52EDEB2E368A41@cisco.com>
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: Mon, 03 Dec 2012 18:11:04 -0000

On Dec 2, 2012, at 10:46 AM, joel jaeggli wrote:

> We have non-native english speakers and remote participants both working =
at a disadvantage to follow the discussion in the room. We should make it h=
arder for them by removing the pretext that the discussion is structured ar=
ound material that they can review and follow along on? I don't think that'=
s even remotely helpful.

To my mind, that is a key concept. Also, a prepared slide showing a graphic=
 and a whiteboard rendition of the same graphic both show a graphic. What i=
s different is that the prepared slide will be more readable (a font is muc=
h clearer than my handwriting), and will take less (real) time to produce (=
I can show a slide instantly, but it may take a couple of minutes to draw t=
he picture). And third, the prepared slide is thought through in advance; t=
he drawn graphic needs to be as well to really be useful, but may be dreame=
d up on the spot, written over several times as the discussion proceeds, et=
c.

>From my perspective, a white board or flip chart is a good thing and I usua=
lly ask from one to be present when I speak. The prepared slides are useful=
 for everyone and especially ESL folks. And BTW, the listener with the slid=
es on his own computer can flip around in the deck on his own ("wait a minu=
te, didn't he just say [flip flip]... Oh, he's saying =85") where an erased=
 whiteboard can't be flipped back to.

I agree with the notion that the primary purpose of the meeting is discussi=
on. What you and I tell those who present in v6ops is that we want the pres=
entation to guide and support a discussion, and anything that is pure prese=
ntation should take no more than half of the time allotted to them. I don't=
 see that the tool is the problem, it's the user of the tool, and we all va=
ry in our presentation/discussion skills.=

From fred@cisco.com  Mon Dec  3 10:24:54 2012
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 2384121F8931 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 10:24:54 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UmrLtMILWJg5 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 10:24:53 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 24EC221F8938 for <ietf@ietf.org>; Mon,  3 Dec 2012 10:24:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=657; q=dns/txt; s=iport; t=1354559093; x=1355768693; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BXqnqliSjAQUJA2cjalQmpjTP4skVtav5MwljSONZG8=; b=iUc4Q1jUJ2c0ykaK4SJLfvpFkpTXzHu2FpUVpcilW9Zxhhg5WvCY2Ho+ ZKgmS7VsaQPZWlI/C8agl48G+AyBNcHE8ganpshcWUYrOfNtOEa9G0lIf 288UQDGQEB7RYkckP9t47aZd8wVZm20R/vMIKPC11J8T/4Ye34gTFEZ6l 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOLtvFCtJXG//2dsb2JhbABEwAEWc4IeAQEBAwE6NAsFCwIBCCIUEDIlAgQODYgCBr5CjECDYGEDpkiCcoIh
X-IronPort-AV: E=McAfee;i="5400,1158,6915"; a="148824088"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-5.cisco.com with ESMTP; 03 Dec 2012 18:24:49 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id qB3IOncS025459 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Dec 2012 18:24:49 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.22]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.001; Mon, 3 Dec 2012 12:24:48 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: SM <sm@resistor.net>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is	done on the mailing lists")
Thread-Topic: When to adopt a draft as a WG doc (was RE: "IETF work is	done on the mailing lists")
Thread-Index: AQHNznUT4KPQFPu7A0q0AeejhJah/pgHzpwA
Date: Mon, 3 Dec 2012 18:24:48 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B6F5FA4@xmb-rcd-x09.cisco.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033897C9BF@PRVPEXVS15.corp.twcable.com> <CALaySJLT=6RTZahqB1LO_Aw=7sAMiyrXK=xacwrBgLieZhqeDw@mail.gmail.com> <2671C6CDFBB59E47B64C10B3E0BD59230338A657EC@PRVPEXVS15.corp.twcable.com> <6.2.5.6.2.20121129105444.0b8d3400@resistor.net>
In-Reply-To: <6.2.5.6.2.20121129105444.0b8d3400@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.120]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <675F36C1B4D79A45BE1492BDA8999C0C@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 03 Dec 2012 18:24:54 -0000

On Nov 29, 2012, at 12:03 PM, SM wrote:

> According to some RFC:
>=20
>  "All relevant documents to be discussed at a session should be published
>   and available as Internet-Drafts at least two weeks before
>   a session starts."
>=20
> If the above was followed there shouldn't be any draft submissions during=
 the week a meeting is held.=20

Not sure I agree with that. A draft submitted during the indicated week isn=
't up for discussion that week, but it may easily be the start of a mailing=
 list discussion for a subsequent meeting, or it may be an update to a draf=
t as an outcome of discussion. I see both pretty regularly.=

From sm@resistor.net  Mon Dec  3 10:39:12 2012
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 45BCC21F8940 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 10:39:12 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UleaGU0Munsx for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 10:39:11 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CD921F8443 for <ietf@ietf.org>; Mon,  3 Dec 2012 10:39:11 -0800 (PST)
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 qB3Id3gR022895; Mon, 3 Dec 2012 10:39:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354559948; bh=yC4xpaePxFgy0B8QB/FEMJNt+i81MIJjJAiWymRpwgs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HfL5yUDpY3Vd/QCBvV86OBEsQHUrjphVJ7FUWCZ/kIvJW1iAUeolrGeKdtsBEu82H ThjE3qzDHGnKDQlFwIXnEgPW2pR1lbE4BI/7x29M/Uhdfd0zcguBiYYi3IdJ4Enkyi BB34lEj7gTJm/5nbny/eTGV6tdRFJNU6RMBsNjH4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354559948; i=@resistor.net; bh=yC4xpaePxFgy0B8QB/FEMJNt+i81MIJjJAiWymRpwgs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uccvLuk/XC3b5WS4pH+1b2/wX+/4luarKFNEQObM8FloBwFKL+P6sFiHLp8112ekN UvomTlc7m/eExwcvod8oiQKjvrR2h6C9Dpp8r2yBqN2/098+xzHboMVdwlZlYL5KSW BcPMcRuzlnuXe9hdG4C6rKQOX9c4xKLnR3UjOgIg=
Message-Id: <6.2.5.6.2.20121203093517.0a1bdc38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 03 Dec 2012 10:01:33 -0800
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
From: SM <sm@resistor.net>
Subject: Re: Simplifying our processes: Conference Calls
In-Reply-To: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net>
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.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: Mon, 03 Dec 2012 18:39:12 -0000

Hi Hannes,
At 07:41 03-12-2012, Hannes Tschofenig wrote:
>Why do we need to announce conference calls (or Jabber chats) on the 
>IETF announce mailing list? How likely is it that someone cares 
>about a working group effort, does not subscribe to the WG mailing 
>list, has not seen a poll about the date and time, and wants to 
>participate in the conference call? To me - this seems rather unlikely.

There are people contributing to a working group who are not 
subscribed to the mailing list.  There are probably people who are 
not actively following a working group who might attend a conference call.

>Could we please change that?

Sending an email through ietf-announce@ is not that much work [1] 
[2].  If you broadcast the announcement to the entire community it's 
public.  You don't have to worry about the questions you asked above 
or conspiracy theories.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/scim/current/msg00782.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg72510.html  


From hannes.tschofenig@gmx.net  Mon Dec  3 11:37:31 2012
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 D844021F8583 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 11:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level: 
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8iwDbxQtOp2 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 11:37:31 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id CAFF021F86A3 for <ietf@ietf.org>; Mon,  3 Dec 2012 11:37:30 -0800 (PST)
Received: (qmail invoked by alias); 03 Dec 2012 19:37:29 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.109]) [88.115.216.191] by mail.gmx.net (mp071) with SMTP; 03 Dec 2012 20:37:29 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19Whl5ubKRWxtKO70H4l9+vFqQ90GuE9vNk9CuKL/ Yg0RlROBXr9rLO
Subject: Re: Simplifying our processes: Conference Calls
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: <6.2.5.6.2.20121203093517.0a1bdc38@resistor.net>
Date: Mon, 3 Dec 2012 21:37:27 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CA77187-1B4C-4F62-9F62-00CD213690D8@gmx.net>
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <6.2.5.6.2.20121203093517.0a1bdc38@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 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: Mon, 03 Dec 2012 19:37:32 -0000

On Dec 3, 2012, at 8:01 PM, SM wrote:

> There are people contributing to a working group who are not =
subscribed to the mailing list.  There are probably people who are not =
actively following a working group who might attend a conference call.

Any data that supports your argument? Are there people subscribed to the =
IETF announce list who just wait for conference calls they can join.=20
With the same argument we should just forward every "interesting" mail =
from the working group just in case that someone on the IETF =
announcement list cares about it.=20

If you do not follow the mailing list how likely is it that you will =
understand the discussions during the conference call?=20

Ciao
Hannes




From bob.hinden@gmail.com  Mon Dec  3 11:59:17 2012
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 9218121F876E for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 11:59:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.71
X-Spam-Level: 
X-Spam-Status: No, score=-103.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytIPanje0jX3 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 11:59:17 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2923921F8675 for <ietf@ietf.org>; Mon,  3 Dec 2012 11:59:16 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so2039643pad.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 11:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=3LoA4uF0zrUHrQ9tpByFJDjOvKHgqb9cYYaVHPhQ3h4=; b=krOTzAkfdJ4TMJC4gvao0LUWd6arCmdq9oH4Kczwq06QZzBHeTq2eNZex1qL8ZJjJ1 DLf61V2Wnhpyh1YnSX6dxvgGldzwcmIOIFL8V5m7VHnxT+5AzncRiFjzpEq4d+P3NKkt afUrX3qev2KK8j64fiHQYe/7iltzEMO81ep9r94BHxW89X+CetG1uNq1qM2MLTtAKAl6 bTg9n8c9MFItlgQQ23VEf2p24nkktOMVbHRcEPvo+kDsKA77cx3PUf2FU3iSM32+5ROO NMRlV0A96gctw9kZ0F5kytxYWoIBKswfyqH7lKprJF35f47sSqDPPRcCI5k+F25VYbls g0WA==
Received: by 10.68.129.227 with SMTP id nz3mr31979983pbb.111.1354564756675; Mon, 03 Dec 2012 11:59:16 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id j9sm8548819paw.2.2012.12.03.11.59.14 (version=SSLv3 cipher=OTHER); Mon, 03 Dec 2012 11:59:15 -0800 (PST)
Subject: Re: Simplifying our processes: Conference Calls
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <4CA77187-1B4C-4F62-9F62-00CD213690D8@gmx.net>
Date: Mon, 3 Dec 2012 11:59:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7244502-DBCE-4162-A0D7-C012BC73FEFA@gmail.com>
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <6.2.5.6.2.20121203093517.0a1bdc38@resistor.net> <4CA77187-1B4C-4F62-9F62-00CD213690D8@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1283)
Cc: SM <sm@resistor.net>, 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, 03 Dec 2012 19:59:17 -0000

Hannes,

On Dec 3, 2012, at 11:37 AM, Hannes Tschofenig wrote:

>=20
> On Dec 3, 2012, at 8:01 PM, SM wrote:
>=20
>> There are people contributing to a working group who are not =
subscribed to the mailing list.  There are probably people who are not =
actively following a working group who might attend a conference call.
>=20
> Any data that supports your argument? Are there people subscribed to =
the IETF announce list who just wait for conference calls they can join.=20=

> With the same argument we should just forward every "interesting" mail =
from the working group just in case that someone on the IETF =
announcement list cares about it.=20
>=20
> If you do not follow the mailing list how likely is it that you will =
understand the discussions during the conference call?=20


If the announcement is sent to IETF announce, then people who are not =
subscribed to the mailing list can decide to participate by subscribing =
to the mailing list, reading the archive, read the drafts, and =
participate in the call.  If they never see the announcement, then this =
can't happen.

I don't see this as a worthwhile simplification to our process.

Thanks,
Bob



From jari.arkko@piuha.net  Mon Dec  3 13:16:08 2012
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 027E021F8538 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:16:08 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEIucf5yrlHw for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:16:07 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 28B7921F84D9 for <ietf@ietf.org>; Mon,  3 Dec 2012 13:16:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1A4BD2CC48; Mon,  3 Dec 2012 23:16:06 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5PUVPyVLC355; Mon,  3 Dec 2012 23:16:05 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 0E65B2CC43; Mon,  3 Dec 2012 23:16:04 +0200 (EET)
Message-ID: <50BD1694.1040208@piuha.net>
Date: Mon, 03 Dec 2012 23:16:04 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, =?UTF-8?B?Ik1hcnRpbiA=?= =?UTF-8?B?Si4gRMO8cnN0Ig==?= <duerst@it.aoyama.ac.jp>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com>
In-Reply-To: <50BC86B7.1010706@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
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, 03 Dec 2012 21:16:08 -0000

Brian, Martin,

> On 03/12/2012 06:01, Martin J. DÃ¼rst wrote:
>> One of the advantages of a standards organization such as the IETF is
>> cross-concern review. For the IETF, one very strong cross-concern is
>> security. Another one (also for my personally) is internationalization.
>> Another, more vague one, is general architecture. Early running code is
>> very often (not always) characterized by the fact that such
>> cross-concerns are actively or passively ignored.
> An excellent point. The fact that a hack works, and can be implemented,
> does not alter the fact that it's a hack. This is the sort of thing that
> cross-area review is supposed to look for. As a gen-art reviewer, I am
> sometimes surprised by what gets through to Last Call in the regular
> process - if the whole review process is squeezed down to a couple
> of weeks, we will definitely miss cross-area issues.

True.

>
> Encouraging running code is a Good Thing. Publishing sloppy specifications
> is a Bad Thing.

Yes. Of course, it is difficult tradeoff. No hard and fast rules here. You have to publish a timely spec to make an impact, but you also have to get it right. But how timely? How right?

>
> The Interop show network used to be a Very Good Thing. We've lost that,
> though I was delighted to see some actual running code at Bits-n-Bytes
> in Atlanta. More please. Maybe a prize for Best Demo?

I've been thinking about something along those lines. Following up in a second e-mail...

jari


From jari.arkko@piuha.net  Mon Dec  3 13:19:06 2012
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 6527621F8538 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:19:06 -0800 (PST)
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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EaUh3y4On6cL for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:19:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id E31FE21F84D9 for <ietf@ietf.org>; Mon,  3 Dec 2012 13:19:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 08A082CC48; Mon,  3 Dec 2012 23:19:05 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2qzfQxnfg4PQ; Mon,  3 Dec 2012 23:19:04 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5686F2CC43; Mon,  3 Dec 2012 23:19:04 +0200 (EET)
Message-ID: <50BD1747.9040904@piuha.net>
Date: Mon, 03 Dec 2012 23:19:03 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC5DA0.2030506@cisco.com> <50BC839A.1070503@cs.tcd.ie> <CAC4RtVBr_0x6NcKJ4OQO=GH4msuXxZ1W_ECW57-3FZAirWTzmw@mail.gmail.com> <50BCB71F.4060205@cs.tcd.ie> <CAC4RtVCg3w7Wtuau7dykC5QKCk9mg7Sz0UCeJ26VG1WB_ut7HQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCg3w7Wtuau7dykC5QKCk9mg7Sz0UCeJ26VG1WB_ut7HQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Mon, 03 Dec 2012 21:19:06 -0000

Barry,

> As I've said on the IESG list, I think this can
> be far better done with an IESG statement that says that
> implementation, testing, and deployment should be considered as we
> (the community and the IESG) evaluate documents.  Then we just make
> sure we facilitate the process instead of getting in the way of it.

+1

Jari


From jmh@joelhalpern.com  Mon Dec  3 13:36:38 2012
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 1590321F85C9 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.487
X-Spam-Level: 
X-Spam-Status: No, score=-102.487 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Z+ci0MFG9IW for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:36:37 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 598A821F85B8 for <ietf@ietf.org>; Mon,  3 Dec 2012 13:36:37 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 49F4D55807F for <ietf@ietf.org>; Mon,  3 Dec 2012 13:36:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 916F1181C36; Mon,  3 Dec 2012 13:36:35 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-71-161-50-174.clppva.btas.verizon.net [71.161.50.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id C8DC0181C34; Mon,  3 Dec 2012 13:36:34 -0800 (PST)
Message-ID: <50BD1B55.5020002@joelhalpern.com>
Date: Mon, 03 Dec 2012 16:36:21 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BCD637.3030009@acm.org> <50BCD962.3020007@cs.tcd.ie> <50BCDBFE.3080701@acm.org>
In-Reply-To: <50BCDBFE.3080701@acm.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
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: Mon, 03 Dec 2012 21:36:38 -0000

And I will strongly oppose any IETF policy that treats commercial or 
proprietary code differently from Open Source code.

Out mantra is "running code".  We try to stay out of people's business 
models.

The presence of a implementation is a useful measure.  The presence of 
interoperability between two independent implementations is clearly a 
much better measure.
But reading the code is not a good measure of the spec.  An implementer 
familiar with the discussions in the WG is likely to get right tings 
that are under-specified.  Such an implementation does not tell us 
anything about the quality of the spec.  Should we require an 
implementation done from the spec without talking to the authors or WG? 
  That would measure the spec better.  But would seem to be an 
unreasonable requiremet.

he IETF, to the degree it wants to encourage something, wants to 
encourage implementation.  It ought to be up to the implementors whether 
they see value in an open source, closed source, or some other form of 
implementation.

One could argue that it does not matter, since the experiment is not 
going to change anything.  But I will assume that it matters, and will 
change something.  If so, it should be "running code" that is the issue.

Yours,
Joel

PS: "Free" for whatever definition of "Free"distinct from Open Source 
the suggester meant, would seem to be completely irrelevant to the IETF.

On 12/3/2012 12:06 PM, Marc Petit-Huguenin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 12/03/2012 08:54 AM, Stephen Farrell wrote:
>>
>> On 12/03/2012 04:41 PM, Marc Petit-Huguenin wrote:
>>> I support this idea, but I think that free software should also be
>>> considered as part of this experiment (free software and open source are
>>> not synonymous). Using the acronym FOSS and defining it as Free or Open
>>> Source Software in the document would achieve this.
>>
>> Fair point. OTOH, there are folks who want to not require open-source too.
>> For now, I'd gone with "ideally open-source." As I said to Sam, let's deal
>> with that, if need be, at IETF LC.
>
> OK, but note that I will oppose for this experiment the use of software that
> is not either available in source form or accompanied with a conformance test
> suite.
>
>>
>> In the meantime, I've posted -01 [1] with a bunch of changes. Do let me
>> know if I forgot to ack someone and as before all comments (inevitable,
>> this being a process thing;-) are very welcome.
>>
>> Thanks, S.
>>
>> [1] http://tools.ietf.org/html/draft-farrell-ft-01
>>
>
>
> - --
> 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)
>
> iQIcBAEBCAAGBQJQvNv6AAoJECnERZXWan7EV3QP/2Tv/rn7+GSwK2KkB3RsnS00
> ryB5FH0drUdMr7c+TreHDXh/uR6HLYxB1Cg9rDd5CZQaSBQlTtwIKVUxMPOW805k
> Uf3/xi8d3DpXVTmlesMtmbT/GeE7S0hJ3wf6LUwl4OkctX8GMDNuaONNudarl3Qt
> sR+AJw8OU8KOFMqEn6fOqpLwY7OiQG3M6tuMwfNIm1Z0bHb/WAssF9l+J2ZTqq8L
> AmJpHPql65WVSPck+jRnYyNtfnSkVCmCQ1y5cMeNoEnm5tkEt5oeinsvDwEAWBB3
> 5YzbUb+q72SCEyTbeVOrwTU1cBU/CKzOH+8r0ykK51KlZ1acYetwh31U4h1jDpHd
> tNrwu1Z5wvKCa4b4dvzkiEBE83gAr6IGMDlPWNkEtotB1ZZd/MUpRNsSCzyivtl5
> zr1rwpMY/5w6LljGO4jN4ZXKtXErFovEQpTc+bUz9K23WYyZMkARehXZLkbEvpb8
> /MY1zGlgRSrGHr5Wn+k9egCeWqYjGNQedYpDcqWw7oQ5V956W+/AvKHo6jPGGweC
> wpW3Hm+AWc3gPZ2pgYYt8dVScscWLo0qDWW4daHwAqu0rvge7PUB8aVagE72fQUn
> fPEPhETD2QqZfXDeCtfNqOVS1/v+SYsAYxcGFYwu7NR51OROBkhMpWT5KDuaPp02
> OPRv2MwPcsanVoQ1uNfY
> =30oW
> -----END PGP SIGNATURE-----
>

From sm@resistor.net  Mon Dec  3 13:39:41 2012
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 0F43521F894F for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.635
X-Spam-Level: 
X-Spam-Status: No, score=-102.635 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEirqrmp1HBY for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 13:39:40 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2F621F85C9 for <ietf@ietf.org>; Mon,  3 Dec 2012 13:39:40 -0800 (PST)
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 qB3LdVYQ015691; Mon, 3 Dec 2012 13:39:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354570777; bh=W44vcz5l2yP775DTGWdeTy4Qg9u9sQqT0MBoTbMIdeg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3pELkPeGn+gDxe3aFSCMgw/ZLEWg4SL+eY2AhlCIhROz6IgManEVbkkiAIWMJNlyu wua0Zrnzw7/nkyPLBeyOeSPkxgC2bdc8bNhIP+iJ4TkeC5pQvNvo8wydA+vukL6MrJ QwwksoKBsz/xFZ2hGJvCeM7Z8aP6f+tPqV0AxhOs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1354570777; i=@resistor.net; bh=W44vcz5l2yP775DTGWdeTy4Qg9u9sQqT0MBoTbMIdeg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nzy6QCsaaj13vzwMH8pRvJjxEEiOfautDf3G8exMHYgSqPGpK1nmxxgzGFEYeRuN0 mHWZpayc6joHHfy/9tz6ILmfUu5hZZIx+3fWJxeWm5iV4vj8uFxetf7S93MQohPZVT cYwQhBc/jdL3+GdUOOENQBGFfkf0B3U7wEC4K+Sg=
Message-Id: <6.2.5.6.2.20121203123043.0a21d408@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 03 Dec 2012 13:27:50 -0800
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
From: SM <sm@resistor.net>
Subject: Re: Simplifying our processes: Conference Calls
In-Reply-To: <4CA77187-1B4C-4F62-9F62-00CD213690D8@gmx.net>
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <6.2.5.6.2.20121203093517.0a1bdc38@resistor.net> <4CA77187-1B4C-4F62-9F62-00CD213690D8@gmx.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: Mon, 03 Dec 2012 21:39:41 -0000

Hi Hannes,
At 11:37 03-12-2012, Hannes Tschofenig wrote:
>Any data that supports your argument? Are there people subscribed to 
>the IETF announce list who just wait for conference calls they can join.

Please do not read this as data.  There are about five messages daily 
about webfinger from non-subscribers.  I doubt that these individuals 
are subscribed to the IETF announce mailing list.

>With the same argument we should just forward every "interesting" 
>mail from the working group just in case that someone on the IETF 
>announcement list cares about it.

If I understood correctly it was a question of "meetings" and not 
"interesting" messages.

>If you do not follow the mailing list how likely is it that you will 
>understand the discussions during the conference call?

It's unlikely that I would be able to understand the discussions if I 
have not read the mailing list.

Regards,
-sm 


From jari.arkko@piuha.net  Mon Dec  3 14:03:56 2012
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 EA0B021F8960 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:03:56 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYPdieLxuduh for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:03:56 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id A3C2F21F895E for <ietf@ietf.org>; Mon,  3 Dec 2012 14:03:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F146E2CC48; Tue,  4 Dec 2012 00:03:54 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ysND_Es27yKc; Tue,  4 Dec 2012 00:03:53 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id CFEE02CC43; Tue,  4 Dec 2012 00:03:53 +0200 (EET)
Message-ID: <50BD21C9.1040602@piuha.net>
Date: Tue, 04 Dec 2012 00:03:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie>
In-Reply-To: <50BA64AB.3010106@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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: Mon, 03 Dec 2012 22:03:57 -0000

Stephen,

Thanks for proposing this. You know that I agree with you that improving =
IETF's ability to publish specifications relating to real code out there =
is important. It is important to come up with ideas in this space. I thin=
k there has been situations where IETF has strayed from the "rough consen=
sus and running code" model.

But of course following the running code is not always easy. I have some =
perspectives on this, both from the IESG side and as a document author wh=
o in some cases had running code. Obviously we want IETF's resources spen=
t on things that result in running code, and we want experiences from tha=
t running code reflected back into specifications. And we want those fast=
-running implementation teams to bring their specs to the IETF rather tha=
n publish them somewhere else.

But on the other side, there are issues. It is sometimes difficult to dis=
tinguish useless junk with several implementations from useful and stable=
 technology that is going to change the Internet and which also has sever=
al implementations. And it is difficult to guess whether an implementatio=
n is the beginning of something great or the by-product of someone's pet =
project that also produced the specs. In many cases it is very cheap to w=
rite an implementation. You can also easily build an implementation and f=
und a few other folks to build theirs. And even if you have independent i=
mplementations, I've seen cases where there are seven implementations tha=
t inter-operate but the spec is still unimplementable for outsiders.

If you want to support IETF work that has implementations better, you hav=
e to decide where your focus is in the overall process. I suspect that th=
e last calls make up a very small part of IETF's overall end-to-end ("dra=
ft-00-to-RFC") delay. I do not have good statistics of this at the moment=
, http://www.arkko.com/tools/lifecycle/wgdocs.html has some numbers from =
buggy code that has not been run since last spring. Those numbers seems t=
o indicate WG process times in the order of two years and LC/IESG times i=
n the order of half a year, plus some RFC editor time. Intuitively, the n=
umbers match my own experience, so maybe they are in the ballpark.

One of the issues is that it is very rare for document to sail through th=
e LC/IESG without any changes. From the same crappy statistics, http://ww=
w.arkko.com/tools/admeasurements/stat/goodprocessingtime_4.html and http:=
//www.arkko.com/tools/admeasurements/stat/processingtime_4.html that's ma=
ybe 10% of all documents; 20% in some cases but those drafts probably hav=
e some RFC Editor notes associated with them. A document that does not ch=
ange goes through quite fast, maybe in a month. A document that needs cha=
nge also needs discussion, debate, and waiting for a revision. Hence the =
half a year. Two weeks out of that? Not a big difference. Two weeks out o=
f 2-3 years for the entire spec development? Not noticeable.

All decisions involving how you give support or priority to running code =
involve difficult judgment calls. There's running code. Does that trump s=
omeone's opinion that the bits should be ordered differently? That the de=
sign should be changed to work better through NATs? That no security is n=
eeded? There is no hard and fast rule for these questions, you have to ev=
aluate what the situation is.

It is not easy to support running code as part of the IETF day-to-day pro=
cess. People test obviously, on their own. Many people bring implementati=
ons to IETF meetings. Some organize back room meetings to do even proper =
interops. We saw some code in bits-n-bytes, and there's been a few other =
demos as well. But interops are not within IETF scope. It is even difficu=
lt to acquire resources for testing in all cases. In Atlanta, we asked fo=
r a room the hallway was no longer sufficient. We did this in the last mi=
nute, got some well-deserved pushback from the NOC crew (who did a wonder=
ful job and supported us anyway - thanks). But we also got some unexpecte=
d pushback from the IESG, who among other things told us that they can't =
help us with a room in any way until the spec is officially a WG document=
=2E But to get to that state we'd need some testing to improve the spec a=
nd convince people that the stuff works. So catch 22. Luckily, we got a r=
oom from IPSO Alliance, who stepped up to help.

Anyway, all this puts me roughly in the same camp as Barry. How about doi=
ng this instead:

1) Write that IESG statement or new RFC that reminds everyone that they s=
hould seriously consider what running code tells us when they weigh issue=
s, decide to send documents forward, etc. Obviously we should not follow =
code blindly. Perhaps the statement could highlight some of the above iss=
ues, or the issues from Stephen's draft to make people aware of the compl=
exity of the matter.

2) Re-focus ourselves in the WG and IESG reviews on the stuff that actual=
ly matters. DISCUSSes on what's in the document header of the I-D... do n=
ot matter as much as whether the thing actually works, or is i18n capable=
 or secure. Yes, I know I've erred on this myself several times.

3) Remember that some of the most successful IETF specifications were thi=
ngs that were brought to us from the outside, with implementations and fi=
rst standards revisions already done. It is not a bad model. You do not a=
lways have to start with a committee. You can finish with a committee.

4) Find ways to support running code in all stages of the IETF process. C=
ould we support unofficial interops better in our meetings, or work with =
more interop organizations? Could we use bits-n-bytes to do more demos, a=
nd would this be useful in promoting running code?

Some more comments on details on your draft:

* The IPR return-to-WG process is actually part of existing operations fo=
r all drafts. Perhaps you could clarify this.

* I'm not sure why you have taken the position that the sponsoring AD doe=
s not have to vote Yes in these. I think that should be necessary even mo=
re than with other drafts. Were you thinking that there's some other AD w=
ho knows the case better? There are certainly cases where another AD know=
s more about a particular case than the one officially in charge of the W=
G. In those cases it might actually make sense for that other AD to take =
on the sponsoring role. But that seems orthogonal to fast tracking, and i=
s already happening.

* I think you have placed perhaps too much emphasis on verifying the soft=
ware. I think these are judgment calls, you figure out what is available,=
 what its functionality is, how it has been tested, and so on. It is hard=
 to codify that in a set of rules. Strict rules may actually rule out som=
e things that would be useful. For instance, would several proprietary im=
plementations with well-documented interop success qualify or not?

Jari



From rbonica@juniper.net  Mon Dec  3 14:34:00 2012
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 83FCE21F8939 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.245
X-Spam-Level: 
X-Spam-Status: No, score=-103.245 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eNin6DgcHQ2q for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:33:59 -0800 (PST)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id AF67421F88EB for <ietf@ietf.org>; Mon,  3 Dec 2012 14:33:59 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUL0o12VNLeZV+zqNxPm4GClOvxPw1Fm+@postini.com; Mon, 03 Dec 2012 14:33:59 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 3 Dec 2012 14:31:17 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Mon, 3 Dec 2012 14:31:17 -0800
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.140) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 3 Dec 2012 14:38:47 -0800
Received: from mail57-db3-R.bigfish.com (10.3.81.232) by DB3EHSOBE008.bigfish.com (10.3.84.28) with Microsoft SMTP Server id 14.1.225.23; Mon, 3 Dec 2012 22:31:03 +0000
Received: from mail57-db3 (localhost [127.0.0.1])	by mail57-db3-R.bigfish.com (Postfix) with ESMTP id 6E152401B4	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon,  3 Dec 2012 22:31:03 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -1
X-BigFish: PS-1(zz1418Izz1de0h1202h1d1ah1d2ahzz8275dh18602ehz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1155h)
Received: from mail57-db3 (localhost.localdomain [127.0.0.1]) by mail57-db3 (MessageSwitch) id 135457386180367_23591; Mon,  3 Dec 2012 22:31:01 +0000 (UTC)
Received: from DB3EHSMHS013.bigfish.com (unknown [10.3.81.251])	by mail57-db3.bigfish.com (Postfix) with ESMTP id 06E5938024B; Mon,  3 Dec 2012 22:31:01 +0000 (UTC)
Received: from BY2PRD0512HT001.namprd05.prod.outlook.com (157.56.238.5) by DB3EHSMHS013.bigfish.com (10.3.87.113) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 3 Dec 2012 22:30:59 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.199]) by BY2PRD0512HT001.namprd05.prod.outlook.com ([10.255.243.34]) with mapi id 14.16.0245.002; Mon, 3 Dec 2012 22:30:54 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: "gih@apnic.net" <gih@apnic.net>, Randy Bush <randy@psg.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Thread-Topic: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Thread-Index: Ac3Rpdqz1VUAff1MSW6LIgvP186FLQ==
Date: Mon, 3 Dec 2012 22:30:54 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501DBADD2@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%APNIC.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.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, 03 Dec 2012 22:34:00 -0000

Geoff, Randy,

Having reflected on your comments, I think that the two of you may be appro=
aching the same problem from two directions. I will try my best to articula=
te the problem. When we agree that we have a common understanding of the pr=
oblem, we can decide whether to fix draft-bonica or abandon it.

Geoff points out that each of the entries mentioned in draft-bonica can be =
characterized as one of the following:

- a special purpose address assignment
- a address reservation

All compliant IP implementations must respect special purpose address assig=
nments. As Randy puts it, special purpose address assignments should be bak=
ed into IP stacks.=20

However, the same is not true of address reservations. While operators may =
afford special treatment to packets that are sourced from or destined to re=
served addresses, these treatments should not be baked into IP implementati=
ons. They should be configurable.

Currently, there is nothing in draft-bonica that distinguishes between spec=
ial purpose address assignments and address reservations. If we were to con=
tinue with this draft, we would have to add a field that makes this distinc=
tion. Having added that field, we should also make clear that that field, a=
nd only that field, determines whether an address should be baked into IP s=
tacks?

Randy, Geoff, have I restated the problem accurately?


--------------------------
Ron Bonica
vcard:       www.bonica.org/ron/ronbonica.vcf




From stephen.farrell@cs.tcd.ie  Mon Dec  3 14:41:46 2012
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 4C20F21F883B for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.458
X-Spam-Level: 
X-Spam-Status: No, score=-102.458 tagged_above=-999 required=5 tests=[AWL=0.141, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xi6PpL0LXkbk for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:41:45 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7012F21F88C2 for <ietf@ietf.org>; Mon,  3 Dec 2012 14:41:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B9F4EBE3C; Mon,  3 Dec 2012 22:41:17 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qH4DvCqBKSd9; Mon,  3 Dec 2012 22:41:16 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.44.79.68]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 844F8BE49; Mon,  3 Dec 2012 22:41:13 +0000 (GMT)
Message-ID: <50BD2A89.2010400@cs.tcd.ie>
Date: Mon, 03 Dec 2012 22:41:13 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BD21C9.1040602@piuha.net>
In-Reply-To: <50BD21C9.1040602@piuha.net>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Mon, 03 Dec 2012 22:41:46 -0000

Hi Jari,

I agree with almost all of what you say. I think we only disagree
in two places, and perhaps more about tactics than anything else.

The first is whether or not its worthwhile addressing the specific
bit of process my draft tackles. I obviously do think it is, even
though you correctly note there's a very modest gain in time.

I think we also disagree as to whether or not an IESG statement
would have any impact - I don't think there would be any good
effect at all for any IESG statement on the topic I can envisage
that wouldn't require community consensus. And as we've seen in
the last couple of days, even my modest idea for an experiment has
generated lots of words and a hugely rough consensus if any.

That seems to be the fate of all process discussions. So my
conclusion is that the best way towards our shared goal is via
small steps such as are represented by my proposal.

I'll look at your specific comments at the end, thanks for those.

S

On 12/03/2012 10:03 PM, Jari Arkko wrote:
> Stephen,
> 
> Thanks for proposing this. You know that I agree with you that improving
> IETF's ability to publish specifications relating to real code out there
> is important. It is important to come up with ideas in this space. I
> think there has been situations where IETF has strayed from the "rough
> consensus and running code" model.
> 
> But of course following the running code is not always easy. I have some
> perspectives on this, both from the IESG side and as a document author
> who in some cases had running code. Obviously we want IETF's resources
> spent on things that result in running code, and we want experiences
> from that running code reflected back into specifications. And we want
> those fast-running implementation teams to bring their specs to the IETF
> rather than publish them somewhere else.
> 
> But on the other side, there are issues. It is sometimes difficult to
> distinguish useless junk with several implementations from useful and
> stable technology that is going to change the Internet and which also
> has several implementations. And it is difficult to guess whether an
> implementation is the beginning of something great or the by-product of
> someone's pet project that also produced the specs. In many cases it is
> very cheap to write an implementation. You can also easily build an
> implementation and fund a few other folks to build theirs. And even if
> you have independent implementations, I've seen cases where there are
> seven implementations that inter-operate but the spec is still
> unimplementable for outsiders.
> 
> If you want to support IETF work that has implementations better, you
> have to decide where your focus is in the overall process. I suspect
> that the last calls make up a very small part of IETF's overall
> end-to-end ("draft-00-to-RFC") delay. I do not have good statistics of
> this at the moment, http://www.arkko.com/tools/lifecycle/wgdocs.html has
> some numbers from buggy code that has not been run since last spring.
> Those numbers seems to indicate WG process times in the order of two
> years and LC/IESG times in the order of half a year, plus some RFC
> editor time. Intuitively, the numbers match my own experience, so maybe
> they are in the ballpark.
> 
> One of the issues is that it is very rare for document to sail through
> the LC/IESG without any changes. From the same crappy statistics,
> http://www.arkko.com/tools/admeasurements/stat/goodprocessingtime_4.html
> and http://www.arkko.com/tools/admeasurements/stat/processingtime_4.html
> that's maybe 10% of all documents; 20% in some cases but those drafts
> probably have some RFC Editor notes associated with them. A document
> that does not change goes through quite fast, maybe in a month. A
> document that needs change also needs discussion, debate, and waiting
> for a revision. Hence the half a year. Two weeks out of that? Not a big
> difference. Two weeks out of 2-3 years for the entire spec development?
> Not noticeable.
> 
> All decisions involving how you give support or priority to running code
> involve difficult judgment calls. There's running code. Does that trump
> someone's opinion that the bits should be ordered differently? That the
> design should be changed to work better through NATs? That no security
> is needed? There is no hard and fast rule for these questions, you have
> to evaluate what the situation is.
> 
> It is not easy to support running code as part of the IETF day-to-day
> process. People test obviously, on their own. Many people bring
> implementations to IETF meetings. Some organize back room meetings to do
> even proper interops. We saw some code in bits-n-bytes, and there's been
> a few other demos as well. But interops are not within IETF scope. It is
> even difficult to acquire resources for testing in all cases. In
> Atlanta, we asked for a room the hallway was no longer sufficient. We
> did this in the last minute, got some well-deserved pushback from the
> NOC crew (who did a wonderful job and supported us anyway - thanks). But
> we also got some unexpected pushback from the IESG, who among other
> things told us that they can't help us with a room in any way until the
> spec is officially a WG document. But to get to that state we'd need
> some testing to improve the spec and convince people that the stuff
> works. So catch 22. Luckily, we got a room from IPSO Alliance, who
> stepped up to help.
> 
> Anyway, all this puts me roughly in the same camp as Barry. How about
> doing this instead:
> 
> 1) Write that IESG statement or new RFC that reminds everyone that they
> should seriously consider what running code tells us when they weigh
> issues, decide to send documents forward, etc. Obviously we should not
> follow code blindly. Perhaps the statement could highlight some of the
> above issues, or the issues from Stephen's draft to make people aware of
> the complexity of the matter.
> 
> 2) Re-focus ourselves in the WG and IESG reviews on the stuff that
> actually matters. DISCUSSes on what's in the document header of the
> I-D... do not matter as much as whether the thing actually works, or is
> i18n capable or secure. Yes, I know I've erred on this myself several
> times.
> 
> 3) Remember that some of the most successful IETF specifications were
> things that were brought to us from the outside, with implementations
> and first standards revisions already done. It is not a bad model. You
> do not always have to start with a committee. You can finish with a
> committee.
> 
> 4) Find ways to support running code in all stages of the IETF process.
> Could we support unofficial interops better in our meetings, or work
> with more interop organizations? Could we use bits-n-bytes to do more
> demos, and would this be useful in promoting running code?
> 
> Some more comments on details on your draft:
> 
> * The IPR return-to-WG process is actually part of existing operations
> for all drafts. Perhaps you could clarify this.
> 
> * I'm not sure why you have taken the position that the sponsoring AD
> does not have to vote Yes in these. I think that should be necessary
> even more than with other drafts. Were you thinking that there's some
> other AD who knows the case better? There are certainly cases where
> another AD knows more about a particular case than the one officially in
> charge of the WG. In those cases it might actually make sense for that
> other AD to take on the sponsoring role. But that seems orthogonal to
> fast tracking, and is already happening.
> 
> * I think you have placed perhaps too much emphasis on verifying the
> software. I think these are judgment calls, you figure out what is
> available, what its functionality is, how it has been tested, and so on.
> It is hard to codify that in a set of rules. Strict rules may actually
> rule out some things that would be useful. For instance, would several
> proprietary implementations with well-documented interop success qualify
> or not?
> 
> Jari
> 
> 
> 
> 

From dwm@xpasc.com  Mon Dec  3 14:50:22 2012
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 F23C321F89AA for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:50:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.953
X-Spam-Level: 
X-Spam-Status: No, score=-3.953 tagged_above=-999 required=5 tests=[AWL=-2.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cLRbaKgPUdPo for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:50:11 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 1898621F899F for <ietf@ietf.org>; Mon,  3 Dec 2012 14:50:11 -0800 (PST)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 615313FBA2 for <ietf@ietf.org>; Mon,  3 Dec 2012 22:50:10 +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 qB3MoAeh007075 for <ietf@ietf.org>; Mon, 3 Dec 2012 14:50:10 -0800
Date: Mon, 3 Dec 2012 14:50:10 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: IETF-Discussion <ietf@ietf.org>
Subject: Re: Idea for a process experiment to reward running code...
In-Reply-To: <50BCD637.3030009@acm.org>
Message-ID: <alpine.LRH.2.01.1212031446410.7002@egate.xpasc.com>
References: <50BA64AB.3010106@cs.tcd.ie> <50BCD637.3030009@acm.org>
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.1+13-gbab1945
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: Mon, 03 Dec 2012 22:50:22 -0000

On Mon, 3 Dec 2012, Marc Petit-Huguenin wrote:


> I support this idea, but I think that free software should also be considered
> as part of this experiment (free software and open source are not synonymous).
>  Using the acronym FOSS and defining it as Free or Open Source Software in the
> document would achieve this.

By my understanding free is not applicable in that software can be free 
without the source being available. The key in my mind to the open source
sugestion is the ability of others to examine the actual code for coverage
of edge concerns or whatever. Open source is available today under many
license agreements. Free is not a requirement to achieve the review
objective.

From stephen.farrell@cs.tcd.ie  Mon Dec  3 14:53:30 2012
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 6389021F897C for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.468
X-Spam-Level: 
X-Spam-Status: No, score=-102.468 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8c51YatzLsk0 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 14:53:29 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 08FA521F8972 for <ietf@ietf.org>; Mon,  3 Dec 2012 14:53:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 20052BE3C; Mon,  3 Dec 2012 22:53:07 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbZ8Ndoye54o; Mon,  3 Dec 2012 22:53:06 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.44.79.68]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 67538BE36; Mon,  3 Dec 2012 22:53:06 +0000 (GMT)
Message-ID: <50BD2D52.2030105@cs.tcd.ie>
Date: Mon, 03 Dec 2012 22:53:06 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BCD637.3030009@acm.org> <alpine.LRH.2.01.1212031446410.7002@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1212031446410.7002@egate.xpasc.com>
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: Mon, 03 Dec 2012 22:53:30 -0000

On 12/03/2012 10:50 PM, David Morris wrote:
> 
> 
> On Mon, 3 Dec 2012, Marc Petit-Huguenin wrote:
> 
> 
>> I support this idea, but I think that free software should also be considered
>> as part of this experiment (free software and open source are not synonymous).
>>  Using the acronym FOSS and defining it as Free or Open Source Software in the
>> document would achieve this.
> 
> By my understanding free is not applicable in that software can be free 
> without the source being available. The key in my mind to the open source
> sugestion is the ability of others to examine the actual code for coverage
> of edge concerns or whatever. Open source is available today under many
> license agreements. Free is not a requirement to achieve the review
> objective.

Folks, can we *please* not rat-hole on this? If the proposal gets to
an IETF LC, then I'll make sure to try find some wording that works for
folks who've expressed divergent opinions on the topic before the
start of IETF LC. So if you care about this, I'd ask that you wait for
an IETF LC before diving in, since a) it doesn't matter until then and
b) I promise, I'll try get some wording that works for all before then.

Thanks,
Stephen.


From gih@apnic.net  Mon Dec  3 15:25:13 2012
Return-Path: <gih@apnic.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 2791A21F8970 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 15:25:13 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YGLHbUbDU74k for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 15:25:12 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 2B52221F896E for <ietf@ietf.org>; Mon,  3 Dec 2012 15:25:11 -0800 (PST)
Received: from 2001-44b8-1121-1a00-8047-fa9d-6338-f77f.static.ipv6.internode.on.net (2001-44b8-1121-1a00-8047-fa9d-6338-f77f.static.ipv6.internode.on.net [IPv6:2001:44b8:1121:1a00:8047:fa9d:6338:f77f]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id D363FB6746; Tue,  4 Dec 2012 09:25:08 +1000 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2501DBADD2@BY2PRD0512MB653.namprd05.prod.outlook.com>
Date: Tue, 4 Dec 2012 10:25:07 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <62AB342F-F2C0-4B06-B137-47CB7047BCB2@apnic.net>
References: <2CF4CB03E2AA464BA0982EC92A02CE2501DBADD2@BY2PRD0512MB653.namprd05.prod.outlook.com>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1499)
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, 03 Dec 2012 23:25:13 -0000

On 04/12/2012, at 9:30 AM, Ronald Bonica <rbonica@juniper.net> wrote:

> Geoff, Randy,
>=20
> Having reflected on your comments, I think that the two of you may be =
approaching the same problem from two directions. I will try my best to =
articulate the problem. When we agree that we have a common =
understanding of the problem, we can decide whether to fix draft-bonica =
or abandon it.
>=20
> Geoff points out that each of the entries mentioned in draft-bonica =
can be characterized as one of the following:
>=20
> - a special purpose address assignment
> - a address reservation
>=20
> All compliant IP implementations must respect special purpose address =
assignments. As Randy puts it, special purpose address assignments =
should be baked into IP stacks.=20
>=20
> However, the same is not true of address reservations. While operators =
may afford special treatment to packets that are sourced from or =
destined to reserved addresses, these treatments should not be baked =
into IP implementations. They should be configurable.
>=20
> Currently, there is nothing in draft-bonica that distinguishes between =
special purpose address assignments and address reservations. If we were =
to continue with this draft, we would have to add a field that makes =
this distinction. Having added that field, we should also make clear =
that that field, and only that field, determines whether an address =
should be baked into IP stacks?
>=20
> Randy, Geoff, have I restated the problem accurately?
>=20


I'd use the opposite terminology. e.g.:

  - I regard 0.0.0.0/8 as a "reservation", and should be baked into IP =
stacks

  - I regard 192.88.99.0/24 as a "special purpose assignment" and is =
configurable by IP stacks.

In IPv4 my understanding of the current set of "reservations" are:

  0.0.0.0/8
  127.0.0.0/8
  169.254.0.0/16
  224.0.0.0/4
  240.0.0.0/4

All others I would see as being special purpose assignments, given that =
they do not require special baked-in treatment by IP stacks.

My personal preference would be to:=20

--  record all special purpose assignments in a special purpose =
assignment registry, such as =
http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-speci=
al-registry.xml for Ipv4


-- record all reservations in the address protocol registry, such as =
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xml =
for Ipv4


regards,

   Geoff





From agmalis@gmail.com  Mon Dec  3 18:00:21 2012
Return-Path: <agmalis@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 CC5C721F8921 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 18:00:21 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Il3p2PmzDIv for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 18:00:21 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 07E6621F8923 for <ietf@ietf.org>; Mon,  3 Dec 2012 18:00:20 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so5717263ieb.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 18:00:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=klwEehYsoqPcooxirYYHaaMgUM7JnYB566HNcpdnZ2w=; b=UE+57YERAaMVthNC7ltZ+XhScOwNLEChKAriw8RS/Vt2WJj+hXGxHOEVxFFs7lzsoV sij+wJZ6b+ghIiGDuvZt+vcTaSiyHpcSPZUsm69zUV5DCHEcChnL+Awb2MB4zIo75HPG Pf8VV/JZ8vif5L9q6DdCH7d73wSNwkErDTZ0QBc288dLBKSKZmw2Bo9+Qbi5k5PZunSF J7C5iKo3PRUWjJgx2jihcyf7nY+X7WtIh9NeZpxl7E0Cjh4an4rh3tj15OaDtnAPAMev Mqse+GeTaTZHSPn0t4+Ni9uIhXUPJkkp35jVNKF0TroPdM2hjRtqmeVt1o6GLwDLcYHe IqVg==
Received: by 10.50.151.172 with SMTP id ur12mr1057415igb.44.1354586417074; Mon, 03 Dec 2012 18:00:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.35.195 with HTTP; Mon, 3 Dec 2012 17:59:56 -0800 (PST)
In-Reply-To: <20121203164849.14555.53508.idtracker@ietfa.amsl.com>
References: <20121203164849.14555.53508.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 4 Dec 2012 10:59:56 +0900
Message-ID: <CAA=duU3LbXZrcDSOx3F0BorS9vLg=nZup+3tDNN2i6taJwD6Ow@mail.gmail.com>
Subject: Re: I-D Action: draft-farrell-ft-01.txt
To: stephen.farrell@cs.tcd.ie
Content-Type: multipart/alternative; boundary=e89a8f3ba03135135304cffd3a52
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, 04 Dec 2012 02:00:21 -0000

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

Stephen,

Your goal is laudatory, but the devil will be in the details. For example,
you wrote:

   Note also that this experiment just needs an implementation that
   makes it possible for the WG chairs and responsible AD to verify (to
   the extent they chose) that the implementation matches the draft.

Will this require WG chairs and/or document shepherds to do a code review
to verify that the implementation and code match? A better criteria might
be that there be at least two independent implementations that successfully
interoperate.  That would also show greater WG interest than just a single
individual or organization.

Open source code is a plus, but shouldn't be a requirement, as such a
requirement might discourage some vendors from implementing.

Thanks,
Andy







On Tue, Dec 4, 2012 at 1:48 AM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>
>
>         Title           : A Fast-Track way to Proposed Standard with
> Running Code
>         Author(s)       : Stephen Farrell
>         Filename        : draft-farrell-ft-01.txt
>         Pages           : 9
>         Date            : 2012-12-03
>
> Abstract:
>    This memo proposes an optional fast-track way to get from a working
>    group document to IESG review that can be used for cases when a
>    working group chair believes that there is running code that
>    implements a working group Internet-Draft.  The basic idea is to do
>    all of working group last call, IETF last call and area director
>    review during the same two week period, and to impose a higher
>    barrier for comments that might block progress.  The motivation is to
>    have the IETF process have a built-in reward for running code,
>    consistent with the IETF's overall philosophy of running code and
>    rough consensus.  This version is solely proposed by the author (and
>    not the IESG) to attempt to ascertain if there is enough interest in
>    this to warrant trying out the idea as an RFC 3933 process
>    experiment.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-farrell-ft
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-farrell-ft-01
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-farrell-ft-01
>
>
> 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
>

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

Stephen,<br><br>Your goal is laudatory, but the devil will be in the detail=
s. For example, you wrote:<br><pre class=3D"">   Note also that this experi=
ment just needs an implementation that
   makes it possible for the WG chairs and responsible AD to verify (to
   the extent they chose) that the implementation matches the draft.
</pre>Will this require WG chairs and/or document shepherds to do a code re=
view to verify that the implementation and code match? A better criteria mi=
ght be that there be at least two independent implementations that successf=
ully interoperate.=A0 That would also show greater WG interest than just a =
single individual or organization.<br>

<br>Open source code is a plus, but shouldn&#39;t be a requirement, as such=
 a requirement might discourage some vendors from implementing.<br><br>Than=
ks,<br>Andy<br><br><br><br><br><br><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">

On Tue, Dec 4, 2012 at 1:48 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:in=
ternet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : A Fast-Track way to Proposed St=
andard with Running Code<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Stephen Farrell<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-farrell-ft-01.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 9<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-12-03<br>
<br>
Abstract:<br>
=A0 =A0This memo proposes an optional fast-track way to get from a working<=
br>
=A0 =A0group document to IESG review that can be used for cases when a<br>
=A0 =A0working group chair believes that there is running code that<br>
=A0 =A0implements a working group Internet-Draft. =A0The basic idea is to d=
o<br>
=A0 =A0all of working group last call, IETF last call and area director<br>
=A0 =A0review during the same two week period, and to impose a higher<br>
=A0 =A0barrier for comments that might block progress. =A0The motivation is=
 to<br>
=A0 =A0have the IETF process have a built-in reward for running code,<br>
=A0 =A0consistent with the IETF&#39;s overall philosophy of running code an=
d<br>
=A0 =A0rough consensus. =A0This version is solely proposed by the author (a=
nd<br>
=A0 =A0not the IESG) to attempt to ascertain if there is enough interest in=
<br>
=A0 =A0this to warrant trying out the idea as an RFC 3933 process<br>
=A0 =A0experiment.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-farrell-ft" target=3D"_bl=
ank">https://datatracker.ietf.org/doc/draft-farrell-ft</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-farrell-ft-01" target=3D"_blank=
">http://tools.ietf.org/html/draft-farrell-ft-01</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-farrell-ft-01" target=
=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-farrell-ft-01</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft" target=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d=
-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 target=3D"_blank">http://www.ietf.org/shadow.html</a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_blank">=
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
</blockquote></div><br></div>

--e89a8f3ba03135135304cffd3a52--

From agmalis@gmail.com  Mon Dec  3 18:01:40 2012
Return-Path: <agmalis@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 4DA0721F8805 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 18:01:40 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ONfLb05DyM6 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 18:01:39 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6E4C321F8596 for <ietf@ietf.org>; Mon,  3 Dec 2012 18:01:39 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so5719181ieb.31 for <ietf@ietf.org>; Mon, 03 Dec 2012 18:01:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=VxDuyKSRd2jBCdwoWXUnoVGrDVETg0J7lCe35wcAW74=; b=a1VF/NRHHiiSFowFNnZ/3oBzO9ywxFTQ4ZHJaSOJEw8nSKKuJDN7WRdnpJStp20S4u 4SN88WZmRjg9sKZA9Kqh1hwkRJt4C0+d+NIdr5zrrVzzOmozjnils/GU+eRjUGqASUiu k6ynby4u+R90wu5uZYQEe7H+9XRTeCXDGummxlDggmLaXKvi2kx9mYRW5orfMn3K4RV4 4Tt0MbWlc2Cgm45PIWNViNHf++kKXXoB9e2Ymj4hqYRyB812SNjP9AKLc66t2AwumsIp e8kdaPJCDI07WvBozekei3wkWyZdHK2oAo/HQpeKOoAt7hQiy4CZ2E7udrMQmZJ4zJYe IZfw==
Received: by 10.43.83.1 with SMTP id ae1mr9839950icc.24.1354586499019; Mon, 03 Dec 2012 18:01:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.35.195 with HTTP; Mon, 3 Dec 2012 18:01:18 -0800 (PST)
In-Reply-To: <CAA=duU3LbXZrcDSOx3F0BorS9vLg=nZup+3tDNN2i6taJwD6Ow@mail.gmail.com>
References: <20121203164849.14555.53508.idtracker@ietfa.amsl.com> <CAA=duU3LbXZrcDSOx3F0BorS9vLg=nZup+3tDNN2i6taJwD6Ow@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 4 Dec 2012 11:01:18 +0900
Message-ID: <CAA=duU2ZnQ2tBCUVq2rTzS4ymP5rgYgELy+eb+Ca=1tzJhcROA@mail.gmail.com>
Subject: Re: I-D Action: draft-farrell-ft-01.txt
To: stephen.farrell@cs.tcd.ie
Content-Type: multipart/alternative; boundary=bcaec519696d17758204cffd3f85
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, 04 Dec 2012 02:01:40 -0000

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

Whoops, I meant that the draft and implementation match, sorry about that.

Cheers,
Andy



On Tue, Dec 4, 2012 at 10:59 AM, Andrew G. Malis <agmalis@gmail.com> wrote:

> Stephen,
>
> Your goal is laudatory, but the devil will be in the details. For example,
> you wrote:
>
>    Note also that this experiment just needs an implementation that
>    makes it possible for the WG chairs and responsible AD to verify (to
>    the extent they chose) that the implementation matches the draft.
>
> Will this require WG chairs and/or document shepherds to do a code review
> to verify that the implementation and code match? A better criteria might
> be that there be at least two independent implementations that successfully
> interoperate.  That would also show greater WG interest than just a single
> individual or organization.
>
> Open source code is a plus, but shouldn't be a requirement, as such a
> requirement might discourage some vendors from implementing.
>
> Thanks,
> Andy
>
>
>
>
>
>
>
>
> On Tue, Dec 4, 2012 at 1:48 AM, <internet-drafts@ietf.org> wrote:
>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>         Title           : A Fast-Track way to Proposed Standard with
>> Running Code
>>         Author(s)       : Stephen Farrell
>>         Filename        : draft-farrell-ft-01.txt
>>         Pages           : 9
>>         Date            : 2012-12-03
>>
>> Abstract:
>>    This memo proposes an optional fast-track way to get from a working
>>    group document to IESG review that can be used for cases when a
>>    working group chair believes that there is running code that
>>    implements a working group Internet-Draft.  The basic idea is to do
>>    all of working group last call, IETF last call and area director
>>    review during the same two week period, and to impose a higher
>>    barrier for comments that might block progress.  The motivation is to
>>    have the IETF process have a built-in reward for running code,
>>    consistent with the IETF's overall philosophy of running code and
>>    rough consensus.  This version is solely proposed by the author (and
>>    not the IESG) to attempt to ascertain if there is enough interest in
>>    this to warrant trying out the idea as an RFC 3933 process
>>    experiment.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-farrell-ft
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-farrell-ft-01
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-farrell-ft-01
>>
>>
>> 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<https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft>directories:
>> http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>
>

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

Whoops, I meant that the draft and implementation match, sorry about that.<=
br><br>Cheers,<br>Andy<br><br><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Tue, Dec 4, 2012 at 10:59 AM, Andrew G. Malis <span dir=
=3D"ltr">&lt;<a href=3D"mailto:agmalis@gmail.com" target=3D"_blank">agmalis=
@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">Stephen,<br><br>Your goal is laudatory, but =
the devil will be in the details. For example, you wrote:<br><pre>   Note a=
lso that this experiment just needs an implementation that
   makes it possible for the WG chairs and responsible AD to verify (to
   the extent they chose) that the implementation matches the draft.
</pre>Will this require WG chairs and/or document shepherds to do a code re=
view to verify that the implementation and code match? A better criteria mi=
ght be that there be at least two independent implementations that successf=
ully interoperate.=A0 That would also show greater WG interest than just a =
single individual or organization.<br>


<br>Open source code is a plus, but shouldn&#39;t be a requirement, as such=
 a requirement might discourage some vendors from implementing.<br><br>Than=
ks,<br>Andy<div class=3D"HOEnZb"><div class=3D"h5"><br><br><br><br><br><br>

<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">
On Tue, Dec 4, 2012 at 1:48 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:in=
ternet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">


<br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : A Fast-Track way to Proposed St=
andard with Running Code<br>
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Stephen Farrell<br>
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-farrell-ft-01.txt<br>
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 9<br>
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2012-12-03<br>
<br>
Abstract:<br>
=A0 =A0This memo proposes an optional fast-track way to get from a working<=
br>
=A0 =A0group document to IESG review that can be used for cases when a<br>
=A0 =A0working group chair believes that there is running code that<br>
=A0 =A0implements a working group Internet-Draft. =A0The basic idea is to d=
o<br>
=A0 =A0all of working group last call, IETF last call and area director<br>
=A0 =A0review during the same two week period, and to impose a higher<br>
=A0 =A0barrier for comments that might block progress. =A0The motivation is=
 to<br>
=A0 =A0have the IETF process have a built-in reward for running code,<br>
=A0 =A0consistent with the IETF&#39;s overall philosophy of running code an=
d<br>
=A0 =A0rough consensus. =A0This version is solely proposed by the author (a=
nd<br>
=A0 =A0not the IESG) to attempt to ascertain if there is enough interest in=
<br>
=A0 =A0this to warrant trying out the idea as an RFC 3933 process<br>
=A0 =A0experiment.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-farrell-ft" target=3D"_bl=
ank">https://datatracker.ietf.org/doc/draft-farrell-ft</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-farrell-ft-01" target=3D"_blank=
">http://tools.ietf.org/html/draft-farrell-ft-01</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-farrell-ft-01" target=
=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-farrell-ft-01</a><br>
<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org" target=3D"_blank">I-D-Announce@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announceInternet-Draft=
" target=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 target=3D"_blank">http://www.ietf.org/shadow.html</a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" target=3D"_blank">=
ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--bcaec519696d17758204cffd3f85--

From duerst@it.aoyama.ac.jp  Mon Dec  3 21:47:22 2012
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 8831C21F8986 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 21:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.278
X-Spam-Level: 
X-Spam-Status: No, score=-100.278 tagged_above=-999 required=5 tests=[AWL=-0.488, 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLHvE-Leo5a7 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 21:47:22 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id C412921F8987 for <ietf@ietf.org>; Mon,  3 Dec 2012 21:47:21 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id qB45lGrN029570 for <ietf@ietf.org>; Tue, 4 Dec 2012 14:47:16 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 1ef2_95b7_0f18bea4_3dd6_11e2_9bf7_001d096c566a; Tue, 04 Dec 2012 14:47:15 +0900
Received: from [IPv6:::1] ([133.2.210.1]:56268) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S161B8DF> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 4 Dec 2012 14:47:16 +0900
Message-ID: <50BD8E60.5030206@it.aoyama.ac.jp>
Date: Tue, 04 Dec 2012 14:47:12 +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: Elwyn Davies <elwynd@dial.pipex.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp>	 <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom>
In-Reply-To: <1354545525.11916.744.camel@mightyatom>
Content-Type: text/plain; charset=UTF-8; format=flowed
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: Tue, 04 Dec 2012 05:47:22 -0000

On 2012/12/03 23:38, Elwyn Davies wrote:

> Given that there is also open source code, reviewers have the chance to
> take a look at that and see the degree of hackiness involved.

Well, yes. It's easy enough to evaluate stuff such as non-descriptive 
variable names, messy indenting, and weird comments.

But there's a catch here: There are so many programming languages that 
it's very well possible that the code is written in a language you don't 
understand. It may be using techniques that are totally accepted for 
that specific language, but in a way that is considered very hacky in 
the relevant community. Or something else. As an outsider, you may have 
no way to evaluate that.

Specs are in English (also a problem for some people, but I hope we can 
leave that to another thread :-), which is at least a single target.

Regards,   Martin.

From ynir@checkpoint.com  Mon Dec  3 22:02:07 2012
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 4B76021F89AB for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 22:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.444
X-Spam-Level: 
X-Spam-Status: No, score=-10.444 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e4LW+CTx8E-2 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 22:02:06 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DB4F421F8991 for <ietf@ietf.org>; Mon,  3 Dec 2012 22:02:05 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id qB461sLh020170; Tue, 4 Dec 2012 08:01:54 +0200
X-CheckPoint: {50BD919B-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.14]) by IL-EX10.ad.checkpoint.com ([194.29.34.147]) with mapi id 14.02.0318.004; Tue, 4 Dec 2012 08:01:54 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: I-D Action: draft-farrell-ft-01.txt
Thread-Topic: I-D Action: draft-farrell-ft-01.txt
Thread-Index: AQHN0XYfSp7GL8lNXkOJCDCwGptFHpgHwaoAgABDmAA=
Date: Tue, 4 Dec 2012 06:01:54 +0000
Message-ID: <4613980CFC78314ABFD7F85CC30277210EDD1DAC@IL-EX10.ad.checkpoint.com>
References: <20121203164849.14555.53508.idtracker@ietfa.amsl.com> <CAA=duU3LbXZrcDSOx3F0BorS9vLg=nZup+3tDNN2i6taJwD6Ow@mail.gmail.com>
In-Reply-To: <CAA=duU3LbXZrcDSOx3F0BorS9vLg=nZup+3tDNN2i6taJwD6Ow@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.194]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <151A29540B11BD4EBCDC8372E29C3F7A@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: Tue, 04 Dec 2012 06:02:07 -0000

Speaking of the devil in the details=85

On Dec 4, 2012, at 3:59 AM, "Andrew G. Malis" <agmalis@gmail.com>
 wrote:

> Stephen,
>=20
> Your goal is laudatory, but the devil will be in the details. For example=
, you wrote:
>    Note also that this experiment just needs an implementation that
>    makes it possible for the WG chairs and responsible AD to verify (to
>    the extent they chose) that the implementation matches the draft.
> Will this require WG chairs and/or document shepherds to do a code review=
 to verify that the implementation and code match? A better criteria might =
be that there be at least two independent implementations that successfully=
 interoperate.  That would also show greater WG interest than just a single=
 individual or organization.

Define "independent". If the draft author contributes to two open source im=
plementations, does it count as independent? What if one author contributes=
 to an open source implementation, the other author implements it in her co=
mpany's product, and they claim interoperability?  That doesn't say much ab=
out the quality of the spec, other than that the authors understand it.

> Open source code is a plus, but shouldn't be a requirement, as such a req=
uirement might discourage some vendors from implementing.
>=20
> Thanks,
> Andy
>=20


From julian.reschke@gmx.de  Mon Dec  3 23:35:00 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFA621F89B0 for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 23:35:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.064
X-Spam-Level: 
X-Spam-Status: No, score=-102.064 tagged_above=-999 required=5 tests=[AWL=-0.535, BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P39qbz1SsmGd for <ietf@ietfa.amsl.com>; Mon,  3 Dec 2012 23:35:00 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 008BD21F89BF for <ietf@ietf.org>; Mon,  3 Dec 2012 23:34:59 -0800 (PST)
Received: (qmail invoked by alias); 04 Dec 2012 07:34:58 -0000
Received: from unknown (EHLO [172.24.113.175]) [192.147.117.12] by mail.gmx.net (mp039) with SMTP; 04 Dec 2012 08:34:58 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19QBvQxaaVQ3gQv8KwI8pwdF6mN/mcx8SPFlpayAe 99h4RGXrwCyOom
Message-ID: <50BD09B8.4000905@gmx.de>
Date: Mon, 03 Dec 2012 21:21:12 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]> <50B8CC84.70603@pi.nu> <18C4713424DC63629B268A03@[192.168.6.112]> <0la9tydi03.fsf@wjh.hardakers.net> <7EB1F9A9-5E55-45EB-9AB5-42973EFCDEF5@bbn.com>
In-Reply-To: <7EB1F9A9-5E55-45EB-9AB5-42973EFCDEF5@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Tue, 04 Dec 2012 07:35:01 -0000

On 2012-11-30 20:16, Richard Barnes wrote:
>
> On Nov 30, 2012, at 2:10 PM, Wes Hardaker <wjhns1@hardakers.net> wrote:
>
>> John C Klensin <john-ietf@jck.com> writes:
>>
>>> I think changing the default is fine.  I'd also be reluctant to
>>> see the "normal" HTML version go away immediately but would be
>>> especially reluctant to see the plain text version go away or
>>> even become less accessible (require more clicks or searching to
>>> navigate too).
>>
>> I suspect we can all agree that this would be optimal:
>>
>> 1) have the tools version be the default (my original statement)
>> 2) have the html version still present
>> 3) have the text version still present
>> 4) produce an xml version for better parsing
>>    (ever try and write an agenda app? Half your time is spent writing a
>>    .txt or .html parser)
>
> s/xml/json/
>
> Ever try writing an XML app?  Half your time is spent writing a .xml parser.

Hahaha.

Best regards, Julian



From hannes.tschofenig@nsn.com  Tue Dec  4 00:29:06 2012
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 170B021F8681 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 00:29:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.45
X-Spam-Level: 
X-Spam-Status: No, score=-106.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZ-+x4Ox46ss for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 00:29:05 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 46E3021F848B for <ietf@ietf.org>; Tue,  4 Dec 2012 00:29:05 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id qB48SxFt020674 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Dec 2012 09:28:59 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id qB48SvQa028743; Tue, 4 Dec 2012 09:28:59 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Dec 2012 09:28:58 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: Simplifying our processes: Conference Calls
Date: Tue, 4 Dec 2012 10:28:08 +0200
Message-ID: <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net>
In-Reply-To: <50BCCE1D.5070001@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Simplifying our processes: Conference Calls
Thread-Index: Ac3RcFLtjBhzd4fYSDK6tH6OyK4/6gAiJ3FA
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <50BCCE1D.5070001@gmail.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Brian E Carpenter" <brian.e.carpenter@gmail.com>, "Hannes Tschofenig" <hannes.tschofenig@gmx.net>
X-OriginalArrivalTime: 04 Dec 2012 08:28:58.0108 (UTC) FILETIME=[67BC7BC0:01CDD1F9]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1504
X-purgate-ID: 151667::1354609741-00006291-AE505E3A/0-0/0-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: Tue, 04 Dec 2012 08:29:06 -0000

SGkgQnJpYW4sIA0KDQoNCj4gVGhlIHBvaW50IGlzIHRoYXQgd2Ugd29yayBpbiBwdWJsaWMsIHNv
IHRoZSB3aG9sZSBjb21tdW5pdHkgc2hvdWxkDQo+IGtub3cuDQoNCldvcmtpbmcgZ3JvdXAgbWFp
bGluZyBsaXN0cyBhcmUgYWxzbyBwdWJsaWMuIA0KDQoNCj4gSSByZWd1bGFybHkgYXR0ZW5kIFdH
IG1lZXRpbmdzIHdoZXJlIEkgYW0gbm90IHN1YnNjcmliZWQgLSBpdCdzIG9uZSBvZg0KPiB0aGUN
Cj4gc2lkZSBiZW5lZml0cyBvZiB0aGUgd2Vlay1sb25nIG1lZXRpbmdzIC0gYW5kIHdobydzIHRv
IHNheSB0aGF0IEkgbWlnaHQNCj4gbm90DQo+IHdhbnQgdG8gZHJvcCBpbnRvIE9BdXRoIHRvbz8N
Cg0KQXJlIHlvdSB0YWxraW5nIGFib3V0IElFVEYgbWVldGluZ3M/IEkgYW0gdGFsa2luZyBhYm91
dCBjb25mZXJlbmNlIGNhbGxzIGhlcmUuIA0KDQpBcmUgeW91IHJlZ3VsYXJseSBqb2luaW5nIGNv
bmZlcmVuY2UgY2FsbHMgb2Ygd29ya2luZyBncm91cHMgd2hlcmUgeW91IGFyZSBub3Qgc3Vic2Ny
aWJlZCB0byB0aGUgbWFpbGluZyBsaXN0cz8NCg0KPiANCj4gU3VwcG9zZSBJIGhhcHBlbmVkIHRv
IG5vdGljZSAoSSBhbSBtYWtpbmcgdGhpcyB1cCkgdGhhdCB0aGUgZm9vYmFyIFdHDQo+IGhhcw0K
PiBkZWNpZGVkIHRvIHVzZSB0aGUgSVB2NiBGbG93IExhYmVsIGZvciBhbiB1bmludGVuZGVkIHB1
cnBvc2U/IEknZCBsaWtlDQo+IHRvIGtub3cgaWYgdGhleSBhcmUgZ29pbmcgdG8gaGF2ZSBhIGNv
bmYgY2FsbCwgc28gdGhhdCBJIGNhbiBleHBsYWluDQo+IFJGQyA2NDM3IHRvIHRoZW0uIE90aGVy
d2lzZSwgSSBoYXZlIG5vIGludGVyZXN0IGluIGZvb2Jhci4NCkhvdyB3b3VsZCB5b3UgZmluZCB0
aGlzIG91dCBmcm9tIHRoZSBhbm5vdW5jZW1lbnQgb2YgdGhlIGNvbmZlcmVuY2UgY2FsbCBnaXZl
biB0aGF0IHRoZSBhZ2VuZGEgZG9lcyBub3QgaGF2ZSB0byBhbm5vdW5jZWQgYXQgdGhlIHNhbWUg
dGltZT8gKHVubGVzcyB5b3Ugam9pbiBldmVyeSBjb25mZXJlbmNlIGNhbGwgdG8gZmlndXJlIG91
dCB3aGV0aGVyIHRoZXJlIGlzIHNvbWV0aGluZyBvZiBpbnRlcmVzdCBmb3IgeW91PykNCg0KQ2lh
bw0KSGFubmVzDQoNCg==

From joelja@bogus.com  Tue Dec  4 00:39:15 2012
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 AC46D21F88BB for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 00:39:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.506
X-Spam-Level: 
X-Spam-Status: No, score=-102.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l2tBBW90Kaih for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 00:39:15 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 19DAA21F85DB for <ietf@ietf.org>; Tue,  4 Dec 2012 00:39:15 -0800 (PST)
Received: from joels-MacBook-Air.local (c-98-207-206-4.hsd1.ca.comcast.net [98.207.206.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id qB48d1Eb031151 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 4 Dec 2012 08:39:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <50BDB6A0.8000201@bogus.com>
Date: Tue, 04 Dec 2012 00:38:56 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:18.0) Gecko/20121128 Thunderbird/18.0
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Subject: Re: Simplifying our processes: Conference Calls
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <50BCCE1D.5070001@gmail.com> <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net>
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.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 04 Dec 2012 08:39:07 +0000 (UTC)
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, 04 Dec 2012 08:39:15 -0000

On 12/4/12 12:28 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
> Hi Brian,
>
>
>> The point is that we work in public, so the whole community should
>> know.
> Working group mailing lists are also public.
>
>
>> I regularly attend WG meetings where I am not subscribed - it's one of
>> the
>> side benefits of the week-long meetings - and who's to say that I might
>> not
>> want to drop into OAuth too?
> Are you talking about IETF meetings? I am talking about conference calls here.
>
> Are you regularly joining conference calls of working groups where you are not subscribed to the mailing lists?

I belive you're drawing a distinction between conference call and 
virtual interim which does not presently exist. It could, but doesn't.

>
>> Suppose I happened to notice (I am making this up) that the foobar WG
>> has
>> decided to use the IPv6 Flow Label for an unintended purpose? I'd like
>> to know if they are going to have a conf call, so that I can explain
>> RFC 6437 to them. Otherwise, I have no interest in foobar.
> How would you find this out from the announcement of the conference call given that the agenda does not have to announced at the same time? (unless you join every conference call to figure out whether there is something of interest for you?)
>
> Ciao
> Hannes
>
>


From pars.mutaf@gmail.com  Tue Dec  4 01:18:04 2012
Return-Path: <pars.mutaf@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 75A9E21F85AC for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 01:18:03 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PpbtiA1rwKaH for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 01:18:02 -0800 (PST)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id 16A5C21F85A5 for <ietf@ietf.org>; Tue,  4 Dec 2012 01:18:01 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id l1so4609111vba.27 for <ietf@ietf.org>; Tue, 04 Dec 2012 01:18:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=yRAIs1A3PhM3CSOnQd/2LSoSVreIbHPEWb7SVU4WgEE=; b=dc3OQxKv6qUA22xtYQp9hog6eIxL5du6/WZNi99fOOB8lrEH2jLb6YeNsBHebB47kZ m9Qx9ERZgvSLn6SlpEMiEIHsAt9xXVpQkref0+Iv2ApjnfXQjiPxCgFMr68NglelbTRE zw8iBNhBgJneafqDYPgB8mW8PlVsaoMHQfIyHYabBx1XJwhOg6ZA7U4UX6t7YuJxpbGY QCxMWeulnq9DN6c9z42HDxj1T3T4gjytKu26Rr6klK8+8eD0hUjvTzK5RSN6rOxCsU2n pdE07RtBVllfqaAZgF2KrwkdBmD8J7BGbFLHrhwU9Tz8vjxWVtt3U8UMhqR1xUxMcq6g KtGw==
MIME-Version: 1.0
Received: by 10.52.98.36 with SMTP id ef4mr1821144vdb.104.1354612680435; Tue, 04 Dec 2012 01:18:00 -0800 (PST)
Received: by 10.59.1.3 with HTTP; Tue, 4 Dec 2012 01:18:00 -0800 (PST)
Date: Tue, 4 Dec 2012 11:18:00 +0200
Message-ID: <CACQuieY9PBbWZFyEYF8dUqFB21Mv5zEGEe8NoMbipbEXdxOgmw@mail.gmail.com>
Subject: The flower standard
From: Pars Mutaf <pars.mutaf@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=20cf307f3434a0271f04d003572d
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 09:21:49 -0000

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

Dear all,

FYI, I designed the following standard myself. It completes IETF RFC 3161.

www.flower-standard.org

Cheers,
Pars Mutaf

--20cf307f3434a0271f04d003572d
Content-Type: text/html; charset=ISO-8859-1

Dear all, <br><br>FYI, I designed the following standard myself. It completes IETF RFC 3161.<br><br><a href="http://www.flower-standard.org">www.flower-standard.org</a><br clear="all"><br>Cheers, <br>Pars Mutaf<br>

--20cf307f3434a0271f04d003572d--

From pars.mutaf@gmail.com  Tue Dec  4 02:19:40 2012
Return-Path: <pars.mutaf@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 E221B21F8968 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 02:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.489
X-Spam-Level: 
X-Spam-Status: No, score=-3.489 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aC8CVMBvibEA for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 02:19:39 -0800 (PST)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id A699D21F8750 for <ietf@ietf.org>; Tue,  4 Dec 2012 02:19:39 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id l1so4706472vba.27 for <ietf@ietf.org>; Tue, 04 Dec 2012 02:19:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=N23oBNg5ZluKezG8DG/TXAU82Z3qOpLLiWtZjIsg7qo=; b=j14y4ZBkbe+BAokJOzrnGR1B8ftI5Us07Ewdz+bqH8sHQkSkNamfg0RuQygENneamI w8X+X6bAxjYrwYryKyTRKbSNSba3VuKezERLxSUqcOdbeN0zaopNY+wCxmcmKYwYn6zk EpRUUW8WhOr6lfFwm1bMROfhl2wyhiatovSbgXKYr1O7giV0XOhhbJ9KgLO3iVyWBhPm d+BxBsUUY4gNS07V4tRUmuB+qkWmnK3tqSmmwr5yPPH36g13V3L+ExtDtDgUXMuk+4Z5 Tfm03iU6bRLNGwz/2fYtwec62E7qnWw/1x8stZcZj3taWhsGlXS3f3QNNiW8COXL1U93 jikA==
MIME-Version: 1.0
Received: by 10.52.33.228 with SMTP id u4mr9763994vdi.4.1354616379003; Tue, 04 Dec 2012 02:19:39 -0800 (PST)
Received: by 10.59.1.3 with HTTP; Tue, 4 Dec 2012 02:19:38 -0800 (PST)
In-Reply-To: <CACQuieY9PBbWZFyEYF8dUqFB21Mv5zEGEe8NoMbipbEXdxOgmw@mail.gmail.com>
References: <CACQuieY9PBbWZFyEYF8dUqFB21Mv5zEGEe8NoMbipbEXdxOgmw@mail.gmail.com>
Date: Tue, 4 Dec 2012 12:19:38 +0200
Message-ID: <CACQuieZFm1yWoYYvWOPd5g8MOyYzQw1WKrTmU=fNxBJ+dOo1xg@mail.gmail.com>
Subject: Re: The flower standard
From: Pars Mutaf <pars.mutaf@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=20cf307d03c213d28e04d004341f
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 10:19:41 -0000

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

For facebook users:
http://www.facebook.com/FlowerStandard

On Tue, Dec 4, 2012 at 11:18 AM, Pars Mutaf <pars.mutaf@gmail.com> wrote:

> Dear all,
>
> FYI, I designed the following standard myself. It completes IETF RFC 3161.
>
> www.flower-standard.org
>
> Cheers,
> Pars Mutaf
>

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

For facebook users: <br><a href=3D"http://www.facebook.com/FlowerStandard">=
http://www.facebook.com/FlowerStandard</a><br><br><div class=3D"gmail_quote=
">On Tue, Dec 4, 2012 at 11:18 AM, Pars Mutaf <span dir=3D"ltr">&lt;<a href=
=3D"mailto:pars.mutaf@gmail.com" target=3D"_blank">pars.mutaf@gmail.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear all, <br><br>FYI, I designed the follow=
ing standard myself. It completes IETF RFC 3161.<br><br><a href=3D"http://w=
ww.flower-standard.org" target=3D"_blank">www.flower-standard.org</a><br cl=
ear=3D"all">
<br>Cheers, <br>Pars Mutaf<br>
</blockquote></div><br>

--20cf307d03c213d28e04d004341f--

From brian.e.carpenter@gmail.com  Tue Dec  4 02:23:45 2012
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 6DA7521F8750 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 02:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LbMhkCqh4zVj for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 02:23:45 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id B2A7621F85D5 for <ietf@ietf.org>; Tue,  4 Dec 2012 02:23:44 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so1661375wey.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 02:23:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AfKCmjZ+OsztEP8dA3HyziEBjg/OvmIHuXgIXhM8Wck=; b=iq5IfWs23pFnVQU8ibUNdVERiMicVwobLxtpppAozwHyQm5cC/Q0PJSJB7AwELuz2n z/k/0PvWJdzJDNlje64hxTd4pYmJU4iqqP/DfxKyA/akMNxTsF/vgIiTKUVHPyenoM60 XKMYMcqEELkBxbEM3UIPuI2VSAsnNgHzJ1bvQmW2pzIEEvQbxcxnHO8S1f1mcLxwPV9E zTlZCqzzCWxAntHcUakeld5QId6M1PRHE0qqpQZMWA7oG8BaEeiyrsaNgvtFxHTG5WTj x01p+nJ0VKS4ai3yrgctaq0Umlqjxn3rgg8oipg0MCDhZle+K1p08NdZMT3bhtr/KzJc 5VLQ==
Received: by 10.216.27.135 with SMTP id e7mr4216680wea.164.1354616623793; Tue, 04 Dec 2012 02:23:43 -0800 (PST)
Received: from [128.232.110.102] (c102.al.cl.cam.ac.uk. [128.232.110.102]) by mx.google.com with ESMTPS id p2sm1201838wic.7.2012.12.04.02.23.42 (version=SSLv3 cipher=OTHER); Tue, 04 Dec 2012 02:23:43 -0800 (PST)
Message-ID: <50BDCF33.5020403@gmail.com>
Date: Tue, 04 Dec 2012 10:23:47 +0000
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: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Subject: Re: Simplifying our processes: Conference Calls
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <50BCCE1D.5070001@gmail.com> <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net>
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, 04 Dec 2012 10:23:45 -0000

Hannes,

On 04/12/2012 08:28, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
> Hi Brian, 
> 
> 
>> The point is that we work in public, so the whole community should
>> know.
> 
> Working group mailing lists are also public. 

Well yes, but we are talking here about (virtual) meetings.

> 
>> I regularly attend WG meetings where I am not subscribed - it's one of
>> the
>> side benefits of the week-long meetings - and who's to say that I might
>> not
>> want to drop into OAuth too?
> 
> Are you talking about IETF meetings? I am talking about conference calls here. 

There's no difference in principle.

> 
> Are you regularly joining conference calls of working groups where you are not subscribed to the mailing lists?

No. My point is that I have the right to. If not, it's a design team, and
that's a different discussion.

>> Suppose I happened to notice (I am making this up) that the foobar WG
>> has
>> decided to use the IPv6 Flow Label for an unintended purpose? I'd like
>> to know if they are going to have a conf call, so that I can explain
>> RFC 6437 to them. Otherwise, I have no interest in foobar.
> How would you find this out from the announcement of the conference call given that the agenda does not have to announced at the same time? (unless you join every conference call to figure out whether there is something of interest for you?)

I assume that the announcement would point to the agenda. Or I could look
at the WG mail archive at that point. In any case, I couldn't complain
later that the discussion had been kept private.

I don't see that informing the secretariat about virtual interims is a
significant burden on WG Chairs, compared to all the other work
involved.

    Brian

     Brian

From randy@psg.com  Tue Dec  4 04:09:12 2012
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 6E68921F8AA2 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 04:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bAfODZ6YZnRN for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 04:09:12 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 1BEBE21F86EE for <ietf@ietf.org>; Tue,  4 Dec 2012 04:09:12 -0800 (PST)
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 1TfrJC-000GJV-9U; Tue, 04 Dec 2012 12:09:06 +0000
Date: Tue, 04 Dec 2012 07:09:07 -0500
Message-ID: <m2r4n6f28s.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: =?ISO-8859-1?Q?=22Martin_J=2E_D=FCrst=22?= <duerst@it.aoyama.ac.jp>
Subject: Re: Idea for a process experiment to reward running code...
In-Reply-To: <50BD8E60.5030206@it.aoyama.ac.jp>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <50BD8E60.5030206@it.aoyama.ac.jp>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 12:09:12 -0000

>> Given that there is also open source code, reviewers have the chance
>> to take a look at that and see the degree of hackiness involved.
> 
> Well, yes. It's easy enough to evaluate stuff such as non-descriptive
> variable names, messy indenting, and weird comments.
> 
> But there's a catch here: There are so many programming languages that 
> it's very well possible that the code is written in a language you don't 
> understand. 

i think we're ratholing here.  the point i get is that, if there is open
source code that suppliments the drafts sufficiently to lend confidence
in the implementability and implementation, then progress might be
accelerated.

notice the if

randy

From tjc@ecs.soton.ac.uk  Tue Dec  4 05:29:59 2012
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 3FA8A21F8629 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 05:29:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWfhoe9eW6Jx for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 05:29:58 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 3110E21F85D5 for <ietf@ietf.org>; Tue,  4 Dec 2012 05:29:50 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id qB4DTkSb006788 for <ietf@ietf.org>; Tue, 4 Dec 2012 13:29:46 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk qB4DTkSb006788
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1354627786; bh=n/DixmxQHqCx0gn0OwJ151HYXmM=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=gGRsVWMzrhYRd3/EBcSUUfAhPWQQNlMiUfrsSCsyIL/PS4mXmf5bBSEI4W5QUMhj4 2qIAXFGNhXCYxd3vSknegGGi+hiccVBNX+KX+dSvXB1rR6Ty0rn2lBUJBO4taixb/L Cn/wzlAPbkP+2rDM1KNMrTD4fj6XRGEDFF/5VG30=
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 oB3DYk0430644510C8 ret-id none; Tue, 04 Dec 2012 13:29:46 +0000
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 qB4DTeIm018404 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 4 Dec 2012 13:29:41 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Useful slide tex (was - Re: English spoken here)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B6F5F2C@xmb-rcd-x09.cisco.com>
Date: Tue, 4 Dec 2012 13:29:42 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ba2897928cf23777aa76076399e696f4oB3DYk03tjc|ecs.soton.ac.uk|F7707BE9-79FA-4AA4-AE1A-9D4DB822BA6D@ecs.soton.ac.uk>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21! D.6090403@bogus.com> <8C48B86A895913448548E6D15DA7553B6F5F2C@xmb-rcd-x09.cisco.com> <F7707BE9-79FA-4AA4-AE1A-9D4DB822BA6D@ecs.soton.ac.uk>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=oB3DYk043064451000; tid=oB3DYk0430644510C8; client=relay,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: qB4DTkSb006788
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 13:29:59 -0000

On 3 Dec 2012, at 18:11, Fred Baker (fred) <fred@cisco.com> wrote:

> I agree with the notion that the primary purpose of the meeting is =
discussion. What you and I tell those who present in v6ops is that we =
want the presentation to guide and support a discussion, and anything =
that is pure presentation should take no more than half of the time =
allotted to them. I don't see that the tool is the problem, it's the =
user of the tool, and we all vary in our presentation/discussion skills.

Exactly. If the "presentation" is one slide listing the key changes in =
the document since the last revision/meeting, and one slide per key =
question/issue being asked of the room, then that should help facilitate =
good discussion, not hinder it.

What doesn't work is a 15 minute presentation of the current contents of =
a draft that leaves a couple of minutes for questions.

It's not the tool, it's how it's used.

And fwiw I think Fred and Joel have done a decent job of this in v6ops, =
and one of the things that's helped there is trimming out drafts that =
don't have evidence of a decent level of mail list discussion.

Tim


From abdussalambaryun@gmail.com  Tue Dec  4 05:32:36 2012
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 F2FED21F8659 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 05:32:35 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CklSXGVIcKq2 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 05:32:34 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 494A521F86EE for <ietf@ietf.org>; Tue,  4 Dec 2012 05:32:34 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so3359621vcb.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 05:32:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=xytfxVDt+n1bErxEwSUY04ClWREtgUmqDmigrg8mtoY=; b=nC4rv+MWxniDlPtQ9HW8pbN/ppYGbHzKCSVSBk4GPJDs/asgoxbNmv8uqMrWNG6AkI KCRZasmomh0HhY6oZg6WZ4jY19UgedaC/EIQBzZ7IxHWf2X6bf7Y9HycPK+WvQeaO7/i E9gfQwXEEMGFDPfuKkVNl3cZobkLkvBokXkratohUIxiNLF9J3UArTRCguOBU3cwVRNA XY8s+MiPINWQfYQqoRLj5iZOLTpte+sT7GRjPNEU3ZxEg1ey5J6qPAx9ee3EeBv1OsQU lXxx6O0OrJ2jDwFU1PxVX9tniUhkXbPRYdP2ZeS8EBWUZNDz+U/FAOrSbySTFk26IDsy kKtw==
MIME-Version: 1.0
Received: by 10.58.243.166 with SMTP id wz6mr11969147vec.28.1354627953523; Tue, 04 Dec 2012 05:32:33 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 4 Dec 2012 05:32:33 -0800 (PST)
Date: Tue, 4 Dec 2012 13:32:33 +0000
Message-ID: <CADnDZ8937L+sGEEj+4QUu33yxhRdm0M_OHAa6sr509hXtc7oJQ@mail.gmail.com>
Subject: Re: Creating an IETF Working Group Draft
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dhc@dcrocker.net
Content-Type: multipart/alternative; boundary=047d7b86f4b2f8fca304d006e5ec
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, 04 Dec 2012 13:32:36 -0000

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

Hi Dave,

Thanks for your work, please provide us with feedback while the process of
editing. I was thinking to do something in the future, but thanks that you
will do it.

AB

Folks, There is now an Internet Draft, based on Adrian's's slides, intended
to document common practice in the adoption of working group drafts:

Title:   Creating an IETF Working Group Draft
Status:  http://datatracker.ietf.org/doc/draft-crocker-id-adoption

Abstract:
   The productive output of IETF working groups is documents, as
   mandated by the working group's charter.  Working groups develop
   these documents based on initial input of varying levels of maturity.
   An initial working group draft might be a document already in wide
   use, or it might be a blank sheet, wholly created by the workiing
   group, or it might represent any level of maturity in between.  This
   document discusses the process of creating formal working group
   drafts that are targeted for publication.

Although it is not intended for a standards-track or bcp publication, it would
be helpful to have discussion that moves the document to represent good
agreement among the community.

d/

--
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

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

<div>Hi Dave,</div><div>=A0</div><div>Thanks for your work, please provide =
us with feedback while the process of editing. I was thinking to do somethi=
ng in the future, but thanks that you will do it.</div><div>=A0</div><div>A=
B</div>
<div>=A0</div><div>Folks,

<tt>There is now an Internet Draft, based on Adrian&#39;s&#39;s slides, int=
ended=20
to </tt><tt>document common practice in the adoption of working group draft=
s:=20
</tt><pre style=3D"margin:0em"></pre>
<blockquote style=3D"margin:0em;padding-left:0.85em;border-left-color:rgb(8=
5,85,238);border-left-width:0.2em;border-left-style:solid"><pre style=3D"ma=
rgin:0em">Title:   Creating an IETF Working Group Draft
Status:  <a href=3D"http://datatracker.ietf.org/doc/draft-crocker-id-adopti=
on" rel=3D"nofollow">http://datatracker.ietf.org/doc/draft-crocker-id-adopt=
ion</a>

Abstract:
   The productive output of IETF working groups is documents, as
   mandated by the working group&#39;s charter.  Working groups develop
   these documents based on initial input of varying levels of maturity.
   An initial working group draft might be a document already in wide
   use, or it might be a blank sheet, wholly created by the workiing
   group, or it might represent any level of maturity in between.  This
   document discusses the process of creating formal working group
   drafts that are targeted for publication.
</pre></blockquote><pre style=3D"margin:0em">
</pre><tt>Although it is not intended for a standards-track or bcp publicat=
ion,=20
it </tt><tt>would be helpful to have discussion that moves the document to=
=20
represent </tt><tt>good agreement among the community. </tt><pre style=3D"m=
argin:0em">d/

--
 Dave Crocker
 Brandenburg InternetWorking
 <a href=3D"http://bbiw.net">bbiw.net</a>
</pre></div>

--047d7b86f4b2f8fca304d006e5ec--

From abdussalambaryun@gmail.com  Tue Dec  4 05:45:51 2012
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 771BE21F898B for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 05:45:51 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rddGv+Tb7sKi for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 05:45:50 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 75FB521F8941 for <ietf@ietf.org>; Tue,  4 Dec 2012 05:45:50 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so3377935vcb.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 05:45:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=+YCNZSLZtD4fWIMteg31C69mszNionzWRMsDSqdRs/Q=; b=XdXHMlw5tRZFypv5aFySJN6eCrougdQ/uUDv+qqAConC8TadMb/jxD9j+MgB9Qvji5 lbXd55Eh4lk3K/q1mDruCPUdChi7TGoXX3p/dswn6QgwXPxlBpwF1w8uvebdgOWB06r6 N1tFzIxhJZuzG9l7u20o/nzs9G8U969Gky40ZUPrB5P17682VOBtOpqhzGEwYWxmhO30 1bsU63dO7azPwh9tB73Ccz2HhPQTqChps+n8cWt8DKw2FvW6t/2Sh3PS6QL7c9kyh0qZ lrPF6fgIcQSC2AQ+XsNv7hVEZoZ1pHsdJdwG5E0wb26B78IQAnr1xQP24igsq+Lm/Ub9 BrKw==
MIME-Version: 1.0
Received: by 10.220.149.69 with SMTP id s5mr11664545vcv.23.1354628749781; Tue, 04 Dec 2012 05:45:49 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 4 Dec 2012 05:45:49 -0800 (PST)
Date: Tue, 4 Dec 2012 13:45:49 +0000
Message-ID: <CADnDZ89RFm54XgPCX+NPSAt_C_6ytr=9-fQkdKq98it_CgsW-w@mail.gmail.com>
Subject: Re: Presentation vs. Discussion sessions (was: PowerPoint considered harmful)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: moore@network-heretics.com
Content-Type: multipart/alternative; boundary=f46d042fd8986ee9b304d007150f
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, 04 Dec 2012 13:45:51 -0000

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

Hi Keith,

I hope that participant that travel to the f2f meeting and attend sessions,
do participate while they are there on the discussion lists of IETF WGs,
yes they attend and discuss which is reflected in the minutes report
document, but still there are some time they spend away from their work
which can be used for progress of our work. We are recommended to discuss
on the lists for the IETF work progress. Why don't the f2f participants
review all their interested WG drafts while they are in the 3 days for the
IETF and give their feedback on the list (within these important days).

If all participants attend remotely and physically in 2 hours per WG, why
not discuss on the list for 3 days or 12 hours interaction (if each
participant spends 4 hours on the list per day per WG).

 Still we need more encouragment to attract participants to review and
comment on the list or by an informational I-D.

AB


On 12/02/2012 01:06 PM, Melinda Shore wrote:

There's a whole nexus of connected issues here, I think, and what
a given person complains about depends on that person's pet peeves.
It seems to me that if we were better about moving work forward
between meetings (<- peeve!) meeting time wouldn't be chewed up
with presenting the current state of the work.

While I fully agree that most WGs could be better at moving work
forward between
meetings, I don't think it would solve the problem of face to face meeting
time being filled up with presentations.

I suspect that most WG participants have difficulty keeping up with the traffic
on their WGs' mailing lists for various reasons (too much "distraction"
from normal work, the sad state of mail user agents, etc.). By forcing
people to travel away from work, face-to-face meetings serve as useful
interruptions from normal distractions and opportunities to catch up on
IETF work. If working groups moved forward even faster than they do now,
that might actually be seen to increase the need for presentations at
face-to-face meetings.

Occasionally I've wondered if IETF meetings should have "presentation" sessions
separate from (and in advance of) "working" sessions. The difference
between the two types of session would be clearly indicated in the
schedule. The presentation sessions would be geared toward presenting an
overview of current state of the proposals, including a summary of recent
changes. Perhaps participants would be allowed to ask questions for
clarification, but discussion should be discouraged and any kind of polling
of the room or other decision making would be forbidden. The presentation
meetings would therefore be optional for those who had kept up on the
mailing list. And presentations would be forbidden in discussion sessions.

I can imagine these being useful in several ways, e.g. in facilitating better
cross-group and cross-area review. People who were active participants in
working groups could attend presentation sessions of other groups, without
sacrificing their attendance in the discussion sessions of the groups in
which they were active.

Perhaps roughly the first 2(?) days of an IETF meeting could be largely devoted
to presentation sessions, and the remainder of the time to discussion
sessions. Having a strict allocation of time for each kind of session isn't
so important as having the presentation sessions for a particular group
well in advance of the discussion session for that group.

This is something that could be tried on a small scale, by a few working groups
(say one in each area) before being widely adopted. It might help, however,
to have explicit support for the idea in the tools that maintain and
display the meeting schedules.

Keith

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

<div>Hi Keith,</div><div>=A0</div><div>I hope that participant that travel =
to the f2f meeting and attend=A0sessions, do participate while they are the=
re on the discussion lists of IETF=A0WGs, yes they attend and discuss which=
 is reflected in the minutes report document, but still there are some time=
 they spend away from their work which can be used for progress of our work=
.=A0We are=A0recommended to discuss on the lists for the IETF work progress=
. Why don&#39;t the f2f participants review all their interested WG drafts =
while they are in the 3 days for the IETF and give their feedback on the li=
st (within these important days).</div>
<div>=A0</div><div>If all participants attend remotely and physically in 2 =
hours per WG, why not discuss on the list for 3 days or 12 hours interactio=
n (if each participant spends 4 hours on the list per day per WG).</div><di=
v>
=A0</div><div>=A0Still we need more encouragment to attract participants to=
 review and comment on the list or by an informational I-D.</div><div>=A0</=
div><div>AB</div><div>=A0</div><div><pre style=3D"margin:0em">On 12/02/2012=
 01:06 PM, Melinda Shore wrote:
</pre>
<blockquote style=3D"margin:0em;padding-left:0.85em;border-left-color:rgb(8=
5,85,238);border-left-width:0.2em;border-left-style:solid"><pre style=3D"ma=
rgin:0em">There&#39;s a whole nexus of connected issues here, I think, and =
what
a given person complains about depends on that person&#39;s pet peeves.
It seems to me that if we were better about moving work forward
between meetings (&lt;- peeve!) meeting time wouldn&#39;t be chewed up
with presenting the current state of the work.
</pre></blockquote><tt>While I fully agree that most WGs could be better at=
=20
moving work forward </tt><tt>between meetings, I don&#39;t think it would s=
olve the=20
problem of face to </tt><tt>face meeting time being filled up with=20
presentations. </tt><pre style=3D"margin:0em"></pre><tt>I suspect that most=
 WG participants have difficulty keeping up with=20
the </tt><tt>traffic on their WGs&#39; mailing lists for various reasons (t=
oo much=20
</tt><tt>&quot;distraction&quot; from normal work, the sad state of mail us=
er agents,=20
</tt><tt>etc.). By forcing people to travel away from work, face-to-face=20
meetings </tt><tt>serve as useful interruptions from normal distractions an=
d=20
opportunities </tt><tt>to catch up on IETF work. If working groups moved fo=
rward=20
even faster </tt><tt>than they do now, that might actually be seen to incre=
ase=20
the need for </tt><tt>presentations at face-to-face meetings. </tt><pre sty=
le=3D"margin:0em"></pre><tt>Occasionally I&#39;ve wondered if IETF meetings=
 should have &quot;presentation&quot;=20
</tt><tt>sessions separate from (and in advance of) &quot;working&quot; ses=
sions. The=20
</tt><tt>difference between the two types of session would be clearly indic=
ated=20
</tt><tt>in the schedule. The presentation sessions would be geared toward=
=20
</tt><tt>presenting an overview of current state of the proposals, includin=
g a=20
</tt><tt>summary of recent changes. Perhaps participants would be allowed t=
o=20
</tt><tt>ask questions for clarification, but discussion should be discoura=
ged=20
</tt><tt>and any kind of polling of the room or other decision making would=
 be=20
</tt><tt>forbidden. The presentation meetings would therefore be optional f=
or=20
</tt><tt>those who had kept up on the mailing list. And presentations would=
 be=20
</tt><tt>forbidden in discussion sessions. </tt><pre style=3D"margin:0em"><=
/pre><tt>I can imagine these being useful in several ways, e.g. in facilita=
ting=20
</tt><tt>better cross-group and cross-area review. People who were active=
=20
</tt><tt>participants in working groups could attend presentation sessions =
of=20
</tt><tt>other groups, without sacrificing their attendance in the discussi=
on=20
</tt><tt>sessions of the groups in which they were active. </tt><pre style=
=3D"margin:0em"></pre><tt>Perhaps roughly the first 2(?) days of an IETF me=
eting could be=20
largely </tt><tt>devoted to presentation sessions, and the remainder of the=
 time=20
to </tt><tt>discussion sessions. Having a strict allocation of time for eac=
h=20
kind </tt><tt>of session isn&#39;t so important as having the presentation =
sessions=20
for a </tt><tt>particular group well in advance of the discussion session f=
or=20
that group. </tt><pre style=3D"margin:0em"></pre><tt>This is something that=
 could be tried on a small scale, by a few=20
working </tt><tt>groups (say one in each area) before being widely adopted.=
 It=20
might </tt><tt>help, however, to have explicit support for the idea in the =
tools=20
that </tt><tt>maintain and display the meeting schedules. </tt><pre style=
=3D"margin:0em">Keith
</pre></div><div>=A0</div>

--f46d042fd8986ee9b304d007150f--

From abdussalambaryun@gmail.com  Tue Dec  4 06:14:14 2012
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 3DAB021F86DD for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:14:14 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-kRFAIluYxP for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:14:13 -0800 (PST)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3838B21F86AB for <ietf@ietf.org>; Tue,  4 Dec 2012 06:14:12 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id l1so5089855vba.27 for <ietf@ietf.org>; Tue, 04 Dec 2012 06:14:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VZXlQof8PNWODSF1UrTnBH6Rb2BOMtL1AwsQfDCq1tA=; b=tB8XT3aSjVApVmvNqF1tNRsL24zwmBUpReHnOIwO+sFATBlAqxD0uy3btNef830Y/n t+E5tsanSReqjWlhCD1I9ne91tiiZUNHJqlLBIMe+Akmw32aPBXFJnD86Hl45b/FQay1 11wjv2f69iqKoRBvMjS6aeBg1g59f15KpBHeRh+4rYce2MZXgxHn6gF5+qc2pKCt5v+2 gtwg2m6ecmoPDDVsCXHrwwmimcszUTZj8IEXvkpaKjZhyBxSEiHuPdz43pC+wn/1ZMQH rPqImxantxcNdNzhGkh5Xg+u4zhXwrPVd7vgqhbT9MO+SFpOLLNxEnQdkgRgG4EKD6oF 3Zmg==
MIME-Version: 1.0
Received: by 10.52.64.168 with SMTP id p8mr913657vds.125.1354630452189; Tue, 04 Dec 2012 06:14:12 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 4 Dec 2012 06:14:12 -0800 (PST)
In-Reply-To: <CADnDZ894SLhPDcNtFBi=RypmWS3cW8yegcjLp-2FWLsrPqDKng@mail.gmail.com>
References: <CADnDZ894SLhPDcNtFBi=RypmWS3cW8yegcjLp-2FWLsrPqDKng@mail.gmail.com>
Date: Tue, 4 Dec 2012 14:14:12 +0000
Message-ID: <CADnDZ88PyhTHOwVRxBF6vRHBV=TqDT4xLhrjPiDXtZRwnnc5Kw@mail.gmail.com>
Subject: Re: When to adopt a draft as a WG doc (was RE: "IETF work is done on the mailing lists")
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3071d004e79b4504d0077a7a
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 14:14:14 -0000

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

On Wed, Nov 28, 2012 at 6:53 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

>
> >But there's no formal process for that, and I think
> >that's how we want it to be.
>
> I don't want no formal in a formal organisation, usually unformal process
> only happen in unformal organisations, so is IETF a formal or non-formal. I
> beleive we are in a formal so our managers (chairs and ADs) SHOULD follow
> formal procedures and participants MAY do both.
>
> I read the procedures and this is what I came out with if I am wrong
> please refer me to where does the procedure mention that WG Chairs have
> such authority.
>
>
>

Now we got an I-D to explain the creation of WG drafts and the formal
Chairs duties in this matter, please read below

http://tools.ietf.org/html/draft-crocker-id-adoption-00


AB

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

<div class=3D"gmail_quote">On Wed, Nov 28, 2012 at 6:53 PM, Abdussalam Bary=
un <span dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" targ=
et=3D"_blank">abdussalambaryun@gmail.com</a>&gt;</span> wrote:<br><blockquo=
te 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>=A0</div><div>&gt;But there&#39;s no formal process for that, and I th=
ink<br>&gt;that&#39;s how we want it to be.</div><div>=A0</div><div>I don&#=
39;t want no formal in a formal organisation, usually unformal process only=
 happen in unformal organisations, so is IETF a formal or non-formal. I bel=
eive we are in a formal so our managers (chairs and ADs) SHOULD follow form=
al procedures and participants MAY do both.</div>

<div>=A0</div><div>I read the procedures and this is what I came out with i=
f I am wrong please refer me to where does the procedure mention that WG=A0=
Chairs have such authority.</div><span class=3D"HOEnZb"><font color=3D"#888=
888"><div>
=A0</div><div>=A0</div></font></span></blockquote><div>=A0</div><div>Now we=
 got an I-D to explain the creation of WG drafts and the formal Chairs duti=
es in this matter, please read below</div><div>=A0</div><div><a href=3D"htt=
p://tools.ietf.org/html/draft-crocker-id-adoption-00">http://tools.ietf.org=
/html/draft-crocker-id-adoption-00</a></div>
<div>=A0</div><div>=A0</div><div>AB=A0</div></div><br>

--20cf3071d004e79b4504d0077a7a--

From abdussalambaryun@gmail.com  Tue Dec  4 06:18:33 2012
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 6AC0021F89BF for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:18:33 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Sa8dt3AefYi for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:18:33 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id D3DB721F89BB for <ietf@ietf.org>; Tue,  4 Dec 2012 06:18:32 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so3422489vcb.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 06:18:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=XJJ0yM2ml4QGMMsvM77LIyZxuulgV4ZKN/7whxxYHa8=; b=sZ2kJWAr1R1ir4p+Vc5x3JBxieIt+wg7JIyiE8OJuSVpW6e6VLUVnt+3v+a4l73/Yc GC0UbEE7YbDwpzWftUlxihwH5MYNlxBbyvWdAYxUK5kmHC7QXQGUCwGekmvtZ2B20tIj AK+Pgp4KGz8hP07cAaLjq0ZgAvKtM9ivachHuchX1W5Z8Q5mpds6BZYoQZ0VxQ5KabRG zzYpjhuBZGlmelKD33qUNjAHJIyvSVRUFQh+xcUzTSGSi8B1gTJsrtHXKDeF/d5+bVXi 4bgzHkzLxILjUDdiV2pAnOkvs+amTsfW5nmiElnOqIfRB0m092kdMMMujL87lAQK/0Ry ChVQ==
MIME-Version: 1.0
Received: by 10.52.64.168 with SMTP id p8mr923663vds.125.1354630712374; Tue, 04 Dec 2012 06:18:32 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Tue, 4 Dec 2012 06:18:32 -0800 (PST)
In-Reply-To: <CADnDZ8-FRwkTgDKi=kr4fmZv5=tvUAcon0oQ1SrjYbgG4rfv1g@mail.gmail.com>
References: <CADnDZ8-FRwkTgDKi=kr4fmZv5=tvUAcon0oQ1SrjYbgG4rfv1g@mail.gmail.com>
Date: Tue, 4 Dec 2012 14:18:32 +0000
Message-ID: <CADnDZ88ev6YjM6NWPULk1PZ4Z+H-acw03PdB=-z7cx6cX2e9mQ@mail.gmail.com>
Subject: Re: When do we ask community for opinion and When we produce an RFC for the community?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3071d00469b40004d0078a09
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 14:18:33 -0000

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

On Wed, Nov 28, 2012 at 7:35 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> My question is when do we ask community (from participant level, or
> from managerial level) and when we produce an RFC (which purpose)?
>
>

I think the answer to this question should be through a
procedure/informational I-D to make things clear to all participants.

AB

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

<div class=3D"gmail_quote">On Wed, Nov 28, 2012 at 7:35 PM, Abdussalam Bary=
un <span dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" targ=
et=3D"_blank">abdussalambaryun@gmail.com</a>&gt;</span> wrote:<br><blockquo=
te 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>My question is when do we=A0ask community (from=A0participant level, o=
r from=A0managerial level) and when we produce an RFC (which=A0purpose)?</d=
iv><div>=A0</div></blockquote><div>=A0</div><div>I think the answer to this=
 question should be through=A0a procedure/informational=A0I-D to make thing=
s clear to all participants.</div>
<div>=A0</div><div>AB=A0</div></div>

--20cf3071d00469b40004d0078a09--

From barryleiba.mailing.lists@gmail.com  Tue Dec  4 06:47:01 2012
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 754A021F866F for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:47:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.976
X-Spam-Level: 
X-Spam-Status: No, score=-102.976 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0i5Ki8Qphck for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:47:01 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id B2ED121F85FC for <ietf@ietf.org>; Tue,  4 Dec 2012 06:47:00 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so3421838lah.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 06:46:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tQEquumasqe1Sq+wFuBDl4QXJUdsQtZVYYbNysYPy1A=; b=EO4XuQ+mXdtp2g08xWnL8aBrvdv9evPBxhXKKUloLnIOadF9Oa05GUQJOVlV24GGfN EyGLIWaWPcnjVlHSV/x/4L3svTsFqx5I4kVVGYRr/S/YzF59C2gUXKtV6MvTv0oA4r1T m20lzatuVb//IONrZLDVlspz3sfwOcVbx2P/WBjq7pn7fkHZyxlFV+BklL6qnB6vbhx+ G+xZT2jxOkrHUiMNW4vqhoOmEbG/rIfRYyGDBN+Efixv45KgQjc99IwqcmsK4E7jzF8t 6iv6YklgL0cRHFFjennXom/Lj92MlqM/XLVbaWcIZMTHjYW9F4wia/qO9lgM53oup71L jPcA==
MIME-Version: 1.0
Received: by 10.112.99.195 with SMTP id es3mr5735013lbb.132.1354632419543; Tue, 04 Dec 2012 06:46:59 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Tue, 4 Dec 2012 06:46:59 -0800 (PST)
In-Reply-To: <m2r4n6f28s.wl%randy@psg.com>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <50BD8E60.5030206@it.aoyama.ac.jp> <m2r4n6f28s.wl%randy@psg.com>
Date: Tue, 4 Dec 2012 09:46:59 -0500
X-Google-Sender-Auth: FAqhMWooFMsTf9kl5p2HCSqEG_4
Message-ID: <CAC4RtVBcRX6WM3bCV_MFr5F08j3z8M0dn7Mg20ZR2x+Yfn8xNw@mail.gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
From: Barry Leiba <barryleiba@computer.org>
To: Randy Bush <randy@psg.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: Tue, 04 Dec 2012 14:47:01 -0000

> i think we're ratholing here.  the point i get is that, if there is open
> source code that suppliments the drafts sufficiently to lend confidence
> in the implementability and implementation, then progress might be
> accelerated.

But the point of "running code" in our nice, catchy slogan, is that
"running" doesn't mean simply that it runs.  It means that it's
actually *in use*, possibly for real, but at least in a test lab where
it's getting real use.  *Real* running code probably does lend such
confidence.  Code that's just been written because it helps your draft
get an extra tick mark in a box almost certainly doesn't, whether we
can see and understand the source code or not.

Barry

From moore@network-heretics.com  Tue Dec  4 06:55:33 2012
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 DDA9521F8BBB for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:55:33 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FMO9ctOxYcav for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 06:55:33 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0F23921F8BBA for <ietf@ietf.org>; Tue,  4 Dec 2012 06:55:33 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 3CC17209EC for <ietf@ietf.org>; Tue,  4 Dec 2012 09:55:32 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Tue, 04 Dec 2012 09:55:32 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=RV8h744bBuyDl/lx1O0VA5 tZokk=; b=alskCMwYDgSFt0UcVP6/EaoOLMNkvotYMQNpkYg2YlQAdF3UgK+aQm Nxj9uZ6HMvN+0nyTFgSIqnIp+hbNjVlwIDoz1IjDLD2AFwXGlI8PHxlLJ7457ziS ILsbb2XVDcl2z7GXSDVixqgJZMi2gdDL92ypSnuF6vujJt4bOsdgE=
X-Sasl-enc: WykhzPhywkUiX7ZmgTY5pHqOD1ZR2U5N0h7DFbXVgB23 1354632931
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A1258E01F5; Tue,  4 Dec 2012 09:55:31 -0500 (EST)
Message-ID: <50BE0EE1.7080808@network-heretics.com>
Date: Tue, 04 Dec 2012 09:55:29 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net> <50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <50BBA21! D.6090403@bogus.com> <8C48B86A895913448548E6D15DA7553B6F5F2C@xmb-rcd-x09.cisco.com> <F7707BE9-79FA-4AA4-AE1A-9D4DB822BA6D@ecs.soton.ac.uk> <EMEW3|ba2897928cf23777aa76076399e696f4oB3DYk03tjc|ecs.soton.ac.uk|F7707BE9-79FA-4AA4-AE1A-9D4DB822BA6D@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|ba2897928cf23777aa76076399e696f4oB3DYk03tjc|ecs.soton.ac.uk|F7707BE9-79FA-4AA4-AE1A-9D4DB822BA6D@ecs.soton.ac.uk>
Content-Type: text/plain; charset=windows-1252; 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: Tue, 04 Dec 2012 14:55:34 -0000

On 12/04/2012 08:29 AM, Tim Chown wrote:
> Exactly. If the "presentation" is one slide listing the key changes in the document since the last revision/meeting, and one slide per key question/issue being asked of the room, then that should help facilitate good discussion, not hinder it.
>
> What doesn't work is a 15 minute presentation of the current contents of a draft that leaves a couple of minutes for questions.
>
> It's not the tool, it's how it's used.

I'm somewhat amused that so many IETFers seem to be saying "don't blame 
the tool, blame the people".   Blaming people is such an effective way 
to encourage them to change their habits. :)

Keith


From adrian@olddog.co.uk  Tue Dec  4 07:51:21 2012
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 F373421F8AF5 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 07:51:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pCx8CwkQkZP for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 07:51:15 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCEA21F8C0B for <ietf@ietf.org>; Tue,  4 Dec 2012 07:51:13 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qB4Fp4wR020232;  Tue, 4 Dec 2012 15:51:05 GMT
Received: from 950129200 (ixe-nat1.juniper.net [193.110.54.36]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id qB4Fp3ld020194 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 4 Dec 2012 15:51:04 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>, <dhc@dcrocker.net>
References: <CADnDZ8937L+sGEEj+4QUu33yxhRdm0M_OHAa6sr509hXtc7oJQ@mail.gmail.com>
In-Reply-To: <CADnDZ8937L+sGEEj+4QUu33yxhRdm0M_OHAa6sr509hXtc7oJQ@mail.gmail.com>
Subject: RE: Creating an IETF Working Group Draft
Date: Tue, 4 Dec 2012 15:51:01 -0000
Message-ID: <051501cdd237$2959aef0$7c0d0cd0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0516_01CDD237.295E42D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIvvuOA4QZ4i0tFTcoutYjrgmplFZdE7vJA
Content-Language: en-gb
Cc: 'ietf' <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, 04 Dec 2012 15:51:21 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0516_01CDD237.295E42D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Abdussalam,
 
By all means send text or suggestions for edits.
 
Dave and I will include what is reasonable and seek a consensus that agrees with
our motivation for writing the document.
 
Thanks,
Adrian
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Abdussalam Baryun
Sent: 04 December 2012 13:33
To: dhc@dcrocker.net
Cc: ietf
Subject: Re: Creating an IETF Working Group Draft
 
Hi Dave,
 
Thanks for your work, please provide us with feedback while the process of
editing. I was thinking to do something in the future, but thanks that you will
do it.
 
AB
 
Folks, There is now an Internet Draft, based on Adrian's's slides, intended to
document common practice in the adoption of working group drafts: 
Title:   Creating an IETF Working Group Draft
Status:  http://datatracker.ietf.org/doc/draft-crocker-id-adoption
 
Abstract:
   The productive output of IETF working groups is documents, as
   mandated by the working group's charter.  Working groups develop
   these documents based on initial input of varying levels of maturity.
   An initial working group draft might be a document already in wide
   use, or it might be a blank sheet, wholly created by the workiing
   group, or it might represent any level of maturity in between.  This
   document discusses the process of creating formal working group
   drafts that are targeted for publication.
 
Although it is not intended for a standards-track or bcp publication, it would
be helpful to have discussion that moves the document to represent good
agreement among the community. 
d/
 
--
 Dave Crocker
 Brandenburg InternetWorking
 bbiw.net

------=_NextPart_000_0516_01CDD237.295E42D0
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@01CDD236.9133F220"><!--[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;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 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;}
pre
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Calibri;}
tt
	{mso-style-noshow:yes;
	mso-style-priority:99;
	font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"HTML Preformatted";
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	mso-fareast-language:EN-GB;}
span.EmailStyle20
	{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;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.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'>Abdussalam,<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'>By all means send text or =
suggestions for edits.<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'>Dave and I will include what =
is reasonable and seek a consensus that agrees with our motivation for =
writing the document.<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'>Thanks,<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'>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'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Abdussalam Baryun<br><b>Sent:</b> 04 December 2012 =
13:33<br><b>To:</b> dhc@dcrocker.net<br><b>Cc:</b> =
ietf<br><b>Subject:</b> Re: Creating an IETF Working Group =
Draft<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>Hi =
Dave,<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Thanks for your work, please provide us with feedback =
while the process of editing. I was thinking to do something in the =
future, but thanks that you will do it.<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>AB<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Folks, <tt><span style=3D'font-size:10.0pt'>There is =
now an Internet Draft, based on Adrian's's slides, intended to document =
common practice in the adoption of working group drafts: =
</span></tt><o:p></o:p></p><blockquote =
style=3D'border:none;border-left:solid #5555EE 2.25pt;padding:0cm 0cm =
0cm 10.0pt;margin-left:0cm;margin-right:0cm'><pre>Title:<span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>Creating an IETF Working =
Group Draft<o:p></o:p></pre><pre>Status:<span =
style=3D'mso-spacerun:yes'>&nbsp; </span><a =
href=3D"http://datatracker.ietf.org/doc/draft-crocker-id-adoption">http:/=
/datatracker.ietf.org/doc/draft-crocker-id-adoption</a><o:p></o:p></pre><=
pre><o:p>&nbsp;</o:p></pre><pre>Abstract:<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>The productive output of =
IETF working groups is documents, as<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>mandated by the working =
group's charter.<span style=3D'mso-spacerun:yes'>&nbsp; </span>Working =
groups develop<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>these documents based on =
initial input of varying levels of maturity.<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>An initial working group =
draft might be a document already in wide<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>use, or it might be a =
blank sheet, wholly created by the workiing<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>group, or it might =
represent any level of maturity in between.<span =
style=3D'mso-spacerun:yes'>&nbsp; </span>This<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>document discusses the =
process of creating formal working group<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>drafts that are targeted =
for =
publication.<o:p></o:p></pre></blockquote><pre><o:p>&nbsp;</o:p></pre><p =
class=3DMsoNormal><tt><span style=3D'font-size:10.0pt'>Although it is =
not intended for a standards-track or bcp publication, it would be =
helpful to have discussion that moves the document to represent good =
agreement among the community. =
</span></tt><o:p></o:p></p><pre>d/<o:p></o:p></pre><pre><o:p>&nbsp;</o:p>=
</pre><pre>--<o:p></o:p></pre><pre> Dave Crocker<o:p></o:p></pre><pre> =
Brandenburg InternetWorking<o:p></o:p></pre><pre> <a =
href=3D"http://bbiw.net">bbiw.net</a><o:p></o:p></pre></div></div></div><=
/body></html>
------=_NextPart_000_0516_01CDD237.295E42D0--


From david.black@emc.com  Mon Dec  3 15:13:12 2012
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 C011521F8968; Mon,  3 Dec 2012 15:13:12 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6k+FL7sRA7Es; Mon,  3 Dec 2012 15:13:11 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CE74E21F86F3; Mon,  3 Dec 2012 15:13:10 -0800 (PST)
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 qB3ND5V0015947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Dec 2012 18:13:06 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 3 Dec 2012 18:12:55 -0500
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qB3NCsh8000640; Mon, 3 Dec 2012 18:12:54 -0500
Received: from mx15a.corp.emc.com ([169.254.1.253]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Mon, 3 Dec 2012 18:12:54 -0500
From: "Black, David" <david.black@emc.com>
To: "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 3 Dec 2012 18:12:52 -0500
Subject: Gen-ART review of draft-ietf-softwire-dslite-deployment-07
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-07
Thread-Index: Ac2rKkPgDErjXyHISiSTlQ/jGKFZIgmf5XbA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712864B595B@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@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, 04 Dec 2012 09:32:20 -0800
Cc: "softwires@ietf.org" <softwires@ietf.org>, "Black, David" <david.black@emc.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, 03 Dec 2012 23:13:12 -0000

Authors,

The -07 version of this draft has resolved most of the concerns raised by
the  Gen-ART review of the -06 version of this draft, with one significant
exception:

> [5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> "the AFTR does not have detailed customer identity information."  Does
> that create a theft of service possibility?  If so, that possibility
> should be mentioned as a security consideration.  Also, Section 2.8
> ought to be expanded with a sentence or two explaining why the AFTR
> does not have that identity information, and in particular to explain
> whether and why it is unreasonable in some or all cases to expect
> that customer identity information be provided to the AFTR as part
> of provisioning each customer's softwire.

This has been partially resolved - the explanation of why the AFTR may
not have that identity information has been added.  Here's the text from
the -07 draft.

   Alternatively, AFTR may perform accounting for IPv4 traffic.
   However, operators must be aware that this will introduce some
   challenges especially in DSL deployment.  In DSL deployment, the AAA
   transaction normally happens between the edge router (i.e., Broadband
   Network Gateway) and AAA server.  [RFC6333] does not require the AFTR
   to interact with the AAA server or edge router.  Thus, AFTR may not
   have the AAA parameters (e.g., Account Session ID) associated to
   users to generate IPv4 accounting record.  The accounting process at
   the AFTR is only necessary if the operator requires separating per
   user accounting records for IPv4 and IPv6 traffic.  If the per user
   IPv6 accounting records, collected by the edge router, are
   sufficient, and the additional complexity of enabling IPv4 accounting
   at the ATFR is not required.  It is important to notice that, since
   the IPv4 traffic is encapsulated in IPv6 packets, the data collected
   by the edge router for IPv6 traffic already contain the total amount
   of traffic (i.e.  IPv4 and IPv6).

This revised text removes my concern about a security risk, but=20
I think the result still provides more support than it should for
trying to do accounting without all the information needed to do it.

Please insert a sentence before "The accounting process at the AFTR is
only necessary if ..." to state that IPv4 traffic accounting at the AFTR
is not recommended when the necessary AAA parameters are not available.
The following sentence would suffice.

   IPv4 traffic accounting at the AFTR is not recommended when the
   AAA parameters necessary to generate complete IPv4 accounting
   records are not available.

Also, the response to this nit could be improved:

> Section 3.2.2 uses 192.0.0.2/32 as an example IP address for the
> B4.  That section should also cross-reference Section 5.7 on RFC 6333
> on IP address assignment to B4s, as other IP addresses may be used.

My original comment wasn't complete - here's a suggested text change
that should be clearer:

OLD
   Operators should assign the same IPv4 address
   (i.e., 192.0.0.2/32) to all AFTRs.  IANA allocates 192.0.0.0/29
   [RFC6333] Section 5.7 that can be used for this purpose.
NEW
   Operators should assign the same IPv4 address
   (e.g., 192.0.0.2/32 [RFC6333]) to all AFTRs.  IANA has allocated
   the 192.0.0.0/29 network prefix to provide IPv4 addresses for this
   purpose [RFC 6333].
END

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Monday, October 15, 2012 7:10 PM
> To: yiu_lee@cable.comcast.com; roberta.maglione@telecomitalia.it; carlw@m=
csr-
> labs.org; christian.jacquenet@orange.com; mohamed.boucadair@orange.com; g=
en-
> art@ietf.org
> Cc: softwires@ietf.org; Black, David; ietf@ietf.org; Ralph Droms
> Subject: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>=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 resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-softwire-dslite-deployment-06
> Reviewer: David L. Black
> Review Date: October 15, 2012
> IETF LC End Date: October 16, 2012
> IESG Telechat Date: October 25, 2012
>=20
> Summary:
>=20
> This draft is on the right track but has open issues, described in the re=
view.
>=20
> This is a generally well-written draft that expands considerably on the b=
rief
> deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dra=
ft
> is clear and reasonably well-written, and a significant improvement on th=
at
> RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> understand this draft, which seems completely reasonable.
>=20
> The B4 and AFTR acronyms are clever - kudos to whomever came up with thos=
e.
>=20
> I found five open issues, all of which are minor.
>=20
> Minor Issues:
>=20
> [1] Ironically, the first issue is that something should be said about
> the relationship of this draft to Appendix A of RFC 6333.  It probably
> suffices to say that this draft expands on the material in that Appendix,
> as I see no need to specify that this draft updates RFC 6333 solely to
> change non-normative material in an Appendix.
>=20
> [2] The MTU increase technique in Section 2.2 is a "may", which is
> consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> draft should also discuss the AFTR resource exhaustion concern that
> described in Section 6.3 of RFC 6333, as that is a potential
> operational reason for an ISP to increase MTU size (e.g., if customer
> sourcing of large IPv4 packets is not sufficiently rare).
>=20
> [3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> two internal interfaces, the physical IPv6 interface (outer header) and
> the tunnel's IPv4 interface (inner header).  The text should be clarified
> to indicate which interface is involved - it appears that the AFTR's
> physical IPv6 interface is intended in this section.
>=20
> [4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> should be cited - either in addition to or instead of RFC 6333.
>=20
> [5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> "the AFTR does not have detailed customer identity information."  Does
> that create a theft of service possibility?  If so, that possibility
> should be mentioned as a security consideration.  Also, Section 2.8
> ought to be expanded with a sentence or two explaining why the AFTR
> does not have that identity information, and in particular to explain
> whether and why it is unreasonable in some or all cases to expect
> that customer identity information be provided to the AFTR as part
> of provisioning each customer's softwire.
>=20
> Nits:
>=20
> Section 2.3 on MTU Considerations could usefully mention MTU discovery
> techniques, as possibilities for customer IPv4 traffic to adapt to a
> smaller IPv4 MTU.  If this is done, it would be useful to mention
> RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>=20
> Section 2.4 should define "lawful intercept".  It would be helpful to
> cite a reference for this concept if something appropriate can be found.
>=20
> Section 2.5:
> - Are one or both types of logging recommended?
> - Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> 	"maintain a timestamped log of" would be a better replacement.
> - Last paragraph in section, where is the batch file sent?
>=20
> In Section 2.7, I'm having a hard time understanding which traffic is
> intended to be subject to the Outgoing Policies and the Incoming Policies=
.
> Expanding each of those two bullets to explain what traffic is subject
> to each class of policies would help.
>=20
> Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> B4.  That section should also cross-reference Section 5.7 on RFC 6333
> on IP address assignment to B4s, as other IP addresses may be used.
>=20
> idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> version 28.
>=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
> ----------------------------------------------------
>=20


From hannes.tschofenig@nsn.com  Tue Dec  4 00:52:44 2012
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0F021F84F8 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 00:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.475
X-Spam-Level: 
X-Spam-Status: No, score=-106.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ms-mUILYQoxK for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 00:52:42 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8AE21F84CF for <ietf@ietf.org>; Tue,  4 Dec 2012 00:52:42 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id qB48qBKL016179 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Dec 2012 09:52:11 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id qB48q8BE016232; Tue, 4 Dec 2012 09:52:08 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Dec 2012 09:52:07 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: Simplifying our processes: Conference Calls
Date: Tue, 4 Dec 2012 10:51:27 +0200
Message-ID: <999913AB42CC9341B05A99BBF358718D022E061C@FIESEXC035.nsn-intra.net>
In-Reply-To: <50BDB6A0.8000201@bogus.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Simplifying our processes: Conference Calls
Thread-Index: Ac3R+tttYu6QVXUET3S03FsWi1kpHQAAPcSg
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <50BCCE1D.5070001@gmail.com> <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net> <50BDB6A0.8000201@bogus.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext joel jaeggli" <joelja@bogus.com>
X-OriginalArrivalTime: 04 Dec 2012 08:52:07.0831 (UTC) FILETIME=[A4136270:01CDD1FC]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 716
X-purgate-ID: 151667::1354611133-00006291-EC8C3658/0-0/0-0
X-Mailman-Approved-At: Tue, 04 Dec 2012 09:32:20 -0800
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, 04 Dec 2012 08:52:44 -0000

PiBJIGJlbGl2ZSB5b3UncmUgZHJhd2luZyBhIGRpc3RpbmN0aW9uIGJldHdlZW4gY29uZmVyZW5j
ZSBjYWxsIGFuZA0KPiB2aXJ0dWFsIGludGVyaW0gd2hpY2ggZG9lcyBub3QgcHJlc2VudGx5IGV4
aXN0LiBJdCBjb3VsZCwgYnV0IGRvZXNuJ3QuDQoNCk5vLCBJIGFtIG5vdCBkb2luZyB0aGF0LiBJ
IGtub3cgdGhhdCB3ZSBjYWxsIGNvbmZlcmVuY2UgY2FsbHMgdmlydHVhbCBpbnRlcmltIG1lZXRp
bmdzLiANCg0KSSBhbHNvIGF0dGVuZCB2YXJpb3VzIHdvcmtpbmcgZ3JvdXAgbWVldGluZ3MgZHVy
aW5nIGFuIElFVEYgd2VlayBqdXN0IHRvIHNlZSB3aGF0IGlzIGdvaW5nIG9uIGJ1dCBJIGRvIG5v
dCByYW5kb21seSBqb2luIGNvbmZlcmVuY2UgY2FsbHMgb2YgZ3JvdXBzIHdoZXJlIEkgYW0gbm90
IHN1YnNjcmliZWQuIEFyZSB5b3Ugam9pbmluZyBjYWxscyBvZiBncm91cHMgeW91IGRvIG5vdCBj
YXJlIGVub3VnaCBhYm91dCB0byBsb29rIGF0IHRoZSBtYWlsaW5nIGxpc3Q/IA0KDQpDaWFvDQpI
YW5uZXMNCg0K

From dhc@dcrocker.net  Tue Dec  4 09:47:43 2012
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 C649D21F8C60 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 09:47:43 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C6kUJQ9j8h-A for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 09:47:43 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B78F21F8C5E for <ietf@ietf.org>; Tue,  4 Dec 2012 09:47:43 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB4HlOx0026768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 4 Dec 2012 09:47:25 -0800
Message-ID: <50BE3721.90004@dcrocker.net>
Date: Tue, 04 Dec 2012 09:47:13 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Subject: Re: Simplifying our processes: Conference Calls
References: <84D0B79A-6D53-47DD-99B8-BC6C18614C74@gmx.net> <50BCCE1D.5070001@gmail.com> <999913AB42CC9341B05A99BBF358718D022E05E1@FIESEXC035.nsn-intra.net> <50BDB6A0.8000201@bogus.com> <999913AB42CC9341B05A99BBF358718D022E061C@FIESEXC035.nsn-intra.net>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D022E061C@FIESEXC035.nsn-intra.net>
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.17]); Tue, 04 Dec 2012 09:47:25 -0800 (PST)
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, 04 Dec 2012 17:47:44 -0000

On 12/4/2012 12:51 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>> I belive you're drawing a distinction between conference call and
>> virtual interim which does not presently exist. It could, but doesn't.
>
> No, I am not doing that. I know that we call conference calls virtual interim meetings.
>
> I also attend various working group meetings during an IETF week just to see what is going on but I do not randomly join conference calls of groups where I am not subscribed. Are you joining calls of groups you do not care enough about to look at the mailing list?


You appear to be using your personal choices as a basis for making a 
conceptual distinction.  It does not matter what the statistics of the 
choices are.

The concept is simple:  a time-specific gather is a meeting.  Meetings 
require prior announcement beyond the working group.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From smb@cs.columbia.edu  Tue Dec  4 09:50:27 2012
Return-Path: <smb@cs.columbia.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 BF68A21F8C7A for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 09:50:27 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ouXqwuCWOOTf for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 09:50:21 -0800 (PST)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id D34F621F8C65 for <ietf@ietf.org>; Tue,  4 Dec 2012 09:50:20 -0800 (PST)
Received: from [10.9.0.222] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id qB4HoHj1018333 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 4 Dec 2012 12:50:19 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: English spoken here (was: PowerPoint considered harmful)
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>
Date: Tue, 4 Dec 2012 12:50:17 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <B933B8C9-F858-4D19-8F45-109A996321B2@cs.columbia.edu>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
Cc: SM <sm@resistor.net>, 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: Tue, 04 Dec 2012 17:50:27 -0000

On Dec 2, 2012, at 12:21 PM, John C Klensin <john-ietf@jck.com> wrote:

> 
> 
> --On Sunday, December 02, 2012 08:35 -0800 SM <sm@resistor.net>
> wrote:
> 
>> 
>> It is not about different dialects of English.  There are
>> people in one part of the world who speak English.  There are
>> people from other parts of the world which do not understand
>> that English because of:
>> 
>>  (a) The way English is spoken
>> 
>>  (b) The speed at which English is spoken
>> 
>>  (c) The vocabulary used
> 
> (d) Their reading-English is much better than their spoken
> English and they have trouble keeping up even if (b) is quite
> moderate.
> 
>> The people face a high barrier for active participation at a
>> meeting.
> 
> But can be considerably aided in many cases by written material
> (slides, summaries, or both) well in advance especially if those
> material are also used at the meeting, thereby aiding
> synchronization.
> 
>> ...
>> Accommodating the group of people is not enough.  It is up to
>> the group of people to say what they would like done to make
>> the IETF easier for them.  It is up to the (North American)
>> group to, if you excuse me, shut up and take what they say at
>> face value instead of trying to prove them wrong.
> 
> Sigh.  Some of the comments above are derived from exactly the
> types of discussions you are trying to encourage.  Other parts
> of it derive from trying to understand and participate in
> presentations and discussions in languages in which I can sort
> of get around but am not real-time fluent (while the issue in
> the IETF is the set of languages, dialects, and pronunciations
> we call "English", the problem isn't unique).  
> 
> Cultural styles also make some of the most affected parties less
> likely to speak up for their specific needs on this list than
> one might like.  That leaves the rest of us with a choice
> between trying to synthesize from other conversations and
> experiences and taking the position that, until the people with
> the most severe versions of the problem speak up, there is no
> problem.  I believe the latter would be unfortunate for many
> reasons, not least of which is that better use of meeting time
> and presentation aids/ materials would help those of us who are
> native speakers as well.


I started making up really good slides (in a variety of settings)
after noticing non-native-English speakers at the IETF taking
pictures of the screen -- it *really* helped them.

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






From wjhns1@hardakers.net  Tue Dec  4 10:25:46 2012
Return-Path: <wjhns1@hardakers.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 641E421F8CA9 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 10:25:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.592
X-Spam-Level: 
X-Spam-Status: No, score=-2.592 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0fAMR8aM4uy for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 10:25:46 -0800 (PST)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED24A21F8C76 for <ietf@ietf.org>; Tue,  4 Dec 2012 10:25:45 -0800 (PST)
Received: from localhost (unknown [50.13.187.159]) by mail.hardakers.net (Postfix) with ESMTPSA id 853AB3B; Tue,  4 Dec 2012 10:25:43 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]> <50B8CC84.70603@pi.nu> <18C4713424DC63629B268A03@[192.168.6.112]> <0la9tydi03.fsf@wjh.hardakers.net> <7EB1F9A9-5E55-45EB-9AB5-42973EFCDEF5@bbn.com>
Date: Tue, 04 Dec 2012 10:25:40 -0800
In-Reply-To: <7EB1F9A9-5E55-45EB-9AB5-42973EFCDEF5@bbn.com> (Richard Barnes's message of "Fri, 30 Nov 2012 14:16:34 -0500")
Message-ID: <0lhao1wu6z.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
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: Tue, 04 Dec 2012 18:25:46 -0000

Richard Barnes <rbarnes@bbn.com> writes:

> Ever try writing an XML app?  Half your time is spent writing a .xml parser.

No, see...  you're expecting good xml.

  use XML::Simple
  $x = xmlIn("file.xml");

It's the easiest thing in the world to use.  But it doesn't parse
complex without more pain (but who wants that) and it's "still perl"
(and who wants that?)
-- 
Wes Hardaker
SPARTA, Inc.

From wjhns1@hardakers.net  Tue Dec  4 10:26:24 2012
Return-Path: <wjhns1@hardakers.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 D92E921F8A84 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 10:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.094
X-Spam-Level: 
X-Spam-Status: No, score=-3.094 tagged_above=-999 required=5 tests=[AWL=0.506,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xh63nragSfku for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 10:26:24 -0800 (PST)
Received: from mail.hardakers.net (mail.hardakers.net [168.150.236.43]) by ietfa.amsl.com (Postfix) with ESMTP id D7BAD21F86B5 for <ietf@ietf.org>; Tue,  4 Dec 2012 10:26:23 -0800 (PST)
Received: from localhost (unknown [50.13.187.159]) by mail.hardakers.net (Postfix) with ESMTPSA id 337C11CF; Tue,  4 Dec 2012 10:26:21 -0800 (PST)
From: Wes Hardaker <wjhns1@hardakers.net>
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: request to make the "tools version" of the agenda the default
References: <0lr4ncgtyd.fsf@wjh.hardakers.net> <8CCC9454D1E6317473AC4576@[192.168.6.112]> <50B8CC84.70603@pi.nu> <18C4713424DC63629B268A03@[192.168.6.112]> <0la9tydi03.fsf@wjh.hardakers.net> <12371.1354398245@obiwan.sandelman.ca>
Date: Tue, 04 Dec 2012 10:26:20 -0800
In-Reply-To: <12371.1354398245@obiwan.sandelman.ca> (Michael Richardson's message of "Sat, 01 Dec 2012 16:44:05 -0500")
Message-ID: <0ld2ypwu5v.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
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: Tue, 04 Dec 2012 18:26:25 -0000

Michael Richardson <mcr@sandelman.ca> writes:

> There is .csv and obviously there is .ics too already.

Didn't know about the CSV; that'd be just fine.  .ics is 'too much' in
general though.
-- 
Wes Hardaker
SPARTA, Inc.

From sm@elandsys.com  Tue Dec  4 12:46:17 2012
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 6451321F85DC for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 12:46:17 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROUeGtGd9TY7 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 12:46:16 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFDB21F859A for <ietf@ietf.org>; Tue,  4 Dec 2012 12:46:16 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.159.250]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qB4Kk1i0016678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 4 Dec 2012 12:46:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354653973; bh=K+WCGz1RZKVAJQsFG7fNH6Nb+aDLfnGRn9O1S5D5svc=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=O//8v0USUXQM8zNlGgFTiVN643M97cGYjk6+l/uD2LAoYZVIiztjOnZ/LVW3oDfr4 3OWfgyIGRuCoHyX7LsDDm/9HQOU5VZqkzn3ewlvYaMayiL/SCYG8Qc9PHTF3g4CGJQ 23sDJpmL+vIQlfV0KhgYjRcIB9N1y2JFYDM6MbwQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1354653973; i=@elandsys.com; bh=K+WCGz1RZKVAJQsFG7fNH6Nb+aDLfnGRn9O1S5D5svc=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=TX+WCMbsdm5NexCeK2a1mwY8c1jyLzJr7k8sse1b6r/6urjpUJFlkl7dxdmg9NDM9 TXDJ0AudII2Huc26Zta1XZsYw5+uNpb12T3lxn2SRo2coDF4wBPXKf9JjoXVY0jZXO qlT7EtR5Y+NGsTVzdbByNF5/kuub+wY1UnCHBn+Q=
Message-Id: <6.2.5.6.2.20121204121234.09360870@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 04 Dec 2012 12:38:23 -0800
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: A mailing list protocol
In-Reply-To: <20121204183432.3748.97064.idtracker@ietfa.amsl.com>
References: <20121204183432.3748.97064.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: Tue, 04 Dec 2012 20:46:17 -0000

Hello,

I submitted a draft which discusses about a mailing list protocol 
[1].  It is a code of courtesy that the reader may wish to extend to 
others to facilitate the exchange of opinions and ideas, and to 
facilitate mailing list discussions.  Sally Hambridge deserves full 
credit for most of the text.

The draft is not about rules, guidelines or BCPs.  The problems I 
encountered are:

  (a) excessive text in mailing list messages causing the message digest to be
      sent after a few messages are posted to a mailing list.

  (b) replies to messages which use an odd quoting style [2].

You are invited to criticize the draft.

Regards,
S. Moonesamy

1. http://tools.ietf.org/html/draft-moonesamy-mail-list-protocol-00
2. http://home.in.tum.de/~jain/software/outlook-quotefix/


From hannes.tschofenig@nsn.com  Tue Dec  4 10:00:10 2012
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D6721F8C80 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 10:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.493
X-Spam-Level: 
X-Spam-Status: No, score=-106.493 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HOuPF+ywfXF6 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 10:00:10 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 3381421F8C76 for <ietf@ietf.org>; Tue,  4 Dec 2012 10:00:10 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id qB4HxXMQ025932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Dec 2012 18:59:35 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id qB4HxTjE027969; Tue, 4 Dec 2012 18:59:31 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 4 Dec 2012 18:59:14 +0100
Received: from 10.144.247.15 ([10.144.247.15]) by FIESEXC035.nsn-intra.net ([10.159.0.182]) with Microsoft Exchange Server HTTP-DAV ;  Tue,  4 Dec 2012 17:59:14 +0000
User-Agent: Microsoft-Entourage/12.35.0.121009
Date: Tue, 04 Dec 2012 19:59:13 +0200
Subject: Re: Simplifying our processes: Conference Calls
From: Hannes Tschofenig <Hannes.Tschofenig@nsn.com>
To: Dave Crocker <dcrocker@bbiw.net>
Message-ID: <CCE40691.1531%Hannes.Tschofenig@nsn.com>
Thread-Topic: Simplifying our processes: Conference Calls
Thread-Index: Ac3SSRFmq6nqeY9Tz0eWsECC+O13UQ==
In-Reply-To: <50BE3721.90004@dcrocker.net>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-OriginalArrivalTime: 04 Dec 2012 17:59:15.0088 (UTC) FILETIME=[12A54900:01CDD249]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 265
X-purgate-ID: 151667::1354643976-00006291-F8A13D1A/0-0/0-0
X-Mailman-Approved-At: Tue, 04 Dec 2012 12:47:59 -0800
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, 04 Dec 2012 18:00:11 -0000

> The concept is simple:  a time-specific gather is a meeting.  Meetings
> require prior announcement beyond the working group.

I am not against a meeting announcement. I am suggesting to announce the
meeting where the audience is -- in the working group. 


From d3e3e3@gmail.com  Tue Dec  4 13:42:19 2012
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 49E5F21F8BC4 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 13:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.379
X-Spam-Level: 
X-Spam-Status: No, score=-103.379 tagged_above=-999 required=5 tests=[AWL=0.220, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yYVktdVU2oFV for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 13:42:18 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id BB13821F8BC1 for <ietf@ietf.org>; Tue,  4 Dec 2012 13:42:18 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so7490941ieb.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 13:42:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FRhgeB2T87K5t0CT09OdYfsU2BeUwgbsRLKcKGxDqX8=; b=lPmSe9e7w14zNuC3rE73X69NcfAmk8UW+abbN3/vfu4XwbZpEcBIyNC3PYBxe49FvL i92ueqpRGt1TAxQcAqEcu90PSpe3DRYwVIUUwYUcD7U+BEhAqp+KFC1uStG6g/uY5bj3 5vlFyx8JE8wtjJmC2yIkkVi/7mJW4qoFBEhUIZ6eGwZMR1PF2k4HZV0yI4f5TafnEV0j O6NkjvS1r46qbdMgGUFMFEQkVGdGb1u+YsbGLMi9gTMNfwVZ7Y6O5Wp1i1QJgRN3f8RO WUKVAGh3Tvy/KLxsNviBPnzPAlk91O2P9nNgkxoV/GJWk/I2cvIyrbrdFR90I54Ki/Gu UBYA==
Received: by 10.50.34.201 with SMTP id b9mr4228982igj.55.1354657335555; Tue, 04 Dec 2012 13:42:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.28.209 with HTTP; Tue, 4 Dec 2012 13:41:54 -0800 (PST)
In-Reply-To: <CCE40691.1531%Hannes.Tschofenig@nsn.com>
References: <50BE3721.90004@dcrocker.net> <CCE40691.1531%Hannes.Tschofenig@nsn.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 4 Dec 2012 16:41:54 -0500
Message-ID: <CAF4+nEGATcHjM0360Vun1KdxsHabxuSyVRPzsFqo-Ex5eqvJ4w@mail.gmail.com>
Subject: Re: Simplifying our processes: Conference Calls
To: Hannes Tschofenig <Hannes.Tschofenig@nsn.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: Tue, 04 Dec 2012 21:42:19 -0000

It's a question of costs and benefits. The cost of the IETF Announce
posting is small. There are not that many of them and I don't find
them to be a burden. The benefit in openness and transparency is
large. Thus the answer is simple and the policy should remain as it is
for now. If conditions change, it can certainly be revisited.

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


On Tue, Dec 4, 2012 at 12:59 PM, Hannes Tschofenig
<Hannes.Tschofenig@nsn.com> wrote:
>> The concept is simple:  a time-specific gather is a meeting.  Meetings
>> require prior announcement beyond the working group.
>
> I am not against a meeting announcement. I am suggesting to announce the
> meeting where the audience is -- in the working group.
>

From wesley.george@twcable.com  Tue Dec  4 14:18:57 2012
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 9241B21F8AF8 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 14:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[AWL=0.355,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGJG4rthq-B9 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 14:18:56 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id B98B421F8AF4 for <ietf@ietf.org>; Tue,  4 Dec 2012 14:18:56 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,217,1355115600"; d="scan'208";a="482728522"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 04 Dec 2012 17:18:46 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Tue, 4 Dec 2012 17:18:55 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>
Date: Tue, 4 Dec 2012 17:19:14 -0500
Subject: RE: A mailing list protocol
Thread-Topic: A mailing list protocol
Thread-Index: Ac3SYIJZ1Q2qb4/pQN2q54OlMWJAjAABq2BQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net>
In-Reply-To: <6.2.5.6.2.20121204121234.09360870@resistor.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-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 22:18:57 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> S Moonesamy
>
>   (b) replies to messages which use an odd quoting style [2].
>
> 2. http://home.in.tum.de/~jain/software/outlook-quotefix/

[WEG] The referenced program doesn't work for anything 2007 or later (aka v=
ersions still supported by MS), making it of limited use.

Is there an IETF standard format for handling inline quote replies? Is it j=
ust not implemented in certain mail clients? If there isn't a relevant stan=
dard, then we have no business whining that people are doing it "wrong", an=
d we should probably get to work defining one, either for use on the client=
 side, or possibly an extension for common mailman software to parse and fi=
x it on the server side to compensate for odd client implementations.

The last thread that talked about how to do email "correctly" focused on th=
e usual bashing of those using outlook or company email addresses, rather t=
han much in the way of helpful advice on how to make it less bad.
[ https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D933&k2=3D6491=
1&tid=3D1354657596 ]

Browbeating people into changing mail clients will be less than effective, =
but something that systematically makes it easier to see who is responsible=
 for what comment in a multi-person thread regardless of source email clien=
t would be welcome. While we're at it, we could maybe implement a fix for t=
he common problem of mangled subject lines that make it very difficult to s=
ort by thread, and add a server-side filter that removes the legal bilgewat=
er automatically added to some outgoing messages (example will follow in th=
is very message) before sending it to the rest of the list recipients, etc.

I'd support a draft of that nature, but rehashing an old draft about nettiq=
uete 101 is less helpful. A simple reference to the original in the Tao web=
page would probably be sufficient to get the behavioral point across, and t=
hen we can focus more on the technical problem that we appear to have.

Wes George

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 tony@att.com  Tue Dec  4 14:35:01 2012
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F81321F88FD for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 14:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.306
X-Spam-Level: 
X-Spam-Status: No, score=-105.306 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y1tShUwR+Q4r for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 14:35:00 -0800 (PST)
Received: from nbfkord-smmo08.seg.att.com (nbfkord-smmo08.seg.att.com [209.65.160.95]) by ietfa.amsl.com (Postfix) with ESMTP id 3783F21F86F8 for <ietf@ietf.org>; Tue,  4 Dec 2012 14:35:00 -0800 (PST)
Received: from unknown [144.160.128.153] (EHLO flpi408.enaf.ffdc.sbc.com) by nbfkord-smmo08.seg.att.com(mxl_mta-6.11.0-12) over TLS secured channel with ESMTP id 39a7eb05.0.888881.00-435.2463605.nbfkord-smmo08.seg.att.com (envelope-from <tony@att.com>);  Tue, 04 Dec 2012 22:35:00 +0000 (UTC)
X-MXL-Hash: 50be7a944284c2c9-75d987ab982c34bfae0a3291b151c75e4f5d26b6
Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id qB4MYx2X015977 for <ietf@ietf.org>; Tue, 4 Dec 2012 14:34:59 -0800
Received: from fflint04.pst.cso.att.com (fflint04.pst.cso.att.com [150.234.39.64]) by flpi408.enaf.ffdc.sbc.com (8.14.5/8.14.5) with ESMTP id qB4MYq7H015668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 4 Dec 2012 14:34:54 -0800
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by fflint04.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Tue, 4 Dec 2012 14:34:34 -0800
Received: from aldc.att.com (localhost.localdomain [127.0.0.1]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qB4MYY3T002267 for <ietf@ietf.org>; Tue, 4 Dec 2012 17:34:34 -0500
Received: from dns.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpd052.aldc.att.com (8.14.4/8.14.4) with ESMTP id qB4MYQJT002138 for <ietf@ietf.org>; Tue, 4 Dec 2012 17:34:31 -0500
Received: from [135.70.31.90] (vpn-135-70-31-90.vpn.west.att.com[135.70.31.90]) by maillennium.att.com (mailgw1) with ESMTP id <20121204223416gw100632sje> (Authid: tony); Tue, 4 Dec 2012 22:34:22 +0000
X-Originating-IP: [135.70.31.90]
Message-ID: <50BE7A6A.1040300@att.com>
Date: Tue, 04 Dec 2012 17:34:18 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Useful slide tex (was - Re: English spoken here)
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <50BB92FB.5040904@dcrocker.net>	<50BB950A.9000408@network-heretics.com> <50BB9699.6070404@dcrocker.net> <50BB9888.8080906@network-heretics.com> <2671C6CDFBB59E47B64C10B3E0BD59230338B42BE8@PRVPEXVS15.corp.twcable.com> <50BCB718.6000805@network-heretics.com>
In-Reply-To: <50BCB718.6000805@network-heretics.com>
Content-Type: multipart/alternative; boundary="------------000403080405050607060203"
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010122901)]
X-MAIL-FROM: <tony@att.com>
X-SOURCE-IP: [144.160.128.153]
X-AnalysisOut: [v=2.0 cv=b/4FFK6x c=1 sm=0 a=xwOvzTHDVLE4u4nGvK72ag==:17 a]
X-AnalysisOut: [=ZfU0TMTo5CsA:10 a=PJtIR_1cTkwA:10 a=oLosoPsM5z4A:10 a=ofM]
X-AnalysisOut: [gfj31e3cA:10 a=BLceEmwcHowA:10 a=zQP7CpKOAAAA:8 a=F9ZbODHN]
X-AnalysisOut: [p60A:10 a=3_QxgV_0h7XgUSHR-L8A:9 a=wPNLvfGTeEIA:10 a=hFTPw]
X-AnalysisOut: [ipgAAAA:8 a=1nGmHW_cxS6ZtJGxzKAA:9 a=_W_S_7VecoQA:10 a=Ozz]
X-AnalysisOut: [FpYB2QQAA:10 a=RWqeqnv3Avcr9cVn:21]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2012 22:35:01 -0000

This is a multi-part message in MIME format.
--------------000403080405050607060203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12/3/2012 9:28 AM, Keith Moore wrote:
> On 12/03/2012 08:57 AM, George, Wes wrote: 
>> You have a very specific opinion of what an effective WG session 
>> should be like and what people should and should not be doing to 
>> facilitate such. Sounds like you need to work with the EDU team to 
>> give a Sunday afternoon training session entitled "how not to turn a 
>> WG session into a broadcast-only medium" possibly with a section for 
>> WG chairs and a section for potential speakers.
> Years ago, my impression was that that Sunday training sessions were 
> pretty much ignored by anyone experienced in the organization.  Is 
> this still the case?
>

Yes. However, the pan-galactic plenaries are still sort-of 
paid-attention-to by those who are present at the meetings, except for 
those totally distracted by the bad-attitude room.

     Tony Hansen

--------------000403080405050607060203
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">
    <link href="chrome://translator/skin/floatingPanel.css"
      type="text/css" rel="stylesheet">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    On 12/3/2012 9:28 AM, Keith Moore wrote:
    <blockquote type="cite">On 12/03/2012 08:57 AM, George, Wes wrote:
    </blockquote>
    <blockquote cite="mid:50BCB718.6000805@network-heretics.com"
      type="cite">
      <blockquote type="cite">You have a very specific opinion of what
        an effective WG session should be like and what people should
        and should not be doing to facilitate such. Sounds like you need
        to work with the EDU team to give a Sunday afternoon training
        session entitled "how not to turn a WG session into a
        broadcast-only medium" possibly with a section for WG chairs and
        a section for potential speakers.
        <br>
      </blockquote>
      Years ago, my impression was that that Sunday training sessions
      were pretty much ignored by anyone experienced in the
      organization.&nbsp; Is this still the case?
      <br>
      <br>
    </blockquote>
    <br>
    Yes. However, the pan-galactic plenaries are still sort-of
    paid-attention-to by those who are present at the meetings, except
    for those totally distracted by the bad-attitude room.<br>
    <br>
    &nbsp;&nbsp;&nbsp; Tony Hansen<br>
    <div style="bottom: auto; left: 429px; right: auto; top: 364px;
      display: none;" class="translator-theme-default"
      id="translator-floating-panel">
      <div title="Click to translate"
        id="translator-floating-panel-button"></div>
    </div>
  </body>
</html>

--------------000403080405050607060203--

From martin.thomson@gmail.com  Tue Dec  4 14:55:50 2012
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 4723B21F8AF4 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 14:55:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.741
X-Spam-Level: 
X-Spam-Status: No, score=-4.741 tagged_above=-999 required=5 tests=[AWL=-1.142, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AHhuxn4ZYOZx for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 14:55:49 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6080E21F8AF8 for <ietf@ietf.org>; Tue,  4 Dec 2012 14:55:49 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so3951024lbk.31 for <ietf@ietf.org>; Tue, 04 Dec 2012 14:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OddOAZjmI+Ka5QTLsLqEnn8Iii5Natiq/WL2AaXnqNQ=; b=HmC0tP4VsiAFVMyYK7f9bpBxbiy1wd269i8Qlb2ApbTiOiz0yIbv96XEAqsfeLVQ42 2N7DHzn6pl1Rbla/KC+ItzdubK60oiRMYaFhWrS8fC0IXk62rJh6057Xda1Ig+lTEs08 J+wOPork55+horuD5iN1ep16VGnQUbrecVh7DEGafVHDMci6/a3jqZ06VyzsZ3R3YRjs w7n7j/sOvPCWSYnk0AhHoR2OfD4mfZ24BhP7iVWeC9wX7cfXOPLwdO0SpeykxdVZj4iu 27XF0Ua5sxGYdKrCA/rSTkEJIA6+yypH51YC4iF1BzLs/O+3sRRHBujeNVftX41dTr/y c29g==
MIME-Version: 1.0
Received: by 10.112.49.65 with SMTP id s1mr3566160lbn.123.1354661746751; Tue, 04 Dec 2012 14:55:46 -0800 (PST)
Received: by 10.112.83.2 with HTTP; Tue, 4 Dec 2012 14:55:46 -0800 (PST)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
Date: Tue, 4 Dec 2012 14:55:46 -0800
Message-ID: <CABkgnnWG6Gn+StCBdft2Ku7B7pbZ-aS=6x2evESGzAr1EvnDyQ@mail.gmail.com>
Subject: Re: A mailing list protocol
From: Martin Thomson <martin.thomson@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=UTF-8
Cc: "ietf@ietf.org" <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: Tue, 04 Dec 2012 22:55:50 -0000

On 4 December 2012 14:19, George, Wes <wesley.george@twcable.com> wrote:
>> 2. http://home.in.tum.de/~jain/software/outlook-quotefix/
>
> [WEG] The referenced program doesn't work for anything 2007 or later (aka versions still supported by MS), making it of limited use.

I'm happy to share my (crappy) VB macro for doing this.  I recall
fixing it so that it worked from individual message windows (as
opposed to just the main window), but I lost the edit when I moved
companies and haven't bothered to go back and fix it.

http://pastebin.com/ebMv7vrw

Some effort required to install, but not beyond the capabilities of
anyone who could be bothered to try.

From lee@asgard.org  Tue Dec  4 15:22:23 2012
Return-Path: <lee@asgard.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 1C9FE21F8A73 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 15:22:23 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2XGK23LW02D for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 15:22:22 -0800 (PST)
Received: from atl4mhob11.myregisteredsite.com (atl4mhob11.myregisteredsite.com [209.17.115.49]) by ietfa.amsl.com (Postfix) with ESMTP id 78EA621F8A72 for <ietf@ietf.org>; Tue,  4 Dec 2012 15:22:22 -0800 (PST)
Received: from mailpod.hostingplatform.com (mail.networksolutionsemail.com [205.178.146.50]) by atl4mhob11.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id qB4NMLnq009099 for <ietf@ietf.org>; Tue, 4 Dec 2012 18:22:21 -0500
Received: (qmail 21300 invoked by uid 0); 4 Dec 2012 23:22:20 -0000
Received: from unknown (HELO HDC00042402) (lee@asgard.org@204.235.115.165) by 0 with ESMTPA; 4 Dec 2012 23:22:20 -0000
From: "Lee Howard" <lee@asgard.org>
To: "'Keith Moore'" <moore@network-heretics.com>, "George, Wes" <Wesley.George@twcable.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com>	<6.2.5.6.2.20121128023905.0afdcde0@resistor.net>	<50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com>	<CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com>	<00c001cdce7a$d9fa6490$8def2db0$@asgard.org>	<50B7EA5D.2030803@qti.qualcomm.com>	<50BA18B8.3090306@network-heretics.com>	<p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net>	<m2obidvuv7.wl%randy@psg.com>	<p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net>	<50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com>	<6.2.5.6.2.20121202073741.0ac80c68@resistor.net>	<A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com>	<50BB92FB.5040904@dcrocker.net>	<50BB950A.9000408@network-heretics.com>	<50BB9699.6070404@dcrocker.net>	<50BB9888.8080906@network-heretics.com>	<2671C6CDFBB59E47B64C10B3E0BD59230338B42BE8@PRVPEXVS15.corp.twcable.com> <50BCB718.! 6000805@network-heretic s.com>
In-Reply-To: <50BCB718.6000805@network-heretics.com>
Subject: RE: Useful slide tex (was - Re: English spoken here)
Date: Tue, 4 Dec 2012 18:22:20 -0500
Message-ID: <000301cdd276$3588bce0$a09a36a0$@asgard.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGuCiyth3j9q+DAiXDkQJ8JXg2BkwFC1Cu9AYkYgw0BXgZD1AGRdepaAVmcm4UBsznlCwHuiInzAgB0NMoBXIN30gFt5O/nAgpbDTwBngATYgL4aMHGAg0wbIAA3tTEDgIizXWYAgK0wFcCL1z3jwHbCBJRAdYJR+wB6ytcTAJrhQ6Ylw1+jiA=
Content-Language: en-us
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, 04 Dec 2012 23:22:23 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Keith Moore
> 
> Years ago, my impression was that that Sunday training sessions were
pretty much ignored
> by anyone experienced in the organization.  Is this still the case?

I've been to the newcomers tutorial at least five times in the last three
years.
I've been to tutorials on tools for creating internet-drafts two or three
times.
I continue to learn, and things change.  I recommend more attendees attend
more of these
sessions (in listening mode).

Lee




From swb@internet2.edu  Tue Dec  4 17:35:32 2012
Return-Path: <swb@internet2.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 D910321F8BE5 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 17:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzKbyJ57ifei for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 17:35:32 -0800 (PST)
Received: from int-proxy01.merit.edu (int-proxy01.merit.edu [207.75.116.230]) by ietfa.amsl.com (Postfix) with ESMTP id 5C97021F8BE4 for <ietf@ietf.org>; Tue,  4 Dec 2012 17:35:32 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy01.merit.edu (Postfix) with ESMTP id C75B2100013; Tue,  4 Dec 2012 20:35:31 -0500 (EST)
X-Virus-Scanned: amavisd-new at int-proxy01.merit.edu
Received: from int-proxy01.merit.edu ([127.0.0.1]) by localhost (int-proxy01.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nmko1gm54AX4; Tue,  4 Dec 2012 20:35:31 -0500 (EST)
Received: from com.flipdogsolutions (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy01.merit.edu (Postfix) with ESMTPSA id 3CBED100001; Tue,  4 Dec 2012 20:35:31 -0500 (EST)
Date: Tue, 4 Dec 2012 20:34:32 -0500
From: Scott Brim <swb@internet2.edu>
To: Martin Thomson <martin.thomson@gmail.com>, "George, Wes" <wesley.george@twcable.com>
Message-ID: <6eef05ba-d970-4f6b-9fde-acbd93035544.maildroid@localhost>
In-Reply-To: <CABkgnnWG6Gn+StCBdft2Ku7B7pbZ-aS=6x2evESGzAr1EvnDyQ@mail.gmail.com>
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <CABkgnnWG6Gn+StCBdft2Ku7B7pbZ-aS=6x2evESGzAr1EvnDyQ@mail.gmail.com>
Subject: Re: A mailing list protocol
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_1_1118717384.1354671272599"
Cc: "ietf@ietf.org" <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, 05 Dec 2012 01:35:33 -0000

------=_Part_1_1118717384.1354671272599
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Those are all endpoint implementation problems and thus not subject to IETF standardization :-)
------=_Part_1_1118717384.1354671272599
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<p>Those are all endpoint implementation problems and thus not subject to IETF standardization :-)</p>

------=_Part_1_1118717384.1354671272599--

From moore@network-heretics.com  Tue Dec  4 19:03:49 2012
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 50BAB21F8BD6 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 19:03:49 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJSRFu8eHl+i for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 19:03:48 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id B3AF621F8BA0 for <ietf@ietf.org>; Tue,  4 Dec 2012 19:03:48 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 7761C20A30; Tue,  4 Dec 2012 22:03:47 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 04 Dec 2012 22:03:47 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type; s=smtpout; bh=Xkk5 OJy7e902juzZi29mtm7RLyk=; b=czEs6QR3DWOuQD6O0a26aUs6GBFMIVhtdpmD 00lRFl65vnOULw8PKRkh/UpvMdWnMDr7W4jQi4fQol/QO+zlAHhil5qMySODIncv pds6oNx7OSakPnYxKqU4YLxkOF+3aODgsnop3lP47oZ/W+cEyvmJ4tlhh/XzeGqC L8kqPo8=
X-Sasl-enc: ZsOfdOgR1tZiEDbMaGD8jgim808Y0jsvsOIA+CQtkmqO 1354676626
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6C61F482669; Tue,  4 Dec 2012 22:03:46 -0500 (EST)
Message-ID: <50BEB98E.7030703@network-heretics.com>
Date: Tue, 04 Dec 2012 22:03:42 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Steven Bellovin <smb@cs.columbia.edu>
Subject: Re: English spoken here
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <B933B8C9-F858-4D19-8F45-109A996321B2@cs.columbia.edu>
In-Reply-To: <B933B8C9-F858-4D19-8F45-109A996321B2@cs.columbia.edu>
Content-Type: multipart/alternative; boundary="------------020504010103030105090402"
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.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, 05 Dec 2012 03:03:49 -0000

This is a multi-part message in MIME format.
--------------020504010103030105090402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 12/04/2012 12:50 PM, Steven Bellovin wrote:
> I started making up really good slides (in a variety of settings)
> after noticing non-native-English speakers at the IETF taking
> pictures of the screen -- it*really*  helped them.
I used to see that also, but I don't recall seeing anyone do that in 
Atlanta.  Maybe people just download the slides now?



--------------020504010103030105090402
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 12/04/2012 12:50 PM, Steven Bellovin
      wrote:<br>
    </div>
    <blockquote
      cite="mid:B933B8C9-F858-4D19-8F45-109A996321B2@cs.columbia.edu"
      type="cite">
      <pre wrap="">I started making up really good slides (in a variety of settings)
after noticing non-native-English speakers at the IETF taking
pictures of the screen -- it <b class="moz-txt-star"><span class="moz-txt-tag">*</span>really<span class="moz-txt-tag">*</span></b> helped them.</pre>
    </blockquote>
    I used to see that also, but I don't recall seeing anyone do that in
    Atlanta.&nbsp; Maybe people just download the slides now?<br>
    <br>
    <br>
  </body>
</html>

--------------020504010103030105090402--

From dougb@dougbarton.us  Tue Dec  4 19:09:51 2012
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 75E7321F8C00 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 19:09:51 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Iq+iOZVLv3B6 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 19:09:51 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id CCECE21F8BFE for <ietf@ietf.org>; Tue,  4 Dec 2012 19:09:50 -0800 (PST)
Received: (qmail 20281 invoked by uid 399); 5 Dec 2012 03:09:29 -0000
Received: from unknown (HELO ?192.168.0.100?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 5 Dec 2012 03:09:29 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50BEBAF8.4010900@dougbarton.us>
Date: Tue, 04 Dec 2012 19:09:44 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Hannes Tschofenig <Hannes.Tschofenig@nsn.com>
Subject: Re: Simplifying our processes: Conference Calls
References: <CCE40691.1531%Hannes.Tschofenig@nsn.com>
In-Reply-To: <CCE40691.1531%Hannes.Tschofenig@nsn.com>
X-Enigmail-Version: 1.4.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Dave Crocker <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, 05 Dec 2012 03:09:51 -0000

On 12/04/2012 09:59 AM, Hannes Tschofenig wrote:
>> The concept is simple:  a time-specific gather is a meeting.  Meetings
>> require prior announcement beyond the working group.
> 
> I am not against a meeting announcement. I am suggesting to announce the
> meeting where the audience is -- in the working group. 

Hannes,

You've stated your perspective several times now. Each time a
non-trivial number of people have spoken up to say that they understand
your perspective, and that while under certain circumstances it may be a
reasonable one; that's not how the IETF operates.

Can we move on now?

Doug


From danny@tcb.net  Tue Dec  4 20:05:33 2012
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 05EA521F8C03 for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 20:05:33 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cHRdwHaCnyod for <ietf@ietfa.amsl.com>; Tue,  4 Dec 2012 20:05:32 -0800 (PST)
Received: from mail.friendswithtools.org (unknown [64.78.239.70]) by ietfa.amsl.com (Postfix) with ESMTP id 9B0D421F8BFF for <ietf@ietf.org>; Tue,  4 Dec 2012 20:05:32 -0800 (PST)
Received: from dspam (unknown [127.0.0.1]) by mail.friendswithtools.org (Postfix) with SMTP id 5C37F2468 for <ietf@ietf.org>; Wed,  5 Dec 2012 04:05:32 +0000 (UTC)
Received: from [172.17.67.35] (unknown [76.8.75.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.friendswithtools.org (Postfix) with ESMTPSA id BEEB12464; Tue,  4 Dec 2012 21:05:31 -0700 (MST)
Subject: Re: Idea for a process experiment to reward running code...
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Danny McPherson <danny@tcb.net>
In-Reply-To: <CAC4RtVBcRX6WM3bCV_MFr5F08j3z8M0dn7Mg20ZR2x+Yfn8xNw@mail.gmail.com>
Date: Tue, 4 Dec 2012 23:05:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A38293F-E79C-49E6-8D3D-71F92288E6AF@tcb.net>
References: <50BA64AB.3010106@cs.tcd.ie> <50BC401C.8020101@it.aoyama.ac.jp> <50BC86B7.1010706@gmail.com> <1354545525.11916.744.camel@mightyatom> <50BD8E60.5030206@it.aoyama.ac.jp> <m2r4n6f28s.wl%randy@psg.com> <CAC4RtVBcRX6WM3bCV_MFr5F08j3z8M0dn7Mg20ZR2x+Yfn8xNw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1283)
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Tue Dec  4 21:05:32 2012
X-DSPAM-Confidence: 1.0000
X-DSPAM-Improbability: 1 in 98689409 chance of being spam
X-DSPAM-Probability: 0.0023
X-DSPAM-Signature: 50bec80c199631316099132
X-DSPAM-Factors: 27, that+#+#+mean, 0.40000, code+#+#+#+such, 0.40000, our+#+#+slogan, 0.40000, lend+such, 0.40000, Real+#+#+#+does, 0.40000, Subject*Idea+#+#+process, 0.40000, an+extra, 0.40000, getting+#+#+#+running, 0.40000, just+#+#+#+it, 0.40000, doesn't+#+#+#+see, 0.40000, meetings+#+#+#+danny, 0.40000, runs+It, 0.40000, certainly+#+whether, 0.40000, if+#+#+the, 0.40000, Subject*for+#+#+#+to, 0.40000, where+#+getting, 0.40000, code+#+#+nice, 0.40000, but+#+#+in, 0.40000, we+#+see, 0.40000, 4+#+at, 0.40000, doesn't+mean, 0.40000, almost+#+#+#+we, 0.40000, is+that, 0.40000, code+#+not, 0.40000, you're+#+#+consultancy, 0.40000, doesn't+#+simply, 0.40000, draft+get, 0.40000
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: Wed, 05 Dec 2012 04:05:33 -0000

On Dec 4, 2012, at 9:46 AM, Barry Leiba wrote:

>=20
> But the point of "running code" in our nice, catchy slogan, is that
> "running" doesn't mean simply that it runs.  It means that it's
> actually *in use*, possibly for real, but at least in a test lab where
> it's getting real use.  *Real* running code probably does lend such
> confidence.  Code that's just been written because it helps your draft
> get an extra tick mark in a box almost certainly doesn't, whether we
> can see and understand the source code or not.

But Barry - if you're in the consultancy business and wear "running code =
and run away" shirts to IETF meetings; well. perspectives diverge...

-danny



From smb@cs.columbia.edu  Wed Dec  5 05:45:09 2012
Return-Path: <smb@cs.columbia.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 0EF7721F8A72 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 05:45:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RZT3B12ypWSV for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 05:45:08 -0800 (PST)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4559D21F89AD for <ietf@ietf.org>; Wed,  5 Dec 2012 05:45:08 -0800 (PST)
Received: from [10.9.0.186] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id qB5DiKed025567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 5 Dec 2012 08:45:07 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: English spoken here
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <50BEB98E.7030703@network-heretics.com>
Date: Wed, 5 Dec 2012 08:45:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B806A4F-0C9A-48D5-B7C1-D93E7F345149@cs.columbia.edu>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <B933B8C9-F858-4D19-8F45-109A996321B2@cs.columbia.edu> <50BEB98E.7030703@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1499)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.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, 05 Dec 2012 13:45:09 -0000

On Dec 4, 2012, at 10:03 PM, Keith Moore <moore@network-heretics.com> =
wrote:

> On 12/04/2012 12:50 PM, Steven Bellovin wrote:
>> I started making up really good slides (in a variety of settings)
>> after noticing non-native-English speakers at the IETF taking
>> pictures of the screen -- it=20
>> *really* helped them.
> I used to see that also, but I don't recall seeing anyone do that in =
Atlanta.  Maybe people just download the slides now?
>=20
That's my assumption -- the infrastructure and policies are better
set up now for that sort of thing.


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






From abdussalambaryun@gmail.com  Wed Dec  5 05:59:13 2012
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 A3D4321F8973 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 05:59:13 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RBfkCrOBknu2 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 05:59:12 -0800 (PST)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id 737FE21F8860 for <ietf@ietf.org>; Wed,  5 Dec 2012 05:59:12 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id l1so7002257vba.27 for <ietf@ietf.org>; Wed, 05 Dec 2012 05:59:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ePyAul6BGWKllaXIw4hqTNgiwu8MkP0WcpEGUzouoVM=; b=sPrXST10jnT+amBsIRD4mAS4a+/Ohc3RgX5m0iR3IciLeyiZIsTpp1wDMc6c5k87Rv KJYoaE/W1hmbYdlEAKYv7XMNEiJUKWkw3nR4FrcZdv4XMiZd5BDtYL+7SbOPdrGiwPvj YFQG+q7jyeRkXYmSg9J0lL0qdvP6oadpbi3R+2qQg0iqoQi1YhmmemTUNrgG6hh7COaC oLq9UMCuehZ0GsDNiv0JYnYl9vBMJSaUdGqn1xj6eTNgDe8XObn15l5oXPI5sRzt9l0H tqAwy7GMgeCChLOE9TPvqiroKXnuP0GZDHXRHeNDUh+USu8SPj/AtWZjdeM4e/xDsRO5 n+qQ==
MIME-Version: 1.0
Received: by 10.52.77.101 with SMTP id r5mr13245476vdw.25.1354715951916; Wed, 05 Dec 2012 05:59:11 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 5 Dec 2012 05:59:11 -0800 (PST)
In-Reply-To: <051501cdd237$2959aef0$7c0d0cd0$@olddog.co.uk>
References: <CADnDZ8937L+sGEEj+4QUu33yxhRdm0M_OHAa6sr509hXtc7oJQ@mail.gmail.com> <051501cdd237$2959aef0$7c0d0cd0$@olddog.co.uk>
Date: Wed, 5 Dec 2012 14:59:11 +0100
Message-ID: <CADnDZ88Lz0Ao4WLc-v+XhpJ=BMDOT9OiW48Z=jOeQOVOw8NHLQ@mail.gmail.com>
Subject: Re: Creating an IETF Working Group Draft
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian@olddog.co.uk
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: Wed, 05 Dec 2012 13:59:13 -0000

Hi Adrian,

> Dave and I will include what is reasonable and seek a consensus that agrees
> with our motivation for writing the document.

I agree totally that only reasonable inputs to Internet Society SHOULD
go through, that is why I am participating, but I when I see no
reasonable input discussed, so I try to fix in IETF and ask to
clarify. Your info-draft is an important information document/input to
clarify the reasons of such managerial decisions in IETF. Always
consensus follow reasonable decisions, because if any participant
(including chairs and ADs) refuse a decision they SHOULD provide a
good reason announced, if they fail then I recommend they are just put
noise against science and engineering.

In general, *Any IETF input SHOULD have an announced/discussed
reason*. I posted before about this [1]. I suggest here that the draft
should make clear *what* drives our documents/decisions which I
beleive is the *knowledgable reasons, science, and engineering*.
Hiding the reason of such decision SHOULD not be a process in our IETF
organisation, if we follow its principles. I think few of processes in
IETF (if not many) still have some non clear announcements by
managers, editors, or by processors. When I finish my overview and
complaints/documents I will be more clear of such processes. However,
my initial specific input as below.

AB>Amend section 1.2>to working group chairs who are charged with
running the process:
AB>to> to working group chairs who are assigned to run the process:

AB>Adding Qs in section 1.2>

-Who is authorise by IETF to make decision in WG to adopt or refuse
such I-D. Should it be in an announce reason or without announcement,
or with no understood reason?

-If the I-D is out of scope of the WG charter, still could the WG adopt it?

- Is the WG charter important influence for the reasons of any
decision made regarding documents, or the market interests and WG
consensus are the main influencer?

- Is a WG chair or AD authorise to call to re-charter WG if the WG
refuses to adopt an I-D, or WGs have power to direct their input to
the IETF WG?

AB> Comments on 1.2> I don't think there is differences in adopt or
care or consideration of WG, if they are interested in such work they
will adopt it, and if they change their interest in future they can
refuse to submit it. The Chairs and ADs SHOULD not control such
decisions that the WG make [2]. If the WG don't get to a decision, the
Chairs and ADs SHOULD undersdtand the reasons and make them announced
and clear. IETF is an Engineering organisation, only good intelligent
engineering reason SHOULD maintain, and others SHOULD stop the noise
if no reason or value in such input. Therefore, only input with
known/documented reasons should progress [1][3].

[1] http://www.ietf.org/mail-archive/web/ietf/current/msg74750.html
[2] http://www.ietf.org/mail-archive/web/ietf/current/msg75119.html
[3] http://www.ietf.org/mail-archive/web/ietf/current/msg75118.html

AB
__

On 12/4/12, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Abdussalam,
>
> By all means send text or suggestions for edits.
>
> Dave and I will include what is reasonable and seek a consensus that agrees
> with
> our motivation for writing the document.
>
> Thanks,
> Adrian
>
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Abdussalam Baryun
> Sent: 04 December 2012 13:33
> To: dhc@dcrocker.net
> Cc: ietf
> Subject: Re: Creating an IETF Working Group Draft
>
> Hi Dave,
>
> Thanks for your work, please provide us with feedback while the process of
> editing. I was thinking to do something in the future, but thanks that you
> will
> do it.
>
> AB
>
> Folks, There is now an Internet Draft, based on Adrian's's slides, intended
> to
> document common practice in the adoption of working group drafts:
> Title:   Creating an IETF Working Group Draft
> Status:  http://datatracker.ietf.org/doc/draft-crocker-id-adoption
>
> Abstract:
>    The productive output of IETF working groups is documents, as
>    mandated by the working group's charter.  Working groups develop
>    these documents based on initial input of varying levels of maturity.
>    An initial working group draft might be a document already in wide
>    use, or it might be a blank sheet, wholly created by the workiing
>    group, or it might represent any level of maturity in between.  This
>    document discusses the process of creating formal working group
>    drafts that are targeted for publication.
>
> Although it is not intended for a standards-track or bcp publication, it
> would
> be helpful to have discussion that moves the document to represent good
> agreement among the community.
> d/
>
> --
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net
>

From arturo.servin@gmail.com  Wed Dec  5 06:16:51 2012
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 F370C21F8BCA for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:16:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9nvmSm9L3RMw for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:16:50 -0800 (PST)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 677C421F8BC7 for <ietf@ietf.org>; Wed,  5 Dec 2012 06:16:50 -0800 (PST)
Received: by mail-gg0-f172.google.com with SMTP id r1so846372ggn.31 for <ietf@ietf.org>; Wed, 05 Dec 2012 06:16:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LcXGzD6uZtRnO15aKVvVaGHcUBAgOSLGTOKCVvUD+YI=; b=DDb6G6QbnCL169UKAInuuIn+e8ULQHxTkj2OED19BJXGnHM7atYzjcR0tUDsar2rKE LSbthSB1GE96cZrMGkjg7kfM3Rs7DeXhd1lAcndLzqis1UZJUXpvhj29hCcQROQJTZAp RHXUGHXhk+8TmOQ2v3gG2nsuokGpZLvPxzcJN0KGh+AhmLZQMXrpRChSY5mOpqxz9rQ5 MbT/YCmFZih6twLIZw+jiWstIsrZCq+V42A+lFtXapa51n1FZYV76zM4nidsJmWzB02O FZ6H+rbXDmz2zetsXdDXq99YJ6BeFk8eoq/mV/MhqNEVEhlhdHP08/QTpCvfOsWJRBqs 1KRQ==
Received: by 10.236.126.196 with SMTP id b44mr20527752yhi.21.1354717010002; Wed, 05 Dec 2012 06:16:50 -0800 (PST)
Received: from 219.9.wired.gter.nic.br ([2001:12ff:0:8:3001:3e91:ed16:122a]) by mx.google.com with ESMTPS id p17sm4668767anh.12.2012.12.05.06.16.47 (version=SSLv3 cipher=OTHER); Wed, 05 Dec 2012 06:16:48 -0800 (PST)
Message-ID: <50BF574F.20505@gmail.com>
Date: Wed, 05 Dec 2012 12:16:47 -0200
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A mailing list protocol
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <CABkgnnWG6Gn+StCBdft2Ku7B7pbZ-aS=6x2evESGzAr1EvnDyQ@mail.gmail.com> <6eef05ba-d970-4f6b-9fde-acbd93035544.maildroid@localhost>
In-Reply-To: <6eef05ba-d970-4f6b-9fde-acbd93035544.maildroid@localhost>
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: Wed, 05 Dec 2012 14:16:51 -0000

	What are "those"?

	Without the context it is impossible to guess, at least for me.

.as


On 04/12/2012 23:34, Scott Brim wrote:
> Those are all endpoint implementation problems and thus not subject to
> IETF standardization :-)
> 

From john-ietf@jck.com  Wed Dec  5 06:29:13 2012
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 ED85A21F8BF7 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:29:13 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bAR0Hrq460PT for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:29:13 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7754621F8C9E for <ietf@ietf.org>; Wed,  5 Dec 2012 06:29:13 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TgFyA-0004tP-VS; Wed, 05 Dec 2012 09:29:02 -0500
Date: Wed, 05 Dec 2012 09:28:53 -0500
From: John C Klensin <john-ietf@jck.com>
To: Steven Bellovin <smb@cs.columbia.edu>, Keith Moore <moore@network-heretics.com>
Subject: Re: English spoken here
Message-ID: <30D7C679AD7C1793B07DF2C3@JcK-HP8200.jck.com>
In-Reply-To: <8B806A4F-0C9A-48D5-B7C1-D93E7F345149@cs.columbia.edu>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <50B5C839.4060909@gmail.com> <59924CD37D50616BA8EB8EF7@JcK-HP8200.jck.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im> <50B68612.7080107@dcrocker.net>	<50B693ED.7000609@stpeter.im> <50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <6.2.5.6.2.20121202073741.0ac80c68@resistor.net> <A1D3CE1A0AA345FE0ECB6697@JcK-HP8200.jck.com> <B933B8C9-F858-4D19-8F45-109A996321B2@cs.columbia.edu> <50BEB98E.7030703@network-heretics.com> <8B806A4F-0C9A-48D5-B7C1-D93E7F345149@cs.columbia.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: SM <sm@resistor.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, 05 Dec 2012 14:29:14 -0000

--On Wednesday, December 05, 2012 08:45 -0500 Steven Bellovin
<smb@cs.columbia.edu> wrote:

>> I used to see that also, but I don't recall seeing anyone do
>> that in Atlanta.  Maybe people just download the slides now?
>> 
> That's my assumption -- the infrastructure and policies are
> better set up now for that sort of thing.

But it does reinforce the importance of getting materials posted
well before the meeting begins.

  john






From abdussalambaryun@gmail.com  Wed Dec  5 06:43:36 2012
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 2BC2C21F8C9B for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:43:36 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5nPWsBkbStc for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:43:35 -0800 (PST)
Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by ietfa.amsl.com (Postfix) with ESMTP id 98BF521F8B2B for <ietf@ietf.org>; Wed,  5 Dec 2012 06:43:35 -0800 (PST)
Received: by mail-vb0-f54.google.com with SMTP id l1so7094226vba.27 for <ietf@ietf.org>; Wed, 05 Dec 2012 06:43:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=2CRcjZFAwhc5xgFVeWKUbGs1VBaCATF0hccoVLu7ozY=; b=C2F5MW2qBxIgcNURwfVTkUlxdEXX1SwG/Gjs1k5BI2zTpLSJUJT19eJM5+hzCRtL1i 3ba1ktq7nPHOjR6Bzr9gA8X+CseRN0gC5DBODDbSije4I52fsHphBEh/ctJyLBqqXc/e pvOXSEqcGbtZhJMByWk3OXXuKOWiXhj9JEwVcBh6HMQronYGtrs6/ulXh0oblFuG59IH d67s4TpJMQ0ABlIFhMTT9c/Fyjxi90OWUPZ10u4BYOl91+KdE9nU7UpAMqFyLrZ5/VLe NDlw8r++YIY6h0EkVJIiUogKO61hWKJxhBVBULKTFnvaso3upst8t+3C/u0TjZGFLl1z 1U7Q==
MIME-Version: 1.0
Received: by 10.58.137.7 with SMTP id qe7mr15813078veb.23.1354718615073; Wed, 05 Dec 2012 06:43:35 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Wed, 5 Dec 2012 06:43:34 -0800 (PST)
Date: Wed, 5 Dec 2012 15:43:34 +0100
Message-ID: <CADnDZ8_vsWwmvZ13z32UXJbFH5A6L_ptJoE_ymThg0K_GJ8pZA@mail.gmail.com>
Subject: RE: Idea for a process experiment to reward running code...
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: stephen.farrell@cs.tcd.ie
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: Wed, 05 Dec 2012 14:43:36 -0000

Hi Stephen,

I think it is great idea, I hope it does not die, we need fast-tracks,
without delays, however, giving a fixed time limit for WG feedback and
WG discussion is important  (suggested 6 months), because discussions
about running code should not be ignored. The draft seems to not give
chance to WG to make a formal decision on its adopted work, why you
put the chair to decide for WG of taking the fast track?

AB
----

Hi all,

I've just posted an idea [1] for a small process improvement.
If it doesn't seem crazy I'll try pursue it with the IESG as
an RFC 3933 process experiment. If its universally hated then
that's fine, it can die.

The IESG have seen (more-or-less) this already but it hasn't
be discussed, so this is just a proposal from me and has no
"official" status whatsoever.

Any comments, suggestions or better ideas are very welcome.
Feel free to send me comments off list for now, or on this
list I guess. If there's loads of email (always possible,
this being a process thing;-) we can move to some other list.

Regards,
Stephen.

[1] http://tools.ietf.org/id/draft-farrell-ft

From stephen.farrell@cs.tcd.ie  Wed Dec  5 06:51:44 2012
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 0B6E321F896C for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:51:44 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WL2bRnDdLLXC for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 06:51:43 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1AF21F8904 for <ietf@ietf.org>; Wed,  5 Dec 2012 06:51:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5C081BE53; Wed,  5 Dec 2012 14:51:21 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B4ZQefDbODs; Wed,  5 Dec 2012 14:51:20 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:8fe:f2f3:f980:9bca] (unknown [IPv6:2001:770:10:203:8fe:f2f3:f980:9bca]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 60ADABE3C; Wed,  5 Dec 2012 14:51:20 +0000 (GMT)
Message-ID: <50BF5F69.2000503@cs.tcd.ie>
Date: Wed, 05 Dec 2012 14:51:21 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Idea for a process experiment to reward running code...
References: <CADnDZ8_vsWwmvZ13z32UXJbFH5A6L_ptJoE_ymThg0K_GJ8pZA@mail.gmail.com>
In-Reply-To: <CADnDZ8_vsWwmvZ13z32UXJbFH5A6L_ptJoE_ymThg0K_GJ8pZA@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 05 Dec 2012 14:51:44 -0000

Hiya,

This proposal only kicks in (as an option) after the WG have
done their job, however they choose to do that (within the
IETF process).

Later on, it might be a fine idea to try extend the fast-track
concept so that a WG has a structured way do similar things
but IMO that'd be better done after we get some experience
with the experiment at the point where the WG get broader IETF
review and hand stuff over to the IESG.

So what you're asking about is not within the scope of this
particular 3933 experiment.

Cheers,
Stephen.

On 12/05/2012 02:43 PM, Abdussalam Baryun wrote:
> Hi Stephen,
> 
> I think it is great idea, I hope it does not die, we need fast-tracks,
> without delays, however, giving a fixed time limit for WG feedback and
> WG discussion is important  (suggested 6 months), because discussions
> about running code should not be ignored. The draft seems to not give
> chance to WG to make a formal decision on its adopted work, why you
> put the chair to decide for WG of taking the fast track?
> 
> AB
> ----
> 
> Hi all,
> 
> I've just posted an idea [1] for a small process improvement.
> If it doesn't seem crazy I'll try pursue it with the IESG as
> an RFC 3933 process experiment. If its universally hated then
> that's fine, it can die.
> 
> The IESG have seen (more-or-less) this already but it hasn't
> be discussed, so this is just a proposal from me and has no
> "official" status whatsoever.
> 
> Any comments, suggestions or better ideas are very welcome.
> Feel free to send me comments off list for now, or on this
> list I guess. If there's loads of email (always possible,
> this being a process thing;-) we can move to some other list.
> 
> Regards,
> Stephen.
> 
> [1] http://tools.ietf.org/id/draft-farrell-ft
> 
> 

From hannes.tschofenig@nsn.com  Wed Dec  5 01:25:58 2012
Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37AD21F8C9E for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 01:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.506
X-Spam-Level: 
X-Spam-Status: No, score=-106.506 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C6U8zKtZUrQG for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 01:25:58 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id DFA9421F8C99 for <ietf@ietf.org>; Wed,  5 Dec 2012 01:25:57 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id qB59PqG2014815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Dec 2012 10:25:52 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id qB59PgRk006353; Wed, 5 Dec 2012 10:25:52 +0100
Received: from FIESEXC035.nsn-intra.net ([10.159.0.25]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 5 Dec 2012 10:25:49 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Simplifying our processes: Conference Calls
Date: Wed, 5 Dec 2012 11:25:43 +0200
Message-ID: <999913AB42CC9341B05A99BBF358718D022E0BE8@FIESEXC035.nsn-intra.net>
In-Reply-To: <CAF4+nEGATcHjM0360Vun1KdxsHabxuSyVRPzsFqo-Ex5eqvJ4w@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Simplifying our processes: Conference Calls
Thread-Index: Ac3SaDvUttnfHPaFSkCEiK1IwKJy1wAYcDPA
References: <50BE3721.90004@dcrocker.net> <CCE40691.1531%Hannes.Tschofenig@nsn.com> <CAF4+nEGATcHjM0360Vun1KdxsHabxuSyVRPzsFqo-Ex5eqvJ4w@mail.gmail.com>
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: "ext Donald Eastlake" <d3e3e3@gmail.com>
X-OriginalArrivalTime: 05 Dec 2012 09:25:49.0073 (UTC) FILETIME=[833E3010:01CDD2CA]
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 1381
X-purgate-ID: 151667::1354699553-00006291-791D25B9/0-0/0-0
X-Mailman-Approved-At: Wed, 05 Dec 2012 08:01:42 -0800
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, 05 Dec 2012 09:25:58 -0000

Hi Donald,=20

> It's a question of costs and benefits. The cost of the IETF Announce
> posting is small. There are not that many of them and I don't find
> them to be a burden.

How many conference calls as part of working group activities did you
organize in the last two years?

Maybe there are not that many because the overhead is too high to
organize them.=20

> The benefit in openness and transparency is
> large.

Are working group activities not open and transparent in your view?

> Thus the answer is simple and the policy should remain as it is
> for now. If conditions change, it can certainly be revisited.
How many conference calls of working groups you are not subscribed to
did you attend?=20

Ciao
Hannes


> 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
>=20
> On Tue, Dec 4, 2012 at 12:59 PM, Hannes Tschofenig
> <Hannes.Tschofenig@nsn.com> wrote:
> >> The concept is simple:  a time-specific gather is a meeting.
> Meetings
> >> require prior announcement beyond the working group.
> >
> > I am not against a meeting announcement. I am suggesting to announce
> the
> > meeting where the audience is -- in the working group.
> >

From marc.blanchet@viagenie.ca  Wed Dec  5 08:09:51 2012
Return-Path: <marc.blanchet@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 32E3521F8CDB for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 08:09:51 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSB+VTRCRO+l for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 08:09:50 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 587B721F8CD8 for <ietf@ietf.org>; Wed,  5 Dec 2012 08:09:50 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B22D5412C7; Wed,  5 Dec 2012 11:09:49 -0500 (EST)
Subject: Re: Simplifying our processes: Conference Calls
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D022E0BE8@FIESEXC035.nsn-intra.net>
Date: Wed, 5 Dec 2012 11:09:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E4964F3-6E62-4AE0-AC1E-B2E5EAB1FAB3@viagenie.ca>
References: <50BE3721.90004@dcrocker.net> <CCE40691.1531%Hannes.Tschofenig@nsn.com> <CAF4+nEGATcHjM0360Vun1KdxsHabxuSyVRPzsFqo-Ex5eqvJ4w@mail.gmail.com> <999913AB42CC9341B05A99BBF358718D022E0BE8@FIESEXC035.nsn-intra.net>
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
X-Mailer: Apple Mail (2.1283)
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, 05 Dec 2012 16:09:51 -0000

Le 2012-12-05 =E0 04:25, Tschofenig, Hannes (NSN - FI/Espoo) a =E9crit :

> Hi Donald,=20
>=20
>> It's a question of costs and benefits. The cost of the IETF Announce
>> posting is small. There are not that many of them and I don't find
>> them to be a burden.
>=20
> How many conference calls as part of working group activities did you
> organize in the last two years?

I did some.

>=20
> Maybe there are not that many because the overhead is too high to
> organize them.=20

don't agree. Matter of minutes.

>=20
>> The benefit in openness and transparency is
>> large.

I agree with Donald.

Marc.

>=20
> Are working group activities not open and transparent in your view?
>=20
>> Thus the answer is simple and the policy should remain as it is
>> for now. If conditions change, it can certainly be revisited.
> How many conference calls of working groups you are not subscribed to
> did you attend?=20
>=20
> Ciao
> Hannes
>=20
>=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
>>=20
>> On Tue, Dec 4, 2012 at 12:59 PM, Hannes Tschofenig
>> <Hannes.Tschofenig@nsn.com> wrote:
>>>> The concept is simple:  a time-specific gather is a meeting.
>> Meetings
>>>> require prior announcement beyond the working group.
>>>=20
>>> I am not against a meeting announcement. I am suggesting to announce
>> the
>>> meeting where the audience is -- in the working group.
>>>=20


From dhc@dcrocker.net  Wed Dec  5 08:24:58 2012
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 0DB0021F8CCB for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 08:24:58 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yaYc+2e678qH for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 08:24:57 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id ECA4D21F8CB6 for <ietf@ietf.org>; Wed,  5 Dec 2012 08:24:56 -0800 (PST)
Received: from [192.168.1.9] (adsl-67-127-190-125.dsl.pltn13.pacbell.net [67.127.190.125]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qB5GOtoW023172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Dec 2012 08:24:56 -0800
Message-ID: <50BF754A.2080107@dcrocker.net>
Date: Wed, 05 Dec 2012 08:24:42 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
Subject: Re: Simplifying our processes: Conference Calls
References: <50BE3721.90004@dcrocker.net> <CCE40691.1531%Hannes.Tschofenig@nsn.com> <CAF4+nEGATcHjM0360Vun1KdxsHabxuSyVRPzsFqo-Ex5eqvJ4w@mail.gmail.com> <999913AB42CC9341B05A99BBF358718D022E0BE8@FIESEXC035.nsn-intra.net>
In-Reply-To: <999913AB42CC9341B05A99BBF358718D022E0BE8@FIESEXC035.nsn-intra.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.17]); Wed, 05 Dec 2012 08:24:56 -0800 (PST)
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, 05 Dec 2012 16:24:58 -0000

On 12/5/2012 1:25 AM, Tschofenig, Hannes (NSN - FI/Espoo) wrote:
>> It's a question of costs and benefits. The cost of the IETF Announce
>> posting is small. There are not that many of them and I don't find
>> them to be a burden.
>
> How many conference calls as part of working group activities did you
> organize in the last two years?


Hannes, your question is in response to the assertion that the cost of 
adding the IETF Announce list is small.  Ignoring the apparent 
non-sequitor of your response, the nature of your question implies that 
you think it is not small.  Please explain.

At base, you want to treat conference calls according to different rules 
than f2f meetings.  What I haven't seen is a principled explanation from 
you that justifies this.  So:  what are the underlying principles that 
justify treating conference calls as different from other time-specific 
IETF interactions?

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@elandsys.com  Wed Dec  5 08:54:35 2012
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 EB05221F8D02 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 08:54:35 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3+vyF7oyyCu for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 08:54:32 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1275121F8D00 for <ietf@ietf.org>; Wed,  5 Dec 2012 08:54:32 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.139.136]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qB5GsCg0001485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 5 Dec 2012 08:54:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1354726464; bh=fhJW1Qyhnp75r8pVKrQ5Zx+PMePpAUjV+wU8PXUI0cE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sVqsQ71f8B84aTcqIm6nmHbmTddI5UpuAgU7+ldJAi7QN8hSas5liTQ+a0K4DJgMS M84XNMfLcOJK66Soqs5D+OvuhCOxq5VTayyZRa546V6cLYzDbyhqia6wW4y5jYr7O2 uk2q6oK/fhkM3hlrBvHZtEdiMbubT9sy2Oqempf0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1354726464; i=@elandsys.com; bh=fhJW1Qyhnp75r8pVKrQ5Zx+PMePpAUjV+wU8PXUI0cE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AyPCFm0f1SEN72YsM0TvIG31UeaS63bDNEFPkJu7MU77Catfilz8+Ke4OmclTQgU7 6/b4ZST4ipco8GNWKifFWwuID/Mrx92d+mYBcXCfLgzsj4FbjUWILD4tLKeaTss8Ja 0oB4ah9te4QBMo9QJzAQx0mbpTX9DM9IKIIheZvU=
Message-Id: <6.2.5.6.2.20121205072148.0a0dbd38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 05 Dec 2012 08:52:59 -0800
To: Arturo Servin <arturo.servin@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A mailing list protocol
In-Reply-To: <50BF574F.20505@gmail.com>
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <CABkgnnWG6Gn+StCBdft2Ku7B7pbZ-aS=6x2evESGzAr1EvnDyQ@mail.gmail.com> <6eef05ba-d970-4f6b-9fde-acbd93035544.maildroid@localhost> <50BF574F.20505@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 16:54:36 -0000

Hi Arturo,
At 06:16 05-12-2012, Arturo Servin wrote:
>         What are "those"?
>
>         Without the context it is impossible to guess, at least for me.

According to=20
http://www.ietf.org/mail-archive/web/ietf/current/msg76273.html=20
the message posted by Scott Brim (=20
http://www.ietf.org/mail-archive/web/ietf/current/msg76275.html=20
) is a follow-up comment to the message posted by=20
Martin Thomson.  The messages posted by these two=20
persons are related to the message posted by Wes=20
George (=20
http://www.ietf.org/mail-archive/web/ietf/current/msg76271.html=20
).  That message contains the words "client=20
implementations".  The comment from Scott Brim could be rewritten as:

   The issues mentioned by George Wes and Martin Thomson are all endpoint
   implementation problems and thus not subject to IETF standardization.

As the sentence written by Scott Brim has a=20
smiley at the end, the idea expressed might be  somewhat similar to:

   Mi perro se comi=F3 las hojas donde estaban mis deberes del colegio.

The comment is actually a good argument.  Whether=20
it would be valid or not is a matter of context.

Regards,
S. Moonesamy=20


From ted.ietf@gmail.com  Wed Dec  5 09:22:18 2012
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 DF19721F8C05 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 09:22:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7qoDPKFJaM3 for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 09:22:13 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9C34521F8A85 for <ietf@ietf.org>; Wed,  5 Dec 2012 09:22:13 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id i20so1933043qad.10 for <ietf@ietf.org>; Wed, 05 Dec 2012 09:22:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=v+51ECtvqANFOUzGJQPMtQpht1N+mZ9vevsABknURLk=; b=sPvY3jdZRjsr1sVhy8KrJoPFG0zOyLjhAULZyWM8nFDZ0qPUGBtdqzMVzAtbBT6dFp VUHWULcAIClt9fFY+79lSRBllmq7HUuNy0vz0186Q1CGkRxTTQQ3veQJe+WSJMj+O0Jy 5vWmXWAaHU4wN3zoR90CHf7vkqhtey0vfE6Gzqk7A8jnR/261kW8PY4QDrM13/hgorD0 oGw3LoCzrYwv2rS3Tv7uyBFbsY81QSjkXWaFgfTxBk91kOTuIXTUuM+az2EWa5D1rqiW O9FuPMR3OG0kCCiUb9C7sA0XCnlSkO6mcJrVYYWZku9PqGFa+PqgDe2wLAhfYXDGzkMc ibRA==
MIME-Version: 1.0
Received: by 10.229.196.96 with SMTP id ef32mr6896449qcb.101.1354728131030; Wed, 05 Dec 2012 09:22:11 -0800 (PST)
Received: by 10.49.121.100 with HTTP; Wed, 5 Dec 2012 09:22:10 -0800 (PST)
Date: Wed, 5 Dec 2012 09:22:10 -0800
Message-ID: <CA+9kkMAGqeOzFHeGmmK6TvGctwO-heVrW5xoBseZ528goXJyOA@mail.gmail.com>
Subject: draft-farrell-ft-01.txt -- what signal are we attempting to sense?
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=0016e6d375a3046dcc04d01e3944
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2012 17:22:19 -0000

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

Reading through Stephen's draft and the discussion to date, I think there
is some confusion/disagreement about what it is having an implementation
at this stage signals.

One way to break up the work of the IETF is:

Engineering--making decisions about the trade-offs related to
             different approaches to solving a problem.

Specification--producing text that describes how to inter-operate with
others.

Standardization--describing the applicability of a specification or
         its suitability as the basis of other work

(Since we reflect all of these in the same document production, it's
really muddier than this, but bear with me)

My experience is that people implementing during the working group
discussion phase generate really useful data about the engineering;
they can tell you the real impact of different trade-offs, so that
this isn't based on general experience.  But it's not such a great
signal about the specification itself, since the spec is designed to
be usable by folks who were not part of the working group process.

Stephen's draft says:

   Note also that this experiment just needs an implementation that
   makes it possible for the WG chairs and responsible AD to verify (to
   the extent they chose) that the implementation matches the draft.

and later:

   An implementation of the draft (ideally open-source) is required
   for fast-track last-call.  If there is no implementation or if the
   implementation is unavailable or does not implement the draft
   sufficiently closely then the document needs to be returned to the
   WG.  This only requires one implementation, not two and the WG
   chairs and responsible AD decide themselves how much validation is
   required for this.

Given the "sufficiently closely" and the timing of production, I
assume that the signal we're looking for here is confirmation of the
engineering choices.  I think that's fine (though I'm not sure this
needs formal experiment status).  But I believe we need to be really
careful that it isn't mistaken for signal about the specification's
quality.  It can happen that a working group has "lore" about what to
do that gets folded into the implementations done by those
participating, but which never quite makes it into the spec "because
everyone knows it".  An implementation written during the working
group process is potentially subject to this effect.

An interoperating implementation written to the spec by a non-working
group participant would be great signal about the specification quality,
but it  is not likely to be available at the stage of the process this
draft
targets.

Again, not objecting to the experiment; I just want to be clear about
what signal we believe we're getting from the implementation.

Just my two cents,

Ted

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

Reading through Stephen&#39;s draft and the discussion to date, I think the=
re<br>is some confusion/disagreement about what it is having an implementat=
ion<br>at this stage signals.<br><br>One way to break up the work of the IE=
TF is:<br>
<br>Engineering--making decisions about the trade-offs related to<br>=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 different approaches to solving a problem.<b=
r><br>Specification--producing text that describes how to inter-operate wit=
h others.<br><br>Standardization--describing the applicability of a specifi=
cation or<br>
=A0=A0=A0 =A0=A0=A0=A0 its suitability as the basis of other work<br><br>(S=
ince we reflect all of these in the same document production, it&#39;s<br>r=
eally muddier than this, but bear with me)<br><br>My experience is that peo=
ple implementing during the working group<br>
discussion phase generate really useful data about the engineering;<br>they=
 can tell you the real impact of different trade-offs, so that<br>this isn&=
#39;t based on general experience.=A0 But it&#39;s not such a great<br>sign=
al about the specification itself, since the spec is designed to<br>
be usable by folks who were not part of the working group process.<br><br>S=
tephen&#39;s draft says:<br><br>=A0=A0 Note also that this experiment just =
needs an implementation that<br>=A0=A0 makes it possible for the WG chairs =
and responsible AD to verify (to<br>
=A0=A0 the extent they chose) that the implementation matches the draft.<br=
><br>and later:<br><br>=A0=A0 An implementation of the draft (ideally open-=
source) is required<br>=A0=A0 for fast-track last-call.=A0 If there is no i=
mplementation or if the<br>
=A0=A0 implementation is unavailable or does not implement the draft<br>=A0=
=A0 sufficiently closely then the document needs to be returned to the<br>=
=A0=A0 WG.=A0 This only requires one implementation, not two and the WG<br>=
=A0=A0 chairs and responsible AD decide themselves how much validation is<b=
r>
=A0=A0 required for this.<br><br>Given the &quot;sufficiently closely&quot;=
 and the timing of production, I<br>assume that the signal we&#39;re lookin=
g for here is confirmation of the<br>engineering choices.=A0 I think that&#=
39;s fine (though I&#39;m not sure this<br>
needs formal experiment status).=A0 But I believe we need to be really<br>c=
areful that it isn&#39;t mistaken for signal about the specification&#39;s<=
br>quality.=A0 It can happen that a working group has &quot;lore&quot; abou=
t what to<br>
do that gets folded into the implementations done by those<br>participating=
, but which never quite makes it into the spec &quot;because<br>everyone kn=
ows it&quot;.=A0 An implementation written during the working<br>group proc=
ess is potentially subject to this effect.<br>
<br>An interoperating implementation written to the spec by a non-working <=
br>group participant would be great signal about the specification quality,=
 <br>but it=A0 is not likely to be available at the stage of the process th=
is draft <br>
targets.<br><br>Again, not objecting to the experiment; I just want to be c=
lear about<br>what signal we believe we&#39;re getting from the implementat=
ion.<br><br>Just my two cents,<br><br>Ted<br>

--0016e6d375a3046dcc04d01e3944--

From stephen.farrell@cs.tcd.ie  Wed Dec  5 09:58:48 2012
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 4EB5621F8C8D for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 09:58:48 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zmYCH4A9b9fE for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 09:58:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8772121F8720 for <ietf@ietf.org>; Wed,  5 Dec 2012 09:58:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C4BD2BE5B; Wed,  5 Dec 2012 17:58:24 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfdlOe9Vqchx; Wed,  5 Dec 2012 17:58:23 +0000 (GMT)
Received: from [IPv6:2001:770:10:203:8fe:f2f3:f980:9bca] (unknown [IPv6:2001:770:10:203:8fe:f2f3:f980:9bca]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id EA6B7BE5A; Wed,  5 Dec 2012 17:58:23 +0000 (GMT)
Message-ID: <50BF8B41.20609@cs.tcd.ie>
Date: Wed, 05 Dec 2012 17:58:25 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: draft-farrell-ft-01.txt -- what signal are we attempting to sense?
References: <CA+9kkMAGqeOzFHeGmmK6TvGctwO-heVrW5xoBseZ528goXJyOA@mail.gmail.com>
In-Reply-To: <CA+9kkMAGqeOzFHeGmmK6TvGctwO-heVrW5xoBseZ528goXJyOA@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 05 Dec 2012 17:58:48 -0000

Hi Ted,

On 12/05/2012 05:22 PM, Ted Hardie wrote:
> Reading through Stephen's draft and the discussion to date, I think there
> is some confusion/disagreement about what it is having an implementation
> at this stage signals.
> 
> One way to break up the work of the IETF is:
> 
> Engineering--making decisions about the trade-offs related to
>              different approaches to solving a problem.
> 
> Specification--producing text that describes how to inter-operate with
> others.
> 
> Standardization--describing the applicability of a specification or
>          its suitability as the basis of other work
> 
> (Since we reflect all of these in the same document production, it's
> really muddier than this, but bear with me)
> 
> My experience is that people implementing during the working group
> discussion phase generate really useful data about the engineering;
> they can tell you the real impact of different trade-offs, so that
> this isn't based on general experience.  But it's not such a great
> signal about the specification itself, since the spec is designed to
> be usable by folks who were not part of the working group process.

Good point.

> Stephen's draft says:
> 
>    Note also that this experiment just needs an implementation that
>    makes it possible for the WG chairs and responsible AD to verify (to
>    the extent they chose) that the implementation matches the draft.
> 
> and later:
> 
>    An implementation of the draft (ideally open-source) is required
>    for fast-track last-call.  If there is no implementation or if the
>    implementation is unavailable or does not implement the draft
>    sufficiently closely then the document needs to be returned to the
>    WG.  This only requires one implementation, not two and the WG
>    chairs and responsible AD decide themselves how much validation is
>    required for this.
> 
> Given the "sufficiently closely" and the timing of production, I
> assume that the signal we're looking for here is confirmation of the
> engineering choices.  I think that's fine (though I'm not sure this
> needs formal experiment status).  

I hadn't thought about this in terms of signals, but its an
interesting way to look at it.

BTW, others have also said (and I agree) that lots of the things
suggested in the draft don't need to be a formal experiment,
but I think doing it that way has merit in any case.

> But I believe we need to be really
> careful that it isn't mistaken for signal about the specification's
> quality.  It can happen that a working group has "lore" about what to
> do that gets folded into the implementations done by those
> participating, but which never quite makes it into the spec "because
> everyone knows it".  An implementation written during the working
> group process is potentially subject to this effect.
> 
> An interoperating implementation written to the spec by a non-working
> group participant would be great signal about the specification quality,
> but it  is not likely to be available at the stage of the process this
> draft
> targets.

That's very true.

I guess I'd be a bit reluctant to try to add text to the
draft about this though, since it might be a bit of a rathole
to try discuss generic good/bad aspects of implementations
and specs. I could see that discussion running and running
and getting nowhere;-)

But maybe it'd be a good idea to maintain a wiki as the
experiment runs where such things could be captured that
could feed into later evaluation of how things went.

If that sounds useful, I'm willing to start that (maybe
once the draft's gotten past IETF LC) and add a bit of text
to the draft pointing at the wiki page. I'm also happy to
do some maintenance on that as things progress, if they do.

If you think some other changes would help instead or
as well, I'll gladly take text of course, or suggestions
for how to (re-)structure the text.

Cheers,
S.

> Again, not objecting to the experiment; I just want to be clear about
> what signal we believe we're getting from the implementation.
> 
> Just my two cents,
> 
> Ted
> 

From ted.ietf@gmail.com  Wed Dec  5 11:36:39 2012
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 5C43A21F860F for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 11:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.377
X-Spam-Level: 
X-Spam-Status: No, score=-3.377 tagged_above=-999 required=5 tests=[AWL=0.221,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0VJOtHtfNLpC for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 11:36:38 -0800 (PST)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id B86FF21F842E for <ietf@ietf.org>; Wed,  5 Dec 2012 11:36:37 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id i20so2077724qad.10 for <ietf@ietf.org>; Wed, 05 Dec 2012 11:36:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=g020bXBpSK+v6JxwtmSNELIyKYVfhRZQN4Lxl9d3oqk=; b=Sl82B/gC4P4xpSxTTDLFikAdgYKFqkSJ7CFwx6+0LxwemQWnU3pNYbaiGTKhwtKzFS eLLHR53b34000bIvYBOmOJQ2ReTGAfRfgklyVGN4/UXp7lQpVx/2njl4W/Ljw3pjIWaR 3dVKpxGFTvHfd8SzcqQ6/3OUmBnM5tfGBsWXB0ZfVg20ywrWwMufr1nG23LTI9ufm7hn m9/afWfwaFIcbNpV/4Lonk4RkLMRnJYTPCQ1kEX5SwAVQqOoF2yIcK0s0/YEW+AlqbXZ 0TAqkuUM0/TM0bSK4c5625q/1ViMc7pkQq3APl9tAoeqfIsmYKfBhFXdJtHDDDlr4iym 6tew==
MIME-Version: 1.0
Received: by 10.49.48.113 with SMTP id k17mr3013668qen.51.1354736197269; Wed, 05 Dec 2012 11:36:37 -0800 (PST)
Received: by 10.49.121.100 with HTTP; Wed, 5 Dec 2012 11:36:37 -0800 (PST)
In-Reply-To: <50BF8B41.20609@cs.tcd.ie>
References: <CA+9kkMAGqeOzFHeGmmK6TvGctwO-heVrW5xoBseZ528goXJyOA@mail.gmail.com> <50BF8B41.20609@cs.tcd.ie>
Date: Wed, 5 Dec 2012 11:36:37 -0800
Message-ID: <CA+9kkMABYj9C+yedEigSG8wwcVoa74qyVcs_Tx1nCU0sZaH54Q@mail.gmail.com>
Subject: Re: draft-farrell-ft-01.txt -- what signal are we attempting to sense?
From: Ted Hardie <ted.ietf@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=047d7b6da460cd7ac104d020194c
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, 05 Dec 2012 19:36:39 -0000

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

Hi Stephen,

Some further comments in-line.

On Wed, Dec 5, 2012 at 9:58 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie>wrote:

>
> Hi Ted,
>
> On 12/05/2012 05:22 PM, Ted Hardie wrote:
> > Reading through Stephen's draft and the discussion to date, I think there
> > is some confusion/disagreement about what it is having an implementation
> > at this stage signals.
> >
> > One way to break up the work of the IETF is:
> >
> > Engineering--making decisions about the trade-offs related to
> >              different approaches to solving a problem.
> >
> > Specification--producing text that describes how to inter-operate with
> > others.
> >
> > Standardization--describing the applicability of a specification or
> >          its suitability as the basis of other work
> >
> > (Since we reflect all of these in the same document production, it's
> > really muddier than this, but bear with me)
> >
> > My experience is that people implementing during the working group
> > discussion phase generate really useful data about the engineering;
> > they can tell you the real impact of different trade-offs, so that
> > this isn't based on general experience.  But it's not such a great
> > signal about the specification itself, since the spec is designed to
> > be usable by folks who were not part of the working group process.
>
> Good point.
>
> > Stephen's draft says:
> >
> >    Note also that this experiment just needs an implementation that
> >    makes it possible for the WG chairs and responsible AD to verify (to
> >    the extent they chose) that the implementation matches the draft.
> >
> > and later:
> >
> >    An implementation of the draft (ideally open-source) is required
> >    for fast-track last-call.  If there is no implementation or if the
> >    implementation is unavailable or does not implement the draft
> >    sufficiently closely then the document needs to be returned to the
> >    WG.  This only requires one implementation, not two and the WG
> >    chairs and responsible AD decide themselves how much validation is
> >    required for this.
> >
> > Given the "sufficiently closely" and the timing of production, I
> > assume that the signal we're looking for here is confirmation of the
> > engineering choices.  I think that's fine (though I'm not sure this
> > needs formal experiment status).
>
> I hadn't thought about this in terms of signals, but its an
> interesting way to look at it.
>
> BTW, others have also said (and I agree) that lots of the things
> suggested in the draft don't need to be a formal experiment,
> but I think doing it that way has merit in any case.
>
> > But I believe we need to be really
> > careful that it isn't mistaken for signal about the specification's
> > quality.  It can happen that a working group has "lore" about what to
> > do that gets folded into the implementations done by those
> > participating, but which never quite makes it into the spec "because
> > everyone knows it".  An implementation written during the working
> > group process is potentially subject to this effect.
> >
> > An interoperating implementation written to the spec by a non-working
> > group participant would be great signal about the specification quality,
> > but it  is not likely to be available at the stage of the process this
> > draft
> > targets.
>
> That's very true.
>
> I guess I'd be a bit reluctant to try to add text to the
> draft about this though, since it might be a bit of a rathole
> to try discuss generic good/bad aspects of implementations
> and specs. I could see that discussion running and running
> and getting nowhere;-)
>
>
I don't think it needs to be a rat-hole.  Let me suggest the following
text:

OLD:

   Sometimes, it can take a long time to get a Proposed Standard
   produced in the IETF.  This memo proposes an optional way to speed up
   the parts of the process that happen after a WG has done its job by
   building a "reward" for having an implementation (ideally open-
   source) available into IETF processes.


NEW:

Implementations developed during the production of an Internet-draft
can indicate that a working group has had the opportunity to get
early confirmation of its engineering choices.  This memo proposes
an optional way to parallel process some final stage reviews when
the working group management and area directors believe that the
implementation can itself serve as a practical review of the engineering
choices.

Does that make sense?



> But maybe it'd be a good idea to maintain a wiki as the
> experiment runs where such things could be captured that
> could feed into later evaluation of how things went.
>
> If that sounds useful, I'm willing to start that (maybe
> once the draft's gotten past IETF LC) and add a bit of text
> to the draft pointing at the wiki page. I'm also happy to
> do some maintenance on that as things progress, if they do.
>
> If you think some other changes would help instead or
> as well, I'll gladly take text of course, or suggestions
> for how to (re-)structure the text.
>
>
I think it might generally useful to talk about this in terms of
parallel processing review, rather than issuing a reward, but
that may be simply a a style preference.

regards,

Ted Hardie


> Cheers,
> S.
>
> > Again, not objecting to the experiment; I just want to be clear about
> > what signal we believe we're getting from the implementation.
> >
> > Just my two cents,
> >
> > Ted
> >
>

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

Hi Stephen,<br><br>Some further comments in-line.<br><br><div class=3D"gmai=
l_quote">On Wed, Dec 5, 2012 at 9:58 AM, Stephen Farrell <span dir=3D"ltr">=
&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank">stephen.=
farrell@cs.tcd.ie</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
Hi Ted,<br>
<div class=3D"im"><br>
On 12/05/2012 05:22 PM, Ted Hardie wrote:<br>
&gt; Reading through Stephen&#39;s draft and the discussion to date, I thin=
k there<br>
&gt; is some confusion/disagreement about what it is having an implementati=
on<br>
&gt; at this stage signals.<br>
&gt;<br>
&gt; One way to break up the work of the IETF is:<br>
&gt;<br>
&gt; Engineering--making decisions about the trade-offs related to<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0different approaches to solving a problem.<=
br>
&gt;<br>
&gt; Specification--producing text that describes how to inter-operate with=
<br>
&gt; others.<br>
&gt;<br>
&gt; Standardization--describing the applicability of a specification or<br=
>
&gt; =A0 =A0 =A0 =A0 =A0its suitability as the basis of other work<br>
&gt;<br>
&gt; (Since we reflect all of these in the same document production, it&#39=
;s<br>
&gt; really muddier than this, but bear with me)<br>
&gt;<br>
&gt; My experience is that people implementing during the working group<br>
&gt; discussion phase generate really useful data about the engineering;<br=
>
&gt; they can tell you the real impact of different trade-offs, so that<br>
&gt; this isn&#39;t based on general experience. =A0But it&#39;s not such a=
 great<br>
&gt; signal about the specification itself, since the spec is designed to<b=
r>
&gt; be usable by folks who were not part of the working group process.<br>
<br>
</div>Good point.<br>
<div class=3D"im"><br>
&gt; Stephen&#39;s draft says:<br>
&gt;<br>
&gt; =A0 =A0Note also that this experiment just needs an implementation tha=
t<br>
&gt; =A0 =A0makes it possible for the WG chairs and responsible AD to verif=
y (to<br>
&gt; =A0 =A0the extent they chose) that the implementation matches the draf=
t.<br>
&gt;<br>
&gt; and later:<br>
&gt;<br>
&gt; =A0 =A0An implementation of the draft (ideally open-source) is require=
d<br>
&gt; =A0 =A0for fast-track last-call. =A0If there is no implementation or i=
f the<br>
&gt; =A0 =A0implementation is unavailable or does not implement the draft<b=
r>
&gt; =A0 =A0sufficiently closely then the document needs to be returned to =
the<br>
&gt; =A0 =A0WG. =A0This only requires one implementation, not two and the W=
G<br>
&gt; =A0 =A0chairs and responsible AD decide themselves how much validation=
 is<br>
&gt; =A0 =A0required for this.<br>
&gt;<br>
&gt; Given the &quot;sufficiently closely&quot; and the timing of productio=
n, I<br>
&gt; assume that the signal we&#39;re looking for here is confirmation of t=
he<br>
&gt; engineering choices. =A0I think that&#39;s fine (though I&#39;m not su=
re this<br>
&gt; needs formal experiment status).<br>
<br>
</div>I hadn&#39;t thought about this in terms of signals, but its an<br>
interesting way to look at it.<br>
<br>
BTW, others have also said (and I agree) that lots of the things<br>
suggested in the draft don&#39;t need to be a formal experiment,<br>
but I think doing it that way has merit in any case.<br>
<div class=3D"im"><br>
&gt; But I believe we need to be really<br>
&gt; careful that it isn&#39;t mistaken for signal about the specification&=
#39;s<br>
&gt; quality. =A0It can happen that a working group has &quot;lore&quot; ab=
out what to<br>
&gt; do that gets folded into the implementations done by those<br>
&gt; participating, but which never quite makes it into the spec &quot;beca=
use<br>
&gt; everyone knows it&quot;. =A0An implementation written during the worki=
ng<br>
&gt; group process is potentially subject to this effect.<br>
&gt;<br>
&gt; An interoperating implementation written to the spec by a non-working<=
br>
&gt; group participant would be great signal about the specification qualit=
y,<br>
&gt; but it =A0is not likely to be available at the stage of the process th=
is<br>
&gt; draft<br>
&gt; targets.<br>
<br>
</div>That&#39;s very true.<br>
<br>
I guess I&#39;d be a bit reluctant to try to add text to the<br>
draft about this though, since it might be a bit of a rathole<br>
to try discuss generic good/bad aspects of implementations<br>
and specs. I could see that discussion running and running<br>
and getting nowhere;-)<br>
<br></blockquote><div><br>I don&#39;t think it needs to be a rat-hole.=A0 L=
et me suggest the following<br>text:<br><br>OLD:<br><br><pre>   Sometimes, =
it can take a long time to get a Proposed Standard
   produced in the IETF.  This memo proposes an optional way to speed up
   the parts of the process that happen after a WG has done its job by
   building a &quot;reward&quot; for having an implementation (ideally open=
-
   source) available into IETF processes.</pre><br>NEW:<br><br>Implementati=
ons developed during the production of an Internet-draft<br>can indicate th=
at a working group has had the opportunity to get<br>early confirmation of =
its engineering choices.=A0 This memo proposes<br>
an optional way to parallel process some final stage reviews when<br>the wo=
rking group management and area directors believe that the<br>implementatio=
n can itself serve as a practical review of the engineering<br>choices.<br>
<br>Does that make sense?<br><br>=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But maybe it&#39;d be a good idea to maintain a wiki as the<br>
experiment runs where such things could be captured that<br>
could feed into later evaluation of how things went.<br>
<br>
If that sounds useful, I&#39;m willing to start that (maybe<br>
once the draft&#39;s gotten past IETF LC) and add a bit of text<br>
to the draft pointing at the wiki page. I&#39;m also happy to<br>
do some maintenance on that as things progress, if they do.<br>
<br>
If you think some other changes would help instead or<br>
as well, I&#39;ll gladly take text of course, or suggestions<br>
for how to (re-)structure the text.<br>
<br></blockquote><div><br>I think it might generally useful to talk about t=
his in terms of<br>parallel processing review, rather than issuing a reward=
, but<br>that may be simply a a style preference. <br><br>regards,<br>
<br>Ted Hardie<br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
<div class=3D"HOEnZb"><div class=3D"h5">S.<br>
<br>
&gt; Again, not objecting to the experiment; I just want to be clear about<=
br>
&gt; what signal we believe we&#39;re getting from the implementation.<br>
&gt;<br>
&gt; Just my two cents,<br>
&gt;<br>
&gt; Ted<br>
&gt;<br>
</div></div></blockquote></div><br>

--047d7b6da460cd7ac104d020194c--

From stephen.farrell@cs.tcd.ie  Wed Dec  5 13:55:31 2012
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 BFF8F21F8C3E for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 13:55:31 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u9asH4Dn5SWq for <ietf@ietfa.amsl.com>; Wed,  5 Dec 2012 13:55:30 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8A94721F8BBA for <ietf@ietf.org>; Wed,  5 Dec 2012 13:55:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7658FBE33; Wed,  5 Dec 2012 21:55:08 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5wjldnq07-S; Wed,  5 Dec 2012 21:55:07 +0000 (GMT)
Received: from [10.87.48.3] (unknown [86.46.20.46]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 67D04BE25; Wed,  5 Dec 2012 21:55:07 +0000 (GMT)
Message-ID: <50BFC2BB.6090103@cs.tcd.ie>
Date: Wed, 05 Dec 2012 21:55:07 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: draft-farrell-ft-01.txt -- what signal are we attempting to sense?
References: <CA+9kkMAGqeOzFHeGmmK6TvGctwO-heVrW5xoBseZ528goXJyOA@mail.gmail.com> <50BF8B41.20609@cs.tcd.ie> <CA+9kkMABYj9C+yedEigSG8wwcVoa74qyVcs_Tx1nCU0sZaH54Q@mail.gmail.com>
In-Reply-To: <CA+9kkMABYj9C+yedEigSG8wwcVoa74qyVcs_Tx1nCU0sZaH54Q@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 05 Dec 2012 21:55:31 -0000

Hi Ted,

Thanks that change looks good to me. I'll whack it in thanks. I do
still like the word "reward" though so I'll tag that on too:-)

Cheers,
S.


On 12/05/2012 07:36 PM, Ted Hardie wrote:
> Hi Stephen,
> 
> Some further comments in-line.
> 
> On Wed, Dec 5, 2012 at 9:58 AM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie>wrote:
> 
>>
>> Hi Ted,
>>
>> On 12/05/2012 05:22 PM, Ted Hardie wrote:
>>> Reading through Stephen's draft and the discussion to date, I think there
>>> is some confusion/disagreement about what it is having an implementation
>>> at this stage signals.
>>>
>>> One way to break up the work of the IETF is:
>>>
>>> Engineering--making decisions about the trade-offs related to
>>>              different approaches to solving a problem.
>>>
>>> Specification--producing text that describes how to inter-operate with
>>> others.
>>>
>>> Standardization--describing the applicability of a specification or
>>>          its suitability as the basis of other work
>>>
>>> (Since we reflect all of these in the same document production, it's
>>> really muddier than this, but bear with me)
>>>
>>> My experience is that people implementing during the working group
>>> discussion phase generate really useful data about the engineering;
>>> they can tell you the real impact of different trade-offs, so that
>>> this isn't based on general experience.  But it's not such a great
>>> signal about the specification itself, since the spec is designed to
>>> be usable by folks who were not part of the working group process.
>>
>> Good point.
>>
>>> Stephen's draft says:
>>>
>>>    Note also that this experiment just needs an implementation that
>>>    makes it possible for the WG chairs and responsible AD to verify (to
>>>    the extent they chose) that the implementation matches the draft.
>>>
>>> and later:
>>>
>>>    An implementation of the draft (ideally open-source) is required
>>>    for fast-track last-call.  If there is no implementation or if the
>>>    implementation is unavailable or does not implement the draft
>>>    sufficiently closely then the document needs to be returned to the
>>>    WG.  This only requires one implementation, not two and the WG
>>>    chairs and responsible AD decide themselves how much validation is
>>>    required for this.
>>>
>>> Given the "sufficiently closely" and the timing of production, I
>>> assume that the signal we're looking for here is confirmation of the
>>> engineering choices.  I think that's fine (though I'm not sure this
>>> needs formal experiment status).
>>
>> I hadn't thought about this in terms of signals, but its an
>> interesting way to look at it.
>>
>> BTW, others have also said (and I agree) that lots of the things
>> suggested in the draft don't need to be a formal experiment,
>> but I think doing it that way has merit in any case.
>>
>>> But I believe we need to be really
>>> careful that it isn't mistaken for signal about the specification's
>>> quality.  It can happen that a working group has "lore" about what to
>>> do that gets folded into the implementations done by those
>>> participating, but which never quite makes it into the spec "because
>>> everyone knows it".  An implementation written during the working
>>> group process is potentially subject to this effect.
>>>
>>> An interoperating implementation written to the spec by a non-working
>>> group participant would be great signal about the specification quality,
>>> but it  is not likely to be available at the stage of the process this
>>> draft
>>> targets.
>>
>> That's very true.
>>
>> I guess I'd be a bit reluctant to try to add text to the
>> draft about this though, since it might be a bit of a rathole
>> to try discuss generic good/bad aspects of implementations
>> and specs. I could see that discussion running and running
>> and getting nowhere;-)
>>
>>
> I don't think it needs to be a rat-hole.  Let me suggest the following
> text:
> 
> OLD:
> 
>    Sometimes, it can take a long time to get a Proposed Standard
>    produced in the IETF.  This memo proposes an optional way to speed up
>    the parts of the process that happen after a WG has done its job by
>    building a "reward" for having an implementation (ideally open-
>    source) available into IETF processes.
> 
> 
> NEW:
> 
> Implementations developed during the production of an Internet-draft
> can indicate that a working group has had the opportunity to get
> early confirmation of its engineering choices.  This memo proposes
> an optional way to parallel process some final stage reviews when
> the working group management and area directors believe that the
> implementation can itself serve as a practical review of the engineering
> choices.
> 
> Does that make sense?
> 
> 
> 
>> But maybe it'd be a good idea to maintain a wiki as the
>> experiment runs where such things could be captured that
>> could feed into later evaluation of how things went.
>>
>> If that sounds useful, I'm willing to start that (maybe
>> once the draft's gotten past IETF LC) and add a bit of text
>> to the draft pointing at the wiki page. I'm also happy to
>> do some maintenance on that as things progress, if they do.
>>
>> If you think some other changes would help instead or
>> as well, I'll gladly take text of course, or suggestions
>> for how to (re-)structure the text.
>>
>>
> I think it might generally useful to talk about this in terms of
> parallel processing review, rather than issuing a reward, but
> that may be simply a a style preference.
> 
> regards,
> 
> Ted Hardie
> 
> 
>> Cheers,
>> S.
>>
>>> Again, not objecting to the experiment; I just want to be clear about
>>> what signal we believe we're getting from the implementation.
>>>
>>> Just my two cents,
>>>
>>> Ted
>>>
>>
> 

From ben@nostrum.com  Wed Dec  5 14:14:53 2012
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 1FA8F21F8CE8; Wed,  5 Dec 2012 14:14:53 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wa-M41qwQ44h; Wed,  5 Dec 2012 14:14:52 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFF421F8CE2; Wed,  5 Dec 2012 14:14:52 -0800 (PST)
Received: from [172.20.10.2] (mobile-166-137-149-189.mycingular.net [166.137.149.189]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qB5MEinA082069 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Dec 2012 16:14:44 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [Gen-art] Gen-ART LC Review of	draft-ietf-karp-routing-tcp-analysis-05.txt
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <7B7C06EA-E5EB-4FD6-ADE6-1A8E38B11405@gmail.com>
Date: Wed, 5 Dec 2012 16:14:38 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <F2278C98-4C60-4D94-910D-D1E2607936B5@nostrum.com>
References: <18E6B18A-D465-47C6-9E06-886DFBFA1F67@nostrum.com> <F53DCC9A-8AA1-42D4-BF19-88ABCCCA68A7@gmail.com> <3B3FEC40-3D96-4F77-A628-E80DFAEB2278@nostrum.com> <F60EDDFC-0612-4636-AFC7-3D7FD9052D74@gmail.com> <7B7C06EA-E5EB-4FD6-ADE6-1A8E38B11405@gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 166.137.149.189 is authenticated by a trusted mechanism)
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <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, 05 Dec 2012 22:14:53 -0000

Hi Mahesh,

The proposed changes work for me.

Thanks!

Ben.

On Nov 30, 2012, at 11:03 AM, Mahesh Jethanandani =
<mjethanandani@gmail.com> wrote:

> Ben,
>=20
> See inline. If you are ok with these changes, I will go ahead and =
submit an updated version of the draft.
>=20
> On Nov 25, 2012, at 5:56 PM, Mahesh Jethanandani wrote:
>=20
>> Further trimming it to sections that require a response.
>>=20
>> On Nov 21, 2012, at 3:12 PM, Ben Campbell wrote:
>>=20
>>>=20
>>>>>=20
>>>>> *** Minor issues *** :
>>>>>=20
>>>>> -- section 2.2, last paragraph:
>>>>>=20
>>>>> The IKE mention lacks context. Do you mean to suggest IKE with =
IPSec? I assume so, but there's been no mention of IPSec so far.
>>>>=20
>>>> No. It implies the use of IKEv2 protocol for performing mutual =
authentication and establishing SA. There is no suggestion of using IKE =
with IPSec.
>>>>=20
>>>> How about this?
>>>>=20
>>>> For point-to-point key management IKEv2[RFC5996] protocol provides =
...
>>>=20
>>> 5996 describes IKEv2 as a component of IPSec, and a key-management =
mechanism for ESP and AH SAs. Now, I won't claim to be an IKE expert by =
any extent, but I think that if you mean to use IKE _without_ IPSec it =
would be good to add a sentence or two pointing that out. Or is there =
some other reference that could be used that describes using IKEv2 for =
non-IPSec SAs?
>>=20
>> Added this sentence.
>>=20
>> Although IKEv2 is discussed as a component of IPsec, KMP can use just =
the mutual authentication and SA establishment portion of IKEv2.
>=20
> This statement has been further modified to:
>=20
> For point-to-point key management IKEv2 [RFC5996] provides for
>  automated key exchange under a SA and can be used for a comprehensive
>  Key Management Protocol (KMP) solution for routers.  IKEv2 can be =
used
>  for both IPsec SAs [RFC4301] and other types of SAs. For example,=20
>  Fibre Channel SAs  [RFC4595] are currently negotiated with IKEv2. =
Using
>  IKEv2 to negotiate TCP-AO is a possible option.
>=20
>=20
>>=20
>>>=20
>>>>=20
>>>>>=20
>>>>> *** Nits/editorial comments ***:
>>>>>=20
>>>>> -- IDNits indicates some unused and obsoleted references. Please =
check.
>>>>=20
>>>> Found one unused reference and have removed it.
>>>=20
>>> Seems like there were more than one. =46rom IDNits:
>>>=20
>>>  =3D=3D Missing Reference: 'IRR' is mentioned on line 92, but not =
defined
>>>=20
>>>  =3D=3D Unused Reference: 'RFC2409' is defined on line 585, but no =
explicit
>>>     reference was found in the text
>>>=20
>>>  =3D=3D Unused Reference: 'RFC3547' is defined on line 588, but no =
explicit
>>>     reference was found in the text
>>>=20
>>>  ** Obsolete normative reference: RFC 2385 (Obsoleted by RFC 5925)
>>>=20
>>>  -- Obsolete informational reference (is this intentional?): RFC =
2409
>>>     (Obsoleted by RFC 4306)
>>>=20
>>>  -- Obsolete informational reference (is this intentional?): RFC =
3547
>>>     (Obsoleted by RFC 6407)
>>=20
>> I have removed these unused references.
>>=20
>>>=20
>>>>>=20
>>>>> -- section 4, 2nd paragraph: "In addition Improving TCP=92s =
Robustness to Blind In-Window Attacks."
>>>>>=20
>>>>> sentence fragment.
>>>>=20
>>>> Changed it to say:
>>>>=20
>>>> In addition, the recommendations in Improving TCP's Robustness to =
Blind In-Window Attacks
>>>>=20
>>>=20
>>> Am I correct in assuming this merges with the following sentence? =
Otherwise, it's still a fragment.
>>>=20
>>=20
>> Changed it to:
>>=20
>> In addition, the recommendations in RFC 5961 should also be followed =
...
>=20
> Mahesh Jethanandani
> mjethanandani@gmail.com
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From magnus.westerlund@ericsson.com  Thu Dec  6 02:01:22 2012
Return-Path: <magnus.westerlund@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 198D721F868A; Thu,  6 Dec 2012 02:01:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level: 
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOXqU+jzL4+K; Thu,  6 Dec 2012 02:01:21 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id BA68F21F8562; Thu,  6 Dec 2012 02:01:13 -0800 (PST)
X-AuditID: c1b4fb2d-b7f1e6d000002d2c-a7-50c06ce779c0
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 86.E3.11564.7EC60C05; Thu,  6 Dec 2012 11:01:11 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0247.eemea.ericsson.se (153.88.115.94) with Microsoft SMTP Server id 8.3.279.1; Thu, 6 Dec 2012 11:01:11 +0100
Message-ID: <50C06CE6.40909@ericsson.com>
Date: Thu, 6 Dec 2012 11:01:10 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-tcpm-initcwnd-06.txt> (Increasing TCP's Initial Window) to Experimental RFC
References: <20121126212940.20378.58186.idtracker@ietfa.amsl.com>
In-Reply-To: <20121126212940.20378.58186.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmluLIzCtJLcpLzFFi42KZGfG3Rvd5zoEAg9X79C2ebZzPYrHt5Hwm ByaPJUt+MgUwRnHZpKTmZJalFunbJXBlLL43h7Hgql7F182vGRsYb6p2MXJySAiYSMxrec0I YYtJXLi3nq2LkYtDSOAko8T99d9YIJxljBKf1q0Ccjg4eAU0JRZ/1QBpYBFQkZhzZioziM0m YCFx80cjG4gtKuArMWvPLyYQm1dAUOLkzCcsILaIgLDEkUf/2EFsZiB70eleVhBbWKBQ4k7j WrB6IQFHiQ0PXoLN5BRwkti8dTkrxHGSEoumdbJA9OpJTLnawghhy0s0b53NDNGrLdHQ1ME6 gVFoFpLVs5C0zELSsoCReRUje25iZk56ueEmRmCAHtzyW3cH46lzIocYpTlYlMR5uZL2+wsJ pCeWpGanphakFsUXleakFh9iZOLglGpgdOJ5NfXr1v3Lm2u/xCvOPC327Q3fpXfVs13WHVfO 3dxWO7v62NOk/5LR4ieN/m7+tvPH6+7K7p933FkkPp6bcuZ3VtlzT+/DwQEZF0tXSXll3zVf /Vjj0OfPVw4earxWcErNcZb/zl9fJ9yVOMxg/7bMJCb71iED9x8bLLO2FK+zTp1wg8Eru1KJ pTgj0VCLuag4EQDwIOhHHgIAAA==
Cc: tcpm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 10:01:22 -0000

Hi,

I have reviewed draft-ietf-tcpm-initcwnd-06 and have some questions and
comments.

1) First of all the experiments done appear to cover the impact on other
applications, like measuring the RTT variations when using IW10 compared
to IW3. If one is interested in the impact this proposal have on
real-time traffic flows over a shared bottle-neck the variations in
queue time at the bottleneck combined with that flows seen loss rates
are the most important factors. As a sudden delay spike of sufficient
magnitude will most likely result in a real-time media packet being
late, i.e. late loss rather than being lost in the network there might
be significant impact on such traffic from these IW10 packet bursts.
Have I missed any material discussing this aspect?

All the latency figures in the parts I was looking at was discussing
cases when the object transfer takes longer time. But it appear obvious
that even with a 100 ms increased one-way transfer time for a packet is
the end of the initial window the total transfer goes faster compared to
the delay caused by growing the window.

2) If I assume that most users are behind buffer-bloated links the
introduction of IW10 on wide scale will additionally disrupt interactive
applications and cause increased delay and possible late loss depending
on application. Especially in combination with domain sharding. For
example a Swedish newspaper's website front page results in that more
than 40 TCP connections are opened in a current browser. If these all
was using IW10, the amount of packets being sent initially will grow
roughly from 40*3 = 120 to 40*10 = 400. There are some distribution over
time but still this likely results in a larger delay spike.

I don't quite know how I should consider this case. One stand point is
that the interactive application is anyway buggered and IW10 effects are
not making it significantly worse. The only remedy is queue separation
so that what ever happens with the web-downloads doesn't affect the
interactive traffic. Another is that it will make the existing situation
worse and we should try to avoid making it worse.

I think I am more in the first camp, but still the second one is
worrying to me. But I dare to guess that the performance gains might be
worth the issues, but without real progress on mitigation of the buffer
bloat issues for interactive real-time traffic this will add
significantly to the issues real-time has to face.


3) The documents talks in quite loose terms about what can be done to
avoid to continue cause issues for destinations which has issues with
IW10. However I think it is a bit unspecific here. I can see that a
content deliverer can have lists for destination address blocks that
they see issues with which configures the sending server side with a
lower IW value. It also talks about the clients can configure to keep
the window low initially to prevent an IW10 sender to clobber ones link
if that is known. My question here is if the recommendation for auto
detection and configuration can be made more explicit. Fortunately the
issues with misconfiguration in this cases is not that serious. But
otherwise there is commonly need to be quite careful with such auto
configs that affects the behavior.

4) I am also worried that the document is a bit to positive in regards
to that IW10 will reduce the domain sharding practice. I think the only
thing that can do is likely a new HTTP transport strata that shows that
significantly improved performance for multiple objects from the same
domain over fewer transport flows. Maybe SPDY + IW10 can provide such
incentive, but I don't think IW10 alone will do much.

Cheers

Magnus

On 2012-11-26 22:29, The IESG wrote:
> 
> The IESG has received a request from the TCP Maintenance and Minor
> Extensions WG (tcpm) to consider the following document:
> - 'Increasing TCP's Initial Window'
>   <draft-ietf-tcpm-initcwnd-06.txt> as Experimental 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 2012-12-10. 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 proposes an experiment to increase the permitted TCP
>    initial window (IW) from between 2 and 4 segments, as specified in
>    RFC 3390, to 10 segments, with a fallback to the existing
>    recommendation when performance issues are detected. It discusses the
>    motivation behind the increase, the advantages and disadvantages of
>    the higher initial window, and presents results from several large
>    scale experiments showing that the higher initial window improves the
>    overall performance of many web services without resulting in a
>    congestion collapse. The document closes with a discussion of usage
>    and deployment for further experimental purpose recommended by the
>    IETF TCP Maintenance and Minor Extensions (TCPM) working group.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-tcpm-initcwnd/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-tcpm-initcwnd/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From dave.cridland@isode.com  Thu Dec  6 04:36:09 2012
Return-Path: <dave.cridland@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9266021F8726 for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 04:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w2YEiA0iP7W2 for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 04:36:09 -0800 (PST)
Received: from statler.isode.com (statler.isode.com [62.3.217.254]) by ietfa.amsl.com (Postfix) with ESMTP id C926621F86AA for <ietf@ietf.org>; Thu,  6 Dec 2012 04:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1354797367; d=isode.com; s=selector; i=@isode.com; bh=SCqSUuabTQlBTBN9atTjOdZEtqDUZP2Dwylg72t2mFg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=sd+yB4cnD6NLVpy2lA0rz1MTEebmxjOFQlG1Iwzdx2WByvfe1XUXtz6tr6ZqXgKLCLiKWq 6obfVXGwFlGGHxVo/k7Sro9/Jb5dHYCvqP6RwYINTU9rbvb1X0600f7aWCSbvApO0JSxCg BaOxRYKAPhZokrhFDYSdYdGK9hfugug=;
Received: from puncture (br.cridland.net [217.155.137.62])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <UMCRNwBEKGTM@statler.isode.com>; Thu, 6 Dec 2012 12:36:07 +0000
X-SMTP-Protocol-Errors: PIPELINING
Subject: RE: A mailing list protocol
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
Message-Id: <7256.1354797367.419104@puncture>
Date: Thu, 06 Dec 2012 12:36:07 +0000
From: Dave Cridland <dave.cridland@isode.com>
To: "George\, Wes" <wesley.george@twcable.com>, IETF-Discussion <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-Mailman-Approved-At: Thu, 06 Dec 2012 09:24:58 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 12:36:09 -0000

On Tue Dec  4 22:19:14 2012, George, Wes wrote:
> Is there an IETF standard format for handling inline quote replies?  
> Is it just not implemented in certain mail clients? 

RFC 3676? (As used here).

It is admittedly primarily useful in simple replies rather than  
quoting (and therefore attribution) from multiple parent messages;  
however that's by far the common case. A further specifcation to  
annotate attribution would be possible, though in principle that  
would be usefully based on the References field.

> Browbeating people into changing mail clients will be less than  
> effective, but something that systematically makes it easier to see  
> who is responsible for what comment in a multi-person thread  
> regardless of source email client would be welcome. While we're at  
> it, we could maybe implement a fix for the common problem of  
> mangled subject lines that make it very difficult to sort by  
> thread, and add a server-side filter that removes the legal  
> bilgewater automatically added to some outgoing messages (example  
> will follow in this very message) before sending it to the rest of  
> the list recipients, etc.

I've not really had a problem with searching for the subject root, in  
general, but I'd be happy to agree despite inexperience with the  
issue that there are standards for reply-mangling of subjects and we  
should note that.

My more common problem is a lack of in-reply-to or references fields  
that I can use for in-thread navigation, which I find particularly  
useful.

In general, there are a number of technical standards and protocols  
which are useful, or essential, for IETF participation; documenting  
these in a single location would seem beneficial.

Dave.

From vesely@tana.it  Thu Dec  6 10:03:36 2012
Return-Path: <vesely@tana.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 01A2521F87F6 for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 10:03:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTlorwKUIq5y for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 10:03:35 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 4983B21F87F2 for <ietf@ietf.org>; Thu,  6 Dec 2012 10:03:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1354817013; bh=SdnPkKvhCQxzOPTCykayD5mPrGuJRRcilIlv6Y7oRbU=; l=383; h=Date:From:To:References:In-Reply-To; b=u+fE95os5R3JVossDRpcjZiBhKdfYk4JMWlstNqd9Oa78zRPrIbRMoPTMAyAzmtWp 1b4PeqhslWmgzzLoARYUk/QcWZkhuD/n53M4Myq0fvl/7MfaeqaYhdoJUW6GAzNLoD bmdpjbCW1JmGrLjoaW88MOezQhVsBq0+a14RtdK0=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Thu, 06 Dec 2012 19:03:33 +0100 id 00000000005DC031.0000000050C0DDF5.00006EF7
Message-ID: <50C0DDF5.2020006@tana.it>
Date: Thu, 06 Dec 2012 19:03:33 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A mailing list protocol
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <7256.1354797367.419104@puncture>
In-Reply-To: <7256.1354797367.419104@puncture>
Content-Type: text/plain; charset=us-ascii
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, 06 Dec 2012 18:03:36 -0000

On Thu 06/Dec/2012 13:36:07 +0100 Dave Cridland wrote:
> 
> In general, there are a number of technical standards and protocols
> which are useful, or essential, for IETF participation; documenting
> these in a single location would seem beneficial.

Don't forget the confidentiality notices conundrum, see e.g.
http://www.ietf.org/mail-archive/web/ietf/current/msg67495.html


From johnl@iecc.com  Thu Dec  6 13:24:29 2012
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 96B2221F85D6 for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 13:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.217
X-Spam-Level: 
X-Spam-Status: No, score=-106.217 tagged_above=-999 required=5 tests=[AWL=0.682, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4upCHd+9tcTk for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 13:24:27 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AFD9321F85E7 for <ietf@ietf.org>; Thu,  6 Dec 2012 13:24:26 -0800 (PST)
Received: (qmail 50890 invoked from network); 6 Dec 2012 21:24:22 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 6 Dec 2012 21:24:22 -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:vbr-info; s=50c10d06.xn--btvx9d.k1211; i=johnl@user.iecc.com; bh=Ca7zdbW7R2ToqPRL+PEuBXFfOXvV6FvvDZx4Bxe9NgY=; b=SfpIjjWcR3c2vriT9JOm44PCD+N6/mfv+PqGQGjrkDNLOszTgFP+7hHj4blwNhxzv1oATwo5o+GCH5dCsDvtB97Vdj/xxo+9JbfxUwTUIi5fGgolRPWR53p0+MYWz6incZnRtKI0qtYtJlpZe0BCWmHsm7IYn0vwmoF9c/ydNa4=
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:vbr-info; s=50c10d06.xn--btvx9d.k1211; olt=johnl@user.iecc.com; bh=Ca7zdbW7R2ToqPRL+PEuBXFfOXvV6FvvDZx4Bxe9NgY=; b=TOtmUrrfDP/5VEdDAjViOqYW1Dk+rXN1epNs7hAGDRQexcaSOOy6vBPuUJedqkMboCaR/W6zvi+qZHUOyp4uOoSdcpYdMLY7ddYYnDHXAbKhNFRxkn7T16XC7Fh5iT6EUBNrPrJNneBnp29RjK9+snBzAYPoCz0BCtxRFSxFuSA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 6 Dec 2012 21:24:00 -0000
Message-ID: <20121206212400.10366.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: A mailing list protocol
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
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, 06 Dec 2012 21:24:29 -0000

>Is there an IETF standard format for handling inline quote replies?

It's defined in the same RFC that specifies the setting of the
Reply-To: header in mailing lists.


From narten@us.ibm.com  Thu Dec  6 21:53:11 2012
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 2C08521F8816 for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 21:53:11 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5MhewG5O8xxV for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 21:53:10 -0800 (PST)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id 5543121F8801 for <ietf@ietf.org>; Thu,  6 Dec 2012 21:53:10 -0800 (PST)
Received: from /spool/local by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 6 Dec 2012 22:53:09 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 6 Dec 2012 22:53:07 -0700
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 748E219D8042 for <ietf@ietf.org>; Thu,  6 Dec 2012 22:53:07 -0700 (MST)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qB75r7Om379554 for <ietf@ietf.org>; Thu, 6 Dec 2012 22:53:07 -0700
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qB75r6A1011102 for <ietf@ietf.org>; Thu, 6 Dec 2012 22:53:06 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qB75r5ra011031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 6 Dec 2012 22:53:05 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qB75r4oL010395 for <ietf@ietf.org>; Fri, 7 Dec 2012 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qB75r47P010350 for ietf@ietf.org; Fri, 7 Dec 2012 00:53:04 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201212070553.qB75r47P010350@rotala.raleigh.ibm.com>
Date: Fri, 07 Dec 2012 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12120705-7282-0000-0000-00000FD2654E
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 05:53:11 -0000

Total of 215 messages in the last 7 days.
 
script run at: Fri Dec  7 00:53:03 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.23% |   22 | 10.49% |   165129 | stephen.farrell@cs.tcd.ie
  8.37% |   18 |  9.22% |   145124 | moore@network-heretics.com
  6.98% |   15 |  6.18% |    97223 | dhc@dcrocker.net
  6.05% |   13 |  5.34% |    84038 | melinda.shore@gmail.com
  4.19% |    9 |  4.07% |    63986 | sm@resistor.net
  4.19% |    9 |  4.05% |    63701 | barryleiba@computer.org
  3.72% |    8 |  3.39% |    53326 | john-ietf@jck.com
  3.26% |    7 |  3.23% |    50885 | joelja@bogus.com
  3.26% |    7 |  3.21% |    50444 | brian.e.carpenter@gmail.com
  2.79% |    6 |  3.31% |    52081 | abdussalambaryun@gmail.com
  3.26% |    7 |  2.39% |    37589 | randy@psg.com
  2.79% |    6 |  2.40% |    37817 | arturo.servin@gmail.com
  2.33% |    5 |  2.52% |    39591 | wesley.george@twcable.com
  0.93% |    2 |  2.67% |    42008 | adrian@olddog.co.uk
  1.86% |    4 |  1.65% |    25890 | hannes.tschofenig@nsn.com
  1.40% |    3 |  1.50% |    23572 | jari.arkko@piuha.net
  1.40% |    3 |  1.38% |    21751 | randy@qti.qualcomm.com
  0.93% |    2 |  1.84% |    28912 | ted.ietf@gmail.com
  1.40% |    3 |  1.24% |    19571 | elwynd@dial.pipex.com
  0.93% |    2 |  1.61% |    25360 | agmalis@gmail.com
  0.93% |    2 |  1.44% |    22644 | magnus.westerlund@ericsson.com
  1.40% |    3 |  0.97% |    15258 | wjhns1@hardakers.net
  0.93% |    2 |  1.10% |    17355 | jmh@joelhalpern.com
  0.93% |    2 |  1.06% |    16637 | tjc@ecs.soton.ac.uk
  0.93% |    2 |  0.99% |    15583 | fred@cisco.com
  0.93% |    2 |  0.96% |    15115 | hsantos@isdg.net
  0.93% |    2 |  0.90% |    14204 | smb@cs.columbia.edu
  0.93% |    2 |  0.86% |    13558 | petithug@acm.org
  0.93% |    2 |  0.81% |    12759 | sm+ietf@elandsys.com
  0.93% |    2 |  0.80% |    12623 | ynir@checkpoint.com
  0.93% |    2 |  0.79% |    12409 | duerst@it.aoyama.ac.jp
  0.93% |    2 |  0.74% |    11719 | pars.mutaf@gmail.com
  0.93% |    2 |  0.74% |    11585 | loa@pi.nu
  0.93% |    2 |  0.72% |    11321 | johnl@taugh.com
  0.93% |    2 |  0.70% |    11081 | hannes.tschofenig@gmx.net
  0.93% |    2 |  0.70% |    11057 | hartmans-ietf@mit.edu
  0.47% |    1 |  1.02% |    16100 | mjethanandani@gmail.com
  0.47% |    1 |  0.90% |    14229 | david.black@emc.com
  0.47% |    1 |  0.66% |    10344 | tony@att.com
  0.47% |    1 |  0.60% |     9448 | narten@us.ibm.com
  0.47% |    1 |  0.56% |     8754 | ben@nostrum.com
  0.47% |    1 |  0.55% |     8717 | rbonica@juniper.net
  0.47% |    1 |  0.46% |     7287 | gih@apnic.net
  0.47% |    1 |  0.46% |     7168 | stbryant@cisco.com
  0.47% |    1 |  0.43% |     6819 | dave.cridland@isode.com
  0.47% |    1 |  0.43% |     6761 | danny@tcb.net
  0.47% |    1 |  0.43% |     6754 | bob.hinden@gmail.com
  0.47% |    1 |  0.41% |     6510 | chuck.lever@oracle.com
  0.47% |    1 |  0.41% |     6475 | lee@asgard.org
  0.47% |    1 |  0.40% |     6355 | dcrocker@bbiw.net
  0.47% |    1 |  0.40% |     6307 | housley@vigilsec.com
  0.47% |    1 |  0.40% |     6293 | suresh.krishnan@ericsson.com
  0.47% |    1 |  0.39% |     6191 | marc.blanchet@viagenie.ca
  0.47% |    1 |  0.39% |     6102 | bertietf@bwijnen.net
  0.47% |    1 |  0.39% |     6071 | aservin@lacnic.net
  0.47% |    1 |  0.38% |     6056 | nomcom-chair@ietf.org
  0.47% |    1 |  0.38% |     6054 | cabo@tzi.org
  0.47% |    1 |  0.38% |     5984 | d3e3e3@gmail.com
  0.47% |    1 |  0.38% |     5917 | fernando@gont.com.ar
  0.47% |    1 |  0.38% |     5902 | martin.thomson@gmail.com
  0.47% |    1 |  0.37% |     5849 | julian.reschke@gmx.de
  0.47% |    1 |  0.36% |     5588 | swb@internet2.edu
  0.47% |    1 |  0.35% |     5535 | rbarnes@bbn.com
  0.47% |    1 |  0.34% |     5356 | dwm@xpasc.com
  0.47% |    1 |  0.34% |     5335 | vesely@tana.it
  0.47% |    1 |  0.34% |     5317 | dougb@dougbarton.us
  0.47% |    1 |  0.34% |     5274 | peter@akayla.com
--------+------+--------+----------+------------------------
100.00% |  215 |100.00% |  1573758 | Total


From pars.mutaf@gmail.com  Thu Dec  6 22:09:22 2012
Return-Path: <pars.mutaf@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 AC16921F885A for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 22:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.984
X-Spam-Level: 
X-Spam-Status: No, score=-2.984 tagged_above=-999 required=5 tests=[AWL=-0.468, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, URIBL_RHS_DOB=1.083]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v61VOLUF99B2 for <ietf@ietfa.amsl.com>; Thu,  6 Dec 2012 22:09:21 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7859921F8801 for <ietf@ietf.org>; Thu,  6 Dec 2012 22:09:15 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so142285vbb.31 for <ietf@ietf.org>; Thu, 06 Dec 2012 22:09:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=r3vB0QOVBGZmGYwsVOY/68vlUnDLFrj7x1PiUeWWRHk=; b=IPBvSNe2c9RzdRxYzNvoJMrdmWPBM23VSN0tu2ieW9Fbm+a9D2a+lZ+Rtvw6VkBW3t g+om4QrrJVjOwtu+yzHPRPi+1otburKSGTNuV6DgxPB7E7vYkoSSm3nTXNrHU3oR+Ek0 JOGy64wy7CKvaLYlJhpZYsbzjJy0qJSP6KFldgeRLnLjc0g+b2UunEsIf2W9hRxEKnl3 YL0cDSZp9teUG/LX3ZWIUuzW3fcUYxVf+MEtESgqu+MyPcS5uOXb9TLaAjilmh2PNSIu WBd7qP4P3KPVczqzatq4IH8T6QJWXzN6Cnx/xNlmG5pD3fzAHsTDTEodU+artk2tT9nK 3TAA==
MIME-Version: 1.0
Received: by 10.58.249.201 with SMTP id yw9mr3308419vec.10.1354860554485; Thu, 06 Dec 2012 22:09:14 -0800 (PST)
Received: by 10.59.1.3 with HTTP; Thu, 6 Dec 2012 22:09:14 -0800 (PST)
In-Reply-To: <CACQuieY9PBbWZFyEYF8dUqFB21Mv5zEGEe8NoMbipbEXdxOgmw@mail.gmail.com>
References: <CACQuieY9PBbWZFyEYF8dUqFB21Mv5zEGEe8NoMbipbEXdxOgmw@mail.gmail.com>
Date: Fri, 7 Dec 2012 08:09:14 +0200
Message-ID: <CACQuieasVy62U1aPv_=1Mak6XR9sV7EpGy-wmYrVCn9Dyk7qFg@mail.gmail.com>
Subject: Re: The flower standard
From: Pars Mutaf <pars.mutaf@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=047d7bacc07e11fee104d03d0e97
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Dec 2012 06:09:22 -0000

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

On Tue, Dec 4, 2012 at 11:18 AM, Pars Mutaf <pars.mutaf@gmail.com> wrote:

> Dear all,
>
> FYI, I designed the following standard myself. It completes IETF RFC 3161.
>
> www.flower-standard.org
>
> Cheers,
> Pars Mutaf
>


More info about the design rational. I provide this information here
because someone may ask later why I did not ask the IETF's opinion.

The flower standard adds the following to RFC3161:

1. Freedom to put your idea anywhere you like. Currently, social networking
sites are the most reliable sites. Using social networking sites is our
idea. RFC 3161 suggests the use of a time-stamp agent. But social
networking sites already do this and they are more reliable and free of
charge and easy to use. Another solution we are working on is augmenting modern
poor man's copyright
<http://en.wikipedia.org/wiki/Poor_man%27s_copyright>with a publish
e-mail function. You can send your idea to yourself via
e-mail. The service provider time-stamps it. You can show others your
e-mail by publishing your e-mail. I.e. giving access to a particular
e-mail.

There are many possible solutions. Flower standard allows to use all of
them this doesn't excluded RFC3161.

2. The flower sign on a file indicates to the public that a document is
original and protected using this method. If I see a document and there is
no flower sign on it, I can pretend that it is mine or try to steal it. But
if there is a flower sign I will know that it is protected. This will stop
me. This is like the copyright sign. But the copyright sign has a different
meaning. It doesn't explain that the idea is time-stamped. In addition,
this concept is not about "copyright". It is about "proof of work". You can
copy my work if I permit but the idea is mine and I can prove it.

Cheers,

-- 
Pars Mutaf
flower-standard.org

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

<br><br><div class=3D"gmail_quote">On Tue, Dec 4, 2012 at 11:18 AM, Pars Mu=
taf <span dir=3D"ltr">&lt;<a href=3D"mailto:pars.mutaf@gmail.com" target=3D=
"_blank">pars.mutaf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
Dear all, <br><br>FYI, I designed the following standard myself. It complet=
es IETF RFC 3161.<br><br><a href=3D"http://www.flower-standard.org" target=
=3D"_blank">www.flower-standard.org</a><br clear=3D"all"><br>Cheers, <br>Pa=
rs Mutaf<br>

</blockquote></div><br><br>More info about the design rational. I provide t=
his information here because someone may ask later why I did not ask the IE=
TF&#39;s opinion. <br><br>The flower standard adds the following to RFC3161=
: <br>
<br>1. Freedom to put your idea anywhere you like. Currently, social=20
networking sites are the most reliable sites. Using social networking=20
sites is our idea. RFC 3161 suggests the use of a time-stamp agent. But=20
social networking sites already do this and they are more reliable and=20
free of charge and easy to use. Another solution we are working on is=20
augmenting <a href=3D"http://en.wikipedia.org/wiki/Poor_man%27s_copyright" =
target=3D"_blank">modern poor man&#39;s copyright</a>
 with a publish e-mail function. You can send your idea to yourself via=20
e-mail. The service provider time-stamps it. You can show others your=20
e-mail by publishing your e-mail. I.e. giving access to a particular=20
e-mail. <br>

<br>There are many possible solutions. Flower standard allows to use all of=
 them this doesn&#39;t excluded RFC3161.<br><br>
2. The flower sign on a file indicates to the public that a document is=20
original and protected using this method. If I see a document and there=20
is no flower sign on it, I can pretend that it is mine or try to steal=20
it. But if there is a flower sign I will know that it is protected. This
 will stop me. This is like the copyright sign. But the copyright sign=20
has a different meaning. It doesn&#39;t explain that the idea is=20
time-stamped. In addition, this concept is not about &quot;copyright&quot;.=
 It is=20
about &quot;proof of work&quot;. You can copy my work if I permit but the i=
dea is=20
mine and I can prove it. <br>

<br>
Cheers, <br>
<br>
-- <br>Pars Mutaf<br><a href=3D"http://flower-standard.org" target=3D"_blan=
k">flower-standard.org</a><br><br>

--047d7bacc07e11fee104d03d0e97--

From hannes.tschofenig@gmx.net  Fri Dec  7 02:27:14 2012
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 91CFF21F86A3 for <ietf@ietfa.amsl.com>; Fri,  7 Dec 2012 02:27:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QabyZdOFCj3q for <ietf@ietfa.amsl.com>; Fri,  7 Dec 2012 02:27:14 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id BC8DB21F869B for <ietf@ietf.org>; Fri,  7 Dec 2012 02:27:13 -0800 (PST)
Received: (qmail invoked by alias); 07 Dec 2012 10:27:11 -0000
Received: from a88-115-216-191.elisa-laajakaista.fi (EHLO [192.168.100.100]) [88.115.216.191] by mail.gmx.net (mp034) with SMTP; 07 Dec 2012 11:27:11 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19UopdZqllUfvWgh1JF3ExXWELi6XOSltU5TlkSDy uYBxQ2eqmSXR3P
Subject: Re: Simplifying our processes: Conference Calls
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: <50BF754A.2080107@dcrocker.net>
Date: Fri, 7 Dec 2012 12:17:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <07CC137B-F0ED-4ACB-A33A-BD5E20ED93B9@gmx.net>
References: <50BE3721.90004@dcrocker.net> <CCE40691.1531%Hannes.Tschofenig@nsn.com> <CAF4+nEGATcHjM0360Vun1KdxsHabxuSyVRPzsFqo-Ex5eqvJ4w@mail.gmail.com> <999913AB42CC9341B05A99BBF358718D022E0BE8@FIESEXC035.nsn-intra.net> <50BF754A.2080107@dcrocker.net>
To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 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: Fri, 07 Dec 2012 10:27:14 -0000

I think I have gotten enough responses to my question on the mailing =
list and also off-list. Thanks a lot. =20

Ciao
Hannes


From sm@elandsys.com  Sun Dec  9 12:13:24 2012
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 B63B521F8CFB for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 12:13:24 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WxB9Cz-t9cyi for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 12:13:23 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D302321F8CF8 for <ietf@ietf.org>; Sun,  9 Dec 2012 12:13:23 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.68]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id qB9KDCMf008442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 9 Dec 2012 12:13:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1355084002; bh=QPJ4LN7uKcyEW9KVxX9hfuAORKJqRL1/Ly/lC0tqq7w=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=XBzNE1zLssHLnquEfGhA0EQjzjx+pjGT9vOIDHinDSQgYiWh+157OhrrlsrQsD/DL GRlocAlZUmzFBnyfHuHXr8WdbkItGd0Ejuzp4lRViYAsA/tZZE/iXwLo1ucA+HdxQc lTTEtRJPj9mVf6X7YQz2eFkMOeRLN6gt5Url8k/A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1355084002; i=@elandsys.com; bh=QPJ4LN7uKcyEW9KVxX9hfuAORKJqRL1/Ly/lC0tqq7w=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=CtdN8V5AFBtXuBCpltnnPlH4ZOrkZSVoLiyIkytaVvLEeQjjR+QXi5sIgYvqDiD4z GNFtzmKnQUsm/J9376aBiMm3Xi8wkE91HRj2h+Nazux5ggZpcFxPGlu+Viqj3y7NZr Wnk5eMvRMEJfYdo7N2y9Xh7Ndyf/0zju8c9wMdCM=
Message-Id: <6.2.5.6.2.20121209105838.09574c88@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 09 Dec 2012 11:43:39 -0800
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A mailing list protocol
In-Reply-To: <20121206212400.10366.qmail@joyce.lan>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <20121206212400.10366.qmail@joyce.lan>
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: Sun, 09 Dec 2012 20:13:24 -0000

Hello,

Thanks to all of you who provided feedback on this thread and 
off-list.  I'll attempt to summarize the comments on this thread.

Wes George asked whether there was an IETF standard format for 
handling inline quote replies and whether it has been implemented 
[1].  He mentioned that rehashing an old draft about nettiquete 101 
is less helpful.  He also commented  about the common problem of 
mangled subject lines that make it very difficult to sort by 
thread.  There was also an off-list comment about this.   Scott 
Brim's comment [2] is an interesting view about standardization.

Dave Cridland mentioned RFC 3676 [3].  He pointed out that it 
primarily useful in simple replies rather than quoting.  One of the 
problem he encounters is a lack of in-reply-to or references fields 
that I can use for in-thread navigation.  Alessandro Vesely commented 
about disclaimers in messages [4].

I avoided a discussion of standards or to dictate etiquette in 
draft-moonesamy-mail-list-protocol.  Section 2 list points which may 
see obvious to a lot of people on this mailing list.  The text at 
http://www.ietf.org/newcomers.html doesn't provide a lot of 
information about facilitating discussions.

I would like to ask you to pick the three points from Section 2 ( 
http://tools.ietf.org/html/draft-moonesamy-mail-list-protocol-00 ) 
which you consider as helpful to facilitate mailing list discussion 
and send them to me off-list.  I'll post a summary to this mailing 
list after a week.

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/ietf/current/msg76271.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg76275.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg76295.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg76296.html


From melinda.shore@gmail.com  Sun Dec  9 12:40:40 2012
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 4CF4021F8CE1 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 12:40:40 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXRfz7cV-pDy for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 12:40:39 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id D35D521F8CD8 for <ietf@ietf.org>; Sun,  9 Dec 2012 12:40:29 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id hz11so1474463pad.31 for <ietf@ietf.org>; Sun, 09 Dec 2012 12:40:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=WcS9fl2FRLifvkjvA2uaUKTqxTrMEWKZmNOxJnZ3vJI=; b=kkqDIH1Yu4EDABiCZKtaTaImy5R6O7cjNEfLYAP/7EQtrIeEp593DEsQ7w5eMv/oZe DN2tt6c5u696use9ADhkQ1AXX50vjNtP7R8BroI9XuYlkGew/jXNjIdeWnByLSIkybbJ vYLyNdWI+SgegaULjYjPNVtmbmuLw6ZN2pomhAnsWE02gJe+CJwWgWTfp1TU2eJ8gr98 zJG6mqJVfZggmENWAo+q5cM6SEST3HLvevHx6pt2QtT1CX9OmR24ytV8uPlzueNgqb1X b44Zdf3a74BKgT/RVZ+NGtpGK3er0KKraV3fCNY8TnXnlnn4n9XXTWNRt3h63G6H3Ytd uzyg==
Received: by 10.68.252.4 with SMTP id zo4mr33555690pbc.126.1355085629330; Sun, 09 Dec 2012 12:40:29 -0800 (PST)
Received: from spandex.local (216-67-41-130-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.41.130]) by mx.google.com with ESMTPS id rk17sm10538288pbb.3.2012.12.09.12.40.27 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 09 Dec 2012 12:40:28 -0800 (PST)
Message-ID: <50C4F73A.1050707@gmail.com>
Date: Sun, 09 Dec 2012 11:40:26 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A mailing list protocol
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net>
In-Reply-To: <6.2.5.6.2.20121209105838.09574c88@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: Sun, 09 Dec 2012 20:40:40 -0000

On 12/9/12 10:43 AM, S Moonesamy wrote:
> I would like to ask you to pick the three points from Section 2 (
> http://tools.ietf.org/html/draft-moonesamy-mail-list-protocol-00 ) which
> you consider as helpful to facilitate mailing list discussion and send
> them to me off-list.  I'll post a summary to this mailing list after a
> week.

I'm increasingly not a fan of process documents.  It may be the case
that we need a process document addressing the problem of excessive
process documents.  I hope that where your efforts end up is a wiki
page or some such, which I think would be helpful, rather than an RFC,
which I think would not.

Melinda



From nick@inex.ie  Sun Dec  9 12:54:57 2012
Return-Path: <nick@inex.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 96E9221F8D06 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 12:54:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGUaopUJe+JU for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 12:54:57 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id CE6F721F8D05 for <ietf@ietf.org>; Sun,  9 Dec 2012 12:54:55 -0800 (PST)
X-Envelope-To: <ietf@ietf.org>
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:29d8:681e:888:4c66]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qB9KrH2h015153 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 9 Dec 2012 20:53:23 GMT (envelope-from nick@inex.ie)
Message-ID: <50C4FA96.9050101@inex.ie>
Date: Sun, 09 Dec 2012 20:54:46 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A mailing list protocol
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net> <50C4F73A.1050707@gmail.com>
In-Reply-To: <50C4F73A.1050707@gmail.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
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, 09 Dec 2012 20:54:57 -0000

On 09/12/2012 20:40, Melinda Shore wrote:
> process documents.  I hope that where your efforts end up is a wiki
> page or some such, which I think would be helpful, rather than an RFC,
> which I think would not.

Pretty much everything in the draft is covered by many third party wikis
and faqs already.  Perhaps a paragraph in the Tao document would suffice
instead of an rfc?

Nick


From john-ietf@jck.com  Sun Dec  9 13:17:18 2012
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 307A921F8CF8 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 13:17:18 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihAD2iEfLZxt for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 13:17:17 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9515A21F8981 for <ietf@ietf.org>; Sun,  9 Dec 2012 13:17:17 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ThoFQ-000BXS-Or; Sun, 09 Dec 2012 16:17:16 -0500
Date: Sun, 09 Dec 2012 16:17:11 -0500
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: A mailing list protocol
Message-ID: <B7B7CE09B650295D27AA1203@JcK-HP8200.jck.com>
In-Reply-To: <50C4F73A.1050707@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net> <50C4F73A.1050707@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: Sun, 09 Dec 2012 21:17:18 -0000

--On Sunday, December 09, 2012 11:40 -0900 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 12/9/12 10:43 AM, S Moonesamy wrote:
>> I would like to ask you to pick the three points from Section
>> 2 (
>> http://tools.ietf.org/html/draft-moonesamy-mail-list-protocol
>> -00 ) which you consider as helpful to facilitate mailing
>> list discussion and send them to me off-list.  I'll post a
>> summary to this mailing list after a week.
> 
> I'm increasingly not a fan of process documents.  It may be
> the case that we need a process document addressing the
> problem of excessive process documents.  I hope that where
> your efforts end up is a wiki page or some such, which I think
> would be helpful, rather than an RFC, which I think would not.

+1 and an observation:  

I think there is a simple test as to when a process document is
actually necessary.  If the nature of the relevant process is
such that one wants a violation to constitute an appeal-able or
recall-able event and believes that the problem created by a
violation is serious appeal or recall should probably succeed,
then getting formal consensus and generating a BCP RFC is
probably justified.  For anything that constitutes general
guidance (as in this case) or is a statement about how some
entity intends to do things until their change their minds
again, "wiki page or some such" should be perfectly adequate and
less likely to waste community time on splitting hairs, picking
nits, and other not-very-productive activities.

Note that the above is consistent with the recent decision(s)
about the Tao: informative document, general guidance, but not
something that contains rule whose violation can be appealed,
hence a web page and some guidance about how it will be
maintained, not a series of RFCs.

    john


From hsantos@isdg.net  Sun Dec  9 13:21:10 2012
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 4016421F8D22 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 13:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.154, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vy1Jrbp0ZmPs for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 13:21:09 -0800 (PST)
Received: from secure.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3B19321F8D20 for <ietf@ietf.org>; Sun,  9 Dec 2012 13:21:08 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=747; t=1355088067; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=62pDJFAcyPOoJfOcqxoli5CvswI=; b=Q+3bf/CboIocLNWuCebl v+zruPE0wwQYB4C7W1dddLuUQ8cTstPlJRVYXb+e2CpukZQWy0L8BgmIbKgkOBSx GUU4VsWRJcSYpFHEiNyrMPN2Zi1VAWwR2M0EpFIZAyXblUxhQF5h5mIYEjnHPP5s WdePxi6mSqtdAr61u0IBIjo=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 09 Dec 2012 16:21:07 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2519822963.15845.3480; Sun, 09 Dec 2012 16:21:06 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=747; t=1355088064; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=UWEdzp8 QYxK1V2wJN6zVw7+RGyV7swqNvBxSQKj+KeE=; b=0jcYA6/hrJtrDOpMETkRngq K3ExPWodUJYnEz6qiv03MBITHW+Ds0r5PC3OKOnwL/YUJHgiV3TrUiZ628XZS2WE vg/JqYBV5HF1di8Uqz9xCnSazi0UKuCgFh+dinukRpdNyovvxdxDiI3lWCyvzL52 PPQwW8b31QSC80pwY4BM=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 09 Dec 2012 16:21:04 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3118547288.10.4616; Sun, 09 Dec 2012 16:21:03 -0500
Message-ID: <50C500F6.3070704@isdg.net>
Date: Sun, 09 Dec 2012 16:21:58 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: A mailing list protocol
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com>	<20121206212400.10366.qmail@joyce.lan>	<6.2.5.6.2.20121209105838.09574c88@resistor.net> <50C4F73A.1050707@gmail.com>
In-Reply-To: <50C4F73A.1050707@gmail.com>
Content-Type: text/plain; charset=UTF-8; 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: Sun, 09 Dec 2012 21:21:10 -0000

Melinda Shore wrote:
> On 12/9/12 10:43 AM, S Moonesamy wrote:
>> I would like to ask you to pick the three points from Section 2 (
>> http://tools.ietf.org/html/draft-moonesamy-mail-list-protocol-00 ) which
>> you consider as helpful to facilitate mailing list discussion and send
>> them to me off-list.  I'll post a summary to this mailing list after a
>> week.
> 
> I'm increasingly not a fan of process documents.  It may be the case
> that we need a process document addressing the problem of excessive
> process documents.  I hope that where your efforts end up is a wiki
> page or some such, which I think would be helpful, rather than an RFC,
> which I think would not.
> 
> Melinda

+1, thank you for speaking up.

-- 
HLS



From randy@psg.com  Sun Dec  9 14:39:51 2012
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 91A0821F8D7D for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 14:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.556
X-Spam-Level: 
X-Spam-Status: No, score=-2.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E9pLJS99uRsI for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 14:39:51 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 36E4521F8D7B for <ietf@ietf.org>; Sun,  9 Dec 2012 14:39:51 -0800 (PST)
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 1ThpXK-0004cW-7g; Sun, 09 Dec 2012 22:39:50 +0000
Date: Mon, 10 Dec 2012 07:39:49 +0900
Message-ID: <m2lid64zpm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: A mailing list protocol
In-Reply-To: <50C4F73A.1050707@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.com> <20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net> <50C4F73A.1050707@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, 09 Dec 2012 22:39:51 -0000

> I'm increasingly not a fan of process documents.

the rise of a bureaucratic class is a dangerous sign of ossification.

i just failed gobbling for an image of the net police ticket dr postel
used to have on his wall.  if anyone has an image, i would dearly love
a copy.  advthanksance.

randy

From randy@qti.qualcomm.com  Sun Dec  9 18:17:55 2012
Return-Path: <randy@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 8852621F8DA3 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 18:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BFfQhuLplWk for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 18:17:55 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id E669121F8D9E for <ietf@ietf.org>; Sun,  9 Dec 2012 18:17:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1355104269; x=1386640269; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=3bU2N97kv2Vm/m/ZC1GdAgjeEQikulJk2gfW9+T1Yaw=; b=q39vH+BiBYi4XU5K8VGljsvBXrBGZSkPXLy5JtCDhEFxDKvTehHFZX+g QOmAuevsZgMEpn9tkw1IpfdTrjJcC8BU7WquZE1LzI8Vu+hJxuStCqTCs J47WqICa21sCumPUZxEUkFR1u4Xc57k1EcpmdgSwsLacupMwksg9sk1p0 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="11212623"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP; 09 Dec 2012 17:51:09 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="440873590"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Dec 2012 18:17:54 -0800
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 9 Dec 2012 18:17:53 -0800
Message-ID: <p06240600cceaf67ab02c@[99.111.97.136]>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.co m>
References: <20121204183432.3748.97064.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121204121234.09360870@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.co m>
X-Mailer: Eudora for Mac OS X
Date: Sun, 9 Dec 2012 18:17:52 -0800
To: "George, Wes" <wesley.george@twcable.com>, "ietf@ietf.org" <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: RE: A mailing list protocol
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 02:17:55 -0000

At 5:19 PM -0500 12/4/12, Wes George wrote:

>  Is there an IETF standard format for handling inline quote replies?

Yes, RFC 3676.

>   Is it just not implemented in certain mail clients?

Sadly, yes.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Ask not what you can do for your country, ask what's for lunch.
                         --Orson Welles on reaching 300 pounds

From randy@qti.qualcomm.com  Sun Dec  9 18:28:51 2012
Return-Path: <randy@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 48D8321F8DB7 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 18:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level: 
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUjfovd7fp79 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 18:28:50 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFF021F8DA0 for <ietf@ietf.org>; Sun,  9 Dec 2012 18:28:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1355105537; x=1386641537; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=ZtF9J55sv8eq+J4IPE7ClPKJeXT7W35aK9Y2Yp8/xW0=; b=gXG2erPaP+XIzL8qvXqXqdy1rzc1Pl3gEweLbMI2PyXKQLoDiAPMmHM0 M/8JXNOh8ea9maQY+jQoDVQMIHBKjWXj5orH4YZKSOdJC4zGTpO8MiWNf Xwuf1dJ+hwlkIfIsMR2xI088DZA42sD/KAIV8Iut/kR0B3fEigQg4oK8F 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="11210369"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 09 Dec 2012 18:12:13 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="356147438"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Dec 2012 18:28:46 -0800
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 9 Dec 2012 18:28:46 -0800
Message-ID: <p06240601cceaf832172f@[99.111.97.136]>
In-Reply-To: <6.2.5.6.2.20121209105838.09574c88@resistor.net>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.co m>	<20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net>
X-Mailer: Eudora for Mac OS X
Date: Sun, 9 Dec 2012 18:28:44 -0800
To: S Moonesamy <sm+ietf@elandsys.com>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: A mailing list protocol
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 02:28:51 -0000

At 11:43 AM -0800 12/9/12, S Moonesamy wrote:

>  Dave Cridland mentioned RFC 3676 [3].  He pointed out that it 
> primarily useful in simple replies rather than quoting.

Just to clarify: Dave didn't say that RFC 3676 is not useful for 
quoting (indeed, quoting is one of it's main points).  Dave pointed 
out that RFC 3676 didn't include a mechanism to attribute each quote 
to a specific author, which is true.  Dave also pointed out that this 
attribution could in theory be accomplished by matching the quote 
level (which is included) to the 'References:' chain, although this 
would be fragile in practice because so few clients correctly 
implement 'References:'.

>  One of the problem he encounters is a lack of in-reply-to or 
> references fields that I can use for in-thread navigation.

Used for threading in general, not in-thread navigation (I'm not sure 
I understand the difference, but to me, threading is the ability to 
group together messages in a logical thread or discussion, while 
in-thread navigation would be the ability to jump around within a 
thread).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
With most men, life is like backgammon -- half skill and half luck.
                                           --Oliver Wendell Holmes

From randy@qti.qualcomm.com  Sun Dec  9 18:39:21 2012
Return-Path: <randy@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 4F22C21F8DC5 for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 18:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.478
X-Spam-Level: 
X-Spam-Status: No, score=-102.478 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G4uUr7wDg6eB for <ietf@ietfa.amsl.com>; Sun,  9 Dec 2012 18:39:20 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id ADD3821F8DC4 for <ietf@ietf.org>; Sun,  9 Dec 2012 18:39:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1355105555; x=1386641555; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=a1y9LLJ7iRm+7n15jiORJiUeTJFtqnZia1WbaHv0Prc=; b=B/3n2NjMjkpPCzNF0gjXQ8ug0+bYnXsRLi5z6IhvxQD+G0NjYp+YvUX6 pb5fpjjqJC01D6QNusLvcR4QMhlMDfQCHO2a786Mzp7qChhkMjPij2cVa cth5Ygfs+0uQzpgsH8QyuaDZzGLAyFVUh71k0nRasHYQykTPGUvDEF0X7 M=;
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="11214786"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 09 Dec 2012 18:12:35 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,6921"; a="382503938"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Dec 2012 18:39:20 -0800
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 9 Dec 2012 18:39:19 -0800
Message-ID: <p06240602cceaf9ca76d6@[99.111.97.136]>
In-Reply-To: <50C4F73A.1050707@gmail.com>
References: <2671C6CDFBB59E47B64C10B3E0BD59230338CCCD84@PRVPEXVS15.corp.twcable.co m>	<20121206212400.10366.qmail@joyce.lan> <6.2.5.6.2.20121209105838.09574c88@resistor.net> <50C4F73A.1050707@gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Sun, 9 Dec 2012 18:33:29 -0800
To: Melinda Shore <melinda.shore@gmail.com>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: A mailing list protocol
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Dec 2012 02:39:21 -0000

At 11:40 AM -0900 12/9/12, Melinda Shore wrote:

>  I'm increasingly not a fan of process documents.  It may be the case
>  that we need a process document addressing the problem of excessive
>  process documents.  I hope that where your efforts end up is a wiki
>  page or some such, which I think would be helpful, rather than an RFC,
>  which I think would not.

Unfortunately, I see little evidence that any of these would be 
useful in this case.  Process documents, web pages, and the like can 
only be useful if people follow them, and I don't see cause for 
optimism that anyone who isn't currently following what we desire 
will start doing so once the RFC or wiki page is published.  I'd be 
delighted to be wrong, of course.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Surströmmingspremier (SEUR-stomins-prem-ya; Swedish; noun): The
first day of the year when it is acceptable eat Surströmming,
extremely foul-smelling fermented herring (banned in some apartment
complexes, airplanes, etc.) -- literally, "sour fish premier."

From barryleiba.mailing.lists@gmail.com  Tue Dec 11 07:25:59 2012
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 82B4021F881A; Tue, 11 Dec 2012 07:25:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.094
X-Spam-Level: 
X-Spam-Status: No, score=-103.094 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XC9xQD2jWMhQ; Tue, 11 Dec 2012 07:25:59 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 84E0C21F8815; Tue, 11 Dec 2012 07:25:58 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so3319883lbk.31 for <multiple recipients>; Tue, 11 Dec 2012 07:25:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=fTJ65mUqmvsYLh3gEWkY6L7PMonGsKL1RCQ1ayttsjo=; b=fltTwEZmb0i14mbPls9Timwe1Kq70cqhJx8A2Se3zI3hl/f/Rf+SfRFAr2f3f53lQ7 P0gF2uMlRu9Dw0fReTJ2luYq6xHJPg9HKlE9j2YyFL1CtZGt/ClcjpNL0pBXWRTPIokY RbD12kNcGSIpTGe7wGEngKFZ30JMq8697xLrKFz39FpzUlAbmSqwORiQqqE5eHtw+efo QHb/pS0H8f9ged19mCM/lkZjT32Pors2URlMWq59qvRimuP+gXownnlwgijfsqEZVbTl rvXZMASpB/caKSGvxJ9w/V+Gc0l7MvAqdK2Stxhtp3OLJzNJoS9wqFADZpbrxel9vApz l4aQ==
MIME-Version: 1.0
Received: by 10.112.25.34 with SMTP id z2mr7677167lbf.125.1355239557492; Tue, 11 Dec 2012 07:25:57 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Tue, 11 Dec 2012 07:25:57 -0800 (PST)
In-Reply-To: <20121211150005.28209.96763.idtracker@ietfa.amsl.com>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com>
Date: Tue, 11 Dec 2012 10:25:57 -0500
X-Google-Sender-Auth: N71ui7HSiSdpSu_2bo6qGeIvU_4
Message-ID: <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@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, 11 Dec 2012 15:25:59 -0000

> Abstract
>    JSON Patch defines the media type "application/json-patch", a JSON
>    document structure for expressing a sequence of operations to apply
>    to a JSON document, suitable for use with the HTTP PATCH method.
...
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/

I've reviewed JSON Patch and JSON Pointer as responsible AD, and am
very happy with the documents -- this is good work, well written.  I
came up with one issue that I want to discuss as part of last call:

   4.1.  add

   The "add" operation adds a new value at the target location.  The
   operation object MUST contain a "value" member that specifies the
   value to be added.

   For example:

   { "op": "add", "path": "/a/b/c", "value": [ "foo", "bar" ] }

   When the operation is applied, the target location MUST reference one
   of:

   o  The root of the target document - whereupon the specified value
      becomes the entire content of the target document.

Now, what this means is that if we start with this:

{ "a": { "num": 1 } }

and we apply this:

{ "op": "add", "path": "", "value": [ "foo", "bar" ] }

we end up with this:

[ "foo", "bar" ]

This doesn't strike me as having any sense of an "add" operation -- it
appears to be a special case that doesn't fit.  In any other
situation, using any other path, the operation either adds something
to what's already there, or it fails.  But when the path is "", it's
anomalous.

So, three questions:

1. Do I have this right, or am I mistaken about the result of that operation?

2. Assuming I have it right, can someone explain why it's this way?

3. Can someone explain why this is the right way to specify it, rather
than using "replace" for this?

Barry

From pier-luc@sarkass.com  Tue Dec 11 15:13:00 2012
Return-Path: <pier-luc@sarkass.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B5021E809B for <ietf@ietfa.amsl.com>; Tue, 11 Dec 2012 15:13:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-X0YvYDL3tx for <ietf@ietfa.amsl.com>; Tue, 11 Dec 2012 15:12:59 -0800 (PST)
Received: from toroondcbmts04-srv.bellnexxia.net (toroondcbmts04-srv.bellnexxia.net [207.236.237.38]) by ietfa.amsl.com (Postfix) with ESMTP id 69BB521E8090 for <ietf@ietf.org>; Tue, 11 Dec 2012 15:12:59 -0800 (PST)
Received: from toip58-bus.srvr.bell.ca ([67.69.240.185]) by toroondcbmts04-srv.bellnexxia.net (InterMail vM.8.00.01.00 201-2244-105-20090324) with ESMTP id <20121211231258.DURJ24138.toroondcbmts04-srv.bellnexxia.net@toip58-bus.srvr.bell.ca> for <ietf@ietf.org>; Tue, 11 Dec 2012 18:12:58 -0500
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYCAPayx1C4keta/2dsb2JhbAANOINIux6DEQEBAQQ4QBELGAkWDwkDAgECAUUTCAKIGadwgzCQQY1kgykDiGCOQ5I9
X-IronPort-AV: E=Sophos;i="4.84,262,1355115600";  d="scan'208";a="8546871"
Received: from bas13-quebec14-3096570714.dsl.bell.ca (HELO [192.168.2.8]) ([184.145.235.90]) by toip58-bus.srvr.bell.ca with ESMTP; 11 Dec 2012 18:12:58 -0500
Message-ID: <50C7BDDC.6080409@sarkass.com>
Date: Tue, 11 Dec 2012 18:12:28 -0500
From: =?ISO-8859-1?Q?Pier-Luc_Th=E9riault?= <pier-luc@sarkass.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121027 Icedove/10.0.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com>
In-Reply-To: <20121211150005.28209.96763.idtracker@ietfa.amsl.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: Tue, 11 Dec 2012 23:13:00 -0000

On 11/12/12 10:00 AM, The IESG wrote:
> Abstract
>     JSON Patch defines the media type "application/json-patch", a JSON
>     document structure for expressing a sequence of operations to apply
>     to a JSON document, suitable for use with the HTTP PATCH method.
>
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/
I think that at paragraph A.14 the first occurence of

A JSON Patch document:

should be

An example target JSON document:


From pier-luc@sarkass.com  Tue Dec 11 15:33:36 2012
Return-Path: <pier-luc@sarkass.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 233E321E8094 for <ietf@ietfa.amsl.com>; Tue, 11 Dec 2012 15:33:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6N6cpgNucJC for <ietf@ietfa.amsl.com>; Tue, 11 Dec 2012 15:33:35 -0800 (PST)
Received: from toroondcbmts07-srv.bellnexxia.net (toroondcbmts07-srv.bellnexxia.net [207.236.237.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2424E21E8093 for <ietf@ietf.org>; Tue, 11 Dec 2012 15:33:35 -0800 (PST)
Received: from toip59-bus.srvr.bell.ca ([67.69.240.186]) by toroondcbmts07-srv.bellnexxia.net (InterMail vM.8.00.01.00 201-2244-105-20090324) with ESMTP id <20121211233330.PFHU8942.toroondcbmts07-srv.bellnexxia.net@toip59-bus.srvr.bell.ca> for <ietf@ietf.org>; Tue, 11 Dec 2012 18:33:30 -0500
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmYCAAq7x1C4keta/2dsb2JhbAANOINIux6DEQEBAQMBOEARCyEWDwkDAgECAUUTCAKIBxKnc4MwkEKNZIMpA4hgjkOSPQ
X-IronPort-AV: E=Sophos;i="4.84,262,1355115600"; d="scan'208";a="44286045"
Received: from bas13-quebec14-3096570714.dsl.bell.ca (HELO [192.168.2.8]) ([184.145.235.90]) by toip59-bus.srvr.bell.ca with ESMTP; 11 Dec 2012 18:33:30 -0500
Message-ID: <50C7C2AB.4080206@sarkass.com>
Date: Tue, 11 Dec 2012 18:32:59 -0500
From: =?ISO-8859-1?Q?Pier-Luc_Th=E9riault?= <pier-luc@sarkass.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121027 Icedove/10.0.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com>
In-Reply-To: <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@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: Tue, 11 Dec 2012 23:33:36 -0000

>> Abstract
>>     JSON Patch defines the media type "application/json-patch", a JSON
>>     document structure for expressing a sequence of operations to apply
>>     to a JSON document, suitable for use with the HTTP PATCH method.
> ...
>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/
> I've reviewed JSON Patch and JSON Pointer as responsible AD, and am
> very happy with the documents -- this is good work, well written.  I
> came up with one issue that I want to discuss as part of last call:
>
>     4.1.  add
>
>     The "add" operation adds a new value at the target location.  The
>     operation object MUST contain a "value" member that specifies the
>     value to be added.
>
>     For example:
>
>     { "op": "add", "path": "/a/b/c", "value": [ "foo", "bar" ] }
>
>     When the operation is applied, the target location MUST reference one
>     of:
>
>     o  The root of the target document - whereupon the specified value
>        becomes the entire content of the target document.
>
> Now, what this means is that if we start with this:
>
> { "a": { "num": 1 } }
>
> and we apply this:
>
> { "op": "add", "path": "", "value": [ "foo", "bar" ] }
>
> we end up with this:
>
> [ "foo", "bar" ]
>
> This doesn't strike me as having any sense of an "add" operation -- it
> appears to be a special case that doesn't fit.  In any other
> situation, using any other path, the operation either adds something
> to what's already there, or it fails.  But when the path is "", it's
> anomalous.
>
> So, three questions:
>
> 1. Do I have this right, or am I mistaken about the result of that operation?
Yes, it's the good result
>
> 2. Assuming I have it right, can someone explain why it's this way?
It's the same as adding a value at any existing path
>
> 3. Can someone explain why this is the right way to specify it, rather
> than using "replace" for this?
It's not the right way, it's a right way. You can use replace to be sure 
that there's a root but there's always a root. Personally I would use 
replace
>
> Barry
>

From mnot@mnot.net  Tue Dec 11 15:41:34 2012
Return-Path: <mnot@mnot.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 06BDA21E80A0 for <ietf@ietfa.amsl.com>; Tue, 11 Dec 2012 15:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.966
X-Spam-Level: 
X-Spam-Status: No, score=-103.966 tagged_above=-999 required=5 tests=[AWL=-1.667, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R+JkybHJWON0 for <ietf@ietfa.amsl.com>; Tue, 11 Dec 2012 15:41:33 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 4485C21E809E for <ietf@ietf.org>; Tue, 11 Dec 2012 15:41:33 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.242.191]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D616522E259; Tue, 11 Dec 2012 18:41:25 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <50C7BDDC.6080409@sarkass.com>
Date: Wed, 12 Dec 2012 10:41:26 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <402815BB-8327-45C7-B126-CBB409B71F92@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <50C7BDDC.6080409@sarkass.com>
To: =?iso-8859-1?Q?Pier-Luc_Th=E9riault?= <pier-luc@sarkass.com>
X-Mailer: Apple Mail (2.1499)
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, 11 Dec 2012 23:41:34 -0000

In SVN, thanks.

On 12/12/2012, at 10:12 AM, Pier-Luc Th=E9riault <pier-luc@sarkass.com> =
wrote:

>=20
>=20
> On 11/12/12 10:00 AM, The IESG wrote:
>> Abstract
>>    JSON Patch defines the media type "application/json-patch", a JSON
>>    document structure for expressing a sequence of operations to =
apply
>>    to a JSON document, suitable for use with the HTTP PATCH method.
>>=20
>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/
> I think that at paragraph A.14 the first occurence of
>=20
> A JSON Patch document:
>=20
> should be
>=20
> An example target JSON document:
>=20

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




From mnot@mnot.net  Tue Dec 11 15:43:25 2012
Return-Path: <mnot@mnot.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 9B30221E8096; Tue, 11 Dec 2012 15:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.073
X-Spam-Level: 
X-Spam-Status: No, score=-104.073 tagged_above=-999 required=5 tests=[AWL=-1.474, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZ7G1iGcmi80; Tue, 11 Dec 2012 15:43:25 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7ED21E808E; Tue, 11 Dec 2012 15:43:25 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.242.191]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9BCAA22E253; Tue, 11 Dec 2012 18:43:23 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com>
Date: Wed, 12 Dec 2012 10:43:25 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3448719B-185A-476A-A927-25A68D4B4358@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 23:43:25 -0000

On 12/12/2012, at 2:25 AM, Barry Leiba <barryleiba@computer.org> wrote:

> 1. Do I have this right, or am I mistaken about the result of that =
operation?

The former.

> 2. Assuming I have it right, can someone explain why it's this way?

"add" has the semantics of "make the value *this*".

"replace" has the semantics of "make the existing value *this*"; if =
there isn't an existing value, it's an error.


> 3. Can someone explain why this is the right way to specify it, rather
> than using "replace" for this?

As has already been mentioned, there are multiple tools in the box.

Cheers,


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




From barryleiba@gmail.com  Tue Dec 11 16:24:29 2012
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 6FEEA1F0CB0; Tue, 11 Dec 2012 16:24:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.079
X-Spam-Level: 
X-Spam-Status: No, score=-103.079 tagged_above=-999 required=5 tests=[AWL=-0.102, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P2ScwGrbMjrM; Tue, 11 Dec 2012 16:24:29 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id BB2E521F8696; Tue, 11 Dec 2012 16:24:28 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so74385vbb.31 for <multiple recipients>; Tue, 11 Dec 2012 16:24:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=CgbVZrq+Ps7iZDZTFuRGomU80q7gsfP+CFICGJI+7PI=; b=b+d2OVmKq+hvJN0Vp+FYoKYr3oKG1DPOcSS2HDYTtsTG2ySuW8lbpk6akkteMIlI57 OEuf4GDmwLaYCyhNDsjYMcOpBVHZlgYIWMJKMCmZ+9vrSFLsfuTslFaOIqJScvYa2Qgq mi8EbCTx83237wlticnlSN8xbbk6/4Kjr1QazP+cLcjeg7FLtpLLZN2reOQoTpCoI3iB PIRiNrS9V5Th+Qh0IRyQA3LcA6iLTgqV7EVj4V0oBvqLxha9qh/cifojaiBDkI7anIej XmZQHDxrqVl/HBtGs0r8ivIZ2iLMsZ6CSsysctj2mAZnIHR/u4DUafS2l9+lznOvXSTj nGNA==
MIME-Version: 1.0
Received: by 10.220.157.71 with SMTP id a7mr6711146vcx.19.1355271868191; Tue, 11 Dec 2012 16:24:28 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Tue, 11 Dec 2012 16:24:27 -0800 (PST)
In-Reply-To: <3448719B-185A-476A-A927-25A68D4B4358@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net>
Date: Tue, 11 Dec 2012 19:24:27 -0500
X-Google-Sender-Auth: VLCsbCAtuoXLafFeQtdZKpgMUMU
Message-ID: <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 00:24:29 -0000

> "add" has the semantics of "make the value *this*".

Yeh, I guess the problem I have with that is that that's not the
semantics most of us attach to the concept of "add a thing to a set".
And it bothers me that "add to an object" and "add to an array" have
different semantics.

That difference is unsettling.  It's OK to have "add" on an array have
the semantics of "insert", especially because there's no "insert"
action.  But having "add" on an object have the semantics of "replace"
seems bad, partly because it's inconsistent with the semantics it has
on an array and because there's already a "replace" action.

If I have { "baz": "qux", "foo": "bar" }, these two do exactly the same thing:

case 1a: [{ "op": "add", "path": "/baz", "value": "blarg" }]

case 1b: [{ "op": "replace", "path": "/baz", "value": "blarg" }]

Both result in { "baz": "blarg", "foo": "bar" }

While these are different:

case 2a: [{ "op": "add", "path": "/hah", "value": "blarg" }]

case 2b: [{ "op": "replace", "path": "/hah", "value": "blarg" }]

Case 2a results in { "baz": "blarg", "foo": "bar", "hah": "blarg" },
and 2b is an error.

Case 1 just seems wrong.  The "add" in 1a should be an error, and then
life would make sense.


> As has already been mentioned, there are multiple tools in the box.

Stretching the analogy, having the wrench act as a hammer in some
cases does not make for a particularly well defined, robust tool box.

Barry

From mnot@mnot.net  Tue Dec 11 16:31:44 2012
Return-Path: <mnot@mnot.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 D02C321F8898; Tue, 11 Dec 2012 16:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.036
X-Spam-Level: 
X-Spam-Status: No, score=-104.036 tagged_above=-999 required=5 tests=[AWL=-1.437, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vWOB-cxYOSpe; Tue, 11 Dec 2012 16:31:44 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 269D211E80A3; Tue, 11 Dec 2012 16:31:43 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.242.191]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 30D0022E1F4; Tue, 11 Dec 2012 19:31:36 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com>
Date: Wed, 12 Dec 2012 11:31:39 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 00:31:45 -0000

So, do you have a suggestion?


On 12/12/2012, at 11:24 AM, Barry Leiba <barryleiba@computer.org> wrote:

>> "add" has the semantics of "make the value *this*".
>=20
> Yeh, I guess the problem I have with that is that that's not the
> semantics most of us attach to the concept of "add a thing to a set".
> And it bothers me that "add to an object" and "add to an array" have
> different semantics.
>=20
> That difference is unsettling.  It's OK to have "add" on an array have
> the semantics of "insert", especially because there's no "insert"
> action.  But having "add" on an object have the semantics of "replace"
> seems bad, partly because it's inconsistent with the semantics it has
> on an array and because there's already a "replace" action.
>=20
> If I have { "baz": "qux", "foo": "bar" }, these two do exactly the =
same thing:
>=20
> case 1a: [{ "op": "add", "path": "/baz", "value": "blarg" }]
>=20
> case 1b: [{ "op": "replace", "path": "/baz", "value": "blarg" }]
>=20
> Both result in { "baz": "blarg", "foo": "bar" }
>=20
> While these are different:
>=20
> case 2a: [{ "op": "add", "path": "/hah", "value": "blarg" }]
>=20
> case 2b: [{ "op": "replace", "path": "/hah", "value": "blarg" }]
>=20
> Case 2a results in { "baz": "blarg", "foo": "bar", "hah": "blarg" },
> and 2b is an error.
>=20
> Case 1 just seems wrong.  The "add" in 1a should be an error, and then
> life would make sense.
>=20
>=20
>> As has already been mentioned, there are multiple tools in the box.
>=20
> Stretching the analogy, having the wrench act as a hammer in some
> cases does not make for a particularly well defined, robust tool box.
>=20
> Barry

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




From barryleiba@gmail.com  Tue Dec 11 17:01:20 2012
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 B560621E8096; Tue, 11 Dec 2012 17:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.078
X-Spam-Level: 
X-Spam-Status: No, score=-103.078 tagged_above=-999 required=5 tests=[AWL=-0.101, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVn+ZYcNjl1g; Tue, 11 Dec 2012 17:01:20 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 07D7111E80A3; Tue, 11 Dec 2012 17:01:19 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so109444vcb.31 for <multiple recipients>; Tue, 11 Dec 2012 17:01:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=k4wXQ6CxOlbWIm4oeubuVGaYhzbDAMzedR2sckPxsCc=; b=Am8uPWc/xqa0DKKfthjE1wQf9RKsulrDlqzaLDbZWlIrjYOzyhe5BLPpryIRZbQKts 8qbiEoi2Qp72OYl1qqE9laGiSRgswieivoQht2OMlR23ObAB0Ln0YX8eVuwDTV01n64v bBS81UG1cyKLnU8b3WdmsDZ/PUvprUlUqDDBtqLBOAJcn/QgEHMjYp3gF1KDSUAbLSZg IG+ls98GIlgeNJVzx+4ozfOp8cKAoBAP+/MMh0x1GoJkcYtxKTJYFDOsNql4Qzgtbc9T Fz47pzUIepAmhVF2yj8mJOKqigPyVs0IPIXN+PSUqt3W8NcXO0Tg4wUkgaseyHUfmzV5 5piA==
MIME-Version: 1.0
Received: by 10.58.221.130 with SMTP id qe2mr20064vec.14.1355274079499; Tue, 11 Dec 2012 17:01:19 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Tue, 11 Dec 2012 17:01:19 -0800 (PST)
In-Reply-To: <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net>
Date: Tue, 11 Dec 2012 20:01:19 -0500
X-Google-Sender-Auth: Q6Kuj75c1hGr8oVPhvVkbv8YXb4
Message-ID: <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 01:01:20 -0000

> So, do you have a suggestion?

I do, and it's buried in there:

>> Case 1 just seems wrong.  The "add" in 1a should be an error, and then
>> life would make sense.

Turning that into a text suggestion, it would be this (which
represents a change to the protocol, so the working group would have
to accept it):

OLD
   When the operation is applied, the target location MUST reference one
   of:

   o  The root of the target document - whereupon the specified value
      becomes the entire content of the target document.

   o  A member to add to an existing object - whereupon the supplied
      value is added to that object at the indicated location.  If the
      member already exists, it is replaced by the specified value.
NEW
   When the operation is applied, the target location MUST reference one
   of:

   o  A member to add to an existing object - whereupon the supplied
      value is added to that object at the indicated location.  It is an error
      for the specified member to already exist.
END

OLD
   For example, "add"ing to the path "/a/b" to this document:

   { "a": { "foo": 1 } }

   is not an error, because "a" exists, and "b" will be added to its
   value.  It is an error in this document:

   { "q": { "bar": 2 } }

   because "a" does not exist.
NEW
   For example, given the following starting document:

   { "a": { "foo": 1 } }

   o  "add"ing to the path "/a/b" is not an error, because "/a" exists,
      and "b" will be added to its value.

   o  "add"ing to the path "/q/b" is an error, because "/q" does not
      exist.  But "/q" can be added first, followed by "add"ing "/q/b".

   o  "add"ing to the path "/a" or "/a/foo" is an error, because "/a"
      and "/a/foo" both exist already, and cannot be added.
END

I understand that this will change implementations -- patches that
used to use "add" will now have to use "replace", and there's now no
way to do "add this if it's not already there, and replace it if it is
already there".  Perhaps there's a need to add something with those
semantics.  On the other hand, as the text stands now, there's no way
to do "add this only if it's not already there", because "test" can't
test for existence.

Barry

From mnot@mnot.net  Tue Dec 11 17:14:53 2012
Return-Path: <mnot@mnot.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 C0EE821E8094; Tue, 11 Dec 2012 17:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.001
X-Spam-Level: 
X-Spam-Status: No, score=-104.001 tagged_above=-999 required=5 tests=[AWL=-1.402, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7YH6Qz16-oA9; Tue, 11 Dec 2012 17:14:53 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 18E2521E8030; Tue, 11 Dec 2012 17:14:53 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.242.191]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1A4DA22E1F4; Tue, 11 Dec 2012 20:14:45 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com>
Date: Wed, 12 Dec 2012 12:14:49 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 01:14:53 -0000

On 12/12/2012, at 12:01 PM, Barry Leiba <barryleiba@computer.org> wrote:
>=20
> I understand that this will change implementations -- patches that
> used to use "add" will now have to use "replace", and there's now no
> way to do "add this if it's not already there, and replace it if it is
> already there".

That was a very desirable feature for many people in the WG.

Personally -- to me, it seems like you're getting hung up on the word =
"add." We've had a few bits of feedback, where people try to map a =
particular meaning of one of the operation names to a programming =
language or other system. In this format, "add" means what the format =
definition says it means, because otherwise we have to rationalise all =
of the different systems people might use it with to make sense.

That said, if changing the operation name would make things easier, I'd =
be OK with that; e.g., "set." However, I suspect doing so would just =
raise issues from other people who are used to having "set" mean =
something slightly different.


> Perhaps there's a need to add something with those
> semantics.  On the other hand, as the text stands now, there's no way
> to do "add this only if it's not already there", because "test" can't
> test for existence.


We discussed having a test for existence in the WG, but there was =
agreement that it wasn't important enough to justify the added =
complexity. YMMV, of course.

Cheers,


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




From barryleiba.mailing.lists@gmail.com  Tue Dec 11 20:25:19 2012
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 7C11521F8675; Tue, 11 Dec 2012 20:25:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.077
X-Spam-Level: 
X-Spam-Status: No, score=-103.077 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Izz8ihkdCaVS; Tue, 11 Dec 2012 20:25:18 -0800 (PST)
Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by ietfa.amsl.com (Postfix) with ESMTP id 7F3A021F869E; Tue, 11 Dec 2012 20:25:17 -0800 (PST)
Received: by mail-lb0-f173.google.com with SMTP id c1so216116lbg.18 for <multiple recipients>; Tue, 11 Dec 2012 20:25:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=CzI6CZAfnJ2XoKhPW+I4ip0b3qNUNO0jGQTf/Kpz7KM=; b=hK3UOfGUN29LXoGMfJDGj3BfmLNCeXKC9aJrnCmOrakd/RbH8DtHqq7Qe211+rEwjd 9y8bJa7iBSPmjRCyHD4DrK/3aq5YYALLH40Cx0F89nNHNNxPP/9xIikImn9u34MGq0TG Z+R7IbtFSeO7kYvia5Ga97V4VzZX6+8IjM8YypMsEgAfAR4F0E0aOPzk5ElJCd4vb6kA t0jatRaG6LyRMrYoVGsFnaqctK3Z3oaXr4AtsUGqbtx1o44TWKL0yNYhdpqMSI5N3uPw 0PcG9eWdbwM1Mnh2tnAiaQ3f2jkAfxTwn0FeEJHZn53yx1h7tcnR+09pNyB0Ea7oHr06 hh+w==
MIME-Version: 1.0
Received: by 10.152.112.36 with SMTP id in4mr5880lab.35.1355286316205; Tue, 11 Dec 2012 20:25:16 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Tue, 11 Dec 2012 20:25:15 -0800 (PST)
In-Reply-To: <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net>
Date: Tue, 11 Dec 2012 23:25:15 -0500
X-Google-Sender-Auth: D4A9R_iy92eFRV18Ki8Z_C9WKik
Message-ID: <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 04:25:19 -0000

> Personally -- to me, it seems like you're getting hung up on the word "add."
...
> "add" means what the format definition says it means, because otherwise
> we have to rationalise all of the different systems people might use it with
> to make sense.

OK, I'll buy that.  Then let's take a different approach, and make it
clearer that it's Humpty Dumpty's version of "add", so maybe neither I
nor Alice will get hung up on it:

OLD
   The "add" operation adds a new value at the target location. The
   operation object MUST contain a "value" member that specifies the
   value to be added.
NEW
   The "add" operation performs the following function, depending upon
   what the target location references (see details below):

   o  If the target location specifies an array index, a new value is
      inserted into the array at the specified index.

   o  If the target location specifies an object member that does not
      already exist, a new member is added to the object.

   o  If the target location specifies an object member that does
      exist, that member's value is replaced.
END

That may be wordier than we need, but I think it makes the point...
feel free to wordsmith.  With something like that, I think we can say
that we had to pick a name, "add" was picked, and it means exactly
what we choose it to mean - neither more nor less.  And that's glory
for you.

Barry

From jasnell@gmail.com  Tue Dec 11 09:22:45 2012
Return-Path: <jasnell@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 82B5A21F84CD; Tue, 11 Dec 2012 09:22:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.834
X-Spam-Level: 
X-Spam-Status: No, score=-3.834 tagged_above=-999 required=5 tests=[AWL=-0.236, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eP35wJcQMseR; Tue, 11 Dec 2012 09:22:43 -0800 (PST)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7D42B21F84CA; Tue, 11 Dec 2012 09:22:38 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id qd14so12938194ieb.6 for <multiple recipients>; Tue, 11 Dec 2012 09:22:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=55steGPZ4XVOvlwQHjlGVsQWc408AgC8tnGDfyBdyf0=; b=Lc8bBBS8eV/p/FKdzm5MzLpTmwz41P+v6RQhufw0Am0cO/c/7y5l/8zM4tYojP/9wZ SVMajKW14I2TX7jvmZ2cRA2EDBJMXkiZRlIDqqbkkDdGgxt1eNxUEhwecCPGUt0H/5Gn rKvoohb1mJz0/Kj5eCf5NueVZlkz3fXsY4RDA/wYpy1d3E8Y/Te2+Uk7zlnfDhgQ9Lmt 0sEEN3ZajFRdxPb7ekucQltYBSEIxPBmxarwHzcx4EG2IFQQY9IgydDyOSV0fe5xKt+d pLNL0ZGAQAHLcQRunCb87mpDceQr/SR055qGMscG0ahyc07h9KPeJEHwUh6orgdNhpdg PKIQ==
Received: by 10.50.151.165 with SMTP id ur5mr3032978igb.24.1355246554595; Tue, 11 Dec 2012 09:22:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Tue, 11 Dec 2012 09:22:14 -0800 (PST)
In-Reply-To: <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Tue, 11 Dec 2012 09:22:14 -0800
Message-ID: <CABP7RbfnfMxEUna=snZHHhFkgorxCM+uTXL69RMriyLo-A6qig@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=e89a8f23541d78414c04d096ed35
X-Mailman-Approved-At: Wed, 12 Dec 2012 10:26:48 -0800
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 17:22:45 -0000

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

You are reading it correctly. Note also that the very next bullet point
says:

  A member to add to an existing object - whereupon the supplied
  value is added to that object at the indicated location.  If the
  member already exists, it is replaced by the specified value.

So an "add" is really a "replace" that does not have the "target location
MUST exist" restriction. Personally, I'm not too fond of that decision. For
anything other than an array, "add" should fail if the target already
exists. For arrays, "add" should insert but never replace an existing
value.

- James


On Tue, Dec 11, 2012 at 7:25 AM, Barry Leiba <barryleiba@computer.org>wrote:

> > Abstract
> >    JSON Patch defines the media type "application/json-patch", a JSON
> >    document structure for expressing a sequence of operations to apply
> >    to a JSON document, suitable for use with the HTTP PATCH method.
> ...
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/
>
> I've reviewed JSON Patch and JSON Pointer as responsible AD, and am
> very happy with the documents -- this is good work, well written.  I
> came up with one issue that I want to discuss as part of last call:
>
>    4.1.  add
>
>    The "add" operation adds a new value at the target location.  The
>    operation object MUST contain a "value" member that specifies the
>    value to be added.
>
>    For example:
>
>    { "op": "add", "path": "/a/b/c", "value": [ "foo", "bar" ] }
>
>    When the operation is applied, the target location MUST reference one
>    of:
>
>    o  The root of the target document - whereupon the specified value
>       becomes the entire content of the target document.
>
> Now, what this means is that if we start with this:
>
> { "a": { "num": 1 } }
>
> and we apply this:
>
> { "op": "add", "path": "", "value": [ "foo", "bar" ] }
>
> we end up with this:
>
> [ "foo", "bar" ]
>
> This doesn't strike me as having any sense of an "add" operation -- it
> appears to be a special case that doesn't fit.  In any other
> situation, using any other path, the operation either adds something
> to what's already there, or it fails.  But when the path is "", it's
> anomalous.
>
> So, three questions:
>
> 1. Do I have this right, or am I mistaken about the result of that
> operation?
>
> 2. Assuming I have it right, can someone explain why it's this way?
>
> 3. Can someone explain why this is the right way to specify it, rather
> than using "replace" for this?
>
> Barry
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

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

<font face=3D"courier new,monospace">You are reading it correctly. Note als=
o that the very next bullet point says:=C2=A0</font><div><font face=3D"cour=
ier new,monospace"><br></font></div><div><font face=3D"courier new,monospac=
e"><div>

=C2=A0 A member to add to an existing object - whereupon the supplied</div>=
<div>=C2=A0 value is added to that object at the indicated location. =C2=A0=
If the</div><div>=C2=A0 member already exists, it is replaced by the specif=
ied value.</div>

<div><br></div><div>So an &quot;add&quot; is really a &quot;replace&quot; t=
hat does not have the &quot;target location MUST exist&quot; restriction. P=
ersonally, I&#39;m not too fond of that decision. For anything other than a=
n array, &quot;add&quot; should fail if the target already exists. For arra=
ys, &quot;add&quot; should insert but never replace an existing value.=C2=
=A0</div>

<div><br></div><div>- James</div></font></div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Tue, Dec 11, 2012 at 7:25 AM, Barry Lei=
ba <span dir=3D"ltr">&lt;<a href=3D"mailto:barryleiba@computer.org" target=
=3D"_blank">barryleiba@computer.org</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">&gt; Abstract<br>
&gt; =C2=A0 =C2=A0JSON Patch defines the media type &quot;application/json-=
patch&quot;, a JSON<br>
&gt; =C2=A0 =C2=A0document structure for expressing a sequence of operation=
s to apply<br>
&gt; =C2=A0 =C2=A0to a JSON document, suitable for use with the HTTP PATCH =
method.<br>
</div>...<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pat=
ch/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-appsawg-j=
son-patch/</a><br>
<br>
I&#39;ve reviewed JSON Patch and JSON Pointer as responsible AD, and am<br>
very happy with the documents -- this is good work, well written. =C2=A0I<b=
r>
came up with one issue that I want to discuss as part of last call:<br>
<br>
=C2=A0 =C2=A04.1. =C2=A0add<br>
<br>
=C2=A0 =C2=A0The &quot;add&quot; operation adds a new value at the target l=
ocation. =C2=A0The<br>
=C2=A0 =C2=A0operation object MUST contain a &quot;value&quot; member that =
specifies the<br>
=C2=A0 =C2=A0value to be added.<br>
<br>
=C2=A0 =C2=A0For example:<br>
<br>
=C2=A0 =C2=A0{ &quot;op&quot;: &quot;add&quot;, &quot;path&quot;: &quot;/a/=
b/c&quot;, &quot;value&quot;: [ &quot;foo&quot;, &quot;bar&quot; ] }<br>
<br>
=C2=A0 =C2=A0When the operation is applied, the target location MUST refere=
nce one<br>
=C2=A0 =C2=A0of:<br>
<br>
=C2=A0 =C2=A0o =C2=A0The root of the target document - whereupon the specif=
ied value<br>
=C2=A0 =C2=A0 =C2=A0 becomes the entire content of the target document.<br>
<br>
Now, what this means is that if we start with this:<br>
<br>
{ &quot;a&quot;: { &quot;num&quot;: 1 } }<br>
<br>
and we apply this:<br>
<br>
{ &quot;op&quot;: &quot;add&quot;, &quot;path&quot;: &quot;&quot;, &quot;va=
lue&quot;: [ &quot;foo&quot;, &quot;bar&quot; ] }<br>
<br>
we end up with this:<br>
<br>
[ &quot;foo&quot;, &quot;bar&quot; ]<br>
<br>
This doesn&#39;t strike me as having any sense of an &quot;add&quot; operat=
ion -- it<br>
appears to be a special case that doesn&#39;t fit. =C2=A0In any other<br>
situation, using any other path, the operation either adds something<br>
to what&#39;s already there, or it fails. =C2=A0But when the path is &quot;=
&quot;, it&#39;s<br>
anomalous.<br>
<br>
So, three questions:<br>
<br>
1. Do I have this right, or am I mistaken about the result of that operatio=
n?<br>
<br>
2. Assuming I have it right, can someone explain why it&#39;s this way?<br>
<br>
3. Can someone explain why this is the right way to specify it, rather<br>
than using &quot;replace&quot; for this?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Barry<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
__________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div></div></blockquote></div><br></div>

--e89a8f23541d78414c04d096ed35--

From pbryan@anode.ca  Tue Dec 11 09:41:43 2012
Return-Path: <pbryan@anode.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 169DF21F885D; Tue, 11 Dec 2012 09:41:43 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jjUylC-gNjwW; Tue, 11 Dec 2012 09:41:42 -0800 (PST)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id 4F49B21F8816; Tue, 11 Dec 2012 09:41:42 -0800 (PST)
Received: from [10.126.22.61] (nat-204-14-239-210-sfo.net.salesforce.com [204.14.239.210]) by maple.anode.ca (Postfix) with ESMTPSA id 7D1C46450; Tue, 11 Dec 2012 17:41:41 +0000 (UTC)
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: "Paul C. Bryan" <pbryan@anode.ca>
To: James M Snell <jasnell@gmail.com>
In-Reply-To: <CABP7RbfnfMxEUna=snZHHhFkgorxCM+uTXL69RMriyLo-A6qig@mail.gmail.com>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <CABP7RbfnfMxEUna=snZHHhFkgorxCM+uTXL69RMriyLo-A6qig@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-Qp5FcYlekSffU306EFPn"
Date: Tue, 11 Dec 2012 09:41:40 -0800
Message-ID: <1355247700.17722.59.camel@pbryan-wsl.internal.salesforce.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
X-Mailman-Approved-At: Wed, 12 Dec 2012 10:26:48 -0800
Cc: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Dec 2012 17:41:43 -0000

--=-Qp5FcYlekSffU306EFPn
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

I'm not fond of that decision either.

Paul

On Tue, 2012-12-11 at 09:22 -0800, James M Snell wrote:

> You are reading it correctly. Note also that the very next bullet
> point says: 
> 
> 
> 
>   A member to add to an existing object - whereupon the supplied
>   value is added to that object at the indicated location.  If the
>   member already exists, it is replaced by the specified value.
> 
> 
> So an "add" is really a "replace" that does not have the "target
> location MUST exist" restriction. Personally, I'm not too fond of that
> decision. For anything other than an array, "add" should fail if the
> target already exists. For arrays, "add" should insert but never
> replace an existing value. 
> 
> 
> - James
> 
> 
> 
> On Tue, Dec 11, 2012 at 7:25 AM, Barry Leiba <barryleiba@computer.org>
> wrote:
> 
>         > Abstract
>         >    JSON Patch defines the media type
>         "application/json-patch", a JSON
>         >    document structure for expressing a sequence of
>         operations to apply
>         >    to a JSON document, suitable for use with the HTTP PATCH
>         method.
>         
>         
>         ...
>         >
>         http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/
>         
>         I've reviewed JSON Patch and JSON Pointer as responsible AD,
>         and am
>         very happy with the documents -- this is good work, well
>         written.  I
>         came up with one issue that I want to discuss as part of last
>         call:
>         
>            4.1.  add
>         
>            The "add" operation adds a new value at the target
>         location.  The
>            operation object MUST contain a "value" member that
>         specifies the
>            value to be added.
>         
>            For example:
>         
>            { "op": "add", "path": "/a/b/c", "value": [ "foo",
>         "bar" ] }
>         
>            When the operation is applied, the target location MUST
>         reference one
>            of:
>         
>            o  The root of the target document - whereupon the
>         specified value
>               becomes the entire content of the target document.
>         
>         Now, what this means is that if we start with this:
>         
>         { "a": { "num": 1 } }
>         
>         and we apply this:
>         
>         { "op": "add", "path": "", "value": [ "foo", "bar" ] }
>         
>         we end up with this:
>         
>         [ "foo", "bar" ]
>         
>         This doesn't strike me as having any sense of an "add"
>         operation -- it
>         appears to be a special case that doesn't fit.  In any other
>         situation, using any other path, the operation either adds
>         something
>         to what's already there, or it fails.  But when the path is
>         "", it's
>         anomalous.
>         
>         So, three questions:
>         
>         1. Do I have this right, or am I mistaken about the result of
>         that operation?
>         
>         2. Assuming I have it right, can someone explain why it's this
>         way?
>         
>         3. Can someone explain why this is the right way to specify
>         it, rather
>         than using "replace" for this?
>         
>         Barry
>         
>         _______________________________________________
>         apps-discuss mailing list
>         apps-discuss@ietf.org
>         https://www.ietf.org/mailman/listinfo/apps-discuss
>         
> 
> 
> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss



--=-Qp5FcYlekSffU306EFPn
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
I'm not fond of that decision either.<BR>
<BR>
Paul<BR>
<BR>
On Tue, 2012-12-11 at 09:22 -0800, James M Snell wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
    You are reading it correctly. Note also that the very next bullet point says:&nbsp;
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    &nbsp; A member to add to an existing object - whereupon the supplied
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    &nbsp; value is added to that object at the indicated location. &nbsp;If the
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    &nbsp; member already exists, it is replaced by the specified value.
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    So an &quot;add&quot; is really a &quot;replace&quot; that does not have the &quot;target location MUST exist&quot; restriction. Personally, I'm not too fond of that decision. For anything other than an array, &quot;add&quot; should fail if the target already exists. For arrays, &quot;add&quot; should insert but never replace an existing value.&nbsp;
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    - James
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    On Tue, Dec 11, 2012 at 7:25 AM, Barry Leiba &lt;<A HREF="mailto:barryleiba@computer.org">barryleiba@computer.org</A>&gt; wrote:
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        &gt; Abstract<BR>
        &gt; &nbsp; &nbsp;JSON Patch defines the media type &quot;application/json-patch&quot;, a JSON<BR>
        &gt; &nbsp; &nbsp;document structure for expressing a sequence of operations to apply<BR>
        &gt; &nbsp; &nbsp;to a JSON document, suitable for use with the HTTP PATCH method.<BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        ...<BR>
        &gt; <A HREF="http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/">http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-patch/</A><BR>
        <BR>
        I've reviewed JSON Patch and JSON Pointer as responsible AD, and am<BR>
        very happy with the documents -- this is good work, well written. &nbsp;I<BR>
        came up with one issue that I want to discuss as part of last call:<BR>
        <BR>
        &nbsp; &nbsp;4.1. &nbsp;add<BR>
        <BR>
        &nbsp; &nbsp;The &quot;add&quot; operation adds a new value at the target location. &nbsp;The<BR>
        &nbsp; &nbsp;operation object MUST contain a &quot;value&quot; member that specifies the<BR>
        &nbsp; &nbsp;value to be added.<BR>
        <BR>
        &nbsp; &nbsp;For example:<BR>
        <BR>
        &nbsp; &nbsp;{ &quot;op&quot;: &quot;add&quot;, &quot;path&quot;: &quot;/a/b/c&quot;, &quot;value&quot;: [ &quot;foo&quot;, &quot;bar&quot; ] }<BR>
        <BR>
        &nbsp; &nbsp;When the operation is applied, the target location MUST reference one<BR>
        &nbsp; &nbsp;of:<BR>
        <BR>
        &nbsp; &nbsp;o &nbsp;The root of the target document - whereupon the specified value<BR>
        &nbsp; &nbsp; &nbsp; becomes the entire content of the target document.<BR>
        <BR>
        Now, what this means is that if we start with this:<BR>
        <BR>
        { &quot;a&quot;: { &quot;num&quot;: 1 } }<BR>
        <BR>
        and we apply this:<BR>
        <BR>
        { &quot;op&quot;: &quot;add&quot;, &quot;path&quot;: &quot;&quot;, &quot;value&quot;: [ &quot;foo&quot;, &quot;bar&quot; ] }<BR>
        <BR>
        we end up with this:<BR>
        <BR>
        [ &quot;foo&quot;, &quot;bar&quot; ]<BR>
        <BR>
        This doesn't strike me as having any sense of an &quot;add&quot; operation -- it<BR>
        appears to be a special case that doesn't fit. &nbsp;In any other<BR>
        situation, using any other path, the operation either adds something<BR>
        to what's already there, or it fails. &nbsp;But when the path is &quot;&quot;, it's<BR>
        anomalous.<BR>
        <BR>
        So, three questions:<BR>
        <BR>
        1. Do I have this right, or am I mistaken about the result of that operation?<BR>
        <BR>
        2. Assuming I have it right, can someone explain why it's this way?<BR>
        <BR>
        3. Can someone explain why this is the right way to specify it, rather<BR>
        than using &quot;replace&quot; for this?<BR>
        <BR>
        <FONT COLOR="#888888">Barry</FONT>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BLOCKQUOTE>
        _______________________________________________<BR>
        apps-discuss mailing list<BR>
        <A HREF="mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</A><BR>
        <A HREF="https://www.ietf.org/mailman/listinfo/apps-discuss">https://www.ietf.org/mailman/listinfo/apps-discuss</A><BR>
        <BR>
    </BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
    <BR>
    <BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<PRE>
_______________________________________________
apps-discuss mailing list
<A HREF="mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</A>
<A HREF="https://www.ietf.org/mailman/listinfo/apps-discuss">https://www.ietf.org/mailman/listinfo/apps-discuss</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-Qp5FcYlekSffU306EFPn--


From windy_1@skyhighway.com  Tue Dec 11 16:43:46 2012
Return-Path: <windy_1@skyhighway.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1053E11E80AE; Tue, 11 Dec 2012 16:43:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.537
X-Spam-Level: 
X-Spam-Status: No, score=-0.537 tagged_above=-999 required=5 tests=[AWL=0.604,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WyYB26L8Lb1R; Tue, 11 Dec 2012 16:43:45 -0800 (PST)
Received: from skyhighway.com (skyhighway.com [63.249.82.6]) by ietfa.amsl.com (Postfix) with ESMTP id A008711E80A3; Tue, 11 Dec 2012 16:43:45 -0800 (PST)
Received: from Firefly.skyhighway.com (dsl-63-249-88-160.static.cruzio.com [63.249.88.160]) by skyhighway.com with ESMTP id qBC0hjW7067663; Tue, 11 Dec 2012 16:43:45 -0800 (PST)
Message-Id: <201212120043.qBC0hjW7067663@skyhighway.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 11 Dec 2012 16:43:58 -0800
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>, trill@ietf.org
From: gayle noble <windy_1@skyhighway.com>
Subject: Re: [trill] Last Call: <draft-ietf-trill-oam-req-04.txt> (Requirements for	Operations, Administration and Maintenance (OAM) in TRILL (Transparent	Interconnection of Lots of Links)) to Informational RFC
In-Reply-To: <20121211145829.3754.44253.idtracker@ietfa.amsl.com>
References: <20121211145829.3754.44253.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
X-Mailman-Approved-At: Wed, 12 Dec 2012 10:26:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 00:43:46 -0000

<html>
<body>
Very well written!! No spelling errors! No grammatical errors! Only one
sentence, in my opinion,&nbsp; could be rephrased for clarity <br>
4.1. Data Plane<br>
&nbsp;RBridges MUST have the ability to identify OAM frames destined for
them or which require processing by the OAM plane from normal data
frames.<br>
<font color="#00FF00">[Might be clearer if it was [RBridges MUST have the
ability to identify OAM frames from normal data frames when the OAM
frames are destined for them or require processing by the OAM plane.]]
<br><br>
</font>gayle</body>
</html>


From rwfranks@gmail.com  Tue Dec 11 17:54:13 2012
Return-Path: <rwfranks@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 951FD21E80C0; Tue, 11 Dec 2012 17:54:13 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ka2IlbTa7a0b; Tue, 11 Dec 2012 17:54:07 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4202E21E8096; Tue, 11 Dec 2012 17:54:07 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so48299wey.3 for <multiple recipients>; Tue, 11 Dec 2012 17:54:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=K0gabIB8Tz+PptTlys9WmbJN+/emkz5j1ihif1L8zYI=; b=E+px4Iu7WOApHgbg4ekhZi1XUf3LMpTfiLtNL/o/G8a3+1g7t+mX2qjZ5fET9jOCuy +4LQH9j+1vDi+EmTrxNgKOSLQFfjXhEwesUL7el6EVBqeAjqkQJ2hvW6N3E9fqnzRWhD WmNV/VCZaVYxzU3mGFZU1VgJnHDZHtI4Am6Sp8KHhVXN8XUPu5pKwpjcOtGbQEuhHgJ2 yE82DotT4zpFnoRfs0RqAGe7ENapOoCmo5rL8wnwClf3FymZI3o2Ch5qg1cQcmm4Sv65 HHNzJDVzrxPBLkd1v3OXWt+XygztGw7edu23bHopK9vmp79mmNtRK57qnQ6YdSuLp6pK BSXQ==
Received: by 10.180.73.80 with SMTP id j16mr243283wiv.5.1355277246289; Tue, 11 Dec 2012 17:54:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.18.65 with HTTP; Tue, 11 Dec 2012 17:53:45 -0800 (PST)
In-Reply-To: <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net>
From: Dick Franks <rwfranks@gmail.com>
Date: Wed, 12 Dec 2012 01:53:45 +0000
Message-ID: <CAKW6Ri4T2BmOsuYriWq_hGkfQ-mf+92Gfhu5mKM5i21CUqWfjQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 12 Dec 2012 10:26:48 -0800
Cc: Mark Nottingham <mnot@mnot.net>, Barry Leiba <barryleiba@computer.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Dec 2012 01:54:13 -0000

On 12 December 2012 01:14, Mark Nottingham <mnot@mnot.net> wrote:
[snip]

>
> Personally -- to me, it seems like you're getting hung up on the word "ad=
d." We've had a few bits of feedback, where people try to map a particular =
meaning of one of the operation names to a programming language or other sy=
stem. In this format, "add" means what the format definition says it means,=
 because otherwise we have to rationalise all of the different systems peop=
le might use it with to make sense.
>



"When I use a word", Humpty Dumpty said, in rather a scornful tone,
"it means what I choose it to mean - neither more nor less."

Lewis Carroll. Through the Looking Glass. 1872.

From peter@akayla.com  Tue Dec 11 21:46:23 2012
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 EAF1D21F8617; Tue, 11 Dec 2012 21:46:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzQ1eOKk6GSd; Tue, 11 Dec 2012 21:46:18 -0800 (PST)
Received: from p3plsmtpa09-08.prod.phx3.secureserver.net (p3plsmtpa09-08.prod.phx3.secureserver.net [173.201.193.237]) by ietfa.amsl.com (Postfix) with ESMTP id 65A1221F886B; Tue, 11 Dec 2012 21:45:59 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-08.prod.phx3.secureserver.net with  id aVlQ1k0011huGat01VlQyp; Tue, 11 Dec 2012 22:45:24 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-avt-rtp-evrc-nw.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-avt-rtp-evrc-nw-08
Date: Tue, 11 Dec 2012 21:45:23 -0800
Message-ID: <002a01cdd82b$e1a913c0$a4fb3b40$@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: Ac3YJzTUtnrb4hGMSyOFNd5zviBrVQ==
Content-Language: en-us
X-Mailman-Approved-At: Wed, 12 Dec 2012 10:26:48 -0800
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: Wed, 12 Dec 2012 05:46: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>.

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

Document: draft-ietf-avt-rtp-evrc-nw-08
Reviewer: Peter Yee
Review Date: Dec-11-2012
IETF LC End Date: Dec-11-2012
IESG Telechat date: Unknown

Summary: This draft is basically ready for publication, but has a few nits
that should be fixed before publication. [Ready with nits.]

This Standards Track draft specifies RTP payload formats for use with the
EVRC-NW.  It contains IANA registration requests.

Major issues:

Minor issues:

Nits/editorial comments:

Section 1, 2nd sentence: decide whether you want to capitalize the packet
format names (Header-Free, Interleaved/Bundled) and then them use
consistently throughout the document.  RFC 3558 uses upper case names
mostly, but is not quite a paragon of consistency.

Section 4, 3rd sentence: change "zero bit" to "zero-bit".

Section 4, table, 1st row: insert a space after "Blank"  and adjust spacing
to maintain alignment of the columns.  Change "0 bit" to "0 bits".

Section 5, 2nd paragraph, 3rd sentence: change "8kHz" to "8 kHz".  Change
"16kHz" to "16 kHz".

Section 6, 3rd numbered item, 2nd sentence: change "identfication" to
"identification".

Section 7, 1st sentence: change ";" to ",".

Section 9.1.2: change "Interoperability considertaions" to "Interoperability
considerations".

Section 9.1.3, mode-set-recv paragraph, 5th sentence: change "narroband" to
"narrowband".

Section 9.1.3: change " Interoperability considertaions" to "
Interoperability considerations".

Section 10, 1st paragraph, 2nd sentence: delete the comma after
"preference".

Section 10, numbered list: I'm not sure why this is a numbered list since
the preceding paragraph makes no direct link to it.  Consider demoting the
list items to individual paragraphs.

Section 10, 1st numbered item, 1st sentence: consider rewriting "inform the
capability of " as "advertise the capability for" or "inform the capability
for". 

Section 10, 2nd numbered item, 1st sentence: rewrite "inform the" as
"indicate a".

Section 11, 2nd paragraph, 4th sentence: change "potentially-high" to
"potentially high"

Section 11, 2nd paragraph, last sentence: change "is used" to "be used".

Section 14, 2nd bullet item, 2nd sentence: capitalize "may" and "should".

Section 14, 3rd bullet item: change "receive only" to "receive-only".

I like using the serial comma (the one before "and" in a list of 3 of more
items) for clarity and to reduce confusion, but did not submit the list of
missing commas for this document -- there are a few.  Let me know if you
care.





From yaronf.ietf@gmail.com  Wed Dec 12 11:31:10 2012
Return-Path: <yaronf.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 369C721E810D for <ietf@ietfa.amsl.com>; Wed, 12 Dec 2012 11:31:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZx5F-A-4jgX for <ietf@ietfa.amsl.com>; Wed, 12 Dec 2012 11:31:09 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 192DA21E80FD for <ietf@ietf.org>; Wed, 12 Dec 2012 11:31:08 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so597338bku.31 for <ietf@ietf.org>; Wed, 12 Dec 2012 11:31:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=84MyTsgc+4RqvBULPrxHxnEkpAUtFADcLhL3J9z33Wo=; b=lqM4MRjEVuiM92bYYU4zqIjZBJ/dqhMq17FHhbKSsVI8ANHQP9AT/ynpeCm9UZlmZJ a0Y3h1AKZSTRxjY0fWfHOiERTRMC6Q4vuq8KbENONrSgF/2L6K04DccPuDd2rhSW4THB ID34RKR2LBp/OfOptQpwvCMDsK9ufhmq5xRMIdBgv/tDzm+anApnF4Mg1yyxI28LKWue Gy6lnM0klpXgwqY/QXr2IlgbwaSyrgXbvhIfzg8Wf3kjQpZJ0tUff2oNgxoMya96atwo 9WxC3P1Z7anEFVYSzzZ5m3obkcOPM0DbtNAys5rpXhY+awLB8VX0c+e9fpa/8XU+gPDy vA0w==
Received: by 10.204.11.208 with SMTP id u16mr1127366bku.81.1355340667956; Wed, 12 Dec 2012 11:31:07 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id o7sm21531896bkv.13.2012.12.12.11.31.05 (version=SSLv3 cipher=OTHER); Wed, 12 Dec 2012 11:31:06 -0800 (PST)
Message-ID: <50C8DB78.3080905@gmail.com>
Date: Wed, 12 Dec 2012 21:31:04 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Running code, take 2
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, 12 Dec 2012 19:31:10 -0000

Hi,

I have just published a draft that proposes an alternative to Stephen's 
"fast track". My proposal simply allows authors to document, in a 
semi-standard way, whatever implementations exist for their protocol, as 
well as their interoperability.

http://www.ietf.org/id/draft-sheffer-running-code-00.txt

I believe this can achieve the same goal, which is to apply preferred 
treatment to protocols that have been implemented, and with a lot less 
process overhead. It also leaves much more leeway for individual working 
groups to apply their own procedures and customs.

Similarly to Stephen's proposal, we can use a process experiment (per 
RFC 3933) to gauge the effectiveness of this one.

I am looking forward to comments and discussion on this list.

     Yaron

From touch@isi.edu  Wed Dec 12 14:32:25 2012
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 8171421F8A70 for <ietf@ietfa.amsl.com>; Wed, 12 Dec 2012 14:32:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.785
X-Spam-Level: 
X-Spam-Status: No, score=-101.785 tagged_above=-999 required=5 tests=[AWL=-1.786, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yccy7nu3cmyI for <ietf@ietfa.amsl.com>; Wed, 12 Dec 2012 14:32:24 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id B1F3821F8A6C for <ietf@ietf.org>; Wed, 12 Dec 2012 14:32:24 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id qBCMWCkp016079 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Dec 2012 14:32:12 -0800 (PST)
Message-ID: <50C905EC.2070700@isi.edu>
Date: Wed, 12 Dec 2012 14:32:12 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: call for papers - IEEE "From Research to Standards" workshop
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@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, 12 Dec 2012 22:32:25 -0000

Hi, all,

I'm helping disseminate the following CFP for a "research to standards" 
workshop at IEEE ICC 2013 in Budapest, Hungary. This meeting is directly 
soliciting the participation of various standards community members, 
including the IETF and IRTF.

Last year I spoke on a panel contrasting the IEEE, ITU, and IETF/IRTF.

I hope this might be of interest to some people on this list, and 
encourage you to consider submitting a paper on your experiences.

If you have any questions on this, please let me know.

Thanks, and apologies for any diversion,

Joe

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


                 CALL FOR PAPERS
        2nd IEEE Workshop On Telecommunications Standards
               “From Research to Standards”

            June 9-13, 2013, Budapest, Hungary
              Co-located with IEEE ICC 2013

                    http://www.research2standards.net/

Paper abstract deadline Jan 4, 2013
Paper submission deadline Jan 11, 2013

Building on the success of the first edition of the IEEE Workshop on
Telecommunications Standards: "From Research to Standards" (which won
the Best IEEE ComSoc Workshop Award at IEEE ICC 2012), we are happy to
announce the organization of its second edition in Budapest, Hungary,
collocated with IEEE ICC 2013.

The goal of this Workshop is to bridge the gap between researchers,
scientists, and standards experts in both academia and industry and to
promote standardization as an important vehicle for information sharing
and cooperation between academia and industry. An additional goal is to
   bring together experts from different standardization bodies,
providing opportunities for closer understanding and collaboration;
catalyzing development of more interoperable standards and more
efficient and effective communication systems.

The Workshop technical program will deliver high quality technical as
well as visionary papers that will be reviewed and selected by an
international program committee representing both academia and industry
with a strong standardization background. All submissions are required
to comply with ICC’s guidelines. Accepted papers will appear in IEEE
Xplore.

Looking forward your submissions to the 2nd IEEE Workshop on
Telecommunications Standards: "From Research to Standards".

Kind regards,

Workshop Official Website: http://www.research2standards.net

Workshop General Chair
• Dr. Tarik Taleb, NEC Europe, Germany
TPC co-Chairs
• Dr. Tuncer Baykas, Tohoku University, Japan
• Dr. Alex Reznik, InterDigital, USA
• Dr. Konstantinos Samdanis , NEC Europe, Germany
Publicity co-chairs
• Prof. Joe Touch, Univ. of Southern California, USA
• Dr. Periklis Chatzimisios, Alexander TEI of Thessaloniki, Greece

IMPORTANT DATES
PAPER REGISTRATION: Jan. 04, 2013 SUBMISSION DEADLINE: Jan. 11, 2013
ACCEPTANCE NOTIFICATION: Feb. 22, 2013 FINAL MANUSCRIPT: Mar. 08, 2013

From randy@qti.qualcomm.com  Wed Dec 12 21:33:18 2012
Return-Path: <randy@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 44D5A21E80A0 for <ietf@ietfa.amsl.com>; Wed, 12 Dec 2012 21:33:18 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJ8ASNHJfj+a for <ietf@ietfa.amsl.com>; Wed, 12 Dec 2012 21:33:17 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id CC9571F0CB1 for <ietf@ietf.org>; Wed, 12 Dec 2012 21:33:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1355375791; x=1386911791; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=dtiX5hlulEC9dlllcTgYP6XR4b/Jr4O81rkUk8qNDYc=; b=FlIFgG8k3XzUKla1uExHSfJU647l7Tb9odz8CKt9zz51pprNOaQngtC6 LhAt2rGCvRQQeTYKyuOZ+2D/pV6bKTEVoMmI9l8KU/sRGU6OvzJFNkeOy Hly/2H9cc5WYqva2vyXjFRjuRSztof99WJ46RJRaBW7XBuySvS0NWSH65 0=;
X-IronPort-AV: E=Sophos;i="4.84,272,1355126400"; d="scan'208";a="11755000"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 12 Dec 2012 21:16:30 -0800
X-IronPort-AV: E=Sophos;i="4.84,272,1355126400"; d="scan'208";a="384621865"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Dec 2012 21:33:15 -0800
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 12 Dec 2012 21:33:15 -0800
Message-ID: <p0624060ccceefc2905c0@[99.111.97.136]>
In-Reply-To: <50BB9FE6.5000000@network-heretics.com>
References: <CAC4RtVCogYS4tmY1LLi0C-E+B+di2_wTD0N-=AZrVR7-A8Mz+A@mail.gmail.com> <6.2.5.6.2.20121128023905.0afdcde0@resistor.net> <50B683C4.2030503@stpeter.im>	<50B68612.7080107@dcrocker.net> <50B693ED.7000609@stpeter.im>	<50B696B0.30904@qti.qualcomm.com> <CAC4RtVAG+pKSQMwPyB6GJ7jxJM4hNpU81Yt8he6ZsEMrg_rTbQ@mail.gmail.com> <00c001cdce7a$d9fa6490$8def2db0$@asgard.org> <50B7EA5D.2030803@qti.qualcomm.com> <50BA18B8.3090306@network-heretics.com> <p06240609cce032de76ff@dhcp184-48-45-14.hroa.orl.wayport.net> <m2obidvuv7.wl%randy@psg.com> <p0624060ccce0b42ffc47@dhcp184-48-45-14.hroa.orl.wayport.net> <50BB10FF.6090105@gmail.com> <50BB5A69.40107@network-heretics.com> <17CDABC9DDB6E00CE9A36B15@JcK-HP8200.jck.com> <50BB6B61.4040304@network-heretics.com> <3717C2CC54EB3B1A8E3E8EEA@JcK-HP8200.jck.com> <50BB6FC8.8040907@network-heretics.com> <50BB8DA8.5070406@joelhalpern.com> <AEDAFA38A99E8B0E926BAC0F@JcK-HP8200.jck. com> <50BB96C4.2080908@network-heretics.com>	<50BB98B0.2060100@gmail.com> <50BB9FE6.5000000@network-heretics.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 12 Dec 2012 21:32:00 -0800
To: Keith Moore <moore@network-heretics.com>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Presentation vs. Discussion sessions (was: PowerPoint considered 	harmful)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 05:33:18 -0000

At 1:37 PM -0500 12/2/12, Keith Moore wrote:

>  On 12/02/2012 01:06 PM, Melinda Shore wrote:
>>  There's a whole nexus of connected issues here, I think, and what
>>  a given person complains about depends on that person's pet peeves.
>>  It seems to me that if we were better about moving work forward
>>  between meetings (<- peeve!) meeting time wouldn't be chewed up
>>  with presenting the current state of the work.
>  While I fully agree that most WGs could be better at moving work 
> forward between meetings, I don't think it would solve the problem 
> of face to face meeting time being filled up with presentations.
>
>  I suspect that most WG participants have difficulty keeping up with 
> the traffic on their WGs' mailing lists for various reasons (too 
> much "distraction" from normal work, the sad state of mail user 
> agents, etc.). By forcing people to travel away from work, 
> face-to-face meetings serve as useful interruptions from normal 
> distractions and opportunities to catch up on IETF work.  If 
> working groups moved forward even faster than they do now, that 
> might actually be seen to increase the need for presentations at 
> face-to-face meetings.
>
>  Occasionally I've wondered if IETF meetings should have 
> "presentation" sessions separate from (and in advance of) "working" 
> sessions.    The difference between the two types of session would 
> be clearly indicated in the schedule.   The presentation sessions 
> would be geared toward presenting an overview of current state of 
> the proposals, including a summary of recent changes.   Perhaps 
> participants would be allowed to ask questions for clarification, 
> but discussion should be discouraged and any kind of polling of the 
> room or other decision making would be forbidden.  The presentation 
> meetings would therefore be optional for those who had kept up on 
> the mailing list.   And presentations would be forbidden in 
> discussion sessions.
>
>  I can imagine these being useful in several ways, e.g. in 
> facilitating better cross-group and cross-area review.   People who 
> were active participants in working groups could attend 
> presentation sessions of other groups, without sacrificing their 
> attendance in the discussion sessions of the groups in which they 
> were active.
>
>  Perhaps roughly the first 2(?) days of an IETF meeting could be 
> largely devoted to presentation sessions, and the remainder of the 
> time to discussion sessions.    Having a strict allocation of time 
> for each kind of session isn't so important as having the 
> presentation sessions for a particular group well in advance of the 
> discussion session for that group.
>
>  This is something that could be tried on a small scale, by a few 
> working groups (say one in each area) before being widely adopted. 
> It might help, however, to have explicit support for the idea in 
> the tools that maintain and display the meeting schedules.

My initial reaction was "No!" with a gut reaction that it would 
worsen the problems we have, but the more I've thought about this, 
the more I like it.  I've now come around to thinking this could be a 
really good idea.  Instead of fighting to hold back the tide, we 
accept it and figure out how to deal with it.  Yes, let's try it.

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

From vesely@tana.it  Thu Dec 13 05:57:46 2012
Return-Path: <vesely@tana.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 6BAE821F8AD1 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 05:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8VoC5cFVAG4t for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 05:57:45 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 7F32C21F8ADB for <ietf@ietf.org>; Thu, 13 Dec 2012 05:57:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1355407063; bh=bpRqw503LmW1csEQR52LfJDm34lzOTym0nV/RHcoQUY=; l=736; h=Date:From:To:References:In-Reply-To; b=WfeW4ev3uI7OyWay4YZmIk5dA9CBd+LDhQBWTU9vsF7WXjDirlVU0Bzip3/iL81ot f5UcioDqf4U1ITOdl3WS4SwR9zgS+cMUWiZim7QSHPkZ/5wuYURrA5KYtQJlX8GqH2 Is/hIDSYNyktJ9MF28qOMo+Hn/3tZH+vmMw+unXo=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Thu, 13 Dec 2012 14:57:43 +0100 id 00000000005DC031.0000000050C9DED7.00001CA7
Message-ID: <50C9DED7.8060604@tana.it>
Date: Thu, 13 Dec 2012 14:57:43 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com>
In-Reply-To: <50C8DB78.3080905@gmail.com>
Content-Type: text/plain; charset=us-ascii
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, 13 Dec 2012 13:57:46 -0000

On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
> 
> I have just published a draft that proposes an alternative to
> Stephen's "fast track". My proposal simply allows authors to document,
> in a semi-standard way, whatever implementations exist for their
> protocol, as well as their interoperability.
> 
> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
> 
> [...]
> 
> I am looking forward to comments and discussion on this list.

As an occasional I-D reader, I'd appreciate "Implementation Status"
sections, including IPR info.  I don't think anything forbids to add
such sections, if the authors wish.  I'd add a count of the number of
I-Ds that actually have it among the experiment's success criteria.

From adrian@olddog.co.uk  Thu Dec 13 06:16:30 2012
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 6FF5721F8B0C for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t2UAUmQ+KSyc for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:16:30 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 8586F21F8B0B for <ietf@ietf.org>; Thu, 13 Dec 2012 06:16:29 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDEGR51015993;  Thu, 13 Dec 2012 14:16:27 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDEGQjq015973 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 13 Dec 2012 14:16:27 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Alessandro Vesely'" <vesely@tana.it>, <ietf@ietf.org>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it>
In-Reply-To: <50C9DED7.8060604@tana.it>
Subject: RE: Running code, take 2
Date: Thu, 13 Dec 2012 14:16:24 -0000
Message-ID: <006601cdd93c$6f9f7a00$4ede6e00$@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: AQGe4+QL1KmOUmkeH6pPkukeTFqmiwITGFE+mGQXbyA=
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: Thu, 13 Dec 2012 14:16:30 -0000

I'm interested in this idea.

However, I note that an "implementation status" section of a document is frozen
in time when a document goes to RFC.

I wonder whether we could leverage our tools and do something similar to IPR
disclosures. That is, provide a semi-formal web page where implementation
details could be recorded and updated. These would then be searchable and linked
to from the tools page for the I-D / RFC. 

They could record the document version that has been implemented, and also allow
space for other notes.

Adrian (Just thinking aloud)

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Alessandro Vesely
> Sent: 13 December 2012 13:58
> To: ietf@ietf.org
> Subject: Re: Running code, take 2
> 
> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
> >
> > I have just published a draft that proposes an alternative to
> > Stephen's "fast track". My proposal simply allows authors to document,
> > in a semi-standard way, whatever implementations exist for their
> > protocol, as well as their interoperability.
> >
> > http://www.ietf.org/id/draft-sheffer-running-code-00.txt
> >
> > [...]
> >
> > I am looking forward to comments and discussion on this list.
> 
> As an occasional I-D reader, I'd appreciate "Implementation Status"
> sections, including IPR info.  I don't think anything forbids to add
> such sections, if the authors wish.  I'd add a count of the number of
> I-Ds that actually have it among the experiment's success criteria.


From marc.blanchet@viagenie.ca  Thu Dec 13 06:18:37 2012
Return-Path: <marc.blanchet@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 4E76521F8948 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:18:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.505
X-Spam-Level: 
X-Spam-Status: No, score=-102.505 tagged_above=-999 required=5 tests=[AWL=0.094, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7Bzw0DLX59B for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:18:36 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id CE6F621F8870 for <ietf@ietf.org>; Thu, 13 Dec 2012 06:18:35 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2E28141474; Thu, 13 Dec 2012 09:18:35 -0500 (EST)
Subject: Re: Running code, take 2
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk>
Date: Thu, 13 Dec 2012 09:18:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1283)
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 14:18:37 -0000

Le 2012-12-13 =E0 09:16, Adrian Farrel a =E9crit :

> I'm interested in this idea.
>=20
> However, I note that an "implementation status" section of a document =
is frozen
> in time when a document goes to RFC.
>=20
> I wonder whether we could leverage our tools and do something similar =
to IPR
> disclosures. That is, provide a semi-formal web page where =
implementation
> details could be recorded and updated. These would then be searchable =
and linked
> to from the tools page for the I-D / RFC.=20
>=20
> They could record the document version that has been implemented, and =
also allow
> space for other notes.


I like that idea.

Marc.

>=20
> Adrian (Just thinking aloud)
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Alessandro Vesely
>> Sent: 13 December 2012 13:58
>> To: ietf@ietf.org
>> Subject: Re: Running code, take 2
>>=20
>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>=20
>>> I have just published a draft that proposes an alternative to
>>> Stephen's "fast track". My proposal simply allows authors to =
document,
>>> in a semi-standard way, whatever implementations exist for their
>>> protocol, as well as their interoperability.
>>>=20
>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>=20
>>> [...]
>>>=20
>>> I am looking forward to comments and discussion on this list.
>>=20
>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>> sections, including IPR info.  I don't think anything forbids to add
>> such sections, if the authors wish.  I'd add a count of the number of
>> I-Ds that actually have it among the experiment's success criteria.


From yaronf.ietf@gmail.com  Thu Dec 13 06:48:08 2012
Return-Path: <yaronf.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 C282121F87F4 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:48:08 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQFPNEb0pQ3U for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:48:08 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id C8B7C21F87F2 for <ietf@ietf.org>; Thu, 13 Dec 2012 06:48:07 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so1802250lah.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 06:48:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=cPAxbHxbnQD1kNjvhd2fk+au8lMGnoPGWrg4MGPXgJk=; b=gDet0oTCi5sw65GLXI+FWWyxU1KqWI2eMsWnO1dmoPS9BmE/yB1AH8DA1u3UJrgnWN e54GrRdCvpTHI8aunqyElutUe9+9pibLW4IE3qQX6ZkeE7ynqJwuTI91V5FCMhRkozlu 623Pg5xIn4hwzSdBCImjbu6kRwE78cKDp+HvN91gCsJO30NHctFeFz8mXgh1lgpj5x6O LTgstyzHwdUMmo+wdsdXOpDagQapN614tupuWPo3Z2Cx/9UM5gSaBkqsx1mN4fWxbjsa uVsZLAYbbCviUq1SQ6tUWcU82bzaCleWglCa2c/Cz3Kiu3CW7W0DZuAS4J+N1xScameE Lm6w==
Received: by 10.152.147.103 with SMTP id tj7mr292897lab.54.1355410086559; Thu, 13 Dec 2012 06:48:06 -0800 (PST)
Received: from [10.0.0.13] (85-250-110-45.bb.netvision.net.il. [85.250.110.45]) by mx.google.com with ESMTPS id ja10sm746535lab.6.2012.12.13.06.48.03 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 06:48:05 -0800 (PST)
Message-ID: <50C9EAA1.5070602@gmail.com>
Date: Thu, 13 Dec 2012 16:48:01 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it>
In-Reply-To: <50C9DED7.8060604@tana.it>
Content-Type: text/plain; charset=windows-1252; 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, 13 Dec 2012 14:48:08 -0000

Thanks Alessandro. I couldn't think of a specific count (10? 100?) for 
the success criteria, which is why the criteria are rather fuzzy. The 
experiment's summary report does promise to list adoption statistics.

Best,
	Yaron

On 12/13/2012 03:57 PM, Alessandro Vesely wrote:
> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>
>> I have just published a draft that proposes an alternative to
>> Stephen's "fast track". My proposal simply allows authors to document,
>> in a semi-standard way, whatever implementations exist for their
>> protocol, as well as their interoperability.
>>
>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>
>> [...]
>>
>> I am looking forward to comments and discussion on this list.
>
> As an occasional I-D reader, I'd appreciate "Implementation Status"
> sections, including IPR info.  I don't think anything forbids to add
> such sections, if the authors wish.  I'd add a count of the number of
> I-Ds that actually have it among the experiment's success criteria.
>

From yaronf.ietf@gmail.com  Thu Dec 13 06:52:52 2012
Return-Path: <yaronf.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 366AC21F88F4 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:52:52 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wPRODajlpXds for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:52:50 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 67A1121F8774 for <ietf@ietf.org>; Thu, 13 Dec 2012 06:52:48 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so1807253lah.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 06:52:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Rx0eCmtJWrx0kRVwn6CvYJVLFvNMf5jC3sgkkwJPC7M=; b=tJX/LowKJlEOR5Pep5CWLqhOGZAD58MsMoPOeF4emqlZPVhTGFNv6fXLviZIbGOmN9 SrGHArjM1c8fFiTWU215Jy59AYH2AIpRbg+/b7IqM8fWnteCYY7xdGahmpB03KcosUYL fy52xb6UnKlOXay/wOpu2E5xzu7/O6dY9H1sH7NqfOoHLqbG6/2ZmLLj5DNrjJ0YqRcm YYXNZl+H1uBRJGfL4hWemPJwIfs86kXhSH6N8NU7p46RiUvwg/w9oLnwg3pYsItXsQU1 X4TaYJwTHvbb7Cv7fKYdwMXEyuJD5kTeIEDUALUF3Mlq9es3ynJRy+i0muvwQ9ZldaaX wSWw==
Received: by 10.152.112.36 with SMTP id in4mr263226lab.35.1355410366094; Thu, 13 Dec 2012 06:52:46 -0800 (PST)
Received: from [10.0.0.13] (85-250-110-45.bb.netvision.net.il. [85.250.110.45]) by mx.google.com with ESMTPS id hu6sm749210lab.13.2012.12.13.06.52.40 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 06:52:44 -0800 (PST)
Message-ID: <50C9EBB3.5040901@gmail.com>
Date: Thu, 13 Dec 2012 16:52:35 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk>
In-Reply-To: <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 14:52:53 -0000

Hi Adrian,

I would suggest to start with my proposal, because it requires zero 
implementation effort. If this catches on, I see a lot of value in your 
proposal.

Please also note that the "implementation status" section (according to 
my proposal) is not "frozen" when published as an RFC, rather it is 
deleted. RFCs are forever, and I think a point-in-time implementation 
status is not appropriate in an RFC.

Thanks,
	Yaron

On 12/13/2012 04:16 PM, Adrian Farrel wrote:
> I'm interested in this idea.
>
> However, I note that an "implementation status" section of a document is frozen
> in time when a document goes to RFC.
>
> I wonder whether we could leverage our tools and do something similar to IPR
> disclosures. That is, provide a semi-formal web page where implementation
> details could be recorded and updated. These would then be searchable and linked
> to from the tools page for the I-D / RFC.
>
> They could record the document version that has been implemented, and also allow
> space for other notes.
>
> Adrian (Just thinking aloud)
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Alessandro Vesely
>> Sent: 13 December 2012 13:58
>> To: ietf@ietf.org
>> Subject: Re: Running code, take 2
>>
>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>
>>> I have just published a draft that proposes an alternative to
>>> Stephen's "fast track". My proposal simply allows authors to document,
>>> in a semi-standard way, whatever implementations exist for their
>>> protocol, as well as their interoperability.
>>>
>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>
>>> [...]
>>>
>>> I am looking forward to comments and discussion on this list.
>>
>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>> sections, including IPR info.  I don't think anything forbids to add
>> such sections, if the authors wish.  I'd add a count of the number of
>> I-Ds that actually have it among the experiment's success criteria.
>

From marc.blanchet@viagenie.ca  Thu Dec 13 06:55:33 2012
Return-Path: <marc.blanchet@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 1D4C721F8AD0 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:55:33 -0800 (PST)
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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BARufobNEj-2 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 06:55:32 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 59C2521F880D for <ietf@ietf.org>; Thu, 13 Dec 2012 06:55:32 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 0021B41474; Thu, 13 Dec 2012 09:55:22 -0500 (EST)
Subject: Re: Running code, take 2
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <50C9EBB3.5040901@gmail.com>
Date: Thu, 13 Dec 2012 09:55:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1283)
Cc: adrian@olddog.co.uk, ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 14:55:33 -0000

Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :

> Hi Adrian,
>=20
> I would suggest to start with my proposal, because it requires zero =
implementation effort.

disagree. phase 1: use IETF wiki. phase 2: develop an widget within data =
tracker.

Marc.


> If this catches on, I see a lot of value in your proposal.
>=20
> Please also note that the "implementation status" section (according =
to my proposal) is not "frozen" when published as an RFC, rather it is =
deleted. RFCs are forever, and I think a point-in-time implementation =
status is not appropriate in an RFC.
>=20
> Thanks,
> 	Yaron
>=20
> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>> I'm interested in this idea.
>>=20
>> However, I note that an "implementation status" section of a document =
is frozen
>> in time when a document goes to RFC.
>>=20
>> I wonder whether we could leverage our tools and do something similar =
to IPR
>> disclosures. That is, provide a semi-formal web page where =
implementation
>> details could be recorded and updated. These would then be searchable =
and linked
>> to from the tools page for the I-D / RFC.
>>=20
>> They could record the document version that has been implemented, and =
also allow
>> space for other notes.
>>=20
>> Adrian (Just thinking aloud)
>>=20
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>>> Alessandro Vesely
>>> Sent: 13 December 2012 13:58
>>> To: ietf@ietf.org
>>> Subject: Re: Running code, take 2
>>>=20
>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>=20
>>>> I have just published a draft that proposes an alternative to
>>>> Stephen's "fast track". My proposal simply allows authors to =
document,
>>>> in a semi-standard way, whatever implementations exist for their
>>>> protocol, as well as their interoperability.
>>>>=20
>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>=20
>>>> [...]
>>>>=20
>>>> I am looking forward to comments and discussion on this list.
>>>=20
>>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>>> sections, including IPR info.  I don't think anything forbids to add
>>> such sections, if the authors wish.  I'd add a count of the number =
of
>>> I-Ds that actually have it among the experiment's success criteria.
>>=20


From yaronf.ietf@gmail.com  Thu Dec 13 07:00:19 2012
Return-Path: <yaronf.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 8B29621F8B3A for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:00:19 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eIuDIkcteu+J for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:00:19 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id AA54E21F8B39 for <ietf@ietf.org>; Thu, 13 Dec 2012 07:00:18 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so1829933lbk.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 07:00:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hDYt3ofUbDnAgTCtKQVTKLd3brfz74fjv3vllk/lkvw=; b=Uy1yiQaQb3OUB5Vrd6zmvjjL+InJuR6NpjNsfFQ5f7mAw1RdweeHRRywfQSEUTdGAB MoVypsSLxhxvzWHB/e3CjQ2ruhS6s2tOTQpxrjMoi8PMOMAeYr37BClJKE3vtLaKFdng L3q9591pex0X0J0ZCNULOPf+LQGot0uzUmvrcPLXn89bve2asbR4f7vlQQAZQw+LKYu1 QdKYcf6qOlsJQ8Q2RrGDSMLfio0yHHTj1cNk+LSAzI4xyQ23pm151Xtx/p3vf8KgJQxX C3EA3H56ZpPy9AmvFqp8kEXUXV7vaqa53PttK5VQxS47j3pmJAZH7xnyMutXYVsDUuzB fY8A==
Received: by 10.152.45.229 with SMTP id q5mr299886lam.34.1355410817485; Thu, 13 Dec 2012 07:00:17 -0800 (PST)
Received: from [10.0.0.13] (85-250-110-45.bb.netvision.net.il. [85.250.110.45]) by mx.google.com with ESMTPS id sr6sm763027lab.4.2012.12.13.07.00.14 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 07:00:16 -0800 (PST)
Message-ID: <50C9ED7B.2010009@gmail.com>
Date: Thu, 13 Dec 2012 17:00:11 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca>
In-Reply-To: <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: adrian@olddog.co.uk, ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 15:00:19 -0000

Hi Marc,

I think it's critical that a person reading a draft (e.g. going to 
http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) 
will have a direct way to check out on the implementation status.

This is trivial if it's a section in the document. It's simple if it's 
linked from the Tools page. Otherwise, e.g. if you put it on the wiki, 
only IETF insiders will be aware of it.

Thanks,
	Yaron

On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>
> Le 2012-12-13 à 09:52, Yaron Sheffer a écrit :
>
>> Hi Adrian,
>>
>> I would suggest to start with my proposal, because it requires zero implementation effort.
>
> disagree. phase 1: use IETF wiki. phase 2: develop an widget within data tracker.
>
> Marc.
>
>
>> If this catches on, I see a lot of value in your proposal.
>>
>> Please also note that the "implementation status" section (according to my proposal) is not "frozen" when published as an RFC, rather it is deleted. RFCs are forever, and I think a point-in-time implementation status is not appropriate in an RFC.
>>
>> Thanks,
>> 	Yaron
>>
>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>> I'm interested in this idea.
>>>
>>> However, I note that an "implementation status" section of a document is frozen
>>> in time when a document goes to RFC.
>>>
>>> I wonder whether we could leverage our tools and do something similar to IPR
>>> disclosures. That is, provide a semi-formal web page where implementation
>>> details could be recorded and updated. These would then be searchable and linked
>>> to from the tools page for the I-D / RFC.
>>>
>>> They could record the document version that has been implemented, and also allow
>>> space for other notes.
>>>
>>> Adrian (Just thinking aloud)
>>>
>>>> -----Original Message-----
>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>>> Alessandro Vesely
>>>> Sent: 13 December 2012 13:58
>>>> To: ietf@ietf.org
>>>> Subject: Re: Running code, take 2
>>>>
>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>
>>>>> I have just published a draft that proposes an alternative to
>>>>> Stephen's "fast track". My proposal simply allows authors to document,
>>>>> in a semi-standard way, whatever implementations exist for their
>>>>> protocol, as well as their interoperability.
>>>>>
>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>
>>>>> [...]
>>>>>
>>>>> I am looking forward to comments and discussion on this list.
>>>>
>>>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>>>> sections, including IPR info.  I don't think anything forbids to add
>>>> such sections, if the authors wish.  I'd add a count of the number of
>>>> I-Ds that actually have it among the experiment's success criteria.
>>>
>

From marc.blanchet@viagenie.ca  Thu Dec 13 07:04:44 2012
Return-Path: <marc.blanchet@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 92D0F21F8B51 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.516
X-Spam-Level: 
X-Spam-Status: No, score=-102.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qAEiI8C1qFu for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:04:44 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id E160B21F894D for <ietf@ietf.org>; Thu, 13 Dec 2012 07:04:43 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 2B18441474; Thu, 13 Dec 2012 10:04:43 -0500 (EST)
Subject: Re: Running code, take 2
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <50C9ED7B.2010009@gmail.com>
Date: Thu, 13 Dec 2012 10:04:42 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
X-Mailer: Apple Mail (2.1283)
Cc: adrian@olddog.co.uk, ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 15:04:44 -0000

Le 2012-12-13 =E0 10:00, Yaron Sheffer a =E9crit :

> Hi Marc,
>=20
> I think it's critical that a person reading a draft (e.g. going to =
http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) =
will have a direct way to check out on the implementation status.
>=20
> This is trivial if it's a section in the document. It's simple if it's =
linked from the Tools page. Otherwise, e.g. if you put it on the wiki, =
only IETF insiders will be aware of it.
>=20

sure. Let me restart:
- I like Adrian proposal: instead of in RFC, put it online within our =
site
- but you wrote: requires implementation effort.
- I replied: well, phase 1 (of put it online within our site) can be =
done with almost zero implementation effort. phase 2 requires some work =
(I'd say not that big) for implementation/tools.

Regards, Marc.

> Thanks,
> 	Yaron
>=20
> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>=20
>> Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :
>>=20
>>> Hi Adrian,
>>>=20
>>> I would suggest to start with my proposal, because it requires zero =
implementation effort.
>>=20
>> disagree. phase 1: use IETF wiki. phase 2: develop an widget within =
data tracker.
>>=20
>> Marc.
>>=20
>>=20
>>> If this catches on, I see a lot of value in your proposal.
>>>=20
>>> Please also note that the "implementation status" section (according =
to my proposal) is not "frozen" when published as an RFC, rather it is =
deleted. RFCs are forever, and I think a point-in-time implementation =
status is not appropriate in an RFC.
>>>=20
>>> Thanks,
>>> 	Yaron
>>>=20
>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>> I'm interested in this idea.
>>>>=20
>>>> However, I note that an "implementation status" section of a =
document is frozen
>>>> in time when a document goes to RFC.
>>>>=20
>>>> I wonder whether we could leverage our tools and do something =
similar to IPR
>>>> disclosures. That is, provide a semi-formal web page where =
implementation
>>>> details could be recorded and updated. These would then be =
searchable and linked
>>>> to from the tools page for the I-D / RFC.
>>>>=20
>>>> They could record the document version that has been implemented, =
and also allow
>>>> space for other notes.
>>>>=20
>>>> Adrian (Just thinking aloud)
>>>>=20
>>>>> -----Original Message-----
>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On =
Behalf Of
>>>>> Alessandro Vesely
>>>>> Sent: 13 December 2012 13:58
>>>>> To: ietf@ietf.org
>>>>> Subject: Re: Running code, take 2
>>>>>=20
>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>=20
>>>>>> I have just published a draft that proposes an alternative to
>>>>>> Stephen's "fast track". My proposal simply allows authors to =
document,
>>>>>> in a semi-standard way, whatever implementations exist for their
>>>>>> protocol, as well as their interoperability.
>>>>>>=20
>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>=20
>>>>>> [...]
>>>>>>=20
>>>>>> I am looking forward to comments and discussion on this list.
>>>>>=20
>>>>> As an occasional I-D reader, I'd appreciate "Implementation =
Status"
>>>>> sections, including IPR info.  I don't think anything forbids to =
add
>>>>> such sections, if the authors wish.  I'd add a count of the number =
of
>>>>> I-Ds that actually have it among the experiment's success =
criteria.
>>>>=20
>>=20


From adrian@olddog.co.uk  Thu Dec 13 07:10:45 2012
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 1FFEF21F8B66 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level: 
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eU9atKYpuQ1F for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:10:44 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 3641221F8B5A for <ietf@ietf.org>; Thu, 13 Dec 2012 07:10:44 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDFAfoK014971;  Thu, 13 Dec 2012 15:10:41 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDFAeN3014950 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 13 Dec 2012 15:10:40 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Marc Blanchet'" <marc.blanchet@viagenie.ca>, "'Yaron Sheffer'" <yaronf.ietf@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca>
In-Reply-To: <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca>
Subject: RE: Running code, take 2
Date: Thu, 13 Dec 2012 15:10:38 -0000
Message-ID: <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGe4+QL1KmOUmkeH6pPkukeTFqmiwITGFE+A18VCBkBz5uMRQJadp8rAcj56PsC2bITcZgCyE8g
Content-Language: en-gb
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
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: Thu, 13 Dec 2012 15:10:45 -0000

How about...

Start with Yaron's proposal to include in the I-D. This is easy as a =
starting
point. Duplicate documentation in wiki may be useful and provide a place =
to
track text for inclusion in the next revision.

When/if inclusion in the I-D gets messy, replace text in I-D with =
pointer to
wiki.

When/if experiment looks like a success, replace all above with data =
tracker
tool and allow it to persist for RFCs.

Adrian

> -----Original Message-----
> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
> Sent: 13 December 2012 15:05
> To: Yaron Sheffer
> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
> Subject: Re: Running code, take 2
>=20
>=20
> Le 2012-12-13 =E0 10:00, Yaron Sheffer a =E9crit :
>=20
> > Hi Marc,
> >
> > I think it's critical that a person reading a draft (e.g. going to
> http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) =
will
have a
> direct way to check out on the implementation status.
> >
> > This is trivial if it's a section in the document. It's simple if =
it's
linked from the
> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF =
insiders will
be
> aware of it.
> >
>=20
> sure. Let me restart:
> - I like Adrian proposal: instead of in RFC, put it online within our =
site
> - but you wrote: requires implementation effort.
> - I replied: well, phase 1 (of put it online within our site) can be =
done with
almost
> zero implementation effort. phase 2 requires some work (I'd say not =
that big)
for
> implementation/tools.
>=20
> Regards, Marc.
>=20
> > Thanks,
> > 	Yaron
> >
> > On 12/13/2012 04:55 PM, Marc Blanchet wrote:
> >>
> >> Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :
> >>
> >>> Hi Adrian,
> >>>
> >>> I would suggest to start with my proposal, because it requires =
zero
> implementation effort.
> >>
> >> disagree. phase 1: use IETF wiki. phase 2: develop an widget within =
data
> tracker.
> >>
> >> Marc.
> >>
> >>
> >>> If this catches on, I see a lot of value in your proposal.
> >>>
> >>> Please also note that the "implementation status" section =
(according to my
> proposal) is not "frozen" when published as an RFC, rather it is =
deleted. RFCs
are
> forever, and I think a point-in-time implementation status is not =
appropriate
in an
> RFC.
> >>>
> >>> Thanks,
> >>> 	Yaron
> >>>
> >>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
> >>>> I'm interested in this idea.
> >>>>
> >>>> However, I note that an "implementation status" section of a =
document is
> frozen
> >>>> in time when a document goes to RFC.
> >>>>
> >>>> I wonder whether we could leverage our tools and do something =
similar to
> IPR
> >>>> disclosures. That is, provide a semi-formal web page where =
implementation
> >>>> details could be recorded and updated. These would then be =
searchable
> and linked
> >>>> to from the tools page for the I-D / RFC.
> >>>>
> >>>> They could record the document version that has been implemented, =
and
> also allow
> >>>> space for other notes.
> >>>>
> >>>> Adrian (Just thinking aloud)
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On =
Behalf Of
> >>>>> Alessandro Vesely
> >>>>> Sent: 13 December 2012 13:58
> >>>>> To: ietf@ietf.org
> >>>>> Subject: Re: Running code, take 2
> >>>>>
> >>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
> >>>>>>
> >>>>>> I have just published a draft that proposes an alternative to
> >>>>>> Stephen's "fast track". My proposal simply allows authors to =
document,
> >>>>>> in a semi-standard way, whatever implementations exist for =
their
> >>>>>> protocol, as well as their interoperability.
> >>>>>>
> >>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
> >>>>>>
> >>>>>> [...]
> >>>>>>
> >>>>>> I am looking forward to comments and discussion on this list.
> >>>>>
> >>>>> As an occasional I-D reader, I'd appreciate "Implementation =
Status"
> >>>>> sections, including IPR info.  I don't think anything forbids to =
add
> >>>>> such sections, if the authors wish.  I'd add a count of the =
number of
> >>>>> I-Ds that actually have it among the experiment's success =
criteria.
> >>>>
> >>


From yaronf.ietf@gmail.com  Thu Dec 13 07:12:02 2012
Return-Path: <yaronf.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 DBDA421F8B75 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:12:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBibnYVVtqvu for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:12:02 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id BB19E21F8B6D for <ietf@ietf.org>; Thu, 13 Dec 2012 07:12:01 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so1843663lbk.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 07:12:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=NYgsCGFKTeT5kSrJ2rZUJ+sVxxlT9p8eQFHLYLRkdhk=; b=DLaiA5H79AiJG7B0Z94JaoXXvI5qAaYi9Wz7m1iKDzKZVQUcM5j5zDBbQeA+4C1mNi U8MJgyralgA5hgNotWrMML7XozhB1krflW6F9DvygDX1HAvcDn9RyqRAq4kgqAmtEFhT 7Nsx1CAt9b4M4aFqnyt+H1VS5Nkdz/K+f5AkqXGIm7ct7/Lo1wv85mG6S2/ibEN3qx3F cYela7zCRxW4fsJ7syW39i21mJvyu/+AzC20W1VqVF0m/Ak+1ERLiJCApciMVQGBrFBF s3zFy97cx4zJ3pimy7/HnUq9MukHmA6nA/QOtTU91oa7l4XjO8RNawTa8bd09zRoByjz lK+A==
Received: by 10.112.23.233 with SMTP id p9mr1094727lbf.6.1355411520672; Thu, 13 Dec 2012 07:12:00 -0800 (PST)
Received: from [10.0.0.13] (85-250-110-45.bb.netvision.net.il. [85.250.110.45]) by mx.google.com with ESMTPS id pw17sm776953lab.5.2012.12.13.07.11.57 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 07:11:59 -0800 (PST)
Message-ID: <50C9F03A.5090506@gmail.com>
Date: Thu, 13 Dec 2012 17:11:54 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
In-Reply-To: <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 15:12:03 -0000

+1.

	Yaron

On 12/13/2012 05:10 PM, Adrian Farrel wrote:
> How about...
>
> Start with Yaron's proposal to include in the I-D. This is easy as a starting
> point. Duplicate documentation in wiki may be useful and provide a place to
> track text for inclusion in the next revision.
>
> When/if inclusion in the I-D gets messy, replace text in I-D with pointer to
> wiki.
>
> When/if experiment looks like a success, replace all above with data tracker
> tool and allow it to persist for RFCs.
>
> Adrian
>
>> -----Original Message-----
>> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>> Sent: 13 December 2012 15:05
>> To: Yaron Sheffer
>> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>> Subject: Re: Running code, take 2
>>
>>
>> Le 2012-12-13 à 10:00, Yaron Sheffer a écrit :
>>
>>> Hi Marc,
>>>
>>> I think it's critical that a person reading a draft (e.g. going to
>> http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) will
> have a
>> direct way to check out on the implementation status.
>>>
>>> This is trivial if it's a section in the document. It's simple if it's
> linked from the
>> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF insiders will
> be
>> aware of it.
>>>
>>
>> sure. Let me restart:
>> - I like Adrian proposal: instead of in RFC, put it online within our site
>> - but you wrote: requires implementation effort.
>> - I replied: well, phase 1 (of put it online within our site) can be done with
> almost
>> zero implementation effort. phase 2 requires some work (I'd say not that big)
> for
>> implementation/tools.
>>
>> Regards, Marc.
>>
>>> Thanks,
>>> 	Yaron
>>>
>>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>>>
>>>> Le 2012-12-13 à 09:52, Yaron Sheffer a écrit :
>>>>
>>>>> Hi Adrian,
>>>>>
>>>>> I would suggest to start with my proposal, because it requires zero
>> implementation effort.
>>>>
>>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget within data
>> tracker.
>>>>
>>>> Marc.
>>>>
>>>>
>>>>> If this catches on, I see a lot of value in your proposal.
>>>>>
>>>>> Please also note that the "implementation status" section (according to my
>> proposal) is not "frozen" when published as an RFC, rather it is deleted. RFCs
> are
>> forever, and I think a point-in-time implementation status is not appropriate
> in an
>> RFC.
>>>>>
>>>>> Thanks,
>>>>> 	Yaron
>>>>>
>>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>>>> I'm interested in this idea.
>>>>>>
>>>>>> However, I note that an "implementation status" section of a document is
>> frozen
>>>>>> in time when a document goes to RFC.
>>>>>>
>>>>>> I wonder whether we could leverage our tools and do something similar to
>> IPR
>>>>>> disclosures. That is, provide a semi-formal web page where implementation
>>>>>> details could be recorded and updated. These would then be searchable
>> and linked
>>>>>> to from the tools page for the I-D / RFC.
>>>>>>
>>>>>> They could record the document version that has been implemented, and
>> also allow
>>>>>> space for other notes.
>>>>>>
>>>>>> Adrian (Just thinking aloud)
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>>>>>> Alessandro Vesely
>>>>>>> Sent: 13 December 2012 13:58
>>>>>>> To: ietf@ietf.org
>>>>>>> Subject: Re: Running code, take 2
>>>>>>>
>>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>>>
>>>>>>>> I have just published a draft that proposes an alternative to
>>>>>>>> Stephen's "fast track". My proposal simply allows authors to document,
>>>>>>>> in a semi-standard way, whatever implementations exist for their
>>>>>>>> protocol, as well as their interoperability.
>>>>>>>>
>>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>>>
>>>>>>>> [...]
>>>>>>>>
>>>>>>>> I am looking forward to comments and discussion on this list.
>>>>>>>
>>>>>>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>>>>>>> sections, including IPR info.  I don't think anything forbids to add
>>>>>>> such sections, if the authors wish.  I'd add a count of the number of
>>>>>>> I-Ds that actually have it among the experiment's success criteria.
>>>>>>
>>>>
>

From adrian@olddog.co.uk  Thu Dec 13 07:13:41 2012
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 CDC1C21F8B1C for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:13:41 -0800 (PST)
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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2pHcXqjZ8aF for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:13:41 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 841B021F8B0A for <ietf@ietf.org>; Thu, 13 Dec 2012 07:13:40 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDFDcqQ016561;  Thu, 13 Dec 2012 15:13:38 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id qBDFDbhK016555 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 13 Dec 2012 15:13:38 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Yaron Sheffer'" <yaronf.ietf@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk> <50C9F03A.5090506@gmail.com>
In-Reply-To: <50C9F03A.5090506@gmail.com>
Subject: RE: Running code, take 2
Date: Thu, 13 Dec 2012 15:13:35 -0000
Message-ID: <009c01cdd944$6c9f11a0$45dd34e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGe4+QL1KmOUmkeH6pPkukeTFqmiwITGFE+A18VCBkBz5uMRQJadp8rAcj56PsC2bITcQIiCX9fAhA6kA2X4Td7QA==
Content-Language: en-gb
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
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: Thu, 13 Dec 2012 15:13:41 -0000

Yaron,

Would you be willing to add this to your I-D?

> -----Original Message-----
> From: Yaron Sheffer [mailto:yaronf.ietf@gmail.com]
> Sent: 13 December 2012 15:12
> To: adrian@olddog.co.uk
> Cc: 'Marc Blanchet'; ietf@ietf.org; 'Alessandro Vesely'
> Subject: Re: Running code, take 2
>=20
> +1.
>=20
> 	Yaron
>=20
> On 12/13/2012 05:10 PM, Adrian Farrel wrote:
> > How about...
> >
> > Start with Yaron's proposal to include in the I-D. This is easy as a
starting
> > point. Duplicate documentation in wiki may be useful and provide a =
place to
> > track text for inclusion in the next revision.
> >
> > When/if inclusion in the I-D gets messy, replace text in I-D with =
pointer to
> > wiki.
> >
> > When/if experiment looks like a success, replace all above with data =
tracker
> > tool and allow it to persist for RFCs.
> >
> > Adrian
> >
> >> -----Original Message-----
> >> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
> >> Sent: 13 December 2012 15:05
> >> To: Yaron Sheffer
> >> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
> >> Subject: Re: Running code, take 2
> >>
> >>
> >> Le 2012-12-13 =E0 10:00, Yaron Sheffer a =E9crit :
> >>
> >>> Hi Marc,
> >>>
> >>> I think it's critical that a person reading a draft (e.g. going to
> >> =
http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) =
will
> > have a
> >> direct way to check out on the implementation status.
> >>>
> >>> This is trivial if it's a section in the document. It's simple if =
it's
> > linked from the
> >> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF =
insiders
will
> > be
> >> aware of it.
> >>>
> >>
> >> sure. Let me restart:
> >> - I like Adrian proposal: instead of in RFC, put it online within =
our site
> >> - but you wrote: requires implementation effort.
> >> - I replied: well, phase 1 (of put it online within our site) can =
be done
with
> > almost
> >> zero implementation effort. phase 2 requires some work (I'd say not =
that
big)
> > for
> >> implementation/tools.
> >>
> >> Regards, Marc.
> >>
> >>> Thanks,
> >>> 	Yaron
> >>>
> >>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
> >>>>
> >>>> Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :
> >>>>
> >>>>> Hi Adrian,
> >>>>>
> >>>>> I would suggest to start with my proposal, because it requires =
zero
> >> implementation effort.
> >>>>
> >>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget =
within data
> >> tracker.
> >>>>
> >>>> Marc.
> >>>>
> >>>>
> >>>>> If this catches on, I see a lot of value in your proposal.
> >>>>>
> >>>>> Please also note that the "implementation status" section =
(according to
> my
> >> proposal) is not "frozen" when published as an RFC, rather it is =
deleted.
RFCs
> > are
> >> forever, and I think a point-in-time implementation status is not
appropriate
> > in an
> >> RFC.
> >>>>>
> >>>>> Thanks,
> >>>>> 	Yaron
> >>>>>
> >>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
> >>>>>> I'm interested in this idea.
> >>>>>>
> >>>>>> However, I note that an "implementation status" section of a =
document
> is
> >> frozen
> >>>>>> in time when a document goes to RFC.
> >>>>>>
> >>>>>> I wonder whether we could leverage our tools and do something =
similar
> to
> >> IPR
> >>>>>> disclosures. That is, provide a semi-formal web page where
> implementation
> >>>>>> details could be recorded and updated. These would then be =
searchable
> >> and linked
> >>>>>> to from the tools page for the I-D / RFC.
> >>>>>>
> >>>>>> They could record the document version that has been =
implemented,
> and
> >> also allow
> >>>>>> space for other notes.
> >>>>>>
> >>>>>> Adrian (Just thinking aloud)
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On =
Behalf
> Of
> >>>>>>> Alessandro Vesely
> >>>>>>> Sent: 13 December 2012 13:58
> >>>>>>> To: ietf@ietf.org
> >>>>>>> Subject: Re: Running code, take 2
> >>>>>>>
> >>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
> >>>>>>>>
> >>>>>>>> I have just published a draft that proposes an alternative to
> >>>>>>>> Stephen's "fast track". My proposal simply allows authors to
> document,
> >>>>>>>> in a semi-standard way, whatever implementations exist for =
their
> >>>>>>>> protocol, as well as their interoperability.
> >>>>>>>>
> >>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
> >>>>>>>>
> >>>>>>>> [...]
> >>>>>>>>
> >>>>>>>> I am looking forward to comments and discussion on this list.
> >>>>>>>
> >>>>>>> As an occasional I-D reader, I'd appreciate "Implementation =
Status"
> >>>>>>> sections, including IPR info.  I don't think anything forbids =
to add
> >>>>>>> such sections, if the authors wish.  I'd add a count of the =
number of
> >>>>>>> I-Ds that actually have it among the experiment's success =
criteria.
> >>>>>>
> >>>>
> >


From marc.blanchet@viagenie.ca  Thu Dec 13 07:18:10 2012
Return-Path: <marc.blanchet@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 EBDDB21F8667 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 tagged_above=-999 required=5 tests=[AWL=0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AM7ZnZu1Y2Yr for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:18:10 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1AB21F865D for <ietf@ietf.org>; Thu, 13 Dec 2012 07:18:10 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id C1DE641474; Thu, 13 Dec 2012 10:18:06 -0500 (EST)
Subject: Re: Running code, take 2
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
Date: Thu, 13 Dec 2012 10:18:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE9B9573-3079-43DF-8EC7-CAA316F0F234@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
To: <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1283)
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 15:18:11 -0000

Le 2012-12-13 =E0 10:10, Adrian Farrel a =E9crit :

> How about...
>=20
> Start with Yaron's proposal to include in the I-D. This is easy as a =
starting
> point. Duplicate documentation in wiki may be useful and provide a =
place to
> track text for inclusion in the next revision.
>=20
> When/if inclusion in the I-D gets messy, replace text in I-D with =
pointer to
> wiki.
>=20
> When/if experiment looks like a success, replace all above with data =
tracker
> tool and allow it to persist for RFCs.

makes sense to me.

Marc.


>=20
> Adrian
>=20
>> -----Original Message-----
>> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>> Sent: 13 December 2012 15:05
>> To: Yaron Sheffer
>> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>> Subject: Re: Running code, take 2
>>=20
>>=20
>> Le 2012-12-13 =E0 10:00, Yaron Sheffer a =E9crit :
>>=20
>>> Hi Marc,
>>>=20
>>> I think it's critical that a person reading a draft (e.g. going to
>> http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) =
will
> have a
>> direct way to check out on the implementation status.
>>>=20
>>> This is trivial if it's a section in the document. It's simple if =
it's
> linked from the
>> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF =
insiders will
> be
>> aware of it.
>>>=20
>>=20
>> sure. Let me restart:
>> - I like Adrian proposal: instead of in RFC, put it online within our =
site
>> - but you wrote: requires implementation effort.
>> - I replied: well, phase 1 (of put it online within our site) can be =
done with
> almost
>> zero implementation effort. phase 2 requires some work (I'd say not =
that big)
> for
>> implementation/tools.
>>=20
>> Regards, Marc.
>>=20
>>> Thanks,
>>> 	Yaron
>>>=20
>>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>>>=20
>>>> Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :
>>>>=20
>>>>> Hi Adrian,
>>>>>=20
>>>>> I would suggest to start with my proposal, because it requires =
zero
>> implementation effort.
>>>>=20
>>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget within =
data
>> tracker.
>>>>=20
>>>> Marc.
>>>>=20
>>>>=20
>>>>> If this catches on, I see a lot of value in your proposal.
>>>>>=20
>>>>> Please also note that the "implementation status" section =
(according to my
>> proposal) is not "frozen" when published as an RFC, rather it is =
deleted. RFCs
> are
>> forever, and I think a point-in-time implementation status is not =
appropriate
> in an
>> RFC.
>>>>>=20
>>>>> Thanks,
>>>>> 	Yaron
>>>>>=20
>>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>>>> I'm interested in this idea.
>>>>>>=20
>>>>>> However, I note that an "implementation status" section of a =
document is
>> frozen
>>>>>> in time when a document goes to RFC.
>>>>>>=20
>>>>>> I wonder whether we could leverage our tools and do something =
similar to
>> IPR
>>>>>> disclosures. That is, provide a semi-formal web page where =
implementation
>>>>>> details could be recorded and updated. These would then be =
searchable
>> and linked
>>>>>> to from the tools page for the I-D / RFC.
>>>>>>=20
>>>>>> They could record the document version that has been implemented, =
and
>> also allow
>>>>>> space for other notes.
>>>>>>=20
>>>>>> Adrian (Just thinking aloud)
>>>>>>=20
>>>>>>> -----Original Message-----
>>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On =
Behalf Of
>>>>>>> Alessandro Vesely
>>>>>>> Sent: 13 December 2012 13:58
>>>>>>> To: ietf@ietf.org
>>>>>>> Subject: Re: Running code, take 2
>>>>>>>=20
>>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>>>=20
>>>>>>>> I have just published a draft that proposes an alternative to
>>>>>>>> Stephen's "fast track". My proposal simply allows authors to =
document,
>>>>>>>> in a semi-standard way, whatever implementations exist for =
their
>>>>>>>> protocol, as well as their interoperability.
>>>>>>>>=20
>>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>>>=20
>>>>>>>> [...]
>>>>>>>>=20
>>>>>>>> I am looking forward to comments and discussion on this list.
>>>>>>>=20
>>>>>>> As an occasional I-D reader, I'd appreciate "Implementation =
Status"
>>>>>>> sections, including IPR info.  I don't think anything forbids to =
add
>>>>>>> such sections, if the authors wish.  I'd add a count of the =
number of
>>>>>>> I-Ds that actually have it among the experiment's success =
criteria.
>>>>>>=20
>>>>=20


From loa@pi.nu  Thu Dec 13 07:22:50 2012
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C173421F8812 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:22:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.824
X-Spam-Level: 
X-Spam-Status: No, score=-101.824 tagged_above=-999 required=5 tests=[AWL=-0.775, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3c3XpJ-1ptcR for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:22:50 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 5948821F87EC for <ietf@ietf.org>; Thu, 13 Dec 2012 07:22:47 -0800 (PST)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 6CF458244B for <ietf@ietf.org>; Thu, 13 Dec 2012 16:22:40 +0100 (CET)
Message-ID: <50C9F2C2.1020004@pi.nu>
Date: Thu, 13 Dec 2012 16:22:42 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
In-Reply-To: <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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, 13 Dec 2012 15:22:50 -0000

Folks,

I agree that understanding the implementation status of a draft
sometimes is essential, but not for all drafts and not always.
Today wg chairs do this type of info collection at the shepherd
write-up.

Have anyone thought about how much work goes into compiling this type
of information. There are vendors that by policy decided not to disclose
implementation information, before the implementation is done and the
document has become an RFC.

Most of the time it is possible to to get some understanding, with a
promise not to make the info public and only use it for a rather
cryptic statement in the shepherd write-up - "we know of existing or
intended implementations of this draft".

A second, rather new problem, is that for some drafts the IANA
assignment is the singular most important part of the ID. We have heard
vendors say "We'll wait for the IANA assignment until we implement!"

/Loa


On 2012-12-13 16:10, Adrian Farrel wrote:
> How about...
>
> Start with Yaron's proposal to include in the I-D. This is easy as a starting
> point. Duplicate documentation in wiki may be useful and provide a place to
> track text for inclusion in the next revision.
>
> When/if inclusion in the I-D gets messy, replace text in I-D with pointer to
> wiki.
>
> When/if experiment looks like a success, replace all above with data tracker
> tool and allow it to persist for RFCs.
>
> Adrian
>
>> -----Original Message-----
>> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>> Sent: 13 December 2012 15:05
>> To: Yaron Sheffer
>> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>> Subject: Re: Running code, take 2
>>
>>
>> Le 2012-12-13 à 10:00, Yaron Sheffer a écrit :
>>
>>> Hi Marc,
>>>
>>> I think it's critical that a person reading a draft (e.g. going to
>> http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) will
> have a
>> direct way to check out on the implementation status.
>>>
>>> This is trivial if it's a section in the document. It's simple if it's
> linked from the
>> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF insiders will
> be
>> aware of it.
>>>
>>
>> sure. Let me restart:
>> - I like Adrian proposal: instead of in RFC, put it online within our site
>> - but you wrote: requires implementation effort.
>> - I replied: well, phase 1 (of put it online within our site) can be done with
> almost
>> zero implementation effort. phase 2 requires some work (I'd say not that big)
> for
>> implementation/tools.
>>
>> Regards, Marc.
>>
>>> Thanks,
>>> 	Yaron
>>>
>>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>>>
>>>> Le 2012-12-13 à 09:52, Yaron Sheffer a écrit :
>>>>
>>>>> Hi Adrian,
>>>>>
>>>>> I would suggest to start with my proposal, because it requires zero
>> implementation effort.
>>>>
>>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget within data
>> tracker.
>>>>
>>>> Marc.
>>>>
>>>>
>>>>> If this catches on, I see a lot of value in your proposal.
>>>>>
>>>>> Please also note that the "implementation status" section (according to my
>> proposal) is not "frozen" when published as an RFC, rather it is deleted. RFCs
> are
>> forever, and I think a point-in-time implementation status is not appropriate
> in an
>> RFC.
>>>>>
>>>>> Thanks,
>>>>> 	Yaron
>>>>>
>>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>>>> I'm interested in this idea.
>>>>>>
>>>>>> However, I note that an "implementation status" section of a document is
>> frozen
>>>>>> in time when a document goes to RFC.
>>>>>>
>>>>>> I wonder whether we could leverage our tools and do something similar to
>> IPR
>>>>>> disclosures. That is, provide a semi-formal web page where implementation
>>>>>> details could be recorded and updated. These would then be searchable
>> and linked
>>>>>> to from the tools page for the I-D / RFC.
>>>>>>
>>>>>> They could record the document version that has been implemented, and
>> also allow
>>>>>> space for other notes.
>>>>>>
>>>>>> Adrian (Just thinking aloud)
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>>>>>> Alessandro Vesely
>>>>>>> Sent: 13 December 2012 13:58
>>>>>>> To: ietf@ietf.org
>>>>>>> Subject: Re: Running code, take 2
>>>>>>>
>>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>>>
>>>>>>>> I have just published a draft that proposes an alternative to
>>>>>>>> Stephen's "fast track". My proposal simply allows authors to document,
>>>>>>>> in a semi-standard way, whatever implementations exist for their
>>>>>>>> protocol, as well as their interoperability.
>>>>>>>>
>>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>>>
>>>>>>>> [...]
>>>>>>>>
>>>>>>>> I am looking forward to comments and discussion on this list.
>>>>>>>
>>>>>>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>>>>>>> sections, including IPR info.  I don't think anything forbids to add
>>>>>>> such sections, if the authors wish.  I'd add a count of the number of
>>>>>>> I-Ds that actually have it among the experiment's success criteria.
>>>>>>
>>>>
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From marc.blanchet@viagenie.ca  Thu Dec 13 07:39:28 2012
Return-Path: <marc.blanchet@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 E27B421F87FD for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:39:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vgM9TGA1jEgA for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 07:39:28 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id DB75A21F87CC for <ietf@ietf.org>; Thu, 13 Dec 2012 07:39:27 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 594E7400C5; Thu, 13 Dec 2012 10:39:17 -0500 (EST)
Subject: Re: Running code, take 2
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <50C9F2C2.1020004@pi.nu>
Date: Thu, 13 Dec 2012 10:39:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D20F60AB-3E90-4342-B13C-7572118EF014@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk> <50C9F2C2.1020004@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1283)
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, 13 Dec 2012 15:39:29 -0000

Le 2012-12-13 =E0 10:22, Loa Andersson a =E9crit :

> Folks,
>=20
> I agree that understanding the implementation status of a draft
> sometimes is essential, but not for all drafts and not always.
> Today wg chairs do this type of info collection at the shepherd
> write-up.
>=20
> Have anyone thought about how much work goes into compiling this type
> of information. There are vendors that by policy decided not to =
disclose
> implementation information, before the implementation is done and the
> document has become an RFC.
>=20
> Most of the time it is possible to to get some understanding, with a
> promise not to make the info public and only use it for a rather
> cryptic statement in the shepherd write-up - "we know of existing or
> intended implementations of this draft".
>=20
> A second, rather new problem, is that for some drafts the IANA
> assignment is the singular most important part of the ID. We have =
heard
> vendors say "We'll wait for the IANA assignment until we implement!"
>=20

right. but that does not preclude doing the proposal. What you are =
saying is that maybe the info (in draft, wiki, tracker) may not be =
complete since some may not disclose. But the available information =
would be valuable.

Marc.


> /Loa
>=20
>=20
> On 2012-12-13 16:10, Adrian Farrel wrote:
>> How about...
>>=20
>> Start with Yaron's proposal to include in the I-D. This is easy as a =
starting
>> point. Duplicate documentation in wiki may be useful and provide a =
place to
>> track text for inclusion in the next revision.
>>=20
>> When/if inclusion in the I-D gets messy, replace text in I-D with =
pointer to
>> wiki.
>>=20
>> When/if experiment looks like a success, replace all above with data =
tracker
>> tool and allow it to persist for RFCs.
>>=20
>> Adrian
>>=20
>>> -----Original Message-----
>>> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>>> Sent: 13 December 2012 15:05
>>> To: Yaron Sheffer
>>> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>>> Subject: Re: Running code, take 2
>>>=20
>>>=20
>>> Le 2012-12-13 =E0 10:00, Yaron Sheffer a =E9crit :
>>>=20
>>>> Hi Marc,
>>>>=20
>>>> I think it's critical that a person reading a draft (e.g. going to
>>> =
http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) =
will
>> have a
>>> direct way to check out on the implementation status.
>>>>=20
>>>> This is trivial if it's a section in the document. It's simple if =
it's
>> linked from the
>>> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF =
insiders will
>> be
>>> aware of it.
>>>>=20
>>>=20
>>> sure. Let me restart:
>>> - I like Adrian proposal: instead of in RFC, put it online within =
our site
>>> - but you wrote: requires implementation effort.
>>> - I replied: well, phase 1 (of put it online within our site) can be =
done with
>> almost
>>> zero implementation effort. phase 2 requires some work (I'd say not =
that big)
>> for
>>> implementation/tools.
>>>=20
>>> Regards, Marc.
>>>=20
>>>> Thanks,
>>>> 	Yaron
>>>>=20
>>>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>>>>=20
>>>>> Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :
>>>>>=20
>>>>>> Hi Adrian,
>>>>>>=20
>>>>>> I would suggest to start with my proposal, because it requires =
zero
>>> implementation effort.
>>>>>=20
>>>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget =
within data
>>> tracker.
>>>>>=20
>>>>> Marc.
>>>>>=20
>>>>>=20
>>>>>> If this catches on, I see a lot of value in your proposal.
>>>>>>=20
>>>>>> Please also note that the "implementation status" section =
(according to my
>>> proposal) is not "frozen" when published as an RFC, rather it is =
deleted. RFCs
>> are
>>> forever, and I think a point-in-time implementation status is not =
appropriate
>> in an
>>> RFC.
>>>>>>=20
>>>>>> Thanks,
>>>>>> 	Yaron
>>>>>>=20
>>>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>>>>> I'm interested in this idea.
>>>>>>>=20
>>>>>>> However, I note that an "implementation status" section of a =
document is
>>> frozen
>>>>>>> in time when a document goes to RFC.
>>>>>>>=20
>>>>>>> I wonder whether we could leverage our tools and do something =
similar to
>>> IPR
>>>>>>> disclosures. That is, provide a semi-formal web page where =
implementation
>>>>>>> details could be recorded and updated. These would then be =
searchable
>>> and linked
>>>>>>> to from the tools page for the I-D / RFC.
>>>>>>>=20
>>>>>>> They could record the document version that has been =
implemented, and
>>> also allow
>>>>>>> space for other notes.
>>>>>>>=20
>>>>>>> Adrian (Just thinking aloud)
>>>>>>>=20
>>>>>>>> -----Original Message-----
>>>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On =
Behalf Of
>>>>>>>> Alessandro Vesely
>>>>>>>> Sent: 13 December 2012 13:58
>>>>>>>> To: ietf@ietf.org
>>>>>>>> Subject: Re: Running code, take 2
>>>>>>>>=20
>>>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>>>>=20
>>>>>>>>> I have just published a draft that proposes an alternative to
>>>>>>>>> Stephen's "fast track". My proposal simply allows authors to =
document,
>>>>>>>>> in a semi-standard way, whatever implementations exist for =
their
>>>>>>>>> protocol, as well as their interoperability.
>>>>>>>>>=20
>>>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>>>>=20
>>>>>>>>> [...]
>>>>>>>>>=20
>>>>>>>>> I am looking forward to comments and discussion on this list.
>>>>>>>>=20
>>>>>>>> As an occasional I-D reader, I'd appreciate "Implementation =
Status"
>>>>>>>> sections, including IPR info.  I don't think anything forbids =
to add
>>>>>>>> such sections, if the authors wish.  I'd add a count of the =
number of
>>>>>>>> I-Ds that actually have it among the experiment's success =
criteria.
>>>>>>>=20
>>>>>=20
>>=20
>=20
> --=20
>=20
>=20
> Loa Andersson                         email: =
loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13


From yaronf.ietf@gmail.com  Thu Dec 13 08:00:35 2012
Return-Path: <yaronf.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 DF70B21F8B93 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 08:00:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.931
X-Spam-Level: 
X-Spam-Status: No, score=-102.931 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FdRywvzKKHI1 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 08:00:23 -0800 (PST)
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by ietfa.amsl.com (Postfix) with ESMTP id 928C321F8BA7 for <ietf@ietf.org>; Thu, 13 Dec 2012 08:00:22 -0800 (PST)
Received: by mail-wi0-f174.google.com with SMTP id hm9so4183491wib.13 for <ietf@ietf.org>; Thu, 13 Dec 2012 08:00:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=user-agent:in-reply-to:references:mime-version:content-type:subject :from:date:to:cc:message-id; bh=GJ6HfQw3y6ZvKN4dqWEdDt2Wm0y00ANo2i7Gr9Hdo5E=; b=Uba4E7PQKAgTEsr3tUcYXWSQXpXBJ2LJMY7L7x+9z4RavUTwIk6OIrPv/P0HyzXsLv FWfsmvmrPnUFjMi9gk3yRq7tXUbZfCIdWtZkU0vXCQXIrPOjYQ4wmsPkIG9FufRAO/Ir 3exbEsQ+nLv8Hi73fB9Ph94eD5OA2eNPVPyRF4l8LY42Zv+weHuH2vFCS6LhYtjQCOw2 IMz5PMGKQ+WRaEWchxmFC8PRYoyBMi8xzS+Tcqo6l+BN1YWmt/iDOlC2hRWz9vpgkFns Xeu3VaUDlwVMlFE5wMLEq001lDEi7pOMquEf1uc4OqPm1GDRexN3oR8LHAfYMx9yielE /c3w==
Received: by 10.181.11.234 with SMTP id el10mr29929506wid.7.1355414422267; Thu, 13 Dec 2012 08:00:22 -0800 (PST)
Received: from [10.0.0.7] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id p3sm8336662wic.8.2012.12.13.08.00.19 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 08:00:21 -0800 (PST)
User-Agent: K-9 Mail for Android
In-Reply-To: <009c01cdd944$6c9f11a0$45dd34e0$@olddog.co.uk>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk> <50C9F03A.5090506@gmail.com> <009c01cdd944$6c9f11a0$45dd34e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----ZBSQUACOIYMDIGPTAJOTFTMKYOPJUT"
Subject: RE: Running code, take 2
From: Yaron Sheffer <yaronf.ietf@gmail.com>
Date: Thu, 13 Dec 2012 17:35:08 +0200
To: adrian@olddog.co.uk,Adrian Farrel <adrian@olddog.co.uk>
Message-ID: <b2d64b6c-1886-4362-8154-ee4589458dbb@email.android.com>
Cc: ietf@ietf.org, 'Alessandro Vesely' <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 16:00:36 -0000

------ZBSQUACOIYMDIGPTAJOTFTMKYOPJUT
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

Sure.

Adrian Farrel <adrian@olddog.co.uk> wrote:

>Yaron,
>
>Would you be willing to add this to your I-D?
>
>> -----Original Message-----
>> From: Yaron Sheffer [mailto:yaronf.ietf@gmail.com]
>> Sent: 13 December 2012 15:12
>> To: adrian@olddog.co.uk
>> Cc: 'Marc Blanchet'; ietf@ietf.org; 'Alessandro Vesely'
>> Subject: Re: Running code, take 2
>> 
>> +1.
>> 
>> 	Yaron
>> 
>> On 12/13/2012 05:10 PM, Adrian Farrel wrote:
>> > How about...
>> >
>> > Start with Yaron's proposal to include in the I-D. This is easy as
>a
>starting
>> > point. Duplicate documentation in wiki may be useful and provide a
>place to
>> > track text for inclusion in the next revision.
>> >
>> > When/if inclusion in the I-D gets messy, replace text in I-D with
>pointer to
>> > wiki.
>> >
>> > When/if experiment looks like a success, replace all above with
>data tracker
>> > tool and allow it to persist for RFCs.
>> >
>> > Adrian
>> >
>> >> -----Original Message-----
>> >> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>> >> Sent: 13 December 2012 15:05
>> >> To: Yaron Sheffer
>> >> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>> >> Subject: Re: Running code, take 2
>> >>
>> >>
>> >> Le 2012-12-13 Ã  10:00, Yaron Sheffer a Ã©crit :
>> >>
>> >>> Hi Marc,
>> >>>
>> >>> I think it's critical that a person reading a draft (e.g. going
>to
>> >>
>http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01)
>will
>> > have a
>> >> direct way to check out on the implementation status.
>> >>>
>> >>> This is trivial if it's a section in the document. It's simple if
>it's
>> > linked from the
>> >> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF
>insiders
>will
>> > be
>> >> aware of it.
>> >>>
>> >>
>> >> sure. Let me restart:
>> >> - I like Adrian proposal: instead of in RFC, put it online within
>our site
>> >> - but you wrote: requires implementation effort.
>> >> - I replied: well, phase 1 (of put it online within our site) can
>be done
>with
>> > almost
>> >> zero implementation effort. phase 2 requires some work (I'd say
>not that
>big)
>> > for
>> >> implementation/tools.
>> >>
>> >> Regards, Marc.
>> >>
>> >>> Thanks,
>> >>> 	Yaron
>> >>>
>> >>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>> >>>>
>> >>>> Le 2012-12-13 Ã  09:52, Yaron Sheffer a Ã©crit :
>> >>>>
>> >>>>> Hi Adrian,
>> >>>>>
>> >>>>> I would suggest to start with my proposal, because it requires
>zero
>> >> implementation effort.
>> >>>>
>> >>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget
>within data
>> >> tracker.
>> >>>>
>> >>>> Marc.
>> >>>>
>> >>>>
>> >>>>> If this catches on, I see a lot of value in your proposal.
>> >>>>>
>> >>>>> Please also note that the "implementation status" section
>(according to
>> my
>> >> proposal) is not "frozen" when published as an RFC, rather it is
>deleted.
>RFCs
>> > are
>> >> forever, and I think a point-in-time implementation status is not
>appropriate
>> > in an
>> >> RFC.
>> >>>>>
>> >>>>> Thanks,
>> >>>>> 	Yaron
>> >>>>>
>> >>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>> >>>>>> I'm interested in this idea.
>> >>>>>>
>> >>>>>> However, I note that an "implementation status" section of a
>document
>> is
>> >> frozen
>> >>>>>> in time when a document goes to RFC.
>> >>>>>>
>> >>>>>> I wonder whether we could leverage our tools and do something
>similar
>> to
>> >> IPR
>> >>>>>> disclosures. That is, provide a semi-formal web page where
>> implementation
>> >>>>>> details could be recorded and updated. These would then be
>searchable
>> >> and linked
>> >>>>>> to from the tools page for the I-D / RFC.
>> >>>>>>
>> >>>>>> They could record the document version that has been
>implemented,
>> and
>> >> also allow
>> >>>>>> space for other notes.
>> >>>>>>
>> >>>>>> Adrian (Just thinking aloud)
>> >>>>>>
>> >>>>>>> -----Original Message-----
>> >>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
>Behalf
>> Of
>> >>>>>>> Alessandro Vesely
>> >>>>>>> Sent: 13 December 2012 13:58
>> >>>>>>> To: ietf@ietf.org
>> >>>>>>> Subject: Re: Running code, take 2
>> >>>>>>>
>> >>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>> >>>>>>>>
>> >>>>>>>> I have just published a draft that proposes an alternative
>to
>> >>>>>>>> Stephen's "fast track". My proposal simply allows authors to
>> document,
>> >>>>>>>> in a semi-standard way, whatever implementations exist for
>their
>> >>>>>>>> protocol, as well as their interoperability.
>> >>>>>>>>
>> >>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>> >>>>>>>>
>> >>>>>>>> [...]
>> >>>>>>>>
>> >>>>>>>> I am looking forward to comments and discussion on this
>list.
>> >>>>>>>
>> >>>>>>> As an occasional I-D reader, I'd appreciate "Implementation
>Status"
>> >>>>>>> sections, including IPR info.  I don't think anything forbids
>to add
>> >>>>>>> such sections, if the authors wish.  I'd add a count of the
>number of
>> >>>>>>> I-Ds that actually have it among the experiment's success
>criteria.
>> >>>>>>
>> >>>>
>> >

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
------ZBSQUACOIYMDIGPTAJOTFTMKYOPJUT
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head/><body><html><head></head><body>Sure.<br><br><div class="gmail_quote">Adrian Farrel &lt;adrian@olddog.co.uk&gt; wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">Yaron,<br /><br />Would you be willing to add this to your I-D?<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">-----Original Message-----<br />From: Yaron Sheffer [mailto:yaronf.ietf@gmail.com]<br />Sent: 13 December 2012 15:12<br />To: adrian@olddog.co.uk<br />Cc: 'Marc Blanchet'; ietf@ietf.org; 'Alessandro Vesely'<br />Subject: Re: Running code, take 2<br /><br />+1.<br /><br /> Yaron<br /><br />On 12/13/2012 05:10 PM, Adrian Farrel wrote:<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">How about...<br /><br />Start with Yaron's proposal to include in the I-D. This is easy as a<br /></blockquote></blockquote>starting<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf;
padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">point. Duplicate documentation in wiki may be useful and provide a place to<br />track text for inclusion in the next revision.<br /><br />When/if inclusion in the I-D gets messy, replace text in I-D with pointer to<br />wiki.<br /><br />When/if experiment looks like a success, replace all above with data tracker<br />tool and allow it to persist for RFCs.<br /><br />Adrian<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">-----Original Message-----<br />From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]<br />Sent: 13 December 2012 15:05<br />To: Yaron Sheffer<br />Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'<br />Subject: Re: Running code, take 2<br /><br /><br />Le 2012-12-13 Ã  10:00, Yaron Sheffer a Ã©crit :<br /><br /><blockquote
class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;">Hi Marc,<br /><br />I think it's critical that a person reading a draft (e.g. going to<br /></blockquote><a href="http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01">http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01</a>) will<br /></blockquote>have a<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">direct way to check out on the implementation status.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;">This is trivial if it's a section in the document. It's simple if it's<br /></blockquote></blockquote>linked from the<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">Tools page. Otherwise, e.g. if you put it on the 
 wiki,
only IETF insiders<br /></blockquote></blockquote></blockquote>will<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">be<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">aware of it.<br /><br /><br />sure. Let me restart:<br />- I like Adrian proposal: instead of in RFC, put it online within our site<br />- but you wrote: requires implementation effort.<br />- I replied: well, phase 1 (of put it online within our site) can be done<br /></blockquote></blockquote></blockquote>with<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left:
1ex;">almost<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">zero implementation effort. phase 2 requires some work (I'd say not that<br /></blockquote></blockquote></blockquote>big)<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">for<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">implementation/tools.<br /><br />Regards, Marc.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;">Thanks,<br /> Yaron<br /><br />On 12/13/2012 04:55 PM, Marc Blanchet wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e;
padding-left: 1ex;">Le 2012-12-13 Ã  09:52, Yaron Sheffer a Ã©crit :<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">Hi Adrian,<br /><br />I would suggest to start with my proposal, because it requires zero<br /></blockquote></blockquote></blockquote>implementation effort.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;">disagree. phase 1: use IETF wiki. phase 2: develop an widget within data<br /></blockquote></blockquote>tracker.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;">Marc.<br /><br /><br /><blockqu
 ote
class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">If this catches on, I see a lot of value in your proposal.<br /><br />Please also note that the "implementation status" section (according to<br /></blockquote></blockquote></blockquote></blockquote></blockquote>my<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">proposal) is not "frozen" when published as an RFC, rather it is deleted.<br /></blockquote></blockquote></blockquote>RFCs<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">are<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex
  0.8ex;
border-left: 1px solid #8ae234; padding-left: 1ex;">forever, and I think a point-in-time implementation status is not<br /></blockquote></blockquote></blockquote>appropriate<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;">in an<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">RFC.<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">Thanks,<br /> Yaron<br /><br />On 12/13/2012 04:16 PM, Adrian Farrel wrote:<br
/><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">I'm interested in this idea.<br /><br />However, I note that an "implementation status" section of a document<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>is<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">frozen<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-
 left:
1px solid #ccc; padding-left: 1ex;">in time when a document goes to RFC.<br /><br />I wonder whether we could leverage our tools and do something similar<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>to<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">IPR<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">disclosures. That is, provide a
semi-formal web page where<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>implementation<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">details could be recorded and updated. These would then be searchable<br /></blockquote></blockquote></blockquote></blockquote>and linked<br /><blockquote
class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">to from the tools page for the I-D / RFC.<br /><br />They could record the document version that has been implemented,<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>and<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;">also allow<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-
 left:
1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">space for other notes.<br /><br />Adrian (Just thinking aloud)<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">-----Original Message-----<br />From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>Of<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8
 ae234;
padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">Alessandro Vesely<br />Sent: 13 December 2012 13:58<br />To: ietf@ietf.org<br />Subject: Re: Running code, take 2<br /><br />On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">I have just published a draft that proposes an alternative to<br />Stephen's "fast 
 track".
My proposal simply allows authors to<br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>document,<br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;"><blockquote
class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ccc; padding-left: 1ex;">in a semi-standard way, whatever implementations exist for their<br />protocol, as well as their interoperability.<br /><br /><a href="http://www.ietf.org/id/draft-sheffer-running-code-00.txt">http://www.ietf.org/id/draft-sheffer-running-code-00.txt</a><br /><br />[...]<br /><br />I am looking forward to comments and discussion on this list.</blockquote><br />As an occasional I-D reader, I'd appreciate "Implementation Status"<br />sections, including IPR info.  I don't think anything forbids to add<br />such sections, if the authors wish.  I'd add a count of the number of<br />I-Ds that actually have it among the experiment's success criteria.</blockquote><br /><br /><br /><br /></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></pre></blockquote></div><br>
-- <br>
Sent from my Android phone with K-9 Mail. Please excuse my brevity.</body></html></body></html>
------ZBSQUACOIYMDIGPTAJOTFTMKYOPJUT--


From ted.ietf@gmail.com  Thu Dec 13 08:01:59 2012
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 7355921F8BA9 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 08:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.451
X-Spam-Level: 
X-Spam-Status: No, score=-3.451 tagged_above=-999 required=5 tests=[AWL=0.147,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d-NOhVG0-xyI for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 08:01:58 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5A60621F8B5E for <ietf@ietf.org>; Thu, 13 Dec 2012 08:01:58 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so2535388vcb.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 08:01:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QaZiFRwU/t1MVJHiFS4s7rxNq9B/Ki6zVX/VRmfOVo0=; b=Pdsd/SBzg2qGx2NN0/RYtsKPcdBvf4uLBHkQ5MGInvRzk8BmlIbaStuzVlR9Fg/UaR Xygz2xE8b0lzAPyKbC7AEUPvzTA2X4aw0vbO/brEy+aPATWipWlJb/u3sMw9eMVfaUrB vJhQeH3aibVgxcu9f9HE3gzLixvWH3e/gKXpQhcIMKZ4Sca3PLZT0TGl+hvqxH5gan7T 3zhE3LqA9SzPWoRAGk0y2f5SFfdgseUaxsDLirUTQHD4YfcmSO1W5NkmKnkXLjNh19Zd jIp9Rs9a/S+CRt10e0eoXYVYRFoCwSP7uzEK8qeRWSqA7+HGFLIl55JuhLwLityu0y/7 YWNQ==
MIME-Version: 1.0
Received: by 10.52.36.167 with SMTP id r7mr3512252vdj.108.1355414517540; Thu, 13 Dec 2012 08:01:57 -0800 (PST)
Received: by 10.58.164.35 with HTTP; Thu, 13 Dec 2012 08:01:57 -0800 (PST)
In-Reply-To: <50C8DB78.3080905@gmail.com>
References: <50C8DB78.3080905@gmail.com>
Date: Thu, 13 Dec 2012 08:01:57 -0800
Message-ID: <CA+9kkMDa6WACEpWPgMuO=QL-QAMGhjemti3qgiR_Otb0fK6ZhA@mail.gmail.com>
Subject: Re: Running code, take 2
From: Ted Hardie <ted.ietf@gmail.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=20cf30780ca4d768e404d0be08bc
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, 13 Dec 2012 16:01:59 -0000

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

Hi Yaron,

Reading through this draft, I note that you're suggesting inclusion of
information about the type of implementation license (open source,
proprietary, etc.).  While that may be useful, I'd be more interested in
knowing whether the implementation represents an exercise of any licenses
required by IPR disclosures for the relevant draft.  Since there are
implementations (even open source implementations) that might be submitted
by the same organization holding the IPR, this is not something you can
automatically infer.  There are also, of course, cases where an implementor
does not agree that an IPR statement's claim of coverage is correct.

Before we eliminated the requirements for demonstrating two interoperable
implementations at Draft, one piece of that requirement was that the two
being used represent different exercises of any license.  If we are going
to start tracking implementations, it might be useful to get that data back.

regards,

Ted Hardie

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

Hi Yaron,<br><br>Reading through this draft, I note that you&#39;re suggest=
ing inclusion of information about the type of implementation license (open=
 source, proprietary, etc.).=A0 While that may be useful, I&#39;d be more i=
nterested in knowing whether the implementation represents an exercise of a=
ny licenses required by IPR disclosures for the relevant draft.=A0 Since th=
ere are implementations (even open source implementations) that might be su=
bmitted by the same organization holding the IPR, this is not something you=
 can automatically infer.=A0 There are also, of course, cases where an impl=
ementor does not agree that an IPR statement&#39;s claim of coverage is cor=
rect.<br>
<br>Before we eliminated the requirements for demonstrating two interoperab=
le implementations at Draft, one piece of that requirement was that the two=
 being used represent different exercises of any license.=A0 If we are goin=
g to start tracking implementations, it might be useful to get that data ba=
ck.<br>
<br>regards,<br><br>Ted Hardie<br>

--20cf30780ca4d768e404d0be08bc--

From loa@pi.nu  Thu Dec 13 08:10:19 2012
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6038321F8529 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 08:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.768
X-Spam-Level: 
X-Spam-Status: No, score=-101.768 tagged_above=-999 required=5 tests=[AWL=-0.720, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHWD0wbpThsO for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 08:10:18 -0800 (PST)
Received: from mail.pi.nu (unknown [195.206.248.139]) by ietfa.amsl.com (Postfix) with ESMTP id 1937C21F8499 for <ietf@ietf.org>; Thu, 13 Dec 2012 08:10:17 -0800 (PST)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.pi.nu (Postfix) with ESMTPSA id 6D2D08244B; Thu, 13 Dec 2012 17:10:14 +0100 (CET)
Message-ID: <50C9FDE8.3090600@pi.nu>
Date: Thu, 13 Dec 2012 17:10:16 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca> <50C9ED7B.2010009@gmail.com> <6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca> <009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk> <50C9F2C2.1020004@pi.nu> <D20F60AB-3E90-4342-B13C-7572118EF014@viagenie.ca>
In-Reply-To: <D20F60AB-3E90-4342-B13C-7572118EF014@viagenie.ca>
Content-Type: text/plain; charset=ISO-8859-1; 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, 13 Dec 2012 16:10:19 -0000

Marc,

inline please!

On 2012-12-13 16:39, Marc Blanchet wrote:
>
> Le 2012-12-13 à 10:22, Loa Andersson a écrit :
>
>> Folks,
>>
>> I agree that understanding the implementation status of a draft
>> sometimes is essential, but not for all drafts and not always.
>> Today wg chairs do this type of info collection at the shepherd
>> write-up.
>>
>> Have anyone thought about how much work goes into compiling this type
>> of information. There are vendors that by policy decided not to disclose
>> implementation information, before the implementation is done and the
>> document has become an RFC.
>>
>> Most of the time it is possible to to get some understanding, with a
>> promise not to make the info public and only use it for a rather
>> cryptic statement in the shepherd write-up - "we know of existing or
>> intended implementations of this draft".
>>
>> A second, rather new problem, is that for some drafts the IANA
>> assignment is the singular most important part of the ID. We have heard
>> vendors say "We'll wait for the IANA assignment until we implement!"
>>
>
> right. but that does not preclude doing the proposal. What you are saying is that maybe the info (in draft, wiki, tracker) may not be complete since some may not disclose. But the available information would be valuable.
>
> Marc.

that entirely depends on the policy of the 4-5 dominating vendors in the
area that the draft is applicable for. I know of people writing drafts
there their own companies say that they can disclose implementation
information in public. Why would anyone else want to supply their
information to that draft.

I think the key word here is "in public", a trustful relationship
between working group chairs gives you enough information to progress
the document through the IESG, I'm afraid that this will be much harder
if we have an empty (or single company) "Implementation Status"
section in the drafts.

/Loa
>
>
>> /Loa
>>
>>
>> On 2012-12-13 16:10, Adrian Farrel wrote:
>>> How about...
>>>
>>> Start with Yaron's proposal to include in the I-D. This is easy as a starting
>>> point. Duplicate documentation in wiki may be useful and provide a place to
>>> track text for inclusion in the next revision.
>>>
>>> When/if inclusion in the I-D gets messy, replace text in I-D with pointer to
>>> wiki.
>>>
>>> When/if experiment looks like a success, replace all above with data tracker
>>> tool and allow it to persist for RFCs.
>>>
>>> Adrian
>>>
>>>> -----Original Message-----
>>>> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>>>> Sent: 13 December 2012 15:05
>>>> To: Yaron Sheffer
>>>> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>>>> Subject: Re: Running code, take 2
>>>>
>>>>
>>>> Le 2012-12-13 à 10:00, Yaron Sheffer a écrit :
>>>>
>>>>> Hi Marc,
>>>>>
>>>>> I think it's critical that a person reading a draft (e.g. going to
>>>> http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01) will
>>> have a
>>>> direct way to check out on the implementation status.
>>>>>
>>>>> This is trivial if it's a section in the document. It's simple if it's
>>> linked from the
>>>> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF insiders will
>>> be
>>>> aware of it.
>>>>>
>>>>
>>>> sure. Let me restart:
>>>> - I like Adrian proposal: instead of in RFC, put it online within our site
>>>> - but you wrote: requires implementation effort.
>>>> - I replied: well, phase 1 (of put it online within our site) can be done with
>>> almost
>>>> zero implementation effort. phase 2 requires some work (I'd say not that big)
>>> for
>>>> implementation/tools.
>>>>
>>>> Regards, Marc.
>>>>
>>>>> Thanks,
>>>>> 	Yaron
>>>>>
>>>>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>>>>>
>>>>>> Le 2012-12-13 à 09:52, Yaron Sheffer a écrit :
>>>>>>
>>>>>>> Hi Adrian,
>>>>>>>
>>>>>>> I would suggest to start with my proposal, because it requires zero
>>>> implementation effort.
>>>>>>
>>>>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget within data
>>>> tracker.
>>>>>>
>>>>>> Marc.
>>>>>>
>>>>>>
>>>>>>> If this catches on, I see a lot of value in your proposal.
>>>>>>>
>>>>>>> Please also note that the "implementation status" section (according to my
>>>> proposal) is not "frozen" when published as an RFC, rather it is deleted. RFCs
>>> are
>>>> forever, and I think a point-in-time implementation status is not appropriate
>>> in an
>>>> RFC.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> 	Yaron
>>>>>>>
>>>>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>>>>>> I'm interested in this idea.
>>>>>>>>
>>>>>>>> However, I note that an "implementation status" section of a document is
>>>> frozen
>>>>>>>> in time when a document goes to RFC.
>>>>>>>>
>>>>>>>> I wonder whether we could leverage our tools and do something similar to
>>>> IPR
>>>>>>>> disclosures. That is, provide a semi-formal web page where implementation
>>>>>>>> details could be recorded and updated. These would then be searchable
>>>> and linked
>>>>>>>> to from the tools page for the I-D / RFC.
>>>>>>>>
>>>>>>>> They could record the document version that has been implemented, and
>>>> also allow
>>>>>>>> space for other notes.
>>>>>>>>
>>>>>>>> Adrian (Just thinking aloud)
>>>>>>>>
>>>>>>>>> -----Original Message-----
>>>>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>>>>>>>> Alessandro Vesely
>>>>>>>>> Sent: 13 December 2012 13:58
>>>>>>>>> To: ietf@ietf.org
>>>>>>>>> Subject: Re: Running code, take 2
>>>>>>>>>
>>>>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>>>>>
>>>>>>>>>> I have just published a draft that proposes an alternative to
>>>>>>>>>> Stephen's "fast track". My proposal simply allows authors to document,
>>>>>>>>>> in a semi-standard way, whatever implementations exist for their
>>>>>>>>>> protocol, as well as their interoperability.
>>>>>>>>>>
>>>>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>>>>>
>>>>>>>>>> [...]
>>>>>>>>>>
>>>>>>>>>> I am looking forward to comments and discussion on this list.
>>>>>>>>>
>>>>>>>>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>>>>>>>>> sections, including IPR info.  I don't think anything forbids to add
>>>>>>>>> such sections, if the authors wish.  I'd add a count of the number of
>>>>>>>>> I-Ds that actually have it among the experiment's success criteria.
>>>>>>>>
>>>>>>
>>>
>>
>> --
>>
>>
>> Loa Andersson                         email: loa.andersson@ericsson.com
>> Sr Strategy and Standards Manager            loa@pi.nu
>> Ericsson Inc                          phone: +46 10 717 52 13
>>                                              +46 767 72 92 13
>

-- 


Loa Andersson                         email: loa.andersson@ericsson.com
Sr Strategy and Standards Manager            loa@pi.nu
Ericsson Inc                          phone: +46 10 717 52 13
                                              +46 767 72 92 13

From melinda.shore@gmail.com  Thu Dec 13 10:04:39 2012
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 1F6F721F8AD0 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:04:39 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nMfP2+YGQL-5 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:04:38 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id A30AD21F8ACA for <ietf@ietf.org>; Thu, 13 Dec 2012 10:04:24 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so901679dae.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 10:04:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=uOvqxCkTRTds8MKMnYDl+LMpjsXjbBS4hgrANh6wucU=; b=0pFXZ4UCWqvPbr4E2nwePDokcI3WB5wDNAvXPutw/4c6ZxrSQ2KO9cvlisu+Z5nnCH RPjEzTM+lIcyzAOz3/HOxjIlc38UKMs5gY6j5SN9XxsLEaAJ6/A6HzCK0CA98iIeBwsD SX0ebi4fDMYF/3B6q5op0542rqkWU96sOvdaChlnGgmemLDSrlRZld974tEBglq2ZMKc p93qIXyo4p6xsnfD3b6roqTvxkuFZOWiXAeqchXUhwme4e70KvI5VKOywhWR0Puw4hyA MaVEOuxioBBfq0U1hPebCK47y+lYZ4yGG7RJ4qYcAYD8Ub5bDl2NJyATGAA2sWB2cEhg YmAA==
Received: by 10.68.231.41 with SMTP id td9mr7591536pbc.128.1355421856808; Thu, 13 Dec 2012 10:04:16 -0800 (PST)
Received: from spandex.local (66-230-80-208-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.208]) by mx.google.com with ESMTPS id uq5sm1380195pbc.56.2012.12.13.10.04.15 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Dec 2012 10:04:16 -0800 (PST)
Message-ID: <50CA189E.1090002@gmail.com>
Date: Thu, 13 Dec 2012 09:04:14 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca>
In-Reply-To: <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca>
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, 13 Dec 2012 18:04:39 -0000

On 12/13/12 5:18 AM, Marc Blanchet wrote:

>Le 2012-12-13 à 09:16, Adrian Farrel a écrit :
>> I wonder whether we could leverage our tools and do something similar to IPR
>> disclosures. That is, provide a semi-formal web page where implementation
>> details could be recorded and updated. These would then be searchable and linked
>> to from the tools page for the I-D / RFC. 
>>
>> They could record the document version that has been implemented, and also allow
>> space for other notes.

> I like that idea.

Me too.

Melinda



From randy@psg.com  Thu Dec 13 10:14:04 2012
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 9DEEE21F899A for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUgHdXyJnBa1 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:14:04 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id E6CF821F8994 for <ietf@ietf.org>; Thu, 13 Dec 2012 10:14:03 -0800 (PST)
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 1TjDI8-000LwN-Nf; Thu, 13 Dec 2012 18:13:52 +0000
Date: Thu, 13 Dec 2012 10:13:54 -0800
Message-ID: <m2sj79zuot.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Running code, take 2
In-Reply-To: <50CA189E.1090002@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 18:14:04 -0000

don't we already have a way of doing this?  implementation reports, e.g.

    draft-ietf-sidr-rpki-rtr-impl-01.txt

a wiki can be more easily curated, though has authorization challenges.

could you clue me into how the different modes would facilitate progress
of the base document(s)?

randy

From melinda.shore@gmail.com  Thu Dec 13 10:19:59 2012
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 DDB5B21F89B6 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:19:59 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f+H0z6rphyvi for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:19:59 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1063C21F899A for <ietf@ietf.org>; Thu, 13 Dec 2012 10:19:58 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so908554dae.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 10:19:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=0tncaK8G+XMt3INmqHjhYzPhwdWztoAVbCtybHWeunQ=; b=BZ+5mbvXyCNHisWodqhwgTipWsOB8N1EMbXweuaPYzpLzGdT0Cdeg0/9CDnDESoHM9 7YvoGl8NMuxIuzOYIV6TU42CL6Amwxtasvs6M2ID0cIqta7ERKrRXrANg+6lgd5W9D7D aH+CpLM6YqGX2iKDz/lnsansvjFK1ucoeiKmr5seC+zbRO+5Y/CV+dK00Ivf4F8vir0R 4bUkwpIoB51zhCKJvD/zkPtHOTjxojIWwg7Gxw0dO4irblcrnaT6DQ7BWrEde+/qK84O cpD//GrSAcFImTpR5qROlDVwEQyTVkLlY34lw4Jk1HDITix4LOjpWNkBC03CLbHBl0PG z32A==
Received: by 10.68.194.6 with SMTP id hs6mr7865471pbc.77.1355422798610; Thu, 13 Dec 2012 10:19:58 -0800 (PST)
Received: from spandex.local (66-230-80-208-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.208]) by mx.google.com with ESMTPS id m3sm1653531pav.4.2012.12.13.10.19.57 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Dec 2012 10:19:57 -0800 (PST)
Message-ID: <50CA1C4B.8030800@gmail.com>
Date: Thu, 13 Dec 2012 09:19:55 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com>
In-Reply-To: <m2sj79zuot.wl%randy@psg.com>
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, 13 Dec 2012 18:20:00 -0000

On 12/13/12 9:13 AM, Randy Bush wrote:
> don't we already have a way of doing this?  implementation reports, e.g.
> 
>     draft-ietf-sidr-rpki-rtr-impl-01.txt
> 
> a wiki can be more easily curated, though has authorization challenges.
> 
> could you clue me into how the different modes would facilitate progress
> of the base document(s)?

The curation model is that somebody/somebodies take responsibility for
authoring a document and tracking down implementations, writing them
up, etc.  The wiki model is that somebody/somebodies say "Hey!  I've got
an implementation, let me tell you about it."  I don't see why they
can't co-exist, but in the meantime I don't think implementation reports
in the form of internet drafts are that common, and I'd be curious to
see which is more effective at getting information out.

What's the long-term plan for the RPKI implementation report -
publication?

Melinda


From zhou.sujing@zte.com.cn  Wed Dec 12 23:05:15 2012
Return-Path: <zhou.sujing@zte.com.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 43E8021F8436; Wed, 12 Dec 2012 23:05:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.006
X-Spam-Level: 
X-Spam-Status: No, score=-98.006 tagged_above=-999 required=5 tests=[AWL=-0.033, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWFeQNwtEW8J; Wed, 12 Dec 2012 23:05:14 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id E891521F88A9; Wed, 12 Dec 2012 23:05:13 -0800 (PST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id A5A2F13BCF28; Thu, 13 Dec 2012 15:06:54 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id qBD74kYV092049; Thu, 13 Dec 2012 15:04:46 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <20121210183357.31726.20901.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF6C540C57.ED2AF4F6-ON48257AD3.0026BDF7-48257AD3.00270258@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Thu, 13 Dec 2012 15:04:37 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-12-13 15:04:41, Serialize complete at 2012-12-13 15:04:41
Content-Type: multipart/alternative; boundary="=_alternative 0027025648257AD3_="
X-MAIL: mse02.zte.com.cn qBD74kYV092049
X-Mailman-Approved-At: Thu, 13 Dec 2012 10:20:54 -0800
Cc: oauth@ietf.org, IETF-Announce <ietf-announce@ietf.org>, oauth-bounces@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 07:05:15 -0000

This is a multipart message in MIME format.
--=_alternative 0027025648257AD3_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SW4gInNlY3Rpb24gMw0KIFRoZSB0b2tlbiBzZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24gaXNzdWVy
OyBpdHMNCiByb2xlIGlzIHRvIGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBjbGllbnRzLCB3aGljaCBw
cmVzZW50IHZhcmlvdXMNCiBjcmVkZW50aWFscywgYW5kIG1pbnQgYXNzZXJ0aW9ucyBhcyByZXF1
ZXN0ZWQsIGZpbGwgdGhlbSB3aXRoDQogYXBwcm9wcmlhdGUgaW5mb3JtYXRpb24sIGFuZCBzaWdu
IHRoZW0uIg0KDQoNCkFzIEkgdW5kZXJzdGFuZCwgYW4gYXNzZXJ0aW9uIGdlbmVyYXRlZCBieSBh
IFNUUywgaXMgZG9uZSBmbG9sbG93aW5nIHRoZXNzIA0Kc3RlcHM6DQoxLiBDbGllbnQgcHJlc2Vu
dHMgY3JlZGVudGlhbCBhbmQgcmVxdWVzdHMgYW4gYXNzZXJ0aW9uDQoyLiBTVFMgZ2VuZXJhdGVz
IGFzc2VydGlvbiBhbmQgc2VuZHMgdG8gQ2xpZW50DQpDb3JyZWN0Pw0KDQpUaGF0IG1heSByZXN0
cmljdCB0aGUgdXNlIGNhc2VzIHRoYXQgdGhpcyBhc3NlcnRpb24gZnJhbWV3b3JrIGNvdWxkIA0K
c3VwcG9ydCwNCmlzIGl0IGEgbXVzdD8NCg0KDQoNCg0Kb2F1dGgtYm91bmNlc0BpZXRmLm9yZyDQ
tNPaIDIwMTItMTItMTEgMDI6MzM6NTc6DQoNCj4gDQo+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBh
IHJlcXVlc3QgZnJvbSB0aGUgV2ViIEF1dGhvcml6YXRpb24gUHJvdG9jb2wgV0cNCj4gKG9hdXRo
KSB0byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Og0KPiAtICdBc3NlcnRpb24gRnJh
bWV3b3JrIGZvciBPQXV0aCAyLjAnDQo+ICAgPGRyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy0w
OC50eHQ+IGFzIFByb3Bvc2VkIFN0YW5kYXJkDQo+IA0KPiBUaGUgSUVTRyBwbGFucyB0byBtYWtl
IGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMNCj4gZmluYWwg
Y29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRz
IHRvIHRoZQ0KPiBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMgYnkgMjAxMi0xMi0yNC4gRXhj
ZXB0aW9uYWxseSwgY29tbWVudHMgbWF5IA0KYmUNCj4gc2VudCB0byBpZXNnQGlldGYub3JnIGlu
c3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZQ0KPiBiZWdpbm5pbmcgb2Yg
dGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4gDQo+IEFic3Ry
YWN0DQo+IA0KPiANCj4gICAgVGhpcyBzcGVjaWZpY2F0aW9uIHByb3ZpZGVzIGEgZnJhbWV3b3Jr
IGZvciB0aGUgdXNlIG9mIGFzc2VydGlvbnMNCj4gICAgd2l0aCBPQXV0aCAyLjAgaW4gdGhlIGZv
cm0gb2YgYSBuZXcgY2xpZW50IGF1dGhlbnRpY2F0aW9uIG1lY2hhbmlzbQ0KPiAgICBhbmQgYSBu
ZXcgYXV0aG9yaXphdGlvbiBncmFudCB0eXBlLiAgTWVjaGFuaXNtcyBhcmUgc3BlY2lmaWVkIGZv
cg0KPiAgICB0cmFuc3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zIHdpdGgg
YSB0b2tlbiBlbmRwb2ludCwgYXMNCj4gICAgd2VsbCBhcyBnZW5lcmFsIHByb2Nlc3NpbmcgcnVs
ZXMuDQo+IA0KPiAgICBUaGUgaW50ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiBpcyB0byBwcm92
aWRlIGEgY29tbW9uIGZyYW1ld29yayBmb3INCj4gICAgT0F1dGggMi4wIHRvIGludGVyd29yayB3
aXRoIG90aGVyIGlkZW50aXR5IHN5c3RlbXMgdXNpbmcgYXNzZXJ0aW9ucywNCj4gICAgYW5kIHRv
IHByb3ZpZGUgYWx0ZXJuYXRpdmUgY2xpZW50IGF1dGhlbnRpY2F0aW9uIG1lY2hhbmlzbXMuDQo+
IA0KPiAgICBOb3RlIHRoYXQgdGhpcyBzcGVjaWZpY2F0aW9uIG9ubHkgZGVmaW5lcyBhYnN0cmFj
dCBtZXNzYWdlIGZsb3dzIGFuZA0KPiAgICBwcm9jZXNzaW5nIHJ1bGVzLiAgSW4gb3JkZXIgdG8g
YmUgaW1wbGVtZW50YWJsZSwgY29tcGFuaW9uDQo+ICAgIHNwZWNpZmljYXRpb25zIGFyZSBuZWNl
c3NhcnkgdG8gcHJvdmlkZSB0aGUgY29ycmVzcG9uZGluZyBjb25jcmV0ZQ0KPiAgICBpbnN0YW50
aWF0aW9ucy4NCj4gDQo+IA0KPiANCj4gDQo+IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWEN
Cj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2Vy
dGlvbnMvDQo+IA0KPiBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+IGh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zL2Jh
bGxvdC8NCj4gDQo+IA0KPiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQg
ZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+IA0KPiANCj4gX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCj4gT0F1dGggbWFpbGluZyBsaXN0DQo+IE9BdXRoQGll
dGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGgNCg0K
--=_alternative 0027025648257AD3_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yPkluICZxdW90O3NlY3Rpb24gMzwvZm9udD4NCjxicj48Zm9udCBz
aXplPTI+Jm5ic3A7VGhlIHRva2VuIHNlcnZpY2UgaXMgdGhlIGFzc2VydGlvbiBpc3N1ZXI7IGl0
czwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+Jm5ic3A7cm9sZSBpcyB0byBmdWxmaWxsIHJlcXVl
c3RzIGZyb20gY2xpZW50cywgd2hpY2gNCnByZXNlbnQgdmFyaW91czwvZm9udD4NCjxicj48Zm9u
dCBzaXplPTI+Jm5ic3A7Y3JlZGVudGlhbHMsIGFuZCBtaW50IGFzc2VydGlvbnMgYXMgcmVxdWVz
dGVkLCBmaWxsDQp0aGVtIHdpdGg8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yPiZuYnNwO2FwcHJv
cHJpYXRlIGluZm9ybWF0aW9uLCBhbmQgc2lnbiB0aGVtLiZxdW90OzwvZm9udD4NCjxicj4NCjxi
cj4NCjxicj48Zm9udCBzaXplPTI+QXMgSSB1bmRlcnN0YW5kLCBhbiBhc3NlcnRpb24gZ2VuZXJh
dGVkIGJ5IGEgU1RTLCBpcyBkb25lDQpmbG9sbG93aW5nIHRoZXNzIHN0ZXBzOjwvZm9udD4NCjxi
cj48Zm9udCBzaXplPTI+MS4gQ2xpZW50IHByZXNlbnRzIGNyZWRlbnRpYWwgYW5kIHJlcXVlc3Rz
IGFuIGFzc2VydGlvbjwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+Mi4gU1RTIGdlbmVyYXRlcyBh
c3NlcnRpb24gYW5kIHNlbmRzIHRvIENsaWVudDwvZm9udD4NCjxicj48Zm9udCBzaXplPTI+Q29y
cmVjdD88L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yPlRoYXQgbWF5IHJlc3RyaWN0IHRo
ZSB1c2UgY2FzZXMgdGhhdCB0aGlzIGFzc2VydGlvbiBmcmFtZXdvcmsNCmNvdWxkIHN1cHBvcnQs
PC9mb250Pg0KPGJyPjxmb250IHNpemU9Mj5pcyBpdCBhIG11c3Q/PC9mb250Pg0KPGJyPg0KPGJy
Pg0KPGJyPg0KPGJyPg0KPGJyPjx0dD48Zm9udCBzaXplPTI+b2F1dGgtYm91bmNlc0BpZXRmLm9y
ZyDQtNPaIDIwMTItMTItMTEgMDI6MzM6NTc6PGJyPg0KPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRo
ZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSB0aGUgV2ViIEF1dGhvcml6YXRpb24g
UHJvdG9jb2wNCldHPGJyPg0KJmd0OyAob2F1dGgpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcg
ZG9jdW1lbnQ6PGJyPg0KJmd0OyAtICdBc3NlcnRpb24gRnJhbWV3b3JrIGZvciBPQXV0aCAyLjAn
PGJyPg0KJmd0OyAmbmJzcDsgJmx0O2RyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy0wOC50eHQm
Z3Q7IGFzIFByb3Bvc2VkIFN0YW5kYXJkPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRoZSBJRVNHIHBs
YW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFuZCBzb2xpY2l0
czxicj4NCiZndDsgZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBzZW5kIHN1
YnN0YW50aXZlIGNvbW1lbnRzIHRvDQp0aGU8YnI+DQomZ3Q7IGlldGZAaWV0Zi5vcmcgbWFpbGlu
ZyBsaXN0cyBieSAyMDEyLTEyLTI0LiBFeGNlcHRpb25hbGx5LCBjb21tZW50cw0KbWF5IGJlPGJy
Pg0KJmd0OyBzZW50IHRvIGllc2dAaWV0Zi5vcmcgaW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBs
ZWFzZSByZXRhaW4gdGhlPGJyPg0KJmd0OyBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0
byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy48YnI+DQomZ3Q7IDxicj4NCiZndDsgQWJzdHJhY3Q8
YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7VGhpcyBzcGVjaWZp
Y2F0aW9uIHByb3ZpZGVzIGEgZnJhbWV3b3JrIGZvciB0aGUgdXNlIG9mDQphc3NlcnRpb25zPGJy
Pg0KJmd0OyAmbmJzcDsgJm5ic3A7d2l0aCBPQXV0aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBuZXcg
Y2xpZW50IGF1dGhlbnRpY2F0aW9uDQptZWNoYW5pc208YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDth
bmQgYSBuZXcgYXV0aG9yaXphdGlvbiBncmFudCB0eXBlLiAmbmJzcDtNZWNoYW5pc21zDQphcmUg
c3BlY2lmaWVkIGZvcjxicj4NCiZndDsgJm5ic3A7ICZuYnNwO3RyYW5zcG9ydGluZyBhc3NlcnRp
b25zIGR1cmluZyBpbnRlcmFjdGlvbnMgd2l0aCBhIHRva2VuDQplbmRwb2ludCwgYXM8YnI+DQom
Z3Q7ICZuYnNwOyAmbmJzcDt3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBydWxlcy48YnI+DQom
Z3Q7IDxicj4NCiZndDsgJm5ic3A7ICZuYnNwO1RoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0
aW9uIGlzIHRvIHByb3ZpZGUgYSBjb21tb24NCmZyYW1ld29yayBmb3I8YnI+DQomZ3Q7ICZuYnNw
OyAmbmJzcDtPQXV0aCAyLjAgdG8gaW50ZXJ3b3JrIHdpdGggb3RoZXIgaWRlbnRpdHkgc3lzdGVt
cyB1c2luZw0KYXNzZXJ0aW9ucyw8YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDthbmQgdG8gcHJvdmlk
ZSBhbHRlcm5hdGl2ZSBjbGllbnQgYXV0aGVudGljYXRpb24gbWVjaGFuaXNtcy48YnI+DQomZ3Q7
IDxicj4NCiZndDsgJm5ic3A7ICZuYnNwO05vdGUgdGhhdCB0aGlzIHNwZWNpZmljYXRpb24gb25s
eSBkZWZpbmVzIGFic3RyYWN0IG1lc3NhZ2UNCmZsb3dzIGFuZDxicj4NCiZndDsgJm5ic3A7ICZu
YnNwO3Byb2Nlc3NpbmcgcnVsZXMuICZuYnNwO0luIG9yZGVyIHRvIGJlIGltcGxlbWVudGFibGUs
DQpjb21wYW5pb248YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDtzcGVjaWZpY2F0aW9ucyBhcmUgbmVj
ZXNzYXJ5IHRvIHByb3ZpZGUgdGhlIGNvcnJlc3BvbmRpbmcNCmNvbmNyZXRlPGJyPg0KJmd0OyAm
bmJzcDsgJm5ic3A7aW5zdGFudGlhdGlvbnMuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZn
dDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWE8YnI+
DQomZ3Q7IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1h
c3NlcnRpb25zLzxicj4NCiZndDsgPGJyPg0KJmd0OyBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRy
YWNrZWQgdmlhPGJyPg0KJmd0OyBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0
LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy9iYWxsb3QvPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4N
CiZndDsgTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5IG9u
IHRoaXMgSS1ELjxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyBPQXV0aCBtYWlsaW5n
IGxpc3Q8YnI+DQomZ3Q7IE9BdXRoQGlldGYub3JnPGJyPg0KJmd0OyBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoPGJyPg0KPC9mb250PjwvdHQ+DQo=
--=_alternative 0027025648257AD3_=--

From randy@psg.com  Thu Dec 13 10:21:19 2012
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 D337D21F8A8B for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UsVfjXMc7+0k for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 10:21:19 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 35A3421F8A0B for <ietf@ietf.org>; Thu, 13 Dec 2012 10:21:19 -0800 (PST)
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 1TjDPK-000Lye-E4; Thu, 13 Dec 2012 18:21:18 +0000
Date: Thu, 13 Dec 2012 10:21:19 -0800
Message-ID: <m2r4mtzucg.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Running code, take 2
In-Reply-To: <50CA1C4B.8030800@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA1C4B.8030800@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 18:21:20 -0000

> What's the long-term plan for the RPKI implementation report -
> publication?

yes.  it is traditional in the routing area.

randy

From yaronf.ietf@gmail.com  Thu Dec 13 13:52:02 2012
Return-Path: <yaronf.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 D9D0921F8BD7 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 13:52:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.377
X-Spam-Level: 
X-Spam-Status: No, score=-103.377 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uQLupgxj1vL4 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 13:52:02 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id C37BD21F8BD6 for <ietf@ietf.org>; Thu, 13 Dec 2012 13:52:00 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so1604430eek.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 13:51:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hhwQSeKb5dd1w23RGwp7V0OwliN6Xzmr7j174KP4Xq0=; b=D53tfYCbme1EPEcJtnre74enJq4uEfvDm9Bpc66eIl3aOegW2bSIM3I+bn5CPWgZVU 3l4jFQIFd5y9I6xEMcDppMoYllCZf6pSzcSt7lCAcrl34emyx8RH61+tsW4hftCRZP0z 5z9M4zOaxznNwaEOFkk7Q6o47CzVDc90ntWvuojTszI6V+Fp5mgfTajv9xB4MVUxEukL hSI7rQJP+pWZ54WCG/qLewvXaCDTaE8n5KVholyIADbOAniKgYqxioHg0aYesjbD77hG a1PCk33QWsiOcZdq4SieSoKLj9OgPH+1M9UQRxFW9yHrtJXPhwL3yfH1SxdvTevAbfR1 9AfA==
Received: by 10.14.194.195 with SMTP id m43mr8798599een.44.1355435519716; Thu, 13 Dec 2012 13:51:59 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id f49sm5460906eep.12.2012.12.13.13.51.56 (version=SSLv3 cipher=OTHER); Thu, 13 Dec 2012 13:51:58 -0800 (PST)
Message-ID: <50CA4DFA.9050500@gmail.com>
Date: Thu, 13 Dec 2012 23:51:54 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com>
In-Reply-To: <m2sj79zuot.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: Thu, 13 Dec 2012 21:52:03 -0000

Hi Randy,

the RPKI report is very impressive and probably very useful. But:

- Other areas (e.g. the Security Area, where I'm coming form) may not 
have this tradition.

- For "smaller" protocols the gain does not justify the effort of 
writing a separate implementation report. A section in the base document 
is much simpler to maintain.

- And as I noted earlier on this thread, a wiki is a good alternative, 
provided everyone reading the base draft is referred to the 
"implementation status" wiki. They should not have to guess that one 
exists, or to search for it.

Thanks,
	Yaron

On 12/13/2012 08:13 PM, Randy Bush wrote:
> don't we already have a way of doing this?  implementation reports, e.g.
>
>      draft-ietf-sidr-rpki-rtr-impl-01.txt
>
> a wiki can be more easily curated, though has authorization challenges.
>
> could you clue me into how the different modes would facilitate progress
> of the base document(s)?
>
> randy
>

From john-ietf@jck.com  Thu Dec 13 14:47:44 2012
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 8E07A21F89A0 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 14:47:44 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gtqz8419IWKO for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 14:47:44 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EA78C21F8644 for <ietf@ietf.org>; Thu, 13 Dec 2012 14:47:43 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TjHZ7-000NtN-9u; Thu, 13 Dec 2012 17:47:41 -0500
Date: Thu, 13 Dec 2012 17:47:36 -0500
From: John C Klensin <john-ietf@jck.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, Randy Bush <randy@psg.com>
Subject: Re: Running code, take 2
Message-ID: <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com>
In-Reply-To: <50CA4DFA.9050500@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@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: Thu, 13 Dec 2012 22:47:44 -0000

--On Thursday, December 13, 2012 23:51 +0200 Yaron Sheffer
<yaronf.ietf@gmail.com> wrote:

> Hi Randy,
> 
> the RPKI report is very impressive and probably very useful.
> But:
> 
> - Other areas (e.g. the Security Area, where I'm coming form)
> may not have this tradition.

If it is important, nothing prevents establishing it.

> - For "smaller" protocols the gain does not justify the effort
> of writing a separate implementation report. A section in the
> base document is much simpler to maintain.

I'm not at all clear why it is more effort to write a separate
report.  But, assuming it is, I am aware of nothing in any IETF
or RFC Editor procedure that prohibits including a discussion of
implementation experience in a standards track RFC.

> - And as I noted earlier on this thread, a wiki is a good
> alternative, provided everyone reading the base draft is
> referred to the "implementation status" wiki. They should not
> have to guess that one exists, or to search for it.

That is a more complicated problem because the RFC Editor is
somewhat reluctant (for good reasons, IMO) to accept references
to web pages whose permanency is not assured.  There are,
however, lots of other ways by which one could imagine creating
and maintaining such pointers.  For example, if you could
convince the community that this was important, and likely to be
done often enough, you might lobby the IESG to negotiate an
additional sentence in the "Status" section of standards track
RFCs that provided a stable pointer to an index of
implementation reports.

My concern remains that we not create new formal procedures to
do (or even experiment with) things that can be done under
existing rules either for the whole IETF or on an area by area
or even document by document basis,  Let me suggest, as
co-author of the "process experiment" doc, that it was intended
to deal to allow experiments that would otherwise be in
violation of existing procedures.  As far as I can see, that
situation doesn't apply with either of these proposals.  And,
given the number of experiments carried out with reference to
RFC 3933 that did not result in useful and formal reports back
to the community, I'm unconvinced that formally identifying any
particular exercise in identifying implementations or handling
some specifications with implementations differently in the IESG
review process than other specifications will increase the odds
of  the results being examined carefully and critically enough
to generate a report and, through it, permanently change
behavior.  YMMD but, if either of these ideas are interesting,
persuade a friendly AD to try it on whatever scale makes sense,
and then let the rest of us know how it worked out for you.
Since no existing rules would thereby be violated, IETF
consensus is not required for such an exercise... or any number
of such exercises.

best,
   john


From randy@psg.com  Thu Dec 13 16:11:03 2012
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 D8B5821F8BE2 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 16:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eJjWqDm6ydy7 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 16:11:03 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 4485121F8B67 for <ietf@ietf.org>; Thu, 13 Dec 2012 16:11:03 -0800 (PST)
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 1TjIrm-000MvF-Dz; Fri, 14 Dec 2012 00:11:02 +0000
Date: Thu, 13 Dec 2012 16:11:02 -0800
Message-ID: <m2lid1ze5l.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Running code, take 2
In-Reply-To: <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@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: Fri, 14 Dec 2012 00:11:04 -0000

> My concern remains that we not create new formal procedures to do (or
> even experiment with) things that can be done under existing rules
> either for the whole IETF or on an area by area or even document by
> document basis

<aol>

my apologies.  i did not mean that formal implementation reports should
be filed for everything, or even everything that wants to be on a fast
track, if there is a fast track.

i meant merely to illustrate that we already have flavors for filing
implementation reports.  and i was asking if/how melinda thought the
format of reporting might affect the speed and direction of the track.

randy

From melinda.shore@gmail.com  Thu Dec 13 16:44:02 2012
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 B850421F8970 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 16:44:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6eFzWUe1Chf for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 16:44:02 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 28A3821F896B for <ietf@ietf.org>; Thu, 13 Dec 2012 16:44:02 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so1056593dae.31 for <ietf@ietf.org>; Thu, 13 Dec 2012 16:44:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rmnGcwRDrJgEB9oytUiicHWtf//Lm/KKcY0vUOGhMio=; b=a3RnojD8Txu8k3CdEOxDIqV/7vtujvfCjvXIPTRPe3L8jowqUyMTKvN4qi281SRktu G5/XA+UjnoHzgQdDz+rQPnT2VcPBwCk04rYrW1Q8qZeFdvk9tL9UzNF8goS33BQ91KoN abueg1qCZW3RzltEhZ0OLYLTVKBo1iQfqiizfTw1MgVhxpY4Jego84Ce/Vv2S3Op/tiK 51OQZLpq1xMonw8k1KREu1EXpFjCNZgEruqt6ho24eR/cfV7AXd5rwRBTuhBsesdlxjs FpUZNeItWbU85MAnJ4WiPXIKYnESa2k9gthG3vauvNFicZiIPoA0ReHL0OV1TbQ89JJZ mobw==
Received: by 10.68.227.41 with SMTP id rx9mr230228pbc.121.1355445841691; Thu, 13 Dec 2012 16:44:01 -0800 (PST)
Received: from spandex.local (66-230-80-208-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.80.208]) by mx.google.com with ESMTPS id ug6sm1873052pbc.4.2012.12.13.16.43.59 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 13 Dec 2012 16:44:00 -0800 (PST)
Message-ID: <50CA764E.8060909@gmail.com>
Date: Thu, 13 Dec 2012 15:43:58 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <m2lid1ze5l.wl%randy@psg.com>
In-Reply-To: <m2lid1ze5l.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: Fri, 14 Dec 2012 00:44:02 -0000

On 12/13/12 3:11 PM, Randy Bush wrote:
> i meant merely to illustrate that we already have flavors for filing
> implementation reports.  and i was asking if/how melinda thought the
> format of reporting might affect the speed and direction of the track.

Right, and I'm not really sure.  I don't think that implementation
reports should be a mandatory document or document section.  sidr
seems to be functioning well but I suspect that a separate
implementation report document is a consequence of it functioning
well (and within a specific context) rather than a causal factor.
Considering, for example, scim, where there are a bunch of
implementations based on the state of the protocol prior to its
adoption as an IETF working group, and it seems to me that there
are is a sufficiently large number of implementations in a sufficiently
dynamic set of states that a document, as opposed to a wiki, may be
more difficult to maintain and ultimately less useful because of
that.

I do agree that there's nothing stopping working groups from
experimenting with various implementation report formats now, and
it may be worth trying several things out.  I'll run this past
the scim guys.

Melinda


From john-ietf@jck.com  Thu Dec 13 17:17:40 2012
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 4393921F8ADA for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 17:17:40 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpiRfqNbvGVG for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 17:17:39 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BDB5221F88D8 for <ietf@ietf.org>; Thu, 13 Dec 2012 17:17:39 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TjJuE-000O8S-Jg; Thu, 13 Dec 2012 20:17:38 -0500
Date: Thu, 13 Dec 2012 20:17:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Running code, take 2
Message-ID: <E4554DA7B4661680FAC1DF29@JcK-HP8200.jck.com>
In-Reply-To: <m2lid1ze5l.wl%randy@psg.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com>	<m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <m2lid1ze5l.wl%randy@psg.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 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, 14 Dec 2012 01:17:40 -0000

--On Thursday, December 13, 2012 16:11 -0800 Randy Bush
<randy@psg.com> wrote:

>> My concern remains that we not create new formal procedures
>> to do (or even experiment with) things that can be done under
>> existing rules either for the whole IETF or on an area by
>> area or even document by document basis
> 
> <aol>
> 
> my apologies.  i did not mean that formal implementation
> reports should be filed for everything, or even everything
> that wants to be on a fast track, if there is a fast track.
> 
> i meant merely to illustrate that we already have flavors for
> filing implementation reports.  and i was asking if/how
> melinda thought the format of reporting might affect the speed
> and direction of the track.

I actually understood that.  Sorry for not being clear.  My
concern about creating new procedures, of even a formal
experiment, is almost orthogonal to your comments and
illustration, for which I'm grateful and in complete agreement.

    john


From narten@us.ibm.com  Thu Dec 13 21:53:10 2012
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 C890821F84B2 for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 21:53:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLi+HanKLJ7y for <ietf@ietfa.amsl.com>; Thu, 13 Dec 2012 21:53:08 -0800 (PST)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id 0E45721F849A for <ietf@ietf.org>; Thu, 13 Dec 2012 21:53:07 -0800 (PST)
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, 13 Dec 2012 22:53:07 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 13 Dec 2012 22:53:04 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 45C8819D803F for <ietf@ietf.org>; Thu, 13 Dec 2012 22:53:04 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qBE5r3Cl308212 for <ietf@ietf.org>; Thu, 13 Dec 2012 22:53:04 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qBE5r3Ls009532 for <ietf@ietf.org>; Thu, 13 Dec 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qBE5r3CJ009508 for <ietf@ietf.org>; Thu, 13 Dec 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qBE5r2qM011165 for <ietf@ietf.org>; Fri, 14 Dec 2012 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qBE5r2rl011133 for ietf@ietf.org; Fri, 14 Dec 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201212140553.qBE5r2rl011133@rotala.raleigh.ibm.com>
Date: Fri, 14 Dec 2012 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12121405-7606-0000-0000-00000678D680
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 05:53:10 -0000

Total of 58 messages in the last 7 days.
 
script run at: Fri Dec 14 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 12.07% |    7 | 16.06% |    71764 | yaronf.ietf@gmail.com
  8.62% |    5 |  9.19% |    41081 | marc.blanchet@viagenie.ca
  8.62% |    5 |  5.56% |    24846 | randy@psg.com
  6.90% |    4 |  6.54% |    29227 | randy@qti.qualcomm.com
  6.90% |    4 |  6.39% |    28536 | barryleiba@computer.org
  6.90% |    4 |  5.66% |    25288 | melinda.shore@gmail.com
  6.90% |    4 |  5.34% |    23854 | mnot@mnot.net
  5.17% |    3 |  5.76% |    25720 | adrian@olddog.co.uk
  5.17% |    3 |  4.38% |    19578 | john-ietf@jck.com
  3.45% |    2 |  4.92% |    21968 | loa@pi.nu
  3.45% |    2 |  2.85% |    12716 | pier-luc@sarkass.com
  1.72% |    1 |  3.15% |    14080 | pbryan@anode.ca
  1.72% |    1 |  2.91% |    12981 | zhou.sujing@zte.com.cn
  1.72% |    1 |  2.79% |    12461 | jasnell@gmail.com
  1.72% |    1 |  2.22% |     9929 | narten@us.ibm.com
  1.72% |    1 |  2.15% |     9615 | pars.mutaf@gmail.com
  1.72% |    1 |  1.64% |     7335 | touch@isi.edu
  1.72% |    1 |  1.63% |     7290 | ted.ietf@gmail.com
  1.72% |    1 |  1.58% |     7074 | peter@akayla.com
  1.72% |    1 |  1.58% |     7064 | sm+ietf@elandsys.com
  1.72% |    1 |  1.51% |     6762 | hsantos@isdg.net
  1.72% |    1 |  1.44% |     6451 | rwfranks@gmail.com
  1.72% |    1 |  1.23% |     5511 | vesely@tana.it
  1.72% |    1 |  1.23% |     5486 | nick@inex.ie
  1.72% |    1 |  1.15% |     5137 | windy_1@skyhighway.com
  1.72% |    1 |  1.13% |     5054 | hannes.tschofenig@gmx.net
--------+------+--------+----------+------------------------
100.00% |   58 |100.00% |   446808 | Total


From yaronf.ietf@gmail.com  Fri Dec 14 00:49:38 2012
Return-Path: <yaronf.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 54B6821F86C4 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 00:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.432
X-Spam-Level: 
X-Spam-Status: No, score=-103.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kml8VXZ6wh35 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 00:49:37 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3A98D21F86C3 for <ietf@ietf.org>; Fri, 14 Dec 2012 00:49:37 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so1497595bku.31 for <ietf@ietf.org>; Fri, 14 Dec 2012 00:49:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ofiv1hr/fksmZwFHoEtgwJOhx/TIPRMRPuDAOTv/Eb8=; b=PZdLvDEI1DAHIvS7Wu3NjV8er26AcPZCojY9pFKozLXy0HR6xXvB0CL+79MYWMguUN 3LARFIK7YT8lmv7Pcbi0Gfk2ea4sXRvSfFK5ios1xEZMs5VOqsLrm3dth+B/6DSqtSjh fmKs64wDiv3qEpYpl8IM/OlPZ1gMQAcbGviInsnbfs+bepcz9Df8N25LOlftBKKUyB+c BwoXl4QLIKVHsC0tROP7ALQNpfvz35XN80PCLlg4j1D63TYL6f/Q8DIP0fS9PAAxlnYF T6dbbUo4/m1O/u0HwiiCWHe1ktSyY8fgzQk2zT3HOdnVUK8czItZDXu7SSIj5W5C7hBP 5Lgg==
Received: by 10.204.152.149 with SMTP id g21mr2323885bkw.97.1355474976293; Fri, 14 Dec 2012 00:49:36 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id o9sm3503643bko.15.2012.12.14.00.49.33 (version=SSLv3 cipher=OTHER); Fri, 14 Dec 2012 00:49:35 -0800 (PST)
Message-ID: <50CAE81A.4040807@gmail.com>
Date: Fri, 14 Dec 2012 10:49:30 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com>
In-Reply-To: <CD38357DE61404E1B49E9B93@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, 14 Dec 2012 08:49:38 -0000

Hi John,

to clarify, my proposal only applies to Internet Drafts, and clearly 
states that the implementation section should be removed from the 
document before it is published as RFC.

Formally, we don't want non-permanent stuff in RFCs. And realistically, 
even if we had an implementation wiki, it is unlikely to be kept up to 
date once the RFC is published.

Regarding the "experiment" question: I fully agree that there's nothing 
preventing us from adopting this proposal (or a variant of it, or 
Stephen's proposal) today.

The value in a 3933 experiment is in the Summary Report, otherwise I 
agree it's a waste of time. At the end of the period we will have a 
little bit of data to understand whether we have traction for this idea, 
and whether we should make it IETF-wide, allow it to quietly die or 
explicitly advise against it.

Thanks,
	Yaron

On 12/14/2012 12:47 AM, John C Klensin wrote:
>
>
> --On Thursday, December 13, 2012 23:51 +0200 Yaron Sheffer
> <yaronf.ietf@gmail.com> wrote:
>
>> Hi Randy,
>>
>> the RPKI report is very impressive and probably very useful.
>> But:
>>
>> - Other areas (e.g. the Security Area, where I'm coming form)
>> may not have this tradition.
>
> If it is important, nothing prevents establishing it.
>
>> - For "smaller" protocols the gain does not justify the effort
>> of writing a separate implementation report. A section in the
>> base document is much simpler to maintain.
>
> I'm not at all clear why it is more effort to write a separate
> report.  But, assuming it is, I am aware of nothing in any IETF
> or RFC Editor procedure that prohibits including a discussion of
> implementation experience in a standards track RFC.
>
>> - And as I noted earlier on this thread, a wiki is a good
>> alternative, provided everyone reading the base draft is
>> referred to the "implementation status" wiki. They should not
>> have to guess that one exists, or to search for it.
>
> That is a more complicated problem because the RFC Editor is
> somewhat reluctant (for good reasons, IMO) to accept references
> to web pages whose permanency is not assured.  There are,
> however, lots of other ways by which one could imagine creating
> and maintaining such pointers.  For example, if you could
> convince the community that this was important, and likely to be
> done often enough, you might lobby the IESG to negotiate an
> additional sentence in the "Status" section of standards track
> RFCs that provided a stable pointer to an index of
> implementation reports.
>
> My concern remains that we not create new formal procedures to
> do (or even experiment with) things that can be done under
> existing rules either for the whole IETF or on an area by area
> or even document by document basis,  Let me suggest, as
> co-author of the "process experiment" doc, that it was intended
> to deal to allow experiments that would otherwise be in
> violation of existing procedures.  As far as I can see, that
> situation doesn't apply with either of these proposals.  And,
> given the number of experiments carried out with reference to
> RFC 3933 that did not result in useful and formal reports back
> to the community, I'm unconvinced that formally identifying any
> particular exercise in identifying implementations or handling
> some specifications with implementations differently in the IESG
> review process than other specifications will increase the odds
> of  the results being examined carefully and critically enough
> to generate a report and, through it, permanently change
> behavior.  YMMD but, if either of these ideas are interesting,
> persuade a friendly AD to try it on whatever scale makes sense,
> and then let the rest of us know how it worked out for you.
> Since no existing rules would thereby be violated, IETF
> consensus is not required for such an exercise... or any number
> of such exercises.
>
> best,
>     john
>

From daedulus@btconnect.com  Fri Dec 14 03:17:56 2012
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 EBC9821F875C for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 03:17:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.849
X-Spam-Level: 
X-Spam-Status: No, score=-5.849 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zOzD5Ws-J+6 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 03:17:56 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id E752E21F874E for <ietf@ietf.org>; Fri, 14 Dec 2012 03:17:55 -0800 (PST)
Received: from mail155-co9-R.bigfish.com (10.236.132.232) by CO9EHSOBE028.bigfish.com (10.236.130.91) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 11:17:54 +0000
Received: from mail155-co9 (localhost [127.0.0.1])	by mail155-co9-R.bigfish.com (Postfix) with ESMTP id C8AE4800CB; Fri, 14 Dec 2012 11:17:54 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: PS-22(zzbb2dI98dI9371I542Id87dh1432I4015Izz1de0h1202h1e76h1d1ah1d2ahzz17326ah8275bh8275dh1033ILz2dh2a8h5a9h668h839h946hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h304l1155h)
Received: from mail155-co9 (localhost.localdomain [127.0.0.1]) by mail155-co9 (MessageSwitch) id 1355483873286322_25833; Fri, 14 Dec 2012 11:17:53 +0000 (UTC)
Received: from CO9EHSMHS009.bigfish.com (unknown [10.236.132.243])	by mail155-co9.bigfish.com (Postfix) with ESMTP id 35B01200058; Fri, 14 Dec 2012 11:17:53 +0000 (UTC)
Received: from DBXPRD0710HT003.eurprd07.prod.outlook.com (157.56.253.197) by CO9EHSMHS009.bigfish.com (10.236.130.19) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 11:17:53 +0000
Received: from DBXPRD0510HT005.eurprd05.prod.outlook.com (157.56.252.165) by pod51017.outlook.com (10.255.79.166) with Microsoft SMTP Server (TLS) id 14.16.245.2; Fri, 14 Dec 2012 11:17:47 +0000
Message-ID: <022b01cdd9ec$69abfa00$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>, <adrian@olddog.co.uk>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it><006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com>
Subject: Re: Running code, take 2
Date: Fri, 14 Dec 2012 11:15:59 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
X-OriginatorOrg: btconnect.com
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, 14 Dec 2012 11:17:57 -0000

----- Original Message -----
From: "Yaron Sheffer" <yaronf.ietf@gmail.com>
To: <adrian@olddog.co.uk>
Cc: <ietf@ietf.org>; "'Alessandro Vesely'" <vesely@tana.it>
Sent: Thursday, December 13, 2012 2:52 PM
> Hi Adrian,
>
> I would suggest to start with my proposal, because it requires zero
> implementation effort.

I am surprised at this.  Gathering information about implementations is
something that happens in some WGs and not in others, but it is always
the chair that is driving it, often as part of the write-up prior to
IETF Last Call.  This takes time, asking, chasing, clarifying, and
getting replies off-list because the implementor does not have
permission to reveal such matters to the world at large.

Since the WG Chair is a limited resource, and is on the critical path
for several actions in the progress of an I-D to RFC, asking them to do
more work can only delay the progress of RFC at large.  This is not a
zero sum game.

Tom Petch

>                             If this catches on, I see a lot of value
in your
> proposal.
>
> Please also note that the "implementation status" section (according
to
> my proposal) is not "frozen" when published as an RFC, rather it is
> deleted. RFCs are forever, and I think a point-in-time implementation
> status is not appropriate in an RFC.
>
> Thanks,
> Yaron
>
> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
> > I'm interested in this idea.
> >
> > However, I note that an "implementation status" section of a
document is frozen
> > in time when a document goes to RFC.
> >
> > I wonder whether we could leverage our tools and do something
similar to IPR
> > disclosures. That is, provide a semi-formal web page where
implementation
> > details could be recorded and updated. These would then be
searchable and linked
> > to from the tools page for the I-D / RFC.
> >
> > They could record the document version that has been implemented,
and also allow
> > space for other notes.
> >
> > Adrian (Just thinking aloud)
> >
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
Behalf Of
> >> Alessandro Vesely
> >> Sent: 13 December 2012 13:58
> >> To: ietf@ietf.org
> >> Subject: Re: Running code, take 2
> >>
> >> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
> >>>
> >>> I have just published a draft that proposes an alternative to
> >>> Stephen's "fast track". My proposal simply allows authors to
document,
> >>> in a semi-standard way, whatever implementations exist for their
> >>> protocol, as well as their interoperability.
> >>>
> >>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
> >>>
> >>> [...]
> >>>
> >>> I am looking forward to comments and discussion on this list.
> >>
> >> As an occasional I-D reader, I'd appreciate "Implementation Status"
> >> sections, including IPR info.  I don't think anything forbids to
add
> >> such sections, if the authors wish.  I'd add a count of the number
of
> >> I-Ds that actually have it among the experiment's success criteria.
> >
>



From daedulus@btconnect.com  Fri Dec 14 03:24:40 2012
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 16CA321F8549 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 03:24:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hv3HRYPf9oSx for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 03:24:39 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id 7723021F853D for <ietf@ietf.org>; Fri, 14 Dec 2012 03:24:33 -0800 (PST)
Received: from mail31-ch1-R.bigfish.com (10.43.68.232) by CH1EHSOBE014.bigfish.com (10.43.70.64) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 11:24:32 +0000
Received: from mail31-ch1 (localhost [127.0.0.1])	by mail31-ch1-R.bigfish.com (Postfix) with ESMTP id 6DA5C605D3; Fri, 14 Dec 2012 11:24:32 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zzbb2dI98dI9371Ic89bh936eI542Id87dh1432I4015I62a3Izz1de0h1202h1e76h1d1ah1d2ahzz17326ah8275bh8275dh1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h304l1155h)
Received: from mail31-ch1 (localhost.localdomain [127.0.0.1]) by mail31-ch1 (MessageSwitch) id 1355484269624956_16861; Fri, 14 Dec 2012 11:24:29 +0000 (UTC)
Received: from CH1EHSMHS001.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.251])	by mail31-ch1.bigfish.com (Postfix) with ESMTP id 92E1B4C0042;	Fri, 14 Dec 2012 11:24:29 +0000 (UTC)
Received: from DB3PRD0710HT001.eurprd07.prod.outlook.com (157.56.253.85) by CH1EHSMHS001.bigfish.com (10.43.70.1) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 11:24:29 +0000
Received: from DBXPRD0510HT005.eurprd05.prod.outlook.com (157.56.252.165) by pod51017.outlook.com (10.255.75.36) with Microsoft SMTP Server (TLS) id 14.16.245.2; Fri, 14 Dec 2012 11:24:27 +0000
Message-ID: <023301cdd9ed$58110780$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Marc Blanchet <marc.blanchet@viagenie.ca>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it><006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk><50C9EBB3.5040901@gmail.com><B73F381B-93E7-4158-B5C5-D1F88994E7DF@viagenie.ca><50C9ED7B.2010009@gmail.com><6404EADF-2DA7-42FF-B6DC-596B0163687B@viagenie.ca><009401cdd944$02fe0da0$08fa28e0$@olddog.co.uk><50C9F2C2.1020004@pi.nu> <D20F60AB-3E90-4342-B13C-7572118EF014@viagenie.ca>
Subject: Re: Running code, take 2
Date: Fri, 14 Dec 2012 11:22:39 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
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, 14 Dec 2012 11:24:40 -0000

----- Original Message -----
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: "Loa Andersson" <loa@pi.nu>
Cc: <ietf@ietf.org>
Sent: Thursday, December 13, 2012 3:39 PM
Le 2012-12-13 =E0 10:22, Loa Andersson a =E9crit :

> Folks,
>
> I agree that understanding the implementation status of a draft
> sometimes is essential, but not for all drafts and not always.
> Today wg chairs do this type of info collection at the shepherd
> write-up.
>
> Have anyone thought about how much work goes into compiling this type
> of information. There are vendors that by policy decided not to
disclose
> implementation information, before the implementation is done and the
> document has become an RFC.
>
> Most of the time it is possible to to get some understanding, with a
> promise not to make the info public and only use it for a rather
> cryptic statement in the shepherd write-up - "we know of existing or
> intended implementations of this draft".
>
> A second, rather new problem, is that for some drafts the IANA
> assignment is the singular most important part of the ID. We have
heard
> vendors say "We'll wait for the IANA assignment until we implement!"
>

right. but that does not preclude doing the proposal. What you are
saying is that maybe the info (in draft, wiki, tracker) may not be
complete since some may not disclose. But the available information
would be valuable.

<tp>
And could be very misleading, because it is incomplete and people will
draw unwarranted inferences from the information that has been made
public.  They will likely not understand the nuances of different
implementors having different policies about when to make such details
public, whether for commercial reasons, IPR reasons or whatever.  Nor
may they realise that an I-D is a work in progress, so an implementation
at an early stage may be really bad news if there is a later change to
the technical details (something of which happened with MPLS-TP OAM,
with an ITU-T approach predating an IETF one).

Tom Petch
</tp>
Marc.


> /Loa
>
>
> On 2012-12-13 16:10, Adrian Farrel wrote:
>> How about...
>>
>> Start with Yaron's proposal to include in the I-D. This is easy as a
starting
>> point. Duplicate documentation in wiki may be useful and provide a
place to
>> track text for inclusion in the next revision.
>>
>> When/if inclusion in the I-D gets messy, replace text in I-D with
pointer to
>> wiki.
>>
>> When/if experiment looks like a success, replace all above with data
tracker
>> tool and allow it to persist for RFCs.
>>
>> Adrian
>>
>>> -----Original Message-----
>>> From: Marc Blanchet [mailto:marc.blanchet@viagenie.ca]
>>> Sent: 13 December 2012 15:05
>>> To: Yaron Sheffer
>>> Cc: adrian@olddog.co.uk; ietf@ietf.org; 'Alessandro Vesely'
>>> Subject: Re: Running code, take 2
>>>
>>>
>>> Le 2012-12-13 =E0 10:00, Yaron Sheffer a =E9crit :
>>>
>>>> Hi Marc,
>>>>
>>>> I think it's critical that a person reading a draft (e.g. going to
>>>
http://tools.ietf.org/html/draft-blanchet-iab-internetoverport443-01)
will
>> have a
>>> direct way to check out on the implementation status.
>>>>
>>>> This is trivial if it's a section in the document. It's simple if
it's
>> linked from the
>>> Tools page. Otherwise, e.g. if you put it on the wiki, only IETF
insiders will
>> be
>>> aware of it.
>>>>
>>>
>>> sure. Let me restart:
>>> - I like Adrian proposal: instead of in RFC, put it online within
our site
>>> - but you wrote: requires implementation effort.
>>> - I replied: well, phase 1 (of put it online within our site) can be
done with
>> almost
>>> zero implementation effort. phase 2 requires some work (I'd say not
that big)
>> for
>>> implementation/tools.
>>>
>>> Regards, Marc.
>>>
>>>> Thanks,
>>>> Yaron
>>>>
>>>> On 12/13/2012 04:55 PM, Marc Blanchet wrote:
>>>>>
>>>>> Le 2012-12-13 =E0 09:52, Yaron Sheffer a =E9crit :
>>>>>
>>>>>> Hi Adrian,
>>>>>>
>>>>>> I would suggest to start with my proposal, because it requires
zero
>>> implementation effort.
>>>>>
>>>>> disagree. phase 1: use IETF wiki. phase 2: develop an widget
within data
>>> tracker.
>>>>>
>>>>> Marc.
>>>>>
>>>>>
>>>>>> If this catches on, I see a lot of value in your proposal.
>>>>>>
>>>>>> Please also note that the "implementation status" section
(according to my
>>> proposal) is not "frozen" when published as an RFC, rather it is
deleted. RFCs
>> are
>>> forever, and I think a point-in-time implementation status is not
appropriate
>> in an
>>> RFC.
>>>>>>
>>>>>> Thanks,
>>>>>> Yaron
>>>>>>
>>>>>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>>>>>> I'm interested in this idea.
>>>>>>>
>>>>>>> However, I note that an "implementation status" section of a
document is
>>> frozen
>>>>>>> in time when a document goes to RFC.
>>>>>>>
>>>>>>> I wonder whether we could leverage our tools and do something
similar to
>>> IPR
>>>>>>> disclosures. That is, provide a semi-formal web page where
implementation
>>>>>>> details could be recorded and updated. These would then be
searchable
>>> and linked
>>>>>>> to from the tools page for the I-D / RFC.
>>>>>>>
>>>>>>> They could record the document version that has been
implemented, and
>>> also allow
>>>>>>> space for other notes.
>>>>>>>
>>>>>>> Adrian (Just thinking aloud)
>>>>>>>
>>>>>>>> -----Original Message-----
>>>>>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
Behalf Of
>>>>>>>> Alessandro Vesely
>>>>>>>> Sent: 13 December 2012 13:58
>>>>>>>> To: ietf@ietf.org
>>>>>>>> Subject: Re: Running code, take 2
>>>>>>>>
>>>>>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>>>>>
>>>>>>>>> I have just published a draft that proposes an alternative to
>>>>>>>>> Stephen's "fast track". My proposal simply allows authors to
document,
>>>>>>>>> in a semi-standard way, whatever implementations exist for
their
>>>>>>>>> protocol, as well as their interoperability.
>>>>>>>>>
>>>>>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>>>>>
>>>>>>>>> [...]
>>>>>>>>>
>>>>>>>>> I am looking forward to comments and discussion on this list.
>>>>>>>>
>>>>>>>> As an occasional I-D reader, I'd appreciate "Implementation
Status"
>>>>>>>> sections, including IPR info.  I don't think anything forbids
to add
>>>>>>>> such sections, if the authors wish.  I'd add a count of the
number of
>>>>>>>> I-Ds that actually have it among the experiment's success
criteria.
>>>>>>>
>>>>>
>>
>
> --
>
>
> Loa Andersson                         email:
loa.andersson@ericsson.com
> Sr Strategy and Standards Manager            loa@pi.nu
> Ericsson Inc                          phone: +46 10 717 52 13
>                                             +46 767 72 92 13




From randy@psg.com  Fri Dec 14 04:10:00 2012
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 4570221F85FE for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MxflqKvWS62y for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:09:59 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id DDFDF21F85EE for <ietf@ietf.org>; Fri, 14 Dec 2012 04:09:59 -0800 (PST)
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 1TjU5O-000OrI-3F; Fri, 14 Dec 2012 12:09:50 +0000
Date: Fri, 14 Dec 2012 04:09:49 -0800
Message-ID: <m28v90zvg2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Running code, take 2
In-Reply-To: <50CAE81A.4040807@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@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: 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: Fri, 14 Dec 2012 12:10:00 -0000

> to clarify, my proposal only applies to Internet Drafts, and clearly 
> states that the implementation section should be removed from the 
> document before it is published as RFC.
> 
> Formally, we don't want non-permanent stuff in RFCs. And realistically, 
> even if we had an implementation wiki, it is unlikely to be kept up to 
> date once the RFC is published.

so, we act on implementation and interoperability data which are not
kept?

randy

From randy@psg.com  Fri Dec 14 04:30:45 2012
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 8C46721F8528 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:30:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iF1vsZsZET-A for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:30:45 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2500F21F851A for <ietf@ietf.org>; Fri, 14 Dec 2012 04:30:45 -0800 (PST)
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 1TjUPc-000OwU-0p; Fri, 14 Dec 2012 12:30:44 +0000
Date: Fri, 14 Dec 2012 04:30:42 -0800
Message-ID: <m24njozuh9.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: t.p. <daedulus@btconnect.com>
Subject: Re: Running code, take 2
In-Reply-To: <022b01cdd9ec$69abfa00$4001a8c0@gateway.2wire.net>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <022b01cdd9ec$69abfa00$4001a8c0@gateway.2wire.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: Fri, 14 Dec 2012 12:30:45 -0000

> I am surprised at this.  Gathering information about implementations is
> something that happens in some WGs and not in others, but it is always
> the chair that is driving it, often as part of the write-up prior to
> IETF Last Call.

uh, not really.  in some wg cultures, it's just seen as part of the
drafters' or implementors' job, just as is doing a mib.  i suspect that
the implementation document (and the mib) i used as an example came as a
surprise to the chairs as they are more security than routing area.

randy

From vesely@tana.it  Fri Dec 14 04:36:50 2012
Return-Path: <vesely@tana.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 80B0221F85FA for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level: 
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vlRIvgwh+d86 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 04:36:49 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A842821F85ED for <ietf@ietf.org>; Fri, 14 Dec 2012 04:36:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1355488607; bh=7YubRqADiw8BMR8QFdCUzoGzM9uTQADZohkqs/Hm9/Q=; l=1447; h=Date:From:To:References:In-Reply-To; b=DXXkwOYUSJkjomEbcfEa7Mkp57z7If1qfHlB3N92q2HePgdDVLGiAIUyFpbd5jWm+ bFOC5MfTs9oqmKfrk8NSi91Z+w1+Zo21JtHuVIYulMar22JuAhv4Ip3cjQoIC+Z3HY JFkereFFNX4Ae2TJVv3refBJQDHc8ZAq2ELDG+Xo=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Fri, 14 Dec 2012 13:36:47 +0100 id 00000000005DC031.0000000050CB1D5F.000030D9
Message-ID: <50CB1D5F.10705@tana.it>
Date: Fri, 14 Dec 2012 13:36:47 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@gmail.com>
In-Reply-To: <50CAE81A.4040807@gmail.com>
Content-Type: text/plain; charset=us-ascii
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, 14 Dec 2012 12:36:50 -0000

On Fri 14/Dec/2012 09:49:30 +0100 Yaron Sheffer wrote:
> 
> to clarify, my proposal only applies to Internet Drafts, and clearly
> states that the implementation section should be removed from the
> document before it is published as RFC.

One place where an Implementation Status may help is IETF LCs:  People
are asked to comment on I-Ds whose development they didn't track, on
topics they may have only a working knowledge of.  Code licensing and
IPR details could quickly convey whether a given standardization
process is being gamed, for example.

> Formally, we don't want non-permanent stuff in RFCs.

We have the Errata and the Outcomes, AFAIK.  The Errata is freely
writable, somewhat impractical, and doesn't address this purpose.

> And realistically, even if we had an implementation wiki, it is
> unlikely to be kept up to date once the RFC is published.

The Outcomes /is/ a wiki, http://trac.tools.ietf.org/misc/outcomes/.
No wonder it's not updated:  It is difficult to find it from the
relevant RFCs (let alone specific sections thereof), and it is not
freely writable.  Anyway, it addresses only a small subset of the
Implementation Status.

While we need no formal procedure to write the Implementation Status
section of an I-D, we probably need to specify how the content of that
section can be used to set off the wiki page for the new RFC,
and how that wiki should work.  Would that help running code?

From yaronf.ietf@gmail.com  Fri Dec 14 05:04:21 2012
Return-Path: <yaronf.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 B409521F87B1 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 05:04:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.488
X-Spam-Level: 
X-Spam-Status: No, score=-103.488 tagged_above=-999 required=5 tests=[AWL=0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3OWHA0kJxKQs for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 05:04:21 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id EB5C521F8563 for <ietf@ietf.org>; Fri, 14 Dec 2012 05:04:20 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so1667479bku.31 for <ietf@ietf.org>; Fri, 14 Dec 2012 05:04:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Yk2sc6TOoKqgHarFh/v2YDkhrllZW9yRTuZpB7OaZkU=; b=o9CDP3CG7sW6lq4XnXMxZbTU4HrMw4TErMWCdj/C7bXS0bE3XdVCeL2dw1RG6/0aPi VuOHI5I1UlHIjzw2K/E0LTr2ZrE2iIfIFGvNt7AOcJvB8q/9agbZiVSzjx7f4dQS8w5l YGzSx7qd3cuYmytSf7DiWVPVdRxTd0AjXrRbFqAJG+1Cx2zWuyo4l9/niHmV72FaRksU 7R8P/vikha2Ykv58Fl7pKXxDZdRjbW3JLF3/mhaLyo5tFbDsO4JHYqJoYGqra6couJGp G9wQHdi5YwwOfqNriA6yvJWBV3WSztA1tiTl9RWVZ71dl5prLzlJ8ieGbppjlLK9raxO r+VQ==
Received: by 10.204.3.205 with SMTP id 13mr2738115bko.38.1355490260005; Fri, 14 Dec 2012 05:04:20 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id y11sm4406253bkw.8.2012.12.14.05.04.17 (version=SSLv3 cipher=OTHER); Fri, 14 Dec 2012 05:04:18 -0800 (PST)
Message-ID: <50CB23CE.9040308@gmail.com>
Date: Fri, 14 Dec 2012 15:04:14 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@gmail.com> <m28v90zvg2.wl%randy@psg.com>
In-Reply-To: <m28v90zvg2.wl%randy@psg.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 13:04:22 -0000

Hi Randy,

I don't know who's "we" in your question.

My proposal is aimed at an earlier stage in the process, when the WG 
needs to evaluate a draft before it becomes a WG document and later, 
during WGLC. During these stages, information about implementation 
status is very useful, even if (as some have stated), it may not always 
be available.

As to the later stage (off topic), let me just give one example. Earlier 
today I sent a SecDir review where I said that a certain 1997 RFC is 
probably not implemented by anybody today. I may be right or I may be 
wrong, I don't have any solid data. But do you expect the author of that 
RFC to maintain an up-to-date implementation status wiki for 15 years 
after the RFC had been published? I don't.

Thanks,
	Yaron

On 12/14/2012 02:09 PM, Randy Bush wrote:
>> to clarify, my proposal only applies to Internet Drafts, and clearly
>> states that the implementation section should be removed from the
>> document before it is published as RFC.
>>
>> Formally, we don't want non-permanent stuff in RFCs. And realistically,
>> even if we had an implementation wiki, it is unlikely to be kept up to
>> date once the RFC is published.
>
> so, we act on implementation and interoperability data which are not
> kept?
>
> randy
>

From framefritti@gmail.com  Fri Dec 14 05:07:05 2012
Return-Path: <framefritti@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 29D9C21F85A7 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 05:07:05 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRIs80fgN+MT for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 05:07:04 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 39B1B21F8623 for <ietf@ietf.org>; Fri, 14 Dec 2012 05:07:04 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so2735460lah.31 for <ietf@ietf.org>; Fri, 14 Dec 2012 05:07:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=fbjTb5PvPSTE7LQPU8Ig0Ez8sYsCQpL8IGfuXZni6N0=; b=rHRF/AB1LwWt0jPrlDZvwiScg9wOBs3ytTihFuJrWoKOnXSzZYTPj36rvIt9Wxsnu6 8zZfLn9C7sSYHXzuUaZLPlA6AJMktp20hl4FWbJMWlyx90euouM7gcbu9H1bRKQMb0Ii GiaHmsm9Z58feZPqw3CwaFUzHAOiAPaxaTqDExrLl5DAYFy9IbWPpyFqUTCKCDOZ6S14 e5D0xhyE182usNHh0JtCkd5k2NNnKYo36jzPohMVR+yVbjE+e2ELdp9EBSfXgDrG90nZ TjxuibBEZ2vx62wNUn/f68G9cTwhTeos8fLsVVvjmO/lywpkR2LOJAr4a8//H8sR3iEj QSZA==
MIME-Version: 1.0
Received: by 10.112.16.110 with SMTP id f14mr2294969lbd.126.1355490423164; Fri, 14 Dec 2012 05:07:03 -0800 (PST)
Received: by 10.112.108.133 with HTTP; Fri, 14 Dec 2012 05:07:02 -0800 (PST)
In-Reply-To: <50CB1D5F.10705@tana.it>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@gmail.com> <50CB1D5F.10705@tana.it>
Date: Fri, 14 Dec 2012 14:07:02 +0100
Message-ID: <CABSMSPW_w3rVpYrnwRqR8HzJzWPK=XowXnx0VV6LypUS8dnwRw@mail.gmail.com>
Subject: Re: Running code, take 2
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF Discussion <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: Fri, 14 Dec 2012 13:07:05 -0000

On Fri, Dec 14, 2012 at 1:36 PM, Alessandro Vesely <vesely@tana.it> wrote:
> On Fri 14/Dec/2012 09:49:30 +0100 Yaron Sheffer wrote:
>>
>> to clarify, my proposal only applies to Internet Drafts, and clearly
>> states that the implementation section should be removed from the
>> document before it is published as RFC.
>
> One place where an Implementation Status may help is IETF LCs:  People
> are asked to comment on I-Ds whose development they didn't track, on
> topics they may have only a working knowledge of.  Code licensing and
> IPR details could quickly convey whether a given standardization
> process is being gamed, for example.
>
>> Formally, we don't want non-permanent stuff in RFCs.
>
> We have the Errata and the Outcomes, AFAIK.  The Errata is freely
> writable, somewhat impractical, and doesn't address this purpose.
>
>> And realistically, even if we had an implementation wiki, it is
>> unlikely to be kept up to date once the RFC is published.
>
> The Outcomes /is/ a wiki, http://trac.tools.ietf.org/misc/outcomes/.
> No wonder it's not updated:  It is difficult to find it from the
> relevant RFCs (let alone specific sections thereof), and it is not
> freely writable.  Anyway, it addresses only a small subset of the
> Implementation Status.
>
> While we need no formal procedure to write the Implementation Status
> section of an I-D, we probably need to specify how the content of that
> section can be used to set off the wiki page for the new RFC,
> and how that wiki should work.  Would that help running code?

<brainstorming_mode>
This just came to my mind... Why not doing a little step more and
making the wiki page a kind of "directory" to available
implementations?  Maybe each entry could have a "license type" field
(e.g. open source, commercial, ...) and "compliant flag" assuming
values like "fully compliant," "partially compliant," "unknown,"
"what kind of weed did they smoke before coding this?!?" :-)  If the
protocol allows it, the compliant flag could be assigned on the basis
of running a suitable set of test vectors (possibly described in the
RFC), otherwise it could be assigned after a community discussion
(maybe inside the WG that produced the protocol, it still existing).

This kind of "implementation directory" could be useful not only to
the IETF, but also to people who needs to implement a protocol and
would prefer to use something ready.  A new entry in the directory
could be written by anyone (or proposed via e-mail).  The author that
writes the entry cannot set the compliant field which will be
"unknown" by default.  If there is some evidence that the
implementation is compliant (e.g., the software is used inside a
widely used browser and it did not cause any meltdown so far:-), the
status could be set to "probably compliant." The upgrade to "fully
compliant" would require running tests and/or community discussion.

Finally, I would also add to the implementation page a reference to
any available test vectors (if the protocol allow them).  I find thme
are quite useful during the implementation phase.
</brainstorming_mode>

Riccardo

From stephen.farrell@cs.tcd.ie  Fri Dec 14 05:19:22 2012
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 2DD2721F896E for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 05:19:22 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rk10nxtLi0uF for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 05:19:21 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2BE21F8645 for <ietf@ietf.org>; Fri, 14 Dec 2012 05:19:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3D975BE64; Fri, 14 Dec 2012 13:18:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbADfazv4x8R; Fri, 14 Dec 2012 13:18:53 +0000 (GMT)
Received: from [161.106.193.212] (unknown [161.106.193.212]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B455CBE5D; Fri, 14 Dec 2012 13:18:53 +0000 (GMT)
Message-ID: <50CB273D.3070208@cs.tcd.ie>
Date: Fri, 14 Dec 2012 13:18:53 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com>
In-Reply-To: <50C8DB78.3080905@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 13:19:22 -0000

Hi Yaron,

I'm glad to see more discussion of this general topic.

On 12/12/2012 07:31 PM, Yaron Sheffer wrote:
> Hi,
> 
> I have just published a draft that proposes an alternative to Stephen's
> "fast track". My proposal simply allows authors to document, in a
> semi-standard way, whatever implementations exist for their protocol, as
> well as their interoperability.
> 
> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
> 
> I believe this can achieve the same goal, which is to apply preferred
> treatment to protocols that have been implemented, and with a lot less
> process overhead. It also leaves much more leeway for individual working
> groups to apply their own procedures and customs.
> 
> Similarly to Stephen's proposal, we can use a process experiment (per
> RFC 3933) to gauge the effectiveness of this one.
> 
> I am looking forward to comments and discussion on this list.

Looks fine to me and I reckon that doing one or both of these
experiments in parallel or series could make sense depending on
what happens when/if they're last called. In contrast with
some others who've posted, I do think doing process experiments
is a good thing and we've not done enough to even know if 3933
can work or not - I only counted 4 or 5 RFCs that seem to refer
to 3933.

Cheers,
S.

PS: I just posted -02 of my proposal. [1]

[1] http://tools.ietf.org/html/draft-farrell-ft-02


> 
>     Yaron
> 

From yaronf.ietf@gmail.com  Fri Dec 14 08:17:09 2012
Return-Path: <yaronf.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 B75E821F891C for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 08:17:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.504
X-Spam-Level: 
X-Spam-Status: No, score=-103.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dSevNCIQrwp for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 08:17:09 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id A7BD221F8910 for <ietf@ietf.org>; Fri, 14 Dec 2012 08:17:08 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id w11so1800213bku.31 for <ietf@ietf.org>; Fri, 14 Dec 2012 08:17:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=WAQe0+PhDrnlYciv6Fc61DP+87ar1XtmzMlYHrRUn4s=; b=0Fy0IvFhRvPPBg0UkEAQ+c0/jWwWmqqKHHVPvvSU42F7MzRtKRJmpUfbtMYG2xrTZD 8f62GsBwyWo6SLHq+lvNMyPJlWH+EiVqI5y6IpkUZSLlY/1fSGIM7KydQCasbElKO3OP QsQGf7dI0bQd7vTgcna4H7mfe14yWgZBN+OZfh7Z/RxGEqzDhkVXRr5cvPF6Jx719PwA AoHZsxt+R5e1FvgiXHWsXIWk+fwqxykDmxoBKwo5EKZCMxC/CpsfFtqSTstXU/TYaugL t7a9CbZoa63WtZi9qxnNGrZwCLpZSvHeDHWTUu9QVlJ3O3GKpKbXViUZ35IkOyqV5sRp RC6g==
Received: by 10.204.130.210 with SMTP id u18mr2947719bks.129.1355501827791; Fri, 14 Dec 2012 08:17:07 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id e22sm5064266bke.14.2012.12.14.08.17.04 (version=SSLv3 cipher=OTHER); Fri, 14 Dec 2012 08:17:06 -0800 (PST)
Message-ID: <50CB50FC.4010700@gmail.com>
Date: Fri, 14 Dec 2012 18:17:00 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it><006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <50C9EBB3.5040901@gmail.com> <022b01cdd9ec$69abfa00$4001a8c0@gateway.2wire.net>
In-Reply-To: <022b01cdd9ec$69abfa00$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 16:17:09 -0000

Hi Tom,

I am myself somewhat puzzled by the current process, where such 
information is gathered prior to IESG review, because (in my limited 
experience) I have never seen the IESG reject a draft merely because it 
is unimplemented.

In any case, my proposal aims to move the burden to authors, who can, if 
they choose, document extant implementations. This information, where 
available, can allow the WG to better judge the maturity of protocol 
proposals.

In cases when implementors choose not to reveal their implementations, 
we are back in the existing situation. Hopefully more people would be 
motivated to share such details publicly if it gives them some benefit 
during the early standardization stages.

Thanks,
	Yaron

On 12/14/2012 01:15 PM, t.p. wrote:
> ----- Original Message -----
> From: "Yaron Sheffer" <yaronf.ietf@gmail.com>
> To: <adrian@olddog.co.uk>
> Cc: <ietf@ietf.org>; "'Alessandro Vesely'" <vesely@tana.it>
> Sent: Thursday, December 13, 2012 2:52 PM
>> Hi Adrian,
>>
>> I would suggest to start with my proposal, because it requires zero
>> implementation effort.
>
> I am surprised at this.  Gathering information about implementations is
> something that happens in some WGs and not in others, but it is always
> the chair that is driving it, often as part of the write-up prior to
> IETF Last Call.  This takes time, asking, chasing, clarifying, and
> getting replies off-list because the implementor does not have
> permission to reveal such matters to the world at large.
>
> Since the WG Chair is a limited resource, and is on the critical path
> for several actions in the progress of an I-D to RFC, asking them to do
> more work can only delay the progress of RFC at large.  This is not a
> zero sum game.
>
> Tom Petch
>
>>                              If this catches on, I see a lot of value
> in your
>> proposal.
>>
>> Please also note that the "implementation status" section (according
> to
>> my proposal) is not "frozen" when published as an RFC, rather it is
>> deleted. RFCs are forever, and I think a point-in-time implementation
>> status is not appropriate in an RFC.
>>
>> Thanks,
>> Yaron
>>
>> On 12/13/2012 04:16 PM, Adrian Farrel wrote:
>>> I'm interested in this idea.
>>>
>>> However, I note that an "implementation status" section of a
> document is frozen
>>> in time when a document goes to RFC.
>>>
>>> I wonder whether we could leverage our tools and do something
> similar to IPR
>>> disclosures. That is, provide a semi-formal web page where
> implementation
>>> details could be recorded and updated. These would then be
> searchable and linked
>>> to from the tools page for the I-D / RFC.
>>>
>>> They could record the document version that has been implemented,
> and also allow
>>> space for other notes.
>>>
>>> Adrian (Just thinking aloud)
>>>
>>>> -----Original Message-----
>>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On
> Behalf Of
>>>> Alessandro Vesely
>>>> Sent: 13 December 2012 13:58
>>>> To: ietf@ietf.org
>>>> Subject: Re: Running code, take 2
>>>>
>>>> On Wed 12/Dec/2012 20:31:04 +0100 Yaron Sheffer wrote:
>>>>>
>>>>> I have just published a draft that proposes an alternative to
>>>>> Stephen's "fast track". My proposal simply allows authors to
> document,
>>>>> in a semi-standard way, whatever implementations exist for their
>>>>> protocol, as well as their interoperability.
>>>>>
>>>>> http://www.ietf.org/id/draft-sheffer-running-code-00.txt
>>>>>
>>>>> [...]
>>>>>
>>>>> I am looking forward to comments and discussion on this list.
>>>>
>>>> As an occasional I-D reader, I'd appreciate "Implementation Status"
>>>> sections, including IPR info.  I don't think anything forbids to
> add
>>>> such sections, if the authors wish.  I'd add a count of the number
> of
>>>> I-Ds that actually have it among the experiment's success criteria.
>>>
>>
>
>

From zhou.sujing@zte.com.cn  Thu Dec 13 16:30:22 2012
Return-Path: <zhou.sujing@zte.com.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 0B63C21F8BE4; Thu, 13 Dec 2012 16:30:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.364
X-Spam-Level: 
X-Spam-Status: No, score=-98.364 tagged_above=-999 required=5 tests=[AWL=-0.391, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sEm+bk7RoK6E; Thu, 13 Dec 2012 16:30:18 -0800 (PST)
Received: from zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 7C29D21F8BDF; Thu, 13 Dec 2012 16:30:17 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id A50AB125EA; Fri, 14 Dec 2012 08:30:07 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id E7774174C771; Fri, 14 Dec 2012 08:19:15 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id qBE0U1Do020840; Fri, 14 Dec 2012 08:30:01 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <18F98790-E67A-44AD-83C6-51118716C9DA@salesforce.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Subject: Re: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFE9540EB0.6D71176A-ON48257AD4.00025F53-48257AD4.0002DDC1@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Fri, 14 Dec 2012 08:29:47 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-12-14 08:29:53, Serialize complete at 2012-12-14 08:29:53
Content-Type: multipart/alternative; boundary="=_alternative 0002DDBE48257AD4_="
X-MAIL: mse02.zte.com.cn qBE0U1Do020840
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 00:30:22 -0000

This is a multipart message in MIME format.
--=_alternative 0002DDBE48257AD4_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

RnJvbSB0aGUgbGFuZ3VhZ2UsIEkgZ290IGFuIGltcHJlc3Npb24gdGhhdCBhc3NlcnRpb24gaXMg
b25seSBnZW5lcmF0ZWQgYnkgDQp0b2tlbiBzZXJ2aWNlIGFmdGVyIGNsaWVudHMgcHJlc2VudGlu
ZyBzb21lIGNyZWRlbnRpYWxzLA0KdGhlcmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRoYXQgImFz
c2VydGlvbiIgZG9uJ3QgbmVlZCBjbGllbnQncyANCmNyZWRlbnRpYWwuDQplLmcuLCBSZXNvdXJj
ZSBvd25lciBhcyBhIHRva2VuIHNlcnZpY2UgIGNvdWxkIGdlbmVyYXRlICJhc3NlcnRpb24iIHRv
IGEgDQpjbGllbnQgaGUgdHJ1c3RzLCBidSBzaWduaW5nIGEgc3RhdGVtZW50IHRoYXQgIlRoaXMg
ZGVsZWdhdGlvbiBpcyBnaXZlbiB0byANCmEgY2xpZW50IGNhbGxlZCBjbGluZXQtaWQgDQpmb3Ig
ZG9pbmcgc29tZXRoaW5nIGZvciBtZSIuDQoNCg0KDQoNCkNodWNrIE1vcnRpbW9yZSA8Y21vcnRp
bW9yZUBzYWxlc2ZvcmNlLmNvbT4g0LTT2iAyMDEyLTEyLTE0IDAwOjM5OjAzOg0KDQo+IFRoZSBs
YW5ndWFnZSBpcyBzaW1wbHkgbWVhbnQgdG8gaGVscCBpbGx1c3RyYXRlIGhvdyB0aGUgZnJhbWV3
b3JrIA0KPiBtaWdodCBiZSB1c2VkLiAgIEhvdyBkbyB5b3UgdGhpbmsgaXQgd2lsbCByZXN0cmlj
dCB1c2FnZT8gICBIb3cgDQo+IGNvdWxkIGl0IGJlIGltcHJvdmVkPw0KPiANCj4gLWNtb3J0DQo+
IA0KPiBPbiBEZWMgMTIsIDIwMTIsIGF0IDExOjA0IFBNLCA8emhvdS5zdWppbmdAenRlLmNvbS5j
bj4gd3JvdGU6DQo+IA0KPiANCj4gSW4gInNlY3Rpb24gMyANCj4gIFRoZSB0b2tlbiBzZXJ2aWNl
IGlzIHRoZSBhc3NlcnRpb24gaXNzdWVyOyBpdHMgDQo+ICByb2xlIGlzIHRvIGZ1bGZpbGwgcmVx
dWVzdHMgZnJvbSBjbGllbnRzLCB3aGljaCBwcmVzZW50IHZhcmlvdXMgDQo+ICBjcmVkZW50aWFs
cywgYW5kIG1pbnQgYXNzZXJ0aW9ucyBhcyByZXF1ZXN0ZWQsIGZpbGwgdGhlbSB3aXRoIA0KPiAg
YXBwcm9wcmlhdGUgaW5mb3JtYXRpb24sIGFuZCBzaWduIHRoZW0uIiANCj4gDQo+IA0KPiBBcyBJ
IHVuZGVyc3RhbmQsIGFuIGFzc2VydGlvbiBnZW5lcmF0ZWQgYnkgYSBTVFMsIGlzIGRvbmUgZmxv
bGxvd2luZw0KPiB0aGVzcyBzdGVwczogDQo+IDEuIENsaWVudCBwcmVzZW50cyBjcmVkZW50aWFs
IGFuZCByZXF1ZXN0cyBhbiBhc3NlcnRpb24gDQo+IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9u
IGFuZCBzZW5kcyB0byBDbGllbnQgDQo+IENvcnJlY3Q/IA0KPiANCj4gVGhhdCBtYXkgcmVzdHJp
Y3QgdGhlIHVzZSBjYXNlcyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yayBjb3VsZCANCnN1
cHBvcnQsIA0KPiBpcyBpdCBhIG11c3Q/IA0KPiANCj4gDQo+IA0KPiANCj4gb2F1dGgtYm91bmNl
c0BpZXRmLm9yZyDQtNPaIDIwMTItMTItMTEgMDI6MzM6NTc6DQo+IA0KPiA+IA0KPiA+IFRoZSBJ
RVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSB0aGUgV2ViIEF1dGhvcml6YXRpb24gUHJv
dG9jb2wgV0cNCj4gPiAob2F1dGgpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6
DQo+ID4gLSAnQXNzZXJ0aW9uIEZyYW1ld29yayBmb3IgT0F1dGggMi4wJw0KPiA+ICAgPGRyYWZ0
LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy0wOC50eHQ+IGFzIFByb3Bvc2VkIFN0YW5kYXJkDQo+ID4g
DQo+ID4gVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3
ZWVrcywgYW5kIHNvbGljaXRzDQo+ID4gZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBs
ZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZQ0KPiA+IGlldGZAaWV0Zi5vcmcg
bWFpbGluZyBsaXN0cyBieSAyMDEyLTEyLTI0LiBFeGNlcHRpb25hbGx5LCBjb21tZW50cyBtYXkg
DQpiZQ0KPiA+IHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwg
cGxlYXNlIHJldGFpbiB0aGUNCj4gPiBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBh
bGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4gPiANCj4gPiBBYnN0cmFjdA0KPiA+IA0KPiA+IA0K
PiA+ICAgIFRoaXMgc3BlY2lmaWNhdGlvbiBwcm92aWRlcyBhIGZyYW1ld29yayBmb3IgdGhlIHVz
ZSBvZiBhc3NlcnRpb25zDQo+ID4gICAgd2l0aCBPQXV0aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBu
ZXcgY2xpZW50IGF1dGhlbnRpY2F0aW9uIG1lY2hhbmlzbQ0KPiA+ICAgIGFuZCBhIG5ldyBhdXRo
b3JpemF0aW9uIGdyYW50IHR5cGUuICBNZWNoYW5pc21zIGFyZSBzcGVjaWZpZWQgZm9yDQo+ID4g
ICAgdHJhbnNwb3J0aW5nIGFzc2VydGlvbnMgZHVyaW5nIGludGVyYWN0aW9ucyB3aXRoIGEgdG9r
ZW4gZW5kcG9pbnQsIA0KYXMNCj4gPiAgICB3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBydWxl
cy4NCj4gPiANCj4gPiAgICBUaGUgaW50ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiBpcyB0byBw
cm92aWRlIGEgY29tbW9uIGZyYW1ld29yayANCmZvcg0KPiA+ICAgIE9BdXRoIDIuMCB0byBpbnRl
cndvcmsgd2l0aCBvdGhlciBpZGVudGl0eSBzeXN0ZW1zIHVzaW5nIA0KYXNzZXJ0aW9ucywNCj4g
PiAgICBhbmQgdG8gcHJvdmlkZSBhbHRlcm5hdGl2ZSBjbGllbnQgYXV0aGVudGljYXRpb24gbWVj
aGFuaXNtcy4NCj4gPiANCj4gPiAgICBOb3RlIHRoYXQgdGhpcyBzcGVjaWZpY2F0aW9uIG9ubHkg
ZGVmaW5lcyBhYnN0cmFjdCBtZXNzYWdlIGZsb3dzIA0KYW5kDQo+ID4gICAgcHJvY2Vzc2luZyBy
dWxlcy4gIEluIG9yZGVyIHRvIGJlIGltcGxlbWVudGFibGUsIGNvbXBhbmlvbg0KPiA+ICAgIHNw
ZWNpZmljYXRpb25zIGFyZSBuZWNlc3NhcnkgdG8gcHJvdmlkZSB0aGUgY29ycmVzcG9uZGluZyBj
b25jcmV0ZQ0KPiA+ICAgIGluc3RhbnRpYXRpb25zLg0KPiA+IA0KPiA+IA0KPiA+IA0KPiA+IA0K
PiA+IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWENCj4gPiBodHRwOi8vZGF0YXRyYWNrZXIu
aWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy8NCj4gPiANCj4gPiBJRVNH
IGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+ID4gaHR0cDovL2RhdGF0cmFja2VyLmll
dGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMvYmFsbG90Lw0KPiA+IA0KPiA+
IA0KPiA+IE5vIElQUiBkZWNsYXJhdGlvbnMgaGF2ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBv
biB0aGlzIEktRC4NCj4gPiANCj4gPiANCj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXw0KPiA+IE9BdXRoIG1haWxpbmcgbGlzdA0KPiA+IE9BdXRoQGll
dGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aA0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBPQXV0
aCBtYWlsaW5nIGxpc3QNCj4gT0F1dGhAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9vYXV0aA0K
--=_alternative 0002DDBE48257AD4_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5Gcm9tIHRoZSBsYW5ndWFnZSwgSSBnb3QgYW4gaW1wcmVz
c2lvbiB0aGF0IGFzc2VydGlvbg0KaXMgb25seSBnZW5lcmF0ZWQgYnkgdG9rZW4gc2VydmljZSBh
ZnRlciBjbGllbnRzIHByZXNlbnRpbmcgc29tZSBjcmVkZW50aWFscyw8L2ZvbnQ+PC90dD4NCjxi
cj48dHQ+PGZvbnQgc2l6ZT0yPnRoZXJlIGFyZSBtYXkgYmUgc29tZSBjYXNlcyB0aGF0ICZxdW90
O2Fzc2VydGlvbiZxdW90Ow0KZG9uJ3QgbmVlZCBjbGllbnQncyBjcmVkZW50aWFsLjwvZm9udD48
L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+ZS5nLiwgUmVzb3VyY2Ugb3duZXIgYXMgYSB0b2tl
biBzZXJ2aWNlICZuYnNwO2NvdWxkDQpnZW5lcmF0ZSAmcXVvdDthc3NlcnRpb24mcXVvdDsgdG8g
YSBjbGllbnQgaGUgdHJ1c3RzLCBidSBzaWduaW5nIGEgc3RhdGVtZW50DQp0aGF0ICZxdW90O1Ro
aXMgZGVsZWdhdGlvbiBpcyBnaXZlbiB0byBhIGNsaWVudCBjYWxsZWQgY2xpbmV0LWlkIDwvZm9u
dD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Zm9yIGRvaW5nIHNvbWV0aGluZyBmb3IgbWUm
cXVvdDsuPC9mb250PjwvdHQ+DQo8YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQo8YnI+PHR0Pjxmb250
IHNpemU9Mj5DaHVjayBNb3J0aW1vcmUgJmx0O2Ntb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20mZ3Q7
DQrQtNPaIDIwMTItMTItMTQgMDA6Mzk6MDM6PGJyPg0KPGJyPg0KJmd0OyBUaGUgbGFuZ3VhZ2Ug
aXMgc2ltcGx5IG1lYW50IHRvIGhlbHAgaWxsdXN0cmF0ZSBob3cgdGhlIGZyYW1ld29yaw0KPGJy
Pg0KJmd0OyBtaWdodCBiZSB1c2VkLiAmbmJzcDsgSG93IGRvIHlvdSB0aGluayBpdCB3aWxsIHJl
c3RyaWN0IHVzYWdlPyAmbmJzcDsNCkhvdyA8YnI+DQomZ3Q7IGNvdWxkIGl0IGJlIGltcHJvdmVk
PzwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IC1jbW9y
dDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IE9uIERl
YyAxMiwgMjAxMiwgYXQgMTE6MDQgUE0sICZsdDt6aG91LnN1amluZ0B6dGUuY29tLmNuJmd0OyB3
cm90ZTo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IEluICZxdW90O3NlY3Rpb24gMyA8YnI+DQomZ3Q7ICZuYnNwO1RoZSB0b2tlbiBz
ZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24gaXNzdWVyOyBpdHMgPGJyPg0KJmd0OyAmbmJzcDtyb2xl
IGlzIHRvIGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBjbGllbnRzLCB3aGljaCBwcmVzZW50IHZhcmlv
dXMNCjxicj4NCiZndDsgJm5ic3A7Y3JlZGVudGlhbHMsIGFuZCBtaW50IGFzc2VydGlvbnMgYXMg
cmVxdWVzdGVkLCBmaWxsIHRoZW0gd2l0aA0KPGJyPg0KJmd0OyAmbmJzcDthcHByb3ByaWF0ZSBp
bmZvcm1hdGlvbiwgYW5kIHNpZ24gdGhlbS4mcXVvdDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxi
cj4NCiZndDsgQXMgSSB1bmRlcnN0YW5kLCBhbiBhc3NlcnRpb24gZ2VuZXJhdGVkIGJ5IGEgU1RT
LCBpcyBkb25lIGZsb2xsb3dpbmc8YnI+DQomZ3Q7IHRoZXNzIHN0ZXBzOiA8YnI+DQomZ3Q7IDEu
IENsaWVudCBwcmVzZW50cyBjcmVkZW50aWFsIGFuZCByZXF1ZXN0cyBhbiBhc3NlcnRpb24gPGJy
Pg0KJmd0OyAyLiBTVFMgZ2VuZXJhdGVzIGFzc2VydGlvbiBhbmQgc2VuZHMgdG8gQ2xpZW50IDxi
cj4NCiZndDsgQ29ycmVjdD8gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFRoYXQgbWF5IHJlc3RyaWN0
IHRoZSB1c2UgY2FzZXMgdGhhdCB0aGlzIGFzc2VydGlvbiBmcmFtZXdvcmsgY291bGQNCnN1cHBv
cnQsIDxicj4NCiZndDsgaXMgaXQgYSBtdXN0PyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgb2F1dGgtYm91bmNlc0BpZXRmLm9yZyDQtNPaIDIw
MTItMTItMTEgMDI6MzM6NTc6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAm
Z3Q7IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSB0aGUgV2ViIEF1dGhvcml6
YXRpb24gUHJvdG9jb2wNCldHPGJyPg0KJmd0OyAmZ3Q7IChvYXV0aCkgdG8gY29uc2lkZXIgdGhl
IGZvbGxvd2luZyBkb2N1bWVudDo8YnI+DQomZ3Q7ICZndDsgLSAnQXNzZXJ0aW9uIEZyYW1ld29y
ayBmb3IgT0F1dGggMi4wJzxicj4NCiZndDsgJmd0OyAmbmJzcDsgJmx0O2RyYWZ0LWlldGYtb2F1
dGgtYXNzZXJ0aW9ucy0wOC50eHQmZ3Q7IGFzIFByb3Bvc2VkDQpTdGFuZGFyZDxicj4NCiZndDsg
Jmd0OyA8YnI+DQomZ3Q7ICZndDsgVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGlu
IHRoZSBuZXh0IGZldyB3ZWVrcywgYW5kDQpzb2xpY2l0czxicj4NCiZndDsgJmd0OyBmaW5hbCBj
b21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMN
CnRvIHRoZTxicj4NCiZndDsgJmd0OyBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMgYnkgMjAx
Mi0xMi0yNC4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMNCm1heSBiZTxicj4NCiZndDsgJmd0OyBz
ZW50IHRvIGllc2dAaWV0Zi5vcmcgaW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBsZWFzZSByZXRh
aW4NCnRoZTxicj4NCiZndDsgJmd0OyBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBh
bGxvdyBhdXRvbWF0ZWQgc29ydGluZy48YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IEFi
c3RyYWN0PGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJm5i
c3A7ICZuYnNwO1RoaXMgc3BlY2lmaWNhdGlvbiBwcm92aWRlcyBhIGZyYW1ld29yayBmb3IgdGhl
DQp1c2Ugb2YgYXNzZXJ0aW9uczxicj4NCiZndDsgJmd0OyAmbmJzcDsgJm5ic3A7d2l0aCBPQXV0
aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBuZXcgY2xpZW50IGF1dGhlbnRpY2F0aW9uDQptZWNoYW5p
c208YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2FuZCBhIG5ldyBhdXRob3JpemF0aW9uIGdy
YW50IHR5cGUuICZuYnNwO01lY2hhbmlzbXMNCmFyZSBzcGVjaWZpZWQgZm9yPGJyPg0KJmd0OyAm
Z3Q7ICZuYnNwOyAmbmJzcDt0cmFuc3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rp
b25zIHdpdGgNCmEgdG9rZW4gZW5kcG9pbnQsIGFzPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJz
cDt3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBydWxlcy48YnI+DQomZ3Q7ICZndDsgPGJyPg0K
Jmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtUaGUgaW50ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiBp
cyB0byBwcm92aWRlIGENCmNvbW1vbiBmcmFtZXdvcmsgZm9yPGJyPg0KJmd0OyAmZ3Q7ICZuYnNw
OyAmbmJzcDtPQXV0aCAyLjAgdG8gaW50ZXJ3b3JrIHdpdGggb3RoZXIgaWRlbnRpdHkgc3lzdGVt
cw0KdXNpbmcgYXNzZXJ0aW9ucyw8YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2FuZCB0byBw
cm92aWRlIGFsdGVybmF0aXZlIGNsaWVudCBhdXRoZW50aWNhdGlvbg0KbWVjaGFuaXNtcy48YnI+
DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtOb3RlIHRoYXQgdGhpcyBz
cGVjaWZpY2F0aW9uIG9ubHkgZGVmaW5lcyBhYnN0cmFjdA0KbWVzc2FnZSBmbG93cyBhbmQ8YnI+
DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3Byb2Nlc3NpbmcgcnVsZXMuICZuYnNwO0luIG9yZGVy
IHRvIGJlIGltcGxlbWVudGFibGUsDQpjb21wYW5pb248YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZu
YnNwO3NwZWNpZmljYXRpb25zIGFyZSBuZWNlc3NhcnkgdG8gcHJvdmlkZSB0aGUgY29ycmVzcG9u
ZGluZw0KY29uY3JldGU8YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2luc3RhbnRpYXRpb25z
Ljxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZn
dDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYTxicj4N
CiZndDsgJmd0OyBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1
dGgtYXNzZXJ0aW9ucy88YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IElFU0cgZGlzY3Vz
c2lvbiBjYW4gYmUgdHJhY2tlZCB2aWE8YnI+DQomZ3Q7ICZndDsgaHR0cDovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMvYmFsbG90Lzxicj4NCiZn
dDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IE5vIElQUiBkZWNsYXJhdGlv
bnMgaGF2ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC48YnI+DQomZ3Q7ICZn
dDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgJmd0OyBPQXV0aCBtYWlsaW5nIGxp
c3Q8YnI+DQomZ3Q7ICZndDsgT0F1dGhAaWV0Zi5vcmc8YnI+DQomZ3Q7ICZndDsgaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aDxicj4NCiZndDsgX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7IE9BdXRoIG1haWxp
bmcgbGlzdDxicj4NCiZndDsgT0F1dGhAaWV0Zi5vcmc8YnI+DQomZ3Q7IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGg8L2ZvbnQ+PC90dD4NCg==
--=_alternative 0002DDBE48257AD4_=--

From cmortimore@salesforce.com  Thu Dec 13 18:10:12 2012
Return-Path: <cmortimore@salesforce.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A15D21F8C12; Thu, 13 Dec 2012 18:10:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.352
X-Spam-Level: 
X-Spam-Status: No, score=-6.352 tagged_above=-999 required=5 tests=[AWL=-0.176, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t4tTAfpdFUjV; Thu, 13 Dec 2012 18:10:11 -0800 (PST)
Received: from exprod8og107.obsmtp.com (exprod8og107.obsmtp.com [64.18.3.94]) by ietfa.amsl.com (Postfix) with SMTP id 0368021F8C11; Thu, 13 Dec 2012 18:10:10 -0800 (PST)
Received: from exsfm-hub5.internal.salesforce.com ([204.14.239.233]) by exprod8ob107.postini.com ([64.18.7.12]) with SMTP ID DSNKUMqKgpnLHvEpxKmtF45GKwMcgcA+zNiB@postini.com; Thu, 13 Dec 2012 18:10:11 PST
Received: from EXSFM-MB03.internal.salesforce.com ([10.1.127.58]) by exsfm-hub5.internal.salesforce.com ([10.1.127.5]) with mapi; Thu, 13 Dec 2012 18:10:10 -0800
From: Chuck Mortimore <cmortimore@salesforce.com>
To: "zhou.sujing@zte.com.cn" <zhou.sujing@zte.com.cn>
Date: Thu, 13 Dec 2012 18:08:34 -0800
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
Thread-Topic: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
Thread-Index: Ac3ZoCS/nRHUZjSLTxyTa6Lheht76w==
Message-ID: <7CCC0903-4D4C-4F49-A7CA-ECA148935B47@salesforce.com>
References: <OFE9540EB0.6D71176A-ON48257AD4.00025F53-48257AD4.0002DDC1@zte.com.cn>
In-Reply-To: <OFE9540EB0.6D71176A-ON48257AD4.00025F53-48257AD4.0002DDC1@zte.com.cn>
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_7CCC09034D4C4F49A7CAECA148935B47salesforcecom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, IETF-Announce <ietf-announce@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 02:10:12 -0000

--_000_7CCC09034D4C4F49A7CAECA148935B47salesforcecom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQpPbiBEZWMgMTMsIDIwMTIsIGF0IDQ6MzAgUE0sICJ6aG91LnN1amluZ0B6dGUuY29tLmNuPG1h
aWx0bzp6aG91LnN1amluZ0B6dGUuY29tLmNuPiIgPHpob3Uuc3VqaW5nQHp0ZS5jb20uY248bWFp
bHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24+PiB3cm90ZToNCg0KDQpGcm9tIHRoZSBsYW5ndWFn
ZSwgSSBnb3QgYW4gaW1wcmVzc2lvbiB0aGF0IGFzc2VydGlvbiBpcyBvbmx5IGdlbmVyYXRlZCBi
eSB0b2tlbiBzZXJ2aWNlIGFmdGVyIGNsaWVudHMgcHJlc2VudGluZyBzb21lIGNyZWRlbnRpYWxz
LA0KdGhlcmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRoYXQgImFzc2VydGlvbiIgZG9uJ3QgbmVl
ZCBjbGllbnQncyBjcmVkZW50aWFsLg0KZS5nLiwgUmVzb3VyY2Ugb3duZXIgYXMgYSB0b2tlbiBz
ZXJ2aWNlICBjb3VsZCBnZW5lcmF0ZSAiYXNzZXJ0aW9uIiB0byBhIGNsaWVudCBoZSB0cnVzdHMs
IGJ1IHNpZ25pbmcgYSBzdGF0ZW1lbnQgdGhhdCAiVGhpcyBkZWxlZ2F0aW9uIGlzIGdpdmVuIHRv
IGEgY2xpZW50IGNhbGxlZCBjbGluZXQtaWQNCmZvciBkb2luZyBzb21ldGhpbmcgZm9yIG1lIi4N
Cg0KU28gaG93IGRvZXMgdGhlIFNUUyB0cnVzdCB0aGUgY2xpZW50PyAgIFByZXN1bWFibHkgaWYg
aXQgaXMgdHJ1c3RlZCBpdCBoYXMgc29tZSBsZXZlbCBvZiBhdXRoZW50aWNhdGlvbiwgeWVzPw0K
DQotY21vcnQNCg0KDQoNCg0KDQpDaHVjayBNb3J0aW1vcmUgPGNtb3J0aW1vcmVAc2FsZXNmb3Jj
ZS5jb208bWFpbHRvOmNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20+PiDlhpnkuo4gMjAxMi0xMi0x
NCAwMDozOTowMzoNCg0KPiBUaGUgbGFuZ3VhZ2UgaXMgc2ltcGx5IG1lYW50IHRvIGhlbHAgaWxs
dXN0cmF0ZSBob3cgdGhlIGZyYW1ld29yaw0KPiBtaWdodCBiZSB1c2VkLiAgIEhvdyBkbyB5b3Ug
dGhpbmsgaXQgd2lsbCByZXN0cmljdCB1c2FnZT8gICBIb3cNCj4gY291bGQgaXQgYmUgaW1wcm92
ZWQ/DQo+DQo+IC1jbW9ydA0KPg0KPiBPbiBEZWMgMTIsIDIwMTIsIGF0IDExOjA0IFBNLCA8emhv
dS5zdWppbmdAenRlLmNvbS5jbjxtYWlsdG86emhvdS5zdWppbmdAenRlLmNvbS5jbj4+IHdyb3Rl
Og0KPg0KPg0KPiBJbiAic2VjdGlvbiAzDQo+ICBUaGUgdG9rZW4gc2VydmljZSBpcyB0aGUgYXNz
ZXJ0aW9uIGlzc3VlcjsgaXRzDQo+ICByb2xlIGlzIHRvIGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBj
bGllbnRzLCB3aGljaCBwcmVzZW50IHZhcmlvdXMNCj4gIGNyZWRlbnRpYWxzLCBhbmQgbWludCBh
c3NlcnRpb25zIGFzIHJlcXVlc3RlZCwgZmlsbCB0aGVtIHdpdGgNCj4gIGFwcHJvcHJpYXRlIGlu
Zm9ybWF0aW9uLCBhbmQgc2lnbiB0aGVtLiINCj4NCj4NCj4gQXMgSSB1bmRlcnN0YW5kLCBhbiBh
c3NlcnRpb24gZ2VuZXJhdGVkIGJ5IGEgU1RTLCBpcyBkb25lIGZsb2xsb3dpbmcNCj4gdGhlc3Mg
c3RlcHM6DQo+IDEuIENsaWVudCBwcmVzZW50cyBjcmVkZW50aWFsIGFuZCByZXF1ZXN0cyBhbiBh
c3NlcnRpb24NCj4gMi4gU1RTIGdlbmVyYXRlcyBhc3NlcnRpb24gYW5kIHNlbmRzIHRvIENsaWVu
dA0KPiBDb3JyZWN0Pw0KPg0KPiBUaGF0IG1heSByZXN0cmljdCB0aGUgdXNlIGNhc2VzIHRoYXQg
dGhpcyBhc3NlcnRpb24gZnJhbWV3b3JrIGNvdWxkIHN1cHBvcnQsDQo+IGlzIGl0IGEgbXVzdD8N
Cj4NCj4NCj4NCj4NCj4gb2F1dGgtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86b2F1dGgtYm91bmNl
c0BpZXRmLm9yZz4g5YaZ5LqOIDIwMTItMTItMTEgMDI6MzM6NTc6DQo+DQo+ID4NCj4gPiBUaGUg
SUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIFdlYiBBdXRob3JpemF0aW9uIFBy
b3RvY29sIFdHDQo+ID4gKG9hdXRoKSB0byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50
Og0KPiA+IC0gJ0Fzc2VydGlvbiBGcmFtZXdvcmsgZm9yIE9BdXRoIDIuMCcNCj4gPiAgIDxkcmFm
dC1pZXRmLW9hdXRoLWFzc2VydGlvbnMtMDgudHh0PiBhcyBQcm9wb3NlZCBTdGFuZGFyZA0KPiA+
DQo+ID4gVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3
ZWVrcywgYW5kIHNvbGljaXRzDQo+ID4gZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBs
ZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZQ0KPiA+IGlldGZAaWV0Zi5vcmc8
bWFpbHRvOmlldGZAaWV0Zi5vcmc+IG1haWxpbmcgbGlzdHMgYnkgMjAxMi0xMi0yNC4gRXhjZXB0
aW9uYWxseSwgY29tbWVudHMgbWF5IGJlDQo+ID4gc2VudCB0byBpZXNnQGlldGYub3JnPG1haWx0
bzppZXNnQGlldGYub3JnPiBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0
aGUNCj4gPiBiZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQg
c29ydGluZy4NCj4gPg0KPiA+IEFic3RyYWN0DQo+ID4NCj4gPg0KPiA+ICAgIFRoaXMgc3BlY2lm
aWNhdGlvbiBwcm92aWRlcyBhIGZyYW1ld29yayBmb3IgdGhlIHVzZSBvZiBhc3NlcnRpb25zDQo+
ID4gICAgd2l0aCBPQXV0aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBuZXcgY2xpZW50IGF1dGhlbnRp
Y2F0aW9uIG1lY2hhbmlzbQ0KPiA+ICAgIGFuZCBhIG5ldyBhdXRob3JpemF0aW9uIGdyYW50IHR5
cGUuICBNZWNoYW5pc21zIGFyZSBzcGVjaWZpZWQgZm9yDQo+ID4gICAgdHJhbnNwb3J0aW5nIGFz
c2VydGlvbnMgZHVyaW5nIGludGVyYWN0aW9ucyB3aXRoIGEgdG9rZW4gZW5kcG9pbnQsIGFzDQo+
ID4gICAgd2VsbCBhcyBnZW5lcmFsIHByb2Nlc3NpbmcgcnVsZXMuDQo+ID4NCj4gPiAgICBUaGUg
aW50ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiBpcyB0byBwcm92aWRlIGEgY29tbW9uIGZyYW1l
d29yayBmb3INCj4gPiAgICBPQXV0aCAyLjAgdG8gaW50ZXJ3b3JrIHdpdGggb3RoZXIgaWRlbnRp
dHkgc3lzdGVtcyB1c2luZyBhc3NlcnRpb25zLA0KPiA+ICAgIGFuZCB0byBwcm92aWRlIGFsdGVy
bmF0aXZlIGNsaWVudCBhdXRoZW50aWNhdGlvbiBtZWNoYW5pc21zLg0KPiA+DQo+ID4gICAgTm90
ZSB0aGF0IHRoaXMgc3BlY2lmaWNhdGlvbiBvbmx5IGRlZmluZXMgYWJzdHJhY3QgbWVzc2FnZSBm
bG93cyBhbmQNCj4gPiAgICBwcm9jZXNzaW5nIHJ1bGVzLiAgSW4gb3JkZXIgdG8gYmUgaW1wbGVt
ZW50YWJsZSwgY29tcGFuaW9uDQo+ID4gICAgc3BlY2lmaWNhdGlvbnMgYXJlIG5lY2Vzc2FyeSB0
byBwcm92aWRlIHRoZSBjb3JyZXNwb25kaW5nIGNvbmNyZXRlDQo+ID4gICAgaW5zdGFudGlhdGlv
bnMuDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPiBUaGUgZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlh
DQo+ID4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFz
c2VydGlvbnMvDQo+ID4NCj4gPiBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+
ID4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2Vy
dGlvbnMvYmFsbG90Lw0KPiA+DQo+ID4NCj4gPiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVl
biBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+ID4NCj4gPg0KPiA+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gT0F1dGggbWFpbGlu
ZyBsaXN0DQo+ID4gT0F1dGhAaWV0Zi5vcmc8bWFpbHRvOk9BdXRoQGlldGYub3JnPg0KPiA+IGh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGgNCj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gT0F1dGggbWFpbGluZyBsaXN0
DQo+IE9BdXRoQGlldGYub3JnPG1haWx0bzpPQXV0aEBpZXRmLm9yZz4NCj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aA0K

--_000_7CCC09034D4C4F49A7CAECA148935B47salesforcecom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPjxkaXY+PGJyPjwvZGl2
PjxkaXY+T24gRGVjIDEzLCAyMDEyLCBhdCA0OjMwIFBNLCAiPGEgaHJlZj0ibWFpbHRvOnpob3Uu
c3VqaW5nQHp0ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248L2E+IiAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248
L2E+Jmd0OyB3cm90ZTo8YnI+PGJyPjwvZGl2PjxkaXY+PC9kaXY+PGJsb2NrcXVvdGUgdHlwZT0i
Y2l0ZSI+PGRpdj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0iMiI+RnJvbSB0aGUgbGFuZ3VhZ2UsIEkg
Z290IGFuIGltcHJlc3Npb24gdGhhdCBhc3NlcnRpb24NCmlzIG9ubHkgZ2VuZXJhdGVkIGJ5IHRv
a2VuIHNlcnZpY2UgYWZ0ZXIgY2xpZW50cyBwcmVzZW50aW5nIHNvbWUgY3JlZGVudGlhbHMsPC9m
b250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9IjIiPnRoZXJlIGFyZSBtYXkgYmUgc29tZSBj
YXNlcyB0aGF0ICJhc3NlcnRpb24iDQpkb24ndCBuZWVkIGNsaWVudCdzIGNyZWRlbnRpYWwuPC9m
b250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9IjIiPmUuZy4sIFJlc291cmNlIG93bmVyIGFz
IGEgdG9rZW4gc2VydmljZSAmbmJzcDtjb3VsZA0KZ2VuZXJhdGUgImFzc2VydGlvbiIgdG8gYSBj
bGllbnQgaGUgdHJ1c3RzLCBidSBzaWduaW5nIGEgc3RhdGVtZW50DQp0aGF0ICJUaGlzIGRlbGVn
YXRpb24gaXMgZ2l2ZW4gdG8gYSBjbGllbnQgY2FsbGVkIGNsaW5ldC1pZCA8L2ZvbnQ+PC90dD4N
Cjxicj48dHQ+PGZvbnQgc2l6ZT0iMiI+Zm9yIGRvaW5nIHNvbWV0aGluZyBmb3IgbWUiLjwvZm9u
dD48L3R0Pg0KPGJyPjwvZGl2PjwvYmxvY2txdW90ZT48ZGl2Pjxicj48L2Rpdj48ZGl2PlNvIGhv
dyBkb2VzIHRoZSBTVFMgdHJ1c3QgdGhlIGNsaWVudD8gJm5ic3A7IFByZXN1bWFibHkgaWYgaXQg
aXMgdHJ1c3RlZCBpdCBoYXMgc29tZSBsZXZlbCBvZiBhdXRoZW50aWNhdGlvbiwgeWVzPzwvZGl2
PjxkaXY+PGJyPjwvZGl2PjxkaXY+LWNtb3J0PC9kaXY+PGJyPjxibG9ja3F1b3RlIHR5cGU9ImNp
dGUiPjxkaXY+DQo8YnI+DQo8YnI+DQo8YnI+DQo8YnI+PHR0Pjxmb250IHNpemU9IjIiPkNodWNr
IE1vcnRpbW9yZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20i
PmNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb208L2E+Jmd0Ow0K5YaZ5LqOIDIwMTItMTItMTQgMDA6
Mzk6MDM6PGJyPg0KPGJyPg0KJmd0OyBUaGUgbGFuZ3VhZ2UgaXMgc2ltcGx5IG1lYW50IHRvIGhl
bHAgaWxsdXN0cmF0ZSBob3cgdGhlIGZyYW1ld29yaw0KPGJyPg0KJmd0OyBtaWdodCBiZSB1c2Vk
LiAmbmJzcDsgSG93IGRvIHlvdSB0aGluayBpdCB3aWxsIHJlc3RyaWN0IHVzYWdlPyAmbmJzcDsN
CkhvdyA8YnI+DQomZ3Q7IGNvdWxkIGl0IGJlIGltcHJvdmVkPzwvZm9udD48L3R0Pg0KPGJyPjx0
dD48Zm9udCBzaXplPSIyIj4mZ3Q7IDxicj4NCiZndDsgLWNtb3J0PC9mb250PjwvdHQ+DQo8YnI+
PHR0Pjxmb250IHNpemU9IjIiPiZndDsgPGJyPg0KJmd0OyBPbiBEZWMgMTIsIDIwMTIsIGF0IDEx
OjA0IFBNLCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24iPnpob3Uu
c3VqaW5nQHp0ZS5jb20uY248L2E+Jmd0OyB3cm90ZTo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZv
bnQgc2l6ZT0iMiI+Jmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgSW4gInNlY3Rpb24gMyA8YnI+
DQomZ3Q7ICZuYnNwO1RoZSB0b2tlbiBzZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24gaXNzdWVyOyBp
dHMgPGJyPg0KJmd0OyAmbmJzcDtyb2xlIGlzIHRvIGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBjbGll
bnRzLCB3aGljaCBwcmVzZW50IHZhcmlvdXMNCjxicj4NCiZndDsgJm5ic3A7Y3JlZGVudGlhbHMs
IGFuZCBtaW50IGFzc2VydGlvbnMgYXMgcmVxdWVzdGVkLCBmaWxsIHRoZW0gd2l0aA0KPGJyPg0K
Jmd0OyAmbmJzcDthcHByb3ByaWF0ZSBpbmZvcm1hdGlvbiwgYW5kIHNpZ24gdGhlbS4iIDxicj4N
CiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEFzIEkgdW5kZXJzdGFuZCwgYW4gYXNzZXJ0aW9u
IGdlbmVyYXRlZCBieSBhIFNUUywgaXMgZG9uZSBmbG9sbG93aW5nPGJyPg0KJmd0OyB0aGVzcyBz
dGVwczogPGJyPg0KJmd0OyAxLiBDbGllbnQgcHJlc2VudHMgY3JlZGVudGlhbCBhbmQgcmVxdWVz
dHMgYW4gYXNzZXJ0aW9uIDxicj4NCiZndDsgMi4gU1RTIGdlbmVyYXRlcyBhc3NlcnRpb24gYW5k
IHNlbmRzIHRvIENsaWVudCA8YnI+DQomZ3Q7IENvcnJlY3Q/IDxicj4NCiZndDsgPGJyPg0KJmd0
OyBUaGF0IG1heSByZXN0cmljdCB0aGUgdXNlIGNhc2VzIHRoYXQgdGhpcyBhc3NlcnRpb24gZnJh
bWV3b3JrIGNvdWxkDQpzdXBwb3J0LCA8YnI+DQomZ3Q7IGlzIGl0IGEgbXVzdD8gPGJyPg0KJmd0
OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxhIGhyZWY9Im1h
aWx0bzpvYXV0aC1ib3VuY2VzQGlldGYub3JnIj5vYXV0aC1ib3VuY2VzQGlldGYub3JnPC9hPiDl
hpnkuo4gMjAxMi0xMi0xMSAwMjozMzo1Nzo8YnI+DQomZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+
DQomZ3Q7ICZndDsgVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBXZWIg
QXV0aG9yaXphdGlvbiBQcm90b2NvbA0KV0c8YnI+DQomZ3Q7ICZndDsgKG9hdXRoKSB0byBjb25z
aWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Ojxicj4NCiZndDsgJmd0OyAtICdBc3NlcnRpb24g
RnJhbWV3b3JrIGZvciBPQXV0aCAyLjAnPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbHQ7ZHJhZnQt
aWV0Zi1vYXV0aC1hc3NlcnRpb25zLTA4LnR4dCZndDsgYXMgUHJvcG9zZWQNClN0YW5kYXJkPGJy
Pg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVj
aXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQNCnNvbGljaXRzPGJyPg0KJmd0OyAmZ3Q7
IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBj
b21tZW50cw0KdG8gdGhlPGJyPg0KJmd0OyAmZ3Q7IDxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYu
b3JnIj5pZXRmQGlldGYub3JnPC9hPiBtYWlsaW5nIGxpc3RzIGJ5IDIwMTItMTItMjQuIEV4Y2Vw
dGlvbmFsbHksIGNvbW1lbnRzDQptYXkgYmU8YnI+DQomZ3Q7ICZndDsgc2VudCB0byA8YSBocmVm
PSJtYWlsdG86aWVzZ0BpZXRmLm9yZyI+aWVzZ0BpZXRmLm9yZzwvYT4gaW5zdGVhZC4gSW4gZWl0
aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4NCnRoZTxicj4NCiZndDsgJmd0OyBiZWdpbm5pbmcgb2Yg
dGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy48YnI+DQomZ3Q7ICZn
dDsgPGJyPg0KJmd0OyAmZ3Q7IEFic3RyYWN0PGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0
OyA8YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO1RoaXMgc3BlY2lmaWNhdGlvbiBwcm92aWRl
cyBhIGZyYW1ld29yayBmb3IgdGhlDQp1c2Ugb2YgYXNzZXJ0aW9uczxicj4NCiZndDsgJmd0OyAm
bmJzcDsgJm5ic3A7d2l0aCBPQXV0aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBuZXcgY2xpZW50IGF1
dGhlbnRpY2F0aW9uDQptZWNoYW5pc208YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2FuZCBh
IG5ldyBhdXRob3JpemF0aW9uIGdyYW50IHR5cGUuICZuYnNwO01lY2hhbmlzbXMNCmFyZSBzcGVj
aWZpZWQgZm9yPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDt0cmFuc3BvcnRpbmcgYXNzZXJ0
aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zIHdpdGgNCmEgdG9rZW4gZW5kcG9pbnQsIGFzPGJyPg0K
Jmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDt3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBydWxlcy48
YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtUaGUgaW50ZW50IG9m
IHRoaXMgc3BlY2lmaWNhdGlvbiBpcyB0byBwcm92aWRlIGENCmNvbW1vbiBmcmFtZXdvcmsgZm9y
PGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtPQXV0aCAyLjAgdG8gaW50ZXJ3b3JrIHdpdGgg
b3RoZXIgaWRlbnRpdHkgc3lzdGVtcw0KdXNpbmcgYXNzZXJ0aW9ucyw8YnI+DQomZ3Q7ICZndDsg
Jm5ic3A7ICZuYnNwO2FuZCB0byBwcm92aWRlIGFsdGVybmF0aXZlIGNsaWVudCBhdXRoZW50aWNh
dGlvbg0KbWVjaGFuaXNtcy48YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAm
bmJzcDtOb3RlIHRoYXQgdGhpcyBzcGVjaWZpY2F0aW9uIG9ubHkgZGVmaW5lcyBhYnN0cmFjdA0K
bWVzc2FnZSBmbG93cyBhbmQ8YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3Byb2Nlc3Npbmcg
cnVsZXMuICZuYnNwO0luIG9yZGVyIHRvIGJlIGltcGxlbWVudGFibGUsDQpjb21wYW5pb248YnI+
DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3NwZWNpZmljYXRpb25zIGFyZSBuZWNlc3NhcnkgdG8g
cHJvdmlkZSB0aGUgY29ycmVzcG9uZGluZw0KY29uY3JldGU8YnI+DQomZ3Q7ICZndDsgJm5ic3A7
ICZuYnNwO2luc3RhbnRpYXRpb25zLjxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJy
Pg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgVGhlIGZpbGUgY2Fu
IGJlIG9idGFpbmVkIHZpYTxicj4NCiZndDsgJmd0OyA8YSBocmVmPSJodHRwOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy8iPmh0dHA6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLzwvYT48YnI+
DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tl
ZCB2aWE8YnI+DQomZ3Q7ICZndDsgPGEgaHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMvYmFsbG90LyI+aHR0cDovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMvYmFsbG90LzwvYT48
YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBObyBJUFIgZGVj
bGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuPGJyPg0K
Jmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7ICZndDsgT0F1dGggbWFp
bGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7IDxhIGhyZWY9Im1haWx0bzpPQXV0aEBpZXRmLm9yZyI+
T0F1dGhAaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OyAmZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGgiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vb2F1dGg8L2E+PGJyPg0KJmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgT0F1dGggbWFpbGluZyBsaXN0PGJyPg0K
Jmd0OyA8YSBocmVmPSJtYWlsdG86T0F1dGhAaWV0Zi5vcmciPk9BdXRoQGlldGYub3JnPC9hPjxi
cj4NCiZndDsgPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9v
YXV0aCI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aDwvYT48L2Zv
bnQ+PC90dD4NCjwvZGl2PjwvYmxvY2txdW90ZT48L2JvZHk+PC9odG1sPg==

--_000_7CCC09034D4C4F49A7CAECA148935B47salesforcecom_--

From zhou.sujing@zte.com.cn  Thu Dec 13 18:27:25 2012
Return-Path: <zhou.sujing@zte.com.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 5A91021F8BD2; Thu, 13 Dec 2012 18:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.003
X-Spam-Level: 
X-Spam-Status: No, score=-98.003 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6bn6MTENeOo; Thu, 13 Dec 2012 18:27:24 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 943DF21F8AD2; Thu, 13 Dec 2012 18:27:23 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 076271243AF0; Fri, 14 Dec 2012 10:29:15 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 00221724CD2; Fri, 14 Dec 2012 10:16:24 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id qBE2R4ei022614; Fri, 14 Dec 2012 10:27:04 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <7CCC0903-4D4C-4F49-A7CA-ECA148935B47@salesforce.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Subject: Re: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFB336BD6F.D58307B1-ON48257AD4.000C51F0-48257AD4.000D954A@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Fri, 14 Dec 2012 10:26:50 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-12-14 10:26:57, Serialize complete at 2012-12-14 10:26:57
Content-Type: multipart/alternative; boundary="=_alternative 000D954948257AD4_="
X-MAIL: mse01.zte.com.cn qBE2R4ei022614
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 02:27:25 -0000

This is a multipart message in MIME format.
--=_alternative 000D954948257AD4_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SSBhbSBub3Qgc3VyZSBpZiB0aGUgZm9sbG93aW5nIHVzZWNhc2UgDQpodHRwOi8vd3d3LmlldGYu
b3JnL21haWwtYXJjaGl2ZS93ZWIvb2F1dGgvY3VycmVudC9tc2cxMDIzMy5odG1sDQpjb3VsZCBi
ZSBzdXBwb3J0ZWQgYnkgYXNzZXJ0aW9uIGZyYW1ld29ya6OsDQpXZSBoYXZlIHNvbWUgZGlzY3Vz
c2lvbiBpbiANCmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9jdXJy
ZW50L21zZzEwMjAzLmh0bWwNCmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9v
YXV0aC9jdXJyZW50L21zZzEwMTk4Lmh0bWwgDQoNCkluIG15IHVzZSBjYXNlIG9yIGluIHNvbWUg
b3RoZXIgY2FzZXMsIGFzc2VydGlvbnMgZG9uJ3QgbmVlZCBjb25maWRlbnRpYWwgDQpwcm90ZWN0
aW9uLCANCmJhc2ljYWxseSBTVFMgZG9uJ3QgaGF2ZSB0byBhdXRoZW50aWNhdGUgYSBjbGllbnQg
YmVmb3JlIGlzc3VlaW5nIA0KImFzc2VydGlvbiIsIGlmIGl0IGNvdWxkIGJlIGNhbGxlZCBhc3Nl
cnRpb24gaGVyZS4NCg0KRXhhbXBsZSxJIHRydXN0IG15IGxheXdlciwgSSBtYXkgaXNzdWUgYW4g
ImFzc2VydGlvbiIgc3RhdGluZyBkZWxlZ2F0aW9uIA0KaW4gYWR2YW5jZSwgYW5kIHNlbmQgdG8g
dGhlIGxhd3llciB3aGVuIGl0IGlzIG5lZWRlZCwNCml0IGNvdWxkIGJlIEkgZ2l2ZSB0aGUgYXNz
ZXJ0aW9uIHRvIGEgZmFsc2UgbGF3eWVyLCBidXQgaXQgZG9lcyBub3QgDQptYXR0ZXIsIGJlY2F1
c2UgdGhlIGxhd3llciBoYXMgdG8gcHJvdmUgaGUga25vd3Mgc29tZSBjcmVkZW50aWFsIA0KY29y
cmVzcG9uZGluZyB0byBoaXMgSUQsDQp3aG8gaXMgZGVsZWdhdGVkIHNvbWUgcmlnaHRzLg0KDQpJ
ZiBhc3NlcnRpb24gZnJhbWV3b3JrIHdhbnQgdG8gc3VwcG9ydCB0aGlzIHVzZSBjYXNlLCB0aGVu
IGdlbmVyYXRpb24gb2YgDQphc3NlcnRpb24gc2hvdWxkIGJlIHJlbGF4ZWQsDQpvdGhlcndpc2Ug
bmV3IHdvcmsgaXMgcmVxdWlyZWQgdG8gc3VwcG9ydCB0aGUgdXNlIGNhc2UuDQoNCg0KDQpDaHVj
ayBNb3J0aW1vcmUgPGNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20+INC009ogMjAxMi0xMi0xNCAx
MDowODozNDoNCg0KPiBPbiBEZWMgMTMsIDIwMTIsIGF0IDQ6MzAgUE0sICJ6aG91LnN1amluZ0B6
dGUuY29tLmNuIiANCjx6aG91LnN1amluZ0B6dGUuY29tLmNuDQo+ID4gd3JvdGU6DQoNCj4gDQo+
IEZyb20gdGhlIGxhbmd1YWdlLCBJIGdvdCBhbiBpbXByZXNzaW9uIHRoYXQgYXNzZXJ0aW9uIGlz
IG9ubHkgDQo+IGdlbmVyYXRlZCBieSB0b2tlbiBzZXJ2aWNlIGFmdGVyIGNsaWVudHMgcHJlc2Vu
dGluZyBzb21lIGNyZWRlbnRpYWxzLCANCj4gdGhlcmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRo
YXQgImFzc2VydGlvbiIgZG9uJ3QgbmVlZCBjbGllbnQncyANCmNyZWRlbnRpYWwuIA0KPiBlLmcu
LCBSZXNvdXJjZSBvd25lciBhcyBhIHRva2VuIHNlcnZpY2UgIGNvdWxkIGdlbmVyYXRlICJhc3Nl
cnRpb24iIA0KPiB0byBhIGNsaWVudCBoZSB0cnVzdHMsIGJ1IHNpZ25pbmcgYSBzdGF0ZW1lbnQg
dGhhdCAiVGhpcyBkZWxlZ2F0aW9uIA0KPiBpcyBnaXZlbiB0byBhIGNsaWVudCBjYWxsZWQgY2xp
bmV0LWlkIA0KPiBmb3IgZG9pbmcgc29tZXRoaW5nIGZvciBtZSIuIA0KPiANCj4gU28gaG93IGRv
ZXMgdGhlIFNUUyB0cnVzdCB0aGUgY2xpZW50PyAgIFByZXN1bWFibHkgaWYgaXQgaXMgdHJ1c3Rl
ZCANCj4gaXQgaGFzIHNvbWUgbGV2ZWwgb2YgYXV0aGVudGljYXRpb24sIHllcz8NCj4gDQo+IC1j
bW9ydA0KPiANCj4gDQo+IA0KPiANCj4gDQo+IENodWNrIE1vcnRpbW9yZSA8Y21vcnRpbW9yZUBz
YWxlc2ZvcmNlLmNvbT4g0LTT2iAyMDEyLTEyLTE0IDAwOjM5OjAzOg0KPiANCj4gPiBUaGUgbGFu
Z3VhZ2UgaXMgc2ltcGx5IG1lYW50IHRvIGhlbHAgaWxsdXN0cmF0ZSBob3cgdGhlIGZyYW1ld29y
ayANCj4gPiBtaWdodCBiZSB1c2VkLiAgIEhvdyBkbyB5b3UgdGhpbmsgaXQgd2lsbCByZXN0cmlj
dCB1c2FnZT8gICBIb3cgDQo+ID4gY291bGQgaXQgYmUgaW1wcm92ZWQ/IA0KPiA+IA0KPiA+IC1j
bW9ydCANCj4gPiANCj4gPiBPbiBEZWMgMTIsIDIwMTIsIGF0IDExOjA0IFBNLCA8emhvdS5zdWpp
bmdAenRlLmNvbS5jbj4gd3JvdGU6IA0KPiA+IA0KPiA+IA0KPiA+IEluICJzZWN0aW9uIDMgDQo+
ID4gIFRoZSB0b2tlbiBzZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24gaXNzdWVyOyBpdHMgDQo+ID4g
IHJvbGUgaXMgdG8gZnVsZmlsbCByZXF1ZXN0cyBmcm9tIGNsaWVudHMsIHdoaWNoIHByZXNlbnQg
dmFyaW91cyANCj4gPiAgY3JlZGVudGlhbHMsIGFuZCBtaW50IGFzc2VydGlvbnMgYXMgcmVxdWVz
dGVkLCBmaWxsIHRoZW0gd2l0aCANCj4gPiAgYXBwcm9wcmlhdGUgaW5mb3JtYXRpb24sIGFuZCBz
aWduIHRoZW0uIiANCj4gPiANCj4gPiANCj4gPiBBcyBJIHVuZGVyc3RhbmQsIGFuIGFzc2VydGlv
biBnZW5lcmF0ZWQgYnkgYSBTVFMsIGlzIGRvbmUgZmxvbGxvd2luZw0KPiA+IHRoZXNzIHN0ZXBz
OiANCj4gPiAxLiBDbGllbnQgcHJlc2VudHMgY3JlZGVudGlhbCBhbmQgcmVxdWVzdHMgYW4gYXNz
ZXJ0aW9uIA0KPiA+IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFuZCBzZW5kcyB0byBDbGll
bnQgDQo+ID4gQ29ycmVjdD8gDQo+ID4gDQo+ID4gVGhhdCBtYXkgcmVzdHJpY3QgdGhlIHVzZSBj
YXNlcyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yayANCj4gY291bGQgc3VwcG9ydCwgDQo+
ID4gaXMgaXQgYSBtdXN0PyANCj4gPiANCj4gPiANCj4gPiANCj4gPiANCj4gPiBvYXV0aC1ib3Vu
Y2VzQGlldGYub3JnINC009ogMjAxMi0xMi0xMSAwMjozMzo1NzoNCj4gPiANCj4gPiA+IA0KPiA+
ID4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBXZWIgQXV0aG9yaXph
dGlvbiBQcm90b2NvbCANCldHDQo+ID4gPiAob2F1dGgpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dp
bmcgZG9jdW1lbnQ6DQo+ID4gPiAtICdBc3NlcnRpb24gRnJhbWV3b3JrIGZvciBPQXV0aCAyLjAn
DQo+ID4gPiAgIDxkcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMtMDgudHh0PiBhcyBQcm9wb3Nl
ZCBTdGFuZGFyZA0KPiA+ID4gDQo+ID4gPiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNp
b24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQgDQpzb2xpY2l0cw0KPiA+ID4gZmluYWwgY29t
bWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRv
IA0KdGhlDQo+ID4gPiBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMgYnkgMjAxMi0xMi0yNC4g
RXhjZXB0aW9uYWxseSwgY29tbWVudHMgDQptYXkgYmUNCj4gPiA+IHNlbnQgdG8gaWVzZ0BpZXRm
Lm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0aGUNCj4gPiA+IGJl
Z2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1dG9tYXRlZCBzb3J0aW5nLg0K
PiA+ID4gDQo+ID4gPiBBYnN0cmFjdA0KPiA+ID4gDQo+ID4gPiANCj4gPiA+ICAgIFRoaXMgc3Bl
Y2lmaWNhdGlvbiBwcm92aWRlcyBhIGZyYW1ld29yayBmb3IgdGhlIHVzZSBvZiBhc3NlcnRpb25z
DQo+ID4gPiAgICB3aXRoIE9BdXRoIDIuMCBpbiB0aGUgZm9ybSBvZiBhIG5ldyBjbGllbnQgYXV0
aGVudGljYXRpb24gDQptZWNoYW5pc20NCj4gPiA+ICAgIGFuZCBhIG5ldyBhdXRob3JpemF0aW9u
IGdyYW50IHR5cGUuICBNZWNoYW5pc21zIGFyZSBzcGVjaWZpZWQgZm9yDQo+ID4gPiAgICB0cmFu
c3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zIHdpdGggYSB0b2tlbiANCmVu
ZHBvaW50LCBhcw0KPiA+ID4gICAgd2VsbCBhcyBnZW5lcmFsIHByb2Nlc3NpbmcgcnVsZXMuDQo+
ID4gPiANCj4gPiA+ICAgIFRoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9uIGlzIHRvIHBy
b3ZpZGUgYSBjb21tb24gZnJhbWV3b3JrIA0KZm9yDQo+ID4gPiAgICBPQXV0aCAyLjAgdG8gaW50
ZXJ3b3JrIHdpdGggb3RoZXIgaWRlbnRpdHkgc3lzdGVtcyB1c2luZyANCmFzc2VydGlvbnMsDQo+
ID4gPiAgICBhbmQgdG8gcHJvdmlkZSBhbHRlcm5hdGl2ZSBjbGllbnQgYXV0aGVudGljYXRpb24g
bWVjaGFuaXNtcy4NCj4gPiA+IA0KPiA+ID4gICAgTm90ZSB0aGF0IHRoaXMgc3BlY2lmaWNhdGlv
biBvbmx5IGRlZmluZXMgYWJzdHJhY3QgbWVzc2FnZSBmbG93cyANCmFuZA0KPiA+ID4gICAgcHJv
Y2Vzc2luZyBydWxlcy4gIEluIG9yZGVyIHRvIGJlIGltcGxlbWVudGFibGUsIGNvbXBhbmlvbg0K
PiA+ID4gICAgc3BlY2lmaWNhdGlvbnMgYXJlIG5lY2Vzc2FyeSB0byBwcm92aWRlIHRoZSBjb3Jy
ZXNwb25kaW5nIA0KY29uY3JldGUNCj4gPiA+ICAgIGluc3RhbnRpYXRpb25zLg0KPiA+ID4gDQo+
ID4gPiANCj4gPiA+IA0KPiA+ID4gDQo+ID4gPiBUaGUgZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlh
DQo+ID4gPiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgt
YXNzZXJ0aW9ucy8NCj4gPiA+IA0KPiA+ID4gSUVTRyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2Vk
IHZpYQ0KPiA+ID4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9h
dXRoLWFzc2VydGlvbnMvYmFsbG90Lw0KPiA+ID4gDQo+ID4gPiANCj4gPiA+IE5vIElQUiBkZWNs
YXJhdGlvbnMgaGF2ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC4NCj4gPiA+
IA0KPiA+ID4gDQo+ID4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KPiA+ID4gT0F1dGggbWFpbGluZyBsaXN0DQo+ID4gPiBPQXV0aEBpZXRmLm9yZw0K
PiA+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aA0KPiA+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gT0F1dGgg
bWFpbGluZyBsaXN0DQo+ID4gT0F1dGhAaWV0Zi5vcmcNCj4gPiBodHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoIA0K
--=_alternative 000D954948257AD4_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkkgYW0gbm90IHN1cmUgaWYgdGhl
IGZvbGxvd2luZyB1c2VjYXNlDQombmJzcDtodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2
ZS93ZWIvb2F1dGgvY3VycmVudC9tc2cxMDIzMy5odG1sPC9mb250Pg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJzYW5zLXNlcmlmIj5jb3VsZCBiZSBzdXBwb3J0ZWQgYnkgYXNzZXJ0aW9uIGZyYW1l
d29ya6OsPC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5XZSBoYXZl
IHNvbWUgZGlzY3Vzc2lvbiBpbiAmbmJzcDs8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9
InNhbnMtc2VyaWYiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9j
dXJyZW50L21zZzEwMjAzLmh0bWw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMt
c2VyaWYiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9jdXJyZW50
L21zZzEwMTk4Lmh0bWwNCjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+SW4gbXkgdXNlIGNhc2Ugb3IgaW4gc29tZSBvdGhlciBjYXNlcywNCmFzc2VydGlv
bnMgZG9uJ3QgbmVlZCBjb25maWRlbnRpYWwgcHJvdGVjdGlvbiwgPC9mb250Pg0KPGJyPjxmb250
IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5iYXNpY2FsbHkgU1RTIGRvbid0IGhhdmUgdG8gYXV0
aGVudGljYXRlDQphIGNsaWVudCBiZWZvcmUgaXNzdWVpbmcgJnF1b3Q7YXNzZXJ0aW9uJnF1b3Q7
LCBpZiBpdCBjb3VsZCBiZSBjYWxsZWQgYXNzZXJ0aW9uDQpoZXJlLjwvZm9udD4NCjxicj4NCjxi
cj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+RXhhbXBsZSxJIHRydXN0IG15IGxheXdl
ciwgSSBtYXkgaXNzdWUNCmFuICZxdW90O2Fzc2VydGlvbiZxdW90OyBzdGF0aW5nIGRlbGVnYXRp
b24gaW4gYWR2YW5jZSwgYW5kIHNlbmQgdG8gdGhlDQpsYXd5ZXIgd2hlbiBpdCBpcyBuZWVkZWQs
PC9mb250Pg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5pdCBjb3VsZCBiZSBJ
IGdpdmUgdGhlIGFzc2VydGlvbiB0bw0KYSBmYWxzZSBsYXd5ZXIsIGJ1dCBpdCBkb2VzIG5vdCBt
YXR0ZXIsIGJlY2F1c2UgdGhlIGxhd3llciBoYXMgdG8gcHJvdmUNCmhlIGtub3dzIHNvbWUgY3Jl
ZGVudGlhbCBjb3JyZXNwb25kaW5nIHRvIGhpcyBJRCw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9InNhbnMtc2VyaWYiPndobyBpcyBkZWxlZ2F0ZWQgc29tZSByaWdodHMuPC9mb250Pg0K
PGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlmIj5JZiBhc3NlcnRpb24gZnJh
bWV3b3JrIHdhbnQgdG8gc3VwcG9ydA0KdGhpcyB1c2UgY2FzZSwgdGhlbiBnZW5lcmF0aW9uIG9m
IGFzc2VydGlvbiBzaG91bGQgYmUgcmVsYXhlZCw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZh
Y2U9InNhbnMtc2VyaWYiPm90aGVyd2lzZSBuZXcgd29yayBpcyByZXF1aXJlZCB0byBzdXBwb3J0
DQp0aGUgdXNlIGNhc2UuPC9mb250Pg0KPGJyPg0KPGJyPg0KPGJyPg0KPGJyPjx0dD48Zm9udCBz
aXplPTI+Q2h1Y2sgTW9ydGltb3JlICZsdDtjbW9ydGltb3JlQHNhbGVzZm9yY2UuY29tJmd0Ow0K
0LTT2iAyMDEyLTEyLTE0IDEwOjA4OjM0Ojxicj4NCjxicj4NCiZndDsgT24gRGVjIDEzLCAyMDEy
LCBhdCA0OjMwIFBNLCAmcXVvdDt6aG91LnN1amluZ0B6dGUuY29tLmNuJnF1b3Q7ICZsdDt6aG91
LnN1amluZ0B6dGUuY29tLmNuPGJyPg0KJmd0OyAmZ3Q7IHdyb3RlOjxicj4NCjwvZm9udD48L3R0
Pg0KPGJyPjx0dD48Zm9udCBzaXplPTI+Jmd0OyA8YnI+DQomZ3Q7IEZyb20gdGhlIGxhbmd1YWdl
LCBJIGdvdCBhbiBpbXByZXNzaW9uIHRoYXQgYXNzZXJ0aW9uIGlzIG9ubHkgPGJyPg0KJmd0OyBn
ZW5lcmF0ZWQgYnkgdG9rZW4gc2VydmljZSBhZnRlciBjbGllbnRzIHByZXNlbnRpbmcgc29tZSBj
cmVkZW50aWFscywNCjxicj4NCiZndDsgdGhlcmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRoYXQg
JnF1b3Q7YXNzZXJ0aW9uJnF1b3Q7IGRvbid0IG5lZWQNCmNsaWVudCdzIGNyZWRlbnRpYWwuIDxi
cj4NCiZndDsgZS5nLiwgUmVzb3VyY2Ugb3duZXIgYXMgYSB0b2tlbiBzZXJ2aWNlICZuYnNwO2Nv
dWxkIGdlbmVyYXRlICZxdW90O2Fzc2VydGlvbiZxdW90Ow0KPGJyPg0KJmd0OyB0byBhIGNsaWVu
dCBoZSB0cnVzdHMsIGJ1IHNpZ25pbmcgYSBzdGF0ZW1lbnQgdGhhdCAmcXVvdDtUaGlzIGRlbGVn
YXRpb24NCjxicj4NCiZndDsgaXMgZ2l2ZW4gdG8gYSBjbGllbnQgY2FsbGVkIGNsaW5ldC1pZCA8
YnI+DQomZ3Q7IGZvciBkb2luZyBzb21ldGhpbmcgZm9yIG1lJnF1b3Q7LiA8L2ZvbnQ+PC90dD4N
Cjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBTbyBob3cgZG9lcyB0aGUgU1RT
IHRydXN0IHRoZSBjbGllbnQ/ICZuYnNwOyBQcmVzdW1hYmx5IGlmIGl0IGlzIHRydXN0ZWQNCjxi
cj4NCiZndDsgaXQgaGFzIHNvbWUgbGV2ZWwgb2YgYXV0aGVudGljYXRpb24sIHllcz88L2ZvbnQ+
PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyAtY21vcnQ8L2ZvbnQ+
PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxi
cj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IENodWNrIE1vcnRpbW9yZSAmbHQ7Y21vcnRp
bW9yZUBzYWxlc2ZvcmNlLmNvbSZndDsg0LTT2iAyMDEyLTEyLTE0DQowMDozOTowMzo8YnI+DQom
Z3Q7IDxicj4NCiZndDsgJmd0OyBUaGUgbGFuZ3VhZ2UgaXMgc2ltcGx5IG1lYW50IHRvIGhlbHAg
aWxsdXN0cmF0ZSBob3cgdGhlIGZyYW1ld29yaw0KPGJyPg0KJmd0OyAmZ3Q7IG1pZ2h0IGJlIHVz
ZWQuICZuYnNwOyBIb3cgZG8geW91IHRoaW5rIGl0IHdpbGwgcmVzdHJpY3QgdXNhZ2U/DQombmJz
cDsgSG93IDxicj4NCiZndDsgJmd0OyBjb3VsZCBpdCBiZSBpbXByb3ZlZD8gPGJyPg0KJmd0OyAm
Z3Q7IDxicj4NCiZndDsgJmd0OyAtY21vcnQgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0
OyBPbiBEZWMgMTIsIDIwMTIsIGF0IDExOjA0IFBNLCAmbHQ7emhvdS5zdWppbmdAenRlLmNvbS5j
biZndDsNCndyb3RlOiA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyBJbiAmcXVvdDtzZWN0aW9uIDMgPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwO1RoZSB0b2tlbiBz
ZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24gaXNzdWVyOyBpdHMgPGJyPg0KJmd0OyAmZ3Q7ICZuYnNw
O3JvbGUgaXMgdG8gZnVsZmlsbCByZXF1ZXN0cyBmcm9tIGNsaWVudHMsIHdoaWNoIHByZXNlbnQN
CnZhcmlvdXMgPGJyPg0KJmd0OyAmZ3Q7ICZuYnNwO2NyZWRlbnRpYWxzLCBhbmQgbWludCBhc3Nl
cnRpb25zIGFzIHJlcXVlc3RlZCwgZmlsbCB0aGVtDQp3aXRoIDxicj4NCiZndDsgJmd0OyAmbmJz
cDthcHByb3ByaWF0ZSBpbmZvcm1hdGlvbiwgYW5kIHNpZ24gdGhlbS4mcXVvdDsgPGJyPg0KJmd0
OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgQXMgSSB1bmRlcnN0YW5kLCBh
biBhc3NlcnRpb24gZ2VuZXJhdGVkIGJ5IGEgU1RTLCBpcyBkb25lIGZsb2xsb3dpbmc8YnI+DQom
Z3Q7ICZndDsgdGhlc3Mgc3RlcHM6IDxicj4NCiZndDsgJmd0OyAxLiBDbGllbnQgcHJlc2VudHMg
Y3JlZGVudGlhbCBhbmQgcmVxdWVzdHMgYW4gYXNzZXJ0aW9uIDxicj4NCiZndDsgJmd0OyAyLiBT
VFMgZ2VuZXJhdGVzIGFzc2VydGlvbiBhbmQgc2VuZHMgdG8gQ2xpZW50IDxicj4NCiZndDsgJmd0
OyBDb3JyZWN0PyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IFRoYXQgbWF5IHJlc3Ry
aWN0IHRoZSB1c2UgY2FzZXMgdGhhdCB0aGlzIGFzc2VydGlvbiBmcmFtZXdvcmsNCjxicj4NCiZn
dDsgY291bGQgc3VwcG9ydCwgPGJyPg0KJmd0OyAmZ3Q7IGlzIGl0IGEgbXVzdD8gPGJyPg0KJmd0
OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxi
cj4NCiZndDsgJmd0OyBvYXV0aC1ib3VuY2VzQGlldGYub3JnINC009ogMjAxMi0xMi0xMSAwMjoz
Mzo1Nzo8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7
ICZndDsgVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBXZWIgQXV0aG9y
aXphdGlvbg0KUHJvdG9jb2wgV0c8YnI+DQomZ3Q7ICZndDsgJmd0OyAob2F1dGgpIHRvIGNvbnNp
ZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6PGJyPg0KJmd0OyAmZ3Q7ICZndDsgLSAnQXNzZXJ0
aW9uIEZyYW1ld29yayBmb3IgT0F1dGggMi4wJzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAm
bHQ7ZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLTA4LnR4dCZndDsgYXMgUHJvcG9zZWQNClN0
YW5kYXJkPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhlIElFU0cg
cGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywNCmFuZCBzb2xp
Y2l0czxicj4NCiZndDsgJmd0OyAmZ3Q7IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQ
bGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21tZW50cw0KdG8gdGhlPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgaWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5IDIwMTItMTItMjQuIEV4Y2VwdGlvbmFs
bHksDQpjb21tZW50cyBtYXkgYmU8YnI+DQomZ3Q7ICZndDsgJmd0OyBzZW50IHRvIGllc2dAaWV0
Zi5vcmcgaW5zdGVhZC4gSW4gZWl0aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4NCnRoZTxicj4NCiZn
dDsgJmd0OyAmZ3Q7IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1dG9t
YXRlZCBzb3J0aW5nLjxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IEFi
c3RyYWN0PGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO1RoaXMgc3BlY2lmaWNhdGlvbiBwcm92aWRlcyBhIGZy
YW1ld29yayBmb3INCnRoZSB1c2Ugb2YgYXNzZXJ0aW9uczxicj4NCiZndDsgJmd0OyAmZ3Q7ICZu
YnNwOyAmbmJzcDt3aXRoIE9BdXRoIDIuMCBpbiB0aGUgZm9ybSBvZiBhIG5ldyBjbGllbnQNCmF1
dGhlbnRpY2F0aW9uIG1lY2hhbmlzbTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDth
bmQgYSBuZXcgYXV0aG9yaXphdGlvbiBncmFudCB0eXBlLiAmbmJzcDtNZWNoYW5pc21zDQphcmUg
c3BlY2lmaWVkIGZvcjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDt0cmFuc3BvcnRp
bmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zDQp3aXRoIGEgdG9rZW4gZW5kcG9pbnQs
IGFzPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3dlbGwgYXMgZ2VuZXJhbCBwcm9j
ZXNzaW5nIHJ1bGVzLjxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZu
YnNwOyAmbmJzcDtUaGUgaW50ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiBpcyB0byBwcm92aWRl
DQphIGNvbW1vbiBmcmFtZXdvcmsgZm9yPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNw
O09BdXRoIDIuMCB0byBpbnRlcndvcmsgd2l0aCBvdGhlciBpZGVudGl0eQ0Kc3lzdGVtcyB1c2lu
ZyBhc3NlcnRpb25zLDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDthbmQgdG8gcHJv
dmlkZSBhbHRlcm5hdGl2ZSBjbGllbnQgYXV0aGVudGljYXRpb24NCm1lY2hhbmlzbXMuPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO05vdGUgdGhh
dCB0aGlzIHNwZWNpZmljYXRpb24gb25seSBkZWZpbmVzIGFic3RyYWN0DQptZXNzYWdlIGZsb3dz
IGFuZDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtwcm9jZXNzaW5nIHJ1bGVzLiAm
bmJzcDtJbiBvcmRlciB0byBiZSBpbXBsZW1lbnRhYmxlLA0KY29tcGFuaW9uPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgJm5ic3A7ICZuYnNwO3NwZWNpZmljYXRpb25zIGFyZSBuZWNlc3NhcnkgdG8gcHJv
dmlkZSB0aGUNCmNvcnJlc3BvbmRpbmcgY29uY3JldGU8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJz
cDsgJm5ic3A7aW5zdGFudGlhdGlvbnMuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYTxicj4NCiZndDsgJmd0
OyAmZ3Q7IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1h
c3NlcnRpb25zLzxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IElFU0cg
ZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWE8YnI+DQomZ3Q7ICZndDsgJmd0OyBodHRwOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy9iYWxs
b3QvPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5
IG9uIHRoaXMNCkktRC48YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8
YnI+DQomZ3Q7ICZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7IE9BdXRoIG1haWxpbmcgbGlzdDxicj4NCiZn
dDsgJmd0OyAmZ3Q7IE9BdXRoQGlldGYub3JnPGJyPg0KJmd0OyAmZ3Q7ICZndDsgaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aDxicj4NCiZndDsgJmd0OyBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgJmd0OyBP
QXV0aCBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsgT0F1dGhAaWV0Zi5vcmc8YnI+DQomZ3Q7
ICZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aCA8L2ZvbnQ+
PC90dD4NCg==
--=_alternative 000D954948257AD4_=--

From markus.lanthaler@gmx.net  Fri Dec 14 02:51:30 2012
Return-Path: <markus.lanthaler@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 EF35721F86EC for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 02:51:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.849
X-Spam-Level: 
X-Spam-Status: No, score=-0.849 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7LYKqQYLoaSn for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 02:51:30 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 7160721F86A5 for <ietf@ietf.org>; Fri, 14 Dec 2012 02:51:16 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0Lo3XS-1TCd5P2H5k-00fwS5 for <ietf@ietf.org>; Fri, 14 Dec 2012 11:51:15 +0100
Received: (qmail invoked by alias); 14 Dec 2012 10:51:15 -0000
Received: from unknown (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp010) with SMTP; 14 Dec 2012 11:51:15 +0100
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1+NRcQuHiONodTOjbH3DuggkEEE/NUV20NB7ZE8Ga lv0NwjBhcZIbgs
From: "Markus Lanthaler" <markus.lanthaler@gmx.net>
To: <ietf@ietf.org>, <apps-discuss@ietf.org>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com>
In-Reply-To: <20121211150057.28223.93310.idtracker@ietfa.amsl.com>
Subject: RE: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt>	(JSON Pointer) to	Proposed Standard
Date: Fri, 14 Dec 2012 11:51:10 +0100
Message-ID: <012301cdd9e8$ee97ac90$cbc705b0$@lanthaler@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac3XsGOrMo1y6p+OQxaQgS0VOp8txQCOE5dw
Content-Language: de
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 10:51:31 -0000

I've asked that before but didn't get an answer. So let me ask again (even
though I'm quite sure it has already been asked by somebody else).

How does JSON Pointer distinguish between objects and arrays? E.g. consider
the following JSON document:

{
  "foo": "bar",
  "1": "baz"
}

As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
though that's probably not what the author intended. Is there a way to avoid
that?


Thanks,
Markus



--
Markus Lanthaler
@markuslanthaler




> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Tuesday, December 11, 2012 4:01 PM
> To: IETF-Announce
> Cc: apps-discuss@ietf.org
> Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> 07.txt> (JSON Pointer) to Proposed Standard
> 
> 
> The IESG has received a request from the Applications Area Working
> Group
> WG (appsawg) to consider the following document:
> - 'JSON Pointer'
>   <draft-ietf-appsawg-json-pointer-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 2012-12-25. Exceptionally, comments may
> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    JSON Pointer defines a string syntax for identifying a specific
> value
>    within a JSON document.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss


From sakimura@gmail.com  Fri Dec 14 07:03:08 2012
Return-Path: <sakimura@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 54F2721F85A6; Fri, 14 Dec 2012 07:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.387
X-Spam-Level: 
X-Spam-Status: No, score=-1.387 tagged_above=-999 required=5 tests=[AWL=-1.261, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, J_CHICKENPOX_71=0.6, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJwSOU6+ywNa; Fri, 14 Dec 2012 07:03:07 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB4821F85B2; Fri, 14 Dec 2012 07:03:06 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so1367336eaa.31 for <multiple recipients>; Fri, 14 Dec 2012 07:03:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:mime-version:in-reply-to:date:message-id:subject:to :cc:content-type; bh=9f6srO+WaskT2GHpL3jWm/WP6g6wjWYzjvVLYZQ92Lc=; b=GZS6gHSPS06F1fMMB9bNaGipXe6rYP8DoSzJC/dmivbfwQzmoB1uxD9T1zBvferPcx 2iAvGiX9kSSJOv8R7QDIA2JmnSdQYvzslhVg5H4PcSYqFztzJ+vpsSy9ypO9dpJicYKN snWaswf8Eg6evG32YsWrqM1fzIhK4fGJKWcoxjqUoRAcp5kSyJCcov9WWufoG517afax NH+aDhcO2DFVgyq5ehi/Lv1gX0ip5YHHb+wHR08aEJxEaEdLTSiyOe3ACzopctjbX4ei urSpI9RGtgJLQf4ufrAFekNQ7FXICSAOL2TdufkRnyPvGOW7k31PaE+XrJJ5joZRDI7Y tjzg==
Received: by 10.14.214.132 with SMTP id c4mr15764163eep.18.1355497385339; Fri, 14 Dec 2012 07:03:05 -0800 (PST)
References: <OF6AFFEFB0.3752F820-ON48257AD4.000F9DD7-48257AD4.00103FB9@zte.com.cn>
From: Nat Sakimura <sakimura@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <OF6AFFEFB0.3752F820-ON48257AD4.000F9DD7-48257AD4.00103FB9@zte.com.cn>
Date: Sat, 15 Dec 2012 00:02:58 +0900
Message-ID: <-5196739590250615087@unknownmsgid>
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
To: "zhou.sujing@zte.com.cn" <zhou.sujing@zte.com.cn>
Content-Type: multipart/alternative; boundary=047d7b621df825ad2504d0d15442
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: "oauth@ietf.org" <oauth@ietf.org>, "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, Chuck Mortimore <cmortimore@salesforce.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, 14 Dec 2012 15:03:08 -0000

--047d7b621df825ad2504d0d15442
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

FYI, I have been writing HoK for JWT/JWS Token by introducing a new claim
'cid'.

=3Dnat via iPhone

Dec 14, 2012 11:56=A1=A2"zhou.sujing@zte.com.cn" <zhou.sujing@zte.com.cn> =
=A4=CE=A5=E1=A5=C3=A5=BB=A9`=A5=B8:


Yep, could do it soon later.

Currently, I suggest a modification for

 "The token service is the assertion issuer; its  role is to fulfill
requests from clients, which present various
 credentials, and mint assertions as requested, fill them with  appropriate
information, and sign them."  (in  section 3 )

into

 "The token service is the assertion issuer, *it could be implemented in
any entity besides client, e.g., Resource Owner, Authorization Server;* its
 role is to fulfill requests from clients, which present various
 credentials, and mint assertions as requested, fill them with  appropriate
information, and sign them."



Chuck Mortimore <cmortimore@salesforce.com> =D0=B4=D3=DA 2012-12-14 10:44:0=
5:

> Correct.   That said no one has yet profiled it for holder of key
>
> - cmort
>
> On Dec 13, 2012, at 6:39 PM, "zhou.sujing@zte.com.cn" <
zhou.sujing@zte.com.cn
> > wrote:

>
> Oh, But the description of assertion generation in the document
> should not be limited by bear assertion, right?
>
>
> Chuck Mortimore <cmortimore@salesforce.com> =D0=B4=D3=DA 2012-12-14 10:34=
:13:
>
> > You want a holder of key pattern.  The draft touches on it
> >
> >
> >    The protocol parameters and processing rules defined in this documen=
t
> >    are intended to support a client presenting a bearer assertion to an
> >    authorization server.  The use of holder-of-key assertions are not
> >    precluded by this document, but additional protocol details would
> >    need to be specified.
>
> >
> > So - if you want this, you should put forth a holder of key
> > profiling of this draft and see if there are any issues.   The only
> > profiles we have thus far are saml and jwt bearer assertions.
> >
> >
> > - cmort
> >
> > On Dec 13, 2012, at 6:27 PM, "zhou.sujing@zte.com.cn" <zhou.
> sujing@zte.com.cn
> > > wrote:
>
> >
> > I am not sure if the following usecase  http://www.ietf.org/mail-
> > archive/web/oauth/current/msg10233.html
> > could be supported by assertion framework=A3=AC
> > We have some discussion in
> > http://www.ietf.org/mail-archive/web/oauth/current/msg10203.html
> > http://www.ietf.org/mail-archive/web/oauth/current/msg10198.html
> >
> > In my use case or in some other cases, assertions don't need
> > confidential protection,
> > basically STS don't have to authenticate a client before issueing
> > "assertion", if it could be called assertion here.
> >
> > Example,I trust my laywer, I may issue an "assertion" stating
> > delegation in advance, and send to the lawyer when it is needed,
> > it could be I give the assertion to a false lawyer, but it does not
> > matter, because the lawyer has to prove he knows some credential
> > corresponding to his ID,
> > who is delegated some rights.
> >
> > If assertion framework want to support this use case, then
> > generation of assertion should be relaxed,
> > otherwise new work is required to support the use case.
> >
> >
> >
> > Chuck Mortimore <cmortimore@salesforce.com> =D0=B4=D3=DA 2012-12-14 10:=
08:34:
> >
> > > On Dec 13, 2012, at 4:30 PM, "zhou.sujing@zte.com.cn" <zhou.
> > sujing@zte.com.cn
> > > > wrote:
> >
> > >
> > > From the language, I got an impression that assertion is only
> > > generated by token service after clients presenting some credentials,
> > > there are may be some cases that "assertion" don't need client's
> > credential.
> > > e.g., Resource owner as a token service  could generate "assertion"
> > > to a client he trusts, bu signing a statement that "This delegation
> > > is given to a client called clinet-id
> > > for doing something for me".
> > >
> > > So how does the STS trust the client?   Presumably if it is trusted
> > > it has some level of authentication, yes?
> > >
> > > -cmort
> > >
> > >
> > >
> > >
> > >
> > > Chuck Mortimore <cmortimore@salesforce.com> =D0=B4=D3=DA 2012-12-14 0=
0:39:03:
> > >
> > > > The language is simply meant to help illustrate how the framework
> > > > might be used.   How do you think it will restrict usage?   How
> > > > could it be improved?
> > > >
> > > > -cmort
> > > >
> > > > On Dec 12, 2012, at 11:04 PM, <zhou.sujing@zte.com.cn> wrote:
> > > >
> > > >
> > > > In "section 3
> > > >  The token service is the assertion issuer; its
> > > >  role is to fulfill requests from clients, which present various
> > > >  credentials, and mint assertions as requested, fill them with
> > > >  appropriate information, and sign them."
> > > >
> > > >
> > > > As I understand, an assertion generated by a STS, is done flollowin=
g
> > > > thess steps:
> > > > 1. Client presents credential and requests an assertion
> > > > 2. STS generates assertion and sends to Client
> > > > Correct?
> > > >
> > > > That may restrict the use cases that this assertion framework
> > > could support,
> > > > is it a must?
> > > >
> > > >
> > > >
> > > >
> > > > oauth-bounces@ietf.org =D0=B4=D3=DA 2012-12-11 02:33:57:
> > > >
> > > > >
> > > > > The IESG has received a request from the Web Authorization
Protocol WG
> > > > > (oauth) to consider the following document:
> > > > > - 'Assertion Framework for OAuth 2.0'
> > > > >   <draft-ietf-oauth-assertions-08.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 2012-12-24. 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 specification provides a framework for the use of
assertions
> > > > >    with OAuth 2.0 in the form of a new client
authenticationmechanism
> > > > >    and a new authorization grant type.  Mechanisms are specified
for
> > > > >    transporting assertions during interactions with a token
> endpoint, as
> > > > >    well as general processing rules.
> > > > >
> > > > >    The intent of this specification is to provide a common
> framework for
> > > > >    OAuth 2.0 to interwork with other identity systems using
> assertions,
> > > > >    and to provide alternative client authentication mechanisms.
> > > > >
> > > > >    Note that this specification only defines abstract
> message flows and
> > > > >    processing rules.  In order to be implementable, companion
> > > > >    specifications are necessary to provide the corresponding
concrete
> > > > >    instantiations.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > The file can be obtained via
> > > > > http://datatracker.ietf.org/doc/draft-ietf-oauth-assertions/
> > > > >
> > > > > IESG discussion can be tracked via
> > > > >
http://datatracker.ietf.org/doc/draft-ietf-oauth-assertions/ballot/
> > > > >
> > > > >
> > > > > No IPR declarations have been submitted directly on this I-D.
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > OAuth mailing list
> > > > > OAuth@ietf.org
> > > > > https://www.ietf.org/mailman/listinfo/oauth
> > > > _______________________________________________
> > > > OAuth mailing list
> > > > OAuth@ietf.org
> > > > https://www.ietf.org/mailman/listinfo/oauth

_______________________________________________
OAuth mailing list
OAuth@ietf.org
https://www.ietf.org/mailman/listinfo/oauth

--047d7b621df825ad2504d0d15442
Content-Type: text/html; charset=GB2312
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=
=3Dutf-8"></head><body dir=3D"auto"><div>FYI, I have been writing HoK for J=
WT/JWS Token by introducing a new claim &#39;cid&#39;.&nbsp;<br><br>=3Dnat =
via iPhone</div>
<div><br>Dec 14, 2012 11:56=A1=A2&quot;<a href=3D"mailto:zhou.sujing@zte.co=
m.cn">zhou.sujing@zte.com.cn</a>&quot; &lt;<a href=3D"mailto:zhou.sujing@zt=
e.com.cn">zhou.sujing@zte.com.cn</a>&gt; =A4=CE=A5=E1=A5=C3=A5=BB=A9`=A5=B8=
:<br><br></div><div><span></span></div>
<blockquote type=3D"cite"><div>
<br><font face=3D"sans-serif">Yep, could do it soon later. </font>
<br>
<br><font face=3D"sans-serif">Currently, I suggest a modification
for </font>
<br>
<br><font face=3D"sans-serif">&nbsp;&quot;The token service is the
assertion issuer; its &nbsp;role is to fulfill requests from clients, which
present various </font>
<br><font face=3D"sans-serif">&nbsp;credentials, and mint assertions
as requested, fill them with &nbsp;appropriate information, and sign them.&=
quot;
&nbsp;(in &nbsp;section 3 )</font>
<br>
<br><font face=3D"sans-serif">into </font>
<br>
<br><font face=3D"sans-serif">&nbsp;&quot;The token service is the
assertion issuer, <b>it could be implemented in any entity besides client,
e.g., Resource Owner, Authorization Server;</b> its &nbsp;role is to fulfil=
l
requests from clients, <strike>which present various &nbsp;credentials</str=
ike>,
and mint assertions as requested, fill them with &nbsp;appropriate informat=
ion,
and sign them.&quot; </font>
<br>
<br>
<br>
<br><tt><font>Chuck Mortimore &lt;<a href=3D"mailto:cmortimore@salesforce.c=
om">cmortimore@salesforce.com</a>&gt;
=D0=B4=D3=DA 2012-12-14 10:44:05:<br>
<br>
&gt; Correct. &nbsp; That said no one has yet profiled it for holder of
key<br>
&gt; <br>
&gt; - cmort</font></tt>
<br><tt><font>&gt; <br>
&gt; On Dec 13, 2012, at 6:39 PM, &quot;<a href=3D"mailto:zhou.sujing@zte.c=
om.cn">zhou.sujing@zte.com.cn</a>&quot; &lt;<a href=3D"mailto:zhou.sujing@z=
te.com.cn">zhou.sujing@zte.com.cn</a><br>
&gt; &gt; wrote:<br>
</font></tt>
<br><tt><font>&gt; <br>
&gt; Oh, But the description of assertion generation in the document <br>
&gt; should not be limited by bear assertion, right? <br>
&gt; <br>
&gt; <br>
&gt; Chuck Mortimore &lt;<a href=3D"mailto:cmortimore@salesforce.com">cmort=
imore@salesforce.com</a>&gt; =D0=B4=D3=DA 2012-12-14
10:34:13:<br>
&gt; <br>
&gt; &gt; You want a holder of key pattern. &nbsp;The draft touches on
it <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; &nbsp; &nbsp;The protocol parameters and processing rules defined
in this document<br>
&gt; &gt; &nbsp; &nbsp;are intended to support a client presenting a bearer
assertion to an<br>
&gt; &gt; &nbsp; &nbsp;authorization server. &nbsp;The use of holder-of-key
assertions are not<br>
&gt; &gt; &nbsp; &nbsp;precluded by this document, but additional protocol
details would<br>
&gt; &gt; &nbsp; &nbsp;need to be specified.<br>
&gt; <br>
&gt; &gt; <br>
&gt; &gt; So - if you want this, you should put forth a holder of key <br>
&gt; &gt; profiling of this draft and see if there are any issues. &nbsp;
The only <br>
&gt; &gt; profiles we have thus far are saml and jwt bearer assertions.
&nbsp; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; - cmort <br>
&gt; &gt; <br>
&gt; &gt; On Dec 13, 2012, at 6:27 PM, &quot;<a href=3D"mailto:zhou.sujing@=
zte.com.cn">zhou.sujing@zte.com.cn</a>&quot;
&lt;zhou.<br>
&gt; <a href=3D"mailto:sujing@zte.com.cn">sujing@zte.com.cn</a><br>
&gt; &gt; &gt; wrote:<br>
&gt; <br>
&gt; &gt; <br>
&gt; &gt; I am not sure if the following usecase &nbsp;<a href=3D"http://ww=
w.ietf.org/mail-">http://www.ietf.org/mail-</a><br>
&gt; &gt; archive/web/oauth/current/msg10233.html <br>
&gt; &gt; could be supported by assertion framework=A3=AC <br>
&gt; &gt; We have some discussion in &nbsp; <br>
&gt; &gt; <a href=3D"http://www.ietf.org/mail-archive/web/oauth/current/msg=
10203.html">http://www.ietf.org/mail-archive/web/oauth/current/msg10203.htm=
l</a>
<br>
&gt; &gt; <a href=3D"http://www.ietf.org/mail-archive/web/oauth/current/msg=
10198.html">http://www.ietf.org/mail-archive/web/oauth/current/msg10198.htm=
l</a>
<br>
&gt; &gt; <br>
&gt; &gt; In my use case or in some other cases, assertions don&#39;t need
<br>
&gt; &gt; confidential protection, <br>
&gt; &gt; basically STS don&#39;t have to authenticate a client before issu=
eing
<br>
&gt; &gt; &quot;assertion&quot;, if it could be called assertion here.
<br>
&gt; &gt; <br>
&gt; &gt; Example,I trust my laywer, I may issue an &quot;assertion&quot;
stating <br>
&gt; &gt; delegation in advance, and send to the lawyer when it is needed,
<br>
&gt; &gt; it could be I give the assertion to a false lawyer, but it does
not <br>
&gt; &gt; matter, because the lawyer has to prove he knows some credential
<br>
&gt; &gt; corresponding to his ID, <br>
&gt; &gt; who is delegated some rights. <br>
&gt; &gt; <br>
&gt; &gt; If assertion framework want to support this use case, then <br>
&gt; &gt; generation of assertion should be relaxed, <br>
&gt; &gt; otherwise new work is required to support the use case. <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; <br>
&gt; &gt; Chuck Mortimore &lt;<a href=3D"mailto:cmortimore@salesforce.com">=
cmortimore@salesforce.com</a>&gt; =D0=B4=D3=DA 2012-12-14
10:08:34:<br>
&gt; &gt; <br>
&gt; &gt; &gt; On Dec 13, 2012, at 4:30 PM, &quot;<a href=3D"mailto:zhou.su=
jing@zte.com.cn">zhou.sujing@zte.com.cn</a>&quot;
&lt;zhou.<br>
&gt; &gt; <a href=3D"mailto:sujing@zte.com.cn">sujing@zte.com.cn</a><br>
&gt; &gt; &gt; &gt; wrote:<br>
&gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; From the language, I got an impression that assertion is
only <br>
&gt; &gt; &gt; generated by token service after clients presenting some
credentials, <br>
&gt; &gt; &gt; there are may be some cases that &quot;assertion&quot; don&#=
39;t
need client&#39;s <br>
&gt; &gt; credential. <br>
&gt; &gt; &gt; e.g., Resource owner as a token service &nbsp;could generate
&quot;assertion&quot; <br>
&gt; &gt; &gt; to a client he trusts, bu signing a statement that &quot;Thi=
s
delegation <br>
&gt; &gt; &gt; is given to a client called clinet-id <br>
&gt; &gt; &gt; for doing something for me&quot;. <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; So how does the STS trust the client? &nbsp; Presumably
if it is trusted <br>
&gt; &gt; &gt; it has some level of authentication, yes? <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; -cmort <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; Chuck Mortimore &lt;<a href=3D"mailto:cmortimore@salesforce.=
com">cmortimore@salesforce.com</a>&gt; =D0=B4=D3=DA
2012-12-14 00:39:03:<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; The language is simply meant to help illustrate how
the framework <br>
&gt; &gt; &gt; &gt; might be used. &nbsp; How do you think it will restrict
usage? &nbsp; How <br>
&gt; &gt; &gt; &gt; could it be improved? <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; -cmort <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; On Dec 12, 2012, at 11:04 PM, &lt;<a href=3D"mailto:zho=
u.sujing@zte.com.cn">zhou.sujing@zte.com.cn</a>&gt;
wrote: <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; In &quot;section 3 <br>
&gt; &gt; &gt; &gt; &nbsp;The token service is the assertion issuer; its
<br>
&gt; &gt; &gt; &gt; &nbsp;role is to fulfill requests from clients, which
present various <br>
&gt; &gt; &gt; &gt; &nbsp;credentials, and mint assertions as requested,
fill them with <br>
&gt; &gt; &gt; &gt; &nbsp;appropriate information, and sign them.&quot;
<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; As I understand, an assertion generated by a STS, is
done flollowing<br>
&gt; &gt; &gt; &gt; thess steps: <br>
&gt; &gt; &gt; &gt; 1. Client presents credential and requests an assertion
<br>
&gt; &gt; &gt; &gt; 2. STS generates assertion and sends to Client <br>
&gt; &gt; &gt; &gt; Correct? <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; That may restrict the use cases that this assertion
framework <br>
&gt; &gt; &gt; could support, <br>
&gt; &gt; &gt; &gt; is it a must? <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; <a href=3D"mailto:oauth-bounces@ietf.org">oauth-bounces=
@ietf.org</a> =D0=B4=D3=DA 2012-12-11 02:33:57:<br>
&gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; The IESG has received a request from the Web Autho=
rization
Protocol WG<br>
&gt; &gt; &gt; &gt; &gt; (oauth) to consider the following document:<br>
&gt; &gt; &gt; &gt; &gt; - &#39;Assertion Framework for OAuth 2.0&#39;<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &lt;draft-ietf-oauth-assertions-08.txt&gt;
as Proposed Standard<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; The IESG plans to make a decision in the next
few weeks, and solicits<br>
&gt; &gt; &gt; &gt; &gt; final comments on this action. Please send substan=
tive
comments to the<br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>=
 mailing lists by 2012-12-24. Exceptionally,
<br>
&gt; &gt; comments may be<br>
&gt; &gt; &gt; &gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf=
.org</a> instead. In either case,
please retain the<br>
&gt; &gt; &gt; &gt; &gt; beginning of the Subject line to allow automated
sorting.<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; Abstract<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;This specification provides a framewo=
rk
for the use of assertions<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;with OAuth 2.0 in the form of a new
client authenticationmechanism<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;and a new authorization grant type.
&nbsp;Mechanisms are specified for<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;transporting assertions during intera=
ctions
with a token <br>
&gt; endpoint, as<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;well as general processing rules.<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;The intent of this specification
is to provide a common <br>
&gt; framework for<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;OAuth 2.0 to interwork with other
identity systems using <br>
&gt; assertions,<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;and to provide alternative client
authentication mechanisms.<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;Note that this specification only
defines abstract <br>
&gt; message flows and<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;processing rules. &nbsp;In order
to be implementable, companion<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;specifications are necessary to provi=
de
the corresponding concrete<br>
&gt; &gt; &gt; &gt; &gt; &nbsp; &nbsp;instantiations.<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; The file can be obtained via<br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-i=
etf-oauth-assertions/">http://datatracker.ietf.org/doc/draft-ietf-oauth-ass=
ertions/</a><br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; IESG discussion can be tracked via<br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-i=
etf-oauth-assertions/ballot/">http://datatracker.ietf.org/doc/draft-ietf-oa=
uth-assertions/ballot/</a><br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; No IPR declarations have been submitted directly
on this I-D.<br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; <br>
&gt; &gt; &gt; &gt; &gt; _______________________________________________<br=
>
&gt; &gt; &gt; &gt; &gt; OAuth mailing list<br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"mailto:OAuth@ietf.org">OAuth@ietf.org</=
a><br>
&gt; &gt; &gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/o=
auth">https://www.ietf.org/mailman/listinfo/oauth</a><br>
&gt; &gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; &gt; OAuth mailing list<br>
&gt; &gt; &gt; &gt; <a href=3D"mailto:OAuth@ietf.org">OAuth@ietf.org</a><br=
>
&gt; &gt; &gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/oauth"=
>https://www.ietf.org/mailman/listinfo/oauth</a> </font></tt>
</div></blockquote><blockquote type=3D"cite"><div><span>___________________=
____________________________</span><br><span>OAuth mailing list</span><br><=
span><a href=3D"mailto:OAuth@ietf.org">OAuth@ietf.org</a></span><br><span><=
a href=3D"https://www.ietf.org/mailman/listinfo/oauth">https://www.ietf.org=
/mailman/listinfo/oauth</a></span><br>
</div></blockquote></body></html>

--047d7b621df825ad2504d0d15442--

From markus.lanthaler@gmx.net  Fri Dec 14 09:17:41 2012
Return-Path: <markus.lanthaler@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 6845221F8A08 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.961
X-Spam-Level: 
X-Spam-Status: No, score=-0.961 tagged_above=-999 required=5 tests=[AWL=0.188,  BAYES_00=-2.599, HTML_MESSAGE=0.001, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BuESEYc7y37G for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:17:40 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 40ABD21F8A00 for <ietf@ietf.org>; Fri, 14 Dec 2012 09:17:40 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.29]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MGDg9-1Tx2sG1B0J-00FAk8 for <ietf@ietf.org>; Fri, 14 Dec 2012 18:17:39 +0100
Received: (qmail invoked by alias); 14 Dec 2012 17:17:38 -0000
Received: from unknown (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp029) with SMTP; 14 Dec 2012 18:17:38 +0100
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX18huEAEOS4hnEAFoDwA6TEOXZ6xFoeaWHs/Aeszkt ZVVNyMy3vXuRwr
From: "Markus Lanthaler" <markus.lanthaler@gmx.net>
To: "'James M Snell'" <jasnell@gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com>
In-Reply-To: <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com>
Subject: RE: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
Date: Fri, 14 Dec 2012 18:17:33 +0100
Message-ID: <01f901cdda1e$e9287830$bb796890$@lanthaler@gmx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_01FA_01CDDA27.4AECE030"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac3aGcp/PEXrnxKCQ+em/G5vi3KWIgABPGqA
Content-Language: de
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: 'IETF Discussion' <ietf@ietf.org>, 'IETF Apps Discuss' <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 17:17:41 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_01FA_01CDDA27.4AECE030
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hmm.. I think that=E2=80=99s quite problematic. Especially considering =
how JSON Pointer is used in JSON Patch.

=20

=20

--

Markus Lanthaler

@markuslanthaler

=20

=20

=20

From: James M Snell [mailto:jasnell@gmail.com]=20
Sent: Friday, December 14, 2012 5:41 PM
To: Markus Lanthaler
Cc: IETF Discussion; IETF Apps Discuss
Subject: Re: [apps-discuss] Last Call: =
<draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed =
Standard

=20

JSON Pointer does not distinguish between objects and arrays. That is =
not determined until the pointer is applied to an actual object =
instance... the pointer "/1" is valid against {"1":"a"} or ["a","b"]

=20

On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler =
<markus.lanthaler@gmx.net> wrote:

I've asked that before but didn't get an answer. So let me ask again =
(even
though I'm quite sure it has already been asked by somebody else).

How does JSON Pointer distinguish between objects and arrays? E.g. =
consider
the following JSON document:

{
  "foo": "bar",
  "1": "baz"
}

As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
though that's probably not what the author intended. Is there a way to =
avoid
that?


Thanks,
Markus



--
Markus Lanthaler
@markuslanthaler





> -----Original Message-----
> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: Tuesday, December 11, 2012 4:01 PM
> To: IETF-Announce
> Cc: apps-discuss@ietf.org
> Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> 07.txt> (JSON Pointer) to Proposed Standard
>
>
> The IESG has received a request from the Applications Area Working
> Group
> WG (appsawg) to consider the following document:
> - 'JSON Pointer'
>   <draft-ietf-appsawg-json-pointer-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 2012-12-25. Exceptionally, comments may
> be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    JSON Pointer defines a string syntax for identifying a specific
> value
>    within a JSON document.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

_______________________________________________
apps-discuss mailing list
apps-discuss@ietf.org
https://www.ietf.org/mailman/listinfo/apps-discuss

=20


------=_NextPart_000_01FA_01CDDA27.4AECE030
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:"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:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	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.E-MailFormatvorlage17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 2.0cm 70.85pt;}
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=3DDE link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hmm.. I =
think that=E2=80=99s quite problematic. Especially considering how JSON =
Pointer is used in JSON Patch.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><div><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>--<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>Markus Lanthaler<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:black'=
>@markuslanthaler</span><span =
style=3D'font-size:10.5pt;font-family:Consolas'><o:p></o:p></span></p></d=
iv><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><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 =
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"'> =
James M Snell [mailto:jasnell@gmail.com] <br><b>Sent:</b> Friday, =
December 14, 2012 5:41 PM<br><b>To:</b> Markus Lanthaler<br><b>Cc:</b> =
IETF Discussion; IETF Apps Discuss<br><b>Subject:</b> Re: [apps-discuss] =
Last Call: &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; (JSON Pointer) =
to Proposed Standard<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-family:"Courier New"'>JSON Pointer does not distinguish =
between objects and arrays. That is not determined until the pointer is =
applied to an actual object instance... the pointer &quot;/1&quot; is =
valid against {&quot;1&quot;:&quot;a&quot;} or =
[&quot;a&quot;,&quot;b&quot;]</span><o:p></o:p></p><div><p =
class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p =
class=3DMsoNormal>On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler =
&lt;<a href=3D"mailto:markus.lanthaler@gmx.net" =
target=3D"_blank">markus.lanthaler@gmx.net</a>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoNormal>I've asked that before but =
didn't get an answer. So let me ask again (even<br>though I'm quite sure =
it has already been asked by somebody else).<br><br>How does JSON =
Pointer distinguish between objects and arrays? E.g. consider<br>the =
following JSON document:<br><br>{<br>&nbsp; &quot;foo&quot;: =
&quot;bar&quot;,<br>&nbsp; &quot;1&quot;: &quot;baz&quot;<br>}<br><br>As =
I read the draft, the JSON Pointer &quot;/1&quot; would evaluate to =
&quot;baz&quot; even<br>though that's probably not what the author =
intended. Is there a way to =
avoid<br>that?<br><br><br>Thanks,<br>Markus<br><br><br><br>--<br>Markus =
Lanthaler<br>@markuslanthaler<o:p></o:p></p><div><div><p =
class=3DMsoNormal><br><br><br><br>&gt; -----Original =
Message-----<br>&gt; From: <a =
href=3D"mailto:apps-discuss-bounces@ietf.org">apps-discuss-bounces@ietf.o=
rg</a> [mailto:<a =
href=3D"mailto:apps-discuss-">apps-discuss-</a><br>&gt; <a =
href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>] On Behalf Of The =
IESG<br>&gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>&gt; To: =
IETF-Announce<br>&gt; Cc: <a =
href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>&gt; =
Subject: [apps-discuss] Last Call: =
&lt;draft-ietf-appsawg-json-pointer-<br>&gt; 07.txt&gt; (JSON Pointer) =
to Proposed Standard<br>&gt;<br>&gt;<br>&gt; The IESG has received a =
request from the Applications Area Working<br>&gt; Group<br>&gt; WG =
(appsawg) to consider the following document:<br>&gt; - 'JSON =
Pointer'<br>&gt; &nbsp; &lt;draft-ietf-appsawg-json-pointer-07.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 =
2012-12-25. Exceptionally, comments may<br>&gt; 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; =
&nbsp; &nbsp;JSON Pointer defines a string syntax for identifying a =
specific<br>&gt; value<br>&gt; &nbsp; &nbsp;within a JSON =
document.<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-ietf-appsawg-json-pointer/"=
 =
target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-appsawg-json=
-pointer/</a><br>&gt;<br>&gt; IESG discussion can be tracked via<br>&gt; =
<a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/b=
allot/" =
target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-appsawg-json=
-pointer/ballot/</a><br>&gt;<br>&gt;<br>&gt; No IPR declarations have =
been submitted directly on this I-D.<br>&gt;<br>&gt;<br>&gt; =
_______________________________________________<br>&gt; apps-discuss =
mailing list<br>&gt; <a =
href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>&gt; =
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><=
br><br>_______________________________________________<br>apps-discuss =
mailing list<br><a =
href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br><a =
href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><=
o:p></o:p></p></div></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_01FA_01CDDA27.4AECE030--


From cmortimore@salesforce.com  Thu Dec 13 18:34:21 2012
Return-Path: <cmortimore@salesforce.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D38D821F89C6; Thu, 13 Dec 2012 18:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.327
X-Spam-Level: 
X-Spam-Status: No, score=-6.327 tagged_above=-999 required=5 tests=[AWL=-0.151, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6tBPlC28Aqg; Thu, 13 Dec 2012 18:34:20 -0800 (PST)
Received: from exprod8og114.obsmtp.com (exprod8og114.obsmtp.com [64.18.3.28]) by ietfa.amsl.com (Postfix) with SMTP id 80C6121F8974; Thu, 13 Dec 2012 18:34:20 -0800 (PST)
Received: from exsfm-hub4.internal.salesforce.com ([204.14.239.239]) by exprod8ob114.postini.com ([64.18.7.12]) with SMTP ID DSNKUMqQLBUfMS/fhUq0BBeLMO4SfiMPFjP0@postini.com; Thu, 13 Dec 2012 18:34:20 PST
Received: from EXSFM-MB03.internal.salesforce.com ([10.1.127.58]) by exsfm-hub4.internal.salesforce.com ([10.1.127.8]) with mapi; Thu, 13 Dec 2012 18:34:20 -0800
From: Chuck Mortimore <cmortimore@salesforce.com>
To: "zhou.sujing@zte.com.cn" <zhou.sujing@zte.com.cn>
Date: Thu, 13 Dec 2012 18:34:13 -0800
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
Thread-Topic: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
Thread-Index: Ac3Zo4Q/pWOl49zpRlOxQ1aeV6bIWg==
Message-ID: <D6F62E88-1656-4951-A206-FC6E20EBBAB5@salesforce.com>
References: <OFB336BD6F.D58307B1-ON48257AD4.000C51F0-48257AD4.000D954A@zte.com.cn>
In-Reply-To: <OFB336BD6F.D58307B1-ON48257AD4.000C51F0-48257AD4.000D954A@zte.com.cn>
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_D6F62E8816564951A206FC6E20EBBAB5salesforcecom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 02:34:22 -0000

--_000_D6F62E8816564951A206FC6E20EBBAB5salesforcecom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

WW91IHdhbnQgYSBob2xkZXIgb2Yga2V5IHBhdHRlcm4uICBUaGUgZHJhZnQgdG91Y2hlcyBvbiBp
dA0KDQoNCg0KDQoNCiAgIFRoZSBwcm90b2NvbCBwYXJhbWV0ZXJzIGFuZCBwcm9jZXNzaW5nIHJ1
bGVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudA0KICAgYXJlIGludGVuZGVkIHRvIHN1cHBvcnQg
YSBjbGllbnQgcHJlc2VudGluZyBhIGJlYXJlciBhc3NlcnRpb24gdG8gYW4NCiAgIGF1dGhvcml6
YXRpb24gc2VydmVyLiAgVGhlIHVzZSBvZiBob2xkZXItb2Yta2V5IGFzc2VydGlvbnMgYXJlIG5v
dA0KICAgcHJlY2x1ZGVkIGJ5IHRoaXMgZG9jdW1lbnQsIGJ1dCBhZGRpdGlvbmFsIHByb3RvY29s
IGRldGFpbHMgd291bGQNCiAgIG5lZWQgdG8gYmUgc3BlY2lmaWVkLg0KDQoNClNvIC0gaWYgeW91
IHdhbnQgdGhpcywgeW91IHNob3VsZCBwdXQgZm9ydGggYSBob2xkZXIgb2Yga2V5IHByb2ZpbGlu
ZyBvZiB0aGlzIGRyYWZ0IGFuZCBzZWUgaWYgdGhlcmUgYXJlIGFueSBpc3N1ZXMuICAgVGhlIG9u
bHkgcHJvZmlsZXMgd2UgaGF2ZSB0aHVzIGZhciBhcmUgc2FtbCBhbmQgand0IGJlYXJlciBhc3Nl
cnRpb25zLg0KDQoNCi0gY21vcnQNCg0KT24gRGVjIDEzLCAyMDEyLCBhdCA2OjI3IFBNLCAiemhv
dS5zdWppbmdAenRlLmNvbS5jbjxtYWlsdG86emhvdS5zdWppbmdAenRlLmNvbS5jbj4iIDx6aG91
LnN1amluZ0B6dGUuY29tLmNuPG1haWx0bzp6aG91LnN1amluZ0B6dGUuY29tLmNuPj4gd3JvdGU6
DQoNCg0KSSBhbSBub3Qgc3VyZSBpZiB0aGUgZm9sbG93aW5nIHVzZWNhc2UgIGh0dHA6Ly93d3cu
aWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9jdXJyZW50L21zZzEwMjMzLmh0bWwNCmNv
dWxkIGJlIHN1cHBvcnRlZCBieSBhc3NlcnRpb24gZnJhbWV3b3Jr77yMDQpXZSBoYXZlIHNvbWUg
ZGlzY3Vzc2lvbiBpbg0KaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL29hdXRo
L2N1cnJlbnQvbXNnMTAyMDMuaHRtbA0KaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUv
d2ViL29hdXRoL2N1cnJlbnQvbXNnMTAxOTguaHRtbA0KDQpJbiBteSB1c2UgY2FzZSBvciBpbiBz
b21lIG90aGVyIGNhc2VzLCBhc3NlcnRpb25zIGRvbid0IG5lZWQgY29uZmlkZW50aWFsIHByb3Rl
Y3Rpb24sDQpiYXNpY2FsbHkgU1RTIGRvbid0IGhhdmUgdG8gYXV0aGVudGljYXRlIGEgY2xpZW50
IGJlZm9yZSBpc3N1ZWluZyAiYXNzZXJ0aW9uIiwgaWYgaXQgY291bGQgYmUgY2FsbGVkIGFzc2Vy
dGlvbiBoZXJlLg0KDQpFeGFtcGxlLEkgdHJ1c3QgbXkgbGF5d2VyLCBJIG1heSBpc3N1ZSBhbiAi
YXNzZXJ0aW9uIiBzdGF0aW5nIGRlbGVnYXRpb24gaW4gYWR2YW5jZSwgYW5kIHNlbmQgdG8gdGhl
IGxhd3llciB3aGVuIGl0IGlzIG5lZWRlZCwNCml0IGNvdWxkIGJlIEkgZ2l2ZSB0aGUgYXNzZXJ0
aW9uIHRvIGEgZmFsc2UgbGF3eWVyLCBidXQgaXQgZG9lcyBub3QgbWF0dGVyLCBiZWNhdXNlIHRo
ZSBsYXd5ZXIgaGFzIHRvIHByb3ZlIGhlIGtub3dzIHNvbWUgY3JlZGVudGlhbCBjb3JyZXNwb25k
aW5nIHRvIGhpcyBJRCwNCndobyBpcyBkZWxlZ2F0ZWQgc29tZSByaWdodHMuDQoNCklmIGFzc2Vy
dGlvbiBmcmFtZXdvcmsgd2FudCB0byBzdXBwb3J0IHRoaXMgdXNlIGNhc2UsIHRoZW4gZ2VuZXJh
dGlvbiBvZiBhc3NlcnRpb24gc2hvdWxkIGJlIHJlbGF4ZWQsDQpvdGhlcndpc2UgbmV3IHdvcmsg
aXMgcmVxdWlyZWQgdG8gc3VwcG9ydCB0aGUgdXNlIGNhc2UuDQoNCg0KDQpDaHVjayBNb3J0aW1v
cmUgPGNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb208bWFpbHRvOmNtb3J0aW1vcmVAc2FsZXNmb3Jj
ZS5jb20+PiDlhpnkuo4gMjAxMi0xMi0xNCAxMDowODozNDoNCg0KPiBPbiBEZWMgMTMsIDIwMTIs
IGF0IDQ6MzAgUE0sICJ6aG91LnN1amluZ0B6dGUuY29tLmNuPG1haWx0bzp6aG91LnN1amluZ0B6
dGUuY29tLmNuPiIgPHpob3Uuc3VqaW5nQHp0ZS5jb20uY248bWFpbHRvOnpob3Uuc3VqaW5nQHp0
ZS5jb20uY24+DQo+ID4gd3JvdGU6DQoNCj4NCj4gRnJvbSB0aGUgbGFuZ3VhZ2UsIEkgZ290IGFu
IGltcHJlc3Npb24gdGhhdCBhc3NlcnRpb24gaXMgb25seQ0KPiBnZW5lcmF0ZWQgYnkgdG9rZW4g
c2VydmljZSBhZnRlciBjbGllbnRzIHByZXNlbnRpbmcgc29tZSBjcmVkZW50aWFscywNCj4gdGhl
cmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRoYXQgImFzc2VydGlvbiIgZG9uJ3QgbmVlZCBjbGll
bnQncyBjcmVkZW50aWFsLg0KPiBlLmcuLCBSZXNvdXJjZSBvd25lciBhcyBhIHRva2VuIHNlcnZp
Y2UgIGNvdWxkIGdlbmVyYXRlICJhc3NlcnRpb24iDQo+IHRvIGEgY2xpZW50IGhlIHRydXN0cywg
YnUgc2lnbmluZyBhIHN0YXRlbWVudCB0aGF0ICJUaGlzIGRlbGVnYXRpb24NCj4gaXMgZ2l2ZW4g
dG8gYSBjbGllbnQgY2FsbGVkIGNsaW5ldC1pZA0KPiBmb3IgZG9pbmcgc29tZXRoaW5nIGZvciBt
ZSIuDQo+DQo+IFNvIGhvdyBkb2VzIHRoZSBTVFMgdHJ1c3QgdGhlIGNsaWVudD8gICBQcmVzdW1h
Ymx5IGlmIGl0IGlzIHRydXN0ZWQNCj4gaXQgaGFzIHNvbWUgbGV2ZWwgb2YgYXV0aGVudGljYXRp
b24sIHllcz8NCj4NCj4gLWNtb3J0DQo+DQo+DQo+DQo+DQo+DQo+IENodWNrIE1vcnRpbW9yZSA8
Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbTxtYWlsdG86Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNv
bT4+IOWGmeS6jiAyMDEyLTEyLTE0IDAwOjM5OjAzOg0KPg0KPiA+IFRoZSBsYW5ndWFnZSBpcyBz
aW1wbHkgbWVhbnQgdG8gaGVscCBpbGx1c3RyYXRlIGhvdyB0aGUgZnJhbWV3b3JrDQo+ID4gbWln
aHQgYmUgdXNlZC4gICBIb3cgZG8geW91IHRoaW5rIGl0IHdpbGwgcmVzdHJpY3QgdXNhZ2U/ICAg
SG93DQo+ID4gY291bGQgaXQgYmUgaW1wcm92ZWQ/DQo+ID4NCj4gPiAtY21vcnQNCj4gPg0KPiA+
IE9uIERlYyAxMiwgMjAxMiwgYXQgMTE6MDQgUE0sIDx6aG91LnN1amluZ0B6dGUuY29tLmNuPG1h
aWx0bzp6aG91LnN1amluZ0B6dGUuY29tLmNuPj4gd3JvdGU6DQo+ID4NCj4gPg0KPiA+IEluICJz
ZWN0aW9uIDMNCj4gPiAgVGhlIHRva2VuIHNlcnZpY2UgaXMgdGhlIGFzc2VydGlvbiBpc3N1ZXI7
IGl0cw0KPiA+ICByb2xlIGlzIHRvIGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBjbGllbnRzLCB3aGlj
aCBwcmVzZW50IHZhcmlvdXMNCj4gPiAgY3JlZGVudGlhbHMsIGFuZCBtaW50IGFzc2VydGlvbnMg
YXMgcmVxdWVzdGVkLCBmaWxsIHRoZW0gd2l0aA0KPiA+ICBhcHByb3ByaWF0ZSBpbmZvcm1hdGlv
biwgYW5kIHNpZ24gdGhlbS4iDQo+ID4NCj4gPg0KPiA+IEFzIEkgdW5kZXJzdGFuZCwgYW4gYXNz
ZXJ0aW9uIGdlbmVyYXRlZCBieSBhIFNUUywgaXMgZG9uZSBmbG9sbG93aW5nDQo+ID4gdGhlc3Mg
c3RlcHM6DQo+ID4gMS4gQ2xpZW50IHByZXNlbnRzIGNyZWRlbnRpYWwgYW5kIHJlcXVlc3RzIGFu
IGFzc2VydGlvbg0KPiA+IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFuZCBzZW5kcyB0byBD
bGllbnQNCj4gPiBDb3JyZWN0Pw0KPiA+DQo+ID4gVGhhdCBtYXkgcmVzdHJpY3QgdGhlIHVzZSBj
YXNlcyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yaw0KPiBjb3VsZCBzdXBwb3J0LA0KPiA+
IGlzIGl0IGEgbXVzdD8NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+IG9hdXRoLWJvdW5jZXNAaWV0
Zi5vcmc8bWFpbHRvOm9hdXRoLWJvdW5jZXNAaWV0Zi5vcmc+IOWGmeS6jiAyMDEyLTEyLTExIDAy
OjMzOjU3Og0KPiA+DQo+ID4gPg0KPiA+ID4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVz
dCBmcm9tIHRoZSBXZWIgQXV0aG9yaXphdGlvbiBQcm90b2NvbCBXRw0KPiA+ID4gKG9hdXRoKSB0
byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Og0KPiA+ID4gLSAnQXNzZXJ0aW9uIEZy
YW1ld29yayBmb3IgT0F1dGggMi4wJw0KPiA+ID4gICA8ZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRp
b25zLTA4LnR4dD4gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCj4gPiA+DQo+ID4gPiBUaGUgSUVTRyBw
bGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNp
dHMNCj4gPiA+IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBzdWJz
dGFudGl2ZSBjb21tZW50cyB0byB0aGUNCj4gPiA+IGlldGZAaWV0Zi5vcmc8bWFpbHRvOmlldGZA
aWV0Zi5vcmc+IG1haWxpbmcgbGlzdHMgYnkgMjAxMi0xMi0yNC4gRXhjZXB0aW9uYWxseSwgY29t
bWVudHMgbWF5IGJlDQo+ID4gPiBzZW50IHRvIGllc2dAaWV0Zi5vcmc8bWFpbHRvOmllc2dAaWV0
Zi5vcmc+IGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZQ0KPiA+ID4g
YmVnaW5uaW5nIG9mIHRoZSBTdWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0b21hdGVkIHNvcnRpbmcu
DQo+ID4gPg0KPiA+ID4gQWJzdHJhY3QNCj4gPiA+DQo+ID4gPg0KPiA+ID4gICAgVGhpcyBzcGVj
aWZpY2F0aW9uIHByb3ZpZGVzIGEgZnJhbWV3b3JrIGZvciB0aGUgdXNlIG9mIGFzc2VydGlvbnMN
Cj4gPiA+ICAgIHdpdGggT0F1dGggMi4wIGluIHRoZSBmb3JtIG9mIGEgbmV3IGNsaWVudCBhdXRo
ZW50aWNhdGlvbiBtZWNoYW5pc20NCj4gPiA+ICAgIGFuZCBhIG5ldyBhdXRob3JpemF0aW9uIGdy
YW50IHR5cGUuICBNZWNoYW5pc21zIGFyZSBzcGVjaWZpZWQgZm9yDQo+ID4gPiAgICB0cmFuc3Bv
cnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zIHdpdGggYSB0b2tlbiBlbmRwb2lu
dCwgYXMNCj4gPiA+ICAgIHdlbGwgYXMgZ2VuZXJhbCBwcm9jZXNzaW5nIHJ1bGVzLg0KPiA+ID4N
Cj4gPiA+ICAgIFRoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9uIGlzIHRvIHByb3ZpZGUg
YSBjb21tb24gZnJhbWV3b3JrIGZvcg0KPiA+ID4gICAgT0F1dGggMi4wIHRvIGludGVyd29yayB3
aXRoIG90aGVyIGlkZW50aXR5IHN5c3RlbXMgdXNpbmcgYXNzZXJ0aW9ucywNCj4gPiA+ICAgIGFu
ZCB0byBwcm92aWRlIGFsdGVybmF0aXZlIGNsaWVudCBhdXRoZW50aWNhdGlvbiBtZWNoYW5pc21z
Lg0KPiA+ID4NCj4gPiA+ICAgIE5vdGUgdGhhdCB0aGlzIHNwZWNpZmljYXRpb24gb25seSBkZWZp
bmVzIGFic3RyYWN0IG1lc3NhZ2UgZmxvd3MgYW5kDQo+ID4gPiAgICBwcm9jZXNzaW5nIHJ1bGVz
LiAgSW4gb3JkZXIgdG8gYmUgaW1wbGVtZW50YWJsZSwgY29tcGFuaW9uDQo+ID4gPiAgICBzcGVj
aWZpY2F0aW9ucyBhcmUgbmVjZXNzYXJ5IHRvIHByb3ZpZGUgdGhlIGNvcnJlc3BvbmRpbmcgY29u
Y3JldGUNCj4gPiA+ICAgIGluc3RhbnRpYXRpb25zLg0KPiA+ID4NCj4gPiA+DQo+ID4gPg0KPiA+
ID4NCj4gPiA+IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWENCj4gPiA+IGh0dHA6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLw0KPiA+ID4N
Cj4gPiA+IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4gPiA+IGh0dHA6Ly9k
YXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zL2JhbGxv
dC8NCj4gPiA+DQo+ID4gPg0KPiA+ID4gTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3Vi
bWl0dGVkIGRpcmVjdGx5IG9uIHRoaXMgSS1ELg0KPiA+ID4NCj4gPiA+DQo+ID4gPiBfX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+ID4gT0F1dGggbWFp
bGluZyBsaXN0DQo+ID4gPiBPQXV0aEBpZXRmLm9yZzxtYWlsdG86T0F1dGhAaWV0Zi5vcmc+DQo+
ID4gPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoDQo+ID4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBPQXV0aCBt
YWlsaW5nIGxpc3QNCj4gPiBPQXV0aEBpZXRmLm9yZzxtYWlsdG86T0F1dGhAaWV0Zi5vcmc+DQo+
ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aA0K

--_000_D6F62E8816564951A206FC6E20EBBAB5salesforcecom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPjxkaXY+WW91IHdhbnQg
YSBob2xkZXIgb2Yga2V5IHBhdHRlcm4uICZuYnNwO1RoZSBkcmFmdCB0b3VjaGVzIG9uIGl0PC9k
aXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PHByZSBzdHls
ZT0id29yZC13cmFwOiBicmVhay13b3JkOyAiPjxmb250IGNsYXNzPSJBcHBsZS1zdHlsZS1zcGFu
IiBmYWNlPSJIZWx2ZXRpY2EiPjxzcGFuIGNsYXNzPSJBcHBsZS1zdHlsZS1zcGFuIiBzdHlsZT0i
d2hpdGUtc3BhY2U6IG5vcm1hbDsiPg0KICAgVGhlIHByb3RvY29sIHBhcmFtZXRlcnMgYW5kIHBy
b2Nlc3NpbmcgcnVsZXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50DQogICBhcmUgaW50ZW5kZWQg
dG8gc3VwcG9ydCBhIGNsaWVudCBwcmVzZW50aW5nIGEgYmVhcmVyIGFzc2VydGlvbiB0byBhbg0K
ICAgYXV0aG9yaXphdGlvbiBzZXJ2ZXIuICBUaGUgdXNlIG9mIGhvbGRlci1vZi1rZXkgYXNzZXJ0
aW9ucyBhcmUgbm90DQogICBwcmVjbHVkZWQgYnkgdGhpcyBkb2N1bWVudCwgYnV0IGFkZGl0aW9u
YWwgcHJvdG9jb2wgZGV0YWlscyB3b3VsZA0KICAgbmVlZCB0byBiZSBzcGVjaWZpZWQuPC9zcGFu
PjwvZm9udD48c3BhbiBjbGFzcz0iQXBwbGUtc3R5bGUtc3BhbiIgc3R5bGU9ImZvbnQtZmFtaWx5
OiBUaW1lczsgZm9udC1zaXplOiBtZWRpdW07IHdoaXRlLXNwYWNlOiBwcmUtd3JhcDsgLXdlYmtp
dC10YXAtaGlnaGxpZ2h0LWNvbG9yOiByZ2JhKDI2LCAyNiwgMjYsIDAuMjkyOTY5KTsgLXdlYmtp
dC1jb21wb3NpdGlvbi1maWxsLWNvbG9yOiByZ2JhKDE3NSwgMTkyLCAyMjcsIDAuMjMwNDY5KTsg
LXdlYmtpdC1jb21wb3NpdGlvbi1mcmFtZS1jb2xvcjogcmdiYSg3NywgMTI4LCAxODAsIDAuMjMw
NDY5KTsgIj4NCjwvc3Bhbj48L3ByZT48ZGl2IHN0eWxlPSJmb250LWZhbWlseTogVGltZXM7IGZv
bnQtc2l6ZTogbWVkaXVtOyAtd2Via2l0LXRhcC1oaWdobGlnaHQtY29sb3I6IHJnYmEoMjYsIDI2
LCAyNiwgMC4yOTI5NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZpbGwtY29sb3I6IHJnYmEoMTc1
LCAxOTIsIDIyNywgMC4yMzA0NjkpOyAtd2Via2l0LWNvbXBvc2l0aW9uLWZyYW1lLWNvbG9yOiBy
Z2JhKDc3LCAxMjgsIDE4MCwgMC4yMzA0NjkpOyAiPjxicj48L2Rpdj48ZGl2PlNvIC0gaWYgeW91
IHdhbnQgdGhpcywgeW91IHNob3VsZCBwdXQgZm9ydGggYSBob2xkZXIgb2Yga2V5IHByb2ZpbGlu
ZyBvZiB0aGlzIGRyYWZ0IGFuZCBzZWUgaWYgdGhlcmUgYXJlIGFueSBpc3N1ZXMuICZuYnNwOyBU
aGUgb25seSBwcm9maWxlcyB3ZSBoYXZlIHRodXMgZmFyIGFyZSBzYW1sIGFuZCBqd3QgYmVhcmVy
IGFzc2VydGlvbnMuICZuYnNwOzwvZGl2PjxkaXY+PGJyPjxicj4tIGNtb3J0PC9kaXY+PGRpdj48
YnI+T24gRGVjIDEzLCAyMDEyLCBhdCA2OjI3IFBNLCAiPGEgaHJlZj0ibWFpbHRvOnpob3Uuc3Vq
aW5nQHp0ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248L2E+IiAmbHQ7PGEgaHJlZj0i
bWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248L2E+
Jmd0OyB3cm90ZTo8YnI+PGJyPjwvZGl2PjxkaXY+PC9kaXY+PGJsb2NrcXVvdGUgdHlwZT0iY2l0
ZSI+PGRpdj4NCjxicj48Zm9udCBzaXplPSIyIiBmYWNlPSJzYW5zLXNlcmlmIj5JIGFtIG5vdCBz
dXJlIGlmIHRoZSBmb2xsb3dpbmcgdXNlY2FzZQ0KJm5ic3A7PGEgaHJlZj0iaHR0cDovL3d3dy5p
ZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL29hdXRoL2N1cnJlbnQvbXNnMTAyMzMuaHRtbCI+aHR0
cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL29hdXRoL2N1cnJlbnQvbXNnMTAyMzMu
aHRtbDwvYT48L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0ic2Fucy1zZXJpZiI+Y291
bGQgYmUgc3VwcG9ydGVkIGJ5IGFzc2VydGlvbiBmcmFtZXdvcmvvvIw8L2ZvbnQ+DQo8YnI+PGZv
bnQgc2l6ZT0iMiIgZmFjZT0ic2Fucy1zZXJpZiI+V2UgaGF2ZSBzb21lIGRpc2N1c3Npb24gaW4g
Jm5ic3A7PC9mb250Pg0KPGJyPjxmb250IHNpemU9IjIiIGZhY2U9InNhbnMtc2VyaWYiPjxhIGhy
ZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9jdXJyZW50L21z
ZzEwMjAzLmh0bWwiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9j
dXJyZW50L21zZzEwMjAzLmh0bWw8L2E+PC9mb250Pg0KPGJyPjxmb250IHNpemU9IjIiIGZhY2U9
InNhbnMtc2VyaWYiPjxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dl
Yi9vYXV0aC9jdXJyZW50L21zZzEwMTk4Lmh0bWwiPmh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1h
cmNoaXZlL3dlYi9vYXV0aC9jdXJyZW50L21zZzEwMTk4Lmh0bWw8L2E+DQo8L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0ic2Fucy1zZXJpZiI+SW4gbXkgdXNlIGNhc2Ugb3Ig
aW4gc29tZSBvdGhlciBjYXNlcywNCmFzc2VydGlvbnMgZG9uJ3QgbmVlZCBjb25maWRlbnRpYWwg
cHJvdGVjdGlvbiwgPC9mb250Pg0KPGJyPjxmb250IHNpemU9IjIiIGZhY2U9InNhbnMtc2VyaWYi
PmJhc2ljYWxseSBTVFMgZG9uJ3QgaGF2ZSB0byBhdXRoZW50aWNhdGUNCmEgY2xpZW50IGJlZm9y
ZSBpc3N1ZWluZyAiYXNzZXJ0aW9uIiwgaWYgaXQgY291bGQgYmUgY2FsbGVkIGFzc2VydGlvbg0K
aGVyZS48L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0ic2Fucy1zZXJpZiI+
RXhhbXBsZSxJIHRydXN0IG15IGxheXdlciwgSSBtYXkgaXNzdWUNCmFuICJhc3NlcnRpb24iIHN0
YXRpbmcgZGVsZWdhdGlvbiBpbiBhZHZhbmNlLCBhbmQgc2VuZCB0byB0aGUNCmxhd3llciB3aGVu
IGl0IGlzIG5lZWRlZCw8L2ZvbnQ+DQo8YnI+PGZvbnQgc2l6ZT0iMiIgZmFjZT0ic2Fucy1zZXJp
ZiI+aXQgY291bGQgYmUgSSBnaXZlIHRoZSBhc3NlcnRpb24gdG8NCmEgZmFsc2UgbGF3eWVyLCBi
dXQgaXQgZG9lcyBub3QgbWF0dGVyLCBiZWNhdXNlIHRoZSBsYXd5ZXIgaGFzIHRvIHByb3ZlDQpo
ZSBrbm93cyBzb21lIGNyZWRlbnRpYWwgY29ycmVzcG9uZGluZyB0byBoaXMgSUQsPC9mb250Pg0K
PGJyPjxmb250IHNpemU9IjIiIGZhY2U9InNhbnMtc2VyaWYiPndobyBpcyBkZWxlZ2F0ZWQgc29t
ZSByaWdodHMuPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9IjIiIGZhY2U9InNhbnMtc2Vy
aWYiPklmIGFzc2VydGlvbiBmcmFtZXdvcmsgd2FudCB0byBzdXBwb3J0DQp0aGlzIHVzZSBjYXNl
LCB0aGVuIGdlbmVyYXRpb24gb2YgYXNzZXJ0aW9uIHNob3VsZCBiZSByZWxheGVkLDwvZm9udD4N
Cjxicj48Zm9udCBzaXplPSIyIiBmYWNlPSJzYW5zLXNlcmlmIj5vdGhlcndpc2UgbmV3IHdvcmsg
aXMgcmVxdWlyZWQgdG8gc3VwcG9ydA0KdGhlIHVzZSBjYXNlLjwvZm9udD4NCjxicj4NCjxicj4N
Cjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0iMiI+Q2h1Y2sgTW9ydGltb3JlICZsdDs8YSBocmVm
PSJtYWlsdG86Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbSI+Y21vcnRpbW9yZUBzYWxlc2ZvcmNl
LmNvbTwvYT4mZ3Q7DQrlhpnkuo4gMjAxMi0xMi0xNCAxMDowODozNDo8YnI+DQo8YnI+DQomZ3Q7
IE9uIERlYyAxMywgMjAxMiwgYXQgNDozMCBQTSwgIjxhIGhyZWY9Im1haWx0bzp6aG91LnN1amlu
Z0B6dGUuY29tLmNuIj56aG91LnN1amluZ0B6dGUuY29tLmNuPC9hPiIgJmx0OzxhIGhyZWY9Im1h
aWx0bzp6aG91LnN1amluZ0B6dGUuY29tLmNuIj56aG91LnN1amluZ0B6dGUuY29tLmNuPC9hPjxi
cj4NCiZndDsgJmd0OyB3cm90ZTo8YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6
ZT0iMiI+Jmd0OyA8YnI+DQomZ3Q7IEZyb20gdGhlIGxhbmd1YWdlLCBJIGdvdCBhbiBpbXByZXNz
aW9uIHRoYXQgYXNzZXJ0aW9uIGlzIG9ubHkgPGJyPg0KJmd0OyBnZW5lcmF0ZWQgYnkgdG9rZW4g
c2VydmljZSBhZnRlciBjbGllbnRzIHByZXNlbnRpbmcgc29tZSBjcmVkZW50aWFscywNCjxicj4N
CiZndDsgdGhlcmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRoYXQgImFzc2VydGlvbiIgZG9uJ3Qg
bmVlZA0KY2xpZW50J3MgY3JlZGVudGlhbC4gPGJyPg0KJmd0OyBlLmcuLCBSZXNvdXJjZSBvd25l
ciBhcyBhIHRva2VuIHNlcnZpY2UgJm5ic3A7Y291bGQgZ2VuZXJhdGUgImFzc2VydGlvbiINCjxi
cj4NCiZndDsgdG8gYSBjbGllbnQgaGUgdHJ1c3RzLCBidSBzaWduaW5nIGEgc3RhdGVtZW50IHRo
YXQgIlRoaXMgZGVsZWdhdGlvbg0KPGJyPg0KJmd0OyBpcyBnaXZlbiB0byBhIGNsaWVudCBjYWxs
ZWQgY2xpbmV0LWlkIDxicj4NCiZndDsgZm9yIGRvaW5nIHNvbWV0aGluZyBmb3IgbWUiLiA8L2Zv
bnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0iMiI+Jmd0OyA8YnI+DQomZ3Q7IFNvIGhvdyBk
b2VzIHRoZSBTVFMgdHJ1c3QgdGhlIGNsaWVudD8gJm5ic3A7IFByZXN1bWFibHkgaWYgaXQgaXMg
dHJ1c3RlZA0KPGJyPg0KJmd0OyBpdCBoYXMgc29tZSBsZXZlbCBvZiBhdXRoZW50aWNhdGlvbiwg
eWVzPzwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPSIyIj4mZ3Q7IDxicj4NCiZndDsg
LWNtb3J0PC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9IjIiPiZndDsgPGJyPg0KJmd0
OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IENodWNrIE1vcnRp
bW9yZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20iPmNtb3J0
aW1vcmVAc2FsZXNmb3JjZS5jb208L2E+Jmd0OyDlhpnkuo4gMjAxMi0xMi0xNA0KMDA6Mzk6MDM6
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgVGhlIGxhbmd1YWdlIGlzIHNpbXBseSBtZWFudCB0
byBoZWxwIGlsbHVzdHJhdGUgaG93IHRoZSBmcmFtZXdvcmsNCjxicj4NCiZndDsgJmd0OyBtaWdo
dCBiZSB1c2VkLiAmbmJzcDsgSG93IGRvIHlvdSB0aGluayBpdCB3aWxsIHJlc3RyaWN0IHVzYWdl
Pw0KJm5ic3A7IEhvdyA8YnI+DQomZ3Q7ICZndDsgY291bGQgaXQgYmUgaW1wcm92ZWQ/IDxicj4N
CiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgLWNtb3J0IDxicj4NCiZndDsgJmd0OyA8YnI+DQom
Z3Q7ICZndDsgT24gRGVjIDEyLCAyMDEyLCBhdCAxMTowNCBQTSwgJmx0OzxhIGhyZWY9Im1haWx0
bzp6aG91LnN1amluZ0B6dGUuY29tLmNuIj56aG91LnN1amluZ0B6dGUuY29tLmNuPC9hPiZndDsN
Cndyb3RlOiA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBJ
biAic2VjdGlvbiAzIDxicj4NCiZndDsgJmd0OyAmbmJzcDtUaGUgdG9rZW4gc2VydmljZSBpcyB0
aGUgYXNzZXJ0aW9uIGlzc3VlcjsgaXRzIDxicj4NCiZndDsgJmd0OyAmbmJzcDtyb2xlIGlzIHRv
IGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBjbGllbnRzLCB3aGljaCBwcmVzZW50DQp2YXJpb3VzIDxi
cj4NCiZndDsgJmd0OyAmbmJzcDtjcmVkZW50aWFscywgYW5kIG1pbnQgYXNzZXJ0aW9ucyBhcyBy
ZXF1ZXN0ZWQsIGZpbGwgdGhlbQ0Kd2l0aCA8YnI+DQomZ3Q7ICZndDsgJm5ic3A7YXBwcm9wcmlh
dGUgaW5mb3JtYXRpb24sIGFuZCBzaWduIHRoZW0uIiA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0
OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBBcyBJIHVuZGVyc3RhbmQsIGFuIGFzc2VydGlvbiBnZW5l
cmF0ZWQgYnkgYSBTVFMsIGlzIGRvbmUgZmxvbGxvd2luZzxicj4NCiZndDsgJmd0OyB0aGVzcyBz
dGVwczogPGJyPg0KJmd0OyAmZ3Q7IDEuIENsaWVudCBwcmVzZW50cyBjcmVkZW50aWFsIGFuZCBy
ZXF1ZXN0cyBhbiBhc3NlcnRpb24gPGJyPg0KJmd0OyAmZ3Q7IDIuIFNUUyBnZW5lcmF0ZXMgYXNz
ZXJ0aW9uIGFuZCBzZW5kcyB0byBDbGllbnQgPGJyPg0KJmd0OyAmZ3Q7IENvcnJlY3Q/IDxicj4N
CiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgVGhhdCBtYXkgcmVzdHJpY3QgdGhlIHVzZSBjYXNl
cyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yaw0KPGJyPg0KJmd0OyBjb3VsZCBzdXBwb3J0
LCA8YnI+DQomZ3Q7ICZndDsgaXMgaXQgYSBtdXN0PyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0
OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxh
IGhyZWY9Im1haWx0bzpvYXV0aC1ib3VuY2VzQGlldGYub3JnIj5vYXV0aC1ib3VuY2VzQGlldGYu
b3JnPC9hPiDlhpnkuo4gMjAxMi0xMi0xMSAwMjozMzo1Nzo8YnI+DQomZ3Q7ICZndDsgPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhlIElFU0cgaGFzIHJlY2VpdmVk
IGEgcmVxdWVzdCBmcm9tIHRoZSBXZWIgQXV0aG9yaXphdGlvbg0KUHJvdG9jb2wgV0c8YnI+DQom
Z3Q7ICZndDsgJmd0OyAob2F1dGgpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgLSAnQXNzZXJ0aW9uIEZyYW1ld29yayBmb3IgT0F1dGggMi4w
Jzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbHQ7ZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRp
b25zLTA4LnR4dCZndDsgYXMgUHJvcG9zZWQNClN0YW5kYXJkPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRlY2lzaW9uIGlu
IHRoZSBuZXh0IGZldyB3ZWVrcywNCmFuZCBzb2xpY2l0czxicj4NCiZndDsgJmd0OyAmZ3Q7IGZp
bmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ugc2VuZCBzdWJzdGFudGl2ZSBjb21t
ZW50cw0KdG8gdGhlPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0
Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+IG1haWxpbmcgbGlzdHMgYnkgMjAxMi0xMi0yNC4gRXhj
ZXB0aW9uYWxseSwNCmNvbW1lbnRzIG1heSBiZTxicj4NCiZndDsgJmd0OyAmZ3Q7IHNlbnQgdG8g
PGEgaHJlZj0ibWFpbHRvOmllc2dAaWV0Zi5vcmciPmllc2dAaWV0Zi5vcmc8L2E+IGluc3RlYWQu
IEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluDQp0aGU8YnI+DQomZ3Q7ICZndDsgJmd0OyBi
ZWdpbm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy48
YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBBYnN0cmFjdDxicj4NCiZn
dDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZu
YnNwOyAmbmJzcDtUaGlzIHNwZWNpZmljYXRpb24gcHJvdmlkZXMgYSBmcmFtZXdvcmsgZm9yDQp0
aGUgdXNlIG9mIGFzc2VydGlvbnM8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7d2l0
aCBPQXV0aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBuZXcgY2xpZW50DQphdXRoZW50aWNhdGlvbiBt
ZWNoYW5pc208YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7YW5kIGEgbmV3IGF1dGhv
cml6YXRpb24gZ3JhbnQgdHlwZS4gJm5ic3A7TWVjaGFuaXNtcw0KYXJlIHNwZWNpZmllZCBmb3I8
YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7dHJhbnNwb3J0aW5nIGFzc2VydGlvbnMg
ZHVyaW5nIGludGVyYWN0aW9ucw0Kd2l0aCBhIHRva2VuIGVuZHBvaW50LCBhczxicj4NCiZndDsg
Jmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDt3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBydWxlcy48
YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7VGhl
IGludGVudCBvZiB0aGlzIHNwZWNpZmljYXRpb24gaXMgdG8gcHJvdmlkZQ0KYSBjb21tb24gZnJh
bWV3b3JrIGZvcjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtPQXV0aCAyLjAgdG8g
aW50ZXJ3b3JrIHdpdGggb3RoZXIgaWRlbnRpdHkNCnN5c3RlbXMgdXNpbmcgYXNzZXJ0aW9ucyw8
YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7YW5kIHRvIHByb3ZpZGUgYWx0ZXJuYXRp
dmUgY2xpZW50IGF1dGhlbnRpY2F0aW9uDQptZWNoYW5pc21zLjxicj4NCiZndDsgJmd0OyAmZ3Q7
IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtOb3RlIHRoYXQgdGhpcyBzcGVjaWZp
Y2F0aW9uIG9ubHkgZGVmaW5lcyBhYnN0cmFjdA0KbWVzc2FnZSBmbG93cyBhbmQ8YnI+DQomZ3Q7
ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7cHJvY2Vzc2luZyBydWxlcy4gJm5ic3A7SW4gb3JkZXIg
dG8gYmUgaW1wbGVtZW50YWJsZSwNCmNvbXBhbmlvbjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNw
OyAmbmJzcDtzcGVjaWZpY2F0aW9ucyBhcmUgbmVjZXNzYXJ5IHRvIHByb3ZpZGUgdGhlDQpjb3Jy
ZXNwb25kaW5nIGNvbmNyZXRlPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2luc3Rh
bnRpYXRpb25zLjxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4N
CiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7
IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWE8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YSBocmVm
PSJodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0
aW9ucy8iPmh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1h
c3NlcnRpb25zLzwvYT48YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBJ
RVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGEg
aHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFz
c2VydGlvbnMvYmFsbG90LyI+aHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1p
ZXRmLW9hdXRoLWFzc2VydGlvbnMvYmFsbG90LzwvYT48YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+
DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBObyBJUFIgZGVjbGFyYXRpb25z
IGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcw0KSS1ELjxicj4NCiZndDsgJmd0
OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgT0F1dGggbWFpbGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGEgaHJlZj0ibWFpbHRv
Ok9BdXRoQGlldGYub3JnIj5PQXV0aEBpZXRmLm9yZzwvYT48YnI+DQomZ3Q7ICZndDsgJmd0OyA8
YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoIj5odHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoPC9hPjxicj4NCiZndDsgJmd0
OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZn
dDsgJmd0OyBPQXV0aCBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsgPGEgaHJlZj0ibWFpbHRv
Ok9BdXRoQGlldGYub3JnIj5PQXV0aEBpZXRmLm9yZzwvYT48YnI+DQomZ3Q7ICZndDsgPGEgaHJl
Zj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aCI+aHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aDwvYT4gPC9mb250PjwvdHQ+DQo8L2Rp
dj48L2Jsb2NrcXVvdGU+PC9ib2R5PjwvaHRtbD4=

--_000_D6F62E8816564951A206FC6E20EBBAB5salesforcecom_--

From zhou.sujing@zte.com.cn  Thu Dec 13 18:40:05 2012
Return-Path: <zhou.sujing@zte.com.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 2ED7221F8A96; Thu, 13 Dec 2012 18:40:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.7
X-Spam-Level: 
X-Spam-Status: No, score=-97.7 tagged_above=-999 required=5 tests=[AWL=-0.327,  BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, J_CHICKENPOX_71=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ziu89OEbk3vu; Thu, 13 Dec 2012 18:40:04 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 36CDB21F8929; Thu, 13 Dec 2012 18:39:52 -0800 (PST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 7C8AA1243DCB; Fri, 14 Dec 2012 10:41:43 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id qBE2dXrP046580; Fri, 14 Dec 2012 10:39:33 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <D6F62E88-1656-4951-A206-FC6E20EBBAB5@salesforce.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Subject: Re: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OFB954FF83.FB35CC6D-ON48257AD4.000E8DAF-48257AD4.000EB9D8@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Fri, 14 Dec 2012 10:39:19 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-12-14 10:39:26, Serialize complete at 2012-12-14 10:39:26
Content-Type: multipart/alternative; boundary="=_alternative 000EB9D648257AD4_="
X-MAIL: mse01.zte.com.cn qBE2dXrP046580
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:49 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 02:40:05 -0000

This is a multipart message in MIME format.
--=_alternative 000EB9D648257AD4_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

T2gsIEJ1dCB0aGUgZGVzY3JpcHRpb24gb2YgYXNzZXJ0aW9uIGdlbmVyYXRpb24gaW4gdGhlIGRv
Y3VtZW50IHNob3VsZCBub3QgDQpiZSBsaW1pdGVkIGJ5IGJlYXIgYXNzZXJ0aW9uLCByaWdodD8N
Cg0KDQpDaHVjayBNb3J0aW1vcmUgPGNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20+INC009ogMjAx
Mi0xMi0xNCAxMDozNDoxMzoNCg0KPiBZb3Ugd2FudCBhIGhvbGRlciBvZiBrZXkgcGF0dGVybi4g
IFRoZSBkcmFmdCB0b3VjaGVzIG9uIGl0DQo+IA0KPiANCj4gICAgVGhlIHByb3RvY29sIHBhcmFt
ZXRlcnMgYW5kIHByb2Nlc3NpbmcgcnVsZXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50DQo+ICAg
IGFyZSBpbnRlbmRlZCB0byBzdXBwb3J0IGEgY2xpZW50IHByZXNlbnRpbmcgYSBiZWFyZXIgYXNz
ZXJ0aW9uIHRvIGFuDQo+ICAgIGF1dGhvcml6YXRpb24gc2VydmVyLiAgVGhlIHVzZSBvZiBob2xk
ZXItb2Yta2V5IGFzc2VydGlvbnMgYXJlIG5vdA0KPiAgICBwcmVjbHVkZWQgYnkgdGhpcyBkb2N1
bWVudCwgYnV0IGFkZGl0aW9uYWwgcHJvdG9jb2wgZGV0YWlscyB3b3VsZA0KPiAgICBuZWVkIHRv
IGJlIHNwZWNpZmllZC4NCg0KPiANCj4gU28gLSBpZiB5b3Ugd2FudCB0aGlzLCB5b3Ugc2hvdWxk
IHB1dCBmb3J0aCBhIGhvbGRlciBvZiBrZXkgDQo+IHByb2ZpbGluZyBvZiB0aGlzIGRyYWZ0IGFu
ZCBzZWUgaWYgdGhlcmUgYXJlIGFueSBpc3N1ZXMuICAgVGhlIG9ubHkgDQo+IHByb2ZpbGVzIHdl
IGhhdmUgdGh1cyBmYXIgYXJlIHNhbWwgYW5kIGp3dCBiZWFyZXIgYXNzZXJ0aW9ucy4gDQo+IA0K
PiANCj4gLSBjbW9ydA0KPiANCj4gT24gRGVjIDEzLCAyMDEyLCBhdCA2OjI3IFBNLCAiemhvdS5z
dWppbmdAenRlLmNvbS5jbiIgDQo8emhvdS5zdWppbmdAenRlLmNvbS5jbg0KPiA+IHdyb3RlOg0K
DQo+IA0KPiBJIGFtIG5vdCBzdXJlIGlmIHRoZSBmb2xsb3dpbmcgdXNlY2FzZSAgaHR0cDovL3d3
dy5pZXRmLm9yZy9tYWlsLQ0KPiBhcmNoaXZlL3dlYi9vYXV0aC9jdXJyZW50L21zZzEwMjMzLmh0
bWwgDQo+IGNvdWxkIGJlIHN1cHBvcnRlZCBieSBhc3NlcnRpb24gZnJhbWV3b3Jro6wgDQo+IFdl
IGhhdmUgc29tZSBkaXNjdXNzaW9uIGluIA0KPiBodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJj
aGl2ZS93ZWIvb2F1dGgvY3VycmVudC9tc2cxMDIwMy5odG1sIA0KPiBodHRwOi8vd3d3LmlldGYu
b3JnL21haWwtYXJjaGl2ZS93ZWIvb2F1dGgvY3VycmVudC9tc2cxMDE5OC5odG1sIA0KPiANCj4g
SW4gbXkgdXNlIGNhc2Ugb3IgaW4gc29tZSBvdGhlciBjYXNlcywgYXNzZXJ0aW9ucyBkb24ndCBu
ZWVkIA0KPiBjb25maWRlbnRpYWwgcHJvdGVjdGlvbiwgDQo+IGJhc2ljYWxseSBTVFMgZG9uJ3Qg
aGF2ZSB0byBhdXRoZW50aWNhdGUgYSBjbGllbnQgYmVmb3JlIGlzc3VlaW5nIA0KPiAiYXNzZXJ0
aW9uIiwgaWYgaXQgY291bGQgYmUgY2FsbGVkIGFzc2VydGlvbiBoZXJlLiANCj4gDQo+IEV4YW1w
bGUsSSB0cnVzdCBteSBsYXl3ZXIsIEkgbWF5IGlzc3VlIGFuICJhc3NlcnRpb24iIHN0YXRpbmcg
DQo+IGRlbGVnYXRpb24gaW4gYWR2YW5jZSwgYW5kIHNlbmQgdG8gdGhlIGxhd3llciB3aGVuIGl0
IGlzIG5lZWRlZCwgDQo+IGl0IGNvdWxkIGJlIEkgZ2l2ZSB0aGUgYXNzZXJ0aW9uIHRvIGEgZmFs
c2UgbGF3eWVyLCBidXQgaXQgZG9lcyBub3QgDQo+IG1hdHRlciwgYmVjYXVzZSB0aGUgbGF3eWVy
IGhhcyB0byBwcm92ZSBoZSBrbm93cyBzb21lIGNyZWRlbnRpYWwgDQo+IGNvcnJlc3BvbmRpbmcg
dG8gaGlzIElELCANCj4gd2hvIGlzIGRlbGVnYXRlZCBzb21lIHJpZ2h0cy4gDQo+IA0KPiBJZiBh
c3NlcnRpb24gZnJhbWV3b3JrIHdhbnQgdG8gc3VwcG9ydCB0aGlzIHVzZSBjYXNlLCB0aGVuIA0K
PiBnZW5lcmF0aW9uIG9mIGFzc2VydGlvbiBzaG91bGQgYmUgcmVsYXhlZCwgDQo+IG90aGVyd2lz
ZSBuZXcgd29yayBpcyByZXF1aXJlZCB0byBzdXBwb3J0IHRoZSB1c2UgY2FzZS4gDQo+IA0KPiAN
Cj4gDQo+IENodWNrIE1vcnRpbW9yZSA8Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbT4g0LTT2iAy
MDEyLTEyLTE0IDEwOjA4OjM0Og0KPiANCj4gPiBPbiBEZWMgMTMsIDIwMTIsIGF0IDQ6MzAgUE0s
ICJ6aG91LnN1amluZ0B6dGUuY29tLmNuIiA8emhvdS4NCj4gc3VqaW5nQHp0ZS5jb20uY24NCj4g
PiA+IHdyb3RlOg0KPiANCj4gPiANCj4gPiBGcm9tIHRoZSBsYW5ndWFnZSwgSSBnb3QgYW4gaW1w
cmVzc2lvbiB0aGF0IGFzc2VydGlvbiBpcyBvbmx5IA0KPiA+IGdlbmVyYXRlZCBieSB0b2tlbiBz
ZXJ2aWNlIGFmdGVyIGNsaWVudHMgcHJlc2VudGluZyBzb21lIGNyZWRlbnRpYWxzLCANCj4gPiB0
aGVyZSBhcmUgbWF5IGJlIHNvbWUgY2FzZXMgdGhhdCAiYXNzZXJ0aW9uIiBkb24ndCBuZWVkIGNs
aWVudCdzIA0KPiBjcmVkZW50aWFsLiANCj4gPiBlLmcuLCBSZXNvdXJjZSBvd25lciBhcyBhIHRv
a2VuIHNlcnZpY2UgIGNvdWxkIGdlbmVyYXRlICJhc3NlcnRpb24iIA0KPiA+IHRvIGEgY2xpZW50
IGhlIHRydXN0cywgYnUgc2lnbmluZyBhIHN0YXRlbWVudCB0aGF0ICJUaGlzIGRlbGVnYXRpb24g
DQo+ID4gaXMgZ2l2ZW4gdG8gYSBjbGllbnQgY2FsbGVkIGNsaW5ldC1pZCANCj4gPiBmb3IgZG9p
bmcgc29tZXRoaW5nIGZvciBtZSIuIA0KPiA+IA0KPiA+IFNvIGhvdyBkb2VzIHRoZSBTVFMgdHJ1
c3QgdGhlIGNsaWVudD8gICBQcmVzdW1hYmx5IGlmIGl0IGlzIHRydXN0ZWQgDQo+ID4gaXQgaGFz
IHNvbWUgbGV2ZWwgb2YgYXV0aGVudGljYXRpb24sIHllcz8gDQo+ID4gDQo+ID4gLWNtb3J0IA0K
PiA+IA0KPiA+IA0KPiA+IA0KPiA+IA0KPiA+IA0KPiA+IENodWNrIE1vcnRpbW9yZSA8Y21vcnRp
bW9yZUBzYWxlc2ZvcmNlLmNvbT4g0LTT2iAyMDEyLTEyLTE0IDAwOjM5OjAzOg0KPiA+IA0KPiA+
ID4gVGhlIGxhbmd1YWdlIGlzIHNpbXBseSBtZWFudCB0byBoZWxwIGlsbHVzdHJhdGUgaG93IHRo
ZSBmcmFtZXdvcmsgDQo+ID4gPiBtaWdodCBiZSB1c2VkLiAgIEhvdyBkbyB5b3UgdGhpbmsgaXQg
d2lsbCByZXN0cmljdCB1c2FnZT8gICBIb3cgDQo+ID4gPiBjb3VsZCBpdCBiZSBpbXByb3ZlZD8g
DQo+ID4gPiANCj4gPiA+IC1jbW9ydCANCj4gPiA+IA0KPiA+ID4gT24gRGVjIDEyLCAyMDEyLCBh
dCAxMTowNCBQTSwgPHpob3Uuc3VqaW5nQHp0ZS5jb20uY24+IHdyb3RlOiANCj4gPiA+IA0KPiA+
ID4gDQo+ID4gPiBJbiAic2VjdGlvbiAzIA0KPiA+ID4gIFRoZSB0b2tlbiBzZXJ2aWNlIGlzIHRo
ZSBhc3NlcnRpb24gaXNzdWVyOyBpdHMgDQo+ID4gPiAgcm9sZSBpcyB0byBmdWxmaWxsIHJlcXVl
c3RzIGZyb20gY2xpZW50cywgd2hpY2ggcHJlc2VudCB2YXJpb3VzIA0KPiA+ID4gIGNyZWRlbnRp
YWxzLCBhbmQgbWludCBhc3NlcnRpb25zIGFzIHJlcXVlc3RlZCwgZmlsbCB0aGVtIHdpdGggDQo+
ID4gPiAgYXBwcm9wcmlhdGUgaW5mb3JtYXRpb24sIGFuZCBzaWduIHRoZW0uIiANCj4gPiA+IA0K
PiA+ID4gDQo+ID4gPiBBcyBJIHVuZGVyc3RhbmQsIGFuIGFzc2VydGlvbiBnZW5lcmF0ZWQgYnkg
YSBTVFMsIGlzIGRvbmUgZmxvbGxvd2luZw0KPiA+ID4gdGhlc3Mgc3RlcHM6IA0KPiA+ID4gMS4g
Q2xpZW50IHByZXNlbnRzIGNyZWRlbnRpYWwgYW5kIHJlcXVlc3RzIGFuIGFzc2VydGlvbiANCj4g
PiA+IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFuZCBzZW5kcyB0byBDbGllbnQgDQo+ID4g
PiBDb3JyZWN0PyANCj4gPiA+IA0KPiA+ID4gVGhhdCBtYXkgcmVzdHJpY3QgdGhlIHVzZSBjYXNl
cyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yayANCj4gPiBjb3VsZCBzdXBwb3J0LCANCj4g
PiA+IGlzIGl0IGEgbXVzdD8gDQo+ID4gPiANCj4gPiA+IA0KPiA+ID4gDQo+ID4gPiANCj4gPiA+
IG9hdXRoLWJvdW5jZXNAaWV0Zi5vcmcg0LTT2iAyMDEyLTEyLTExIDAyOjMzOjU3Og0KPiA+ID4g
DQo+ID4gPiA+IA0KPiA+ID4gPiBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20g
dGhlIFdlYiBBdXRob3JpemF0aW9uIA0KUHJvdG9jb2wgV0cNCj4gPiA+ID4gKG9hdXRoKSB0byBj
b25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Og0KPiA+ID4gPiAtICdBc3NlcnRpb24gRnJh
bWV3b3JrIGZvciBPQXV0aCAyLjAnDQo+ID4gPiA+ICAgPGRyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0
aW9ucy0wOC50eHQ+IGFzIFByb3Bvc2VkIFN0YW5kYXJkDQo+ID4gPiA+IA0KPiA+ID4gPiBUaGUg
SUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQg
DQpzb2xpY2l0cw0KPiA+ID4gPiBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNl
IHNlbmQgc3Vic3RhbnRpdmUgY29tbWVudHMgdG8gDQp0aGUNCj4gPiA+ID4gaWV0ZkBpZXRmLm9y
ZyBtYWlsaW5nIGxpc3RzIGJ5IDIwMTItMTItMjQuIEV4Y2VwdGlvbmFsbHksIA0KPiBjb21tZW50
cyBtYXkgYmUNCj4gPiA+ID4gc2VudCB0byBpZXNnQGlldGYub3JnIGluc3RlYWQuIEluIGVpdGhl
ciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZQ0KPiA+ID4gPiBiZWdpbm5pbmcgb2YgdGhlIFN1Ympl
Y3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4gPiA+ID4gDQo+ID4gPiA+IEFi
c3RyYWN0DQo+ID4gPiA+IA0KPiA+ID4gPiANCj4gPiA+ID4gICAgVGhpcyBzcGVjaWZpY2F0aW9u
IHByb3ZpZGVzIGEgZnJhbWV3b3JrIGZvciB0aGUgdXNlIG9mIA0KYXNzZXJ0aW9ucw0KPiA+ID4g
PiAgICB3aXRoIE9BdXRoIDIuMCBpbiB0aGUgZm9ybSBvZiBhIG5ldyBjbGllbnQgYXV0aGVudGlj
YXRpb24gDQptZWNoYW5pc20NCj4gPiA+ID4gICAgYW5kIGEgbmV3IGF1dGhvcml6YXRpb24gZ3Jh
bnQgdHlwZS4gIE1lY2hhbmlzbXMgYXJlIHNwZWNpZmllZCANCmZvcg0KPiA+ID4gPiAgICB0cmFu
c3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zIHdpdGggYSB0b2tlbiANCmVu
ZHBvaW50LCBhcw0KPiA+ID4gPiAgICB3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBydWxlcy4N
Cj4gPiA+ID4gDQo+ID4gPiA+ICAgIFRoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9uIGlz
IHRvIHByb3ZpZGUgYSBjb21tb24gDQpmcmFtZXdvcmsgZm9yDQo+ID4gPiA+ICAgIE9BdXRoIDIu
MCB0byBpbnRlcndvcmsgd2l0aCBvdGhlciBpZGVudGl0eSBzeXN0ZW1zIHVzaW5nIA0KYXNzZXJ0
aW9ucywNCj4gPiA+ID4gICAgYW5kIHRvIHByb3ZpZGUgYWx0ZXJuYXRpdmUgY2xpZW50IGF1dGhl
bnRpY2F0aW9uIG1lY2hhbmlzbXMuDQo+ID4gPiA+IA0KPiA+ID4gPiAgICBOb3RlIHRoYXQgdGhp
cyBzcGVjaWZpY2F0aW9uIG9ubHkgZGVmaW5lcyBhYnN0cmFjdCBtZXNzYWdlIA0KZmxvd3MgYW5k
DQo+ID4gPiA+ICAgIHByb2Nlc3NpbmcgcnVsZXMuICBJbiBvcmRlciB0byBiZSBpbXBsZW1lbnRh
YmxlLCBjb21wYW5pb24NCj4gPiA+ID4gICAgc3BlY2lmaWNhdGlvbnMgYXJlIG5lY2Vzc2FyeSB0
byBwcm92aWRlIHRoZSBjb3JyZXNwb25kaW5nIA0KY29uY3JldGUNCj4gPiA+ID4gICAgaW5zdGFu
dGlhdGlvbnMuDQo+ID4gPiA+IA0KPiA+ID4gPiANCj4gPiA+ID4gDQo+ID4gPiA+IA0KPiA+ID4g
PiBUaGUgZmlsZSBjYW4gYmUgb2J0YWluZWQgdmlhDQo+ID4gPiA+IGh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLw0KPiA+ID4gPiANCj4g
PiA+ID4gSUVTRyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYQ0KPiA+ID4gPiANCmh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zL2Jh
bGxvdC8NCj4gPiA+ID4gDQo+ID4gPiA+IA0KPiA+ID4gPiBObyBJUFIgZGVjbGFyYXRpb25zIGhh
dmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+ID4gPiA+IA0KPiA+ID4g
PiANCj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gPiA+ID4gT0F1dGggbWFpbGluZyBsaXN0DQo+ID4gPiA+IE9BdXRoQGlldGYub3JnDQo+
ID4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGgNCj4gPiA+
IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gPiBP
QXV0aCBtYWlsaW5nIGxpc3QNCj4gPiA+IE9BdXRoQGlldGYub3JnDQo+ID4gPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoIA0K
--=_alternative 000EB9D648257AD4_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPk9oLCBCdXQgdGhlIGRlc2NyaXB0
aW9uIG9mIGFzc2VydGlvbg0KZ2VuZXJhdGlvbiBpbiB0aGUgZG9jdW1lbnQgc2hvdWxkIG5vdCBi
ZSBsaW1pdGVkIGJ5IGJlYXIgYXNzZXJ0aW9uLCByaWdodD88L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8
YnI+PHR0Pjxmb250IHNpemU9Mj5DaHVjayBNb3J0aW1vcmUgJmx0O2Ntb3J0aW1vcmVAc2FsZXNm
b3JjZS5jb20mZ3Q7DQrQtNPaIDIwMTItMTItMTQgMTA6MzQ6MTM6PGJyPg0KPGJyPg0KJmd0OyBZ
b3Ugd2FudCBhIGhvbGRlciBvZiBrZXkgcGF0dGVybi4gJm5ic3A7VGhlIGRyYWZ0IHRvdWNoZXMg
b24gaXQ8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7ICZuYnNwOyAmbmJzcDtUaGUgcHJvdG9jb2wgcGFyYW1ldGVycyBhbmQgcHJvY2Vz
c2luZyBydWxlcyBkZWZpbmVkDQppbiB0aGlzIGRvY3VtZW50PGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7YXJlIGludGVuZGVkIHRvIHN1cHBvcnQgYSBjbGllbnQgcHJlc2VudGluZyBhIGJlYXJlcg0K
YXNzZXJ0aW9uIHRvIGFuPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7YXV0aG9yaXphdGlvbiBzZXJ2
ZXIuICZuYnNwO1RoZSB1c2Ugb2YgaG9sZGVyLW9mLWtleQ0KYXNzZXJ0aW9ucyBhcmUgbm90PGJy
Pg0KJmd0OyAmbmJzcDsgJm5ic3A7cHJlY2x1ZGVkIGJ5IHRoaXMgZG9jdW1lbnQsIGJ1dCBhZGRp
dGlvbmFsIHByb3RvY29sIGRldGFpbHMNCndvdWxkPGJyPg0KJmd0OyAmbmJzcDsgJm5ic3A7bmVl
ZCB0byBiZSBzcGVjaWZpZWQuPGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9
Mj4mZ3Q7IDxicj4NCiZndDsgU28gLSBpZiB5b3Ugd2FudCB0aGlzLCB5b3Ugc2hvdWxkIHB1dCBm
b3J0aCBhIGhvbGRlciBvZiBrZXkgPGJyPg0KJmd0OyBwcm9maWxpbmcgb2YgdGhpcyBkcmFmdCBh
bmQgc2VlIGlmIHRoZXJlIGFyZSBhbnkgaXNzdWVzLiAmbmJzcDsgVGhlDQpvbmx5IDxicj4NCiZn
dDsgcHJvZmlsZXMgd2UgaGF2ZSB0aHVzIGZhciBhcmUgc2FtbCBhbmQgand0IGJlYXJlciBhc3Nl
cnRpb25zLiAmbmJzcDs8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJy
Pg0KJmd0OyA8YnI+DQomZ3Q7IC0gY21vcnQ8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6
ZT0yPiZndDsgPGJyPg0KJmd0OyBPbiBEZWMgMTMsIDIwMTIsIGF0IDY6MjcgUE0sICZxdW90O3po
b3Uuc3VqaW5nQHp0ZS5jb20uY24mcXVvdDsgJmx0O3pob3Uuc3VqaW5nQHp0ZS5jb20uY248YnI+
DQomZ3Q7ICZndDsgd3JvdGU6PGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9
Mj4mZ3Q7IDxicj4NCiZndDsgSSBhbSBub3Qgc3VyZSBpZiB0aGUgZm9sbG93aW5nIHVzZWNhc2Ug
Jm5ic3A7aHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLTxicj4NCiZndDsgYXJjaGl2ZS93ZWIvb2F1
dGgvY3VycmVudC9tc2cxMDIzMy5odG1sIDxicj4NCiZndDsgY291bGQgYmUgc3VwcG9ydGVkIGJ5
IGFzc2VydGlvbiBmcmFtZXdvcmujrCA8YnI+DQomZ3Q7IFdlIGhhdmUgc29tZSBkaXNjdXNzaW9u
IGluICZuYnNwOyA8YnI+DQomZ3Q7IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dl
Yi9vYXV0aC9jdXJyZW50L21zZzEwMjAzLmh0bWwgPGJyPg0KJmd0OyBodHRwOi8vd3d3LmlldGYu
b3JnL21haWwtYXJjaGl2ZS93ZWIvb2F1dGgvY3VycmVudC9tc2cxMDE5OC5odG1sIDxicj4NCiZn
dDsgPGJyPg0KJmd0OyBJbiBteSB1c2UgY2FzZSBvciBpbiBzb21lIG90aGVyIGNhc2VzLCBhc3Nl
cnRpb25zIGRvbid0IG5lZWQgPGJyPg0KJmd0OyBjb25maWRlbnRpYWwgcHJvdGVjdGlvbiwgPGJy
Pg0KJmd0OyBiYXNpY2FsbHkgU1RTIGRvbid0IGhhdmUgdG8gYXV0aGVudGljYXRlIGEgY2xpZW50
IGJlZm9yZSBpc3N1ZWluZw0KPGJyPg0KJmd0OyAmcXVvdDthc3NlcnRpb24mcXVvdDssIGlmIGl0
IGNvdWxkIGJlIGNhbGxlZCBhc3NlcnRpb24gaGVyZS4gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEV4
YW1wbGUsSSB0cnVzdCBteSBsYXl3ZXIsIEkgbWF5IGlzc3VlIGFuICZxdW90O2Fzc2VydGlvbiZx
dW90OyBzdGF0aW5nDQo8YnI+DQomZ3Q7IGRlbGVnYXRpb24gaW4gYWR2YW5jZSwgYW5kIHNlbmQg
dG8gdGhlIGxhd3llciB3aGVuIGl0IGlzIG5lZWRlZCwgPGJyPg0KJmd0OyBpdCBjb3VsZCBiZSBJ
IGdpdmUgdGhlIGFzc2VydGlvbiB0byBhIGZhbHNlIGxhd3llciwgYnV0IGl0IGRvZXMgbm90DQo8
YnI+DQomZ3Q7IG1hdHRlciwgYmVjYXVzZSB0aGUgbGF3eWVyIGhhcyB0byBwcm92ZSBoZSBrbm93
cyBzb21lIGNyZWRlbnRpYWwgPGJyPg0KJmd0OyBjb3JyZXNwb25kaW5nIHRvIGhpcyBJRCwgPGJy
Pg0KJmd0OyB3aG8gaXMgZGVsZWdhdGVkIHNvbWUgcmlnaHRzLiA8YnI+DQomZ3Q7IDxicj4NCiZn
dDsgSWYgYXNzZXJ0aW9uIGZyYW1ld29yayB3YW50IHRvIHN1cHBvcnQgdGhpcyB1c2UgY2FzZSwg
dGhlbiA8YnI+DQomZ3Q7IGdlbmVyYXRpb24gb2YgYXNzZXJ0aW9uIHNob3VsZCBiZSByZWxheGVk
LCA8YnI+DQomZ3Q7IG90aGVyd2lzZSBuZXcgd29yayBpcyByZXF1aXJlZCB0byBzdXBwb3J0IHRo
ZSB1c2UgY2FzZS4gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyBD
aHVjayBNb3J0aW1vcmUgJmx0O2Ntb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20mZ3Q7INC009ogMjAx
Mi0xMi0xNA0KMTA6MDg6MzQ6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgT24gRGVjIDEzLCAy
MDEyLCBhdCA0OjMwIFBNLCAmcXVvdDt6aG91LnN1amluZ0B6dGUuY29tLmNuJnF1b3Q7DQombHQ7
emhvdS48YnI+DQomZ3Q7IHN1amluZ0B6dGUuY29tLmNuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgd3Jv
dGU6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IEZyb20gdGhlIGxh
bmd1YWdlLCBJIGdvdCBhbiBpbXByZXNzaW9uIHRoYXQgYXNzZXJ0aW9uIGlzIG9ubHkNCjxicj4N
CiZndDsgJmd0OyBnZW5lcmF0ZWQgYnkgdG9rZW4gc2VydmljZSBhZnRlciBjbGllbnRzIHByZXNl
bnRpbmcgc29tZSBjcmVkZW50aWFscywNCjxicj4NCiZndDsgJmd0OyB0aGVyZSBhcmUgbWF5IGJl
IHNvbWUgY2FzZXMgdGhhdCAmcXVvdDthc3NlcnRpb24mcXVvdDsgZG9uJ3QNCm5lZWQgY2xpZW50
J3MgPGJyPg0KJmd0OyBjcmVkZW50aWFsLiA8YnI+DQomZ3Q7ICZndDsgZS5nLiwgUmVzb3VyY2Ug
b3duZXIgYXMgYSB0b2tlbiBzZXJ2aWNlICZuYnNwO2NvdWxkIGdlbmVyYXRlDQomcXVvdDthc3Nl
cnRpb24mcXVvdDsgPGJyPg0KJmd0OyAmZ3Q7IHRvIGEgY2xpZW50IGhlIHRydXN0cywgYnUgc2ln
bmluZyBhIHN0YXRlbWVudCB0aGF0ICZxdW90O1RoaXMNCmRlbGVnYXRpb24gPGJyPg0KJmd0OyAm
Z3Q7IGlzIGdpdmVuIHRvIGEgY2xpZW50IGNhbGxlZCBjbGluZXQtaWQgPGJyPg0KJmd0OyAmZ3Q7
IGZvciBkb2luZyBzb21ldGhpbmcgZm9yIG1lJnF1b3Q7LiA8YnI+DQomZ3Q7ICZndDsgPGJyPg0K
Jmd0OyAmZ3Q7IFNvIGhvdyBkb2VzIHRoZSBTVFMgdHJ1c3QgdGhlIGNsaWVudD8gJm5ic3A7IFBy
ZXN1bWFibHkgaWYgaXQNCmlzIHRydXN0ZWQgPGJyPg0KJmd0OyAmZ3Q7IGl0IGhhcyBzb21lIGxl
dmVsIG9mIGF1dGhlbnRpY2F0aW9uLCB5ZXM/IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZn
dDsgLWNtb3J0IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7
IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IENodWNrIE1v
cnRpbW9yZSAmbHQ7Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbSZndDsg0LTT2iAyMDEyLTEyLTE0
DQowMDozOTowMzo8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhlIGxhbmd1
YWdlIGlzIHNpbXBseSBtZWFudCB0byBoZWxwIGlsbHVzdHJhdGUgaG93IHRoZQ0KZnJhbWV3b3Jr
IDxicj4NCiZndDsgJmd0OyAmZ3Q7IG1pZ2h0IGJlIHVzZWQuICZuYnNwOyBIb3cgZG8geW91IHRo
aW5rIGl0IHdpbGwgcmVzdHJpY3QNCnVzYWdlPyAmbmJzcDsgSG93IDxicj4NCiZndDsgJmd0OyAm
Z3Q7IGNvdWxkIGl0IGJlIGltcHJvdmVkPyA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7
ICZndDsgJmd0OyAtY21vcnQgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgT24gRGVjIDEyLCAyMDEyLCBhdCAxMTowNCBQTSwgJmx0O3pob3Uuc3VqaW5nQHp0ZS5jb20u
Y24mZ3Q7DQp3cm90ZTogPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgSW4gJnF1b3Q7c2VjdGlvbiAzIDxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZuYnNwO1RoZSB0b2tlbiBzZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24gaXNzdWVyOyBpdHMg
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7cm9sZSBpcyB0byBmdWxmaWxsIHJlcXVlc3RzIGZy
b20gY2xpZW50cywgd2hpY2ggcHJlc2VudA0KdmFyaW91cyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAm
bmJzcDtjcmVkZW50aWFscywgYW5kIG1pbnQgYXNzZXJ0aW9ucyBhcyByZXF1ZXN0ZWQsIGZpbGwN
CnRoZW0gd2l0aCA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDthcHByb3ByaWF0ZSBpbmZvcm1h
dGlvbiwgYW5kIHNpZ24gdGhlbS4mcXVvdDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgQXMgSSB1bmRlcnN0YW5kLCBhbiBhc3Nl
cnRpb24gZ2VuZXJhdGVkIGJ5IGEgU1RTLCBpcyBkb25lDQpmbG9sbG93aW5nPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgdGhlc3Mgc3RlcHM6IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDEuIENsaWVudCBwcmVz
ZW50cyBjcmVkZW50aWFsIGFuZCByZXF1ZXN0cyBhbiBhc3NlcnRpb24NCjxicj4NCiZndDsgJmd0
OyAmZ3Q7IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFuZCBzZW5kcyB0byBDbGllbnQgPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgQ29ycmVjdD8gPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgVGhhdCBtYXkgcmVzdHJpY3QgdGhlIHVzZSBjYXNlcyB0aGF0IHRoaXMgYXNz
ZXJ0aW9uIGZyYW1ld29yaw0KPGJyPg0KJmd0OyAmZ3Q7IGNvdWxkIHN1cHBvcnQsIDxicj4NCiZn
dDsgJmd0OyAmZ3Q7IGlzIGl0IGEgbXVzdD8gPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgb2F1dGgtYm91bmNlc0BpZXRmLm9yZyDQtNPaIDIwMTItMTItMTEg
MDI6MzM6NTc6PGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8
YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3Qg
ZnJvbSB0aGUgV2ViIEF1dGhvcml6YXRpb24NClByb3RvY29sIFdHPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgJmd0OyAob2F1dGgpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6PGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgJmd0OyAtICdBc3NlcnRpb24gRnJhbWV3b3JrIGZvciBPQXV0aCAyLjAn
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJmx0O2RyYWZ0LWlldGYtb2F1dGgtYXNz
ZXJ0aW9ucy0wOC50eHQmZ3Q7IGFzDQpQcm9wb3NlZCBTdGFuZGFyZDxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBUaGUgSUVTRyBwbGFucyB0byBtYWtl
IGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLA0KYW5kIHNvbGljaXRzPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgJmd0OyBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNl
bmQgc3Vic3RhbnRpdmUNCmNvbW1lbnRzIHRvIHRoZTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsg
aWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5IDIwMTItMTItMjQuIEV4Y2VwdGlvbmFsbHks
DQo8YnI+DQomZ3Q7IGNvbW1lbnRzIG1heSBiZTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgc2Vu
dCB0byBpZXNnQGlldGYub3JnIGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UNCnJldGFp
biB0aGU8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBs
aW5lIHRvIGFsbG93IGF1dG9tYXRlZCBzb3J0aW5nLjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsg
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBBYnN0cmFjdDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZn
dDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZu
YnNwOyAmbmJzcDtUaGlzIHNwZWNpZmljYXRpb24gcHJvdmlkZXMgYSBmcmFtZXdvcmsNCmZvciB0
aGUgdXNlIG9mIGFzc2VydGlvbnM8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJz
cDt3aXRoIE9BdXRoIDIuMCBpbiB0aGUgZm9ybSBvZiBhIG5ldyBjbGllbnQNCmF1dGhlbnRpY2F0
aW9uIG1lY2hhbmlzbTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2FuZCBh
IG5ldyBhdXRob3JpemF0aW9uIGdyYW50IHR5cGUuICZuYnNwO01lY2hhbmlzbXMNCmFyZSBzcGVj
aWZpZWQgZm9yPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7dHJhbnNwb3J0
aW5nIGFzc2VydGlvbnMgZHVyaW5nIGludGVyYWN0aW9ucw0Kd2l0aCBhIHRva2VuIGVuZHBvaW50
LCBhczxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3dlbGwgYXMgZ2VuZXJh
bCBwcm9jZXNzaW5nIHJ1bGVzLjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7VGhlIGludGVudCBvZiB0aGlzIHNwZWNpZmljYXRp
b24gaXMgdG8NCnByb3ZpZGUgYSBjb21tb24gZnJhbWV3b3JrIGZvcjxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZndDsgJm5ic3A7ICZuYnNwO09BdXRoIDIuMCB0byBpbnRlcndvcmsgd2l0aCBvdGhlciBp
ZGVudGl0eQ0Kc3lzdGVtcyB1c2luZyBhc3NlcnRpb25zLDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZn
dDsgJm5ic3A7ICZuYnNwO2FuZCB0byBwcm92aWRlIGFsdGVybmF0aXZlIGNsaWVudCBhdXRoZW50
aWNhdGlvbg0KbWVjaGFuaXNtcy48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO05vdGUgdGhhdCB0aGlzIHNwZWNpZmljYXRpb24g
b25seSBkZWZpbmVzDQphYnN0cmFjdCBtZXNzYWdlIGZsb3dzIGFuZDxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZndDsgJm5ic3A7ICZuYnNwO3Byb2Nlc3NpbmcgcnVsZXMuICZuYnNwO0luIG9yZGVyIHRv
IGJlDQppbXBsZW1lbnRhYmxlLCBjb21wYW5pb248YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZu
YnNwOyAmbmJzcDtzcGVjaWZpY2F0aW9ucyBhcmUgbmVjZXNzYXJ5IHRvIHByb3ZpZGUNCnRoZSBj
b3JyZXNwb25kaW5nIGNvbmNyZXRlPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5i
c3A7aW5zdGFudGlhdGlvbnMuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZn
dDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5l
ZCB2aWE8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZn
dDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNr
ZWQgdmlhPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy9iYWxsb3QvPGJyPg0KJmd0OyAmZ3Q7
ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7
ICZndDsgTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5IG9u
DQp0aGlzIEktRC48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7
ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgT0F1dGggbWFp
bGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBPQXV0aEBpZXRmLm9yZzxicj4NCiZn
dDsgJmd0OyAmZ3Q7ICZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9v
YXV0aDxicj4NCiZndDsgJmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fPGJyPg0KJmd0OyAmZ3Q7ICZndDsgT0F1dGggbWFpbGluZyBsaXN0PGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgT0F1dGhAaWV0Zi5vcmc8YnI+DQomZ3Q7ICZndDsgJmd0OyBodHRw
czovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL29hdXRoIDwvZm9udD48L3R0Pg0K
--=_alternative 000EB9D648257AD4_=--

From cmortimore@salesforce.com  Thu Dec 13 18:44:08 2012
Return-Path: <cmortimore@salesforce.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5146921F8B11; Thu, 13 Dec 2012 18:44:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.008
X-Spam-Level: 
X-Spam-Status: No, score=-6.008 tagged_above=-999 required=5 tests=[AWL=-0.432, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, J_CHICKENPOX_71=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B3HBadGCCl-U; Thu, 13 Dec 2012 18:44:07 -0800 (PST)
Received: from exprod8og120.obsmtp.com (exprod8og120.obsmtp.com [64.18.3.40]) by ietfa.amsl.com (Postfix) with SMTP id E2ED821F8AF1; Thu, 13 Dec 2012 18:44:06 -0800 (PST)
Received: from exsfm-hub3.internal.salesforce.com ([204.14.239.238]) by exprod8ob120.postini.com ([64.18.7.12]) with SMTP ID DSNKUMqSdqYutAjUgQ2xPzWnQ85OESLVrfk1@postini.com; Thu, 13 Dec 2012 18:44:07 PST
Received: from EXSFM-MB03.internal.salesforce.com ([10.1.127.58]) by exsfm-hub3.internal.salesforce.com ([10.1.127.7]) with mapi; Thu, 13 Dec 2012 18:44:06 -0800
From: Chuck Mortimore <cmortimore@salesforce.com>
To: "zhou.sujing@zte.com.cn" <zhou.sujing@zte.com.cn>
Date: Thu, 13 Dec 2012 18:44:05 -0800
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
Thread-Topic: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
Thread-Index: Ac3ZpOJpkTur59oCT1mDawjYT6PI8w==
Message-ID: <D0292BED-C6D8-4B56-9BBE-6C280F38BC42@salesforce.com>
References: <OFB954FF83.FB35CC6D-ON48257AD4.000E8DAF-48257AD4.000EB9D8@zte.com.cn>
In-Reply-To: <OFB954FF83.FB35CC6D-ON48257AD4.000E8DAF-48257AD4.000EB9D8@zte.com.cn>
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_D0292BEDC6D84B569BBE6C280F38BC42salesforcecom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:48 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 02:44:08 -0000

--_000_D0292BEDC6D84B569BBE6C280F38BC42salesforcecom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Q29ycmVjdC4gICBUaGF0IHNhaWQgbm8gb25lIGhhcyB5ZXQgcHJvZmlsZWQgaXQgZm9yIGhvbGRl
ciBvZiBrZXkNCg0KLSBjbW9ydA0KDQpPbiBEZWMgMTMsIDIwMTIsIGF0IDY6MzkgUE0sICJ6aG91
LnN1amluZ0B6dGUuY29tLmNuPG1haWx0bzp6aG91LnN1amluZ0B6dGUuY29tLmNuPiIgPHpob3Uu
c3VqaW5nQHp0ZS5jb20uY248bWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24+PiB3cm90ZToN
Cg0KDQpPaCwgQnV0IHRoZSBkZXNjcmlwdGlvbiBvZiBhc3NlcnRpb24gZ2VuZXJhdGlvbiBpbiB0
aGUgZG9jdW1lbnQgc2hvdWxkIG5vdCBiZSBsaW1pdGVkIGJ5IGJlYXIgYXNzZXJ0aW9uLCByaWdo
dD8NCg0KDQpDaHVjayBNb3J0aW1vcmUgPGNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb208bWFpbHRv
OmNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb20+PiDlhpnkuo4gMjAxMi0xMi0xNCAxMDozNDoxMzoN
Cg0KPiBZb3Ugd2FudCBhIGhvbGRlciBvZiBrZXkgcGF0dGVybi4gIFRoZSBkcmFmdCB0b3VjaGVz
IG9uIGl0DQo+DQo+DQo+ICAgIFRoZSBwcm90b2NvbCBwYXJhbWV0ZXJzIGFuZCBwcm9jZXNzaW5n
IHJ1bGVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudA0KPiAgICBhcmUgaW50ZW5kZWQgdG8gc3Vw
cG9ydCBhIGNsaWVudCBwcmVzZW50aW5nIGEgYmVhcmVyIGFzc2VydGlvbiB0byBhbg0KPiAgICBh
dXRob3JpemF0aW9uIHNlcnZlci4gIFRoZSB1c2Ugb2YgaG9sZGVyLW9mLWtleSBhc3NlcnRpb25z
IGFyZSBub3QNCj4gICAgcHJlY2x1ZGVkIGJ5IHRoaXMgZG9jdW1lbnQsIGJ1dCBhZGRpdGlvbmFs
IHByb3RvY29sIGRldGFpbHMgd291bGQNCj4gICAgbmVlZCB0byBiZSBzcGVjaWZpZWQuDQoNCj4N
Cj4gU28gLSBpZiB5b3Ugd2FudCB0aGlzLCB5b3Ugc2hvdWxkIHB1dCBmb3J0aCBhIGhvbGRlciBv
ZiBrZXkNCj4gcHJvZmlsaW5nIG9mIHRoaXMgZHJhZnQgYW5kIHNlZSBpZiB0aGVyZSBhcmUgYW55
IGlzc3Vlcy4gICBUaGUgb25seQ0KPiBwcm9maWxlcyB3ZSBoYXZlIHRodXMgZmFyIGFyZSBzYW1s
IGFuZCBqd3QgYmVhcmVyIGFzc2VydGlvbnMuDQo+DQo+DQo+IC0gY21vcnQNCj4NCj4gT24gRGVj
IDEzLCAyMDEyLCBhdCA2OjI3IFBNLCAiemhvdS5zdWppbmdAenRlLmNvbS5jbjxtYWlsdG86emhv
dS5zdWppbmdAenRlLmNvbS5jbj4iIDx6aG91LnN1amluZ0B6dGUuY29tLmNuPG1haWx0bzp6aG91
LnN1amluZ0B6dGUuY29tLmNuPg0KPiA+IHdyb3RlOg0KDQo+DQo+IEkgYW0gbm90IHN1cmUgaWYg
dGhlIGZvbGxvd2luZyB1c2VjYXNlICBodHRwOi8vd3d3LmlldGYub3JnL21haWwtDQo+IGFyY2hp
dmUvd2ViL29hdXRoL2N1cnJlbnQvbXNnMTAyMzMuaHRtbA0KPiBjb3VsZCBiZSBzdXBwb3J0ZWQg
YnkgYXNzZXJ0aW9uIGZyYW1ld29ya++8jA0KPiBXZSBoYXZlIHNvbWUgZGlzY3Vzc2lvbiBpbg0K
PiBodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvb2F1dGgvY3VycmVudC9tc2cx
MDIwMy5odG1sDQo+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9j
dXJyZW50L21zZzEwMTk4Lmh0bWwNCj4NCj4gSW4gbXkgdXNlIGNhc2Ugb3IgaW4gc29tZSBvdGhl
ciBjYXNlcywgYXNzZXJ0aW9ucyBkb24ndCBuZWVkDQo+IGNvbmZpZGVudGlhbCBwcm90ZWN0aW9u
LA0KPiBiYXNpY2FsbHkgU1RTIGRvbid0IGhhdmUgdG8gYXV0aGVudGljYXRlIGEgY2xpZW50IGJl
Zm9yZSBpc3N1ZWluZw0KPiAiYXNzZXJ0aW9uIiwgaWYgaXQgY291bGQgYmUgY2FsbGVkIGFzc2Vy
dGlvbiBoZXJlLg0KPg0KPiBFeGFtcGxlLEkgdHJ1c3QgbXkgbGF5d2VyLCBJIG1heSBpc3N1ZSBh
biAiYXNzZXJ0aW9uIiBzdGF0aW5nDQo+IGRlbGVnYXRpb24gaW4gYWR2YW5jZSwgYW5kIHNlbmQg
dG8gdGhlIGxhd3llciB3aGVuIGl0IGlzIG5lZWRlZCwNCj4gaXQgY291bGQgYmUgSSBnaXZlIHRo
ZSBhc3NlcnRpb24gdG8gYSBmYWxzZSBsYXd5ZXIsIGJ1dCBpdCBkb2VzIG5vdA0KPiBtYXR0ZXIs
IGJlY2F1c2UgdGhlIGxhd3llciBoYXMgdG8gcHJvdmUgaGUga25vd3Mgc29tZSBjcmVkZW50aWFs
DQo+IGNvcnJlc3BvbmRpbmcgdG8gaGlzIElELA0KPiB3aG8gaXMgZGVsZWdhdGVkIHNvbWUgcmln
aHRzLg0KPg0KPiBJZiBhc3NlcnRpb24gZnJhbWV3b3JrIHdhbnQgdG8gc3VwcG9ydCB0aGlzIHVz
ZSBjYXNlLCB0aGVuDQo+IGdlbmVyYXRpb24gb2YgYXNzZXJ0aW9uIHNob3VsZCBiZSByZWxheGVk
LA0KPiBvdGhlcndpc2UgbmV3IHdvcmsgaXMgcmVxdWlyZWQgdG8gc3VwcG9ydCB0aGUgdXNlIGNh
c2UuDQo+DQo+DQo+DQo+IENodWNrIE1vcnRpbW9yZSA8Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNv
bTxtYWlsdG86Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbT4+IOWGmeS6jiAyMDEyLTEyLTE0IDEw
OjA4OjM0Og0KPg0KPiA+IE9uIERlYyAxMywgMjAxMiwgYXQgNDozMCBQTSwgInpob3Uuc3VqaW5n
QHp0ZS5jb20uY248bWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24+IiA8emhvdS4NCj4gc3Vq
aW5nQHp0ZS5jb20uY248bWFpbHRvOnN1amluZ0B6dGUuY29tLmNuPg0KPiA+ID4gd3JvdGU6DQo+
DQo+ID4NCj4gPiBGcm9tIHRoZSBsYW5ndWFnZSwgSSBnb3QgYW4gaW1wcmVzc2lvbiB0aGF0IGFz
c2VydGlvbiBpcyBvbmx5DQo+ID4gZ2VuZXJhdGVkIGJ5IHRva2VuIHNlcnZpY2UgYWZ0ZXIgY2xp
ZW50cyBwcmVzZW50aW5nIHNvbWUgY3JlZGVudGlhbHMsDQo+ID4gdGhlcmUgYXJlIG1heSBiZSBz
b21lIGNhc2VzIHRoYXQgImFzc2VydGlvbiIgZG9uJ3QgbmVlZCBjbGllbnQncw0KPiBjcmVkZW50
aWFsLg0KPiA+IGUuZy4sIFJlc291cmNlIG93bmVyIGFzIGEgdG9rZW4gc2VydmljZSAgY291bGQg
Z2VuZXJhdGUgImFzc2VydGlvbiINCj4gPiB0byBhIGNsaWVudCBoZSB0cnVzdHMsIGJ1IHNpZ25p
bmcgYSBzdGF0ZW1lbnQgdGhhdCAiVGhpcyBkZWxlZ2F0aW9uDQo+ID4gaXMgZ2l2ZW4gdG8gYSBj
bGllbnQgY2FsbGVkIGNsaW5ldC1pZA0KPiA+IGZvciBkb2luZyBzb21ldGhpbmcgZm9yIG1lIi4N
Cj4gPg0KPiA+IFNvIGhvdyBkb2VzIHRoZSBTVFMgdHJ1c3QgdGhlIGNsaWVudD8gICBQcmVzdW1h
Ymx5IGlmIGl0IGlzIHRydXN0ZWQNCj4gPiBpdCBoYXMgc29tZSBsZXZlbCBvZiBhdXRoZW50aWNh
dGlvbiwgeWVzPw0KPiA+DQo+ID4gLWNtb3J0DQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0KPiA+
IENodWNrIE1vcnRpbW9yZSA8Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbTxtYWlsdG86Y21vcnRp
bW9yZUBzYWxlc2ZvcmNlLmNvbT4+IOWGmeS6jiAyMDEyLTEyLTE0IDAwOjM5OjAzOg0KPiA+DQo+
ID4gPiBUaGUgbGFuZ3VhZ2UgaXMgc2ltcGx5IG1lYW50IHRvIGhlbHAgaWxsdXN0cmF0ZSBob3cg
dGhlIGZyYW1ld29yaw0KPiA+ID4gbWlnaHQgYmUgdXNlZC4gICBIb3cgZG8geW91IHRoaW5rIGl0
IHdpbGwgcmVzdHJpY3QgdXNhZ2U/ICAgSG93DQo+ID4gPiBjb3VsZCBpdCBiZSBpbXByb3ZlZD8N
Cj4gPiA+DQo+ID4gPiAtY21vcnQNCj4gPiA+DQo+ID4gPiBPbiBEZWMgMTIsIDIwMTIsIGF0IDEx
OjA0IFBNLCA8emhvdS5zdWppbmdAenRlLmNvbS5jbjxtYWlsdG86emhvdS5zdWppbmdAenRlLmNv
bS5jbj4+IHdyb3RlOg0KPiA+ID4NCj4gPiA+DQo+ID4gPiBJbiAic2VjdGlvbiAzDQo+ID4gPiAg
VGhlIHRva2VuIHNlcnZpY2UgaXMgdGhlIGFzc2VydGlvbiBpc3N1ZXI7IGl0cw0KPiA+ID4gIHJv
bGUgaXMgdG8gZnVsZmlsbCByZXF1ZXN0cyBmcm9tIGNsaWVudHMsIHdoaWNoIHByZXNlbnQgdmFy
aW91cw0KPiA+ID4gIGNyZWRlbnRpYWxzLCBhbmQgbWludCBhc3NlcnRpb25zIGFzIHJlcXVlc3Rl
ZCwgZmlsbCB0aGVtIHdpdGgNCj4gPiA+ICBhcHByb3ByaWF0ZSBpbmZvcm1hdGlvbiwgYW5kIHNp
Z24gdGhlbS4iDQo+ID4gPg0KPiA+ID4NCj4gPiA+IEFzIEkgdW5kZXJzdGFuZCwgYW4gYXNzZXJ0
aW9uIGdlbmVyYXRlZCBieSBhIFNUUywgaXMgZG9uZSBmbG9sbG93aW5nDQo+ID4gPiB0aGVzcyBz
dGVwczoNCj4gPiA+IDEuIENsaWVudCBwcmVzZW50cyBjcmVkZW50aWFsIGFuZCByZXF1ZXN0cyBh
biBhc3NlcnRpb24NCj4gPiA+IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFuZCBzZW5kcyB0
byBDbGllbnQNCj4gPiA+IENvcnJlY3Q/DQo+ID4gPg0KPiA+ID4gVGhhdCBtYXkgcmVzdHJpY3Qg
dGhlIHVzZSBjYXNlcyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yaw0KPiA+IGNvdWxkIHN1
cHBvcnQsDQo+ID4gPiBpcyBpdCBhIG11c3Q/DQo+ID4gPg0KPiA+ID4NCj4gPiA+DQo+ID4gPg0K
PiA+ID4gb2F1dGgtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86b2F1dGgtYm91bmNlc0BpZXRmLm9y
Zz4g5YaZ5LqOIDIwMTItMTItMTEgMDI6MzM6NTc6DQo+ID4gPg0KPiA+ID4gPg0KPiA+ID4gPiBU
aGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIFdlYiBBdXRob3JpemF0aW9u
IFByb3RvY29sIFdHDQo+ID4gPiA+IChvYXV0aCkgdG8gY29uc2lkZXIgdGhlIGZvbGxvd2luZyBk
b2N1bWVudDoNCj4gPiA+ID4gLSAnQXNzZXJ0aW9uIEZyYW1ld29yayBmb3IgT0F1dGggMi4wJw0K
PiA+ID4gPiAgIDxkcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMtMDgudHh0PiBhcyBQcm9wb3Nl
ZCBTdGFuZGFyZA0KPiA+ID4gPg0KPiA+ID4gPiBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVj
aXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQgc29saWNpdHMNCj4gPiA+ID4gZmluYWwg
Y29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRz
IHRvIHRoZQ0KPiA+ID4gPiBpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPiBtYWls
aW5nIGxpc3RzIGJ5IDIwMTItMTItMjQuIEV4Y2VwdGlvbmFsbHksDQo+IGNvbW1lbnRzIG1heSBi
ZQ0KPiA+ID4gPiBzZW50IHRvIGllc2dAaWV0Zi5vcmc8bWFpbHRvOmllc2dAaWV0Zi5vcmc+IGlu
c3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2UgcmV0YWluIHRoZQ0KPiA+ID4gPiBiZWdpbm5p
bmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4gPiA+
ID4NCj4gPiA+ID4gQWJzdHJhY3QNCj4gPiA+ID4NCj4gPiA+ID4NCj4gPiA+ID4gICAgVGhpcyBz
cGVjaWZpY2F0aW9uIHByb3ZpZGVzIGEgZnJhbWV3b3JrIGZvciB0aGUgdXNlIG9mIGFzc2VydGlv
bnMNCj4gPiA+ID4gICAgd2l0aCBPQXV0aCAyLjAgaW4gdGhlIGZvcm0gb2YgYSBuZXcgY2xpZW50
IGF1dGhlbnRpY2F0aW9uIG1lY2hhbmlzbQ0KPiA+ID4gPiAgICBhbmQgYSBuZXcgYXV0aG9yaXph
dGlvbiBncmFudCB0eXBlLiAgTWVjaGFuaXNtcyBhcmUgc3BlY2lmaWVkIGZvcg0KPiA+ID4gPiAg
ICB0cmFuc3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zIHdpdGggYSB0b2tl
biBlbmRwb2ludCwgYXMNCj4gPiA+ID4gICAgd2VsbCBhcyBnZW5lcmFsIHByb2Nlc3NpbmcgcnVs
ZXMuDQo+ID4gPiA+DQo+ID4gPiA+ICAgIFRoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9u
IGlzIHRvIHByb3ZpZGUgYSBjb21tb24gZnJhbWV3b3JrIGZvcg0KPiA+ID4gPiAgICBPQXV0aCAy
LjAgdG8gaW50ZXJ3b3JrIHdpdGggb3RoZXIgaWRlbnRpdHkgc3lzdGVtcyB1c2luZyBhc3NlcnRp
b25zLA0KPiA+ID4gPiAgICBhbmQgdG8gcHJvdmlkZSBhbHRlcm5hdGl2ZSBjbGllbnQgYXV0aGVu
dGljYXRpb24gbWVjaGFuaXNtcy4NCj4gPiA+ID4NCj4gPiA+ID4gICAgTm90ZSB0aGF0IHRoaXMg
c3BlY2lmaWNhdGlvbiBvbmx5IGRlZmluZXMgYWJzdHJhY3QgbWVzc2FnZSBmbG93cyBhbmQNCj4g
PiA+ID4gICAgcHJvY2Vzc2luZyBydWxlcy4gIEluIG9yZGVyIHRvIGJlIGltcGxlbWVudGFibGUs
IGNvbXBhbmlvbg0KPiA+ID4gPiAgICBzcGVjaWZpY2F0aW9ucyBhcmUgbmVjZXNzYXJ5IHRvIHBy
b3ZpZGUgdGhlIGNvcnJlc3BvbmRpbmcgY29uY3JldGUNCj4gPiA+ID4gICAgaW5zdGFudGlhdGlv
bnMuDQo+ID4gPiA+DQo+ID4gPiA+DQo+ID4gPiA+DQo+ID4gPiA+DQo+ID4gPiA+IFRoZSBmaWxl
IGNhbiBiZSBvYnRhaW5lZCB2aWENCj4gPiA+ID4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMvDQo+ID4gPiA+DQo+ID4gPiA+IElFU0cg
ZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4gPiA+ID4gaHR0cDovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFzc2VydGlvbnMvYmFsbG90Lw0KPiA+ID4g
Pg0KPiA+ID4gPg0KPiA+ID4gPiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0
ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+ID4gPiA+DQo+ID4gPiA+DQo+ID4gPiA+IF9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gPiA+IE9BdXRo
IG1haWxpbmcgbGlzdA0KPiA+ID4gPiBPQXV0aEBpZXRmLm9yZzxtYWlsdG86T0F1dGhAaWV0Zi5v
cmc+DQo+ID4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGgN
Cj4gPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4gPiBPQXV0aCBtYWlsaW5nIGxpc3QNCj4gPiA+IE9BdXRoQGlldGYub3JnPG1haWx0bzpPQXV0
aEBpZXRmLm9yZz4NCj4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
b2F1dGgNCg==

--_000_D0292BEDC6D84B569BBE6C280F38BC42salesforcecom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PC9oZWFkPjxib2R5IGJnY29sb3I9IiNGRkZGRkYiPjxkaXY+Q29ycmVjdC4g
Jm5ic3A7IFRoYXQgc2FpZCBubyBvbmUgaGFzIHlldCBwcm9maWxlZCBpdCBmb3IgaG9sZGVyIG9m
IGtleTxicj48YnI+LSBjbW9ydDwvZGl2PjxkaXY+PGJyPk9uIERlYyAxMywgMjAxMiwgYXQgNjoz
OSBQTSwgIjxhIGhyZWY9Im1haWx0bzp6aG91LnN1amluZ0B6dGUuY29tLmNuIj56aG91LnN1amlu
Z0B6dGUuY29tLmNuPC9hPiIgJmx0OzxhIGhyZWY9Im1haWx0bzp6aG91LnN1amluZ0B6dGUuY29t
LmNuIj56aG91LnN1amluZ0B6dGUuY29tLmNuPC9hPiZndDsgd3JvdGU6PGJyPjxicj48L2Rpdj48
ZGl2PjwvZGl2PjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxkaXY+DQo8YnI+PGZvbnQgc2l6ZT0i
MiIgZmFjZT0ic2Fucy1zZXJpZiI+T2gsIEJ1dCB0aGUgZGVzY3JpcHRpb24gb2YgYXNzZXJ0aW9u
DQpnZW5lcmF0aW9uIGluIHRoZSBkb2N1bWVudCBzaG91bGQgbm90IGJlIGxpbWl0ZWQgYnkgYmVh
ciBhc3NlcnRpb24sIHJpZ2h0PzwvZm9udD4NCjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6
ZT0iMiI+Q2h1Y2sgTW9ydGltb3JlICZsdDs8YSBocmVmPSJtYWlsdG86Y21vcnRpbW9yZUBzYWxl
c2ZvcmNlLmNvbSI+Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbTwvYT4mZ3Q7DQrlhpnkuo4gMjAx
Mi0xMi0xNCAxMDozNDoxMzo8YnI+DQo8YnI+DQomZ3Q7IFlvdSB3YW50IGEgaG9sZGVyIG9mIGtl
eSBwYXR0ZXJuLiAmbmJzcDtUaGUgZHJhZnQgdG91Y2hlcyBvbiBpdDwvZm9udD48L3R0Pg0KPGJy
Pjx0dD48Zm9udCBzaXplPSIyIj4mZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyAmbmJzcDsgJm5i
c3A7VGhlIHByb3RvY29sIHBhcmFtZXRlcnMgYW5kIHByb2Nlc3NpbmcgcnVsZXMgZGVmaW5lZA0K
aW4gdGhpcyBkb2N1bWVudDxicj4NCiZndDsgJm5ic3A7ICZuYnNwO2FyZSBpbnRlbmRlZCB0byBz
dXBwb3J0IGEgY2xpZW50IHByZXNlbnRpbmcgYSBiZWFyZXINCmFzc2VydGlvbiB0byBhbjxicj4N
CiZndDsgJm5ic3A7ICZuYnNwO2F1dGhvcml6YXRpb24gc2VydmVyLiAmbmJzcDtUaGUgdXNlIG9m
IGhvbGRlci1vZi1rZXkNCmFzc2VydGlvbnMgYXJlIG5vdDxicj4NCiZndDsgJm5ic3A7ICZuYnNw
O3ByZWNsdWRlZCBieSB0aGlzIGRvY3VtZW50LCBidXQgYWRkaXRpb25hbCBwcm90b2NvbCBkZXRh
aWxzDQp3b3VsZDxicj4NCiZndDsgJm5ic3A7ICZuYnNwO25lZWQgdG8gYmUgc3BlY2lmaWVkLjxi
cj4NCjwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPSIyIj4mZ3Q7IDxicj4NCiZndDsg
U28gLSBpZiB5b3Ugd2FudCB0aGlzLCB5b3Ugc2hvdWxkIHB1dCBmb3J0aCBhIGhvbGRlciBvZiBr
ZXkgPGJyPg0KJmd0OyBwcm9maWxpbmcgb2YgdGhpcyBkcmFmdCBhbmQgc2VlIGlmIHRoZXJlIGFy
ZSBhbnkgaXNzdWVzLiAmbmJzcDsgVGhlDQpvbmx5IDxicj4NCiZndDsgcHJvZmlsZXMgd2UgaGF2
ZSB0aHVzIGZhciBhcmUgc2FtbCBhbmQgand0IGJlYXJlciBhc3NlcnRpb25zLiAmbmJzcDs8L2Zv
bnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0iMiI+Jmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZn
dDsgLSBjbW9ydDwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9udCBzaXplPSIyIj4mZ3Q7IDxicj4N
CiZndDsgT24gRGVjIDEzLCAyMDEyLCBhdCA2OjI3IFBNLCAiPGEgaHJlZj0ibWFpbHRvOnpob3Uu
c3VqaW5nQHp0ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248L2E+IiAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248
L2E+PGJyPg0KJmd0OyAmZ3Q7IHdyb3RlOjxicj4NCjwvZm9udD48L3R0Pg0KPGJyPjx0dD48Zm9u
dCBzaXplPSIyIj4mZ3Q7IDxicj4NCiZndDsgSSBhbSBub3Qgc3VyZSBpZiB0aGUgZm9sbG93aW5n
IHVzZWNhc2UgJm5ic3A7PGEgaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLSI+aHR0cDov
L3d3dy5pZXRmLm9yZy9tYWlsLTwvYT48YnI+DQomZ3Q7IGFyY2hpdmUvd2ViL29hdXRoL2N1cnJl
bnQvbXNnMTAyMzMuaHRtbCA8YnI+DQomZ3Q7IGNvdWxkIGJlIHN1cHBvcnRlZCBieSBhc3NlcnRp
b24gZnJhbWV3b3Jr77yMIDxicj4NCiZndDsgV2UgaGF2ZSBzb21lIGRpc2N1c3Npb24gaW4gJm5i
c3A7IDxicj4NCiZndDsgPGEgaHJlZj0iaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUv
d2ViL29hdXRoL2N1cnJlbnQvbXNnMTAyMDMuaHRtbCI+aHR0cDovL3d3dy5pZXRmLm9yZy9tYWls
LWFyY2hpdmUvd2ViL29hdXRoL2N1cnJlbnQvbXNnMTAyMDMuaHRtbDwvYT4gPGJyPg0KJmd0OyA8
YSBocmVmPSJodHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvb2F1dGgvY3VycmVu
dC9tc2cxMDE5OC5odG1sIj5odHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvb2F1
dGgvY3VycmVudC9tc2cxMDE5OC5odG1sPC9hPiA8YnI+DQomZ3Q7IDxicj4NCiZndDsgSW4gbXkg
dXNlIGNhc2Ugb3IgaW4gc29tZSBvdGhlciBjYXNlcywgYXNzZXJ0aW9ucyBkb24ndCBuZWVkIDxi
cj4NCiZndDsgY29uZmlkZW50aWFsIHByb3RlY3Rpb24sIDxicj4NCiZndDsgYmFzaWNhbGx5IFNU
UyBkb24ndCBoYXZlIHRvIGF1dGhlbnRpY2F0ZSBhIGNsaWVudCBiZWZvcmUgaXNzdWVpbmcNCjxi
cj4NCiZndDsgImFzc2VydGlvbiIsIGlmIGl0IGNvdWxkIGJlIGNhbGxlZCBhc3NlcnRpb24gaGVy
ZS4gPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IEV4YW1wbGUsSSB0cnVzdCBteSBsYXl3ZXIsIEkgbWF5
IGlzc3VlIGFuICJhc3NlcnRpb24iIHN0YXRpbmcNCjxicj4NCiZndDsgZGVsZWdhdGlvbiBpbiBh
ZHZhbmNlLCBhbmQgc2VuZCB0byB0aGUgbGF3eWVyIHdoZW4gaXQgaXMgbmVlZGVkLCA8YnI+DQom
Z3Q7IGl0IGNvdWxkIGJlIEkgZ2l2ZSB0aGUgYXNzZXJ0aW9uIHRvIGEgZmFsc2UgbGF3eWVyLCBi
dXQgaXQgZG9lcyBub3QNCjxicj4NCiZndDsgbWF0dGVyLCBiZWNhdXNlIHRoZSBsYXd5ZXIgaGFz
IHRvIHByb3ZlIGhlIGtub3dzIHNvbWUgY3JlZGVudGlhbCA8YnI+DQomZ3Q7IGNvcnJlc3BvbmRp
bmcgdG8gaGlzIElELCA8YnI+DQomZ3Q7IHdobyBpcyBkZWxlZ2F0ZWQgc29tZSByaWdodHMuIDxi
cj4NCiZndDsgPGJyPg0KJmd0OyBJZiBhc3NlcnRpb24gZnJhbWV3b3JrIHdhbnQgdG8gc3VwcG9y
dCB0aGlzIHVzZSBjYXNlLCB0aGVuIDxicj4NCiZndDsgZ2VuZXJhdGlvbiBvZiBhc3NlcnRpb24g
c2hvdWxkIGJlIHJlbGF4ZWQsIDxicj4NCiZndDsgb3RoZXJ3aXNlIG5ldyB3b3JrIGlzIHJlcXVp
cmVkIHRvIHN1cHBvcnQgdGhlIHVzZSBjYXNlLiA8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IENodWNrIE1vcnRpbW9yZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmNtb3J0
aW1vcmVAc2FsZXNmb3JjZS5jb20iPmNtb3J0aW1vcmVAc2FsZXNmb3JjZS5jb208L2E+Jmd0OyDl
hpnkuo4gMjAxMi0xMi0xNA0KMTA6MDg6MzQ6PGJyPg0KJmd0OyA8YnI+DQomZ3Q7ICZndDsgT24g
RGVjIDEzLCAyMDEyLCBhdCA0OjMwIFBNLCAiPGEgaHJlZj0ibWFpbHRvOnpob3Uuc3VqaW5nQHp0
ZS5jb20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248L2E+Ig0KJmx0O3pob3UuPGJyPg0KJmd0
OyA8YSBocmVmPSJtYWlsdG86c3VqaW5nQHp0ZS5jb20uY24iPnN1amluZ0B6dGUuY29tLmNuPC9h
Pjxicj4NCiZndDsgJmd0OyAmZ3Q7IHdyb3RlOjxicj4NCiZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxi
cj4NCiZndDsgJmd0OyBGcm9tIHRoZSBsYW5ndWFnZSwgSSBnb3QgYW4gaW1wcmVzc2lvbiB0aGF0
IGFzc2VydGlvbiBpcyBvbmx5DQo8YnI+DQomZ3Q7ICZndDsgZ2VuZXJhdGVkIGJ5IHRva2VuIHNl
cnZpY2UgYWZ0ZXIgY2xpZW50cyBwcmVzZW50aW5nIHNvbWUgY3JlZGVudGlhbHMsDQo8YnI+DQom
Z3Q7ICZndDsgdGhlcmUgYXJlIG1heSBiZSBzb21lIGNhc2VzIHRoYXQgImFzc2VydGlvbiIgZG9u
J3QNCm5lZWQgY2xpZW50J3MgPGJyPg0KJmd0OyBjcmVkZW50aWFsLiA8YnI+DQomZ3Q7ICZndDsg
ZS5nLiwgUmVzb3VyY2Ugb3duZXIgYXMgYSB0b2tlbiBzZXJ2aWNlICZuYnNwO2NvdWxkIGdlbmVy
YXRlDQoiYXNzZXJ0aW9uIiA8YnI+DQomZ3Q7ICZndDsgdG8gYSBjbGllbnQgaGUgdHJ1c3RzLCBi
dSBzaWduaW5nIGEgc3RhdGVtZW50IHRoYXQgIlRoaXMNCmRlbGVnYXRpb24gPGJyPg0KJmd0OyAm
Z3Q7IGlzIGdpdmVuIHRvIGEgY2xpZW50IGNhbGxlZCBjbGluZXQtaWQgPGJyPg0KJmd0OyAmZ3Q7
IGZvciBkb2luZyBzb21ldGhpbmcgZm9yIG1lIi4gPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyBTbyBob3cgZG9lcyB0aGUgU1RTIHRydXN0IHRoZSBjbGllbnQ/ICZuYnNwOyBQcmVzdW1h
Ymx5IGlmIGl0DQppcyB0cnVzdGVkIDxicj4NCiZndDsgJmd0OyBpdCBoYXMgc29tZSBsZXZlbCBv
ZiBhdXRoZW50aWNhdGlvbiwgeWVzPyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IC1j
bW9ydCA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+
DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBDaHVjayBNb3J0aW1v
cmUgJmx0OzxhIGhyZWY9Im1haWx0bzpjbW9ydGltb3JlQHNhbGVzZm9yY2UuY29tIj5jbW9ydGlt
b3JlQHNhbGVzZm9yY2UuY29tPC9hPiZndDsg5YaZ5LqOIDIwMTItMTItMTQNCjAwOjM5OjAzOjxi
cj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBUaGUgbGFuZ3VhZ2UgaXMgc2ltcGx5
IG1lYW50IHRvIGhlbHAgaWxsdXN0cmF0ZSBob3cgdGhlDQpmcmFtZXdvcmsgPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgbWlnaHQgYmUgdXNlZC4gJm5ic3A7IEhvdyBkbyB5b3UgdGhpbmsgaXQgd2lsbCBy
ZXN0cmljdA0KdXNhZ2U/ICZuYnNwOyBIb3cgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgY291bGQgaXQg
YmUgaW1wcm92ZWQ/IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IC1j
bW9ydCA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBPbiBEZWMgMTIs
IDIwMTIsIGF0IDExOjA0IFBNLCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnpob3Uuc3VqaW5nQHp0ZS5j
b20uY24iPnpob3Uuc3VqaW5nQHp0ZS5jb20uY248L2E+Jmd0Ow0Kd3JvdGU6IDxicj4NCiZndDsg
Jmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7IEluICJz
ZWN0aW9uIDMgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJm5ic3A7VGhlIHRva2VuIHNlcnZpY2UgaXMg
dGhlIGFzc2VydGlvbiBpc3N1ZXI7IGl0cyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmbmJzcDtyb2xl
IGlzIHRvIGZ1bGZpbGwgcmVxdWVzdHMgZnJvbSBjbGllbnRzLCB3aGljaCBwcmVzZW50DQp2YXJp
b3VzIDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZuYnNwO2NyZWRlbnRpYWxzLCBhbmQgbWludCBhc3Nl
cnRpb25zIGFzIHJlcXVlc3RlZCwgZmlsbA0KdGhlbSB3aXRoIDxicj4NCiZndDsgJmd0OyAmZ3Q7
ICZuYnNwO2FwcHJvcHJpYXRlIGluZm9ybWF0aW9uLCBhbmQgc2lnbiB0aGVtLiIgPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgQXMg
SSB1bmRlcnN0YW5kLCBhbiBhc3NlcnRpb24gZ2VuZXJhdGVkIGJ5IGEgU1RTLCBpcyBkb25lDQpm
bG9sbG93aW5nPGJyPg0KJmd0OyAmZ3Q7ICZndDsgdGhlc3Mgc3RlcHM6IDxicj4NCiZndDsgJmd0
OyAmZ3Q7IDEuIENsaWVudCBwcmVzZW50cyBjcmVkZW50aWFsIGFuZCByZXF1ZXN0cyBhbiBhc3Nl
cnRpb24NCjxicj4NCiZndDsgJmd0OyAmZ3Q7IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFu
ZCBzZW5kcyB0byBDbGllbnQgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgQ29ycmVjdD8gPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgVGhhdCBtYXkgcmVzdHJpY3QgdGhlIHVz
ZSBjYXNlcyB0aGF0IHRoaXMgYXNzZXJ0aW9uIGZyYW1ld29yaw0KPGJyPg0KJmd0OyAmZ3Q7IGNv
dWxkIHN1cHBvcnQsIDxicj4NCiZndDsgJmd0OyAmZ3Q7IGlzIGl0IGEgbXVzdD8gPGJyPg0KJmd0
OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGEgaHJlZj0ibWFpbHRvOm9h
dXRoLWJvdW5jZXNAaWV0Zi5vcmciPm9hdXRoLWJvdW5jZXNAaWV0Zi5vcmc8L2E+IOWGmeS6jiAy
MDEyLTEyLTExIDAyOjMzOjU3Ojxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQg
YSByZXF1ZXN0IGZyb20gdGhlIFdlYiBBdXRob3JpemF0aW9uDQpQcm90b2NvbCBXRzxicj4NCiZn
dDsgJmd0OyAmZ3Q7ICZndDsgKG9hdXRoKSB0byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3Vt
ZW50Ojxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgLSAnQXNzZXJ0aW9uIEZyYW1ld29yayBmb3Ig
T0F1dGggMi4wJzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZsdDtkcmFmdC1pZXRm
LW9hdXRoLWFzc2VydGlvbnMtMDgudHh0Jmd0OyBhcw0KUHJvcG9zZWQgU3RhbmRhcmQ8YnI+DQom
Z3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgVGhlIElFU0cgcGxh
bnMgdG8gbWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywNCmFuZCBzb2xpY2l0
czxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24u
IFBsZWFzZSBzZW5kIHN1YnN0YW50aXZlDQpjb21tZW50cyB0byB0aGU8YnI+DQomZ3Q7ICZndDsg
Jmd0OyAmZ3Q7IDxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj5pZXRmQGlldGYub3JnPC9h
PiBtYWlsaW5nIGxpc3RzIGJ5IDIwMTItMTItMjQuIEV4Y2VwdGlvbmFsbHksDQo8YnI+DQomZ3Q7
IGNvbW1lbnRzIG1heSBiZTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgc2VudCB0byA8YSBocmVm
PSJtYWlsdG86aWVzZ0BpZXRmLm9yZyI+aWVzZ0BpZXRmLm9yZzwvYT4gaW5zdGVhZC4gSW4gZWl0
aGVyIGNhc2UsIHBsZWFzZQ0KcmV0YWluIHRoZTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgYmVn
aW5uaW5nIG9mIHRoZSBTdWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0b21hdGVkIHNvcnRpbmcuPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IEFic3RyYWN0
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4N
CiZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO1RoaXMgc3BlY2lmaWNhdGlvbiBwcm92
aWRlcyBhIGZyYW1ld29yaw0KZm9yIHRoZSB1c2Ugb2YgYXNzZXJ0aW9uczxicj4NCiZndDsgJmd0
OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3dpdGggT0F1dGggMi4wIGluIHRoZSBmb3JtIG9mIGEg
bmV3IGNsaWVudA0KYXV0aGVudGljYXRpb24gbWVjaGFuaXNtPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
Jmd0OyAmbmJzcDsgJm5ic3A7YW5kIGEgbmV3IGF1dGhvcml6YXRpb24gZ3JhbnQgdHlwZS4gJm5i
c3A7TWVjaGFuaXNtcw0KYXJlIHNwZWNpZmllZCBmb3I8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7
ICZuYnNwOyAmbmJzcDt0cmFuc3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25z
DQp3aXRoIGEgdG9rZW4gZW5kcG9pbnQsIGFzPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJz
cDsgJm5ic3A7d2VsbCBhcyBnZW5lcmFsIHByb2Nlc3NpbmcgcnVsZXMuPGJyPg0KJmd0OyAmZ3Q7
ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtUaGUgaW50
ZW50IG9mIHRoaXMgc3BlY2lmaWNhdGlvbiBpcyB0bw0KcHJvdmlkZSBhIGNvbW1vbiBmcmFtZXdv
cmsgZm9yPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7T0F1dGggMi4wIHRv
IGludGVyd29yayB3aXRoIG90aGVyIGlkZW50aXR5DQpzeXN0ZW1zIHVzaW5nIGFzc2VydGlvbnMs
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7YW5kIHRvIHByb3ZpZGUgYWx0
ZXJuYXRpdmUgY2xpZW50IGF1dGhlbnRpY2F0aW9uDQptZWNoYW5pc21zLjxicj4NCiZndDsgJmd0
OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7Tm90ZSB0
aGF0IHRoaXMgc3BlY2lmaWNhdGlvbiBvbmx5IGRlZmluZXMNCmFic3RyYWN0IG1lc3NhZ2UgZmxv
d3MgYW5kPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7cHJvY2Vzc2luZyBy
dWxlcy4gJm5ic3A7SW4gb3JkZXIgdG8gYmUNCmltcGxlbWVudGFibGUsIGNvbXBhbmlvbjxicj4N
CiZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3NwZWNpZmljYXRpb25zIGFyZSBuZWNl
c3NhcnkgdG8gcHJvdmlkZQ0KdGhlIGNvcnJlc3BvbmRpbmcgY29uY3JldGU8YnI+DQomZ3Q7ICZn
dDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtpbnN0YW50aWF0aW9ucy48YnI+DQomZ3Q7ICZndDsg
Jmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
Jmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsg
VGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgPGEg
aHJlZj0iaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW9hdXRoLWFz
c2VydGlvbnMvIj5odHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1
dGgtYXNzZXJ0aW9ucy88L2E+PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZn
dDsgJmd0OyAmZ3Q7IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWE8YnI+DQomZ3Q7
ICZndDsgJmd0OyAmZ3Q7IDxhIGhyZWY9Imh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zL2JhbGxvdC8iPmh0dHA6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zL2JhbGxvdC88L2E+PGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyAmZ3Q7ICZndDsgTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRp
cmVjdGx5IG9uDQp0aGlzIEktRC48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBfX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsg
T0F1dGggbWFpbGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YSBocmVmPSJtYWls
dG86T0F1dGhAaWV0Zi5vcmciPk9BdXRoQGlldGYub3JnPC9hPjxicj4NCiZndDsgJmd0OyAmZ3Q7
ICZndDsgPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0
aCI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9vYXV0aDwvYT48YnI+DQom
Z3Q7ICZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7IE9BdXRoIG1haWxpbmcgbGlzdDxicj4NCiZndDsgJmd0
OyAmZ3Q7IDxhIGhyZWY9Im1haWx0bzpPQXV0aEBpZXRmLm9yZyI+T0F1dGhAaWV0Zi5vcmc8L2E+
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9vYXV0aCI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9v
YXV0aDwvYT4gPC9mb250PjwvdHQ+DQo8L2Rpdj48L2Jsb2NrcXVvdGU+PC9ib2R5PjwvaHRtbD4=

--_000_D0292BEDC6D84B569BBE6C280F38BC42salesforcecom_--

From zhou.sujing@zte.com.cn  Thu Dec 13 18:56:32 2012
Return-Path: <zhou.sujing@zte.com.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 C23F521F899D; Thu, 13 Dec 2012 18:56:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.675
X-Spam-Level: 
X-Spam-Status: No, score=-97.675 tagged_above=-999 required=5 tests=[AWL=-0.302, BAYES_00=-2.599, FRT_FOLLOW2=0.422, HTML_MESSAGE=0.001, J_CHICKENPOX_71=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nMc3QRJZd+V; Thu, 13 Dec 2012 18:56:31 -0800 (PST)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 0389D21F8929; Thu, 13 Dec 2012 18:56:31 -0800 (PST)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id 02B541244005; Fri, 14 Dec 2012 10:58:20 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 12F4F724F17; Fri, 14 Dec 2012 10:45:30 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id qBE2uBnA046867; Fri, 14 Dec 2012 10:56:11 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <D0292BED-C6D8-4B56-9BBE-6C280F38BC42@salesforce.com>
To: Chuck Mortimore <cmortimore@salesforce.com>
Subject: Re: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-assertions-08.txt> (Assertion Framework for OAuth 2.0) to Proposed Standard
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF6AFFEFB0.3752F820-ON48257AD4.000F9DD7-48257AD4.00103FB9@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Fri, 14 Dec 2012 10:55:57 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-12-14 10:56:04, Serialize complete at 2012-12-14 10:56:04
Content-Type: multipart/alternative; boundary="=_alternative 00103FB948257AD4_="
X-MAIL: mse02.zte.com.cn qBE2uBnA046867
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:49 -0800
Cc: "oauth-bounces@ietf.org" <oauth-bounces@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "oauth@ietf.org" <oauth@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 02:56:32 -0000

This is a multipart message in MIME format.
--=_alternative 00103FB948257AD4_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

WWVwLCBjb3VsZCBkbyBpdCBzb29uIGxhdGVyLiANCg0KQ3VycmVudGx5LCBJIHN1Z2dlc3QgYSBt
b2RpZmljYXRpb24gZm9yIA0KDQogIlRoZSB0b2tlbiBzZXJ2aWNlIGlzIHRoZSBhc3NlcnRpb24g
aXNzdWVyOyBpdHMgIHJvbGUgaXMgdG8gZnVsZmlsbCANCnJlcXVlc3RzIGZyb20gY2xpZW50cywg
d2hpY2ggcHJlc2VudCB2YXJpb3VzIA0KIGNyZWRlbnRpYWxzLCBhbmQgbWludCBhc3NlcnRpb25z
IGFzIHJlcXVlc3RlZCwgZmlsbCB0aGVtIHdpdGggYXBwcm9wcmlhdGUgDQppbmZvcm1hdGlvbiwg
YW5kIHNpZ24gdGhlbS4iICAoaW4gIHNlY3Rpb24gMyApDQoNCmludG8gDQoNCiAiVGhlIHRva2Vu
IHNlcnZpY2UgaXMgdGhlIGFzc2VydGlvbiBpc3N1ZXIsIGl0IGNvdWxkIGJlIGltcGxlbWVudGVk
IGluIA0KYW55IGVudGl0eSBiZXNpZGVzIGNsaWVudCwgZS5nLiwgUmVzb3VyY2UgT3duZXIsIEF1
dGhvcml6YXRpb24gU2VydmVyOyBpdHMgDQogcm9sZSBpcyB0byBmdWxmaWxsIHJlcXVlc3RzIGZy
b20gY2xpZW50cywgd2hpY2ggcHJlc2VudCB2YXJpb3VzIA0KY3JlZGVudGlhbHMsIGFuZCBtaW50
IGFzc2VydGlvbnMgYXMgcmVxdWVzdGVkLCBmaWxsIHRoZW0gd2l0aCAgYXBwcm9wcmlhdGUgDQpp
bmZvcm1hdGlvbiwgYW5kIHNpZ24gdGhlbS4iIA0KDQoNCg0KQ2h1Y2sgTW9ydGltb3JlIDxjbW9y
dGltb3JlQHNhbGVzZm9yY2UuY29tPiDQtNPaIDIwMTItMTItMTQgMTA6NDQ6MDU6DQoNCj4gQ29y
cmVjdC4gICBUaGF0IHNhaWQgbm8gb25lIGhhcyB5ZXQgcHJvZmlsZWQgaXQgZm9yIGhvbGRlciBv
ZiBrZXkNCj4gDQo+IC0gY21vcnQNCj4gDQo+IE9uIERlYyAxMywgMjAxMiwgYXQgNjozOSBQTSwg
Inpob3Uuc3VqaW5nQHp0ZS5jb20uY24iIA0KPHpob3Uuc3VqaW5nQHp0ZS5jb20uY24NCj4gPiB3
cm90ZToNCg0KPiANCj4gT2gsIEJ1dCB0aGUgZGVzY3JpcHRpb24gb2YgYXNzZXJ0aW9uIGdlbmVy
YXRpb24gaW4gdGhlIGRvY3VtZW50IA0KPiBzaG91bGQgbm90IGJlIGxpbWl0ZWQgYnkgYmVhciBh
c3NlcnRpb24sIHJpZ2h0PyANCj4gDQo+IA0KPiBDaHVjayBNb3J0aW1vcmUgPGNtb3J0aW1vcmVA
c2FsZXNmb3JjZS5jb20+INC009ogMjAxMi0xMi0xNCAxMDozNDoxMzoNCj4gDQo+ID4gWW91IHdh
bnQgYSBob2xkZXIgb2Yga2V5IHBhdHRlcm4uICBUaGUgZHJhZnQgdG91Y2hlcyBvbiBpdCANCj4g
PiANCj4gPiANCj4gPiAgICBUaGUgcHJvdG9jb2wgcGFyYW1ldGVycyBhbmQgcHJvY2Vzc2luZyBy
dWxlcyBkZWZpbmVkIGluIHRoaXMgDQpkb2N1bWVudA0KPiA+ICAgIGFyZSBpbnRlbmRlZCB0byBz
dXBwb3J0IGEgY2xpZW50IHByZXNlbnRpbmcgYSBiZWFyZXIgYXNzZXJ0aW9uIHRvIA0KYW4NCj4g
PiAgICBhdXRob3JpemF0aW9uIHNlcnZlci4gIFRoZSB1c2Ugb2YgaG9sZGVyLW9mLWtleSBhc3Nl
cnRpb25zIGFyZSBub3QNCj4gPiAgICBwcmVjbHVkZWQgYnkgdGhpcyBkb2N1bWVudCwgYnV0IGFk
ZGl0aW9uYWwgcHJvdG9jb2wgZGV0YWlscyB3b3VsZA0KPiA+ICAgIG5lZWQgdG8gYmUgc3BlY2lm
aWVkLg0KPiANCj4gPiANCj4gPiBTbyAtIGlmIHlvdSB3YW50IHRoaXMsIHlvdSBzaG91bGQgcHV0
IGZvcnRoIGEgaG9sZGVyIG9mIGtleSANCj4gPiBwcm9maWxpbmcgb2YgdGhpcyBkcmFmdCBhbmQg
c2VlIGlmIHRoZXJlIGFyZSBhbnkgaXNzdWVzLiAgIFRoZSBvbmx5IA0KPiA+IHByb2ZpbGVzIHdl
IGhhdmUgdGh1cyBmYXIgYXJlIHNhbWwgYW5kIGp3dCBiZWFyZXIgYXNzZXJ0aW9ucy4gDQo+ID4g
DQo+ID4gDQo+ID4gLSBjbW9ydCANCj4gPiANCj4gPiBPbiBEZWMgMTMsIDIwMTIsIGF0IDY6Mjcg
UE0sICJ6aG91LnN1amluZ0B6dGUuY29tLmNuIiA8emhvdS4NCj4gc3VqaW5nQHp0ZS5jb20uY24N
Cj4gPiA+IHdyb3RlOg0KPiANCj4gPiANCj4gPiBJIGFtIG5vdCBzdXJlIGlmIHRoZSBmb2xsb3dp
bmcgdXNlY2FzZSAgaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLQ0KPiA+IGFyY2hpdmUvd2ViL29h
dXRoL2N1cnJlbnQvbXNnMTAyMzMuaHRtbCANCj4gPiBjb3VsZCBiZSBzdXBwb3J0ZWQgYnkgYXNz
ZXJ0aW9uIGZyYW1ld29ya6OsIA0KPiA+IFdlIGhhdmUgc29tZSBkaXNjdXNzaW9uIGluIA0KPiA+
IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9jdXJyZW50L21zZzEw
MjAzLmh0bWwgDQo+ID4gaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL29hdXRo
L2N1cnJlbnQvbXNnMTAxOTguaHRtbCANCj4gPiANCj4gPiBJbiBteSB1c2UgY2FzZSBvciBpbiBz
b21lIG90aGVyIGNhc2VzLCBhc3NlcnRpb25zIGRvbid0IG5lZWQgDQo+ID4gY29uZmlkZW50aWFs
IHByb3RlY3Rpb24sIA0KPiA+IGJhc2ljYWxseSBTVFMgZG9uJ3QgaGF2ZSB0byBhdXRoZW50aWNh
dGUgYSBjbGllbnQgYmVmb3JlIGlzc3VlaW5nIA0KPiA+ICJhc3NlcnRpb24iLCBpZiBpdCBjb3Vs
ZCBiZSBjYWxsZWQgYXNzZXJ0aW9uIGhlcmUuIA0KPiA+IA0KPiA+IEV4YW1wbGUsSSB0cnVzdCBt
eSBsYXl3ZXIsIEkgbWF5IGlzc3VlIGFuICJhc3NlcnRpb24iIHN0YXRpbmcgDQo+ID4gZGVsZWdh
dGlvbiBpbiBhZHZhbmNlLCBhbmQgc2VuZCB0byB0aGUgbGF3eWVyIHdoZW4gaXQgaXMgbmVlZGVk
LCANCj4gPiBpdCBjb3VsZCBiZSBJIGdpdmUgdGhlIGFzc2VydGlvbiB0byBhIGZhbHNlIGxhd3ll
ciwgYnV0IGl0IGRvZXMgbm90IA0KPiA+IG1hdHRlciwgYmVjYXVzZSB0aGUgbGF3eWVyIGhhcyB0
byBwcm92ZSBoZSBrbm93cyBzb21lIGNyZWRlbnRpYWwgDQo+ID4gY29ycmVzcG9uZGluZyB0byBo
aXMgSUQsIA0KPiA+IHdobyBpcyBkZWxlZ2F0ZWQgc29tZSByaWdodHMuIA0KPiA+IA0KPiA+IElm
IGFzc2VydGlvbiBmcmFtZXdvcmsgd2FudCB0byBzdXBwb3J0IHRoaXMgdXNlIGNhc2UsIHRoZW4g
DQo+ID4gZ2VuZXJhdGlvbiBvZiBhc3NlcnRpb24gc2hvdWxkIGJlIHJlbGF4ZWQsIA0KPiA+IG90
aGVyd2lzZSBuZXcgd29yayBpcyByZXF1aXJlZCB0byBzdXBwb3J0IHRoZSB1c2UgY2FzZS4gDQo+
ID4gDQo+ID4gDQo+ID4gDQo+ID4gQ2h1Y2sgTW9ydGltb3JlIDxjbW9ydGltb3JlQHNhbGVzZm9y
Y2UuY29tPiDQtNPaIDIwMTItMTItMTQgMTA6MDg6MzQ6DQo+ID4gDQo+ID4gPiBPbiBEZWMgMTMs
IDIwMTIsIGF0IDQ6MzAgUE0sICJ6aG91LnN1amluZ0B6dGUuY29tLmNuIiA8emhvdS4NCj4gPiBz
dWppbmdAenRlLmNvbS5jbg0KPiA+ID4gPiB3cm90ZToNCj4gPiANCj4gPiA+IA0KPiA+ID4gRnJv
bSB0aGUgbGFuZ3VhZ2UsIEkgZ290IGFuIGltcHJlc3Npb24gdGhhdCBhc3NlcnRpb24gaXMgb25s
eSANCj4gPiA+IGdlbmVyYXRlZCBieSB0b2tlbiBzZXJ2aWNlIGFmdGVyIGNsaWVudHMgcHJlc2Vu
dGluZyBzb21lIA0KY3JlZGVudGlhbHMsIA0KPiA+ID4gdGhlcmUgYXJlIG1heSBiZSBzb21lIGNh
c2VzIHRoYXQgImFzc2VydGlvbiIgZG9uJ3QgbmVlZCBjbGllbnQncyANCj4gPiBjcmVkZW50aWFs
LiANCj4gPiA+IGUuZy4sIFJlc291cmNlIG93bmVyIGFzIGEgdG9rZW4gc2VydmljZSAgY291bGQg
Z2VuZXJhdGUgImFzc2VydGlvbiIgDQo+ID4gPiB0byBhIGNsaWVudCBoZSB0cnVzdHMsIGJ1IHNp
Z25pbmcgYSBzdGF0ZW1lbnQgdGhhdCAiVGhpcyBkZWxlZ2F0aW9uIA0KPiA+ID4gaXMgZ2l2ZW4g
dG8gYSBjbGllbnQgY2FsbGVkIGNsaW5ldC1pZCANCj4gPiA+IGZvciBkb2luZyBzb21ldGhpbmcg
Zm9yIG1lIi4gDQo+ID4gPiANCj4gPiA+IFNvIGhvdyBkb2VzIHRoZSBTVFMgdHJ1c3QgdGhlIGNs
aWVudD8gICBQcmVzdW1hYmx5IGlmIGl0IGlzIHRydXN0ZWQgDQo+ID4gPiBpdCBoYXMgc29tZSBs
ZXZlbCBvZiBhdXRoZW50aWNhdGlvbiwgeWVzPyANCj4gPiA+IA0KPiA+ID4gLWNtb3J0IA0KPiA+
ID4gDQo+ID4gPiANCj4gPiA+IA0KPiA+ID4gDQo+ID4gPiANCj4gPiA+IENodWNrIE1vcnRpbW9y
ZSA8Y21vcnRpbW9yZUBzYWxlc2ZvcmNlLmNvbT4g0LTT2iAyMDEyLTEyLTE0IA0KMDA6Mzk6MDM6
DQo+ID4gPiANCj4gPiA+ID4gVGhlIGxhbmd1YWdlIGlzIHNpbXBseSBtZWFudCB0byBoZWxwIGls
bHVzdHJhdGUgaG93IHRoZSBmcmFtZXdvcmsgDQo+ID4gPiA+IG1pZ2h0IGJlIHVzZWQuICAgSG93
IGRvIHlvdSB0aGluayBpdCB3aWxsIHJlc3RyaWN0IHVzYWdlPyAgIEhvdyANCj4gPiA+ID4gY291
bGQgaXQgYmUgaW1wcm92ZWQ/IA0KPiA+ID4gPiANCj4gPiA+ID4gLWNtb3J0IA0KPiA+ID4gPiAN
Cj4gPiA+ID4gT24gRGVjIDEyLCAyMDEyLCBhdCAxMTowNCBQTSwgPHpob3Uuc3VqaW5nQHp0ZS5j
b20uY24+IHdyb3RlOiANCj4gPiA+ID4gDQo+ID4gPiA+IA0KPiA+ID4gPiBJbiAic2VjdGlvbiAz
IA0KPiA+ID4gPiAgVGhlIHRva2VuIHNlcnZpY2UgaXMgdGhlIGFzc2VydGlvbiBpc3N1ZXI7IGl0
cyANCj4gPiA+ID4gIHJvbGUgaXMgdG8gZnVsZmlsbCByZXF1ZXN0cyBmcm9tIGNsaWVudHMsIHdo
aWNoIHByZXNlbnQgdmFyaW91cyANCj4gPiA+ID4gIGNyZWRlbnRpYWxzLCBhbmQgbWludCBhc3Nl
cnRpb25zIGFzIHJlcXVlc3RlZCwgZmlsbCB0aGVtIHdpdGggDQo+ID4gPiA+ICBhcHByb3ByaWF0
ZSBpbmZvcm1hdGlvbiwgYW5kIHNpZ24gdGhlbS4iIA0KPiA+ID4gPiANCj4gPiA+ID4gDQo+ID4g
PiA+IEFzIEkgdW5kZXJzdGFuZCwgYW4gYXNzZXJ0aW9uIGdlbmVyYXRlZCBieSBhIFNUUywgaXMg
ZG9uZSANCmZsb2xsb3dpbmcNCj4gPiA+ID4gdGhlc3Mgc3RlcHM6IA0KPiA+ID4gPiAxLiBDbGll
bnQgcHJlc2VudHMgY3JlZGVudGlhbCBhbmQgcmVxdWVzdHMgYW4gYXNzZXJ0aW9uIA0KPiA+ID4g
PiAyLiBTVFMgZ2VuZXJhdGVzIGFzc2VydGlvbiBhbmQgc2VuZHMgdG8gQ2xpZW50IA0KPiA+ID4g
PiBDb3JyZWN0PyANCj4gPiA+ID4gDQo+ID4gPiA+IFRoYXQgbWF5IHJlc3RyaWN0IHRoZSB1c2Ug
Y2FzZXMgdGhhdCB0aGlzIGFzc2VydGlvbiBmcmFtZXdvcmsgDQo+ID4gPiBjb3VsZCBzdXBwb3J0
LCANCj4gPiA+ID4gaXMgaXQgYSBtdXN0PyANCj4gPiA+ID4gDQo+ID4gPiA+IA0KPiA+ID4gPiAN
Cj4gPiA+ID4gDQo+ID4gPiA+IG9hdXRoLWJvdW5jZXNAaWV0Zi5vcmcg0LTT2iAyMDEyLTEyLTEx
IDAyOjMzOjU3Og0KPiA+ID4gPiANCj4gPiA+ID4gPiANCj4gPiA+ID4gPiBUaGUgSUVTRyBoYXMg
cmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIFdlYiBBdXRob3JpemF0aW9uIA0KUHJvdG9jb2wg
V0cNCj4gPiA+ID4gPiAob2F1dGgpIHRvIGNvbnNpZGVyIHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6
DQo+ID4gPiA+ID4gLSAnQXNzZXJ0aW9uIEZyYW1ld29yayBmb3IgT0F1dGggMi4wJw0KPiA+ID4g
PiA+ICAgPGRyYWZ0LWlldGYtb2F1dGgtYXNzZXJ0aW9ucy0wOC50eHQ+IGFzIFByb3Bvc2VkIFN0
YW5kYXJkDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gVGhlIElFU0cgcGxhbnMgdG8gbWFrZSBhIGRl
Y2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywgYW5kIA0Kc29saWNpdHMNCj4gPiA+ID4gPiBm
aW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29t
bWVudHMgDQp0byB0aGUNCj4gPiA+ID4gPiBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMgYnkg
MjAxMi0xMi0yNC4gRXhjZXB0aW9uYWxseSwgDQo+ID4gY29tbWVudHMgbWF5IGJlDQo+ID4gPiA+
ID4gc2VudCB0byBpZXNnQGlldGYub3JnIGluc3RlYWQuIEluIGVpdGhlciBjYXNlLCBwbGVhc2Ug
cmV0YWluIHRoZQ0KPiA+ID4gPiA+IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFs
bG93IGF1dG9tYXRlZCBzb3J0aW5nLg0KPiA+ID4gPiA+IA0KPiA+ID4gPiA+IEFic3RyYWN0DQo+
ID4gPiA+ID4gDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gICAgVGhpcyBzcGVjaWZpY2F0aW9uIHBy
b3ZpZGVzIGEgZnJhbWV3b3JrIGZvciB0aGUgdXNlIG9mIA0KYXNzZXJ0aW9ucw0KPiA+ID4gPiA+
ICAgIHdpdGggT0F1dGggMi4wIGluIHRoZSBmb3JtIG9mIGEgbmV3IGNsaWVudCANCmF1dGhlbnRp
Y2F0aW9ubWVjaGFuaXNtDQo+ID4gPiA+ID4gICAgYW5kIGEgbmV3IGF1dGhvcml6YXRpb24gZ3Jh
bnQgdHlwZS4gIE1lY2hhbmlzbXMgYXJlIHNwZWNpZmllZCANCmZvcg0KPiA+ID4gPiA+ICAgIHRy
YW5zcG9ydGluZyBhc3NlcnRpb25zIGR1cmluZyBpbnRlcmFjdGlvbnMgd2l0aCBhIHRva2VuIA0K
PiBlbmRwb2ludCwgYXMNCj4gPiA+ID4gPiAgICB3ZWxsIGFzIGdlbmVyYWwgcHJvY2Vzc2luZyBy
dWxlcy4NCj4gPiA+ID4gPiANCj4gPiA+ID4gPiAgICBUaGUgaW50ZW50IG9mIHRoaXMgc3BlY2lm
aWNhdGlvbiBpcyB0byBwcm92aWRlIGEgY29tbW9uIA0KPiBmcmFtZXdvcmsgZm9yDQo+ID4gPiA+
ID4gICAgT0F1dGggMi4wIHRvIGludGVyd29yayB3aXRoIG90aGVyIGlkZW50aXR5IHN5c3RlbXMg
dXNpbmcgDQo+IGFzc2VydGlvbnMsDQo+ID4gPiA+ID4gICAgYW5kIHRvIHByb3ZpZGUgYWx0ZXJu
YXRpdmUgY2xpZW50IGF1dGhlbnRpY2F0aW9uIG1lY2hhbmlzbXMuDQo+ID4gPiA+ID4gDQo+ID4g
PiA+ID4gICAgTm90ZSB0aGF0IHRoaXMgc3BlY2lmaWNhdGlvbiBvbmx5IGRlZmluZXMgYWJzdHJh
Y3QgDQo+IG1lc3NhZ2UgZmxvd3MgYW5kDQo+ID4gPiA+ID4gICAgcHJvY2Vzc2luZyBydWxlcy4g
IEluIG9yZGVyIHRvIGJlIGltcGxlbWVudGFibGUsIGNvbXBhbmlvbg0KPiA+ID4gPiA+ICAgIHNw
ZWNpZmljYXRpb25zIGFyZSBuZWNlc3NhcnkgdG8gcHJvdmlkZSB0aGUgY29ycmVzcG9uZGluZyAN
CmNvbmNyZXRlDQo+ID4gPiA+ID4gICAgaW5zdGFudGlhdGlvbnMuDQo+ID4gPiA+ID4gDQo+ID4g
PiA+ID4gDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gVGhlIGZpbGUgY2FuIGJl
IG9idGFpbmVkIHZpYQ0KPiA+ID4gPiA+IGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLw0KPiA+ID4gPiA+IA0KPiA+ID4gPiA+IElFU0cg
ZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4gPiA+ID4gPiANCmh0dHA6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zL2JhbGxvdC8NCj4g
PiA+ID4gPiANCj4gPiA+ID4gPiANCj4gPiA+ID4gPiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUg
YmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQo+ID4gPiA+ID4gDQo+ID4gPiA+
ID4gDQo+ID4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4gPiA+ID4gPiBPQXV0aCBtYWlsaW5nIGxpc3QNCj4gPiA+ID4gPiBPQXV0aEBpZXRm
Lm9yZw0KPiA+ID4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1
dGgNCj4gPiA+ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCj4gPiA+ID4gT0F1dGggbWFpbGluZyBsaXN0DQo+ID4gPiA+IE9BdXRoQGlldGYub3JnDQo+
ID4gPiA+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vb2F1dGggDQo=
--=_alternative 00103FB948257AD4_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPlllcCwgY291bGQgZG8gaXQgc29v
biBsYXRlci4gPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJzYW5zLXNlcmlm
Ij5DdXJyZW50bHksIEkgc3VnZ2VzdCBhIG1vZGlmaWNhdGlvbg0KZm9yIDwvZm9udD4NCjxicj4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+Jm5ic3A7JnF1b3Q7VGhlIHRva2Vu
IHNlcnZpY2UgaXMgdGhlDQphc3NlcnRpb24gaXNzdWVyOyBpdHMgJm5ic3A7cm9sZSBpcyB0byBm
dWxmaWxsIHJlcXVlc3RzIGZyb20gY2xpZW50cywgd2hpY2gNCnByZXNlbnQgdmFyaW91cyA8L2Zv
bnQ+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPiZuYnNwO2NyZWRlbnRpYWxz
LCBhbmQgbWludCBhc3NlcnRpb25zDQphcyByZXF1ZXN0ZWQsIGZpbGwgdGhlbSB3aXRoICZuYnNw
O2FwcHJvcHJpYXRlIGluZm9ybWF0aW9uLCBhbmQgc2lnbiB0aGVtLiZxdW90Ow0KJm5ic3A7KGlu
ICZuYnNwO3NlY3Rpb24gMyApPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJz
YW5zLXNlcmlmIj5pbnRvIDwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fu
cy1zZXJpZiI+Jm5ic3A7JnF1b3Q7VGhlIHRva2VuIHNlcnZpY2UgaXMgdGhlDQphc3NlcnRpb24g
aXNzdWVyLCA8Yj5pdCBjb3VsZCBiZSBpbXBsZW1lbnRlZCBpbiBhbnkgZW50aXR5IGJlc2lkZXMg
Y2xpZW50LA0KZS5nLiwgUmVzb3VyY2UgT3duZXIsIEF1dGhvcml6YXRpb24gU2VydmVyOzwvYj4g
aXRzICZuYnNwO3JvbGUgaXMgdG8gZnVsZmlsbA0KcmVxdWVzdHMgZnJvbSBjbGllbnRzLCA8c3Ry
aWtlPndoaWNoIHByZXNlbnQgdmFyaW91cyAmbmJzcDtjcmVkZW50aWFsczwvc3RyaWtlPiwNCmFu
ZCBtaW50IGFzc2VydGlvbnMgYXMgcmVxdWVzdGVkLCBmaWxsIHRoZW0gd2l0aCAmbmJzcDthcHBy
b3ByaWF0ZSBpbmZvcm1hdGlvbiwNCmFuZCBzaWduIHRoZW0uJnF1b3Q7IDwvZm9udD4NCjxicj4N
Cjxicj4NCjxicj4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPkNodWNrIE1vcnRpbW9yZSAmbHQ7Y21v
cnRpbW9yZUBzYWxlc2ZvcmNlLmNvbSZndDsNCtC009ogMjAxMi0xMi0xNCAxMDo0NDowNTo8YnI+
DQo8YnI+DQomZ3Q7IENvcnJlY3QuICZuYnNwOyBUaGF0IHNhaWQgbm8gb25lIGhhcyB5ZXQgcHJv
ZmlsZWQgaXQgZm9yIGhvbGRlciBvZg0Ka2V5PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IC0gY21vcnQ8
L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPiZndDsgPGJyPg0KJmd0OyBPbiBEZWMg
MTMsIDIwMTIsIGF0IDY6MzkgUE0sICZxdW90O3pob3Uuc3VqaW5nQHp0ZS5jb20uY24mcXVvdDsg
Jmx0O3pob3Uuc3VqaW5nQHp0ZS5jb20uY248YnI+DQomZ3Q7ICZndDsgd3JvdGU6PGJyPg0KPC9m
b250PjwvdHQ+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj4mZ3Q7IDxicj4NCiZndDsgT2gsIEJ1dCB0
aGUgZGVzY3JpcHRpb24gb2YgYXNzZXJ0aW9uIGdlbmVyYXRpb24gaW4gdGhlIGRvY3VtZW50IDxi
cj4NCiZndDsgc2hvdWxkIG5vdCBiZSBsaW1pdGVkIGJ5IGJlYXIgYXNzZXJ0aW9uLCByaWdodD8g
PGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4NCiZndDsgQ2h1Y2sgTW9ydGltb3JlICZsdDtjbW9y
dGltb3JlQHNhbGVzZm9yY2UuY29tJmd0OyDQtNPaIDIwMTItMTItMTQNCjEwOjM0OjEzOjxicj4N
CiZndDsgPGJyPg0KJmd0OyAmZ3Q7IFlvdSB3YW50IGEgaG9sZGVyIG9mIGtleSBwYXR0ZXJuLiAm
bmJzcDtUaGUgZHJhZnQgdG91Y2hlcyBvbg0KaXQgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyA8YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO1RoZSBwcm90b2NvbCBwYXJhbWV0ZXJz
IGFuZCBwcm9jZXNzaW5nIHJ1bGVzIGRlZmluZWQNCmluIHRoaXMgZG9jdW1lbnQ8YnI+DQomZ3Q7
ICZndDsgJm5ic3A7ICZuYnNwO2FyZSBpbnRlbmRlZCB0byBzdXBwb3J0IGEgY2xpZW50IHByZXNl
bnRpbmcgYSBiZWFyZXINCmFzc2VydGlvbiB0byBhbjxicj4NCiZndDsgJmd0OyAmbmJzcDsgJm5i
c3A7YXV0aG9yaXphdGlvbiBzZXJ2ZXIuICZuYnNwO1RoZSB1c2Ugb2YgaG9sZGVyLW9mLWtleQ0K
YXNzZXJ0aW9ucyBhcmUgbm90PGJyPg0KJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtwcmVjbHVkZWQg
YnkgdGhpcyBkb2N1bWVudCwgYnV0IGFkZGl0aW9uYWwgcHJvdG9jb2wNCmRldGFpbHMgd291bGQ8
YnI+DQomZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO25lZWQgdG8gYmUgc3BlY2lmaWVkLjxicj4NCiZn
dDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBTbyAtIGlmIHlvdSB3YW50IHRoaXMs
IHlvdSBzaG91bGQgcHV0IGZvcnRoIGEgaG9sZGVyIG9mIGtleSA8YnI+DQomZ3Q7ICZndDsgcHJv
ZmlsaW5nIG9mIHRoaXMgZHJhZnQgYW5kIHNlZSBpZiB0aGVyZSBhcmUgYW55IGlzc3Vlcy4gJm5i
c3A7DQpUaGUgb25seSA8YnI+DQomZ3Q7ICZndDsgcHJvZmlsZXMgd2UgaGF2ZSB0aHVzIGZhciBh
cmUgc2FtbCBhbmQgand0IGJlYXJlciBhc3NlcnRpb25zLg0KJm5ic3A7IDxicj4NCiZndDsgJmd0
OyA8YnI+DQomZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IC0gY21vcnQgPGJyPg0KJmd0OyAmZ3Q7
IDxicj4NCiZndDsgJmd0OyBPbiBEZWMgMTMsIDIwMTIsIGF0IDY6MjcgUE0sICZxdW90O3pob3Uu
c3VqaW5nQHp0ZS5jb20uY24mcXVvdDsNCiZsdDt6aG91Ljxicj4NCiZndDsgc3VqaW5nQHp0ZS5j
b20uY248YnI+DQomZ3Q7ICZndDsgJmd0OyB3cm90ZTo8YnI+DQomZ3Q7IDxicj4NCiZndDsgJmd0
OyA8YnI+DQomZ3Q7ICZndDsgSSBhbSBub3Qgc3VyZSBpZiB0aGUgZm9sbG93aW5nIHVzZWNhc2Ug
Jm5ic3A7aHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLTxicj4NCiZndDsgJmd0OyBhcmNoaXZlL3dl
Yi9vYXV0aC9jdXJyZW50L21zZzEwMjMzLmh0bWwgPGJyPg0KJmd0OyAmZ3Q7IGNvdWxkIGJlIHN1
cHBvcnRlZCBieSBhc3NlcnRpb24gZnJhbWV3b3Jro6wgPGJyPg0KJmd0OyAmZ3Q7IFdlIGhhdmUg
c29tZSBkaXNjdXNzaW9uIGluICZuYnNwOyA8YnI+DQomZ3Q7ICZndDsgaHR0cDovL3d3dy5pZXRm
Lm9yZy9tYWlsLWFyY2hpdmUvd2ViL29hdXRoL2N1cnJlbnQvbXNnMTAyMDMuaHRtbA0KPGJyPg0K
Jmd0OyAmZ3Q7IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9vYXV0aC9jdXJy
ZW50L21zZzEwMTk4Lmh0bWwNCjxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgSW4gbXkg
dXNlIGNhc2Ugb3IgaW4gc29tZSBvdGhlciBjYXNlcywgYXNzZXJ0aW9ucyBkb24ndCBuZWVkDQo8
YnI+DQomZ3Q7ICZndDsgY29uZmlkZW50aWFsIHByb3RlY3Rpb24sIDxicj4NCiZndDsgJmd0OyBi
YXNpY2FsbHkgU1RTIGRvbid0IGhhdmUgdG8gYXV0aGVudGljYXRlIGEgY2xpZW50IGJlZm9yZSBp
c3N1ZWluZw0KPGJyPg0KJmd0OyAmZ3Q7ICZxdW90O2Fzc2VydGlvbiZxdW90OywgaWYgaXQgY291
bGQgYmUgY2FsbGVkIGFzc2VydGlvbiBoZXJlLg0KPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyBFeGFtcGxlLEkgdHJ1c3QgbXkgbGF5d2VyLCBJIG1heSBpc3N1ZSBhbiAmcXVvdDthc3Nl
cnRpb24mcXVvdDsNCnN0YXRpbmcgPGJyPg0KJmd0OyAmZ3Q7IGRlbGVnYXRpb24gaW4gYWR2YW5j
ZSwgYW5kIHNlbmQgdG8gdGhlIGxhd3llciB3aGVuIGl0IGlzIG5lZWRlZCwNCjxicj4NCiZndDsg
Jmd0OyBpdCBjb3VsZCBiZSBJIGdpdmUgdGhlIGFzc2VydGlvbiB0byBhIGZhbHNlIGxhd3llciwg
YnV0IGl0IGRvZXMNCm5vdCA8YnI+DQomZ3Q7ICZndDsgbWF0dGVyLCBiZWNhdXNlIHRoZSBsYXd5
ZXIgaGFzIHRvIHByb3ZlIGhlIGtub3dzIHNvbWUgY3JlZGVudGlhbA0KPGJyPg0KJmd0OyAmZ3Q7
IGNvcnJlc3BvbmRpbmcgdG8gaGlzIElELCA8YnI+DQomZ3Q7ICZndDsgd2hvIGlzIGRlbGVnYXRl
ZCBzb21lIHJpZ2h0cy4gPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBJZiBhc3NlcnRp
b24gZnJhbWV3b3JrIHdhbnQgdG8gc3VwcG9ydCB0aGlzIHVzZSBjYXNlLCB0aGVuIDxicj4NCiZn
dDsgJmd0OyBnZW5lcmF0aW9uIG9mIGFzc2VydGlvbiBzaG91bGQgYmUgcmVsYXhlZCwgPGJyPg0K
Jmd0OyAmZ3Q7IG90aGVyd2lzZSBuZXcgd29yayBpcyByZXF1aXJlZCB0byBzdXBwb3J0IHRoZSB1
c2UgY2FzZS4gPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsg
PGJyPg0KJmd0OyAmZ3Q7IENodWNrIE1vcnRpbW9yZSAmbHQ7Y21vcnRpbW9yZUBzYWxlc2ZvcmNl
LmNvbSZndDsg0LTT2iAyMDEyLTEyLTE0DQoxMDowODozNDo8YnI+DQomZ3Q7ICZndDsgPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgT24gRGVjIDEzLCAyMDEyLCBhdCA0OjMwIFBNLCAmcXVvdDt6aG91LnN1
amluZ0B6dGUuY29tLmNuJnF1b3Q7DQombHQ7emhvdS48YnI+DQomZ3Q7ICZndDsgc3VqaW5nQHp0
ZS5jb20uY248YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IHdyb3RlOjxicj4NCiZndDsgJmd0OyA8
YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBGcm9tIHRoZSBsYW5ndWFn
ZSwgSSBnb3QgYW4gaW1wcmVzc2lvbiB0aGF0IGFzc2VydGlvbiBpcw0Kb25seSA8YnI+DQomZ3Q7
ICZndDsgJmd0OyBnZW5lcmF0ZWQgYnkgdG9rZW4gc2VydmljZSBhZnRlciBjbGllbnRzIHByZXNl
bnRpbmcgc29tZQ0KY3JlZGVudGlhbHMsIDxicj4NCiZndDsgJmd0OyAmZ3Q7IHRoZXJlIGFyZSBt
YXkgYmUgc29tZSBjYXNlcyB0aGF0ICZxdW90O2Fzc2VydGlvbiZxdW90OyBkb24ndA0KbmVlZCBj
bGllbnQncyA8YnI+DQomZ3Q7ICZndDsgY3JlZGVudGlhbC4gPGJyPg0KJmd0OyAmZ3Q7ICZndDsg
ZS5nLiwgUmVzb3VyY2Ugb3duZXIgYXMgYSB0b2tlbiBzZXJ2aWNlICZuYnNwO2NvdWxkIGdlbmVy
YXRlDQomcXVvdDthc3NlcnRpb24mcXVvdDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgdG8gYSBjbGll
bnQgaGUgdHJ1c3RzLCBidSBzaWduaW5nIGEgc3RhdGVtZW50IHRoYXQgJnF1b3Q7VGhpcw0KZGVs
ZWdhdGlvbiA8YnI+DQomZ3Q7ICZndDsgJmd0OyBpcyBnaXZlbiB0byBhIGNsaWVudCBjYWxsZWQg
Y2xpbmV0LWlkIDxicj4NCiZndDsgJmd0OyAmZ3Q7IGZvciBkb2luZyBzb21ldGhpbmcgZm9yIG1l
JnF1b3Q7LiA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyBTbyBob3cg
ZG9lcyB0aGUgU1RTIHRydXN0IHRoZSBjbGllbnQ/ICZuYnNwOyBQcmVzdW1hYmx5DQppZiBpdCBp
cyB0cnVzdGVkIDxicj4NCiZndDsgJmd0OyAmZ3Q7IGl0IGhhcyBzb21lIGxldmVsIG9mIGF1dGhl
bnRpY2F0aW9uLCB5ZXM/IDxicj4NCiZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7
IC1jbW9ydCA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQom
Z3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyA8
YnI+DQomZ3Q7ICZndDsgJmd0OyBDaHVjayBNb3J0aW1vcmUgJmx0O2Ntb3J0aW1vcmVAc2FsZXNm
b3JjZS5jb20mZ3Q7INC009oNCjIwMTItMTItMTQgMDA6Mzk6MDM6PGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBUaGUgbGFuZ3VhZ2UgaXMgc2ltcGx5IG1lYW50
IHRvIGhlbHAgaWxsdXN0cmF0ZSBob3cNCnRoZSBmcmFtZXdvcmsgPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgJmd0OyBtaWdodCBiZSB1c2VkLiAmbmJzcDsgSG93IGRvIHlvdSB0aGluayBpdCB3aWxsIHJl
c3RyaWN0DQp1c2FnZT8gJm5ic3A7IEhvdyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGNvdWxk
IGl0IGJlIGltcHJvdmVkPyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0
OyAmZ3Q7ICZndDsgLWNtb3J0IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgJmd0OyBPbiBEZWMgMTIsIDIwMTIsIGF0IDExOjA0IFBNLCAmbHQ7emhvdS5zdWpp
bmdAenRlLmNvbS5jbiZndDsNCndyb3RlOiA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4N
CiZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBJbiAmcXVvdDtz
ZWN0aW9uIDMgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDtUaGUgdG9rZW4gc2Vydmlj
ZSBpcyB0aGUgYXNzZXJ0aW9uIGlzc3VlcjsgaXRzDQo8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7
ICZuYnNwO3JvbGUgaXMgdG8gZnVsZmlsbCByZXF1ZXN0cyBmcm9tIGNsaWVudHMsIHdoaWNoDQpw
cmVzZW50IHZhcmlvdXMgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDtjcmVkZW50aWFs
cywgYW5kIG1pbnQgYXNzZXJ0aW9ucyBhcyByZXF1ZXN0ZWQsDQpmaWxsIHRoZW0gd2l0aCA8YnI+
DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwO2FwcHJvcHJpYXRlIGluZm9ybWF0aW9uLCBhbmQg
c2lnbiB0aGVtLiZxdW90Ow0KPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZn
dDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgQXMgSSB1bmRlcnN0YW5kLCBh
biBhc3NlcnRpb24gZ2VuZXJhdGVkIGJ5IGEgU1RTLCBpcw0KZG9uZSBmbG9sbG93aW5nPGJyPg0K
Jmd0OyAmZ3Q7ICZndDsgJmd0OyB0aGVzcyBzdGVwczogPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0
OyAxLiBDbGllbnQgcHJlc2VudHMgY3JlZGVudGlhbCBhbmQgcmVxdWVzdHMgYW4gYXNzZXJ0aW9u
DQo8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDIuIFNUUyBnZW5lcmF0ZXMgYXNzZXJ0aW9uIGFu
ZCBzZW5kcyB0byBDbGllbnQgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBDb3JyZWN0PyA8YnI+
DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgVGhhdCBtYXkg
cmVzdHJpY3QgdGhlIHVzZSBjYXNlcyB0aGF0IHRoaXMgYXNzZXJ0aW9uDQpmcmFtZXdvcmsgPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgY291bGQgc3VwcG9ydCwgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0
OyBpcyBpdCBhIG11c3Q/IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7
ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7
ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyBvYXV0aC1ib3VuY2VzQGlldGYub3JnINC0
09ogMjAxMi0xMi0xMSAwMjozMzo1Nzo8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZn
dDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgVGhl
IElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIHRoZSBXZWIgQXV0aG9yaXphdGlvbg0K
UHJvdG9jb2wgV0c8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgKG9hdXRoKSB0byBjb25z
aWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50Ojxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0
OyAtICdBc3NlcnRpb24gRnJhbWV3b3JrIGZvciBPQXV0aCAyLjAnPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbHQ7ZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLTA4LnR4
dCZndDsNCmFzIFByb3Bvc2VkIFN0YW5kYXJkPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7
IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyBUaGUgSUVTRyBwbGFucyB0byBtYWtlIGEg
ZGVjaXNpb24gaW4gdGhlIG5leHQNCmZldyB3ZWVrcywgYW5kIHNvbGljaXRzPGJyPg0KJmd0OyAm
Z3Q7ICZndDsgJmd0OyAmZ3Q7IGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ug
c2VuZCBzdWJzdGFudGl2ZQ0KY29tbWVudHMgdG8gdGhlPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0
OyAmZ3Q7IGlldGZAaWV0Zi5vcmcgbWFpbGluZyBsaXN0cyBieSAyMDEyLTEyLTI0LiBFeGNlcHRp
b25hbGx5LA0KPGJyPg0KJmd0OyAmZ3Q7IGNvbW1lbnRzIG1heSBiZTxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZndDsgJmd0OyBzZW50IHRvIGllc2dAaWV0Zi5vcmcgaW5zdGVhZC4gSW4gZWl0aGVyIGNh
c2UsDQpwbGVhc2UgcmV0YWluIHRoZTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyBiZWdp
bm5pbmcgb2YgdGhlIFN1YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQNCnNvcnRpbmcuPGJy
Pg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0
OyBBYnN0cmFjdDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsg
Jmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJz
cDtUaGlzIHNwZWNpZmljYXRpb24gcHJvdmlkZXMgYSBmcmFtZXdvcmsNCmZvciB0aGUgdXNlIG9m
IGFzc2VydGlvbnM8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO3dp
dGggT0F1dGggMi4wIGluIHRoZSBmb3JtIG9mIGEgbmV3DQpjbGllbnQgYXV0aGVudGljYXRpb25t
ZWNoYW5pc208YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNwO2FuZCBh
IG5ldyBhdXRob3JpemF0aW9uIGdyYW50IHR5cGUuDQombmJzcDtNZWNoYW5pc21zIGFyZSBzcGVj
aWZpZWQgZm9yPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDt0cmFu
c3BvcnRpbmcgYXNzZXJ0aW9ucyBkdXJpbmcgaW50ZXJhY3Rpb25zDQp3aXRoIGEgdG9rZW4gPGJy
Pg0KJmd0OyBlbmRwb2ludCwgYXM8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7
ICZuYnNwO3dlbGwgYXMgZ2VuZXJhbCBwcm9jZXNzaW5nIHJ1bGVzLjxicj4NCiZndDsgJmd0OyAm
Z3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgJm5ic3A7ICZuYnNw
O1RoZSBpbnRlbnQgb2YgdGhpcyBzcGVjaWZpY2F0aW9uDQppcyB0byBwcm92aWRlIGEgY29tbW9u
IDxicj4NCiZndDsgZnJhbWV3b3JrIGZvcjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyAm
bmJzcDsgJm5ic3A7T0F1dGggMi4wIHRvIGludGVyd29yayB3aXRoIG90aGVyDQppZGVudGl0eSBz
eXN0ZW1zIHVzaW5nIDxicj4NCiZndDsgYXNzZXJ0aW9ucyw8YnI+DQomZ3Q7ICZndDsgJmd0OyAm
Z3Q7ICZndDsgJm5ic3A7ICZuYnNwO2FuZCB0byBwcm92aWRlIGFsdGVybmF0aXZlIGNsaWVudA0K
YXV0aGVudGljYXRpb24gbWVjaGFuaXNtcy48YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsg
PGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZuYnNwOyAmbmJzcDtOb3RlIHRoYXQgdGhp
cyBzcGVjaWZpY2F0aW9uIG9ubHkNCmRlZmluZXMgYWJzdHJhY3QgPGJyPg0KJmd0OyBtZXNzYWdl
IGZsb3dzIGFuZDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7cHJv
Y2Vzc2luZyBydWxlcy4gJm5ic3A7SW4gb3JkZXINCnRvIGJlIGltcGxlbWVudGFibGUsIGNvbXBh
bmlvbjxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7c3BlY2lmaWNh
dGlvbnMgYXJlIG5lY2Vzc2FyeSB0byBwcm92aWRlDQp0aGUgY29ycmVzcG9uZGluZyBjb25jcmV0
ZTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyAmbmJzcDsgJm5ic3A7aW5zdGFudGlhdGlv
bnMuPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZn
dDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZn
dDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyBUaGUgZmlsZSBjYW4g
YmUgb2J0YWluZWQgdmlhPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7IGh0dHA6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1vYXV0aC1hc3NlcnRpb25zLzxicj4NCiZn
dDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgSUVT
RyBkaXNjdXNzaW9uIGNhbiBiZSB0cmFja2VkIHZpYTxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsg
Jmd0OyBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtb2F1dGgtYXNz
ZXJ0aW9ucy9iYWxsb3QvPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAmZ3Q7IDxicj4NCiZndDsg
Jmd0OyAmZ3Q7ICZndDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgTm8gSVBS
IGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5DQpvbiB0aGlzIEktRC48
YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgPGJyPg0KJmd0OyAmZ3Q7ICZndDsgJmd0OyAm
Z3Q7IDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgJmd0OyBP
QXV0aCBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgT0F1dGhAaWV0
Zi5vcmc8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7ICZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9vYXV0aDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQomZ3Q7ICZndDsgJmd0
OyAmZ3Q7IE9BdXRoIG1haWxpbmcgbGlzdDxicj4NCiZndDsgJmd0OyAmZ3Q7ICZndDsgT0F1dGhA
aWV0Zi5vcmc8YnI+DQomZ3Q7ICZndDsgJmd0OyAmZ3Q7IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vb2F1dGggPC9mb250PjwvdHQ+DQo=
--=_alternative 00103FB948257AD4_=--

From jasnell@gmail.com  Fri Dec 14 08:41:02 2012
Return-Path: <jasnell@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 D684121F89E9; Fri, 14 Dec 2012 08:41:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.707
X-Spam-Level: 
X-Spam-Status: No, score=-3.707 tagged_above=-999 required=5 tests=[AWL=-0.109, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUm6sSIM2Ni5; Fri, 14 Dec 2012 08:41:02 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id CF5A321F894D; Fri, 14 Dec 2012 08:41:01 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so6252261ieb.31 for <multiple recipients>; Fri, 14 Dec 2012 08:40:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Z4cmBJ7oAY29bR3/a8ACPI4H06Lrrmh4SGAYfcHCLrI=; b=NecIG+gej7MZatR1XcBVIlmAmywKjNBqYE/2JbXCXkdX+vWNLX8W3RbBAs5gTJSZ80 TvU7H0xNd5P0ZakWZkdDVSKalvMzG2M9Nw+xD3KIITqyMaJg8nNPR/dipmGqV/WhY5kB /BWKqC3/3+EXT3eThhZdBYehv/10LHLbgmfqWgToYFIaj8GSxyYmeOi4SJguzQNdn4yD iRFzGAQ0jrxyxo3bLtYPI+5+/bz41PbQt6ubN8ZWm5CSgIVs6bFlVQuQSYmUcaM5bZyt O+NmHCwou/lCkqBjP80eG9gSfSAfCue5PWQqMN9kKhSc+gi0zOGxLB7wdf1wcdxpBBvb ax/A==
Received: by 10.50.6.169 with SMTP id c9mr2179709iga.24.1355503256744; Fri, 14 Dec 2012 08:40:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Fri, 14 Dec 2012 08:40:36 -0800 (PST)
In-Reply-To: <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com>
From: James M Snell <jasnell@gmail.com>
Date: Fri, 14 Dec 2012 08:40:36 -0800
Message-ID: <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: multipart/alternative; boundary=e89a8f6467171c338604d0d2b2c4
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:57 -0800
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 16:41:03 -0000

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

JSON Pointer does not distinguish between objects and arrays. That is not
determined until the pointer is applied to an actual object instance... the
pointer "/1" is valid against {"1":"a"} or ["a","b"]


On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
<markus.lanthaler@gmx.net>wrote:

> I've asked that before but didn't get an answer. So let me ask again (even
> though I'm quite sure it has already been asked by somebody else).
>
> How does JSON Pointer distinguish between objects and arrays? E.g. consider
> the following JSON document:
>
> {
>   "foo": "bar",
>   "1": "baz"
> }
>
> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
> though that's probably not what the author intended. Is there a way to
> avoid
> that?
>
>
> Thanks,
> Markus
>
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> > bounces@ietf.org] On Behalf Of The IESG
> > Sent: Tuesday, December 11, 2012 4:01 PM
> > To: IETF-Announce
> > Cc: apps-discuss@ietf.org
> > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> > 07.txt> (JSON Pointer) to Proposed Standard
> >
> >
> > The IESG has received a request from the Applications Area Working
> > Group
> > WG (appsawg) to consider the following document:
> > - 'JSON Pointer'
> >   <draft-ietf-appsawg-json-pointer-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 2012-12-25. Exceptionally, comments may
> > be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    JSON Pointer defines a string syntax for identifying a specific
> > value
> >    within a JSON document.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

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

<font face=3D"courier new,monospace">JSON Pointer does not distinguish betw=
een objects and arrays. That is not determined until the pointer is applied=
 to an actual object instance... the pointer &quot;/1&quot; is valid agains=
t {&quot;1&quot;:&quot;a&quot;} or [&quot;a&quot;,&quot;b&quot;]</font><div=
 class=3D"gmail_extra">

<br><br><div class=3D"gmail_quote">On Fri, Dec 14, 2012 at 2:51 AM, Markus =
Lanthaler <span dir=3D"ltr">&lt;<a href=3D"mailto:markus.lanthaler@gmx.net"=
 target=3D"_blank">markus.lanthaler@gmx.net</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">

I&#39;ve asked that before but didn&#39;t get an answer. So let me ask agai=
n (even<br>
though I&#39;m quite sure it has already been asked by somebody else).<br>
<br>
How does JSON Pointer distinguish between objects and arrays? E.g. consider=
<br>
the following JSON document:<br>
<br>
{<br>
=C2=A0 &quot;foo&quot;: &quot;bar&quot;,<br>
=C2=A0 &quot;1&quot;: &quot;baz&quot;<br>
}<br>
<br>
As I read the draft, the JSON Pointer &quot;/1&quot; would evaluate to &quo=
t;baz&quot; even<br>
though that&#39;s probably not what the author intended. Is there a way to =
avoid<br>
that?<br>
<br>
<br>
Thanks,<br>
Markus<br>
<br>
<br>
<br>
--<br>
Markus Lanthaler<br>
@markuslanthaler<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: <a href=3D"mailto:apps-discuss-bounces@ietf.org">apps-discuss-bo=
unces@ietf.org</a> [mailto:<a href=3D"mailto:apps-discuss-">apps-discuss-</=
a><br>
&gt; <a href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>] On Behalf Of=
 The IESG<br>
&gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>
&gt; To: IETF-Announce<br>
&gt; Cc: <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>=
<br>
&gt; Subject: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-json-pointer=
-<br>
&gt; 07.txt&gt; (JSON Pointer) to Proposed Standard<br>
&gt;<br>
&gt;<br>
&gt; The IESG has received a request from the Applications Area Working<br>
&gt; Group<br>
&gt; WG (appsawg) to consider the following document:<br>
&gt; - &#39;JSON Pointer&#39;<br>
&gt; =C2=A0 &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; as Proposed Stan=
dard<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=
12-12-25. Exceptionally, comments may<br>
&gt; 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; =C2=A0 =C2=A0JSON Pointer defines a string syntax for identifying a sp=
ecific<br>
&gt; value<br>
&gt; =C2=A0 =C2=A0within a JSON document.<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-ietf-appsawg-json-poi=
nter/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-appsawg=
-json-pointer/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-poi=
nter/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-=
appsawg-json-pointer/ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div></div></blockquote></div><br></div>

--e89a8f6467171c338604d0d2b2c4--

From jasnell@gmail.com  Fri Dec 14 09:18:58 2012
Return-Path: <jasnell@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 0068E21F8A55; Fri, 14 Dec 2012 09:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.697
X-Spam-Level: 
X-Spam-Status: No, score=-3.697 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mh9-VcgxC+q7; Fri, 14 Dec 2012 09:18:57 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9587C21F8A51; Fri, 14 Dec 2012 09:18:55 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so6324513ieb.31 for <multiple recipients>; Fri, 14 Dec 2012 09:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=tbCgJNfktKcobFaaT/Y5VhPBqKb0oJ0vYEJoqqX/zTg=; b=ZpJ2kHiz79ra6OAa7OplaG4IsHH+nrInu0Urkw9aygdC1IOXB8ZARUPwxsSAQwxIR0 UWBMYVGjjHQ68I6krp8ogJQ7f76FKVAE/eXVl8RtIGRwJHXbdRIHT4HoICIIHKMT/LcP r/iYWWU1fHekgMMVG6Ucf6sTps6VLIiIUAPvHjgPr77543LOtETdQDwXdybkfrB9kTr7 kXrNSjkQllVINnrvCDLcjjqTMF9El5VsFYhksCwTxw1nqNO/YFRPKnyugZk9ZB751JTl DfutthAoS3or5D7cEaS77JH5gshVj6npN7xpHwuBN1Xb2ZNhV9IAPs8iGcW42+m3bXVW hN0Q==
Received: by 10.42.41.144 with SMTP id p16mr5048672ice.39.1355505535258; Fri, 14 Dec 2012 09:18:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Fri, 14 Dec 2012 09:18:34 -0800 (PST)
In-Reply-To: <50cb5f33.295eb40a.7e3d.ffff919fSMTPIN_ADDED_BROKEN@mx.google.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f33.295eb40a.7e3d.ffff919fSMTPIN_ADDED_BROKEN@mx.google.com>
From: James M Snell <jasnell@gmail.com>
Date: Fri, 14 Dec 2012 09:18:34 -0800
Message-ID: <CABP7Rbf9cZb1uJrkenxrGH06h-hsWSbG5PXyV6W-3Tm7aER4Ng@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: multipart/alternative; boundary=20cf301d4232eb903c04d0d339b3
X-Mailman-Approved-At: Fri, 14 Dec 2012 09:26:57 -0800
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 17:18:58 -0000

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

How so? Doesn't appear to be a problem in practice.


On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
<markus.lanthaler@gmx.net>wrote:

> Hmm.. I think that=E2=80=99s quite problematic. Especially considering ho=
w JSON
> Pointer is used in JSON Patch.****
>
> ** **
>
> ** **
>
> --****
>
> Markus Lanthaler****
>
> @markuslanthaler****
>
> ** **
>
> ** **
>
> ** **
>
> *From:* James M Snell [mailto:jasnell@gmail.com]
> *Sent:* Friday, December 14, 2012 5:41 PM
> *To:* Markus Lanthaler
> *Cc:* IETF Discussion; IETF Apps Discuss
> *Subject:* Re: [apps-discuss] Last Call:
> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Stand=
ard
> ****
>
> ** **
>
> JSON Pointer does not distinguish between objects and arrays. That is not
> determined until the pointer is applied to an actual object instance... t=
he
> pointer "/1" is valid against {"1":"a"} or ["a","b"]****
>
> ** **
>
> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler <
> markus.lanthaler@gmx.net> wrote:****
>
> I've asked that before but didn't get an answer. So let me ask again (eve=
n
> though I'm quite sure it has already been asked by somebody else).
>
> How does JSON Pointer distinguish between objects and arrays? E.g. consid=
er
> the following JSON document:
>
> {
>   "foo": "bar",
>   "1": "baz"
> }
>
> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
> though that's probably not what the author intended. Is there a way to
> avoid
> that?
>
>
> Thanks,
> Markus
>
>
>
> --
> Markus Lanthaler
> @markuslanthaler****
>
>
>
>
>
> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> > bounces@ietf.org] On Behalf Of The IESG
> > Sent: Tuesday, December 11, 2012 4:01 PM
> > To: IETF-Announce
> > Cc: apps-discuss@ietf.org
> > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> > 07.txt> (JSON Pointer) to Proposed Standard
> >
> >
> > The IESG has received a request from the Applications Area Working
> > Group
> > WG (appsawg) to consider the following document:
> > - 'JSON Pointer'
> >   <draft-ietf-appsawg-json-pointer-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 2012-12-25. Exceptionally, comments may
> > be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    JSON Pointer defines a string syntax for identifying a specific
> > value
> >    within a JSON document.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss****
>
> ** **
>

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

<font face=3D"courier new, monospace">How so? Doesn&#39;t appear to be a pr=
oblem in practice.=C2=A0</font><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:markus.lanthaler@gmx.net" target=3D"_blank=
">markus.lanthaler@gmx.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div lang=3D"DE" link=3D"blue" vlink=3D"purp=
le"><div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Hmm.. I think t=
hat=E2=80=99s quite problematic. Especially considering how JSON Pointer is=
 used in JSON Patch.<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;"><u></u>=C2=A0<u></u></span></p><p class=
=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>

<div><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">--<u></u><u></u></s=
pan></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Markus Lanthaler=
<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;">@markuslanthaler</span><=
span style=3D"font-size:10.5pt;font-family:Consolas"><u></u><u></u></span><=
/p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></sp=
an></p><p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0p=
t;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u><=
/u></span></p>

<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><u></u>=C2=A0<u></u></sp=
an></p><div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0=
cm 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 style=3D"font-size:10.0pt;fon=
t-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span s=
tyle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&qu=
ot;"> James M Snell [mailto:<a href=3D"mailto:jasnell@gmail.com" target=3D"=
_blank">jasnell@gmail.com</a>] <br>

<b>Sent:</b> Friday, December 14, 2012 5:41 PM<br><b>To:</b> Markus Lanthal=
er<br><b>Cc:</b> IETF Discussion; IETF Apps Discuss<br><b>Subject:</b> Re: =
[apps-discuss] Last Call: &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; (J=
SON Pointer) to Proposed Standard<u></u><u></u></span></p>

</div></div><div><div class=3D"h5"><p class=3D"MsoNormal"><u></u>=C2=A0<u><=
/u></p><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&=
quot;">JSON Pointer does not distinguish between objects and arrays. That i=
s not determined until the pointer is applied to an actual object instance.=
.. the pointer &quot;/1&quot; is valid against {&quot;1&quot;:&quot;a&quot;=
} or [&quot;a&quot;,&quot;b&quot;]</span><u></u><u></u></p>

<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=C2=A0<u>=
</u></p><div><p class=3D"MsoNormal">On Fri, Dec 14, 2012 at 2:51 AM, Markus=
 Lanthaler &lt;<a href=3D"mailto:markus.lanthaler@gmx.net" target=3D"_blank=
">markus.lanthaler@gmx.net</a>&gt; wrote:<u></u><u></u></p>

<p class=3D"MsoNormal">I&#39;ve asked that before but didn&#39;t get an ans=
wer. So let me ask again (even<br>though I&#39;m quite sure it has already =
been asked by somebody else).<br><br>How does JSON Pointer distinguish betw=
een objects and arrays? E.g. consider<br>

the following JSON document:<br><br>{<br>=C2=A0 &quot;foo&quot;: &quot;bar&=
quot;,<br>=C2=A0 &quot;1&quot;: &quot;baz&quot;<br>}<br><br>As I read the d=
raft, the JSON Pointer &quot;/1&quot; would evaluate to &quot;baz&quot; eve=
n<br>
though that&#39;s probably not what the author intended. Is there a way to =
avoid<br>
that?<br><br><br>Thanks,<br>Markus<br><br><br><br>--<br>Markus Lanthaler<br=
>@markuslanthaler<u></u><u></u></p><div><div><p class=3D"MsoNormal"><br><br=
><br><br>&gt; -----Original Message-----<br>&gt; From: <a href=3D"mailto:ap=
ps-discuss-bounces@ietf.org" target=3D"_blank">apps-discuss-bounces@ietf.or=
g</a> [mailto:<a href=3D"mailto:apps-discuss-" target=3D"_blank">apps-discu=
ss-</a><br>

&gt; <a href=3D"mailto:bounces@ietf.org" target=3D"_blank">bounces@ietf.org=
</a>] On Behalf Of The IESG<br>&gt; Sent: Tuesday, December 11, 2012 4:01 P=
M<br>&gt; To: IETF-Announce<br>&gt; Cc: <a href=3D"mailto:apps-discuss@ietf=
.org" target=3D"_blank">apps-discuss@ietf.org</a><br>

&gt; Subject: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-json-pointer=
-<br>&gt; 07.txt&gt; (JSON Pointer) to Proposed Standard<br>&gt;<br>&gt;<br=
>&gt; The IESG has received a request from the Applications Area Working<br=
>

&gt; Group<br>&gt; WG (appsawg) to consider the following document:<br>&gt;=
 - &#39;JSON Pointer&#39;<br>&gt; =C2=A0 &lt;draft-ietf-appsawg-json-pointe=
r-07.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" target=3D"_blank">ietf@ietf.org</=
a> mailing lists by 2012-12-25. Exceptionally, comments may<br>&gt; be<br>
&gt; sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.o=
rg</a> instead. In either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>&gt;<br>&=
gt; Abstract<br>&gt;<br>&gt;<br>&gt; =C2=A0 =C2=A0JSON Pointer defines a st=
ring syntax for identifying a specific<br>&gt; value<br>&gt; =C2=A0 =C2=A0w=
ithin a JSON document.<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-ietf-appsawg-json-pointer/"=
 target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-=
pointer/</a><br>

&gt;<br>&gt; IESG discussion can be tracked via<br>&gt; <a href=3D"http://d=
atatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/" target=3D"=
_blank">http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/bal=
lot/</a><br>

&gt;<br>&gt;<br>&gt; No IPR declarations have been submitted directly on th=
is I-D.<br>&gt;<br>&gt;<br>&gt; ___________________________________________=
____<br>&gt; apps-discuss mailing list<br>&gt; <a href=3D"mailto:apps-discu=
ss@ietf.org" target=3D"_blank">apps-discuss@ietf.org</a><br>

&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br><br>_=
______________________________________________<br>apps-discuss mailing list=
<br>

<a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discuss@iet=
f.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><u=
></u><u></u></p>

</div></div></div><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p></div></di=
v></div></div></div></div></blockquote></div><br></div>

--20cf301d4232eb903c04d0d339b3--

From David.Biesack@sas.com  Fri Dec 14 08:46:04 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF25921F89C1 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 08:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=1.110,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMkE40z5at9J for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 08:46:04 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe002.messaging.microsoft.com [216.32.181.182]) by ietfa.amsl.com (Postfix) with ESMTP id CB40521F89C0 for <ietf@ietf.org>; Fri, 14 Dec 2012 08:46:00 -0800 (PST)
Received: from mail261-ch1-R.bigfish.com (10.43.68.231) by CH1EHSOBE011.bigfish.com (10.43.70.61) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 16:45:59 +0000
Received: from mail261-ch1 (localhost [127.0.0.1])	by mail261-ch1-R.bigfish.com (Postfix) with ESMTP id E30A96401A6	for <ietf@ietf.org>; Fri, 14 Dec 2012 16:45:59 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.149; KIP:(null); UIP:(null); IPV:NLI; H:mercav05r.na.sas.com; RD:mercav05r.na.sas.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: S0(zzzz1de0h1202h1e76h1d1ah1d2ahzz18602eh8275bhz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail261-ch1: domain of sas.com designates 149.173.6.149 as permitted sender) client-ip=149.173.6.149; envelope-from=David.Biesack@sas.com; helo=mercav05r.na.sas.com ; r.na.sas.com ; 
Received: from mail261-ch1 (localhost.localdomain [127.0.0.1]) by mail261-ch1 (MessageSwitch) id 1355503552656522_22007; Fri, 14 Dec 2012 16:45:52 +0000 (UTC)
Received: from CH1EHSMHS029.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.227])	by mail261-ch1.bigfish.com (Postfix) with ESMTP id 8F63694004D	for <ietf@ietf.org>; Fri, 14 Dec 2012 16:45:52 +0000 (UTC)
Received: from mercav05r.na.sas.com (149.173.6.149) by CH1EHSMHS029.bigfish.com (10.43.70.29) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 16:45:52 +0000
X-TM-IMSS-Message-ID: <9a9025110021d431@mercav05r.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav05r.na.sas.com ([10.16.10.186]) with ESMTP (TREND IMSS SMTP Service 7.1) id 9a9025110021d431 ; Fri, 14 Dec 2012 11:45:49 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
Date: Fri, 14 Dec 2012 11:45:47 -0500
Message-ID: <p1txrolgzo.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 14 Dec 2012 18:07:59 -0000

"4.1 add" bullet 3 reads (when completing the introductory sentence)

 ... the target location MUST reference ...
 o An element to add to an existing array.

I think this is incorrect; the target location is the array and the "value" is the "element to add to an existing array". I suggest:

 ... the target location MUST reference ...
 o An existing array.

-- 
David J. Biesack | Principal API Architect, SAS | @davidbiesack | 919-531-7771 | www.sas.com


From David.Biesack@sas.com  Fri Dec 14 09:13:31 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B6621F855B for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:13:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.044
X-Spam-Level: 
X-Spam-Status: No, score=-3.044 tagged_above=-999 required=5 tests=[AWL=0.555,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CrJLxiXMEhju for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:13:29 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe004.messaging.microsoft.com [213.199.154.207]) by ietfa.amsl.com (Postfix) with ESMTP id 64F0621F8467 for <ietf@ietf.org>; Fri, 14 Dec 2012 09:13:16 -0800 (PST)
Received: from mail70-am1-R.bigfish.com (10.3.201.247) by AM1EHSOBE005.bigfish.com (10.3.204.25) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 17:13:15 +0000
Received: from mail70-am1 (localhost [127.0.0.1])	by mail70-am1-R.bigfish.com (Postfix) with ESMTP id 66E8E3E028F	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:13:15 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.149; KIP:(null); UIP:(null); IPV:NLI; H:mercav05r.na.sas.com; RD:mercav05r.na.sas.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: S0(zzzz1de0h1202h1e76h1d1ah1d2ahzz18602eh8275bhz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail70-am1: domain of sas.com designates 149.173.6.149 as permitted sender) client-ip=149.173.6.149; envelope-from=David.Biesack@sas.com; helo=mercav05r.na.sas.com ; r.na.sas.com ; 
Received: from mail70-am1 (localhost.localdomain [127.0.0.1]) by mail70-am1 (MessageSwitch) id 1355505193673164_18133; Fri, 14 Dec 2012 17:13:13 +0000 (UTC)
Received: from AM1EHSMHS017.bigfish.com (unknown [10.3.201.230])	by mail70-am1.bigfish.com (Postfix) with ESMTP id A28172C03D1	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:13:13 +0000 (UTC)
Received: from mercav05r.na.sas.com (149.173.6.149) by AM1EHSMHS017.bigfish.com (10.3.207.155) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 17:13:13 +0000
X-TM-IMSS-Message-ID: <9aa92e5e0021db26@mercav05r.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav05r.na.sas.com ([10.16.10.186]) with ESMTP (TREND IMSS SMTP Service 7.1) id 9aa92e5e0021db26 ; Fri, 14 Dec 2012 12:13:10 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
Date: Fri, 14 Dec 2012 12:13:07 -0500
Message-ID: <p1sj78lfq4.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 14 Dec 2012 18:15:14 -0000

"4.1 add" and "4.2 remove" refers to "specified index", but I do not see name of the index member specified in the draft, or how to represent it.
(Other sections are more explicit, i.e. "from" for the "move" op.)

i.e. "index" as in 

  "index" : integer 

The phrasing 

   If the "-" character is used to index the end of the array, this has the effect of appending the value to the array.

is not clear. Where does this "-" character appear? Does one use just

  "index" : "-" 

in which case the spec should be 

  If the "-" string is used ...

If instead you mean a negative integer, i.e.

  "index" : negative-integer

and not just "-", does the spec interpret all negative integers to indicate appending to the end?

I'd prefer the value not have two separate types, integer vs. string.

Suggestion: allow negative numbers to indicate a position counted from the end of the array i.e. -1 to append, -2 to insert before the last item, and so on. E.g. after appending to an array of length l at i < 0, the item will be at the zero-based index (l + 1) + i. Error if |i| > l

E.g. given the document with an array of length 4:

{ "a" : [ 0, 1, 2, 3, ] }

then 

{ "op" : "add", "path" : "a", "value" : 99, "index" : -1 }

yields

{ "a" : [ 0, 1, 2, 3, 99] }

i.e. 99 is found at (4 + 1) -1 == 4

{ "op" : "add", "path" : "a", "value" : 99, "index" : -2 }

yields

{ "a" : [ 0, 1, 2, 99, 3] }

i.e. 99 is found at (4 + 1) -2 == 3

and finally

{ "op" : "add", "path" : "a", "value" : 99, "index" : -5 }

yields

{ "a" : [ 99, 0, 1, 2,, 3] }

i.e. 99 is found at (4 + 1) -5 == 0

-- 
David J. Biesack | Principal API Architect, SAS | @davidbiesack | 919-531-7771 | www.sas.com


From David.Biesack@sas.com  Fri Dec 14 09:27:42 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2EF321F8B22 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.729
X-Spam-Level: 
X-Spam-Status: No, score=-4.729 tagged_above=-999 required=5 tests=[AWL=1.870,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-QaR-PQOHKD for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:27:42 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe004.messaging.microsoft.com [207.46.163.27]) by ietfa.amsl.com (Postfix) with ESMTP id B1EB621F8B04 for <ietf@ietf.org>; Fri, 14 Dec 2012 09:27:40 -0800 (PST)
Received: from mail174-co9-R.bigfish.com (10.236.132.247) by CO9EHSOBE020.bigfish.com (10.236.130.83) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 17:27:40 +0000
Received: from mail174-co9 (localhost [127.0.0.1])	by mail174-co9-R.bigfish.com (Postfix) with ESMTP id 070909801B7	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:27:40 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.147; KIP:(null); UIP:(null); IPV:NLI; H:mercav04d.na.sas.com; RD:mercav04d.na.sas.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: S0(zzzz1de0h1202h1e76h1d1ah1d2ahzz18602eh8275bhz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail174-co9: domain of sas.com designates 149.173.6.147 as permitted sender) client-ip=149.173.6.147; envelope-from=David.Biesack@sas.com; helo=mercav04d.na.sas.com ; d.na.sas.com ; 
Received: from mail174-co9 (localhost.localdomain [127.0.0.1]) by mail174-co9 (MessageSwitch) id 1355506057496272_1377; Fri, 14 Dec 2012 17:27:37 +0000 (UTC)
Received: from CO9EHSMHS016.bigfish.com (unknown [10.236.132.226])	by mail174-co9.bigfish.com (Postfix) with ESMTP id 6AEF5340043	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:27:37 +0000 (UTC)
Received: from mercav04d.na.sas.com (149.173.6.147) by CO9EHSMHS016.bigfish.com (10.236.130.26) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 17:27:37 +0000
X-TM-IMSS-Message-ID: <9a4eb1c20019a0a2@mercav04d.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav04d.na.sas.com ([10.36.10.9]) with ESMTP (TREND IMSS SMTP Service 7.1) id 9a4eb1c20019a0a2 ; Fri, 14 Dec 2012 12:27:34 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
Date: Fri, 14 Dec 2012 12:27:32 -0500
Message-ID: <p1r4mslf23.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 14 Dec 2012 18:16:08 -0000

Can one add elements of array to an array? 

E.g. given the document

 { "a" : { "b" : [ "red", "green" ] } }

If I want to add two values to an existing array, I can use

[
 { "op": "add", "path": "/a/b/-", "value": "blue" },
 { "op": "add", "path": "/a/b/-", "value": "yellow" }
]

(I found in the examples how an array index is specified in the path, not in a separate "index" member;
I guess my comments there should be directed at draft-ietf-appsawg-json-pointer-06 )

However, for appending to arrays, I would like to use

[ { "op": "add", "path": "/a/b/-", "value": [ "blue", "yellow" ] } ]

Reading the spec literally, I expect that this will yield

 { "a" : { "b" : [ "red", "green", [ "blue", "yellow" ] ] } }

instead of the desired

 { "a" : { "b" : [ "red", "green", "blue", "yellow" ] } }

I suggest the semantics of this case should be explicit, to avoid unexpected surprises.

-- 
David J. Biesack | Principal API Architect, SAS | @davidbiesack | 919-531-7771 | www.sas.com


From David.Biesack@sas.com  Fri Dec 14 09:54:26 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2348B21F8A05 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.677
X-Spam-Level: 
X-Spam-Status: No, score=-3.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXcPzq+Ap2Ry for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:54:25 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB7B21F89A9 for <ietf@ietf.org>; Fri, 14 Dec 2012 09:54:25 -0800 (PST)
Received: from mail26-ch1-R.bigfish.com (10.43.68.234) by CH1EHSOBE007.bigfish.com (10.43.70.57) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 17:54:24 +0000
Received: from mail26-ch1 (localhost [127.0.0.1])	by mail26-ch1-R.bigfish.com (Postfix) with ESMTP id 788674A024D	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:54:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.147; KIP:(null); UIP:(null); IPV:NLI; H:mercav04d.na.sas.com; RD:mercav04d.na.sas.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: S0(zzzz1de0h1202h1e76h1d1ah1d2ahzz18602eh8275bhz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail26-ch1: domain of sas.com designates 149.173.6.147 as permitted sender) client-ip=149.173.6.147; envelope-from=David.Biesack@sas.com; helo=mercav04d.na.sas.com ; d.na.sas.com ; 
Received: from mail26-ch1 (localhost.localdomain [127.0.0.1]) by mail26-ch1 (MessageSwitch) id 1355507662705851_24075; Fri, 14 Dec 2012 17:54:22 +0000 (UTC)
Received: from CH1EHSMHS023.bigfish.com (snatpool3.int.messaging.microsoft.com [10.43.68.228])	by mail26-ch1.bigfish.com (Postfix) with ESMTP id A9E37160062 for <ietf@ietf.org>; Fri, 14 Dec 2012 17:54:22 +0000 (UTC)
Received: from mercav04d.na.sas.com (149.173.6.147) by CH1EHSMHS023.bigfish.com (10.43.70.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 17:54:21 +0000
X-TM-IMSS-Message-ID: <9a672f980019a396@mercav04d.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav04d.na.sas.com ([10.36.10.9]) with ESMTP (TREND IMSS SMTP Service 7.1) id 9a672f980019a396 ; Fri, 14 Dec 2012 12:54:20 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: <ietf@ietf.org>
Subject: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
Date: Fri, 14 Dec 2012 12:54:17 -0500
Message-ID: <p1obhwldti.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 14 Dec 2012 18:16:36 -0000

I originally posted this in a "Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard" thread
but now I've read draft-ietf-appsawg-json-pointer-07 and have changed that suggestion to reflect draft-ietf-appsawg-json-pointer-07

Suggestion: allow negative numbers to indicate a position counted from the end of the array instead "array/-".

For example, a/-1 to point to the last item in an array (length > 0), -2 to point to the penultimate item, and so on. 
The notation -i is an alias for (array.length - i)

It is an error if |i| > array length.

For the json-patch "add" operation, use 

   { "op" : "add", "path" : "...array/-1", "value" : value } 

to append to the end, "...array/-2" to insert before the last item, and so on.
The "path" is the path that the item will be addressed by after inserting it.
I.e. after appending to an array of length l at j < 0, the item will be at the zero-based index (l + 1) + j. 

E.g. given the document with an array of length 4:

{ "a" : [ 0, 1, 2, 3, ] }

then 

{ "op" : "add", "path" : "/a/-1", "value" : 99 }

yields

{ "a" : [ 0, 1, 2, 3, 99] }

i.e. 99 is found at (4 + 1) -1 == 4


{ "op" : "add", "path" : "/a/-2", "value" : 99}

yields

{ "a" : [ 0, 1, 2, 99, 3] }

i.e. 99 is found at (4 + 1) -2 == 3

and finally

{ "op" : "add", "path" : "/a/-5", "value" : 99 }

yields

{ "a" : [ 99, 0, 1, 2, 3] }

i.e. 99 is found at (4 + 1) -5 == 0

-- 
David J. Biesack | Principal API Architect, SAS | @davidbiesack | 919-531-7771 | www.sas.com


From David.Biesack@sas.com  Fri Dec 14 09:34:23 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EEC21F8A75 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:34:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.697
X-Spam-Level: 
X-Spam-Status: No, score=-3.697 tagged_above=-999 required=5 tests=[AWL=-0.098, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KMzl61ydXQgC for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:34:22 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id 8117F21F8A6B for <ietf@ietf.org>; Fri, 14 Dec 2012 09:34:22 -0800 (PST)
Received: from mail218-ch1-R.bigfish.com (10.43.68.251) by CH1EHSOBE004.bigfish.com (10.43.70.54) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 17:34:21 +0000
Received: from mail218-ch1 (localhost [127.0.0.1])	by mail218-ch1-R.bigfish.com (Postfix) with ESMTP id BFA943002B0	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:34:21 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.148; KIP:(null); UIP:(null); IPV:NLI; H:mercav06d.na.sas.com; RD:mercav06d.na.sas.com; EFVD:NLI
X-SpamScore: 0
X-BigFish: S0(zzzz1de0h1202h1e76h1d1ah1d2ahzz18602eh8275bhz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail218-ch1: domain of sas.com designates 149.173.6.148 as permitted sender) client-ip=149.173.6.148; envelope-from=David.Biesack@sas.com; helo=mercav06d.na.sas.com ; d.na.sas.com ; 
Received: from mail218-ch1 (localhost.localdomain [127.0.0.1]) by mail218-ch1 (MessageSwitch) id 1355506459672287_18574; Fri, 14 Dec 2012 17:34:19 +0000 (UTC)
Received: from CH1EHSMHS031.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.243])	by mail218-ch1.bigfish.com (Postfix) with ESMTP id 98046220149	for <ietf@ietf.org>; Fri, 14 Dec 2012 17:34:19 +0000 (UTC)
Received: from mercav06d.na.sas.com (149.173.6.148) by CH1EHSMHS031.bigfish.com (10.43.70.31) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 17:34:19 +0000
X-TM-IMSS-Message-ID: <95f13603001e1b70@mercav06d.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav06d.na.sas.com ([10.36.10.11]) with ESMTP (TREND IMSS SMTP Service 7.1) id 95f13603001e1b70 ; Fri, 14 Dec 2012 12:34:17 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
Date: Fri, 14 Dec 2012 12:34:14 -0500
Message-ID: <p1pq2cleqx.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 14 Dec 2012 18:17:20 -0000

"4.4.  move" states

   The target location MUST NOT be part of the location defined by
   "from"; i.e., a location cannot be moved into one of its children.

This constraint is backwards. I.e. to disallow moving into a child, 

 { "op": "move", "from": "/a/b/c", "path": "/a/b/c/d" }

this should read:

   The "from" location MUST NOT be a proper prefix of the "path" location;
   i.e., a location cannot be moved into one of its children.

I suggest using "proper prefix" instead of just "part of". For example,
"/a/b/c" is "part of" "q/a/b/c" but such a move should be allowed
because it is not a proper prefix.

As currently stated, moving a value UP would be disallowed. Below, the target location is part of the "from" :

 { "op": "move", "from": "/a/b/c/d", "path": "/a/b/c" }

-- 
David J. Biesack | Principal API Architect, SAS | @davidbiesack | 919-531-7771 | www.sas.com


From David.Biesack@sas.com  Fri Dec 14 10:37:55 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CDC321F8A7C for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 10:37:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.831
X-Spam-Level: 
X-Spam-Status: No, score=-4.831 tagged_above=-999 required=5 tests=[AWL=1.768,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aj0+KjpdwX8B for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 10:37:54 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7F3E721F8A75 for <ietf@ietf.org>; Fri, 14 Dec 2012 10:37:54 -0800 (PST)
Received: from mail199-co9-R.bigfish.com (10.236.132.249) by CO9EHSOBE014.bigfish.com (10.236.130.77) with Microsoft SMTP Server id 14.1.225.23; Fri, 14 Dec 2012 18:37:51 +0000
Received: from mail199-co9 (localhost [127.0.0.1])	by mail199-co9-R.bigfish.com (Postfix) with ESMTP id AD2FC5C005F	for <ietf@ietf.org>; Fri, 14 Dec 2012 18:37:51 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.147; KIP:(null); UIP:(null); IPV:NLI; H:mercav04d.na.sas.com; RD:mercav04d.na.sas.com; EFVD:NLI
X-SpamScore: -1
X-BigFish: S-1(zz1432Izz1de0h1202h1e76h1d1ah1d2ahzz18602eh8275bhz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail199-co9: domain of sas.com designates 149.173.6.147 as permitted sender) client-ip=149.173.6.147; envelope-from=David.Biesack@sas.com; helo=mercav04d.na.sas.com ; d.na.sas.com ; 
Received: from mail199-co9 (localhost.localdomain [127.0.0.1]) by mail199-co9 (MessageSwitch) id 1355510269957031_9387; Fri, 14 Dec 2012 18:37:49 +0000 (UTC)
Received: from CO9EHSMHS032.bigfish.com (unknown [10.236.132.247])	by mail199-co9.bigfish.com (Postfix) with ESMTP id DDB53440231	for <ietf@ietf.org>; Fri, 14 Dec 2012 18:37:49 +0000 (UTC)
Received: from mercav04d.na.sas.com (149.173.6.147) by CO9EHSMHS032.bigfish.com (10.236.130.42) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 14 Dec 2012 18:37:49 +0000
X-TM-IMSS-Message-ID: <9a8ef54b0019abec@mercav04d.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav04d.na.sas.com ([10.36.10.9]) with ESMTP (TREND IMSS SMTP Service 7.1) id 9a8ef54b0019abec ; Fri, 14 Dec 2012 13:37:46 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
Date: Fri, 14 Dec 2012 13:37:43 -0500
Message-ID: <p14njolbt4.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 14 Dec 2012 18:37:55 -0000

I wrote previously :

> "4.1 add" bullet 3 reads (when completing the introductory sentence) 
>  
> ... the target location MUST reference ... 
> o An element to add to an existing array. 
>  
> I think this is incorrect; the target location is the array and the "value" is the "element to add to an existing array". I suggest: 
>  
> ... the target location MUST reference ... 
> o An existing array. 

but now I see my error; the examples at the bottom of the doc clarify
the JSON-Pointer location using the form "/path/to/array/index", so the original
wording is correct. Sorry for the noise.

djb
-- 
David J. Biesack | Principal API Architect, SAS | @davidbiesack | 919-531-7771 | www.sas.com


From john-ietf@jck.com  Fri Dec 14 15:09:58 2012
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 8D73621F8AB9 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 15:09:58 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bq2hzDmviO-7 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 15:09:57 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 85F1421F8AAC for <ietf@ietf.org>; Fri, 14 Dec 2012 15:09:57 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TjeOC-0000kT-Fq for ietf@ietf.org; Fri, 14 Dec 2012 18:09:56 -0500
Date: Fri, 14 Dec 2012 18:09:51 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: The notion of "fast tracking" drafts (was: Re: Running code, take 2)
Message-ID: <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com>
In-Reply-To: <50CB273D.3070208@cs.tcd.ie>
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 23:09:58 -0000

Hi.

I've been trying to say out of this because I think most of the
suggestions are better carried out by AD-encouraged experiments
and reports to the rest of us on effectiveness rather than by
long discussions in the community about details and the costs of
an unnecessary consensus process. 

However, since I gather we are pushing (or being pushed) down
this path, let me suggest that approval of an IETF spec,
especially a standards-track one, has (or should have) elements
of all of the following:

(1) A conviction that the idea is implementable and that the
ideas expressed are consistent with implementation (and,
ideally, operational realities.

(2) Specification of sufficient quality to make
independently-developed interoperable implementations by people
who were not part of the WG or development process possible and
specifically that there are no ambiguities that could adversely
affect interoperable implementations.  This includes, but is not
limited to, editorial quality in terms of good technical
English, but does not include "good idea" criteria (see (4)).

(3) "No known technical defects" in the spec (the RFC 2026
requirement).  Note that, while an implementation might turn up
technical defects that might otherwise be unknown, it might
easily not turn up ones that could be identified in other ways.
It should imply a fairly comprehensive review that would have a
high likelihood of turning up any technical defects that are
present, but we all know that sometimes doesn't happen.

(4) Some level of IETF consensus that publishing the
specification has value for the community.  This might or might
not include a community belief that the document specifies a
good idea that should be implemented and deployed (the latter is
why we have Applicability Statements).

While I hope the above is obvious, the four categories are
nearly orthogonal.   One can have a good specification and a
worthwhile idea without an implementation, an implementation of
a bad idea and a lousy specification, and so on.   I believe...

(i) It is a bad idea, and could be a real disservice to the
community, to say that meeting a high standard on any one of
those dimensions should allow some of the others to be dealt
with in a perfunctory fashion.  That is exactly what a "fast
track" idea seems to be about and much of the debate seem to be
about how high a standard is relevant.

(ii) If it were really acceptable to decide that an
implementation (i.e., a limited demonstration of the first
criterion) justifies a "fast track", then demonstrations of the
others should to.  For example, if a WG could demonstrate that
the specification had been carefully and professionally
technically edited, perhaps that should justify "fast track"
treatment.  If there is already wide and successful deployment
of what is supposedly the specification, leaving aside the
question of whether those deployments and the specification
actually match, perhaps that should justify "fast track"
treatment.  If the review of the specification in a WG had been
particularly intense, including careful looks by many diverse
parties, perhaps that should justify "fast track" treatment.

I'm not certain what makes having an implementation more special
than any of these other categories and, to the extent to which
"fast track" means "less review" or a "higher bar to comments",
the idea makes me really, really, nervous, especially if the
requirement is not for a production-quality implementation that
has been tested both for interoperability and through deployment
to users.

   john


From john-ietf@jck.com  Fri Dec 14 15:15:38 2012
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 9807F21F8AEC for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 15:15:38 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MAHPK20moiB for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 15:15:38 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1BBDE21F8AB9 for <ietf@ietf.org>; Fri, 14 Dec 2012 15:15:38 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TjeTg-0000lD-LH; Fri, 14 Dec 2012 18:15:36 -0500
Date: Fri, 14 Dec 2012 18:15:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Running code, take 2
Message-ID: <C49D02AFB5025BD44B8E1EA1@JcK-HP8200.jck.com>
In-Reply-To: <50CAE81A.4040807@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@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: Fri, 14 Dec 2012 23:15:38 -0000

--On Friday, December 14, 2012 10:49 +0200 Yaron Sheffer
<yaronf.ietf@gmail.com> wrote:

>... 
> The value in a 3933 experiment is in the Summary Report,
> otherwise I agree it's a waste of time. At the end of the
> period we will have a little bit of data to understand whether
> we have traction for this idea, and whether we should make it
> IETF-wide, allow it to quietly die or explicitly advise
> against it.

I would encourage anyone who believes in "running code" wrt IETF
processes and who is willing to argue that one of the current
proposals should be adopted because there is real value in the
Summary Reports called for by 3933 to compile a list of 

	* 3933 Experiments
	* The published summary reports for each
	* How and where they found those reports.
	
I predict the results will be enlightening.  :-(

   john


From stephen.farrell@cs.tcd.ie  Sat Dec 15 06:59:06 2012
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 4BD6D21F85E6 for <ietf@ietfa.amsl.com>; Sat, 15 Dec 2012 06:59:06 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JzXaPYPvFpDw for <ietf@ietfa.amsl.com>; Sat, 15 Dec 2012 06:59:05 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6843221F85DF for <ietf@ietf.org>; Sat, 15 Dec 2012 06:59:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 844E0BE39; Sat, 15 Dec 2012 14:58:36 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qSY9lAJaHRTX; Sat, 15 Dec 2012 14:58:35 +0000 (GMT)
Received: from [10.87.48.8] (unknown [86.45.61.73]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 56EC4BDC7; Sat, 15 Dec 2012 14:58:35 +0000 (GMT)
Message-ID: <50CC901A.7090904@cs.tcd.ie>
Date: Sat, 15 Dec 2012 14:58:34 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: The notion of "fast tracking" drafts
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@cs.tcd.ie> <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com>
In-Reply-To: <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Dec 2012 14:59:06 -0000

Hiya,

On 12/14/2012 11:09 PM, John C Klensin wrote:
> Hi.
> 
> I've been trying to say out of this because I think most of the
> suggestions are better carried out by AD-encouraged experiments
> and reports to the rest of us on effectiveness rather than by
> long discussions in the community about details and the costs of
> an unnecessary consensus process. 

That's a defensible opinion that I don't share. I'd say
s/most/many/ above would be better, but also think that we
ought try break this logjam where everything that touches
on process has to involve a gigantic debate with all the
usual suspects. (I don't foresee success in breaking that
logjam, but do think we ought not let it prevent us trying
things.)

I also think that since my proposal has a corner case where
a WG chair gets to put a draft on the IESG telechat agenda
that that ought only be done after some form of IETF LC.

> However, since I gather we are pushing (or being pushed) down
> this path, let me suggest that approval of an IETF spec,
> especially a standards-track one, has (or should have) elements
> of all of the following:

Luckily my draft says that: "All other criteria for Proposed
Standard or Experimental need to be met as usual." So I've no
idea how the text below is relevant.

Cheers,
S.

> 
> (1) A conviction that the idea is implementable and that the
> ideas expressed are consistent with implementation (and,
> ideally, operational realities.
> 
> (2) Specification of sufficient quality to make
> independently-developed interoperable implementations by people
> who were not part of the WG or development process possible and
> specifically that there are no ambiguities that could adversely
> affect interoperable implementations.  This includes, but is not
> limited to, editorial quality in terms of good technical
> English, but does not include "good idea" criteria (see (4)).
> 
> (3) "No known technical defects" in the spec (the RFC 2026
> requirement).  Note that, while an implementation might turn up
> technical defects that might otherwise be unknown, it might
> easily not turn up ones that could be identified in other ways.
> It should imply a fairly comprehensive review that would have a
> high likelihood of turning up any technical defects that are
> present, but we all know that sometimes doesn't happen.
> 
> (4) Some level of IETF consensus that publishing the
> specification has value for the community.  This might or might
> not include a community belief that the document specifies a
> good idea that should be implemented and deployed (the latter is
> why we have Applicability Statements).
> 
> While I hope the above is obvious, the four categories are
> nearly orthogonal.   One can have a good specification and a
> worthwhile idea without an implementation, an implementation of
> a bad idea and a lousy specification, and so on.   I believe...
> 
> (i) It is a bad idea, and could be a real disservice to the
> community, to say that meeting a high standard on any one of
> those dimensions should allow some of the others to be dealt
> with in a perfunctory fashion.  That is exactly what a "fast
> track" idea seems to be about and much of the debate seem to be
> about how high a standard is relevant.
> 
> (ii) If it were really acceptable to decide that an
> implementation (i.e., a limited demonstration of the first
> criterion) justifies a "fast track", then demonstrations of the
> others should to.  For example, if a WG could demonstrate that
> the specification had been carefully and professionally
> technically edited, perhaps that should justify "fast track"
> treatment.  If there is already wide and successful deployment
> of what is supposedly the specification, leaving aside the
> question of whether those deployments and the specification
> actually match, perhaps that should justify "fast track"
> treatment.  If the review of the specification in a WG had been
> particularly intense, including careful looks by many diverse
> parties, perhaps that should justify "fast track" treatment.
> 
> I'm not certain what makes having an implementation more special
> than any of these other categories and, to the extent to which
> "fast track" means "less review" or a "higher bar to comments",
> the idea makes me really, really, nervous, especially if the
> requirement is not for a production-quality implementation that
> has been tested both for interoperability and through deployment
> to users.
> 
>    john
> 
> 

From yaronf.ietf@gmail.com  Sat Dec 15 08:03:29 2012
Return-Path: <yaronf.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 DE64121F84E3 for <ietf@ietfa.amsl.com>; Sat, 15 Dec 2012 08:03:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.516
X-Spam-Level: 
X-Spam-Status: No, score=-103.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcG0bO7I9Fe2 for <ietf@ietfa.amsl.com>; Sat, 15 Dec 2012 08:03:29 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2148821F84D7 for <ietf@ietf.org>; Sat, 15 Dec 2012 08:03:28 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so2548121eek.31 for <ietf@ietf.org>; Sat, 15 Dec 2012 08:03:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=G80kqoLh3fjkStTLodj/XqpZaZ/fJczqH/CaV3o4nsM=; b=qZxINktBfweoIzspjqdvE9iTusf12E2BIdsOoDXKl3Yl7ObmYIxvZffAGAAik5vw/Q 7h5PDiyiaNWLYUTzMSiylqvVG5XVCrLtIlnZzmGnbL9E72wuPursgK8Sj46oply/959b rU5wG0RRWArmOTc/4Qa4oZsKxInPM1iT+6uhPhuzkXEq2+a8aGqfIeSCTDJskZ0q1rJL Y3x/SGA+Kf/0oKGmANeqZHgiFa/PG6P6mRyrHqaHdpMK036YcswQj7yp6YzTSItvTdOM TKhRtFZl2YeRBIOQKcprnLBEIvqi0ZM8YhLzVX5cbNO78zYoIgE6lBpIkdO0VawYZvz6 w1Ng==
Received: by 10.14.194.199 with SMTP id m47mr24816118een.11.1355587408273; Sat, 15 Dec 2012 08:03:28 -0800 (PST)
Received: from [10.0.0.3] (bzq-79-179-146-198.red.bezeqint.net. [79.179.146.198]) by mx.google.com with ESMTPS id f49sm16674451eep.12.2012.12.15.08.03.25 (version=SSLv3 cipher=OTHER); Sat, 15 Dec 2012 08:03:27 -0800 (PST)
Message-ID: <50CC9F47.8080905@gmail.com>
Date: Sat, 15 Dec 2012 18:03:19 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Running code, take 2
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@gmail.com> <C49D02AFB5025BD44B8E1EA1@JcK-HP8200.jck.com>
In-Reply-To: <C49D02AFB5025BD44B8E1EA1@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: Sat, 15 Dec 2012 16:03:30 -0000

Hi John,

According to Google, exactly one such report was issued: 
http://tools.ietf.org/html/draft-yevstifeyev-ion-report-06 (the 
published RFC omitted the results of the experiment, somehow). And this 
particular experiment is not even mentioned in 
http://www.ietf.org/iesg/process-experiment.html. Two other experiments 
are listed, and I was unable to find any reports summarizing them.

So I'm willing to concede that the "process experiment" experiment 
failed. But since I think it *could have been* a valuable process, and 
since I'm seeing an IESG member proposing to use it, I would request to 
hear from the IESG if they think RFC 3933 is still a management tool 
they'd like to use.

Thanks,
	Yaron


On 12/15/2012 01:15 AM, John C Klensin wrote:
>
>
> --On Friday, December 14, 2012 10:49 +0200 Yaron Sheffer
> <yaronf.ietf@gmail.com> wrote:
>
>> ...
>> The value in a 3933 experiment is in the Summary Report,
>> otherwise I agree it's a waste of time. At the end of the
>> period we will have a little bit of data to understand whether
>> we have traction for this idea, and whether we should make it
>> IETF-wide, allow it to quietly die or explicitly advise
>> against it.
>
> I would encourage anyone who believes in "running code" wrt IETF
> processes and who is willing to argue that one of the current
> proposals should be adopted because there is real value in the
> Summary Reports called for by 3933 to compile a list of
>
> 	* 3933 Experiments
> 	* The published summary reports for each
> 	* How and where they found those reports.
> 	
> I predict the results will be enlightening.  :-(
>
>     john
>

From john-ietf@jck.com  Sat Dec 15 13:14:16 2012
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 2CD2F21F8513 for <ietf@ietfa.amsl.com>; Sat, 15 Dec 2012 13:14:16 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hJpKlaI4k9Tb for <ietf@ietfa.amsl.com>; Sat, 15 Dec 2012 13:14:15 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 91BCE21F84C8 for <ietf@ietf.org>; Sat, 15 Dec 2012 13:14:15 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tjz3l-0003H5-NT; Sat, 15 Dec 2012 16:14:13 -0500
Date: Sat, 15 Dec 2012 16:14:08 -0500
From: John C Klensin <john-ietf@jck.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Running code, take 2
Message-ID: <EAF367E2A7EEB8742207664A@JcK-HP8200.jck.com>
In-Reply-To: <50CC9F47.8080905@gmail.com>
References: <50C8DB78.3080905@gmail.com> <50C9DED7.8060604@tana.it> <006601cdd93c$6f9f7a00$4ede6e00$@olddog.co.uk> <9F862855-15A5-4109-88AE-32AAD7D1C21C@viagenie.ca> <50CA189E.1090002@gmail.com> <m2sj79zuot.wl%randy@psg.com> <50CA4DFA.9050500@gmail.com> <CD38357DE61404E1B49E9B93@JcK-HP8200.jck.com> <50CAE81A.4040807@gmail.com> <C49D02AFB5025BD44B8E1EA1@JcK-HP8200.jck.com> <50CC9F47.8080905@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: Sat, 15 Dec 2012 21:14:16 -0000

--On Saturday, December 15, 2012 18:03 +0200 Yaron Sheffer
<yaronf.ietf@gmail.com> wrote:

> Hi John,
> 
> According to Google, exactly one such report was issued:
> http://tools.ietf.org/html/draft-yevstifeyev-ion-report-06
> (the published RFC omitted the results of the experiment,
> somehow). And this particular experiment is not even mentioned
> in http://www.ietf.org/iesg/process-experiment.html. Two other
> experiments are listed, and I was unable to find any reports
> summarizing them.
> 
> So I'm willing to concede that the "process experiment"
> experiment failed. But since I think it *could have been* a
> valuable process, and since I'm seeing an IESG member
> proposing to use it, I would request to hear from the IESG if
> they think RFC 3933 is still a management tool they'd like to
> use.

Yaron,

FWIW, _I_ still think it us a useful tool for situations in
which an experiment cannot otherwise be performed without
violating existing procedures.   In that regard, I've just been
trying to make two points:

(1) As far as I can tell, neither your proposal nor Stephen's
requires a violation of existing rules.   Both, again as far as
I can tell, can be performed by agreement between WG Chairs and
the relevant AD and at the discretion of the latter.   That
assumes that no one on the IESG would object strenuously and
that no one would find a decision to appeal on the grounds that
the faster procedure had the effect of suppressing important
input, but those risks would occur even if there were a formal
process experiment.

(2) One cannot justify a formal, 3933-style, process experiment
on the grounds that it would produce a report.  Reports are
possible without such experiments and, as you have seen, despite
the 3933 requirement the reports often do not appear in the
official record.

   john


From sayrer@gmail.com  Sat Dec 15 20:36:09 2012
Return-Path: <sayrer@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 620A521F8566; Sat, 15 Dec 2012 20:36:09 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S+8+NmIFK6ak; Sat, 15 Dec 2012 20:36:08 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5F39321F845A; Sat, 15 Dec 2012 20:36:08 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so2276856wey.31 for <multiple recipients>; Sat, 15 Dec 2012 20:36:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=1UpRj7ApAA8YI+lkyR1A8ofFuuzUDbqp+QVzkAfqgo0=; b=KOK7Wne6kLpWvaLv/3u3k9nswRvD4600bul0L5//jRJQ/5cG/EwDqrKoVwPzc7SHcQ 6SoQrydvKHHnfgK+rVnL7SOxPHswYhbX3x2V8JKnBEWsGtk0lNOPKHKJsZaiQVFz0R4r XAyBHrPHjjUNDZFH8vgqwK4xrwmlMS5Vh2W11fRkc3q86uo5f1iWJmWYacB4kDVmE3hj TCOU3glKrTjuVYfa6xAdYDf5n1xJj4T+LnyOAUWZZNRg8hdBrJfRjA65GlhCojwGhsgX dQM4Fw1xZVzZkzjUZMJWHa/RJ2fWl4P8P5ZxwJRyCCis1i8bIJl08IFHv7vvn10Tdy8P PQew==
MIME-Version: 1.0
Received: by 10.194.23.37 with SMTP id j5mr10657051wjf.28.1355632567498; Sat, 15 Dec 2012 20:36:07 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sat, 15 Dec 2012 20:36:07 -0800 (PST)
In-Reply-To: <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com>
Date: Sat, 15 Dec 2012 20:36:07 -0800
Message-ID: <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: James M Snell <jasnell@gmail.com>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 04:36:09 -0000

On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
<markus.lanthaler@gmx.net> wrote:
>
> Hmm.. I think that=92s quite problematic. Especially considering how JSON=
 Pointer is used in JSON Patch.

I agree--I provided the same feedback privately. It seems
straightforwardly unsound.

- Rob


>
> --
>
> Markus Lanthaler
>
> @markuslanthaler
>
>
>
>
>
>
>
> From: James M Snell [mailto:jasnell@gmail.com]
> Sent: Friday, December 14, 2012 5:41 PM
> To: Markus Lanthaler
> Cc: IETF Discussion; IETF Apps Discuss
> Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-0=
7.txt> (JSON Pointer) to Proposed Standard
>
>
>
> JSON Pointer does not distinguish between objects and arrays. That is not=
 determined until the pointer is applied to an actual object instance... th=
e pointer "/1" is valid against {"1":"a"} or ["a","b"]
>
>
>
> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler <markus.lanthaler@gmx.n=
et> wrote:
>
> I've asked that before but didn't get an answer. So let me ask again (eve=
n
> though I'm quite sure it has already been asked by somebody else).
>
> How does JSON Pointer distinguish between objects and arrays? E.g. consid=
er
> the following JSON document:
>
> {
>   "foo": "bar",
>   "1": "baz"
> }
>
> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
> though that's probably not what the author intended. Is there a way to av=
oid
> that?
>
>
> Thanks,
> Markus
>
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
>
> > -----Original Message-----
> > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> > bounces@ietf.org] On Behalf Of The IESG
> > Sent: Tuesday, December 11, 2012 4:01 PM
> > To: IETF-Announce
> > Cc: apps-discuss@ietf.org
> > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> > 07.txt> (JSON Pointer) to Proposed Standard
> >
> >
> > The IESG has received a request from the Applications Area Working
> > Group
> > WG (appsawg) to consider the following document:
> > - 'JSON Pointer'
> >   <draft-ietf-appsawg-json-pointer-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 2012-12-25. Exceptionally, comments may
> > be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    JSON Pointer defines a string syntax for identifying a specific
> > value
> >    within a JSON document.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

From ron.even.tlv@gmail.com  Sat Dec 15 23:34:55 2012
Return-Path: <ron.even.tlv@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 3730521F84E8; Sat, 15 Dec 2012 23:34:55 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wjfp90a-4jaB; Sat, 15 Dec 2012 23:34:54 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4BD21F84E7; Sat, 15 Dec 2012 23:34:53 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so2715118eek.31 for <multiple recipients>; Sat, 15 Dec 2012 23:34:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=lDGDOPjJCRWKcNG48D1WIzSlzziQH4uEQZsASR8tF00=; b=uWlVKRsQVQAphHR9FohG3sLfRfO0m6Kq89MgEs0R2sAHf8hxHD6VeBh1siY6s3dwY6 85hoKkSoAegSJA+K8mbA4wfNnZ7wP5w2+kc7/P67P0ateqhAmbhuKNeGt/81af9nYfkc QYOOyfJN3JBY4txossT8Uhgc5y4R7+NrnFTlPSa+0tKSzd0V/4ly1OqbADyda57hoQ80 2Pmaz23HsgKU8fwIYLA3Nr3RuI6ZfmQ0KLbbKEVg1PUj/Tjq/I8eWlcDzrOpOW9dNoII I0x53CQsBeDWUcs/AWpM/47dZw9d7BR7GsDZ5HIW/hoqt1bsKBEYaI0GmVCgGEdDMSWV X+FQ==
Received: by 10.14.219.3 with SMTP id l3mr30237826eep.5.1355643292542; Sat, 15 Dec 2012 23:34:52 -0800 (PST)
Received: from RoniE (bzq-79-176-185-176.red.bezeqint.net. [79.176.185.176]) by mx.google.com with ESMTPS id 46sm20727493eeg.4.2012.12.15.23.34.48 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 15 Dec 2012 23:34:51 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <ietf@ietf.org>, <draft-ietf-appsawg-json-patch.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-appsawg-json-patch-08
Date: Sun, 16 Dec 2012 09:32:03 +0200
Message-ID: <023301cddb5f$73eb02d0$5bc10870$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0234_01CDDB70.37749620"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3bX3EjFnMrNpEpREWWeLmjX+vykQ==
Content-Language: en-us
Cc: gen-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 07:34:55 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0234_01CDDB70.37749620
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

 

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

 

Document: draft-ietf-appsawg-json-patch-08

Reviewer: Roni Even

Review Date:2012-12-16

IETF LC End Date: 2012-12-25

IESG Telechat date: 2013-1-10

 

Summary: This draft is almost  ready for publication.

 

 

Major issues:

 

Minor issues:

1.       The document has as the intended status "Informational" while the
last call says that the intended status is proposed standard?

 

 

Nits/editorial comments:

1.	In the IANA section the "Encoding considerations:  binary". I
noticed that RFC 4627 has a broader description:

"Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32

JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is
written in UTF-8, JSON is 8bit compatible.  When JSON is written in UTF-16
or UTF-32, the binary content-transfer-encoding   must be used."

 

 


------=_NextPart_000_0234_01CDDB70.37749620
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:789938108;
	mso-list-type:hybrid;
	mso-list-template-ids:-835678812 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1666859179;
	mso-list-type:hybrid;
	mso-list-template-ids:560766234 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>draft-ietf-=
appsawg-json-patch-08</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;12&#8211;16<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2012&#8211;12&#8211;25<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2013-1-10<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost&nbsp; ready for publication</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>The =
document has as the intended status &#8220;Informational&#8221; while =
the last call says that the intended status is proposed =
standard?<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo2'>In the =
IANA section the &#8220;Encoding considerations:&nbsp; binary&#8221;. I =
noticed that RFC 4627 has a broader description:<o:p></o:p></li></ol><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;line-height:normal'>&#8220;Encoding =
considerations: 8bit if UTF-8; binary if UTF-16 or =
UTF-32<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;line-height:normal'>JSON may be =
represented using UTF-8, UTF-16, or UTF-32.&nbsp; When JSON is written =
in UTF-8, JSON is 8bit compatible.&nbsp; When JSON is written in UTF-16 =
or UTF-32, the binary content-transfer-encoding&nbsp;&nbsp; must be =
used.&#8221;<o:p></o:p></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;line-height:normal'><o:p>&nbsp;</o:p></p=
><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0234_01CDDB70.37749620--


From markus.lanthaler@gmx.net  Fri Dec 14 09:38:38 2012
Return-Path: <markus.lanthaler@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 B6DF321F85B3 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:38:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[AWL=0.151,  BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OM0xzIX05hr7 for <ietf@ietfa.amsl.com>; Fri, 14 Dec 2012 09:38:38 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 00B2A21F897B for <ietf@ietf.org>; Fri, 14 Dec 2012 09:38:38 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.20]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MC6gQ-1TsKey3FSq-008rVm for <ietf@ietf.org>; Fri, 14 Dec 2012 18:38:36 +0100
Received: (qmail invoked by alias); 14 Dec 2012 17:38:36 -0000
Received: from unknown (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp020) with SMTP; 14 Dec 2012 18:38:36 +0100
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX18C4iwMq38CBurbmemGiWEHepaAVUcbDgPR6usqMP AGdG5jL/CrT7lR
From: "Markus Lanthaler" <markus.lanthaler@gmx.net>
To: "'James M Snell'" <jasnell@gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f33.295eb40a.7e3d.ffff919fSMTPIN_ADDED_BROKEN@mx.google.com> <CABP7Rbf9cZb1uJrkenxrGH06h-hsWSbG5PXyV6W-3Tm7aER4Ng@mail.gmail.com>
In-Reply-To: <CABP7Rbf9cZb1uJrkenxrGH06h-hsWSbG5PXyV6W-3Tm7aER4Ng@mail.gmail.com>
Subject: RE: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
Date: Fri, 14 Dec 2012 18:38:31 +0100
Message-ID: <021601cdda21$d6c541c0$844fc540$@lanthaler@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac3aHxjjg7lMd90fTjSw+Fg4sHvJ/wAAVshQ
Content-Language: de
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Sun, 16 Dec 2012 08:01:45 -0800
Cc: 'IETF Discussion' <ietf@ietf.org>, 'IETF Apps Discuss' <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 17:38:38 -0000

On Friday, December 14, 2012 6:19 PM, James M Snell wrote:

> > On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler wrote:
> >
> > Hmm.. I think that=E2=80=99s quite problematic. Especially =
considering
> > how JSON Pointer is used in JSON Patch.
>
> How so? Doesn't appear to be a problem in practice.=20

Since it doesn't express the authors intent. For example, assume you =
have a JSON Patch document like the following:

   [
     { "op": "test", "path": "/1", "value": 68 },
     { "op": "add", "path": "/2", "value": 105 }
   ]

What would you expect it to do? I think almost everyone would say that =
it set the third element of an array to 105 iff the second value is 68. =
So you might expect to get back an array on success but what you really =
get back might be something like this:=20

{
  "some": "value",
  "1": 68,
  "some other": "value",
  "and": "finally",
  "2": 105
}

Maybe having something like ~2 to express that a number is to be treated =
as an array index would solve it!?


--
Markus Lanthaler
@markuslanthaler


From jasnell@gmail.com  Fri Dec 14 09:43:22 2012
Return-Path: <jasnell@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 42CFB21F852D; Fri, 14 Dec 2012 09:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.695
X-Spam-Level: 
X-Spam-Status: No, score=-3.695 tagged_above=-999 required=5 tests=[AWL=-0.097, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YD95+H-+2lU8; Fri, 14 Dec 2012 09:43:21 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 035CE21F8501; Fri, 14 Dec 2012 09:43:18 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so3404145iaz.31 for <multiple recipients>; Fri, 14 Dec 2012 09:43:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0w8DafvQpeVofSm3ieh73xHdc/q4au1yO8kZ4sI8kaU=; b=RAsUK7u9o6MJARv91zS/V9BYhAKPCVlt+p0ROBmZX/BffbXkYafNPs7GK90HdMHE9e aGxsAyNwfUbqFxLQH3LUwUKAzNJPzWh67bYZe3MhqAnrWC6YacUfjHofOGFzwfVqG6RE qgHyaTbd/txGuoTGOBEzxcm29bhJXxxJC5nz1IfW7GycYEPFnKAhhd6swa+05zO+PLZq /YtZxIjGdEMPqoilByDbZBQ0UGRS3DeBTLGYvQuJn1TH9yOsAKG3rO6BVCNtpCwd2Bne SHuxms8CdUr8WXuhAUOzElBboOZqHvhyMozzuBLwgHzZATSURvDoIG20Q7f5DuuChp8W Jkgg==
Received: by 10.50.151.238 with SMTP id ut14mr2350608igb.72.1355506998679; Fri, 14 Dec 2012 09:43:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Fri, 14 Dec 2012 09:42:58 -0800 (PST)
In-Reply-To: <50cb641d.87cd0e0a.7f49.7549SMTPIN_ADDED_BROKEN@mx.google.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f33.295eb40a.7e3d.ffff919fSMTPIN_ADDED_BROKEN@mx.google.com> <CABP7Rbf9cZb1uJrkenxrGH06h-hsWSbG5PXyV6W-3Tm7aER4Ng@mail.gmail.com> <50cb641d.87cd0e0a.7f49.7549SMTPIN_ADDED_BROKEN@mx.google.com>
From: James M Snell <jasnell@gmail.com>
Date: Fri, 14 Dec 2012 09:42:58 -0800
Message-ID: <CABP7RbdXLTXhVO-HS++_Krf1EgQU+pTNRJpxu0s3Bn=NW1p8cQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Markus Lanthaler <markus.lanthaler@gmx.net>
Content-Type: multipart/alternative; boundary=e89a8f3b9f7d25978304d0d39110
X-Mailman-Approved-At: Sun, 16 Dec 2012 08:01:45 -0800
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 17:43:22 -0000

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

The author just needs to be aware of the current state of the object being
patched. Using conditional requests mechanisms can make it more reliable.


On Fri, Dec 14, 2012 at 9:38 AM, Markus Lanthaler
<markus.lanthaler@gmx.net>wrote:

> On Friday, December 14, 2012 6:19 PM, James M Snell wrote:
>
> > > On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler wrote:
> > >
> > > Hmm.. I think that=E2=80=99s quite problematic. Especially considerin=
g
> > > how JSON Pointer is used in JSON Patch.
> >
> > How so? Doesn't appear to be a problem in practice.
>
> Since it doesn't express the authors intent. For example, assume you have
> a JSON Patch document like the following:
>
>    [
>      { "op": "test", "path": "/1", "value": 68 },
>      { "op": "add", "path": "/2", "value": 105 }
>    ]
>
> What would you expect it to do? I think almost everyone would say that it
> set the third element of an array to 105 iff the second value is 68. So y=
ou
> might expect to get back an array on success but what you really get back
> might be something like this:
>
> {
>   "some": "value",
>   "1": 68,
>   "some other": "value",
>   "and": "finally",
>   "2": 105
> }
>
> Maybe having something like ~2 to express that a number is to be treated
> as an array index would solve it!?
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>

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

<font face=3D"courier new,monospace">The author just needs to be aware of t=
he current state of the object being patched. Using conditional requests me=
chanisms can make it more reliable.=C2=A0</font><div class=3D"gmail_extra">=
<br><br>

<div class=3D"gmail_quote">On Fri, Dec 14, 2012 at 9:38 AM, Markus Lanthale=
r <span dir=3D"ltr">&lt;<a href=3D"mailto:markus.lanthaler@gmx.net" target=
=3D"_blank">markus.lanthaler@gmx.net</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">

On Friday, December 14, 2012 6:19 PM, James M Snell wrote:<br>
<div class=3D"im"><br>
&gt; &gt; On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler wrote:<br>
&gt; &gt;<br>
&gt; &gt; Hmm.. I think that=E2=80=99s quite problematic. Especially consid=
ering<br>
&gt; &gt; how JSON Pointer is used in JSON Patch.<br>
&gt;<br>
</div><div class=3D"im">&gt; How so? Doesn&#39;t appear to be a problem in =
practice.<br>
<br>
</div>Since it doesn&#39;t express the authors intent. For example, assume =
you have a JSON Patch document like the following:<br>
<br>
=C2=A0 =C2=A0[<br>
=C2=A0 =C2=A0 =C2=A0{ &quot;op&quot;: &quot;test&quot;, &quot;path&quot;: &=
quot;/1&quot;, &quot;value&quot;: 68 },<br>
=C2=A0 =C2=A0 =C2=A0{ &quot;op&quot;: &quot;add&quot;, &quot;path&quot;: &q=
uot;/2&quot;, &quot;value&quot;: 105 }<br>
=C2=A0 =C2=A0]<br>
<br>
What would you expect it to do? I think almost everyone would say that it s=
et the third element of an array to 105 iff the second value is 68. So you =
might expect to get back an array on success but what you really get back m=
ight be something like this:<br>


<br>
{<br>
=C2=A0 &quot;some&quot;: &quot;value&quot;,<br>
=C2=A0 &quot;1&quot;: 68,<br>
=C2=A0 &quot;some other&quot;: &quot;value&quot;,<br>
=C2=A0 &quot;and&quot;: &quot;finally&quot;,<br>
=C2=A0 &quot;2&quot;: 105<br>
}<br>
<br>
Maybe having something like ~2 to express that a number is to be treated as=
 an array index would solve it!?<br>
<br>
<br>
--<br>
Markus Lanthaler<br>
@markuslanthaler<br>
<br>
</blockquote></div><br></div>

--e89a8f3b9f7d25978304d0d39110--

From jasnell@gmail.com  Sat Dec 15 21:23:19 2012
Return-Path: <jasnell@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 3ADCD21F846D; Sat, 15 Dec 2012 21:23:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.69
X-Spam-Level: 
X-Spam-Status: No, score=-3.69 tagged_above=-999 required=5 tests=[AWL=-0.092,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZW2sM4kza-o; Sat, 15 Dec 2012 21:23:18 -0800 (PST)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 10FA221F8434; Sat, 15 Dec 2012 21:23:18 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id z13so4454604iaz.31 for <multiple recipients>; Sat, 15 Dec 2012 21:23:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=QPPDjy2CZR1Uur+AmrisQ0fpquvcD29fH82JYzAdvbo=; b=IzhaRCeXnRffXbiBYJbeZOnxQsrZGQpRyVVAepMoL9O/GzF9Oo2fucmAdHf+ie6xmY 2n6tWCSV0hCHNyi3zZbZx0++odREoCV51wO+EL7iEUac6FEzFKVJe0jZx7DPuji1Whaj RUP/7qKPCNWLC3tnqyAuPvbC8n8k6zS+ojVsvgClJiUFrocylzgy/jix6UXh6GK01+CP NmsvaaOv9L+/YEwPwJrs4PT2S/kbi0tLv7wVEiknUkU7P+9LaK9bnW9cRKh1Wz7uFo3n AtT/BlOJcMbbZa+NYC3EPiTKRSe7XB/f5G7XUSXcnEaxiD+Wr4dSeCj1pGLxS3hb+0+z A0lQ==
Received: by 10.50.0.193 with SMTP id 1mr6069724igg.0.1355635397593; Sat, 15 Dec 2012 21:23:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Sat, 15 Dec 2012 21:22:57 -0800 (PST)
In-Reply-To: <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Sat, 15 Dec 2012 21:22:57 -0800
Message-ID: <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Robert Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f502f8e51897304d0f17665
X-Mailman-Approved-At: Sun, 16 Dec 2012 08:01:45 -0800
Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, IETF Apps Discuss <apps-discuss@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: Sun, 16 Dec 2012 05:23:19 -0000

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

On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wrote:

> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
> <markus.lanthaler@gmx.net> wrote:
> >
> > Hmm.. I think that=E2=80=99s quite problematic. Especially considering =
how JSON
> Pointer is used in JSON Patch.
>
> I agree--I provided the same feedback privately. It seems
> straightforwardly unsound.
>
>
In practice it doesn't seem to be much of an issue.

Specifically, if I GET an existing document and get an etag with the JSON,
then make some changes and send a PATCH with If-Match, the fact that any
given pointer could point to an array or object member doesn't really
matter much.

For example:

  >  GET /the/doc HTTP/1.1

  <  HTTP/1.1 200 OK
     ETag: "my-document-tag"
     Content-Type: application/json

     {"1":"foo"}

  >  PATCH /the/doc HTTP/1.1
     If-Match: "my-document-etag"
     Content-Type: application/json-patch

     [{"op":"add","path":"/2","value":"bar"}]

Generally speaking, someone should not be using PATCH to perform a partial
modification if they don't already have some knowledge in advance what they
are modifying. The only time the apparent ambiguity becomes an issue is
when a client is blindly sending a patch to an unknown endpoint... in which
case, you get whatever you end up with.

- James



> - Rob
>
>
> >
> > --
> >
> > Markus Lanthaler
> >
> > @markuslanthaler
> >
> >
> >
> >
> >
> >
> >
> > From: James M Snell [mailto:jasnell@gmail.com]
> > Sent: Friday, December 14, 2012 5:41 PM
> > To: Markus Lanthaler
> > Cc: IETF Discussion; IETF Apps Discuss
> > Subject: Re: [apps-discuss] Last Call:
> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Stand=
ard
> >
> >
> >
> > JSON Pointer does not distinguish between objects and arrays. That is
> not determined until the pointer is applied to an actual object instance.=
..
> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
> >
> >
> >
> > On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler <
> markus.lanthaler@gmx.net> wrote:
> >
> > I've asked that before but didn't get an answer. So let me ask again
> (even
> > though I'm quite sure it has already been asked by somebody else).
> >
> > How does JSON Pointer distinguish between objects and arrays? E.g.
> consider
> > the following JSON document:
> >
> > {
> >   "foo": "bar",
> >   "1": "baz"
> > }
> >
> > As I read the draft, the JSON Pointer "/1" would evaluate to "baz" even
> > though that's probably not what the author intended. Is there a way to
> avoid
> > that?
> >
> >
> > Thanks,
> > Markus
> >
> >
> >
> > --
> > Markus Lanthaler
> > @markuslanthaler
> >
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> > > bounces@ietf.org] On Behalf Of The IESG
> > > Sent: Tuesday, December 11, 2012 4:01 PM
> > > To: IETF-Announce
> > > Cc: apps-discuss@ietf.org
> > > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
> > > 07.txt> (JSON Pointer) to Proposed Standard
> > >
> > >
> > > The IESG has received a request from the Applications Area Working
> > > Group
> > > WG (appsawg) to consider the following document:
> > > - 'JSON Pointer'
> > >   <draft-ietf-appsawg-json-pointer-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 th=
e
> > > ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments ma=
y
> > > be
> > > sent to iesg@ietf.org instead. In either case, please retain the
> > > beginning of the Subject line to allow automated sorting.
> > >
> > > Abstract
> > >
> > >
> > >    JSON Pointer defines a string syntax for identifying a specific
> > > value
> > >    within a JSON document.
> > >
> > >
> > >
> > >
> > > The file can be obtained via
> > > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> > >
> > > IESG discussion can be tracked via
> > >
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> > >
> > >
> > > No IPR declarations have been submitted directly on this I-D.
> > >
> > >
> > > _______________________________________________
> > > apps-discuss mailing list
> > > apps-discuss@ietf.org
> > > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> >
> >
> >
> > _______________________________________________
> > apps-discuss mailing list
> > apps-discuss@ietf.org
> > https://www.ietf.org/mailman/listinfo/apps-discuss
> >
>

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

<font face=3D"courier new,monospace"><br></font><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote">On Sat, Dec 15, 2012 at 8:36 PM, Robert =
Sayre <span dir=3D"ltr">&lt;<a href=3D"mailto:sayrer@gmail.com" target=3D"_=
blank">sayrer@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Fri, Dec 14, 2012 at 9:=
17 AM, Markus Lanthaler<br>
&lt;<a href=3D"mailto:markus.lanthaler@gmx.net">markus.lanthaler@gmx.net</a=
>&gt; wrote:<br>
&gt;<br>
&gt; Hmm.. I think that=E2=80=99s quite problematic. Especially considering=
 how JSON Pointer is used in JSON Patch.<br>
<br>
</div>I agree--I provided the same feedback privately. It seems<br>
straightforwardly unsound.<br>
<br></blockquote><div><br></div><div><font face=3D"courier new, monospace">=
In practice it doesn&#39;t seem to be much of an issue.</font></div><div><f=
ont face=3D"courier new, monospace"><br></font></div><div><font face=3D"cou=
rier new, monospace">Specifically, if I GET an existing document and get an=
 etag with the JSON, then make some changes and send a PATCH with If-Match,=
 the fact that any given pointer could point to an array or object member d=
oesn&#39;t really matter much.</font></div>

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">For example:</font></div><div><font face=3D"cou=
rier new, monospace"><br></font></div><div><font face=3D"courier new, monos=
pace">=C2=A0 &gt; =C2=A0GET /the/doc HTTP/1.1</font></div>

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=C2=A0 &lt; =C2=A0HTTP/1.1 200 OK</font></div><=
div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0ETag: &quot;m=
y-document-tag&quot;</font></div>

<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0Content-Type=
: application/json</font></div><div><font face=3D"courier new, monospace"><=
br></font></div><div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =
=C2=A0{&quot;1&quot;:&quot;foo&quot;}</font></div>

<div><br></div><div><font face=3D"courier new, monospace">=C2=A0 &gt; =C2=
=A0PATCH /the/doc HTTP/1.1</font></div><div><font face=3D"courier new, mono=
space">=C2=A0 =C2=A0 =C2=A0If-Match: &quot;my-document-etag&quot;</font></d=
iv><div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0Content-T=
ype: application/json-patch</font></div>

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0[{&quot;op&quot;:&quot;add&=
quot;,&quot;path&quot;:&quot;/2&quot;,&quot;value&quot;:&quot;bar&quot;}]</=
font></div><div>

<br></div><div><font face=3D"courier new, monospace">Generally speaking, so=
meone should not be using PATCH to perform a partial modification if they d=
on&#39;t already have some knowledge in advance what they are modifying. Th=
e only time the apparent ambiguity becomes an issue is when a client is bli=
ndly sending a patch to an unknown endpoint... in which case, you get whate=
ver you end up with.=C2=A0</font></div>

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">- James</font></div><div><br></div><div>=C2=A0<=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">


- Rob<br>
<div class=3D"im"><br>
<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; Markus Lanthaler<br>
&gt;<br>
&gt; @markuslanthaler<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: James M Snell [mailto:<a href=3D"mailto:jasnell@gmail.com">jasne=
ll@gmail.com</a>]<br>
&gt; Sent: Friday, December 14, 2012 5:41 PM<br>
&gt; To: Markus Lanthaler<br>
&gt; Cc: IETF Discussion; IETF Apps Discuss<br>
</div>&gt; Subject: Re: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-js=
on-pointer-07.txt&gt; (JSON Pointer) to Proposed Standard<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt;<br>
&gt;<br>
&gt;<br>
&gt; JSON Pointer does not distinguish between objects and arrays. That is =
not determined until the pointer is applied to an actual object instance...=
 the pointer &quot;/1&quot; is valid against {&quot;1&quot;:&quot;a&quot;} =
or [&quot;a&quot;,&quot;b&quot;]<br>


&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler &lt;<a href=3D"mailt=
o:markus.lanthaler@gmx.net">markus.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt;<br>
&gt; I&#39;ve asked that before but didn&#39;t get an answer. So let me ask=
 again (even<br>
&gt; though I&#39;m quite sure it has already been asked by somebody else).=
<br>
&gt;<br>
&gt; How does JSON Pointer distinguish between objects and arrays? E.g. con=
sider<br>
&gt; the following JSON document:<br>
&gt;<br>
&gt; {<br>
&gt; =C2=A0 &quot;foo&quot;: &quot;bar&quot;,<br>
&gt; =C2=A0 &quot;1&quot;: &quot;baz&quot;<br>
&gt; }<br>
&gt;<br>
&gt; As I read the draft, the JSON Pointer &quot;/1&quot; would evaluate to=
 &quot;baz&quot; even<br>
&gt; though that&#39;s probably not what the author intended. Is there a wa=
y to avoid<br>
&gt; that?<br>
&gt;<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Markus<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Markus Lanthaler<br>
&gt; @markuslanthaler<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:apps-discuss-bounces@ietf.org">apps-discu=
ss-bounces@ietf.org</a> [mailto:<a href=3D"mailto:apps-discuss-">apps-discu=
ss-</a><br>
&gt; &gt; <a href=3D"mailto:bounces@ietf.org">bounces@ietf.org</a>] On Beha=
lf Of The IESG<br>
&gt; &gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>
&gt; &gt; To: IETF-Announce<br>
&gt; &gt; Cc: <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.or=
g</a><br>
&gt; &gt; Subject: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-json-po=
inter-<br>
&gt; &gt; 07.txt&gt; (JSON Pointer) to Proposed Standard<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The IESG has received a request from the Applications Area Workin=
g<br>
&gt; &gt; Group<br>
&gt; &gt; WG (appsawg) to consider the following document:<br>
&gt; &gt; - &#39;JSON Pointer&#39;<br>
&gt; &gt; =C2=A0 &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; as Proposed=
 Standard<br>
&gt; &gt;<br>
&gt; &gt; The IESG plans to make a decision in the next few weeks, and soli=
cits<br>
&gt; &gt; final comments on this action. Please send substantive comments t=
o the<br>
&gt; &gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists =
by 2012-12-25. Exceptionally, comments may<br>
&gt; &gt; be<br>
&gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instea=
d. In either case, please retain the<br>
&gt; &gt; beginning of the Subject line to allow automated sorting.<br>
&gt; &gt;<br>
&gt; &gt; Abstract<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; =C2=A0 =C2=A0JSON Pointer defines a string syntax for identifying=
 a specific<br>
&gt; &gt; value<br>
&gt; &gt; =C2=A0 =C2=A0within a JSON document.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The file can be obtained via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-jso=
n-pointer/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-ap=
psawg-json-pointer/</a><br>
&gt; &gt;<br>
&gt; &gt; IESG discussion can be tracked via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-jso=
n-pointer/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-=
ietf-appsawg-json-pointer/ballot/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; apps-discuss mailing list<br>
&gt; &gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a=
><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
</div></div></blockquote></div><br></div>

--e89a8f502f8e51897304d0f17665--

From moore@network-heretics.com  Sun Dec 16 12:08:44 2012
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 7981621F8972 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 12:08:44 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lVHkdi7G2kF1 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 12:08:43 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 914C221F8970 for <ietf@ietf.org>; Sun, 16 Dec 2012 12:08:43 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D5E77205F5 for <ietf@ietf.org>; Sun, 16 Dec 2012 15:08:42 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Sun, 16 Dec 2012 15:08:42 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=pGDOccyI6KJ3Cf/tjKZHOG rv/Xw=; b=O60XpP6i72aOHfyf8a00jntEqiCvovsFNXq/7n7rUhsHjvYPmghcaY ea9HzuUTyYwpcy7mvhgP3XV92AcdsoSOiWNAnprHsNiFMeiH4OJpyzkhLjZD6wQ4 7KaVAIWRQiXksZvKfMNEjItvxOpbe78xNCTze8RRjgRfObPtl1pcs=
X-Sasl-enc: LxhS36w2M0czlPxFfBnJEBY9WBwJYAbOlToKYLa6YBA9 1355688522
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2113A8E0636; Sun, 16 Dec 2012 15:08:42 -0500 (EST)
Message-ID: <50CE2A46.2010107@network-heretics.com>
Date: Sun, 16 Dec 2012 15:08:38 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The notion of "fast tracking" drafts
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@cs.tcd.ie> <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com>
In-Reply-To: <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.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: Sun, 16 Dec 2012 20:08:44 -0000

On 12/14/2012 06:09 PM, John C Klensin wrote:
> I've been trying to say out of this because I think most of the
> suggestions are better carried out by AD-encouraged experiments
> and reports to the rest of us on effectiveness rather than by
> long discussions in the community about details and the costs of
> an unnecessary consensus process.
>
> However, since I gather we are pushing (or being pushed) down
> this path, let me suggest that approval of an IETF spec,
> especially a standards-track one, has (or should have) elements
> of all of the following:
>
> (1) A conviction that the idea is implementable and that the
> ideas expressed are consistent with implementation (and,
> ideally, operational realities.
>
> (2) Specification of sufficient quality to make
> independently-developed interoperable implementations by people
> who were not part of the WG or development process possible and
> specifically that there are no ambiguities that could adversely
> affect interoperable implementations.  This includes, but is not
> limited to, editorial quality in terms of good technical
> English, but does not include "good idea" criteria (see (4)).
>
> (3) "No known technical defects" in the spec (the RFC 2026
> requirement).  Note that, while an implementation might turn up
> technical defects that might otherwise be unknown, it might
> easily not turn up ones that could be identified in other ways.
> It should imply a fairly comprehensive review that would have a
> high likelihood of turning up any technical defects that are
> present, but we all know that sometimes doesn't happen.
>
> (4) Some level of IETF consensus that publishing the
> specification has value for the community.  This might or might
> not include a community belief that the document specifies a
> good idea that should be implemented and deployed (the latter is
> why we have Applicability Statements).
to this I'd add

(5) Widespread, examined belief that the specification has minimal 
impact on the Internet architecture.

I keep seeing IETF standardize protocols that seem likely to have 
seriously damaging architectural impact without much, if any, 
examination of that impact (the PCP and MIF work come most immediately 
to mind, but I could cite several others given a few minutes to think 
about it).  I'd hate to see a fast-tracking procedure used as a way to 
further circumvent such examination.

Keith


From john-ietf@jck.com  Sun Dec 16 12:49:50 2012
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 8239621F8935 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 12:49:50 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsgtCKoRVTZx for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 12:49:50 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BD57821F8932 for <ietf@ietf.org>; Sun, 16 Dec 2012 12:49:45 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TkL9b-0005YZ-LK; Sun, 16 Dec 2012 15:49:43 -0500
X-Vipre-Scanned: 02A50274002C3102A503C1-TDI
Date: Sun, 16 Dec 2012 15:49:43 -0500
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: The notion of "fast tracking" drafts
Message-ID: <836340163076CC86CACF70FB@[192.168.1.128]>
In-Reply-To: <50CE2A46.2010107@network-heretics.com>
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@cs.tcd.ie> <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com> <50CE2A46.2010107@network-heretics.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: Sun, 16 Dec 2012 20:49:50 -0000

--On Sunday, December 16, 2012 15:08 -0500 Keith Moore
<moore@network-heretics.com> wrote:

> to this I'd add
> 
> (5) Widespread, examined belief that the specification has
> minimal impact on the Internet architecture.
> 
> I keep seeing IETF standardize protocols that seem likely to
> have seriously damaging architectural impact without much, if
> any, examination of that impact (the PCP and MIF work come
> most immediately to mind, but I could cite several others
> given a few minutes to think about it).  I'd hate to see a
> fast-tracking procedure used as a way to further circumvent
> such examination.

I think I would have said "impact on the Internet architecture
is well-understood and judged to be acceptable" instead, but we
agree about the general principle.

   john




From stephen.farrell@cs.tcd.ie  Sun Dec 16 13:49:48 2012
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 CC40D21F89C6 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 13:49:48 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzvjSwagz2Nt for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 13:49:48 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3B2E921F88C8 for <ietf@ietf.org>; Sun, 16 Dec 2012 13:49:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CEBC5BE2F; Sun, 16 Dec 2012 21:49:23 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROULkhQE0eUN; Sun, 16 Dec 2012 21:49:23 +0000 (GMT)
Received: from [10.87.48.8] (unknown [86.44.64.140]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 059A5BE29; Sun, 16 Dec 2012 21:49:23 +0000 (GMT)
Message-ID: <50CE41E2.7000604@cs.tcd.ie>
Date: Sun, 16 Dec 2012 21:49:22 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>,  Keith Moore <moore@network-heretics.com>
Subject: Re: The notion of "fast tracking" drafts
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@cs.tcd.ie> <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com> <50CE2A46.2010107@network-heretics.com> <836340163076CC86CACF70FB@[192.168.1.128]>
In-Reply-To: <836340163076CC86CACF70FB@[192.168.1.128]>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 21:49:48 -0000

John, Keith,

I really have to say that you both seem to be talking about
things that have nothing whatsoever to do with my proposal.

ISTM that you are of the opinion that anything the IETF
does to go faster is bad in and of itself because its
scary. This also seems to me to be an example of the kind
of process discussion wandering onto everyone's favourite
hobby horse that I mentioned before.

So I don't see any change to the draft is required, but
if you do have a direct comment on the draft, that'd be
welcome and I'd be very happy to get such comments. Or
perhaps I'm missing something that is relevant to my
draft, but if so, I don't see it, so you need to bring
your concerns down to issues with the draft if you are
making a specific comment rather than being generally
worried.

Cheers,
S.

On 12/16/2012 08:49 PM, John C Klensin wrote:
> 
> 
> --On Sunday, December 16, 2012 15:08 -0500 Keith Moore
> <moore@network-heretics.com> wrote:
> 
>> to this I'd add
>>
>> (5) Widespread, examined belief that the specification has
>> minimal impact on the Internet architecture.
>>
>> I keep seeing IETF standardize protocols that seem likely to
>> have seriously damaging architectural impact without much, if
>> any, examination of that impact (the PCP and MIF work come
>> most immediately to mind, but I could cite several others
>> given a few minutes to think about it).  I'd hate to see a
>> fast-tracking procedure used as a way to further circumvent
>> such examination.
> 
> I think I would have said "impact on the Internet architecture
> is well-understood and judged to be acceptable" instead, but we
> agree about the general principle.
> 
>    john
> 
> 
> 

From moore@network-heretics.com  Sun Dec 16 14:28:06 2012
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 44CB621F86A5 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 14:28:06 -0800 (PST)
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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2suZS5bJPHX9 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 14:28:05 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id 4F40721F86A1 for <ietf@ietf.org>; Sun, 16 Dec 2012 14:28:05 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E78E220675; Sun, 16 Dec 2012 17:28:04 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Sun, 16 Dec 2012 17:28:04 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=7lYN97HhQ91FD9VDJcd8QP f0ZZw=; b=AqEq9n1ch3qrVW+qN58dRtslOSLrAjMHNbI5Y/ubN5wio9dgCe3BOF myy6w+vNQQjoHCdiPmVl4ZRIjZb8Yq/jFxM8WAQ/UAWMvzHphx9n9qBLRJpLEjf9 GmuDSNo/TyPtjAXF+8XNQ0MLx4fRmWQSd8cogSgMKBGnGLp9taGnE=
X-Sasl-enc: yAAPTnhXniTPGixR4tHZslXXxXXjIFAlAgD1YpcAG2RM 1355696884
Received: from [192.168.1.20] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id EA7028E0699; Sun, 16 Dec 2012 17:28:02 -0500 (EST)
Message-ID: <50CE4AED.6000003@network-heretics.com>
Date: Sun, 16 Dec 2012 17:27:57 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: The notion of "fast tracking" drafts
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@cs.tcd.ie> <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com> <50CE2A46.2010107@network-heretics.com> <836340163076CC86CACF70FB@[192.168.1.128]> <50CE41E2.7000604@cs.tcd.ie>
In-Reply-To: <50CE41E2.7000604@cs.tcd.ie>
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 22:28:06 -0000

On 12/16/2012 04:49 PM, Stephen Farrell wrote:
> ISTM that you are of the opinion that anything the IETF
> does to go faster is bad in and of itself because its
> scary.
It's not that simple, at least in my opinion.

I'm generally fine with fast tracking a document that describes a simple 
protocol that is easily understood, easily implemented, 
noncontroversial, and has a limited impact.  In all other cases, I think 
that more deliberation is appropriate.   That's not to say that IETF 
currently makes good use of deliberation time.  But I'd rather see it 
make better use of that time, than to try to reduce that time without 
first improving protocol and document quality. For example, I'd like to 
see earlier and more explicit cross-area review.

Keith


From yaronf.ietf@gmail.com  Sun Dec 16 14:30:46 2012
Return-Path: <yaronf.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 25B6E21F86A1 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 14:30:46 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SzoAUlc1NuZ for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 14:30:45 -0800 (PST)
Received: from mail-ee0-f44.google.com (mail-ee0-f44.google.com [74.125.83.44]) by ietfa.amsl.com (Postfix) with ESMTP id 73FD121F8477 for <ietf@ietf.org>; Sun, 16 Dec 2012 14:30:45 -0800 (PST)
Received: by mail-ee0-f44.google.com with SMTP id b47so2942095eek.31 for <ietf@ietf.org>; Sun, 16 Dec 2012 14:30:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=EKG4xzT3HzjYH8xLVnBJHFraBLwimrpad6xy8J8n0Os=; b=fJkGbBMy8ND9y4l2LDaonvEG+BysUYvstvFyjanae+wXsRH2eYQnm0lsL8K/yJZ+tF kn+bfmFyx0cDzDdylNgTWcSobNjAAOCBGwfwaYjOJi4Iwtxq/GE0XzF5zPkQxEJaH9Rq K77M7l1EynKYFHpEzeJkRvhHEVKG/Wf2sxiiqB2CDTk5Wg2yNuiI1b4pmEnmOggWVCec pO/XkU+XNZaQddsqnzGGeBpsfqBfs2B9GcWEdZzE3SKun8QTPo6Hh9HpXpRNsCtKopnw 09yPxevqyiyedwfrcloJmj3v/ba0SFx69L8c9pnHYRecsgmoDxw/qQ+QKaJpBh8xYJ8v sEJg==
Received: by 10.14.208.137 with SMTP id q9mr35198629eeo.28.1355697044699; Sun, 16 Dec 2012 14:30:44 -0800 (PST)
Received: from [10.0.0.5] (bzq-79-182-171-89.red.bezeqint.net. [79.182.171.89]) by mx.google.com with ESMTPS id z8sm25177435eeo.11.2012.12.16.14.30.42 (version=SSLv3 cipher=OTHER); Sun, 16 Dec 2012 14:30:43 -0800 (PST)
Message-ID: <50CE4B91.7030000@gmail.com>
Date: Mon, 17 Dec 2012 00:30:41 +0200
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Running code draft -01
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: Sun, 16 Dec 2012 22:30:46 -0000

Hi,

we have just published version -01: 
http://tools.ietf.org/html/draft-sheffer-running-code-01

Main changes:

- Adrian Farrel joined as co-author (thanks!)
- This is an experiment, just not an RFC 3933 experiment.
- The Implementation Status may, under some circumstances, migrate from 
the Internet Draft into a web/wiki page.
- Added some background regarding the routing community's approach to 
protocol implementation.

Thanks,
     Yaron

From stephen.farrell@cs.tcd.ie  Sun Dec 16 14:39:22 2012
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 E0FE321F851E for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 14:39:22 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rXHsy7H2qZIp for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 14:39:22 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 15EF721F851C for <ietf@ietf.org>; Sun, 16 Dec 2012 14:39:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4B234BE2F; Sun, 16 Dec 2012 22:38:55 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wxuglUOookBD; Sun, 16 Dec 2012 22:38:54 +0000 (GMT)
Received: from [10.87.48.8] (unknown [86.44.64.140]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id ADD28BE29; Sun, 16 Dec 2012 22:38:54 +0000 (GMT)
Message-ID: <50CE4D7D.5020108@cs.tcd.ie>
Date: Sun, 16 Dec 2012 22:38:53 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: The notion of "fast tracking" drafts
References: <50C8DB78.3080905@gmail.com> <50CB273D.3070208@cs.tcd.ie> <BE67CCC33A07BB09E69FE1CF@JcK-HP8200.jck.com> <50CE2A46.2010107@network-heretics.com> <836340163076CC86CACF70FB@[192.168.1.128]> <50CE41E2.7000604@cs.tcd.ie> <50CE4AED.6000003@network-heretics.com>
In-Reply-To: <50CE4AED.6000003@network-heretics.com>
X-Enigmail-Version: 1.4.6
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: Sun, 16 Dec 2012 22:39:23 -0000

Hiya,

On 12/16/2012 10:27 PM, Keith Moore wrote:
> On 12/16/2012 04:49 PM, Stephen Farrell wrote:
>> ISTM that you are of the opinion that anything the IETF
>> does to go faster is bad in and of itself because its
>> scary.
> It's not that simple, at least in my opinion.
> 
> I'm generally fine with fast tracking a document that describes a simple
> protocol that is easily understood, easily implemented,
> noncontroversial, and has a limited impact.  In all other cases, I think
> that more deliberation is appropriate.   That's not to say that IETF
> currently makes good use of deliberation time.  But I'd rather see it
> make better use of that time, than to try to reduce that time without
> first improving protocol and document quality. For example, I'd like to
> see earlier and more explicit cross-area review.

All reasonable stuff and the draft says that this won't be suitable
for all cases. If you've better wording to suggest that'd be welcome.

Cheers,
S.

> 
> Keith
> 
> 
> 

From ron.even.tlv@gmail.com  Sun Dec 16 14:59:59 2012
Return-Path: <ron.even.tlv@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 6A43F21F863B; Sun, 16 Dec 2012 14:59:59 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ssmhKEvjmlD; Sun, 16 Dec 2012 14:59:58 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1A21521F8635; Sun, 16 Dec 2012 14:59:57 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id a1so2149598eaa.31 for <multiple recipients>; Sun, 16 Dec 2012 14:59:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=4wn3IOb3NI2Fe3DGv/8NajVs1/ivCeLBXNe+YCXUWHI=; b=NXvXheB/yBz9OsBFBgT7kg4eUHtgAQ8InAyNPGXy+llQU3Xtyc4i7xrzgkadzsK/Vb rNchpbqWgLrGLxwPEc+K1he9bxAaCRuKTt6hYFP38OC/41cg9r00nvDh87aEkPLxgNIf FW5SgDqCvMooW85dMydjlmxxCvl4eIDMfXHBiCi+FR/KYmf7+SKQfupLOr+oCAOi5Dps mHPi7fXWhR5OOgjcl5ZH6qgzu95jIy7Usi/qABKSi1Gl5GDuF8BSvaaM/XuHMGEC3duS es07jjK6OCeoN+Tj/DMeTsmsHoZyr9NychXWBvKNoZgaiOlmQplJaN/zNwKGGAcr6ZO+ c1aQ==
Received: by 10.14.0.133 with SMTP id 5mr35096112eeb.29.1355698797268; Sun, 16 Dec 2012 14:59:57 -0800 (PST)
Received: from RoniE (bzq-79-176-185-176.red.bezeqint.net. [79.176.185.176]) by mx.google.com with ESMTPS id f49sm25280183eep.12.2012.12.16.14.59.53 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Dec 2012 14:59:56 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <ietf@ietf.org>
Subject: Gen-ART LC review of draft-daboo-ical-vcard-parameter-encoding-02
Date: Mon, 17 Dec 2012 00:57:08 +0200
Message-ID: <026d01cddbe0$afb19320$0f14b960$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_026E_01CDDBF1.733AFF60"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac3b4KyqaBiVYCC7SBib9omClLXGWA==
Content-Language: en-us
Cc: gen-art@ietf.org, draft-daboo-ical-vcard-parameter-encoding.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, 16 Dec 2012 22:59:59 -0000

This is a multipart message in MIME format.

------=_NextPart_000_026E_01CDDBF1.733AFF60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

 

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

 

Document: draft-daboo-ical-vcard-parameter-encoding-02

Reviewer: Roni Even

Review Date:2012-12-17

IETF LC End Date: 2012-12-14

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 


------=_NextPart_000_026E_01CDDBF1.733AFF60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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


From barryleiba.mailing.lists@gmail.com  Sun Dec 16 15:13:05 2012
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 CF9CF21F8738; Sun, 16 Dec 2012 15:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.044
X-Spam-Level: 
X-Spam-Status: No, score=-103.044 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5jtdSH3Xzr9b; Sun, 16 Dec 2012 15:13:02 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3957021F86D9; Sun, 16 Dec 2012 15:13:01 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so4157158lbk.31 for <multiple recipients>; Sun, 16 Dec 2012 15:12:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=XdPW6Em3ERt9x+ZG9pqrK7feXlcbz5aFYfBkS0Qxq4c=; b=jAaX9cKoJhomGJr/GqOcqHjDt1Hnbw/TU95k9rJyBqUypyFqULQpRbg+W7u1g3fJ2t MAaJXVhmxAm1aTS01A40tLcX5pdgVFcako5z/RtEXJakkEK5T5KSECM3sAigdQ3CAfRc mFl014JnPHESPKPmXdx5eluNupA98dRevldNhUSzFyvHzlWJ0VCbnE/nIzkTSxhP8Pb0 eXaFVxXmxkOJOzqHedKJqbiLcOecNVqUQUxSAJjB2NoQOPWttLtqTqnLGgW+NKYK2J9O XrKV0wuMGGCjijAOTtX6TdWSLhJAlqU+EVMVGyXDaQvTSwm4DE43vhWFH6E2WlHJIYjv tKyQ==
MIME-Version: 1.0
Received: by 10.112.101.135 with SMTP id fg7mr5087581lbb.87.1355699575857; Sun, 16 Dec 2012 15:12:55 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Sun, 16 Dec 2012 15:12:55 -0800 (PST)
In-Reply-To: <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net> <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com>
Date: Sun, 16 Dec 2012 18:12:55 -0500
X-Google-Sender-Auth: 2OE11SKONsT-ucV1TskA7vwKvlw
Message-ID: <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 23:13:05 -0000

Anyone have any comments on what I suggested below?

Barry

On Tue, Dec 11, 2012 at 11:25 PM, Barry Leiba <barryleiba@computer.org> wrote:
>> Personally -- to me, it seems like you're getting hung up on the word "add."
> ...
>> "add" means what the format definition says it means, because otherwise
>> we have to rationalise all of the different systems people might use it with
>> to make sense.
>
> OK, I'll buy that.  Then let's take a different approach, and make it
> clearer that it's Humpty Dumpty's version of "add", so maybe neither I
> nor Alice will get hung up on it:
>
> OLD
>    The "add" operation adds a new value at the target location. The
>    operation object MUST contain a "value" member that specifies the
>    value to be added.
> NEW
>    The "add" operation performs the following function, depending upon
>    what the target location references (see details below):
>
>    o  If the target location specifies an array index, a new value is
>       inserted into the array at the specified index.
>
>    o  If the target location specifies an object member that does not
>       already exist, a new member is added to the object.
>
>    o  If the target location specifies an object member that does
>       exist, that member's value is replaced.
> END
>
> That may be wordier than we need, but I think it makes the point...
> feel free to wordsmith.  With something like that, I think we can say
> that we had to pick a name, "add" was picked, and it means exactly
> what we choose it to mean - neither more nor less.  And that's glory
> for you.
>
> Barry

From john@jck.com  Sun Dec 16 15:53:31 2012
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 D938021F843A; Sun, 16 Dec 2012 15:53:31 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ESgJaY8cmme; Sun, 16 Dec 2012 15:53:31 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5980121F8430; Sun, 16 Dec 2012 15:53:31 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1TkO1O-0005ra-Iz; Sun, 16 Dec 2012 18:53:26 -0500
X-Vipre-Scanned: 034D352B002C31034D3678-TDI
Date: Sun, 16 Dec 2012 18:53:25 -0500
From: John C Klensin <john@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Mark Nottingham <mnot@mnot.net>
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to	Proposed Standard
Message-ID: <5C6A104276F197129659DF24@[192.168.1.128]>
In-Reply-To: <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.com>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net> <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com> <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>, apps-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Dec 2012 23:53:32 -0000

--On Sunday, December 16, 2012 18:12 -0500 Barry Leiba
<barryleiba@computer.org> wrote:

> Anyone have any comments on what I suggested below?

How about "+1" --complete agreement.  The terminology, if
interpreted in a "normal English" context, lies somewhere
between confusing and misleading and a precise local definition
is the more efficient fix.

   john

>...
> On Tue, Dec 11, 2012 at 11:25 PM, Barry Leiba
> <barryleiba@computer.org> wrote:
>>> Personally -- to me, it seems like you're getting hung up on
>>> the word "add."
>> ...
>>> "add" means what the format definition says it means,
>>> because otherwise we have to rationalise all of the
>>> different systems people might use it with to make sense.
>> 
>> OK, I'll buy that.  Then let's take a different approach, and
>> make it clearer that it's Humpty Dumpty's version of "add",
>> so maybe neither I nor Alice will get hung up on it:
>...


From mnot@mnot.net  Sun Dec 16 16:31:38 2012
Return-Path: <mnot@mnot.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 B5D9A21F8514; Sun, 16 Dec 2012 16:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.029
X-Spam-Level: 
X-Spam-Status: No, score=-104.029 tagged_above=-999 required=5 tests=[AWL=-1.430, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xHeA2I-e7VRQ; Sun, 16 Dec 2012 16:31:38 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id F3D0221F84F8; Sun, 16 Dec 2012 16:31:37 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 0B3A6509B7; Sun, 16 Dec 2012 19:31:33 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.com>
Date: Mon, 17 Dec 2012 11:31:29 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <45747DE2-66C7-4198-9BA2-06B3D27E6F2C@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net> <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com> <CAC4RtVDRt5xkvcpf54x0tkZpQcK6=r-WuhVPW5zisJD2pyn=-Q@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 00:31:38 -0000

Works for me.

On 17/12/2012, at 10:12 AM, Barry Leiba <barryleiba@computer.org> wrote:

> Anyone have any comments on what I suggested below?
>=20
> Barry
>=20
> On Tue, Dec 11, 2012 at 11:25 PM, Barry Leiba =
<barryleiba@computer.org> wrote:
>>> Personally -- to me, it seems like you're getting hung up on the =
word "add."
>> ...
>>> "add" means what the format definition says it means, because =
otherwise
>>> we have to rationalise all of the different systems people might use =
it with
>>> to make sense.
>>=20
>> OK, I'll buy that.  Then let's take a different approach, and make it
>> clearer that it's Humpty Dumpty's version of "add", so maybe neither =
I
>> nor Alice will get hung up on it:
>>=20
>> OLD
>>   The "add" operation adds a new value at the target location. The
>>   operation object MUST contain a "value" member that specifies the
>>   value to be added.
>> NEW
>>   The "add" operation performs the following function, depending upon
>>   what the target location references (see details below):
>>=20
>>   o  If the target location specifies an array index, a new value is
>>      inserted into the array at the specified index.
>>=20
>>   o  If the target location specifies an object member that does not
>>      already exist, a new member is added to the object.
>>=20
>>   o  If the target location specifies an object member that does
>>      exist, that member's value is replaced.
>> END
>>=20
>> That may be wordier than we need, but I think it makes the point...
>> feel free to wordsmith.  With something like that, I think we can say
>> that we had to pick a name, "add" was picked, and it means exactly
>> what we choose it to mean - neither more nor less.  And that's glory
>> for you.
>>=20
>> Barry

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




From mnot@mnot.net  Sun Dec 16 16:33:48 2012
Return-Path: <mnot@mnot.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 0F0DC21F87BD for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 16:33:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.996
X-Spam-Level: 
X-Spam-Status: No, score=-103.996 tagged_above=-999 required=5 tests=[AWL=-1.397, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YH65rc7FtfSI for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 16:33:47 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED8521F8782 for <ietf@ietf.org>; Sun, 16 Dec 2012 16:33:47 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 32126509B5; Sun, 16 Dec 2012 19:33:45 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p1obhwldti.fsf@d72933.na.sas.com>
Date: Mon, 17 Dec 2012 11:33:41 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6B4F2945-EC54-4171-92FF-3A88CEB27D23@mnot.net>
References: <p1obhwldti.fsf@d72933.na.sas.com>
To: David J. Biesack <David.Biesack@sas.com>
X-Mailer: Apple Mail (2.1499)
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, 17 Dec 2012 00:33:48 -0000

David,

This was discussed in the Working Group, but it wasn't felt that the =
added complexity was worth it; there's a strong feeling that this spec =
should be as simple as possible.

Cheers,


On 15/12/2012, at 4:54 AM, David J. Biesack <David.Biesack@sas.com> =
wrote:

>=20
> I originally posted this in a "Re: Last Call: =
<draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed =
Standard" thread
> but now I've read draft-ietf-appsawg-json-pointer-07 and have changed =
that suggestion to reflect draft-ietf-appsawg-json-pointer-07
>=20
> Suggestion: allow negative numbers to indicate a position counted from =
the end of the array instead "array/-".
>=20
> For example, a/-1 to point to the last item in an array (length > 0), =
-2 to point to the penultimate item, and so on.=20
> The notation -i is an alias for (array.length - i)
>=20
> It is an error if |i| > array length.
>=20
> For the json-patch "add" operation, use=20
>=20
>   { "op" : "add", "path" : "...array/-1", "value" : value }=20
>=20
> to append to the end, "...array/-2" to insert before the last item, =
and so on.
> The "path" is the path that the item will be addressed by after =
inserting it.
> I.e. after appending to an array of length l at j < 0, the item will =
be at the zero-based index (l + 1) + j.=20
>=20
> E.g. given the document with an array of length 4:
>=20
> { "a" : [ 0, 1, 2, 3, ] }
>=20
> then=20
>=20
> { "op" : "add", "path" : "/a/-1", "value" : 99 }
>=20
> yields
>=20
> { "a" : [ 0, 1, 2, 3, 99] }
>=20
> i.e. 99 is found at (4 + 1) -1 =3D=3D 4
>=20
>=20
> { "op" : "add", "path" : "/a/-2", "value" : 99}
>=20
> yields
>=20
> { "a" : [ 0, 1, 2, 99, 3] }
>=20
> i.e. 99 is found at (4 + 1) -2 =3D=3D 3
>=20
> and finally
>=20
> { "op" : "add", "path" : "/a/-5", "value" : 99 }
>=20
> yields
>=20
> { "a" : [ 99, 0, 1, 2, 3] }
>=20
> i.e. 99 is found at (4 + 1) -5 =3D=3D 0
>=20
> --=20
> David J. Biesack | Principal API Architect, SAS | @davidbiesack | =
919-531-7771 | www.sas.com
>=20

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




From jasnell@gmail.com  Sun Dec 16 18:35:44 2012
Return-Path: <jasnell@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 6399F21F8860; Sun, 16 Dec 2012 18:35:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.687
X-Spam-Level: 
X-Spam-Status: No, score=-3.687 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiXuVS202seV; Sun, 16 Dec 2012 18:35:43 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0446421F8825; Sun, 16 Dec 2012 18:35:42 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so8520174ieb.31 for <multiple recipients>; Sun, 16 Dec 2012 18:35:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q8FyqoDZvfe5BBRIx/TCBDqQc0TuUN2a4xXnEYIFs5k=; b=NudX4eixKcjNA7nw6jd9AQ64zsrjeqOCWrCYEG/T75JbUlN/nI4tTheP1Qr7iN2v8i eo96ahbRlno5hbOhYnf/RzWXrzaV4e5TbggPQPPOquTpuXw21jiY4wZ9PrNu8BdkAFhy FiXcLmBankT/CjtEcuZirdxWMqqL3+LharHnrYquLlfRqp5W2RU4A6er8Co1YdBWg1z5 DoBVrMQ423eZhuDeT6K2HI0bGn0uL5ZRc+OVgzh/of/QDyEbZU6tma7uJ+ts1Ucp1vSz wjAROzx7VNT0I5hiVmWM13Jr/utTVT9WRiXZyfkCCMrMLWJKVSxGZLvBrJ4AhygOs5Ke weCQ==
MIME-Version: 1.0
Received: by 10.50.151.165 with SMTP id ur5mr7887996igb.24.1355711742549; Sun, 16 Dec 2012 18:35:42 -0800 (PST)
Received: by 10.64.7.19 with HTTP; Sun, 16 Dec 2012 18:35:42 -0800 (PST)
Received: by 10.64.7.19 with HTTP; Sun, 16 Dec 2012 18:35:42 -0800 (PST)
In-Reply-To: <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com>
Date: Sun, 16 Dec 2012 18:35:42 -0800
Message-ID: <CABP7RbdG6-g-rS_Gh=hwjxX-ArE+okvONUqssujDF9Q2Ot9ugQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: James M Snell <jasnell@gmail.com>
To: Matthew Morley <matt@mpcm.com>
Content-Type: multipart/alternative; boundary=e89a8f23541dd51e2704d1033cdd
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 02:35:44 -0000

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

Using json-patch with my json-predicates draft allows testing for existing
value type before applying a patch operation.
On Dec 16, 2012 4:33 PM, "Matthew Morley" <matt@mpcm.com> wrote:

> I am usually lurking and struggling to keep up with these posts. But, I
> concur with James, this really is a non-issue in practice.
>
> The JSON Pointer expresses a path down a JSON object to a specific contex=
t.
> The Patch expresses a change within or to that context.
> Everything about the both standards is about that end context.
>
> If you want to confirm the type of the context before applying a patch,
> this should probably be part of a test operation. I'm not sure if this is
> possible at this point (?), but that is where the logic should exist.
>
>
> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> wrote=
:
>
>>
>>
>>
>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>>
>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>> <markus.lanthaler@gmx.net> wrote:
>>> >
>>> > Hmm.. I think that=E2=80=99s quite problematic. Especially considerin=
g how
>>> JSON Pointer is used in JSON Patch.
>>>
>>> I agree--I provided the same feedback privately. It seems
>>> straightforwardly unsound.
>>>
>>>
>> In practice it doesn't seem to be much of an issue.
>>
>> Specifically, if I GET an existing document and get an etag with the
>> JSON, then make some changes and send a PATCH with If-Match, the fact th=
at
>> any given pointer could point to an array or object member doesn't reall=
y
>> matter much.
>>
>> For example:
>>
>>   >  GET /the/doc HTTP/1.1
>>
>>   <  HTTP/1.1 200 OK
>>      ETag: "my-document-tag"
>>      Content-Type: application/json
>>
>>      {"1":"foo"}
>>
>>   >  PATCH /the/doc HTTP/1.1
>>      If-Match: "my-document-etag"
>>      Content-Type: application/json-patch
>>
>>      [{"op":"add","path":"/2","value":"bar"}]
>>
>> Generally speaking, someone should not be using PATCH to perform a
>> partial modification if they don't already have some knowledge in advanc=
e
>> what they are modifying. The only time the apparent ambiguity becomes an
>> issue is when a client is blindly sending a patch to an unknown endpoint=
...
>> in which case, you get whatever you end up with.
>>
>> - James
>>
>>
>>
>>> - Rob
>>>
>>>
>>> >
>>> > --
>>> >
>>> > Markus Lanthaler
>>> >
>>> > @markuslanthaler
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > From: James M Snell [mailto:jasnell@gmail.com]
>>> > Sent: Friday, December 14, 2012 5:41 PM
>>> > To: Markus Lanthaler
>>> > Cc: IETF Discussion; IETF Apps Discuss
>>> > Subject: Re: [apps-discuss] Last Call:
>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Sta=
ndard
>>> >
>>> >
>>> >
>>> > JSON Pointer does not distinguish between objects and arrays. That is
>>> not determined until the pointer is applied to an actual object instanc=
e...
>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>> >
>>> >
>>> >
>>> > On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler <
>>> markus.lanthaler@gmx.net> wrote:
>>> >
>>> > I've asked that before but didn't get an answer. So let me ask again
>>> (even
>>> > though I'm quite sure it has already been asked by somebody else).
>>> >
>>> > How does JSON Pointer distinguish between objects and arrays? E.g.
>>> consider
>>> > the following JSON document:
>>> >
>>> > {
>>> >   "foo": "bar",
>>> >   "1": "baz"
>>> > }
>>> >
>>> > As I read the draft, the JSON Pointer "/1" would evaluate to "baz" ev=
en
>>> > though that's probably not what the author intended. Is there a way t=
o
>>> avoid
>>> > that?
>>> >
>>> >
>>> > Thanks,
>>> > Markus
>>> >
>>> >
>>> >
>>> > --
>>> > Markus Lanthaler
>>> > @markuslanthaler
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > > -----Original Message-----
>>> > > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>> > > bounces@ietf.org] On Behalf Of The IESG
>>> > > Sent: Tuesday, December 11, 2012 4:01 PM
>>> > > To: IETF-Announce
>>> > > Cc: apps-discuss@ietf.org
>>> > > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer=
-
>>> > > 07.txt> (JSON Pointer) to Proposed Standard
>>> > >
>>> > >
>>> > > The IESG has received a request from the Applications Area Working
>>> > > Group
>>> > > WG (appsawg) to consider the following document:
>>> > > - 'JSON Pointer'
>>> > >   <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>> > >
>>> > > The IESG plans to make a decision in the next few weeks, and solici=
ts
>>> > > final comments on this action. Please send substantive comments to
>>> the
>>> > > ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments
>>> may
>>> > > be
>>> > > sent to iesg@ietf.org instead. In either case, please retain the
>>> > > beginning of the Subject line to allow automated sorting.
>>> > >
>>> > > Abstract
>>> > >
>>> > >
>>> > >    JSON Pointer defines a string syntax for identifying a specific
>>> > > value
>>> > >    within a JSON document.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > The file can be obtained via
>>> > > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>> > >
>>> > > IESG discussion can be tracked via
>>> > >
>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
>>> > >
>>> > >
>>> > > No IPR declarations have been submitted directly on this I-D.
>>> > >
>>> > >
>>> > > _______________________________________________
>>> > > apps-discuss mailing list
>>> > > apps-discuss@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/apps-discuss
>>> >
>>> > _______________________________________________
>>> > apps-discuss mailing list
>>> > apps-discuss@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > apps-discuss mailing list
>>> > apps-discuss@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>>> >
>>>
>>
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>>
>
>
> --
> Matthew P. C. Morley
>

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

<p dir=3D"ltr">Using json-patch with my json-predicates draft allows testin=
g for existing value type before applying a patch operation. </p>
<div class=3D"gmail_quote">On Dec 16, 2012 4:33 PM, &quot;Matthew Morley&qu=
ot; &lt;<a href=3D"mailto:matt@mpcm.com">matt@mpcm.com</a>&gt; wrote:<br ty=
pe=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
I am usually lurking and struggling to keep up with these posts. But, I con=
cur with James, this really is a non-issue in practice.<br><br>The JSON Poi=
nter expresses=C2=A0a path down a JSON object to a specific context.<br>The=
 Patch expresses a change within or to that context.<br>

Everything about the both standards is about that end context.<br><br>If yo=
u want to confirm the type of the context before applying a patch, this sho=
uld probably be part of a test operation.=C2=A0I&#39;m not sure if this is =
possible at this point (?), but that is where the logic should exist.<br>

<br><br><div class=3D"gmail_quote">On Sun, Dec 16, 2012 at 12:22 AM, James =
M Snell <span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com" target=
=3D"_blank">jasnell@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">

<font face=3D"courier new,monospace"><br></font><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote"><div>On Sat, Dec 15, 2012 at 8:36 PM, Ro=
bert Sayre <span dir=3D"ltr">&lt;<a href=3D"mailto:sayrer@gmail.com" target=
=3D"_blank">sayrer@gmail.com</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>On Fri, Dec 14, 2012 at 9:17 AM, Markus=
 Lanthaler<br>
&lt;<a href=3D"mailto:markus.lanthaler@gmx.net" target=3D"_blank">markus.la=
nthaler@gmx.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hmm.. I think that=E2=80=99s quite problematic. Especially considering=
 how JSON Pointer is used in JSON Patch.<br>
<br>
</div>I agree--I provided the same feedback privately. It seems<br>
straightforwardly unsound.<br>
<br></blockquote><div><br></div></div><div><font face=3D"courier new, monos=
pace">In practice it doesn&#39;t seem to be much of an issue.</font></div><=
div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">Specifically, if I GET an existing document and=
 get an etag with the JSON, then make some changes and send a PATCH with If=
-Match, the fact that any given pointer could point to an array or object m=
ember doesn&#39;t really matter much.</font></div>



<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">For example:</font></div><div><font face=3D"cou=
rier new, monospace"><br></font></div><div><font face=3D"courier new, monos=
pace">=C2=A0 &gt; =C2=A0GET /the/doc HTTP/1.1</font></div>



<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=C2=A0 &lt; =C2=A0HTTP/1.1 200 OK</font></div><=
div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0ETag: &quot;m=
y-document-tag&quot;</font></div>



<div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0Content-Type=
: application/json</font></div><div><font face=3D"courier new, monospace"><=
br></font></div><div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =
=C2=A0{&quot;1&quot;:&quot;foo&quot;}</font></div>



<div><br></div><div><font face=3D"courier new, monospace">=C2=A0 &gt; =C2=
=A0PATCH /the/doc HTTP/1.1</font></div><div><font face=3D"courier new, mono=
space">=C2=A0 =C2=A0 =C2=A0If-Match: &quot;my-document-etag&quot;</font></d=
iv><div><font face=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0Content-T=
ype: application/json-patch</font></div>



<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=C2=A0 =C2=A0 =C2=A0[{&quot;op&quot;:&quot;add&=
quot;,&quot;path&quot;:&quot;/2&quot;,&quot;value&quot;:&quot;bar&quot;}]</=
font></div><div>



<br></div><div><font face=3D"courier new, monospace">Generally speaking, so=
meone should not be using PATCH to perform a partial modification if they d=
on&#39;t already have some knowledge in advance what they are modifying. Th=
e only time the apparent ambiguity becomes an issue is when a client is bli=
ndly sending a patch to an unknown endpoint... in which case, you get whate=
ver you end up with.=C2=A0</font></div>

<span><font color=3D"#888888">

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">- James</font></div></font></span><div><div><di=
v><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">




- Rob<br>
<div><br>
<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; Markus Lanthaler<br>
&gt;<br>
&gt; @markuslanthaler<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: James M Snell [mailto:<a href=3D"mailto:jasnell@gmail.com" targe=
t=3D"_blank">jasnell@gmail.com</a>]<br>
&gt; Sent: Friday, December 14, 2012 5:41 PM<br>
&gt; To: Markus Lanthaler<br>
&gt; Cc: IETF Discussion; IETF Apps Discuss<br>
</div>&gt; Subject: Re: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-js=
on-pointer-07.txt&gt; (JSON Pointer) to Proposed Standard<br>
<div><div>&gt;<br>
&gt;<br>
&gt;<br>
&gt; JSON Pointer does not distinguish between objects and arrays. That is =
not determined until the pointer is applied to an actual object instance...=
 the pointer &quot;/1&quot; is valid against {&quot;1&quot;:&quot;a&quot;} =
or [&quot;a&quot;,&quot;b&quot;]<br>




&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler &lt;<a href=3D"mailt=
o:markus.lanthaler@gmx.net" target=3D"_blank">markus.lanthaler@gmx.net</a>&=
gt; wrote:<br>
&gt;<br>
&gt; I&#39;ve asked that before but didn&#39;t get an answer. So let me ask=
 again (even<br>
&gt; though I&#39;m quite sure it has already been asked by somebody else).=
<br>
&gt;<br>
&gt; How does JSON Pointer distinguish between objects and arrays? E.g. con=
sider<br>
&gt; the following JSON document:<br>
&gt;<br>
&gt; {<br>
&gt; =C2=A0 &quot;foo&quot;: &quot;bar&quot;,<br>
&gt; =C2=A0 &quot;1&quot;: &quot;baz&quot;<br>
&gt; }<br>
&gt;<br>
&gt; As I read the draft, the JSON Pointer &quot;/1&quot; would evaluate to=
 &quot;baz&quot; even<br>
&gt; though that&#39;s probably not what the author intended. Is there a wa=
y to avoid<br>
&gt; that?<br>
&gt;<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Markus<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Markus Lanthaler<br>
&gt; @markuslanthaler<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:apps-discuss-bounces@ietf.org" target=3D"=
_blank">apps-discuss-bounces@ietf.org</a> [mailto:<a href=3D"mailto:apps-di=
scuss-" target=3D"_blank">apps-discuss-</a><br>
&gt; &gt; <a href=3D"mailto:bounces@ietf.org" target=3D"_blank">bounces@iet=
f.org</a>] On Behalf Of The IESG<br>
&gt; &gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>
&gt; &gt; To: IETF-Announce<br>
&gt; &gt; Cc: <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">ap=
ps-discuss@ietf.org</a><br>
&gt; &gt; Subject: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-json-po=
inter-<br>
&gt; &gt; 07.txt&gt; (JSON Pointer) to Proposed Standard<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The IESG has received a request from the Applications Area Workin=
g<br>
&gt; &gt; Group<br>
&gt; &gt; WG (appsawg) to consider the following document:<br>
&gt; &gt; - &#39;JSON Pointer&#39;<br>
&gt; &gt; =C2=A0 &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; as Proposed=
 Standard<br>
&gt; &gt;<br>
&gt; &gt; The IESG plans to make a decision in the next few weeks, and soli=
cits<br>
&gt; &gt; final comments on this action. Please send substantive comments t=
o the<br>
&gt; &gt; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org<=
/a> mailing lists by 2012-12-25. Exceptionally, comments may<br>
&gt; &gt; be<br>
&gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@i=
etf.org</a> instead. In either case, please retain the<br>
&gt; &gt; beginning of the Subject line to allow automated sorting.<br>
&gt; &gt;<br>
&gt; &gt; Abstract<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; =C2=A0 =C2=A0JSON Pointer defines a string syntax for identifying=
 a specific<br>
&gt; &gt; value<br>
&gt; &gt; =C2=A0 =C2=A0within a JSON document.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The file can be obtained via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-jso=
n-pointer/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-ap=
psawg-json-pointer/</a><br>
&gt; &gt;<br>
&gt; &gt; IESG discussion can be tracked via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-jso=
n-pointer/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-=
ietf-appsawg-json-pointer/ballot/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; apps-discuss mailing list<br>
&gt; &gt; <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-d=
iscuss@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discus=
s@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discus=
s@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
</div></div></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discuss@iet=
f.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Matthew =
P. C. Morley<br>
</blockquote></div>

--e89a8f23541dd51e2704d1033cdd--

From mnot@mnot.net  Sun Dec 16 19:25:48 2012
Return-Path: <mnot@mnot.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 1FC2C21F8554; Sun, 16 Dec 2012 19:25:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.965
X-Spam-Level: 
X-Spam-Status: No, score=-103.965 tagged_above=-999 required=5 tests=[AWL=-1.366, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4q7yZIEu835E; Sun, 16 Dec 2012 19:25:47 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 1924521F89AC; Sun, 16 Dec 2012 19:25:46 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 40484509B5; Sun, 16 Dec 2012 22:25:43 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART LC review of draft-ietf-appsawg-json-patch-08
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <023301cddb5f$73eb02d0$5bc10870$@gmail.com>
Date: Mon, 17 Dec 2012 14:25:40 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net>
References: <023301cddb5f$73eb02d0$5bc10870$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-appsawg-json-patch.all@tools.ietf.org, 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, 17 Dec 2012 03:25:48 -0000

Both fixed in SVN; thanks for the review.


On 16/12/2012, at 6:32 PM, Roni Even <ron.even.tlv@gmail.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
> =20
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> =20
> Document: draft-ietf-appsawg-json-patch-08
> Reviewer: Roni Even
> Review Date:2012=9612=9616
> IETF LC End Date: 2012=9612=9625
> IESG Telechat date: 2013-1-10
> =20
> Summary: This draft is almost  ready for publication.
> =20
> =20
> Major issues:
> =20
> Minor issues:
> 1.       The document has as the intended status =93Informational=94 =
while the last call says that the intended status is proposed standard?
> =20
> =20
> Nits/editorial comments:
>=20
> 	=95 In the IANA section the =93Encoding considerations:  =
binary=94. I noticed that RFC 4627 has a broader description:
> =93Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32
> JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is =
written in UTF-8, JSON is 8bit compatible.  When JSON is written in =
UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.=94
> =20
> =20
>=20

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




From mnot@mnot.net  Sun Dec 16 19:30:27 2012
Return-Path: <mnot@mnot.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 2E54F21F85C4; Sun, 16 Dec 2012 19:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.935
X-Spam-Level: 
X-Spam-Status: No, score=-103.935 tagged_above=-999 required=5 tests=[AWL=-1.336, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A3FnpCkCz3tq; Sun, 16 Dec 2012 19:30:26 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 51F1921F85BA; Sun, 16 Dec 2012 19:30:26 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 714C0509B8; Sun, 16 Dec 2012 22:30:23 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com>
Date: Mon, 17 Dec 2012 14:30:21 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1E0F71D3-DC1C-4342-AFB1-D2CAAA71AA2E@mnot.net>
References: <20121211150005.28209.96763.idtracker@ietfa.amsl.com> <CAC4RtVBNxQu03hZxFZiRg-7s2G_KYKFJjUUvSC_UUFwE_FZFdg@mail.gmail.com> <3448719B-185A-476A-A927-25A68D4B4358@mnot.net> <CALaySJ+BMsBJt7wWHN90itdPcqUqSd0gMh_YzmHZpN=8jcKJJA@mail.gmail.com> <82A453F8-9F1A-4427-B238-A63B43447F21@mnot.net> <CALaySJJ33RjEJRNbY3-PREMbE76SyFi+hpQg2BwgFd8N2DOWNw@mail.gmail.com> <E22F085E-5C3C-4628-BAF9-0AE3FA32063D@mnot.net> <CAC4RtVCdE5jK4hm_wgzfrOQZ3edmYosyRz=xck06Hxz068AK_Q@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>, "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 03:30:27 -0000

Now in SVN.


On 12/12/2012, at 3:25 PM, Barry Leiba <barryleiba@computer.org> wrote:

>> Personally -- to me, it seems like you're getting hung up on the word =
"add."
> ...
>> "add" means what the format definition says it means, because =
otherwise
>> we have to rationalise all of the different systems people might use =
it with
>> to make sense.
>=20
> OK, I'll buy that.  Then let's take a different approach, and make it
> clearer that it's Humpty Dumpty's version of "add", so maybe neither I
> nor Alice will get hung up on it:
>=20
> OLD
>   The "add" operation adds a new value at the target location. The
>   operation object MUST contain a "value" member that specifies the
>   value to be added.
> NEW
>   The "add" operation performs the following function, depending upon
>   what the target location references (see details below):
>=20
>   o  If the target location specifies an array index, a new value is
>      inserted into the array at the specified index.
>=20
>   o  If the target location specifies an object member that does not
>      already exist, a new member is added to the object.
>=20
>   o  If the target location specifies an object member that does
>      exist, that member's value is replaced.
> END
>=20
> That may be wordier than we need, but I think it makes the point...
> feel free to wordsmith.  With something like that, I think we can say
> that we had to pick a name, "add" was picked, and it means exactly
> what we choose it to mean - neither more nor less.  And that's glory
> for you.
>=20
> Barry

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




From mnot@mnot.net  Sun Dec 16 19:40:19 2012
Return-Path: <mnot@mnot.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 C2CA821F88A5 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 19:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.907
X-Spam-Level: 
X-Spam-Status: No, score=-103.907 tagged_above=-999 required=5 tests=[AWL=-1.308, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9jIkNOnxAr7 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 19:40:18 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id DA4FA21F88A4 for <ietf@ietf.org>; Sun, 16 Dec 2012 19:40:18 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8EEB3509B5; Sun, 16 Dec 2012 22:40:17 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p1txrolgzo.fsf@d72933.na.sas.com>
Date: Mon, 17 Dec 2012 14:40:14 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CA116C1-3730-4602-AD07-890AABD9211F@mnot.net>
References: <p1txrolgzo.fsf@d72933.na.sas.com>
To: David J. Biesack <David.Biesack@sas.com>
X-Mailer: Apple Mail (2.1499)
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, 17 Dec 2012 03:40:19 -0000

On 15/12/2012, at 3:45 AM, David J. Biesack <David.Biesack@sas.com> =
wrote:

>=20
> "4.1 add" bullet 3 reads (when completing the introductory sentence)
>=20
> ... the target location MUST reference ...
> o An element to add to an existing array.
>=20
> I think this is incorrect; the target location is the array and the =
"value" is the "element to add to an existing array". I suggest:
>=20
> ... the target location MUST reference ...
> o An existing array.


Given the JSON:

{
  "foo": [ "a", "b", "c" ]
}

then a reference to an existing array would be:

/foo

whereas a reference to an element of an existing array would be:

/foo/1

'add'ing to these would have VERY different effects; the former would =
replace the entire array; the latter would replace one member of it.

Both are legal, it's just that the former isn't getting captured in this =
definition; it's an object member, not an array member.

Cheers,

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




From mnot@mnot.net  Sun Dec 16 19:40:51 2012
Return-Path: <mnot@mnot.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 6722521F88D1 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 19:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.88
X-Spam-Level: 
X-Spam-Status: No, score=-103.88 tagged_above=-999 required=5 tests=[AWL=-1.281, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDPsGDnO0APJ for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 19:40:50 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id C946521F88CF for <ietf@ietf.org>; Sun, 16 Dec 2012 19:40:50 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 898A2509B5; Sun, 16 Dec 2012 22:40:49 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p14njolbt4.fsf@d72933.na.sas.com>
Date: Mon, 17 Dec 2012 14:40:48 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A029184-1ABA-4797-9B4F-573F86EFA66A@mnot.net>
References: <p14njolbt4.fsf@d72933.na.sas.com>
To: David J. Biesack <David.Biesack@sas.com>
X-Mailer: Apple Mail (2.1499)
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, 17 Dec 2012 03:40:51 -0000

... and I just caught up with my e-mail; no worries :)


On 15/12/2012, at 5:37 AM, David J. Biesack <David.Biesack@sas.com> =
wrote:

>=20
> I wrote previously :
>=20
>> "4.1 add" bullet 3 reads (when completing the introductory sentence)=20=

>>=20
>> ... the target location MUST reference ...=20
>> o An element to add to an existing array.=20
>>=20
>> I think this is incorrect; the target location is the array and the =
"value" is the "element to add to an existing array". I suggest:=20
>>=20
>> ... the target location MUST reference ...=20
>> o An existing array.=20
>=20
> but now I see my error; the examples at the bottom of the doc clarify
> the JSON-Pointer location using the form "/path/to/array/index", so =
the original
> wording is correct. Sorry for the noise.
>=20
> djb
> --=20
> David J. Biesack | Principal API Architect, SAS | @davidbiesack | =
919-531-7771 | www.sas.com
>=20

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




From mnot@mnot.net  Sun Dec 16 20:00:11 2012
Return-Path: <mnot@mnot.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 762B521F88CF for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 20:00:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.854
X-Spam-Level: 
X-Spam-Status: No, score=-103.854 tagged_above=-999 required=5 tests=[AWL=-1.255, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kkwJ3PemBDWN for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 20:00:10 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 911EF21F88C4 for <ietf@ietf.org>; Sun, 16 Dec 2012 20:00:10 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 103F8509B6; Sun, 16 Dec 2012 23:00:08 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p1r4mslf23.fsf@d72933.na.sas.com>
Date: Mon, 17 Dec 2012 15:00:05 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <61917A76-B4BD-4207-8C21-DEAE7BF255D8@mnot.net>
References: <p1r4mslf23.fsf@d72933.na.sas.com>
To: David J. Biesack <David.Biesack@sas.com>
X-Mailer: Apple Mail (2.1499)
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, 17 Dec 2012 04:00:11 -0000

On 15/12/2012, at 4:27 AM, David J. Biesack <David.Biesack@sas.com> =
wrote:

>=20
> Can one add elements of array to an array?=20
>=20
> E.g. given the document
>=20
> { "a" : { "b" : [ "red", "green" ] } }
>=20
> If I want to add two values to an existing array, I can use
>=20
> [
> { "op": "add", "path": "/a/b/-", "value": "blue" },
> { "op": "add", "path": "/a/b/-", "value": "yellow" }
> ]
>=20
> (I found in the examples how an array index is specified in the path, =
not in a separate "index" member;
> I guess my comments there should be directed at =
draft-ietf-appsawg-json-pointer-06 )
>=20
> However, for appending to arrays, I would like to use
>=20
> [ { "op": "add", "path": "/a/b/-", "value": [ "blue", "yellow" ] } ]
>=20
> Reading the spec literally, I expect that this will yield
>=20
> { "a" : { "b" : [ "red", "green", [ "blue", "yellow" ] ] } }

Exactly.

> instead of the desired
>=20
> { "a" : { "b" : [ "red", "green", "blue", "yellow" ] } }
>=20
> I suggest the semantics of this case should be explicit, to avoid =
unexpected surprises.

I've added an example to clarify this; thanks.



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




From mnot@mnot.net  Sun Dec 16 20:19:24 2012
Return-Path: <mnot@mnot.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 DD5AC21F8518 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 20:19:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.829
X-Spam-Level: 
X-Spam-Status: No, score=-103.829 tagged_above=-999 required=5 tests=[AWL=-1.230, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K09qlvywAoz0 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 20:19:22 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id C592D21F850E for <ietf@ietf.org>; Sun, 16 Dec 2012 20:19:22 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6FCA6509B8; Sun, 16 Dec 2012 23:19:21 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p1sj78lfq4.fsf@d72933.na.sas.com>
Date: Mon, 17 Dec 2012 15:19:17 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB1AAE6C-B3B5-418D-A367-D22366EDE86A@mnot.net>
References: <p1sj78lfq4.fsf@d72933.na.sas.com>
To: David J. Biesack <David.Biesack@sas.com>
X-Mailer: Apple Mail (2.1499)
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, 17 Dec 2012 04:19:24 -0000

On 15/12/2012, at 4:13 AM, David J. Biesack <David.Biesack@sas.com> =
wrote:

>=20
> "4.1 add" and "4.2 remove" refers to "specified index", but I do not =
see name of the index member specified in the draft, or how to represent =
it.
> (Other sections are more explicit, i.e. "from" for the "move" op.)
>=20
> i.e. "index" as in=20
>=20
>  "index" : integer=20
>=20
> The phrasing=20
>=20
>   If the "-" character is used to index the end of the array, this has =
the effect of appending the value to the array.
>=20
> is not clear. Where does this "-" character appear? Does one use just
>=20
>  "index" : "-"=20
>=20
> in which case the spec should be=20
>=20
>  If the "-" string is used ...
>=20
> If instead you mean a negative integer, i.e.
>=20
>  "index" : negative-integer
>=20
> and not just "-", does the spec interpret all negative integers to =
indicate appending to the end?

I think a reference to the JSON-Pointer spec at an appropriate place =
here will help readers.

Thanks,



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




From sayrer@gmail.com  Sun Dec 16 20:36:21 2012
Return-Path: <sayrer@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 9EE8121F8942; Sun, 16 Dec 2012 20:36:21 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CfZihLLkO+VK; Sun, 16 Dec 2012 20:36:20 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 48B5321F8938; Sun, 16 Dec 2012 20:36:20 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so2616998wey.31 for <multiple recipients>; Sun, 16 Dec 2012 20:36:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GnRoInqjd7m2nYXc/NT6NIXevyMJ2gW4lBkFEtgK0RU=; b=iRw4LU4XLoCD+H3W/i6Q1lzVMcVx36bNwqW8hZamohMO4NCnDi4Z2dzGCjko+Owv9Z 7TFVfEeDpn3jKpk4xVbIwaOBmawFnKNMmS6651yMaGR+F2zQT9YT8/jZW8kszvrQAJau 5oq8e5cW1GEZbO6bJFzvznOUfRGuGyVIgex8/sCwzT2tt3jEW3GR0AKIF2/5nwlhT3yA X+Q6G3m2hodu6jbDVgA36bBxpPOA6nh2XUK9lhD1nkW2SaorZA60Bt7nZzRF5dCIL/1B wQzjiF2fhLoarDDcSDdejDyjivQA2roR8RUVUcGXnpCjvuB84OOr9+Q4y6pM7fMlOE5N OL2w==
MIME-Version: 1.0
Received: by 10.194.78.162 with SMTP id c2mr14467013wjx.46.1355718979294; Sun, 16 Dec 2012 20:36:19 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Sun, 16 Dec 2012 20:36:19 -0800 (PST)
In-Reply-To: <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com>
Date: Sun, 16 Dec 2012 20:36:19 -0800
Message-ID: <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Matthew Morley <matt@mpcm.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: James M Snell <jasnell@gmail.com>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 04:36:21 -0000

The cost of fixing it seems low, either by changing the path syntax of
JSON pointer or changing the names of operations applied to arrays.
Array-like objects are common enough in JavaScript to make this a
worry. The other suggestions either assume a particular policy for
concurrent edits or require more machinery (test operation etc).
Wouldn't it be simpler to make the patch format more precise?

- Rob

On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
> I am usually lurking and struggling to keep up with these posts. But, I
> concur with James, this really is a non-issue in practice.
>
> The JSON Pointer expresses a path down a JSON object to a specific contex=
t.
> The Patch expresses a change within or to that context.
> Everything about the both standards is about that end context.
>
> If you want to confirm the type of the context before applying a patch, t=
his
> should probably be part of a test operation. I'm not sure if this is
> possible at this point (?), but that is where the logic should exist.
>
>
>
> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> wrote=
:
>>
>>
>>
>>
>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>>>
>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>> <markus.lanthaler@gmx.net> wrote:
>>> >
>>> > Hmm.. I think that=92s quite problematic. Especially considering how =
JSON
>>> > Pointer is used in JSON Patch.
>>>
>>> I agree--I provided the same feedback privately. It seems
>>> straightforwardly unsound.
>>>
>>
>> In practice it doesn't seem to be much of an issue.
>>
>> Specifically, if I GET an existing document and get an etag with the JSO=
N,
>> then make some changes and send a PATCH with If-Match, the fact that any
>> given pointer could point to an array or object member doesn't really ma=
tter
>> much.
>>
>> For example:
>>
>>   >  GET /the/doc HTTP/1.1
>>
>>   <  HTTP/1.1 200 OK
>>      ETag: "my-document-tag"
>>      Content-Type: application/json
>>
>>      {"1":"foo"}
>>
>>   >  PATCH /the/doc HTTP/1.1
>>      If-Match: "my-document-etag"
>>      Content-Type: application/json-patch
>>
>>      [{"op":"add","path":"/2","value":"bar"}]
>>
>> Generally speaking, someone should not be using PATCH to perform a parti=
al
>> modification if they don't already have some knowledge in advance what t=
hey
>> are modifying. The only time the apparent ambiguity becomes an issue is =
when
>> a client is blindly sending a patch to an unknown endpoint... in which c=
ase,
>> you get whatever you end up with.
>>
>> - James
>>
>>
>>>
>>> - Rob
>>>
>>>
>>> >
>>> > --
>>> >
>>> > Markus Lanthaler
>>> >
>>> > @markuslanthaler
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > From: James M Snell [mailto:jasnell@gmail.com]
>>> > Sent: Friday, December 14, 2012 5:41 PM
>>> > To: Markus Lanthaler
>>> > Cc: IETF Discussion; IETF Apps Discuss
>>> > Subject: Re: [apps-discuss] Last Call:
>>> > <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed S=
tandard
>>> >
>>> >
>>> >
>>> > JSON Pointer does not distinguish between objects and arrays. That is
>>> > not determined until the pointer is applied to an actual object insta=
nce...
>>> > the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>> >
>>> >
>>> >
>>> > On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>> > <markus.lanthaler@gmx.net> wrote:
>>> >
>>> > I've asked that before but didn't get an answer. So let me ask again
>>> > (even
>>> > though I'm quite sure it has already been asked by somebody else).
>>> >
>>> > How does JSON Pointer distinguish between objects and arrays? E.g.
>>> > consider
>>> > the following JSON document:
>>> >
>>> > {
>>> >   "foo": "bar",
>>> >   "1": "baz"
>>> > }
>>> >
>>> > As I read the draft, the JSON Pointer "/1" would evaluate to "baz" ev=
en
>>> > though that's probably not what the author intended. Is there a way t=
o
>>> > avoid
>>> > that?
>>> >
>>> >
>>> > Thanks,
>>> > Markus
>>> >
>>> >
>>> >
>>> > --
>>> > Markus Lanthaler
>>> > @markuslanthaler
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > > -----Original Message-----
>>> > > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>> > > bounces@ietf.org] On Behalf Of The IESG
>>> > > Sent: Tuesday, December 11, 2012 4:01 PM
>>> > > To: IETF-Announce
>>> > > Cc: apps-discuss@ietf.org
>>> > > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer=
-
>>> > > 07.txt> (JSON Pointer) to Proposed Standard
>>> > >
>>> > >
>>> > > The IESG has received a request from the Applications Area Working
>>> > > Group
>>> > > WG (appsawg) to consider the following document:
>>> > > - 'JSON Pointer'
>>> > >   <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>> > >
>>> > > The IESG plans to make a decision in the next few weeks, and solici=
ts
>>> > > final comments on this action. Please send substantive comments to
>>> > > the
>>> > > ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments
>>> > > may
>>> > > be
>>> > > sent to iesg@ietf.org instead. In either case, please retain the
>>> > > beginning of the Subject line to allow automated sorting.
>>> > >
>>> > > Abstract
>>> > >
>>> > >
>>> > >    JSON Pointer defines a string syntax for identifying a specific
>>> > > value
>>> > >    within a JSON document.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > The file can be obtained via
>>> > > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>> > >
>>> > > IESG discussion can be tracked via
>>> > >
>>> > > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/bal=
lot/
>>> > >
>>> > >
>>> > > No IPR declarations have been submitted directly on this I-D.
>>> > >
>>> > >
>>> > > _______________________________________________
>>> > > apps-discuss mailing list
>>> > > apps-discuss@ietf.org
>>> > > https://www.ietf.org/mailman/listinfo/apps-discuss
>>> >
>>> > _______________________________________________
>>> > apps-discuss mailing list
>>> > apps-discuss@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > apps-discuss mailing list
>>> > apps-discuss@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>>> >
>>
>>
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>
>
>
> --
> Matthew P. C. Morley

From mnot@mnot.net  Sun Dec 16 21:41:33 2012
Return-Path: <mnot@mnot.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 9544721F8B30; Sun, 16 Dec 2012 21:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.776
X-Spam-Level: 
X-Spam-Status: No, score=-103.776 tagged_above=-999 required=5 tests=[AWL=-1.177, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gkMtbHboJWM7; Sun, 16 Dec 2012 21:41:31 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id A73CA21F89E9; Sun, 16 Dec 2012 21:41:30 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4BA40509B7; Mon, 17 Dec 2012 00:41:27 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com>
Date: Mon, 17 Dec 2012 16:41:24 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com>
To: Robert Sayre <sayrer@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@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: Mon, 17 Dec 2012 05:41:33 -0000

Robert,=20

This was discussed extensively in the Working Group.=20

The root of the issue was that some people reflexively felt that this =
was necessary, but upon reflection, we decided it wasn't; although it =
seems "natural" to some, especially those coming from a static language =
background, it didn't provide any utility.

You might argue that someone who (for example) adds to "/foo/1" in the =
mistaken belief that it's an array, when in fact it's an object, will =
get surprising results. That's true, but if we were to solve this =
problem, that person would still need to understand the underlying =
semantics of "foo" to do anything useful to it -- and I'm not hearing =
anyone complain about that (I hope).

Put another way -- do you really think that people PATCHing something as =
if it's an array (when in fact it's an object) is a significant, =
real-world problem, given that the patch author already has to =
understand the semantics of the document they're patching? I don't, and =
the WG didn't either.

Regards,


On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:

> The cost of fixing it seems low, either by changing the path syntax of
> JSON pointer or changing the names of operations applied to arrays.
> Array-like objects are common enough in JavaScript to make this a
> worry. The other suggestions either assume a particular policy for
> concurrent edits or require more machinery (test operation etc).
> Wouldn't it be simpler to make the patch format more precise?
>=20
> - Rob
>=20
> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
>> I am usually lurking and struggling to keep up with these posts. But, =
I
>> concur with James, this really is a non-issue in practice.
>>=20
>> The JSON Pointer expresses a path down a JSON object to a specific =
context.
>> The Patch expresses a change within or to that context.
>> Everything about the both standards is about that end context.
>>=20
>> If you want to confirm the type of the context before applying a =
patch, this
>> should probably be part of a test operation. I'm not sure if this is
>> possible at this point (?), but that is where the logic should exist.
>>=20
>>=20
>>=20
>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> =
wrote:
>>>=20
>>>=20
>>>=20
>>>=20
>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> =
wrote:
>>>>=20
>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>=20
>>>>> Hmm.. I think that=92s quite problematic. Especially considering =
how JSON
>>>>> Pointer is used in JSON Patch.
>>>>=20
>>>> I agree--I provided the same feedback privately. It seems
>>>> straightforwardly unsound.
>>>>=20
>>>=20
>>> In practice it doesn't seem to be much of an issue.
>>>=20
>>> Specifically, if I GET an existing document and get an etag with the =
JSON,
>>> then make some changes and send a PATCH with If-Match, the fact that =
any
>>> given pointer could point to an array or object member doesn't =
really matter
>>> much.
>>>=20
>>> For example:
>>>=20
>>>> GET /the/doc HTTP/1.1
>>>=20
>>>  <  HTTP/1.1 200 OK
>>>     ETag: "my-document-tag"
>>>     Content-Type: application/json
>>>=20
>>>     {"1":"foo"}
>>>=20
>>>> PATCH /the/doc HTTP/1.1
>>>     If-Match: "my-document-etag"
>>>     Content-Type: application/json-patch
>>>=20
>>>     [{"op":"add","path":"/2","value":"bar"}]
>>>=20
>>> Generally speaking, someone should not be using PATCH to perform a =
partial
>>> modification if they don't already have some knowledge in advance =
what they
>>> are modifying. The only time the apparent ambiguity becomes an issue =
is when
>>> a client is blindly sending a patch to an unknown endpoint... in =
which case,
>>> you get whatever you end up with.
>>>=20
>>> - James
>>>=20
>>>=20
>>>>=20
>>>> - Rob
>>>>=20
>>>>=20
>>>>>=20
>>>>> --
>>>>>=20
>>>>> Markus Lanthaler
>>>>>=20
>>>>> @markuslanthaler
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>> To: Markus Lanthaler
>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to =
Proposed Standard
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> JSON Pointer does not distinguish between objects and arrays. That =
is
>>>>> not determined until the pointer is applied to an actual object =
instance...
>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>=20
>>>>> I've asked that before but didn't get an answer. So let me ask =
again
>>>>> (even
>>>>> though I'm quite sure it has already been asked by somebody else).
>>>>>=20
>>>>> How does JSON Pointer distinguish between objects and arrays? E.g.
>>>>> consider
>>>>> the following JSON document:
>>>>>=20
>>>>> {
>>>>>  "foo": "bar",
>>>>>  "1": "baz"
>>>>> }
>>>>>=20
>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" =
even
>>>>> though that's probably not what the author intended. Is there a =
way to
>>>>> avoid
>>>>> that?
>>>>>=20
>>>>>=20
>>>>> Thanks,
>>>>> Markus
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --
>>>>> Markus Lanthaler
>>>>> @markuslanthaler
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>> -----Original Message-----
>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>> To: IETF-Announce
>>>>>> Cc: apps-discuss@ietf.org
>>>>>> Subject: [apps-discuss] Last Call: =
<draft-ietf-appsawg-json-pointer-
>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>=20
>>>>>>=20
>>>>>> The IESG has received a request from the Applications Area =
Working
>>>>>> Group
>>>>>> WG (appsawg) to consider the following document:
>>>>>> - 'JSON Pointer'
>>>>>>  <draft-ietf-appsawg-json-pointer-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 2012-12-25. Exceptionally, =
comments
>>>>>> may
>>>>>> be
>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>=20
>>>>>> Abstract
>>>>>>=20
>>>>>>=20
>>>>>>   JSON Pointer defines a string syntax for identifying a specific
>>>>>> value
>>>>>>   within a JSON document.
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>>=20
>>>>>> The file can be obtained via
>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>>>>>=20
>>>>>> IESG discussion can be tracked via
>>>>>>=20
>>>>>> =
http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
>>>>>>=20
>>>>>>=20
>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>=20
>>>>>>=20
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>=20
>>>>> _______________________________________________
>>>>> apps-discuss mailing list
>>>>> apps-discuss@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>=20
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> _______________________________________________
>>>>> apps-discuss mailing list
>>>>> apps-discuss@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>=20
>>=20
>>=20
>>=20
>> --
>> Matthew P. C. Morley
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss

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




From sayrer@gmail.com  Mon Dec 17 02:01:32 2012
Return-Path: <sayrer@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 D254421F8A6B; Mon, 17 Dec 2012 02:01:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.117
X-Spam-Level: 
X-Spam-Status: No, score=-2.117 tagged_above=-999 required=5 tests=[AWL=0.282,  BAYES_00=-2.599, J_CHICKENPOX_31=0.6, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bkR4QSNJZlE7; Mon, 17 Dec 2012 02:01:28 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id 086DC21F842B; Mon, 17 Dec 2012 02:01:27 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hj13so1794096wib.13 for <multiple recipients>; Mon, 17 Dec 2012 02:01:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=6oM4a7Ql/IhvEkMqKzq6CR/2utGalGeLqJHkLpoQrHY=; b=frcxaD1uQ1FSCm9pleQ2/EzcFmEyJmNBIlKhDrrbcGlxnSTPatWj0WwYufj7z5QTWo bnAZJHiGf+8EBEGrPKEI2dCLFVXoPVNd1LgIVnJhwt8l9Q6M68BFW+PNCrOp8oOWg/IO fSKG8n/gyr6qw/fuBYLFJIpyNkVdRF4FMkkh3jSNXnaT88jjqaRkMhLTyLn/c3yOKSpK cJNZ6lPQT8NpR8Q/4wuqdzl4T0WSIoowkr42IwX1lpTnjOVqU7QKrK7estC7BPmR+oGc CYGPBmjPGbbLj4W/sdDFKZow/+nVOGKEED36FlmF/l8rny5426kkeNtTdJb2Dpvr7zvA Hofg==
MIME-Version: 1.0
Received: by 10.180.72.232 with SMTP id g8mr14601997wiv.0.1355738487127; Mon, 17 Dec 2012 02:01:27 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Mon, 17 Dec 2012 02:01:27 -0800 (PST)
In-Reply-To: <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net>
Date: Mon, 17 Dec 2012 02:01:27 -0800
Message-ID: <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@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: Mon, 17 Dec 2012 10:01:33 -0000

On Sun, Dec 16, 2012 at 9:41 PM, Mark Nottingham <mnot@mnot.net> wrote:
> Robert,
>
> This was discussed extensively in the Working Group.

Presumably every line of the document was discussed by the WG at some
point. This phase of review is wider, and this point has been raised
separately three times, so perhaps the WG should take another look.
One thing that strikes me about the arguments in favor of the status
quo is that they seem non-technical. Is there a technical case for
leaving this ambiguity in the patch format?

> The root of the issue was that some people reflexively felt that this was=
 necessary, but upon reflection, we decided it wasn't; although it seems "n=
atural" to some, especially those coming from a static language background,=
 it didn't provide any utility.

I'm approaching it as an implementor in JavaScript that happens to
have spent some on the ECMAScript committee and implemented the native
JSON.parse and JSON.stringify methods for Mozilla Firefox. I think
this issue leaves open a chance for data corruption with no real
upside. I could understand leaving it be if making arrays explicit in
the patch format were complex or onerous, but I don't think anyone is
arguing that.

>
> You might argue that someone who (for example) adds to "/foo/1" in the mi=
staken belief that it's an array, when in fact it's an object, will get sur=
prising results. That's true, but if we were to solve this problem, that pe=
rson would still need to understand the underlying semantics of "foo" to do=
 anything useful to it -- and I'm not hearing anyone complain about that (I=
 hope).

The first case that can come up is editing documents that have been
refactored. It's quite common to refactor JSON documents as below when
a little extra metadata is needed for a collection:

{ "foo":[1,2,3] }

then becomes

{
  "foo":
  "bar": "baz",
  "members": [1,2,3]
}

now, an operation on /foo/1 is quite a different thing in the second
document. It's not too hard to see how a client that's been out of
contact with the server for a while could send an addition to /foo
intended for the array that's been moved down to "members". Now, there
are ways to catch this if you're willing to bloat the patch document
with other checks, or by insisting on a matching ETag. But one of the
nice things about patch formats is that you can try for more
optimistic concurrent editing. This ambiguity in the patch format
makes it needlessly more costly to detect unsound edits.

Another source of bugs from JavaScript side of things will be
"array-like" objects. These are really quite common (jQuery lists,
arguments object, etc), and authors very often don't realize they
won't be serialized as an array. To be sure, this is a bug on the
author's side, but some checks in the patch format would really help.
They'll probably become even more common as ES6 is standardizing
iterators http://wiki.ecmascript.org/doku.php?id=3Dharmony:iterators.
Here's an example in a JS REPL using the arguments object (but keep in
mind there are many other objects out there that behave this way).

> function foo(list) { console.log(JSON.stringify(list)) }
> function bar(a,b,c) { foo(arguments) }
> bar("a", "b", "c");
{"0":"a","1":"b","2":"c"}

>
> Put another way -- do you really think

Yes, really.

> that people PATCHing something as if it's an array (when in fact it's an =
object) is a significant, real-world problem, given that the patch author a=
lready has to understand the semantics of the document they're patching?

I don't see that requirement in the draft, and I certainly wouldn't
bet on it being true in all cases. Wasn't one of the motivating
use-cases for this patch format CouchDB? That software operates on
arbitrary, user-defined JSON documents.

- Rob

> I don't, and the WG didn't either.
>
> Regards,
>
>
> On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>
>> The cost of fixing it seems low, either by changing the path syntax of
>> JSON pointer or changing the names of operations applied to arrays.
>> Array-like objects are common enough in JavaScript to make this a
>> worry. The other suggestions either assume a particular policy for
>> concurrent edits or require more machinery (test operation etc).
>> Wouldn't it be simpler to make the patch format more precise?
>>
>> - Rob
>>
>> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
>>> I am usually lurking and struggling to keep up with these posts. But, I
>>> concur with James, this really is a non-issue in practice.
>>>
>>> The JSON Pointer expresses a path down a JSON object to a specific cont=
ext.
>>> The Patch expresses a change within or to that context.
>>> Everything about the both standards is about that end context.
>>>
>>> If you want to confirm the type of the context before applying a patch,=
 this
>>> should probably be part of a test operation. I'm not sure if this is
>>> possible at this point (?), but that is where the logic should exist.
>>>
>>>
>>>
>>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> wro=
te:
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wrote=
:
>>>>>
>>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>
>>>>>> Hmm.. I think that=92s quite problematic. Especially considering how=
 JSON
>>>>>> Pointer is used in JSON Patch.
>>>>>
>>>>> I agree--I provided the same feedback privately. It seems
>>>>> straightforwardly unsound.
>>>>>
>>>>
>>>> In practice it doesn't seem to be much of an issue.
>>>>
>>>> Specifically, if I GET an existing document and get an etag with the J=
SON,
>>>> then make some changes and send a PATCH with If-Match, the fact that a=
ny
>>>> given pointer could point to an array or object member doesn't really =
matter
>>>> much.
>>>>
>>>> For example:
>>>>
>>>>> GET /the/doc HTTP/1.1
>>>>
>>>>  <  HTTP/1.1 200 OK
>>>>     ETag: "my-document-tag"
>>>>     Content-Type: application/json
>>>>
>>>>     {"1":"foo"}
>>>>
>>>>> PATCH /the/doc HTTP/1.1
>>>>     If-Match: "my-document-etag"
>>>>     Content-Type: application/json-patch
>>>>
>>>>     [{"op":"add","path":"/2","value":"bar"}]
>>>>
>>>> Generally speaking, someone should not be using PATCH to perform a par=
tial
>>>> modification if they don't already have some knowledge in advance what=
 they
>>>> are modifying. The only time the apparent ambiguity becomes an issue i=
s when
>>>> a client is blindly sending a patch to an unknown endpoint... in which=
 case,
>>>> you get whatever you end up with.
>>>>
>>>> - James
>>>>
>>>>
>>>>>
>>>>> - Rob
>>>>>
>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Markus Lanthaler
>>>>>>
>>>>>> @markuslanthaler
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> From: James M Snell [mailto:jasnell@gmail.com]
>>>>>> Sent: Friday, December 14, 2012 5:41 PM
>>>>>> To: Markus Lanthaler
>>>>>> Cc: IETF Discussion; IETF Apps Discuss
>>>>>> Subject: Re: [apps-discuss] Last Call:
>>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed =
Standard
>>>>>>
>>>>>>
>>>>>>
>>>>>> JSON Pointer does not distinguish between objects and arrays. That i=
s
>>>>>> not determined until the pointer is applied to an actual object inst=
ance...
>>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
>>>>>> <markus.lanthaler@gmx.net> wrote:
>>>>>>
>>>>>> I've asked that before but didn't get an answer. So let me ask again
>>>>>> (even
>>>>>> though I'm quite sure it has already been asked by somebody else).
>>>>>>
>>>>>> How does JSON Pointer distinguish between objects and arrays? E.g.
>>>>>> consider
>>>>>> the following JSON document:
>>>>>>
>>>>>> {
>>>>>>  "foo": "bar",
>>>>>>  "1": "baz"
>>>>>> }
>>>>>>
>>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "baz" e=
ven
>>>>>> though that's probably not what the author intended. Is there a way =
to
>>>>>> avoid
>>>>>> that?
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>> Markus
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Markus Lanthaler
>>>>>> @markuslanthaler
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>>>>>>> bounces@ietf.org] On Behalf Of The IESG
>>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
>>>>>>> To: IETF-Announce
>>>>>>> Cc: apps-discuss@ietf.org
>>>>>>> Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer=
-
>>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
>>>>>>>
>>>>>>>
>>>>>>> The IESG has received a request from the Applications Area Working
>>>>>>> Group
>>>>>>> WG (appsawg) to consider the following document:
>>>>>>> - 'JSON Pointer'
>>>>>>>  <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>>>>>>>
>>>>>>> The IESG plans to make a decision in the next few weeks, and solici=
ts
>>>>>>> final comments on this action. Please send substantive comments to
>>>>>>> the
>>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments
>>>>>>> may
>>>>>>> be
>>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>>>>> beginning of the Subject line to allow automated sorting.
>>>>>>>
>>>>>>> Abstract
>>>>>>>
>>>>>>>
>>>>>>>   JSON Pointer defines a string syntax for identifying a specific
>>>>>>> value
>>>>>>>   within a JSON document.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> The file can be obtained via
>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>>>>>>>
>>>>>>> IESG discussion can be tracked via
>>>>>>>
>>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/bal=
lot/
>>>>>>>
>>>>>>>
>>>>>>> No IPR declarations have been submitted directly on this I-D.
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> apps-discuss mailing list
>>>>>>> apps-discuss@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> apps-discuss mailing list
>>>>>> apps-discuss@ietf.org
>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> apps-discuss mailing list
>>>> apps-discuss@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>>
>>>
>>>
>>>
>>> --
>>> Matthew P. C. Morley
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>

From David.Biesack@sas.com  Mon Dec 17 06:02:29 2012
Return-Path: <David.Biesack@sas.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D68421F8AD6 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 06:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.478
X-Spam-Level: 
X-Spam-Status: No, score=-3.478 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnFW9OVtLNET for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 06:02:25 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe003.messaging.microsoft.com [213.199.154.141]) by ietfa.amsl.com (Postfix) with ESMTP id CB39421F8AD4 for <ietf@ietf.org>; Mon, 17 Dec 2012 06:02:24 -0800 (PST)
Received: from mail125-db3-R.bigfish.com (10.3.81.240) by DB3EHSOBE010.bigfish.com (10.3.84.30) with Microsoft SMTP Server id 14.1.225.23; Mon, 17 Dec 2012 14:02:23 +0000
Received: from mail125-db3 (localhost [127.0.0.1])	by mail125-db3-R.bigfish.com (Postfix) with ESMTP id 34C1C4A0171	for <ietf@ietf.org>; Mon, 17 Dec 2012 14:02:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:149.173.6.148; KIP:(null); UIP:(null); IPV:NLI; H:mercav06d.na.sas.com; RD:mercav06d.na.sas.com; EFVD:NLI
X-SpamScore: -2
X-BigFish: S-2(zz1432I1447Izz1de0h1202h1e76h1d1ah1d2ahzz8275ch17326ahz2fh2a8h668h839h944hcf6hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1155h)
Received-SPF: pass (mail125-db3: domain of sas.com designates 149.173.6.148 as permitted sender) client-ip=149.173.6.148; envelope-from=David.Biesack@sas.com; helo=mercav06d.na.sas.com ; d.na.sas.com ; 
Received: from mail125-db3 (localhost.localdomain [127.0.0.1]) by mail125-db3 (MessageSwitch) id 1355752941209829_8019; Mon, 17 Dec 2012 14:02:21 +0000 (UTC)
Received: from DB3EHSMHS017.bigfish.com (unknown [10.3.81.233])	by mail125-db3.bigfish.com (Postfix) with ESMTP id 27D15A0056	for <ietf@ietf.org>; Mon, 17 Dec 2012 14:02:21 +0000 (UTC)
Received: from mercav06d.na.sas.com (149.173.6.148) by DB3EHSMHS017.bigfish.com (10.3.87.117) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 17 Dec 2012 14:02:19 +0000
X-TM-IMSS-Message-ID: <a4a1fd3a002010bf@mercav06d.na.sas.com>
Received: from d72933.na.sas.com.na.sas.com ([10.23.16.81]) by mercav06d.na.sas.com ([10.36.10.11]) with ESMTP (TREND IMSS SMTP Service 7.1) id a4a1fd3a002010bf ; Mon, 17 Dec 2012 09:02:13 -0500
From: "David J. Biesack" <David.Biesack@sas.com>
To: Mark Nottingham <mnot@mnot.net>, <ietf@ietf.org>
Subject: Re: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
In-Reply-To: <6B4F2945-EC54-4171-92FF-3A88CEB27D23@mnot.net> (message from Mark Nottingham on Mon, 17 Dec 2012 11:33:41 +1100)
Date: Mon, 17 Dec 2012 09:02:10 -0500
Message-ID: <p1txrkkc9p.fsf@d72933.na.sas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginatorOrg: sas.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, 17 Dec 2012 14:02:29 -0000

Mark Nottingham <mnot@mnot.net> writes:

>> Suggestion: allow negative numbers to indicate a position counted from the end of the array instead "array/-".
>> [some measure of complexity omitted here...]

> David,
>
> This was discussed in the Working Group, but it wasn't felt that the added complexity was worth it; there's a strong feeling that this spec should be as simple as possible.
>
> Cheers,

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

Understood - simplicity is a great Guiding Principle.

Might I suggest, however, using -1 instead of "-" to refer to the last item in an array, as this provides two benefits:

1) Allows for adding the complexity down the road in a compatible way, should there be need
2) Uniformity; i.e. always using integer values for referring to array elements.

Thanks for the consideration,
djb


From sayrer@gmail.com  Mon Dec 17 06:19:17 2012
Return-Path: <sayrer@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 6A09421F8AD9; Mon, 17 Dec 2012 06:19:17 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbVaHuy9jzbL; Mon, 17 Dec 2012 06:19:17 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 61BEB21F8AD8; Mon, 17 Dec 2012 06:19:16 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id r3so2884052wey.31 for <multiple recipients>; Mon, 17 Dec 2012 06:19:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bPRDAATgmUCEaJnH3bM6yXTOygKUIfD7uVvCVSvbUYY=; b=ulE0J5UDZOTZqqyJzvyLoKUBOEEBNw5qQVm1Ghb8mWbIJ+2bz/Hwwd/8Ji/Ibu5C2t y/gmcNuNq3trlb8OY+ezm7M4488MWRaqN16TdhWxF+z2nIGsCin/vEk1Fmqs2CWg/Ll+ 9rW2V+7yQca4BWYezyF6F/4N1ert66VnddtbqdQ4E11U1KqeZpWD6dpcYKvasMVSPZzD G9u4h+8/kPC6DB45OMXPa2ZMpxm+6safI7FdOzAR7ggCvCPQxXOpixCZgAdIXDta/Uz0 nAnT7BPLzWio6lmIiQ4TeLWTt+dBSD5G5YbJh4yNtLXXubq8LCPbpCAA0CPGNZOJGI5a QGUA==
MIME-Version: 1.0
Received: by 10.194.78.162 with SMTP id c2mr17262915wjx.46.1355753955529; Mon, 17 Dec 2012 06:19:15 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Mon, 17 Dec 2012 06:19:15 -0800 (PST)
In-Reply-To: <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com>
Date: Mon, 17 Dec 2012 06:19:15 -0800
Message-ID: <CAChr6SxiWZBZ2O6tdNmDUaufiCu=cg3hxJUrVJw7xiMmby70HA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Matthew Morley <matt@mpcm.com>, IETF Apps Discuss <apps-discuss@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: Mon, 17 Dec 2012 14:19:17 -0000

On Mon, Dec 17, 2012 at 2:01 AM, Robert Sayre <sayrer@gmail.com> wrote:
>
> The first case that can come up is editing documents that have been
> refactored. It's quite common to refactor JSON documents as below when
> a little extra metadata is needed for a collection:
>
> { "foo":[1,2,3] }
>
> then becomes
>
> {
>   "foo":
>   "bar": "baz",
>   "members": [1,2,3]
> }
>

Oh drat, I missed a pair of brackets here.

I meant:

{
  "foo":
  {
    "bar": "baz",
    "members": [1,2,3]
  }
}

- Rob

From jasnell@gmail.com  Mon Dec 17 07:09:07 2012
Return-Path: <jasnell@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 8C26521F8B23; Mon, 17 Dec 2012 07:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.385
X-Spam-Level: 
X-Spam-Status: No, score=-3.385 tagged_above=-999 required=5 tests=[AWL=-0.387, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djGYjwA-xpRU; Mon, 17 Dec 2012 07:09:04 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3964A21F8B04; Mon, 17 Dec 2012 07:09:04 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so9346596ieb.31 for <multiple recipients>; Mon, 17 Dec 2012 07:08:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Vkfa6t16crRL0rBWNJEKgovvg1T+ozp7m9l07NFSjIU=; b=JWE9TCUqEUqt+FOJlMd7mdV7BS5j03Ed4gtfLTfcVGmeI53VZvcIRnYxskQo5CBK4x hd28HGV+ssUwtUn4S3/9ZEIyixUk8kozVPe9o6iM3q3J7a+6SS54xRumk6RdSyR/nU1a mqFzri88+HFxOnIsgCIclk+I0IC51CMjrmMpli6sssAaj5ZlFuDrreQEhx/H7MaS7hRl e8wN5o7b/dsfJqEIovqVEwEPFKzd+Pz3z+UDP/KykogMgvko6PTLRXJ+pW/YDZMntVSS Wy3ivZYlRFxGo/c7TshFXxV/11U9gKXN0rQ+4oGEZnEJU5YJZGoqw9i17mYZ3U3aZT0u VAPA==
Received: by 10.50.45.166 with SMTP id o6mr9492703igm.0.1355756928025; Mon, 17 Dec 2012 07:08:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Mon, 17 Dec 2012 07:08:27 -0800 (PST)
In-Reply-To: <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 17 Dec 2012 07:08:27 -0800
Message-ID: <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Robert Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=14dae934035718c53f04d10dc217
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 15:09:07 -0000

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

On Mon, Dec 17, 2012 at 2:01 AM, Robert Sayre <sayrer@gmail.com> wrote:

> [snip]
> >
> > You might argue that someone who (for example) adds to "/foo/1" in the
> mistaken belief that it's an array, when in fact it's an object, will get
> surprising results. That's true, but if we were to solve this problem, th=
at
> person would still need to understand the underlying semantics of "foo" t=
o
> do anything useful to it -- and I'm not hearing anyone complain about tha=
t
> (I hope).
>
> The first case that can come up is editing documents that have been
> refactored. It's quite common to refactor JSON documents as below when
> a little extra metadata is needed for a collection:
>
> { "foo":[1,2,3] }
>
> then becomes
>
> {
>   "foo":
>   "bar": "baz",
>   "members": [1,2,3]
> }
>
> now, an operation on /foo/1 is quite a different thing in the second
> document. It's not too hard to see how a client that's been out of
> contact with the server for a while could send an addition to /foo
> intended for the array that's been moved down to "members". Now, there
> are ways to catch this if you're willing to bloat the patch document
> with other checks, or by insisting on a matching ETag. But one of the
> nice things about patch formats is that you can try for more
> optimistic concurrent editing. This ambiguity in the patch format
> makes it needlessly more costly to detect unsound edits.
>
>
Appreciate the concrete use case... while it has come up a few times, this
is the first actual case that's been presented. If I understand the issue
correctly, you're basically talking about a client making a blind partial
update to an arbitrarily structured JSON document whose structure may have
changed since the last time the client edited it...  In such cases, I would
argue that you get whatever you end up with.

Everyone's idea of "bloat" is different. Adding etag checking is a simple,
effective best practice for detecting concurrent document changes and is
likely a really good idea in a scenario where we're making partial
modifications to arbitrary documents. Adding in support for json-predicates
adds a bit more (not a lot really but opinions vary.. in the ruby
implementation it's only approximately 140 more lines of code, mostly
formatting) but can make it rather more reliable... For instance,

  [
    {"op": "type", "path": "/foo/1", "value": "array"},
    {"op": "add", "path": "/foo/1", "value": 1}
  ]

Again, the point is, I don't see this as a problem in practice.
Implementers that make blind edits to arbitrary docs can expect surprising
results sometimes. That's just the way it is. There are mechanisms defined
(test, json-predicates and conditional requests) that can make the edit
more reliable.


> Another source of bugs from JavaScript side of things will be
> "array-like" objects. These are really quite common (jQuery lists,
> arguments object, etc), and authors very often don't realize they
> won't be serialized as an array. To be sure, this is a bug on the
> author's side, but some checks in the patch format would really help.
> They'll probably become even more common as ES6 is standardizing
> iterators http://wiki.ecmascript.org/doku.php?id=3Dharmony:iterators.
> Here's an example in a JS REPL using the arguments object (but keep in
> mind there are many other objects out there that behave this way).
>
> > function foo(list) { console.log(JSON.stringify(list)) }
> > function bar(a,b,c) { foo(arguments) }
> > bar("a", "b", "c");
> {"0":"a","1":"b","2":"c"}
>
>
Definitely understand this case, but json-patch is defined in terms of the
basic json model and not javascript. In other words... again.. the
developer using the patch needs to be aware of the structure of the target
resource. Json-predicate provides a good approach to dealing with that by
allowing a developer to test the structure before attempting to edit.

- James

>
> > Put another way -- do you really think
>
> Yes, really.
>
> > that people PATCHing something as if it's an array (when in fact it's a=
n
> object) is a significant, real-world problem, given that the patch author
> already has to understand the semantics of the document they're patching?
>
> I don't see that requirement in the draft, and I certainly wouldn't
> bet on it being true in all cases. Wasn't one of the motivating
> use-cases for this patch format CouchDB? That software operates on
> arbitrary, user-defined JSON documents.
>
> - Rob
>
> > I don't, and the WG didn't either.
> >
> > Regards,
> >
> >
> > On 17/12/2012, at 3:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
> >
> >> The cost of fixing it seems low, either by changing the path syntax of
> >> JSON pointer or changing the names of operations applied to arrays.
> >> Array-like objects are common enough in JavaScript to make this a
> >> worry. The other suggestions either assume a particular policy for
> >> concurrent edits or require more machinery (test operation etc).
> >> Wouldn't it be simpler to make the patch format more precise?
> >>
> >> - Rob
> >>
> >> On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley <matt@mpcm.com> wrote:
> >>> I am usually lurking and struggling to keep up with these posts. But,=
 I
> >>> concur with James, this really is a non-issue in practice.
> >>>
> >>> The JSON Pointer expresses a path down a JSON object to a specific
> context.
> >>> The Patch expresses a change within or to that context.
> >>> Everything about the both standards is about that end context.
> >>>
> >>> If you want to confirm the type of the context before applying a
> patch, this
> >>> should probably be part of a test operation. I'm not sure if this is
> >>> possible at this point (?), but that is where the logic should exist.
> >>>
> >>>
> >>>
> >>> On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com>
> wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com>
> wrote:
> >>>>>
> >>>>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
> >>>>> <markus.lanthaler@gmx.net> wrote:
> >>>>>>
> >>>>>> Hmm.. I think that=E2=80=99s quite problematic. Especially conside=
ring how
> JSON
> >>>>>> Pointer is used in JSON Patch.
> >>>>>
> >>>>> I agree--I provided the same feedback privately. It seems
> >>>>> straightforwardly unsound.
> >>>>>
> >>>>
> >>>> In practice it doesn't seem to be much of an issue.
> >>>>
> >>>> Specifically, if I GET an existing document and get an etag with the
> JSON,
> >>>> then make some changes and send a PATCH with If-Match, the fact that
> any
> >>>> given pointer could point to an array or object member doesn't reall=
y
> matter
> >>>> much.
> >>>>
> >>>> For example:
> >>>>
> >>>>> GET /the/doc HTTP/1.1
> >>>>
> >>>>  <  HTTP/1.1 200 OK
> >>>>     ETag: "my-document-tag"
> >>>>     Content-Type: application/json
> >>>>
> >>>>     {"1":"foo"}
> >>>>
> >>>>> PATCH /the/doc HTTP/1.1
> >>>>     If-Match: "my-document-etag"
> >>>>     Content-Type: application/json-patch
> >>>>
> >>>>     [{"op":"add","path":"/2","value":"bar"}]
> >>>>
> >>>> Generally speaking, someone should not be using PATCH to perform a
> partial
> >>>> modification if they don't already have some knowledge in advance
> what they
> >>>> are modifying. The only time the apparent ambiguity becomes an issue
> is when
> >>>> a client is blindly sending a patch to an unknown endpoint... in
> which case,
> >>>> you get whatever you end up with.
> >>>>
> >>>> - James
> >>>>
> >>>>
> >>>>>
> >>>>> - Rob
> >>>>>
> >>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Markus Lanthaler
> >>>>>>
> >>>>>> @markuslanthaler
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> From: James M Snell [mailto:jasnell@gmail.com]
> >>>>>> Sent: Friday, December 14, 2012 5:41 PM
> >>>>>> To: Markus Lanthaler
> >>>>>> Cc: IETF Discussion; IETF Apps Discuss
> >>>>>> Subject: Re: [apps-discuss] Last Call:
> >>>>>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Propose=
d
> Standard
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> JSON Pointer does not distinguish between objects and arrays. That
> is
> >>>>>> not determined until the pointer is applied to an actual object
> instance...
> >>>>>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler
> >>>>>> <markus.lanthaler@gmx.net> wrote:
> >>>>>>
> >>>>>> I've asked that before but didn't get an answer. So let me ask aga=
in
> >>>>>> (even
> >>>>>> though I'm quite sure it has already been asked by somebody else).
> >>>>>>
> >>>>>> How does JSON Pointer distinguish between objects and arrays? E.g.
> >>>>>> consider
> >>>>>> the following JSON document:
> >>>>>>
> >>>>>> {
> >>>>>>  "foo": "bar",
> >>>>>>  "1": "baz"
> >>>>>> }
> >>>>>>
> >>>>>> As I read the draft, the JSON Pointer "/1" would evaluate to "baz"
> even
> >>>>>> though that's probably not what the author intended. Is there a wa=
y
> to
> >>>>>> avoid
> >>>>>> that?
> >>>>>>
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Markus
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Markus Lanthaler
> >>>>>> @markuslanthaler
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> -----Original Message-----
> >>>>>>> From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
> >>>>>>> bounces@ietf.org] On Behalf Of The IESG
> >>>>>>> Sent: Tuesday, December 11, 2012 4:01 PM
> >>>>>>> To: IETF-Announce
> >>>>>>> Cc: apps-discuss@ietf.org
> >>>>>>> Subject: [apps-discuss] Last Call:
> <draft-ietf-appsawg-json-pointer-
> >>>>>>> 07.txt> (JSON Pointer) to Proposed Standard
> >>>>>>>
> >>>>>>>
> >>>>>>> The IESG has received a request from the Applications Area Workin=
g
> >>>>>>> Group
> >>>>>>> WG (appsawg) to consider the following document:
> >>>>>>> - 'JSON Pointer'
> >>>>>>>  <draft-ietf-appsawg-json-pointer-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 t=
o
> >>>>>>> the
> >>>>>>> ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comment=
s
> >>>>>>> may
> >>>>>>> be
> >>>>>>> sent to iesg@ietf.org instead. In either case, please retain the
> >>>>>>> beginning of the Subject line to allow automated sorting.
> >>>>>>>
> >>>>>>> Abstract
> >>>>>>>
> >>>>>>>
> >>>>>>>   JSON Pointer defines a string syntax for identifying a specific
> >>>>>>> value
> >>>>>>>   within a JSON document.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> The file can be obtained via
> >>>>>>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
> >>>>>>>
> >>>>>>> IESG discussion can be tracked via
> >>>>>>>
> >>>>>>>
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
> >>>>>>>
> >>>>>>>
> >>>>>>> No IPR declarations have been submitted directly on this I-D.
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> apps-discuss mailing list
> >>>>>>> apps-discuss@ietf.org
> >>>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> apps-discuss mailing list
> >>>>>> apps-discuss@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> apps-discuss mailing list
> >>>>>> apps-discuss@ietf.org
> >>>>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> apps-discuss mailing list
> >>>> apps-discuss@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/apps-discuss
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Matthew P. C. Morley
> >> _______________________________________________
> >> apps-discuss mailing list
> >> apps-discuss@ietf.org
> >> https://www.ietf.org/mailman/listinfo/apps-discuss
> >
> > --
> > Mark Nottingham   http://www.mnot.net/
> >
> >
> >
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

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

<font face=3D"courier new,monospace"><br></font><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote">On Mon, Dec 17, 2012 at 2:01 AM, Robert =
Sayre <span dir=3D"ltr">&lt;<a href=3D"mailto:sayrer@gmail.com" target=3D"_=
blank">sayrer@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">[snip]</div><div class=3D"=
im">
&gt;<br>
&gt; You might argue that someone who (for example) adds to &quot;/foo/1&qu=
ot; in the mistaken belief that it&#39;s an array, when in fact it&#39;s an=
 object, will get surprising results. That&#39;s true, but if we were to so=
lve this problem, that person would still need to understand the underlying=
 semantics of &quot;foo&quot; to do anything useful to it -- and I&#39;m no=
t hearing anyone complain about that (I hope).<br>


<br>
</div>The first case that can come up is editing documents that have been<b=
r>
refactored. It&#39;s quite common to refactor JSON documents as below when<=
br>
a little extra metadata is needed for a collection:<br>
<br>
{ &quot;foo&quot;:[1,2,3] }<br>
<br>
then becomes<br>
<br>
{<br>
=C2=A0 &quot;foo&quot;:<br>
=C2=A0 &quot;bar&quot;: &quot;baz&quot;,<br>
=C2=A0 &quot;members&quot;: [1,2,3]<br>
}<br>
<br>
now, an operation on /foo/1 is quite a different thing in the second<br>
document. It&#39;s not too hard to see how a client that&#39;s been out of<=
br>
contact with the server for a while could send an addition to /foo<br>
intended for the array that&#39;s been moved down to &quot;members&quot;. N=
ow, there<br>
are ways to catch this if you&#39;re willing to bloat the patch document<br=
>
with other checks, or by insisting on a matching ETag. But one of the<br>
nice things about patch formats is that you can try for more<br>
optimistic concurrent editing. This ambiguity in the patch format<br>
makes it needlessly more costly to detect unsound edits.<br>
<br></blockquote><div><br></div><div>Appreciate the concrete use case... wh=
ile it has come up a few times, this is the first actual case that&#39;s be=
en presented. If I understand the issue correctly, you&#39;re basically tal=
king about a client making a blind partial update to an arbitrarily structu=
red JSON document whose structure may have changed since the last time the =
client edited it... =C2=A0In such cases, I would argue that you get whateve=
r you end up with.=C2=A0</div>

<div><br></div><div>Everyone&#39;s idea of &quot;bloat&quot; is different. =
Adding etag checking is a simple, effective best practice for detecting con=
current document changes and is likely a really good idea in a scenario whe=
re we&#39;re making partial modifications to arbitrary documents. Adding in=
 support for json-predicates adds a bit more (not a lot really but opinions=
 vary.. in the ruby implementation it&#39;s only approximately 140 more lin=
es of code, mostly formatting) but can make it rather more reliable... For =
instance,</div>

<div><br></div><div>=C2=A0 [</div><div>=C2=A0 =C2=A0 {&quot;op&quot;: &quot=
;type&quot;, &quot;path&quot;: &quot;/foo/1&quot;, &quot;value&quot;: &quot=
;array&quot;},</div><div>=C2=A0 =C2=A0 {&quot;op&quot;: &quot;add&quot;, &q=
uot;path&quot;: &quot;/foo/1&quot;, &quot;value&quot;: 1}</div>

<div>=C2=A0 ]</div><div><br></div><div>Again, the point is, I don&#39;t see=
 this as a problem in practice. Implementers that make blind edits to arbit=
rary docs can expect surprising results sometimes. That&#39;s just the way =
it is. There are mechanisms defined (test, json-predicates and conditional =
requests) that can make the edit more reliable.</div>

<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
Another source of bugs from JavaScript side of things will be<br>
&quot;array-like&quot; objects. These are really quite common (jQuery lists=
,<br>
arguments object, etc), and authors very often don&#39;t realize they<br>
won&#39;t be serialized as an array. To be sure, this is a bug on the<br>
author&#39;s side, but some checks in the patch format would really help.<b=
r>
They&#39;ll probably become even more common as ES6 is standardizing<br>
iterators <a href=3D"http://wiki.ecmascript.org/doku.php?id=3Dharmony:itera=
tors" target=3D"_blank">http://wiki.ecmascript.org/doku.php?id=3Dharmony:it=
erators</a>.<br>
Here&#39;s an example in a JS REPL using the arguments object (but keep in<=
br>
mind there are many other objects out there that behave this way).<br>
<br>
&gt; function foo(list) { console.log(JSON.stringify(list)) }<br>
&gt; function bar(a,b,c) { foo(arguments) }<br>
&gt; bar(&quot;a&quot;, &quot;b&quot;, &quot;c&quot;);<br>
{&quot;0&quot;:&quot;a&quot;,&quot;1&quot;:&quot;b&quot;,&quot;2&quot;:&quo=
t;c&quot;}<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>Definitely und=
erstand this case, but json-patch is defined in terms of the basic json mod=
el and not javascript. In other words... again.. the developer using the pa=
tch needs to be aware of the structure of the target resource. Json-predica=
te provides a good approach to dealing with that by allowing a developer to=
 test the structure before attempting to edit.=C2=A0</div>

<div>=C2=A0</div><div>- James</div><div><br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><div class=3D"im">
&gt;<br>
&gt; Put another way -- do you really think<br>
<br>
</div>Yes, really.<br>
<div class=3D"im"><br>
&gt; that people PATCHing something as if it&#39;s an array (when in fact i=
t&#39;s an object) is a significant, real-world problem, given that the pat=
ch author already has to understand the semantics of the document they&#39;=
re patching?<br>


<br>
</div>I don&#39;t see that requirement in the draft, and I certainly wouldn=
&#39;t<br>
bet on it being true in all cases. Wasn&#39;t one of the motivating<br>
use-cases for this patch format CouchDB? That software operates on<br>
arbitrary, user-defined JSON documents.<br>
<br>
- Rob<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; I don&#39;t, and the WG didn&#39;t either.<br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt;<br>
&gt; On 17/12/2012, at 3:36 PM, Robert Sayre &lt;<a href=3D"mailto:sayrer@g=
mail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; The cost of fixing it seems low, either by changing the path synta=
x of<br>
&gt;&gt; JSON pointer or changing the names of operations applied to arrays=
.<br>
&gt;&gt; Array-like objects are common enough in JavaScript to make this a<=
br>
&gt;&gt; worry. The other suggestions either assume a particular policy for=
<br>
&gt;&gt; concurrent edits or require more machinery (test operation etc).<b=
r>
&gt;&gt; Wouldn&#39;t it be simpler to make the patch format more precise?<=
br>
&gt;&gt;<br>
&gt;&gt; - Rob<br>
&gt;&gt;<br>
&gt;&gt; On Sun, Dec 16, 2012 at 4:33 PM, Matthew Morley &lt;<a href=3D"mai=
lto:matt@mpcm.com">matt@mpcm.com</a>&gt; wrote:<br>
&gt;&gt;&gt; I am usually lurking and struggling to keep up with these post=
s. But, I<br>
&gt;&gt;&gt; concur with James, this really is a non-issue in practice.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The JSON Pointer expresses a path down a JSON object to a spec=
ific context.<br>
&gt;&gt;&gt; The Patch expresses a change within or to that context.<br>
&gt;&gt;&gt; Everything about the both standards is about that end context.=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; If you want to confirm the type of the context before applying=
 a patch, this<br>
&gt;&gt;&gt; should probably be part of a test operation. I&#39;m not sure =
if this is<br>
&gt;&gt;&gt; possible at this point (?), but that is where the logic should=
 exist.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On Sun, Dec 16, 2012 at 12:22 AM, James M Snell &lt;<a href=3D=
"mailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre &lt;<a href=
=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:markus.lanthaler@gmx.net">markus=
.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Hmm.. I think that=E2=80=99s quite problematic. Es=
pecially considering how JSON<br>
&gt;&gt;&gt;&gt;&gt;&gt; Pointer is used in JSON Patch.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I agree--I provided the same feedback privately. It se=
ems<br>
&gt;&gt;&gt;&gt;&gt; straightforwardly unsound.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; In practice it doesn&#39;t seem to be much of an issue.<br=
>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Specifically, if I GET an existing document and get an eta=
g with the JSON,<br>
&gt;&gt;&gt;&gt; then make some changes and send a PATCH with If-Match, the=
 fact that any<br>
&gt;&gt;&gt;&gt; given pointer could point to an array or object member doe=
sn&#39;t really matter<br>
&gt;&gt;&gt;&gt; much.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; For example:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; GET /the/doc HTTP/1.1<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =C2=A0&lt; =C2=A0HTTP/1.1 200 OK<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 ETag: &quot;my-document-tag&quot;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Content-Type: application/json<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 {&quot;1&quot;:&quot;foo&quot;}<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; PATCH /the/doc HTTP/1.1<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 If-Match: &quot;my-document-etag&quot;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 Content-Type: application/json-patch<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =C2=A0 =C2=A0 [{&quot;op&quot;:&quot;add&quot;,&quot;path&=
quot;:&quot;/2&quot;,&quot;value&quot;:&quot;bar&quot;}]<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Generally speaking, someone should not be using PATCH to p=
erform a partial<br>
&gt;&gt;&gt;&gt; modification if they don&#39;t already have some knowledge=
 in advance what they<br>
&gt;&gt;&gt;&gt; are modifying. The only time the apparent ambiguity become=
s an issue is when<br>
&gt;&gt;&gt;&gt; a client is blindly sending a patch to an unknown endpoint=
... in which case,<br>
&gt;&gt;&gt;&gt; you get whatever you end up with.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; - James<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; - Rob<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; @markuslanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; From: James M Snell [mailto:<a href=3D"mailto:jasn=
ell@gmail.com">jasnell@gmail.com</a>]<br>
&gt;&gt;&gt;&gt;&gt;&gt; Sent: Friday, December 14, 2012 5:41 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt; To: Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt; Cc: IETF Discussion; IETF Apps Discuss<br>
&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [apps-discuss] Last Call:<br>
&gt;&gt;&gt;&gt;&gt;&gt; &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; (JS=
ON Pointer) to Proposed Standard<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; JSON Pointer does not distinguish between objects =
and arrays. That is<br>
&gt;&gt;&gt;&gt;&gt;&gt; not determined until the pointer is applied to an =
actual object instance...<br>
&gt;&gt;&gt;&gt;&gt;&gt; the pointer &quot;/1&quot; is valid against {&quot=
;1&quot;:&quot;a&quot;} or [&quot;a&quot;,&quot;b&quot;]<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler<=
br>
&gt;&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:markus.lanthaler@gmx.net">ma=
rkus.lanthaler@gmx.net</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; I&#39;ve asked that before but didn&#39;t get an a=
nswer. So let me ask again<br>
&gt;&gt;&gt;&gt;&gt;&gt; (even<br>
&gt;&gt;&gt;&gt;&gt;&gt; though I&#39;m quite sure it has already been aske=
d by somebody else).<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; How does JSON Pointer distinguish between objects =
and arrays? E.g.<br>
&gt;&gt;&gt;&gt;&gt;&gt; consider<br>
&gt;&gt;&gt;&gt;&gt;&gt; the following JSON document:<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; {<br>
&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0&quot;foo&quot;: &quot;bar&quot;,<br>
&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0&quot;1&quot;: &quot;baz&quot;<br>
&gt;&gt;&gt;&gt;&gt;&gt; }<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; As I read the draft, the JSON Pointer &quot;/1&quo=
t; would evaluate to &quot;baz&quot; even<br>
&gt;&gt;&gt;&gt;&gt;&gt; though that&#39;s probably not what the author int=
ended. Is there a way to<br>
&gt;&gt;&gt;&gt;&gt;&gt; avoid<br>
&gt;&gt;&gt;&gt;&gt;&gt; that?<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&gt;&gt;&gt; Markus<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; --<br>
&gt;&gt;&gt;&gt;&gt;&gt; Markus Lanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt; @markuslanthaler<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original Message-----<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: <a href=3D"mailto:apps-discuss-bounces@i=
etf.org">apps-discuss-bounces@ietf.org</a> [mailto:<a href=3D"mailto:apps-d=
iscuss-">apps-discuss-</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:bounces@ietf.org">bounces@ie=
tf.org</a>] On Behalf Of The IESG<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: IETF-Announce<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Cc: <a href=3D"mailto:apps-discuss@ietf.org">a=
pps-discuss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: [apps-discuss] Last Call: &lt;draft-i=
etf-appsawg-json-pointer-<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; 07.txt&gt; (JSON Pointer) to Proposed Standard=
<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IESG has received a request from the Appli=
cations Area Working<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Group<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; WG (appsawg) to consider the following documen=
t:<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; - &#39;JSON Pointer&#39;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0&lt;draft-ietf-appsawg-json-pointer-07.t=
xt&gt; as Proposed Standard<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The IESG plans to make a decision in the next =
few weeks, and solicits<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; final comments on this action. Please send sub=
stantive comments to<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org=
</a> mailing lists by 2012-12-25. Exceptionally, comments<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; may<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@=
ietf.org</a> instead. In either case, please retain the<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; beginning of the Subject line to allow automat=
ed sorting.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; Abstract<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 JSON Pointer defines a string syntax fo=
r identifying a specific<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; value<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; =C2=A0 within a JSON document.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; The file can be obtained via<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/dra=
ft-ietf-appsawg-json-pointer/" target=3D"_blank">http://datatracker.ietf.or=
g/doc/draft-ietf-appsawg-json-pointer/</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/dra=
ft-ietf-appsawg-json-pointer/ballot/" target=3D"_blank">http://datatracker.=
ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; No IPR declarations have been submitted direct=
ly on this I-D.<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; ______________________________________________=
_<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-=
discuss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listin=
fo/apps-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ap=
ps-discuss</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; _______________________________________________<br=
>
&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-disc=
uss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/a=
pps-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-d=
iscuss</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; _______________________________________________<br=
>
&gt;&gt;&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-disc=
uss@ietf.org</a><br>
&gt;&gt;&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/a=
pps-discuss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-d=
iscuss</a><br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt;&gt; apps-discuss mailing list<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf=
.org</a><br>
&gt;&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-disc=
uss" target=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</=
a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; --<br>
&gt;&gt;&gt; Matthew P. C. Morley<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; apps-discuss mailing list<br>
&gt;&gt; <a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a>=
<br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt; --<br>
&gt; Mark Nottingham =C2=A0 <a href=3D"http://www.mnot.net/" target=3D"_bla=
nk">http://www.mnot.net/</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div></div></blockquote></div><br></div>

--14dae934035718c53f04d10dc217--

From dromasca@avaya.com  Mon Dec 17 08:02:51 2012
Return-Path: <dromasca@avaya.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38BED21F8B37; Mon, 17 Dec 2012 08:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.381
X-Spam-Level: 
X-Spam-Status: No, score=-103.381 tagged_above=-999 required=5 tests=[AWL=0.218, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MCqFlmTBnwf; Mon, 17 Dec 2012 08:02:50 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id D706621F8B39; Mon, 17 Dec 2012 08:02:49 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEKAKUvoFDGmAcF/2dsb2JhbABEgmzAaYEBB4IeAQEBAQMBAQEPKDQLDAQCAQgNBAQBAQsUBQQHJwsUCQgCBA4FCBqHaAEKniacAIwVhWlhA5cYhHGKNoJvghk
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="336707118"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 17 Dec 2012 10:56:03 -0500
Received: from unknown (HELO AZ-FFEXHC01.global.avaya.com) ([135.64.58.11]) by co300216-co-erhwest-out.avaya.com with ESMTP; 17 Dec 2012 10:59:37 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0318.004; Mon, 17 Dec 2012 11:02:40 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-11.txt>	(The Common	Log Format (CLF) for the Session Initiation	Protocol (SIP):	Framework and Data Model) to Proposed Standard
Thread-Topic: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-11.txt>	(The Common	Log Format (CLF) for the Session Initiation	Protocol (SIP):	Framework and Data Model) to Proposed Standard
Thread-Index: AQHN0Zcqqd06/SGCyUe0bHqFyrUH+ZgdOdKw
Date: Mon, 17 Dec 2012 16:02:40 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA042028@AZ-FFEXMB04.global.avaya.com>
References: <20121203204501.12217.39525.idtracker@ietfa.amsl.com>
In-Reply-To: <20121203204501.12217.39525.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "sip-clf@ietf.org" <sip-clf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 16:02:51 -0000

Hi,

I believe that this is a good document and I support its approval.=20

I do have a number of issues which I suggest to take into consideration bef=
ore approval and publication:=20

1. In Section 4:=20

 The SIP CLF is amenable to easy parsing and lends itself well to
   creating other innovative tools.

I am not sure what this sentence really says. What does 'easy parsing' mean=
? The previous paragraph referred to 'quick parsing (i.e., well-delimited f=
ields)' - quick parsing is a relative notion but at least there was an exam=
ple. Here, I do not know.

What does 'other innovative tools' means escapes me totally. Why 'other'? '=
other' than what? And what 'innovative tools' means?=20


2. In Section 11

   SIP CLF log files will take up substantive amount of disk space
   depending on traffic volume at a processing entity and the amount of
   information being logged.  As such, any organization using SIP CLF
   should establish operational procedures for file rollovers as
   appropriate to the needs of the organization.

Procedures for file rollovers is not enough - actually there need to be in =
place procedures for periodic retrieval of logs before rollover.=20

3. [RFC3261] needs to be a Normative Reference. All this document speaks ab=
out logs for SIP, refers to SIP entities, messages, fields in the SIP messa=
ges - on short it cannot be understood and the SIP-CLF cannot be implemente=
d without a good reading and understanding of [RFC3261].=20

Regards,

Dan
=20


> -----Original Message-----
> From: sip-clf-bounces@ietf.org [mailto:sip-clf-bounces@ietf.org] On
> Behalf Of The IESG
> Sent: Monday, December 03, 2012 10:45 PM
> To: IETF-Announce
> Cc: sip-clf@ietf.org
> Subject: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-
> 11.txt> (The Common Log Format (CLF) for the Session Initiation Protocol
> (SIP): Framework and Data Model) to Proposed Standard
>=20
>=20
> The IESG has received a request from the SIP Common Log Format WG
> (sipclf) to consider the following document:
> - 'The Common Log Format (CLF) for the Session Initiation Protocol
> (SIP):
>    Framework and Data Model'
>   <draft-ietf-sipclf-problem-statement-11.txt> as Proposed Standard
>=20
> A previous version of this document was Last Called with an
> Informational intended publication status. Issues with the document's
> scope and technical concerns with internationalization were identified
> during IESG evaluation and the document was returned to the working
> group.
>=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 2012-12-17. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    Well-known web servers such as Apache and web proxies like Squid
>    support event logging using a common log format.  The logs produced
>    using these de-facto standard formats are invaluable to system
>    administrators for trouble-shooting a server and tool writers to
>    craft tools that mine the log files and produce reports and trends.
>    Furthermore, these log files can also be used to train anomaly
>    detection systems and feed events into a security event management
>    system.  The Session Initiation Protocol (SIP) does not have a common
>    log format, and as a result, each server supports a distinct log
>    format that makes it unnecessarily complex to produce tools to do
>    trend analysis and security detection.  We propose a common log file
>    format for SIP servers that can be used uniformly by user agents,
>    proxies, registrars, redirect servers as well as back-to-back user
>    agents.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-sipclf-problem-statement/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-sipclf-problem-
> statement/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> sip-clf mailing list
> sip-clf@ietf.org
> https://www.ietf.org/mailman/listinfo/sip-clf

From mmorley@mpcm.com  Sun Dec 16 16:33:39 2012
Return-Path: <mmorley@mpcm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D33A921F8526 for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 16:33:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izDT-OIxGOSH for <ietf@ietfa.amsl.com>; Sun, 16 Dec 2012 16:33:38 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8583321F8507 for <ietf@ietf.org>; Sun, 16 Dec 2012 16:33:38 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so6398550vbb.31 for <ietf@ietf.org>; Sun, 16 Dec 2012 16:33:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=YWNL5PMJIo9RTkUe18XEXF22Cu5izble7vJ/5tBhSoU=; b=ak5/zjcRi93HNs69tW3UEE9vTvsbnzvjqT5jh1kYI03wR0PWrKwZXrmbv4of5Salgz X6ewS2Aoni4hBv4lM2NRwU/MAb4GZtDb2jRzqKGYd6gTEAwqeLF33uG5RAsKVE/QYnP3 2qFDhMk88Ob3VpOfTHFjOMjezToLUsHnrg1f44BG9LpyJqzWrjnWsy3Ykx2Gwzk0HlfR PtHujs9PtxIbGGuPEMLlzHwKZ679MKq8h19LH5GmnUvAdFro+PD1VAs3gYlbVSODuvra axVzpVBQV5QrIanjET0xZXViFRgdQZBQkcDER0/CSDBgszQxsPqiZojv506YdqnBFa7k IW5w==
MIME-Version: 1.0
Received: by 10.220.219.204 with SMTP id hv12mr20181599vcb.71.1355704417586; Sun, 16 Dec 2012 16:33:37 -0800 (PST)
Sender: mmorley@mpcm.com
Received: by 10.220.227.197 with HTTP; Sun, 16 Dec 2012 16:33:37 -0800 (PST)
In-Reply-To: <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com>
Date: Sun, 16 Dec 2012 19:33:37 -0500
X-Google-Sender-Auth: t1EVySSBC5Z8_bAkNvpNHwqwiK4
Message-ID: <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Matthew Morley <matt@mpcm.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: multipart/alternative; boundary=14dae9cfcea43b0e9d04d101883e
X-Gm-Message-State: ALoCoQnEVlSgrgS1lDjHwNc7DsKR/Fq8MylEj9dThURQ6xrnWHCNjxLOSgjGu4tQ0UODjSc43Pxr
X-Mailman-Approved-At: Mon, 17 Dec 2012 08:33:54 -0800
Cc: IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 00:33:40 -0000

--14dae9cfcea43b0e9d04d101883e
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I am usually lurking and struggling to keep up with these posts. But, I
concur with James, this really is a non-issue in practice.

The JSON Pointer expresses a path down a JSON object to a specific context.
The Patch expresses a change within or to that context.
Everything about the both standards is about that end context.

If you want to confirm the type of the context before applying a patch,
this should probably be part of a test operation. I'm not sure if this is
possible at this point (?), but that is where the logic should exist.


On Sun, Dec 16, 2012 at 12:22 AM, James M Snell <jasnell@gmail.com> wrote:

>
>
>
> On Sat, Dec 15, 2012 at 8:36 PM, Robert Sayre <sayrer@gmail.com> wrote:
>
>> On Fri, Dec 14, 2012 at 9:17 AM, Markus Lanthaler
>> <markus.lanthaler@gmx.net> wrote:
>> >
>> > Hmm.. I think that=92s quite problematic. Especially considering how J=
SON
>> Pointer is used in JSON Patch.
>>
>> I agree--I provided the same feedback privately. It seems
>> straightforwardly unsound.
>>
>>
> In practice it doesn't seem to be much of an issue.
>
> Specifically, if I GET an existing document and get an etag with the JSON=
,
> then make some changes and send a PATCH with If-Match, the fact that any
> given pointer could point to an array or object member doesn't really
> matter much.
>
> For example:
>
>   >  GET /the/doc HTTP/1.1
>
>   <  HTTP/1.1 200 OK
>      ETag: "my-document-tag"
>      Content-Type: application/json
>
>      {"1":"foo"}
>
>   >  PATCH /the/doc HTTP/1.1
>      If-Match: "my-document-etag"
>      Content-Type: application/json-patch
>
>      [{"op":"add","path":"/2","value":"bar"}]
>
> Generally speaking, someone should not be using PATCH to perform a partia=
l
> modification if they don't already have some knowledge in advance what th=
ey
> are modifying. The only time the apparent ambiguity becomes an issue is
> when a client is blindly sending a patch to an unknown endpoint... in whi=
ch
> case, you get whatever you end up with.
>
> - James
>
>
>
>> - Rob
>>
>>
>> >
>> > --
>> >
>> > Markus Lanthaler
>> >
>> > @markuslanthaler
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > From: James M Snell [mailto:jasnell@gmail.com]
>> > Sent: Friday, December 14, 2012 5:41 PM
>> > To: Markus Lanthaler
>> > Cc: IETF Discussion; IETF Apps Discuss
>> > Subject: Re: [apps-discuss] Last Call:
>> <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Stan=
dard
>> >
>> >
>> >
>> > JSON Pointer does not distinguish between objects and arrays. That is
>> not determined until the pointer is applied to an actual object instance=
...
>> the pointer "/1" is valid against {"1":"a"} or ["a","b"]
>> >
>> >
>> >
>> > On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler <
>> markus.lanthaler@gmx.net> wrote:
>> >
>> > I've asked that before but didn't get an answer. So let me ask again
>> (even
>> > though I'm quite sure it has already been asked by somebody else).
>> >
>> > How does JSON Pointer distinguish between objects and arrays? E.g.
>> consider
>> > the following JSON document:
>> >
>> > {
>> >   "foo": "bar",
>> >   "1": "baz"
>> > }
>> >
>> > As I read the draft, the JSON Pointer "/1" would evaluate to "baz" eve=
n
>> > though that's probably not what the author intended. Is there a way to
>> avoid
>> > that?
>> >
>> >
>> > Thanks,
>> > Markus
>> >
>> >
>> >
>> > --
>> > Markus Lanthaler
>> > @markuslanthaler
>> >
>> >
>> >
>> >
>> >
>> > > -----Original Message-----
>> > > From: apps-discuss-bounces@ietf.org [mailto:apps-discuss-
>> > > bounces@ietf.org] On Behalf Of The IESG
>> > > Sent: Tuesday, December 11, 2012 4:01 PM
>> > > To: IETF-Announce
>> > > Cc: apps-discuss@ietf.org
>> > > Subject: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-
>> > > 07.txt> (JSON Pointer) to Proposed Standard
>> > >
>> > >
>> > > The IESG has received a request from the Applications Area Working
>> > > Group
>> > > WG (appsawg) to consider the following document:
>> > > - 'JSON Pointer'
>> > >   <draft-ietf-appsawg-json-pointer-07.txt> as Proposed Standard
>> > >
>> > > The IESG plans to make a decision in the next few weeks, and solicit=
s
>> > > final comments on this action. Please send substantive comments to t=
he
>> > > ietf@ietf.org mailing lists by 2012-12-25. Exceptionally, comments
>> may
>> > > be
>> > > sent to iesg@ietf.org instead. In either case, please retain the
>> > > beginning of the Subject line to allow automated sorting.
>> > >
>> > > Abstract
>> > >
>> > >
>> > >    JSON Pointer defines a string syntax for identifying a specific
>> > > value
>> > >    within a JSON document.
>> > >
>> > >
>> > >
>> > >
>> > > The file can be obtained via
>> > > http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/
>> > >
>> > > IESG discussion can be tracked via
>> > >
>> http://datatracker.ietf.org/doc/draft-ietf-appsawg-json-pointer/ballot/
>> > >
>> > >
>> > > No IPR declarations have been submitted directly on this I-D.
>> > >
>> > >
>> > > _______________________________________________
>> > > apps-discuss mailing list
>> > > apps-discuss@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/apps-discuss
>> >
>> > _______________________________________________
>> > apps-discuss mailing list
>> > apps-discuss@ietf.org
>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > apps-discuss mailing list
>> > apps-discuss@ietf.org
>> > https://www.ietf.org/mailman/listinfo/apps-discuss
>> >
>>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>


--=20
Matthew P. C. Morley

--14dae9cfcea43b0e9d04d101883e
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I am usually lurking and struggling to keep up with these posts. But, I con=
cur with James, this really is a non-issue in practice.<br><br>The JSON Poi=
nter expresses=A0a path down a JSON object to a specific context.<br>The Pa=
tch expresses a change within or to that context.<br>
Everything about the both standards is about that end context.<br><br>If yo=
u want to confirm the type of the context before applying a patch, this sho=
uld probably be part of a test operation.=A0I&#39;m not sure if this is pos=
sible at this point (?), but that is where the logic should exist.<br>
<br><br><div class=3D"gmail_quote">On Sun, Dec 16, 2012 at 12:22 AM, James =
M Snell <span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com" target=
=3D"_blank">jasnell@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">
<font face=3D"courier new,monospace"><br></font><div class=3D"gmail_extra">=
<br><br><div class=3D"gmail_quote"><div class=3D"im">On Sat, Dec 15, 2012 a=
t 8:36 PM, Robert Sayre <span dir=3D"ltr">&lt;<a href=3D"mailto:sayrer@gmai=
l.com" target=3D"_blank">sayrer@gmail.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>On Fri, Dec 14, 2012 at 9:17 AM, Markus=
 Lanthaler<br>
&lt;<a href=3D"mailto:markus.lanthaler@gmx.net" target=3D"_blank">markus.la=
nthaler@gmx.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Hmm.. I think that=92s quite problematic. Especially considering how J=
SON Pointer is used in JSON Patch.<br>
<br>
</div>I agree--I provided the same feedback privately. It seems<br>
straightforwardly unsound.<br>
<br></blockquote><div><br></div></div><div><font face=3D"courier new, monos=
pace">In practice it doesn&#39;t seem to be much of an issue.</font></div><=
div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">Specifically, if I GET an existing document and=
 get an etag with the JSON, then make some changes and send a PATCH with If=
-Match, the fact that any given pointer could point to an array or object m=
ember doesn&#39;t really matter much.</font></div>


<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">For example:</font></div><div><font face=3D"cou=
rier new, monospace"><br></font></div><div><font face=3D"courier new, monos=
pace">=A0 &gt; =A0GET /the/doc HTTP/1.1</font></div>


<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=A0 &lt; =A0HTTP/1.1 200 OK</font></div><div><f=
ont face=3D"courier new, monospace">=A0 =A0 =A0ETag: &quot;my-document-tag&=
quot;</font></div>


<div><font face=3D"courier new, monospace">=A0 =A0 =A0Content-Type: applica=
tion/json</font></div><div><font face=3D"courier new, monospace"><br></font=
></div><div><font face=3D"courier new, monospace">=A0 =A0 =A0{&quot;1&quot;=
:&quot;foo&quot;}</font></div>


<div><br></div><div><font face=3D"courier new, monospace">=A0 &gt; =A0PATCH=
 /the/doc HTTP/1.1</font></div><div><font face=3D"courier new, monospace">=
=A0 =A0 =A0If-Match: &quot;my-document-etag&quot;</font></div><div><font fa=
ce=3D"courier new, monospace">=A0 =A0 =A0Content-Type: application/json-pat=
ch</font></div>


<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">=A0 =A0 =A0[{&quot;op&quot;:&quot;add&quot;,&qu=
ot;path&quot;:&quot;/2&quot;,&quot;value&quot;:&quot;bar&quot;}]</font></di=
v><div>


<br></div><div><font face=3D"courier new, monospace">Generally speaking, so=
meone should not be using PATCH to perform a partial modification if they d=
on&#39;t already have some knowledge in advance what they are modifying. Th=
e only time the apparent ambiguity becomes an issue is when a client is bli=
ndly sending a patch to an unknown endpoint... in which case, you get whate=
ver you end up with.=A0</font></div>
<span class=3D"HOEnZb"><font color=3D"#888888">

<div><font face=3D"courier new, monospace"><br></font></div><div><font face=
=3D"courier new, monospace">- James</font></div></font></span><div><div cla=
ss=3D"h5"><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">



- Rob<br>
<div><br>
<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt; Markus Lanthaler<br>
&gt;<br>
&gt; @markuslanthaler<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; From: James M Snell [mailto:<a href=3D"mailto:jasnell@gmail.com" targe=
t=3D"_blank">jasnell@gmail.com</a>]<br>
&gt; Sent: Friday, December 14, 2012 5:41 PM<br>
&gt; To: Markus Lanthaler<br>
&gt; Cc: IETF Discussion; IETF Apps Discuss<br>
</div>&gt; Subject: Re: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-js=
on-pointer-07.txt&gt; (JSON Pointer) to Proposed Standard<br>
<div><div>&gt;<br>
&gt;<br>
&gt;<br>
&gt; JSON Pointer does not distinguish between objects and arrays. That is =
not determined until the pointer is applied to an actual object instance...=
 the pointer &quot;/1&quot; is valid against {&quot;1&quot;:&quot;a&quot;} =
or [&quot;a&quot;,&quot;b&quot;]<br>



&gt;<br>
&gt;<br>
&gt;<br>
&gt; On Fri, Dec 14, 2012 at 2:51 AM, Markus Lanthaler &lt;<a href=3D"mailt=
o:markus.lanthaler@gmx.net" target=3D"_blank">markus.lanthaler@gmx.net</a>&=
gt; wrote:<br>
&gt;<br>
&gt; I&#39;ve asked that before but didn&#39;t get an answer. So let me ask=
 again (even<br>
&gt; though I&#39;m quite sure it has already been asked by somebody else).=
<br>
&gt;<br>
&gt; How does JSON Pointer distinguish between objects and arrays? E.g. con=
sider<br>
&gt; the following JSON document:<br>
&gt;<br>
&gt; {<br>
&gt; =A0 &quot;foo&quot;: &quot;bar&quot;,<br>
&gt; =A0 &quot;1&quot;: &quot;baz&quot;<br>
&gt; }<br>
&gt;<br>
&gt; As I read the draft, the JSON Pointer &quot;/1&quot; would evaluate to=
 &quot;baz&quot; even<br>
&gt; though that&#39;s probably not what the author intended. Is there a wa=
y to avoid<br>
&gt; that?<br>
&gt;<br>
&gt;<br>
&gt; Thanks,<br>
&gt; Markus<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Markus Lanthaler<br>
&gt; @markuslanthaler<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: <a href=3D"mailto:apps-discuss-bounces@ietf.org" target=3D"=
_blank">apps-discuss-bounces@ietf.org</a> [mailto:<a href=3D"mailto:apps-di=
scuss-" target=3D"_blank">apps-discuss-</a><br>
&gt; &gt; <a href=3D"mailto:bounces@ietf.org" target=3D"_blank">bounces@iet=
f.org</a>] On Behalf Of The IESG<br>
&gt; &gt; Sent: Tuesday, December 11, 2012 4:01 PM<br>
&gt; &gt; To: IETF-Announce<br>
&gt; &gt; Cc: <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">ap=
ps-discuss@ietf.org</a><br>
&gt; &gt; Subject: [apps-discuss] Last Call: &lt;draft-ietf-appsawg-json-po=
inter-<br>
&gt; &gt; 07.txt&gt; (JSON Pointer) to Proposed Standard<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The IESG has received a request from the Applications Area Workin=
g<br>
&gt; &gt; Group<br>
&gt; &gt; WG (appsawg) to consider the following document:<br>
&gt; &gt; - &#39;JSON Pointer&#39;<br>
&gt; &gt; =A0 &lt;draft-ietf-appsawg-json-pointer-07.txt&gt; as Proposed St=
andard<br>
&gt; &gt;<br>
&gt; &gt; The IESG plans to make a decision in the next few weeks, and soli=
cits<br>
&gt; &gt; final comments on this action. Please send substantive comments t=
o the<br>
&gt; &gt; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org<=
/a> mailing lists by 2012-12-25. Exceptionally, comments may<br>
&gt; &gt; be<br>
&gt; &gt; sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@i=
etf.org</a> instead. In either case, please retain the<br>
&gt; &gt; beginning of the Subject line to allow automated sorting.<br>
&gt; &gt;<br>
&gt; &gt; Abstract<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; =A0 =A0JSON Pointer defines a string syntax for identifying a spe=
cific<br>
&gt; &gt; value<br>
&gt; &gt; =A0 =A0within a JSON document.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; The file can be obtained via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-jso=
n-pointer/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-ap=
psawg-json-pointer/</a><br>
&gt; &gt;<br>
&gt; &gt; IESG discussion can be tracked via<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-appsawg-jso=
n-pointer/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-=
ietf-appsawg-json-pointer/ballot/</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; apps-discuss mailing list<br>
&gt; &gt; <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-d=
iscuss@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discus=
s@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; apps-discuss mailing list<br>
&gt; <a href=3D"mailto:apps-discuss@ietf.org" target=3D"_blank">apps-discus=
s@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
&gt;<br>
</div></div></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Matthew =
P. C. Morley<br>

--14dae9cfcea43b0e9d04d101883e--

From denis.pinkas@bull.net  Mon Dec 17 07:31:31 2012
Return-Path: <denis.pinkas@bull.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 8279E21F8AD2 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 07:31:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level: 
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKSOQsE9wjEK for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 07:31:30 -0800 (PST)
Received: from odin2.bull.net (odin2.bull.net [129.184.85.11]) by ietfa.amsl.com (Postfix) with ESMTP id 0378821F8B03 for <ietf@ietf.org>; Mon, 17 Dec 2012 07:31:29 -0800 (PST)
Received: from MSGC-007.bull.fr (unknown [129.184.87.136]) by odin2.bull.net (Bull S.A.) with ESMTP id 1BD151CCC0 for <ietf@ietf.org>; Mon, 17 Dec 2012 16:31:28 +0100 (CET)
Received: from [127.0.0.1] ([129.182.109.143]) by MSGC-007.bull.fr (Lotus Domino Release 8.5.3FP1) with ESMTP id 2012121716312720-23796 ; Mon, 17 Dec 2012 16:31:27 +0100 
Message-ID: <50CF3ACB.2070201@bull.net>
Date: Mon, 17 Dec 2012 16:31:23 +0100
From: Denis Pinkas <denis.pinkas@bull.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [pkix] Fwd: Last Call: <draft-schaad-pkix-rfc2875-bis-03.txt> (Diffie-Hellman Proof-of-Possession Algorithms) to Proposed Standard
References: <20121205220801.25486.73072.idtracker@ietfa.amsl.com> <50CF3435.9020403@ieca.com>
In-Reply-To: <50CF3435.9020403@ieca.com>
X-MIMETrack: Itemize by SMTP Server on MSGC-007/SRV/BULL(Release 8.5.3FP1|March 07, 2012) at 17/12/2012 16:31:27, Serialize by Router on MSGC-007/SRV/BULL(Release 8.5.3FP1|March 07, 2012) at 17/12/2012 16:31:28, Serialize complete at 17/12/2012 16:31:28
X-TNEFEvaluated: 1
Content-Type: multipart/alternative; boundary="------------060609020605040509090500"
X-Mailman-Approved-At: Mon, 17 Dec 2012 08:33:59 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 15:31:31 -0000

This is a multi-part message in MIME format.
--------------060609020605040509090500
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


The text states: "The reasoning behind doing POP can be found in 
Appendix C in [CRMF]."

Appendix C from [CRMF] states:

       POP for key management keys:   Similarly, POP for key management

       keys (that is, keys used for either key agreement or key exchange)

       can help to prevent undermining confidence in the PKI.   Suppose

       that Al is a new instructor in the Computer Science Department of

       a local university.   Al has created a draft final exam for the

       Introduction to Networking course he is teaching.   He wants to

       send a copy of the draft final to Dorothy, the Department Head,

       for her review prior to giving the exam.   This exam will of course

       be encrypted, as several students have access to the computer

       system.   However, a quick search of the certificate repository

       (e.g., search the repository for all records with

       subjectPublicKey=Dorothy's-value) turns up the fact thatseveral

       students have certificates containing the same public key

       management  key as Dorothy.   At this point, if no POP has been done

       by the CA, Al has no way of knowing whether all of the students

       have simply created these certificates without knowing the

       corresponding private key (and thus it is safe to send the

       encrypted exam to Dorothy), or whether the students have somehow

       acquired Dorothy's private key (and thus it is certainly not safe

       to send the exam).   Thus, the service to be provided by the PKI

       allowing users to communicate with one another, with confidence in

       who they are communicating with, has been totally defeated.   If

       the CA is providing POP, then either no students will have such

       certificates, or Al can know with certainty that the students do

       indeed know Dorothy's private key, and act accordingly.


I do not believe that refering to this text is adequate nor sufficient.
A real explanation, in the context of DH key exchange, is necessary,

Denis

> Some on this list might be interested about this draft. Please send 
> any comments to ietf@ietf.org.
>
> spt
>
> -------- Original Message --------
> Subject: Last Call: <draft-schaad-pkix-rfc2875-bis-03.txt> 
> (Diffie-Hellman Proof-of-Possession Algorithms) to Proposed Standard
> Date: Wed, 05 Dec 2012 14:08:01 -0800
> From: The IESG <iesg-secretary@ietf.org>
> Reply-To: ietf@ietf.org
> To: IETF-Announce <ietf-announce@ietf.org>
>
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Diffie-Hellman Proof-of-Possession Algorithms'
>   <draft-schaad-pkix-rfc2875-bis-03.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-01-02. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes two methods for producing an integrity check
>    value from a Diffie-Hellman key pair and one method for producing an
>    integrity check value from an Elliptic Curve key pair.  This behavior
>    is needed for such operations as creating the signature of a PKCS #10
>    certification request.  These algorithms are designed to provide a
>    proof-of-possession rather than general purpose signing.
>
>    This document obsoletes RFC 2875.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-schaad-pkix-rfc2875-bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-schaad-pkix-rfc2875-bis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix


--------------060609020605040509090500
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset=ISO-8859-1

<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"><br>
      The text states: "The reasoning behind doing POP can be found in
      Appendix C in [CRMF]."<br>
      <br>
      Appendix C from [CRMF] states:<br>
      <br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>POP for key management keys:<span style="mso-spacerun:yes">&nbsp; </span>Similarly, POP for key management<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>keys (that is, keys used for either key agreement or key exchange)<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>can help to prevent undermining confidence in the PKI.<span style="mso-spacerun:yes">&nbsp; </span>Suppose<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>that Al is a new instructor in the Computer Science Department of<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>a local university.<span style="mso-spacerun:yes">&nbsp; </span>Al has created a draft final exam for the<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Introduction to Networking course he is teaching.<span style="mso-spacerun:yes">&nbsp; </span>He wants to<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>send a copy of the draft final to Dorothy, the Department Head,<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>for her review prior to giving the exam.<span style="mso-spacerun:yes">&nbsp; </span>This exam will of course<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>be encrypted, as several students have access to the computer<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>system.<span style="mso-spacerun:yes">&nbsp; </span>However, a quick search of the certificate repository<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>(e.g., search the repository for all records with<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>subjectPublicKey=Dorothy's-value) turns up the fact that <span style="background:yellow;mso-highlight:yellow">several<o:p></o:p></span></span></pre>
      <pre><span style="background:yellow;mso-highlight:yellow;mso-ansi-language:
EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>students have certificates containing the same public key<o:p></o:p></span></pre>
      <pre><span style="background:yellow;mso-highlight:yellow;mso-ansi-language:
EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>management</span><span style="mso-ansi-language:EN-GB" lang="EN-GB"> key as Dorothy.<span style="mso-spacerun:yes">&nbsp; </span>At this point, if no POP has been done<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>by the CA, Al has no way of knowing whether all of the students<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>have simply created these certificates without knowing the<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>corresponding private key (and thus it is safe to send the<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>encrypted exam to Dorothy), or whether the students have somehow<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>acquired Dorothy's private key (and thus it is certainly not safe<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>to send the exam).<span style="mso-spacerun:yes">&nbsp; </span>Thus, the service to be provided by the PKI<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>allowing users to communicate with one another, with confidence in<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>who they are communicating with, has been totally defeated.<span style="mso-spacerun:yes">&nbsp; </span>If<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>the CA is providing POP, then either no students will have such<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>certificates, or Al can know with certainty that the students do<o:p></o:p></span></pre>
      <pre><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>indeed know Dorothy's private key, and act accordingly.<o:p></o:p></span></pre>
      <meta name="ProgId" content="Word.Document">
      <meta name="Generator" content="Microsoft Word 11">
      <meta name="Originator" content="Microsoft Word 11">
      <link rel="File-List"
href="file:///C:%5CDOCUME%7E1%5CPINKAS%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml">
      <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
 </w:LatentStyles>
</xml><![endif]-->
      <style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	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:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]--><br>
      I do not believe that refering to this text is adequate nor
      sufficient. <br>
      A real explanation, in the context of DH key exchange, is
      necessary,&nbsp; <br>
      <br>
      Denis<br>
      <br>
    </div>
    <blockquote cite="mid:50CF3435.9020403@ieca.com" type="cite">Some on
      this list might be interested about this draft. Please send any
      comments to <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>.
      <br>
      <br>
      spt
      <br>
      <br>
      -------- Original Message --------
      <br>
      Subject: Last Call: &lt;draft-schaad-pkix-rfc2875-bis-03.txt&gt;
      (Diffie-Hellman Proof-of-Possession Algorithms) to Proposed
      Standard
      <br>
      Date: Wed, 05 Dec 2012 14:08:01 -0800
      <br>
      From: The IESG <a class="moz-txt-link-rfc2396E" href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a>
      <br>
      Reply-To: <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>
      <br>
      To: IETF-Announce <a class="moz-txt-link-rfc2396E" href="mailto:ietf-announce@ietf.org">&lt;ietf-announce@ietf.org&gt;</a>
      <br>
      <br>
      <br>
      The IESG has received a request from an individual submitter to
      consider
      <br>
      the following document:
      <br>
      - 'Diffie-Hellman Proof-of-Possession Algorithms'
      <br>
      &nbsp; &lt;draft-schaad-pkix-rfc2875-bis-03.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 class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-01-02. Exceptionally, comments
      may be
      <br>
      sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
      <br>
      beginning of the Subject line to allow automated sorting.
      <br>
      <br>
      Abstract
      <br>
      <br>
      <br>
      &nbsp;&nbsp; This document describes two methods for producing an integrity
      check
      <br>
      &nbsp;&nbsp; value from a Diffie-Hellman key pair and one method for
      producing an
      <br>
      &nbsp;&nbsp; integrity check value from an Elliptic Curve key pair.&nbsp; This
      behavior
      <br>
      &nbsp;&nbsp; is needed for such operations as creating the signature of a
      PKCS #10
      <br>
      &nbsp;&nbsp; certification request.&nbsp; These algorithms are designed to
      provide a
      <br>
      &nbsp;&nbsp; proof-of-possession rather than general purpose signing.
      <br>
      <br>
      &nbsp;&nbsp; This document obsoletes RFC 2875.
      <br>
      <br>
      <br>
      <br>
      <br>
      The file can be obtained via
      <br>
      <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-schaad-pkix-rfc2875-bis/">http://datatracker.ietf.org/doc/draft-schaad-pkix-rfc2875-bis/</a>
      <br>
      <br>
      IESG discussion can be tracked via
      <br>
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-schaad-pkix-rfc2875-bis/ballot/">http://datatracker.ietf.org/doc/draft-schaad-pkix-rfc2875-bis/ballot/</a>
      <br>
      <br>
      <br>
      No IPR declarations have been submitted directly on this I-D.
      <br>
      <br>
      <br>
      <br>
      <br>
      <br>
      _______________________________________________
      <br>
      pkix mailing list
      <br>
      <a class="moz-txt-link-abbreviated" href="mailto:pkix@ietf.org">pkix@ietf.org</a>
      <br>
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pkix">https://www.ietf.org/mailman/listinfo/pkix</a>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------060609020605040509090500--


From barryleiba.mailing.lists@gmail.com  Mon Dec 17 11:54:06 2012
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 B89F821F87D7 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 11:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.041
X-Spam-Level: 
X-Spam-Status: No, score=-103.041 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0bXqCmbuxdrw for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 11:54:06 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id CB44321F85BC for <ietf@ietf.org>; Mon, 17 Dec 2012 11:54:05 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so5048602lah.31 for <ietf@ietf.org>; Mon, 17 Dec 2012 11:54:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HI7kJYOjY9A6kV2ZVifunybB6vC4wYGdO4tRYvOubNs=; b=PnTP4/ory6Vwbz3jkaZ3KEgiIZGMkyWoUDmDDHDYqEBUaRVreAUKc337U0HfrDHHlS 5a8MYMZt03fAqkVN125j3yP1JM3utkfrxdrzg7uOJFLzAVlnsCgPSNZoobnRF1KxZy5O a42GH2sYCKhMpkTX+fZVcxEpdtyeLkDct3D6i+9J83qnKWRFKRuCcDeoVPQXe03up6e4 9rgPu1oA4OpuxgDnKQLNcIamJOmpM8DQD/AG1MdADAC+ZWCyCXz13c8vN4tB+SYicnH1 TCqKjRzAfpoODnEYED40hYYR+gHIUGS0Euhup+7LWt18rKnkhzwz5W7geQgo9zsAxmEw l4vA==
MIME-Version: 1.0
Received: by 10.112.51.233 with SMTP id n9mr6235274lbo.47.1355774044420; Mon, 17 Dec 2012 11:54:04 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Mon, 17 Dec 2012 11:54:04 -0800 (PST)
In-Reply-To: <p1txrkkc9p.fsf@d72933.na.sas.com>
References: <6B4F2945-EC54-4171-92FF-3A88CEB27D23@mnot.net> <p1txrkkc9p.fsf@d72933.na.sas.com>
Date: Mon, 17 Dec 2012 14:54:04 -0500
X-Google-Sender-Auth: z6y0iyqd_S-NYxSQQwb-AifMduk
Message-ID: <CAC4RtVDaxJRXw-LkEfot6gkJyDY9ncRdc9oD8WdNwMsi+20nQw@mail.gmail.com>
Subject: Re: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
From: Barry Leiba <barryleiba@computer.org>
To: "David J. Biesack" <David.Biesack@sas.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, 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: Mon, 17 Dec 2012 19:54:07 -0000

>> This was discussed in the Working Group, but it wasn't felt that the added
>> complexity was worth it; there's a strong feeling that this spec should be as
>> simple as possible.
>
> Might I suggest, however, using -1 instead of "-" to refer to the last item in an
> array, as this provides two benefits:
>
> 1) Allows for adding the complexity down the road in a compatible way, should
>    there be need
> 2) Uniformity; i.e. always using integer values for referring to array elements.

I have to say that this suggestion sounds very compelling to me, for
both reasons.  I know there's a bunch of running code out there, but
this (and perhaps teasing apart the "add" and "insert" concepts into
separate verbs) seems worth the bother.

Barry, as participant

From martin.thomson@gmail.com  Mon Dec 17 13:31:22 2012
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 AEEAE21F886F for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 13:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.918
X-Spam-Level: 
X-Spam-Status: No, score=-4.918 tagged_above=-999 required=5 tests=[AWL=-1.319, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFtm-UqY2Qdm for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 13:31:22 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id E6D3121F879A for <ietf@ietf.org>; Mon, 17 Dec 2012 13:31:21 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so37960lbk.31 for <ietf@ietf.org>; Mon, 17 Dec 2012 13:31:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ousvSUnx9p5KY66Rw1NW6nTmPN3tIwKWofQ+KfbKNaU=; b=x3hfzB6ULbLs3sDxB6JYqJWjVT4/0yduTKt2IyY7rsuPGfVYrsSZnGqoE+JiuasU4T L5flVMQdSDpNXvKYWQ6oxdN86f5wabwF86vsP3HxPrVRRJTVgWBZlgWyvFfl5Zlh/N9v 3ITMuffmLD+4vxp+GuI8X0GJdx4CuH+qCreGboGi3ghSwFrFb1kl7tAfK0Y7sCWMIyST td0foyDUeV8z2OYN0NF17JiqYpenM8+Nl2548ZHuxqd+L5ZBZYpw5RLG/rpV6bK7zr2K l1beluzeIqgLT7NYcpJ893q1GLu0jN0mUEI1z3uyB1UTFkmRX3MqedTUIZ1JgG1msVRd 6ScA==
MIME-Version: 1.0
Received: by 10.152.106.212 with SMTP id gw20mr12501178lab.8.1355779880815; Mon, 17 Dec 2012 13:31:20 -0800 (PST)
Received: by 10.112.98.200 with HTTP; Mon, 17 Dec 2012 13:31:20 -0800 (PST)
In-Reply-To: <CAC4RtVDaxJRXw-LkEfot6gkJyDY9ncRdc9oD8WdNwMsi+20nQw@mail.gmail.com>
References: <6B4F2945-EC54-4171-92FF-3A88CEB27D23@mnot.net> <p1txrkkc9p.fsf@d72933.na.sas.com> <CAC4RtVDaxJRXw-LkEfot6gkJyDY9ncRdc9oD8WdNwMsi+20nQw@mail.gmail.com>
Date: Mon, 17 Dec 2012 13:31:20 -0800
Message-ID: <CABkgnnUvu2ikiKvgP90Uro2BTaM2XzZSHNPmpRKaJiqoLj_qBg@mail.gmail.com>
Subject: Re: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
From: Martin Thomson <martin.thomson@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=UTF-8
Cc: Mark Nottingham <mnot@mnot.net>, "David J. Biesack" <David.Biesack@sas.com>, 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: Mon, 17 Dec 2012 21:31:22 -0000

On 17 December 2012 11:54, Barry Leiba <barryleiba@computer.org> wrote:
>> Might I suggest, however, using -1 instead of "-" to refer to the last item in an
>> array, as this provides two benefits:
>>
>> 1) Allows for adding the complexity down the road in a compatible way, should
>>    there be need
>> 2) Uniformity; i.e. always using integer values for referring to array elements.
>
> I have to say that this suggestion sounds very compelling to me, for
> both reasons.  I know there's a bunch of running code out there, but
> this (and perhaps teasing apart the "add" and "insert" concepts into
> separate verbs) seems worth the bother.

This is true, it does sound compelling.

There will, no doubt, be questions about why -2 doesn't work.  It's
tempting to implement -2 and -3, so you might have to explain why that
is a bad idea.

index = (index + length) % length

From eosterweil@verisign.com  Mon Dec 17 13:42:20 2012
Return-Path: <eosterweil@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 2828C21F8949 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 13:42:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.392
X-Spam-Level: 
X-Spam-Status: No, score=-4.392 tagged_above=-999 required=5 tests=[AWL=-0.793, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EkqieOi7cI57 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 13:42:16 -0800 (PST)
Received: from exprod6og120.obsmtp.com (exprod6og120.obsmtp.com [64.18.1.236]) by ietfa.amsl.com (Postfix) with ESMTP id 0611C21F8973 for <ietf@ietf.org>; Mon, 17 Dec 2012 13:42:16 -0800 (PST)
Received: from osprey.verisign.com ([216.168.239.75]) (using TLSv1) by exprod6ob120.postini.com ([64.18.5.12]) with SMTP ID DSNKUM+Rt09CC8NRY+lHwitUt5o7rqEVMkmY@postini.com; Mon, 17 Dec 2012 13:42:16 PST
Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [10.170.12.138]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id qBHLgFh4005477 for <ietf@ietf.org>; Mon, 17 Dec 2012 16:42:15 -0500
Received: from dul1eosterwe-m1.vcorp.ad.vrsn.com ([10.100.0.11]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 17 Dec 2012 16:42:14 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-algorithm-agility-08.txt> (Algorithm	Agility Procedure for RPKI.) to Proposed Standard
From: Eric Osterweil <eosterweil@verisign.com>
In-Reply-To: <20121130153835.30764.59524.idtracker@ietfa.amsl.com>
Date: Mon, 17 Dec 2012 16:42:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <37ADFDF9-912A-470E-BE5E-DC561659E2D9@verisign.com>
References: <20121130153835.30764.59524.idtracker@ietfa.amsl.com>
To: IETF Disgust <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
X-OriginalArrivalTime: 17 Dec 2012 21:42:14.0799 (UTC) FILETIME=[60F1E9F0:01CDDC9F]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 21:42:20 -0000

All,

Sorry for the late reply.  I realize these comments come after the 12/14 =
deadline, but it is my hope that they can still inform any active =
decision processes.

I'd like to mention that some of us have calculated that the global RPKI =
will take a significant amount of time to crawl [1], and the algorithm =
agility draft (as it is currently proposed) will almost double that =
time, because it will necessarily almost double the number of objects in =
the global RPKI.  I personally worry a lot about this approach, as I =
feel it will likely lead to an operationally unviable standard, in which =
routing will be unable to adapt to changes in configuration for days, =
weeks, or even months, because of this design (described in [1]).

The lateness of this message is simply a consequence of the fact that =
our analyses have taken longer than we planned, and I do apologize for =
that.

Thanks,

Eric

[ 1 ] =
http://techreports.verisignlabs.com/tr-lookup.cgi?trid=3D1120005&rev=3D2

On Nov 30, 2012, at 10:38 AM, The IESG wrote:

>=20
> The IESG has received a request from the Secure Inter-Domain Routing =
WG
> (sidr) to consider the following document:
> - 'Algorithm Agility Procedure for RPKI.'
>  <draft-ietf-sidr-algorithm-agility-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 2012-12-14. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document specifies the process that Certification Authorities
>   (CAs) and Relying Parties (RPs) participating in the Resource Public
>   Key Infrastructure (RPKI) will need to follow to transition to a new
>   (and probably cryptographically stronger) algorithm set.  The =
process
>   is expected to be completed in a time scale of months or years.
>   Consequently, no emergency transition is specified.  The transition
>   procedure defined in this document supports only a top-down =
migration
>   (parent migrates before children).
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-sidr-algorithm-agility/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-sidr-algorithm-agility/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> sidr mailing list
> sidr@ietf.org
> https://www.ietf.org/mailman/listinfo/sidr


From worley@shell01.TheWorld.com  Mon Dec 17 13:43:07 2012
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D63CB21F89A5 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 13:43:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.759
X-Spam-Level: 
X-Spam-Status: No, score=-99.759 tagged_above=-999 required=5 tests=[AWL=0.678, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VoRe9ieYQQei for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 13:43:07 -0800 (PST)
Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id 470C921F873F for <ietf@ietf.org>; Mon, 17 Dec 2012 13:43:07 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id qBHLgpc1021187 for <ietf@ietf.org>; Mon, 17 Dec 2012 16:42:54 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id qBHLgnJi3205651 for <ietf@ietf.org>; Mon, 17 Dec 2012 16:42:51 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id qBHLgmD33218862; Mon, 17 Dec 2012 16:42:48 -0500 (EST)
Date: Mon, 17 Dec 2012 16:42:48 -0500 (EST)
Message-Id: <201212172142.qBHLgmD33218862@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
Subject: Last call comments on draft-ietf-bliss-call-completion-18.
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2012 21:43:08 -0000

My apologies for dealing with this earlier.  I've been neglecting this
draft.

Fundamentally, I think the draft is in great shape.  The only
significant change is that I think a summary of the "retain option"
procedures and considerations should be added so the reader can see
how it affects the procedures (and how gateways to the PSTN handle
"retain").

Only items 2 and 19 have technical content; the remainder are
editorial.  Item 2 is a request to insert a short section summarizing
the "retain option" processing.  The relevant information is scattered
throughout the draft and it could be difficult for an implementer to
find all the fragments that are relevent.  Item 19 is probably an
editing error, but currently the ABNF doesn't match the text.

item 1) headers

Can you abbreviate my affiliation on the front page to "Ariadne"?  I
you are using XML2RFC, you can use the 'abrev' attribute of the
<organization> element:

    <organization abbrev='ISI'>
        USC/Information Sciences Institute
    </organization>

item 2) overall

The procedures regarding the retain option are scattered throughout
the document in a way that makes it difficult to see how it is
handled.  It seems to me that it would be helpful to add a summary of
retain option processing as a section, perhaps at the end of section
4.  This allows deleting the last paragraph of section 4.2, which is
vague when it stands alone.

   4.5 Summary of retain option procedures

   When the call completion call fails there are two possible options:
   the CC feature has to be activated again by caller's agent
   subscribing to callee's monitor, or CC remains activated and the
   original CC request remains in the queue.

   If the callee's monitor operates in the latter way, it is said to
   support the retain option.  Callee's monitors SHOULD support the
   retain option.  If a monitor supports the retain option, it SHOULD
   provide the cc-service-retention header in its call-completion
   events.  The caller's agent can use this header to know that this
   monitor supports the retain option.

   If a callee's monitor does not support the retain option (e.g., if
   it is a gateway to a network device whose CC functionality does not
   support the retain option), it SHOULD NOT provide the
   cc-service-retention header.  In addition, after a failed CC call
   that causes the CC request to be deleted from the queue, the
   monitor MUST terminate the corresponding agent's subscription to
   inform the agent that its CC request is no longer in the queue.

   After a failed CC call, the caller's agent MAY terminate its
   subscription, to inform the monitor that it is terminating its CC
   request.  After a failed CC call, the caller's agent MAY receive a
   termination of its subscription from the callee's monitor, if the
   monitor has terminated the agent's CC request.  In either case, the
   agent MAY create a new subscription (as described in section 6.2)
   to create a new CC request for the same original call.  The agent
   SHOULD avoid terminating one subscription and creating a new one if
   the caller's monitor has indicated support of the retain option.

I have used SHOULD to describe procedures which are desirable but are
not required for correct functioning.  In particular, the
cc-service-retention value does not have to be correct for a
properly-implemented agent and monitor to interact correctly.  This
gives us some freedom in situations where a gateway cannot discern
accurately whether the callee supports the retain option or not.

Pure SIP agents and monitors can implement all the SHOULD behaviors,
so in the pure-SIP case, CC is done with the retain option.

item 3) section 4.1

   The callee's monitor maintains information about the set of INVITEs
   received by the callee's UA(s) considered unsuccessful by the caller.

Strictly speaking, the monitor can't know if an INVITE is considered
unsuccessful by the caller.  This wording might fix that:

   The callee's monitor maintains information about the set of INVITEs
   received by the callee's UA(s) that the caller might consider
   unsuccessful.

item 4) section 4.2

   The callee's monitor
   keeps a list or queue of the caller's agent's subscriptions,
   representing the requests from the caller's agent to the callee's
---------------------------------------------------^
should be "agents"
   monitors for call-completion services.
----------^
should be "monitor"

item 5) section 4.2

   When the callee's monitor determines the callee and/or callee's UA
insert "are" here
   available for a CC call, it selects a caller to execute the CC call
   and sends a call-completion event update (''cc-state: ready'') via a
---------------------------------------------^^
this should probably use " rather than ''
   NOTIFY request to the selected caller's agent's subscription, telling
   it to begin the CC call to the callee's UA.

item 6) section 4.2

   When the call completion call fails there are two possible options:
   the CC feature has to be activated again by caller's agent
   subscribing to callee's monitor, or CC remains activated and the
   original CC request retains its position in the queue if retain
   option is supported.

This is kinda vague.  See item 2.

item 7) section 4.3

   There is no interaction between call completion and automatic redial,
-----------------------------------^
There is a risk of confusion.  I think this could be clarified as

   There is no interaction between automatic redial and call
   completion (as defined in this document), as they use different
   event packages and specify different behaviors regarding the
   events.

item 8) section 5

   Each CCE has an availability state, determined through caller's
   presence status at the callee's monitor.  A presence status of
   ''open'' represents CCE's availability state of 'available' and a
---^^
this should probably use " rather than ''
   presence status of "closed" represents CCE's availability state of
   'unavailable'.

item 9) section 5

   A CCE is identified by the
   request-URI (if it was taken from a call-completion event
--------------^^^^^^^
I think this would be clearer as

   request-URI of the PUBLISH request (if that URI was taken from a
   call-completion event

item 10) section 5

   notification which identifies the CCE) or the From URI of the request
   (matching the From URI recorded in the CCE).

   state of the CCE to 'not-available' (suspend).
------------------------^^^^
Other locations in the text use the value 'unavailable'.

item 11) section 7.1

   The callee's monitor SHOULD insert a URI in the Call-Info header

Since the first sentence of the previous paragraph specifies "MUST"
regarding inserting Call-Info, this "SHOULD" would be better specified
as "MUST".

item 12) section 7.1

   The 'm' parameter defines the "mode" of call completion.  The "m=NR"
   parameter indicates that it failed due to lack of response, the
----------------------------^^
this "it" should be "the original call"
   "m=BS" parameter indicates that it failed due to busy subscriber, and
-----------------------------------^^
the latter two "it"s are probably unambiguous
   the "m=NL" parameter indicates that it failed due to non registered
---------------------------------------^^
   subscriber (no devices are registered for the AoR contacted).  The

item 13) section 7.4

   The callee's UA(s) and the callee's monitor may give the CC call
   precedence over non-CC calls by evaluating the presence of the 'm'
   URI parameter and the From header of the INVITE request.
-----------------^^^

I don't think this "and" is correct.  One possibility is:

   The callee's UA(s) and the callee's monitor may give the CC call
   precedence over non-CC calls by evaluating the presence of the 'm'
   URI parameter in the From header of the INVITE request.

item 14) section 7.5

   the retain option and terminate the subscription along with the queue
   if it doesn't support the retain option.  Similarly, if the CC call
I think "queue" is supposed to be "CCE".

item 15) section 7.5

   completion" events, or any URI it returns as the "URI" line of the
---------------------------------------------^^
I think this is supposed to be "in".

item 16) section 7.5

   The receipt of the PUBLISH request initiates a presence event state
   for the caller's identity at the presence server functionality of the
   callee's monitor as specified in [RFC3903] , together with a logical
   presence server if this has not been done before for another call.

   Note: The presence server may initiate a presence event state for the
   caller's identity at the receipt of SUBSCRIBE request as well,
   dependent on the implementation.

These paragraphs do not match the following paragraph from 4.2:

       Upon receiving a SUBSCRIBE request from the caller's agent, the
       callee's monitor instantiates a presence state for the caller's UA
       which can be modified by the caller's UA to indicate its availability
       for CC call.  The status at the presence upon instantiation is
       "open".

Also, this section doesn't explicitly specify what is happening:  The
first sentences need to say that suspend requests are PUBLISH with
status 'closed'.  Somewhere in this section it needs to be mentioned
that the CCE is set to 'unavailable'.

item 17) section 7.6

Similarly to 7.5, the first sentences need to say that suspend
requests are PUBLISH with status 'closed'.  Somewhere in this section
it needs to be mentioned that the CCE is set to 'unavailable'.

The final sentence seems to be incorrect in some cases:

   If the callee
   is not busy and there is no entry in the CC queue which is currently
   being processed, the callee's monitor MUST process the queue as
   described in section 7.3 above.

because the callee's policy may not allow any CCE to be recalled at
this time.  (For example, if a recall for that CCE has recently
failed.)

Assembling these changes, I think something like this would be better:

   A CC request is resumed by a PUBLISH request from caller's agent as
   described in section 6.6, that is, containing a 'state' of 'open'.
   The presence event state for the caller's identity at the presence
   server functionality of the CC monitor MUST be updated as described
   in [RFC3903], and the corresponding CCE's availablity state must be
   set to 'available'.  This may cause the CCE to be selected for
   recall under the monitor's policy.

item 18) section 8

In the second example, I see two uses of "Content-Type: 'app/pidf'".
I think this should be spelled out as "Content-Type: application/pidf".

For the bodies, I think it would be safer to spell out the PIDF a bit
more:

         | Body: ...<status><basic>open</basic></status>...

item 19) section 10.3

   The cc-URI line provides a URI (possibly in the form of a name-addr)

but it also says

   cc-URI = "cc-URI" HCOLON addr-spec

There are three choices for the syntax of the value of cc-URI:

addr-spec
	this eliminates the possibility of generic-params ("header parameters")
name-addr
	this allows generic-params but requires that we rephrase the
	first sentences of the section, as a name-addr isn't a URI, strictly
	speaking.
addr-spec / name-addr
	this alternative is used a lot in headers, but we would have
	to mention that the rule in RFC 3261 section 20.10 applies:

	   Even if the "display-name" is empty, the "name-addr" form MUST be
	   used if the "addr-spec" contains a comma, semicolon, or question
	   mark.  There may or may not be LWS between the display-name and the
	   "<".

Looking at the old drafts, we changed the value from "(name-addr /
addr-spec)" to "addr-spec" in -15.  So the ABNF is probably correct.
So we should reduce the text of this section to just the first three
sentences:

   The cc-URI line provides a URI (possibly in the form of a name-addr)
   which the agent SHOULD use as the request-URI of the CC recall INVITE
   and the suspend/resume PUBLISH.  It SHOULD be provided in all
   NOTIFYs.  The URI SHOULD be globally routable and SHOULD uniquely
   identify the CCE in question. 

item 20) section 12.2

   Intended usage: LIMITED USE

We could expand this to:

   Intended usage:  Within the procedures of RFC XXXX.

item 21) section 12.4

   Reference: [RFC3261].[RFC5367][[RFC XXXX]]
-----------------------^

I think this is intended to be a comma.

Dale

From william.atwood@concordia.ca  Mon Dec 17 15:56:24 2012
Return-Path: <william.atwood@concordia.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 EDE9A11E8097 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 15:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.197
X-Spam-Level: 
X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6DqQhGkD9I4h for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 15:56:23 -0800 (PST)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.94]) by ietfa.amsl.com (Postfix) with ESMTP id 1913821F84F3 for <ietf@ietf.org>; Mon, 17 Dec 2012 15:56:13 -0800 (PST)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from william.atwood@concordia.ca) (8.13.7/8.13.7) with ESMTP id qBHNu7RU031289; Mon, 17 Dec 2012 18:56:08 -0500
Message-ID: <50CFB119.1010205@concordia.ca>
Date: Mon, 17 Dec 2012 18:56:09 -0500
From: John William Atwood <william.atwood@concordia.ca>
Organization: Concordia University, Montreal
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-udpchecksums-06.txt> (IPv6 and UDP Checksums for Tunneled Packets) to Proposed Standard
References: <20121212011555.15698.49063.idtracker@ietfa.amsl.com>
In-Reply-To: <20121212011555.15698.49063.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2012/12/17 18:56:08 EST
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, Philip Chimento <Philip.Chimento@jhuapl.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: Mon, 17 Dec 2012 23:56:25 -0000

Comments on draft-ietf-6man-udpchecksums-06

The following are comments on grammatical issues with the above-noted
document.  I apologize for waiting until IESG last call to make these
comments.

Abstract, line 5.  "for suitable" -> "for a suitable"

Page 3, para 4, line 2.  "Automatic IP Multicast Without Explicit
Tunnels" -> "Automatic Multicast Tunneling"

Page 4, section 3, para 1, second sentence.  This sentence has two
subordinate clauses and no principal clause.  I suggest removing the
second "where": in line 5:
"software, where the cost" -> "software, the cost"

Page 5, section 4.1, para 1, lines 4-5.  "thought safe" -> "thought to
be safe"

Bullet 1, line 1.  "Context (i.e. tunneling" -> "Context (i.e.,
tunneling)  (See below for the explanation.)

Line 9.  "that affect not only the" -> "that may affect much more than the"

Bullet 2, line 8.  "with both a non-zero-checksum and ones" -> "with a
non-zero-checksum and datagrams"   (There are two things wrong here.
First, the use of "both" could be taken to imply that the datagrams must
have both types of checksums (in the same packet), which is not what you
intend.  Second, when "both" is used, the two things referenced by
"both" should be "equal" grammatically.  In this case, one is "non-zero
checksum" and the other is "ones" (i.e., datagrams).  The proposed
rewording removes these problems.)

Bullet 3, line 1.  "packets" -> "packet"

Line 2.  "i.e." -> "i.e.,"

Line 4.  "i.e." -> "i.e.,"

Note:  Bullets 1 and 2 each begin with a sentence: "Context should be",
"Keep-alive datagrams should be".  Bullet 3 begins with a "header",
which is not a sentence.  In addition, it appears to me that you are
listing four things in the first sentence, and five things in the second
sentence.  Finally, you talk about the "protocol" with two senses in
sentence two.  I suspect that the second reference is really the
"protocol number" inside the tunneled packet.  You might consider
restructuring the first two sentences of the third bullet as follows:

"An attempt should be made to detect corruption of the address
information in an encapsulating packet.  A robust tunnel protocol should
track tunnel context based on the 5-tuple (tunneled protocol number,
IPv6 source address, IPv6 destination address, UDP source port, UDP
destination port)."

The third sentence should be left as it is.

Bullet 3, sub-bullet 1.  What does it mean, "the 5-tuple with a zero
checksum enabled"?  I _believe_ that you are trying to indicate that the
delivery mechanism has a data structure with the 5-tuple and an
indication that this context has enabled zero checksums and that the
incoming packet has a zero checksum and that the 5-tuple matches the one
in the data structure.  I am not sure what to suggest, but the potential
for erroneous coding seems high to me.

Bullet 3, sub-bullet 1.  If a payload is matched to the wrong context,
why is it delivered as if it were correct?  Is there something that I am
missing here?

Bullet 4 (on page 6).  Again, there is a "header", not a sentence.
However, at least this time the header ends with a colon, rather than a
period.

Page 7, Section 4.2, bullet 1, line 1.  "semantics that" -> "semantics,
which"  (See note at the end about which/that.)

Line 8.  "that an" -> "that any"

Bullet 3, line 5.  "effect" -> "affect"

Page 8, Bullet 1, line 6.  "spend" -> "spending  (to match "processing")

Section 4.3, line 5.  "needs" -> "need"  (has to agree with "protocols".)

Page 9, replacement text, para 1, lines 6-9.  This sentence has no
subject.  I suggest the following text:

"As an alternative usage for some protocols, such as protocols that use
UDP as a tunnel encapsulation, the zero-checksum mode MAY be enabled for
specific sets of ports."

I note, however, that the phrase "zero-checksum mode" is probably not
defined anywhere in RFC2460, so it may be necessary to be more specific
here: "a packet with a zero checksum MAY be allowed for specific sets of
ports."


NOTE on use of "which" and "that".  "that" is used when the phrase
following it is _required_ if we are going to be able to completely
identify what is being talked about, while "which" is used to introduce
supplementary information.  Some examples:

1) If there are three houses on the street, and only one of them is at
the corner, then you say:
"The house that is on the corner needs to be painted."
2) If there are three houses on the street, and only one of them is
yellow, then you say:
"The yellow house, which needs to be painted, is for sale."

In the first case, the observer cannot identify the exact house until
its position is given.  In the second case, the house is completely
identified by its colour, and the information about the need to be
painted is supplementary information.  This information is set off with
commas, and introduced with "which".

NOTES on the use of "i.e." and "e.g.".
"i.e." is an abbreviation for "id est", a Latin phrase meaning "that
is".  As such, it should be punctuated as if it were the full phrase.
Unless there is a parenthesis on one side or the other, it is always
preceded by a comma and a space, and always followed by a comma.
"e.g." is an abbreviation for "exempli gratia", a Latin phrase meaning
"for example".  It should also be punctuated as if the full phrase were
present.  Unless there is a parenthesis on one side or the other, it is
always preceded by a comma and a space, and always followed by a comma.


On 12/11/2012 8:15 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'IPv6 and UDP Checksums for Tunneled Packets'
>   <draft-ietf-6man-udpchecksums-06.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 2012-12-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document provides an update of the Internet Protocol version 6
>    (IPv6) specification (RFC2460) to improve the performance in the use
>    case when a tunnel protocol uses UDP with IPv6 to tunnel packets.
>    The performance improvement is obtained by relaxing the IPv6 UDP
>    checksum requirement for suitable tunneling protocol where header
>    information is protected on the "inner" packet being carried.  This
>    relaxation removes the overhead associated with the computation of
>    UDP checksums on IPv6 packets used to carry tunnel protocols.  The
>    specification describes how the IPv6 UDP checksum requirement can be
>    relaxed for the situation where the encapsulated packet itself
>    contains a checksum.  The limitations and risks of this approach are
>    described, and restrictions specified on the use of the method.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6man-udpchecksums/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6man-udpchecksums/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 

-- 
Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email:william.atwood@concordia.ca
1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8

From mnot@mnot.net  Mon Dec 17 16:10:47 2012
Return-Path: <mnot@mnot.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 7446121F86F5; Mon, 17 Dec 2012 16:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.753
X-Spam-Level: 
X-Spam-Status: No, score=-103.753 tagged_above=-999 required=5 tests=[AWL=-1.154, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOZI75UR5Lx2; Mon, 17 Dec 2012 16:10:46 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id B326A21F86B8; Mon, 17 Dec 2012 16:10:46 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3EA6C509B5; Mon, 17 Dec 2012 19:10:43 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART LC review of draft-ietf-appsawg-json-patch-08
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <1355764639.3017.8.camel@pbryan-wsl.internal.salesforce.com>
Date: Tue, 18 Dec 2012 11:10:41 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A474180D-347E-44C6-8651-225CC05EBFC1@mnot.net>
References: <023301cddb5f$73eb02d0$5bc10870$@gmail.com> <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net> <1355764639.3017.8.camel@pbryan-wsl.internal.salesforce.com>
To: Paul C. Bryan <pbryan@anode.ca>
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-appsawg-json-patch.all@tools.ietf.org, 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: Tue, 18 Dec 2012 00:10:47 -0000

Ah, thanks for the context; will change it back.


On 18/12/2012, at 4:17 AM, Paul C. Bryan <pbryan@anode.ca> wrote:

> Incidentally, early (draft-pbryan-json-patch-*) drafts were aligned =
with JSON; later feedback when adopted by the IETF APPSAWG changed it to =
binary (starting in draft-ietf-appsawg-json-patch-00). The grounds for =
this was a consensus that the JSON draft was wrong to have made it 8bit =
for UTF-8.
>=20
> Paul
>=20
> On Mon, 2012-12-17 at 14:25 +1100, Mark Nottingham wrote:
>> Both fixed in SVN; thanks for the review.
>>=20
>>=20
>> On 16/12/2012, at 6:32 PM, Roni Even <
>> ron.even.tlv@gmail.com
>> > wrote:
>>=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
>> > =20
>> >=20
>> > Please resolve these comments along with any other Last Call =
comments you may receive.
>> >=20
>> > =20
>> > Document: draft-ietf-appsawg-json-patch-08
>> > Reviewer: Roni Even
>> > Review Date:2012=9612=9616
>> > IETF LC End Date: 2012=9612=9625
>> > IESG Telechat date: 2013-1-10
>> > =20
>> > Summary: This draft is almost  ready for publication.
>> > =20
>> > =20
>> > Major issues:
>> > =20
>> > Minor issues:
>> > 1.       The document has as the intended status =93Informational=94 =
while the last call says that the intended status is proposed standard?
>> > =20
>> > =20
>> > Nits/editorial comments:
>> >=20
>> > 	=95 In the IANA section the =93Encoding considerations:  =
binary=94. I noticed that RFC 4627 has a broader description:
>> > =93Encoding considerations: 8bit if UTF-8; binary if UTF-16 or =
UTF-32
>> > JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON =
is written in UTF-8, JSON is 8bit compatible.  When JSON is written in =
UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.=94
>> > =20
>> > =20
>> >=20
>>=20
>> --
>> Mark Nottingham  =20
>> http://www.mnot.net/
>>=20
>>=20
>>=20
>>=20
>>=20
>=20

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




From mnot@mnot.net  Mon Dec 17 16:36:39 2012
Return-Path: <mnot@mnot.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 2AAA021E8039 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 16:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.732
X-Spam-Level: 
X-Spam-Status: No, score=-103.732 tagged_above=-999 required=5 tests=[AWL=-1.133, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dC7j4egqS2q for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 16:36:35 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id E3A8D21E802E for <ietf@ietf.org>; Mon, 17 Dec 2012 16:36:34 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F15C2509B6; Mon, 17 Dec 2012 19:36:32 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAC4RtVDaxJRXw-LkEfot6gkJyDY9ncRdc9oD8WdNwMsi+20nQw@mail.gmail.com>
Date: Tue, 18 Dec 2012 11:36:28 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F341FF15-EE2B-4D36-A484-1D44FB7D16F4@mnot.net>
References: <6B4F2945-EC54-4171-92FF-3A88CEB27D23@mnot.net> <p1txrkkc9p.fsf@d72933.na.sas.com> <CAC4RtVDaxJRXw-LkEfot6gkJyDY9ncRdc9oD8WdNwMsi+20nQw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1499)
Cc: "David J. Biesack" <David.Biesack@sas.com>, 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, 18 Dec 2012 00:36:39 -0000

I disagree. Adding a capability for other indices down the road is NOT =
compatible for existing uses, so adding it will cause confusion ("are =
you using the old JSON Pointer or the new one?") and interop problems.

IIRC the discussion in the WG went much along these lines, and led to us =
explicitly choosing a single character, rather than a misleading "-1" =
construct. I'd be more comfortable with changing the character to =
something even further away, rather than making this construct even more =
confusing.=20

The other way we could go would be to do full negative indexing; we =
don't have any use cases for that, and it increases complexity a bit, =
but at least it would be unsurprising.


On 18/12/2012, at 6:54 AM, Barry Leiba <barryleiba@computer.org> wrote:

>>> This was discussed in the Working Group, but it wasn't felt that the =
added
>>> complexity was worth it; there's a strong feeling that this spec =
should be as
>>> simple as possible.
>>=20
>> Might I suggest, however, using -1 instead of "-" to refer to the =
last item in an
>> array, as this provides two benefits:
>>=20
>> 1) Allows for adding the complexity down the road in a compatible =
way, should
>>   there be need
>> 2) Uniformity; i.e. always using integer values for referring to =
array elements.
>=20
> I have to say that this suggestion sounds very compelling to me, for
> both reasons.  I know there's a bunch of running code out there, but
> this (and perhaps teasing apart the "add" and "insert" concepts into
> separate verbs) seems worth the bother.
>=20
> Barry, as participant

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




From McQuilWP@pobox.com  Mon Dec 17 16:55:45 2012
Return-Path: <McQuilWP@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E8F21E8037 for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 16:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBKGc+ui88CJ for <ietf@ietfa.amsl.com>; Mon, 17 Dec 2012 16:55:41 -0800 (PST)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9CE5221E804A for <ietf@ietf.org>; Mon, 17 Dec 2012 16:55:30 -0800 (PST)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 33F05A46E; Mon, 17 Dec 2012 19:55:29 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=QmVVlyOffVWT GNlZZccT9EH25yU=; b=d5y1QFgGg5Jlmq6+xFilXb37mqAnIuiME97gDmwKs5y2 61FfecvsNSbygAOSxHgowCAAOGms8D28Fd0vMqB+afslzYnIjx3i98RBSE4a9wR9 PySYBWN1FoSoSN7Uc2NTPf2SWrh6GBHonEzrBJ3HV7QzNZnfeE8PdPv95UJSud0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=hgxlzp ezLO0UmqCIUvwrSvm5Bl+PSYqZHubtMVa7qW003oWow2fWd4kliY4DHEuvOtOZuc nAv3yuLNvD5Xh32GWk3oGADRXyJIjy52Cwq09YpdEy3UAJxU6kjrU4RZQgWBkga+ 0zA/M2jlB1TXtvg4TXxAN8AWZWEAx1SwOuigU=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 21504A46C; Mon, 17 Dec 2012 19:55:29 -0500 (EST)
Received: from BQ07NB (unknown [68.107.15.47]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id 40413A46B; Mon, 17 Dec 2012 19:55:28 -0500 (EST)
Date: Mon, 17 Dec 2012 16:55:26 -0800
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1128899190.20121217165526@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: draft-ietf-appsawg-json-pointer-07 - array index for end ofarray
In-Reply-To: <F341FF15-EE2B-4D36-A484-1D44FB7D16F4@mnot.net>
References: <6B4F2945-EC54-4171-92FF-3A88CEB27D23@mnot.net> <p1txrkkc9p.fsf@d72933.na.sas.com> <CAC4RtVDaxJRXw-LkEfot6gkJyDY9ncRdc9oD8WdNwMsi+20nQw@mail.gmail.com> <F341FF15-EE2B-4D36-A484-1D44FB7D16F4@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 9DBE5696-48AD-11E2-BA53-F0CE2E706CDE-02871704!b-pb-sasl-quonix.pobox.com
Cc: Barry Leiba <barryleiba@computer.org>, "David J. Biesack" <David.Biesack@sas.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, 18 Dec 2012 00:55:45 -0000

ISTM that if the person constructing the pointer wants to append 
to an array and knows the size of the array (as pointed out in 
another thread) he should be able to use "/foo/<len>" where <len> 
is the index of the element just after the last existing one in 
the array. No need for "/foo/-" or any negative integers. The only 
requirement is to allow that one extra index to be used without 
error.


On Mon, 2012-12-17, Mark Nottingham wrote:
> I disagree. Adding a capability for other indices down the
> road is NOT compatible for existing uses, so adding it will
> cause confusion ("are you using the old JSON Pointer or the new one?") and interop problems.

> IIRC the discussion in the WG went much along these lines, and
> led to us explicitly choosing a single character, rather than a
> misleading "-1" construct. I'd be more comfortable with
> changing the character to something even further away, rather
> than making this construct even more confusing. 

> The other way we could go would be to do full negative
> indexing; we don't have any use cases for that, and it
> increases complexity a bit, but at least it would be unsurprising.


> On 18/12/2012, at 6:54 AM, Barry Leiba
> <barryleiba@computer.org> wrote:

>>>> This was discussed in the Working Group, but it wasn't felt that the added
>>>> complexity was worth it; there's a strong feeling that this spec should be as
>>>> simple as possible.
>>> 
>>> Might I suggest, however, using -1 instead of "-" to refer to the last item in an
>>> array, as this provides two benefits:
>>> 
>>> 1) Allows for adding the complexity down the road in a compatible way, should
>>>   there be need
>>> 2) Uniformity; i.e. always using integer values for referring to array elements.
>> 
>> I have to say that this suggestion sounds very compelling to me, for
>> both reasons.  I know there's a bunch of running code out there, but
>> this (and perhaps teasing apart the "add" and "insert" concepts into
>> separate verbs) seems worth the bother.
>> 
>> Barry, as participant

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



-- 
Bill McQuillan <McQuilWP@pobox.com>


From sayrer@gmail.com  Mon Dec 17 19:41:05 2012
Return-Path: <sayrer@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 2E15721E8041; Mon, 17 Dec 2012 19:41:05 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UnL9vw0-n0JY; Mon, 17 Dec 2012 19:41:04 -0800 (PST)
Received: from mail-we0-f173.google.com (mail-we0-f173.google.com [74.125.82.173]) by ietfa.amsl.com (Postfix) with ESMTP id EE31821E8039; Mon, 17 Dec 2012 19:41:03 -0800 (PST)
Received: by mail-we0-f173.google.com with SMTP id z2so52964wey.18 for <multiple recipients>; Mon, 17 Dec 2012 19:41:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EGBKZGwymRgwmz1g5mmLkfZC6sPY+Bv7gBwz0ttxzis=; b=a4QThT785SUeJgyQq8yCu3l87w7yos6AajJojo2rSJaCVqUsDjBIPFRZPUmqtxHtee ozKTxZgPT3YuZQ61CDU9WGk1kLNFvzx5BH0s8RNvhBsHyp8/riuJLQFP+xjyPOT1GyD7 0sQ3QLc4Dud+DiXsRxCHinCUicsJGOv/wNkoKfKnPd8G4vKAyZp3reLRSwoZHbp6Hj/i FyzO5fwQAD6s5M6jkdbuu6W82Z8f5m2isVWD9ymcocr/LiDzUrrBlPk4Z61Z5JJqABSz Tj+NMmwQDDq9SA+BL0AaCybdm8leEv8k0xTEEz/gY5PmitJONpTRMFQA2XEExuPwbf4P r3lA==
MIME-Version: 1.0
Received: by 10.194.76.99 with SMTP id j3mr971835wjw.47.1355802062898; Mon, 17 Dec 2012 19:41:02 -0800 (PST)
Received: by 10.194.1.101 with HTTP; Mon, 17 Dec 2012 19:41:02 -0800 (PST)
In-Reply-To: <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com> <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com>
Date: Mon, 17 Dec 2012 19:41:02 -0800
Message-ID: <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Robert Sayre <sayrer@gmail.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 03:41:05 -0000

On Mon, Dec 17, 2012 at 7:08 AM, James M Snell <jasnell@gmail.com> wrote:
>
> Everyone's idea of "bloat" is different.

What I meant was that the predicate additions increase the size of the
protocol messages. Your example is twice as large. The check could be
more efficiently represented in the path notation or the operation
names.

> Again, the point is, I don't see this as a problem in practice. Implementers
> that make blind edits to arbitrary docs can expect surprising results
> sometimes. That's just the way it is. There are mechanisms defined (test,
> json-predicates and conditional requests) that can make the edit more
> reliable.

Well, one way of putting it would be that the patch format makes it
difficult to ensure convergence at quiescence in OT software when
there's a change in type from array to object or vice-versa:

<http://en.wikipedia.org/wiki/Operational_transformation#The_CC_model>

There's no good reason for it to be that way, is there?

- Rob

From jasnell@gmail.com  Mon Dec 17 19:54:10 2012
Return-Path: <jasnell@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 355BE21E804D; Mon, 17 Dec 2012 19:54:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.679
X-Spam-Level: 
X-Spam-Status: No, score=-3.679 tagged_above=-999 required=5 tests=[AWL=-0.081, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lB2A18v+QnkY; Mon, 17 Dec 2012 19:54:09 -0800 (PST)
Received: from mail-ia0-f173.google.com (mail-ia0-f173.google.com [209.85.210.173]) by ietfa.amsl.com (Postfix) with ESMTP id 50CA421E804C; Mon, 17 Dec 2012 19:54:09 -0800 (PST)
Received: by mail-ia0-f173.google.com with SMTP id w21so135259iac.32 for <multiple recipients>; Mon, 17 Dec 2012 19:54:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=xMnwV/UIS1JmPTGMpOCMLF7XzACv6147MLk94/lgUJA=; b=gNIWuRmxbqtkkrQqVSWgRFZgLGDvBLI5JjsfMP6gd7oBDrhZlZV4WmxLiYj29N3Xnt zWJbs/gJm9szzBkN4IXBYcENpRVLieziGbNqQcg0oy/vjW3s/eKBkP1PY8g1lBHkiZI9 x09WMF0WkPYoIrBKmRn8ojlQjCvDk5JBjNPlnxDEyjlEkHCUtmcooxi8ATY3nu/ae+41 QPI30wZvTQVwdd+kEoaRkHKgaGHKxP3Zl+g/77wUAJyyyNIhNWpJYgPuOhDQs7MC+4A8 Av0U7E5uMFPEjHwH4exm5RbqX7/pw3/MzO3/lK9QHSi2uUUacHJLRPGn61JmSzImbCpC QdVg==
Received: by 10.50.6.169 with SMTP id c9mr731126iga.24.1355802848780; Mon, 17 Dec 2012 19:54:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Mon, 17 Dec 2012 19:53:48 -0800 (PST)
In-Reply-To: <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com> <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com> <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 17 Dec 2012 19:53:48 -0800
Message-ID: <CABP7RbdQCh+9kLh22U1Oa3ncUt6VLB=M-hgJaTrRppXnxTeW7A@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: Robert Sayre <sayrer@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f6467172fe21404d1187383
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 03:54:10 -0000

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

The key advantage to the current syntax is that it's just absolutely drop
dead simple. I get what you're saying but I'd rather avoid increasing the
complexity of the syntax any more than we absolutely have to. And, to be
absolutely honest, I haven't yet seen an actual application case where it's
been an issue (that's not to say they don't exist, just haven't seen it in
practice yet). What's your suggestion for making the syntax better?

On Mon, Dec 17, 2012 at 7:41 PM, Robert Sayre <sayrer@gmail.com> wrote:

> On Mon, Dec 17, 2012 at 7:08 AM, James M Snell <jasnell@gmail.com> wrote:
> >
> > Everyone's idea of "bloat" is different.
>
> What I meant was that the predicate additions increase the size of the
> protocol messages. Your example is twice as large. The check could be
> more efficiently represented in the path notation or the operation
> names.
>
> > Again, the point is, I don't see this as a problem in practice.
> Implementers
> > that make blind edits to arbitrary docs can expect surprising results
> > sometimes. That's just the way it is. There are mechanisms defined (test,
> > json-predicates and conditional requests) that can make the edit more
> > reliable.
>
> Well, one way of putting it would be that the patch format makes it
> difficult to ensure convergence at quiescence in OT software when
> there's a change in type from array to object or vice-versa:
>
> <http://en.wikipedia.org/wiki/Operational_transformation#The_CC_model>
>
> There's no good reason for it to be that way, is there?
>
> - Rob
>

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

<div dir=3D"ltr"><font face=3D"courier new,monospace"><br></font><div class=
=3D"gmail_extra">The key advantage to the current syntax is that it&#39;s j=
ust absolutely drop dead simple. I get what you&#39;re saying but I&#39;d r=
ather avoid increasing the complexity of the syntax any more than we absolu=
tely have to. And, to be absolutely honest, I haven&#39;t yet seen an actua=
l application case where it&#39;s been an issue (that&#39;s not to say they=
 don&#39;t exist, just haven&#39;t seen it in practice yet). What&#39;s you=
r suggestion for making the syntax better?<br>

<br><div class=3D"gmail_quote">On Mon, Dec 17, 2012 at 7:41 PM, Robert Sayr=
e <span dir=3D"ltr">&lt;<a href=3D"mailto:sayrer@gmail.com" target=3D"_blan=
k">sayrer@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>

<div class=3D"im">On Mon, Dec 17, 2012 at 7:08 AM, James M Snell &lt;<a hre=
f=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Everyone&#39;s idea of &quot;bloat&quot; is different.<br>
<br>
</div>What I meant was that the predicate additions increase the size of th=
e<br>
protocol messages. Your example is twice as large. The check could be<br>
more efficiently represented in the path notation or the operation<br>
names.<br>
<div class=3D"im"><br>
&gt; Again, the point is, I don&#39;t see this as a problem in practice. Im=
plementers<br>
&gt; that make blind edits to arbitrary docs can expect surprising results<=
br>
&gt; sometimes. That&#39;s just the way it is. There are mechanisms defined=
 (test,<br>
&gt; json-predicates and conditional requests) that can make the edit more<=
br>
&gt; reliable.<br>
<br>
</div>Well, one way of putting it would be that the patch format makes it<b=
r>
difficult to ensure convergence at quiescence in OT software when<br>
there&#39;s a change in type from array to object or vice-versa:<br>
<br>
&lt;<a href=3D"http://en.wikipedia.org/wiki/Operational_transformation#The_=
CC_model" target=3D"_blank">http://en.wikipedia.org/wiki/Operational_transf=
ormation#The_CC_model</a>&gt;<br>
<br>
There&#39;s no good reason for it to be that way, is there?<br>
<br>
- Rob<br>
</blockquote></div><br></div></div>

--e89a8f6467172fe21404d1187383--

From jasnell@gmail.com  Mon Dec 17 21:25:11 2012
Return-Path: <jasnell@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 1339321F8573; Mon, 17 Dec 2012 21:25:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.677
X-Spam-Level: 
X-Spam-Status: No, score=-3.677 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4su-CWVsEASZ; Mon, 17 Dec 2012 21:25:10 -0800 (PST)
Received: from mail-ia0-f181.google.com (mail-ia0-f181.google.com [209.85.210.181]) by ietfa.amsl.com (Postfix) with ESMTP id 3094121F8563; Mon, 17 Dec 2012 21:25:09 -0800 (PST)
Received: by mail-ia0-f181.google.com with SMTP id s32so186365iak.12 for <multiple recipients>; Mon, 17 Dec 2012 21:25:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KuWfD+hl74ZdxJEk5LpuYCQ7BwOSl2EI+wuDq5WKqaI=; b=QeaiDSd+pNo65tao6tByZ5QEMDm5QIq5aRYQyF43d8nolclR106ysCzi3lFsLjNXG3 sHIOtNihujKltZMZ+57hXP+7mY3x48G7a2HHp9gPPBjEriEoNcsOINEkr019jR1m2/gp I1G1E+2QmCjn3J52cDkZ4hXcR9xlGws4rKDtxQ1NRYUd8vig30Uvl9I8w0fqRBwVRsBF YYcV813S6+O0xHBEJDrNyx7PI3P/un8sqdB9gB6Ow2a41XiifcnxE7tC+oFJhXg4DluZ oAjOtwaz+IJ+DkHud+VehePrBbOjGvgPfG1/oM0YIqGl3gDaFGls8MExrU3Hq0fcoeH0 Cpdw==
Received: by 10.50.178.106 with SMTP id cx10mr1306380igc.24.1355808308974; Mon, 17 Dec 2012 21:25:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.7.19 with HTTP; Mon, 17 Dec 2012 21:24:48 -0800 (PST)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1150408948F@WSMSG3153V.srv.dir.telstra.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com> <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com> <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1150408948F@WSMSG3153V.srv.dir.telstra.com>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 17 Dec 2012 21:24:48 -0800
Message-ID: <CABP7Rbc10-B1Fgu5w5LSATWW2vCxdcpERKTi6cbUXgF03ks7Cw@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: multipart/alternative; boundary=e89a8f5036c8a3d5f404d119b87a
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 05:25:11 -0000

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

What I'm not clear on, however, is what significant benefit making this
kind of change would provide. Yes, the syntax can be more verbose and exact
but it's not clear that the change is worth the cost.

Robert mentioned that the addition of the json-predicates test doubled the
size of the json-patch file, and yes, I get that.. but if we're talking
about sending a two-object json-patch document to modify a JSON document
many times larger than that, it's still worth the extra handful of bytes it
takes. Sure, if we had a complex patch document consisting of large amounts
of json-patch and json-predicate objects being applied to an arbitrarily
structured document, I could understand the concern, but in that case one
would have to question the wisdom of doing a partial update in the first
place. JSON-Patch documents are best served small and simple, and the
inclusion of a json-predicate or two per instance is not going to blow the
budget on bits on the wire.

So the key question becomes: what added benefit does a more verbose pointer
syntax provide us? And is there a concrete need for that benefit that can
be demonstrated?

- James


On Mon, Dec 17, 2012 at 9:12 PM, Manger, James H <
James.H.Manger@team.telstra.com> wrote:

> If we were starting from scratch and defining JSON Pointer again I would
> argue for distinguishing array indices and object names in the syntax. For
> instance, prefix an object name with "/" and an array index with ":".
>
>    json-pointer = *segment
>    segment = "/" name  /  ":" index
>    name = *( unescaped / escaped )
>    unescaped = %x00-2E / %x30-39 / %x3B-7D / %x7F-10FFFF
>    escaped = "~" ( "0" / "1" / "2" )
>    index = "0" / %x31-39 *(%x30-39) / "-"
>
> 1. It makes parsing marginally harder: you cannot just split on "/" and
> unescape each segment.
> 2. It doesn't make much difference for selecting a value from some JSON,
> or for finding a spot to insert a new value.
> 3. It would allow you to automatically create object *or array* ancestors
> when setting a new value (eg adding 23 at /a:0/b:0 to {} could give
> {"a":[{"b":[23]}]}).
> 4. It might encourage better validation of pointers, but that is probably
> wishful thinking.
>
> But JSON Pointer drafts have used the /{name|index} format for a year.
> There are a bunch of implementations. The difference is minor in most
> circumstances. So while I would be happy to change, I am also comfortable
> staying with the current pointer syntax.
>
>
> > There's no good reason for it to be that way, is there?
>
> I don't think so.
>
> --
> James Manger
>

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

<div dir=3D"ltr"><font face=3D"courier new,monospace">What I&#39;m not clea=
r on, however, is what significant benefit making this kind of change would=
 provide. Yes, the syntax can be more verbose and exact but it&#39;s not cl=
ear that the change is worth the cost.=C2=A0</font><div>

<font face=3D"courier new,monospace"><br></font></div><div><font face=3D"co=
urier new,monospace">Robert mentioned that the addition of the json-predica=
tes test doubled the size of the json-patch file, and yes, I get that.. but=
 if we&#39;re talking about sending a two-object json-patch document to mod=
ify a JSON document many times larger than that, it&#39;s still worth the e=
xtra handful of bytes it takes. Sure, if we had a complex patch document co=
nsisting of large amounts of json-patch and json-predicate objects being ap=
plied to an=C2=A0arbitrarily structured document, I could understand the co=
ncern, but in that case one would have to question the wisdom of doing a pa=
rtial update in the first place. JSON-Patch documents are best served small=
 and simple, and the inclusion of a json-predicate or two per instance is n=
ot going to blow the budget on bits on the wire.=C2=A0</font></div>

<div><font face=3D"courier new,monospace"><br></font></div><div style><font=
 face=3D"courier new,monospace">So the key question becomes: what added ben=
efit does a more verbose pointer syntax provide us? And is there a concrete=
 need for that benefit that can be demonstrated?</font></div>

<div style><font face=3D"courier new,monospace"><br></font></div><div style=
><font face=3D"courier new,monospace">- James</font></div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Dec 17, 2012 at=
 9:12 PM, Manger, James H <span dir=3D"ltr">&lt;<a href=3D"mailto:James.H.M=
anger@team.telstra.com" target=3D"_blank">James.H.Manger@team.telstra.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">If we were starting from scratch and definin=
g JSON Pointer again I would argue for distinguishing array indices and obj=
ect names in the syntax. For instance, prefix an object name with &quot;/&q=
uot; and an array index with &quot;:&quot;.<br>


<br>
=C2=A0 =C2=A0json-pointer =3D *segment<br>
=C2=A0 =C2=A0segment =3D &quot;/&quot; name =C2=A0/ =C2=A0&quot;:&quot; ind=
ex<br>
=C2=A0 =C2=A0name =3D *( unescaped / escaped )<br>
=C2=A0 =C2=A0unescaped =3D %x00-2E / %x30-39 / %x3B-7D / %x7F-10FFFF<br>
=C2=A0 =C2=A0escaped =3D &quot;~&quot; ( &quot;0&quot; / &quot;1&quot; / &q=
uot;2&quot; )<br>
=C2=A0 =C2=A0index =3D &quot;0&quot; / %x31-39 *(%x30-39) / &quot;-&quot;<b=
r>
<br>
1. It makes parsing marginally harder: you cannot just split on &quot;/&quo=
t; and unescape each segment.<br>
2. It doesn&#39;t make much difference for selecting a value from some JSON=
, or for finding a spot to insert a new value.<br>
3. It would allow you to automatically create object *or array* ancestors w=
hen setting a new value (eg adding 23 at /a:0/b:0 to {} could give {&quot;a=
&quot;:[{&quot;b&quot;:[23]}]}).<br>
4. It might encourage better validation of pointers, but that is probably w=
ishful thinking.<br>
<br>
But JSON Pointer drafts have used the /{name|index} format for a year. Ther=
e are a bunch of implementations. The difference is minor in most circumsta=
nces. So while I would be happy to change, I am also comfortable staying wi=
th the current pointer syntax.<br>


<div class=3D"im"><br>
<br>
&gt; There&#39;s no good reason for it to be that way, is there?<br>
<br>
</div>I don&#39;t think so.<br>
<br>
--<br>
James Manger<br>
</blockquote></div><br></div>

--e89a8f5036c8a3d5f404d119b87a--

From magnus.westerlund@ericsson.com  Tue Dec 18 02:31:54 2012
Return-Path: <magnus.westerlund@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 9742B21F884C for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 02:31:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.213
X-Spam-Level: 
X-Spam-Status: No, score=-106.213 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9Wk29uFxsUp for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 02:31:54 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 819CD21F8840 for <ietf@ietf.org>; Tue, 18 Dec 2012 02:31:53 -0800 (PST)
X-AuditID: c1b4fb30-b7f736d0000010de-31-50d046122af8
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id CD.39.04318.21640D05; Tue, 18 Dec 2012 11:31:46 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0197.eemea.ericsson.se (153.88.115.88) with Microsoft SMTP Server id 8.3.279.1; Tue, 18 Dec 2012 11:31:46 +0100
Message-ID: <50D04611.5040807@ericsson.com>
Date: Tue, 18 Dec 2012 11:31:45 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: John William Atwood <william.atwood@concordia.ca>
Subject: Re: Last Call: <draft-ietf-6man-udpchecksums-06.txt> (IPv6 and UDP Checksums for Tunneled Packets) to Proposed Standard
References: <20121212011555.15698.49063.idtracker@ietfa.amsl.com> <50CFB119.1010205@concordia.ca>
In-Reply-To: <50CFB119.1010205@concordia.ca>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCLMWRmVeSWpSXmKPExsUyM+Jvja6Q24UAg8n7BS2ebZzPYnFn81pm i94HM1ktmhZfYXVg8fhy5BWjx85Zd9k9liz5yeRxd75VAEsUl01Kak5mWWqRvl0CV8axD9eY Cz5KVcx4oNjAeFy0i5GTQ0LAROLc0+vMELaYxIV769m6GLk4hAROMkr8bnkG5SxnlPi0aScb SBWvgLbE6cdL2UFsFgFVia9zZ4DF2QQsJG7+aASzRQV8JWbt+cUEUS8ocXLmExYQW0TAVOLS tdtg25gFCiU2XJzKCLJAWKCJUeL1qwdgzUICiRKbzreBNXAK6Eicfr+DCeI8SYlF0zpZIJr1 JKZcbWGEsOUlmrfOZobo1ZZoaOpgncAoNAvJ7llIWmYhaVnAyLyKkT03MTMnvdx8EyMwpA9u +W2wg3HTfbFDjNIcLErivOGuFwKEBNITS1KzU1MLUovii0pzUosPMTJxcEoBA1F62+lXn575 10980rZ+fptZzNqVXgy5Fw5lsphlXDk17Vfcs797FzA7PD212NLxrbril+uJ06ayb5f7vV+K +0wiy8LzH/xnHL/sP1f7/D2Duc8fmRpVreCxlJ7fEtk/8xa38ez3ARdNFS7mpaaWeZU9eV+r cNe6QvP3ze/TLrlfVrPN3X+seZsSS3FGoqEWc1FxIgBkv7mYNwIAAA==
Cc: ietf@ietf.org, Philip Chimento <Philip.Chimento@jhuapl.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, 18 Dec 2012 10:31:54 -0000

Thanks John

The editorial nits we will take care of in an update. Many of these are
new due to the significant changes, and this is in fact the first chance
to comment on them. Thus, do not feel bad for it being IETF last call.


On 2012-12-18 00:56, John William Atwood wrote:
> Comments on draft-ietf-6man-udpchecksums-06
> 
> 

> 
> Bullet 3, sub-bullet 1.  What does it mean, "the 5-tuple with a zero
> checksum enabled"?  I _believe_ that you are trying to indicate that the
> delivery mechanism has a data structure with the 5-tuple and an
> indication that this context has enabled zero checksums and that the
> incoming packet has a zero checksum and that the 5-tuple matches the one
> in the data structure.  I am not sure what to suggest, but the potential
> for erroneous coding seems high to me.

A packet matching an existing context which has zero checksum enables
receives a packet not intended for this context, but due to some
corruption event of the address information it arrives in this context.

You are correct that there is basically nothing you can do against this
unless you actually have a checksum to detect the corruption. In the
case of a tunneling protocol is is also likely that the tunneling
protocol is so thin, i.e. no or few headers that using them to detect
that this packet is not intended for this context is difficult.
Correctly I think this is something you have to accept when using
non-checksum protected receivers. It can occur but more than 10000 times
as common when using Internet checksums.

> 
> Bullet 3, sub-bullet 1.  If a payload is matched to the wrong context,
> why is it delivered as if it were correct?  Is there something that I am
> missing here?

The receiving context interprets the packet according to the rules of
the existing context. If nothing in this processing is tripped then what
was in that packet will be used as a valid packet in that context.

To be clear here, we are describing the cases using full knowledge of
what occurs, but the receiving node can't see the difference between a
corrupted zero-checksummed packet and a correct one. That is what it
requires the checksum to do.

> 
> Page 9, replacement text, para 1, lines 6-9.  This sentence has no
> subject.  I suggest the following text:
> 
> "As an alternative usage for some protocols, such as protocols that use
> UDP as a tunnel encapsulation, the zero-checksum mode MAY be enabled for
> specific sets of ports."
> 
> I note, however, that the phrase "zero-checksum mode" is probably not
> defined anywhere in RFC2460, so it may be necessary to be more specific
> here: "a packet with a zero checksum MAY be allowed for specific sets of
> ports."

The zero-checksum mode is intended to be defined by this text, where the
zero-checksum mode is defined by the rules in draft-ietf-6man-udpzero. I
have some difficulties determining what changes would improve this.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From chair@ietf.org  Tue Dec 18 07:48:57 2012
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 32BEB21F86C7; Tue, 18 Dec 2012 07:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.932
X-Spam-Level: 
X-Spam-Status: No, score=-102.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VV4pmysRTFfO; Tue, 18 Dec 2012 07:48:56 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 9112C21F862D; Tue, 18 Dec 2012 07:48:53 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7F53E124ABD; Tue, 18 Dec 2012 07:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IRO6PiPH6K7N; Tue, 18 Dec 2012 07:48:53 -0800 (PST)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 1420E1245F2; Tue, 18 Dec 2012 07:48:52 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Orlando IETF Codesprint
Mime-Version: 1.0 (Apple Message framework v1085)
From: IETF Chair <chair@ietf.org>
Date: Tue, 18 Dec 2012 10:48:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9A45ECE-3815-419A-8CEB-F8C9EAFF95F5@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>, 86all@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, 18 Dec 2012 15:48:57 -0000

Vancouver IETF Codesprint

When:  Saturday, 9 March 2013, starting at 9:30 AM

Where: IETF Hotel

What:  A bunch of hackers get together to work on code for the
   IETF.  All code will become part of the open source IETF tools.

Who:   Hopefully you can help

Many of the results of previous codesprint activities are being used =
every day by the IETF community.  Shortly before the Paris meeting, we =
transitioned to a new database schema.  It makes many tasks much easier. =
 Please come to the codesprint and work to polish or improve existing =
tools, fix bugs, or make altogether new tools.  All efforts are =
appreciated and most welcome.

Steve Conte and Robert Sparks will be helping with advance planning.  =
Henrik Levkowetz will be coordinating the event in Vancouver.  You can =
find more information here:

  http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF86Sprint

If you are able to participate, please sign up on the wiki at:

  http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF86SprintSignUp

Please support the tools development effort,
 Russ


From pbryan@anode.ca  Mon Dec 17 09:17:29 2012
Return-Path: <pbryan@anode.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 F1B0C21F8B6E; Mon, 17 Dec 2012 09:17:28 -0800 (PST)
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=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vc6FeGE8uFjq; Mon, 17 Dec 2012 09:17:27 -0800 (PST)
Received: from maple.anode.ca (maple.anode.ca [72.14.183.184]) by ietfa.amsl.com (Postfix) with ESMTP id 5028F21F8B32; Mon, 17 Dec 2012 09:17:27 -0800 (PST)
Received: from [10.126.22.61] (nat-204-14-239-210-sfo.net.salesforce.com [204.14.239.210]) by maple.anode.ca (Postfix) with ESMTPSA id 575FB6A3A; Mon, 17 Dec 2012 17:17:26 +0000 (UTC)
Subject: Re: Gen-ART LC review of draft-ietf-appsawg-json-patch-08
From: "Paul C. Bryan" <pbryan@anode.ca>
To: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net>
References: <023301cddb5f$73eb02d0$5bc10870$@gmail.com> <CA1BECA0-5084-4833-8EA8-EC507C7913E8@mnot.net>
Content-Type: multipart/alternative; boundary="=-vVdoXRaiQCXJBx99gYas"
Date: Mon, 17 Dec 2012 09:17:19 -0800
Message-ID: <1355764639.3017.8.camel@pbryan-wsl.internal.salesforce.com>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
X-Mailman-Approved-At: Tue, 18 Dec 2012 09:08:50 -0800
Cc: draft-ietf-appsawg-json-patch.all@tools.ietf.org, 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, 17 Dec 2012 17:17:29 -0000

--=-vVdoXRaiQCXJBx99gYas
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit

Incidentally, early (draft-pbryan-json-patch-*) drafts were aligned with
JSON; later feedback when adopted by the IETF APPSAWG changed it to
binary (starting in draft-ietf-appsawg-json-patch-00). The grounds for
this was a consensus that the JSON draft was wrong to have made it 8bit
for UTF-8.

Paul

On Mon, 2012-12-17 at 14:25 +1100, Mark Nottingham wrote:

> Both fixed in SVN; thanks for the review.
> 
> 
> On 16/12/2012, at 6:32 PM, Roni Even <ron.even.tlv@gmail.com> wrote:
> 
> > I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > 
> >  
> > 
> > Please resolve these comments along with any other Last Call comments you may receive.
> > 
> >  
> > Document: draft-ietf-appsawg-json-patch-08
> > Reviewer: Roni Even
> > Review Date:2012â€“12â€“16
> > IETF LC End Date: 2012â€“12â€“25
> > IESG Telechat date: 2013-1-10
> >  
> > Summary: This draft is almost  ready for publication.
> >  
> >  
> > Major issues:
> >  
> > Minor issues:
> > 1.       The document has as the intended status â€œInformationalâ€� while the last call says that the intended status is proposed standard?
> >  
> >  
> > Nits/editorial comments:
> > 
> > 	â€¢ In the IANA section the â€œEncoding considerations:  binaryâ€�. I noticed that RFC 4627 has a broader description:
> > â€œEncoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32
> > JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is written in UTF-8, JSON is 8bit compatible.  When JSON is written in UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.â€�
> >  
> >  
> > 
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 



--=-vVdoXRaiQCXJBx99gYas
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
Incidentally, early (draft-pbryan-json-patch-*) drafts were aligned with JSON; later feedback when adopted by the IETF APPSAWG changed it to binary (starting in draft-ietf-appsawg-json-patch-00). The grounds for this was a consensus that the JSON draft was wrong to have made it 8bit for UTF-8.<BR>
<BR>
Paul<BR>
<BR>
On Mon, 2012-12-17 at 14:25 +1100, Mark Nottingham wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Both fixed in SVN; thanks for the review.


On 16/12/2012, at 6:32 PM, Roni Even &lt;<A HREF="mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</A>&gt; wrote:

&gt; I am the assigned Gen-ART reviewer for this draft. For background on Gen-ART, please see the FAQ at &lt;<A HREF="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</A>&gt;.
&gt; 
&gt;  
&gt; 
&gt; Please resolve these comments along with any other Last Call comments you may receive.
&gt; 
&gt;  
&gt; Document: draft-ietf-appsawg-json-patch-08
&gt; Reviewer: Roni Even
&gt; Review Date:2012&#8211;12&#8211;16
&gt; IETF LC End Date: 2012&#8211;12&#8211;25
&gt; IESG Telechat date: 2013-1-10
&gt;  
&gt; Summary: This draft is almost  ready for publication.
&gt;  
&gt;  
&gt; Major issues:
&gt;  
&gt; Minor issues:
&gt; 1.       The document has as the intended status &#8220;Informational&#8221; while the last call says that the intended status is proposed standard?
&gt;  
&gt;  
&gt; Nits/editorial comments:
&gt; 
&gt; 	&#8226; In the IANA section the &#8220;Encoding considerations:  binary&#8221;. I noticed that RFC 4627 has a broader description:
&gt; &#8220;Encoding considerations: 8bit if UTF-8; binary if UTF-16 or UTF-32
&gt; JSON may be represented using UTF-8, UTF-16, or UTF-32.  When JSON is written in UTF-8, JSON is 8bit compatible.  When JSON is written in UTF-16 or UTF-32, the binary content-transfer-encoding   must be used.&#8221;
&gt;  
&gt;  
&gt; 

--
Mark Nottingham   <A HREF="http://www.mnot.net/">http://www.mnot.net/</A>



</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>

--=-vVdoXRaiQCXJBx99gYas--


From James.H.Manger@team.telstra.com  Mon Dec 17 21:12:55 2012
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D6E1F0CE4; Mon, 17 Dec 2012 21:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.882
X-Spam-Level: 
X-Spam-Status: No, score=-0.882 tagged_above=-999 required=5 tests=[AWL=0.019,  BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HD0GaIU49X0C; Mon, 17 Dec 2012 21:12:55 -0800 (PST)
Received: from ipxcno.tcif.telstra.com.au (ipxcno.tcif.telstra.com.au [203.35.82.208]) by ietfa.amsl.com (Postfix) with ESMTP id A8D2A1F0CE3; Mon, 17 Dec 2012 21:12:53 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,307,1355058000"; d="scan'208";a="106798582"
Received: from unknown (HELO ipcani.tcif.telstra.com.au) ([10.97.216.200]) by ipocni.tcif.telstra.com.au with ESMTP; 18 Dec 2012 16:12:50 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6929"; a="52493278"
Received: from wsmsg3757.srv.dir.telstra.com ([172.49.40.85]) by ipcani.tcif.telstra.com.au with ESMTP; 18 Dec 2012 16:12:51 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3757.srv.dir.telstra.com ([172.49.40.85]) with mapi; Tue, 18 Dec 2012 16:12:51 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Robert Sayre <sayrer@gmail.com>, James M Snell <jasnell@gmail.com>
Date: Tue, 18 Dec 2012 16:12:49 +1100
Subject: RE: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
Thread-Topic: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
Thread-Index: Ac3c0aLlBYpU3oEaTmCM88zjVoe+NwAAM0Nw
Message-ID: <255B9BB34FB7D647A506DC292726F6E1150408948F@WSMSG3153V.srv.dir.telstra.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com> <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com> <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com>
In-Reply-To: <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 18 Dec 2012 09:08:50 -0800
Cc: Mark Nottingham <mnot@mnot.net>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Dec 2012 05:12:55 -0000

SWYgd2Ugd2VyZSBzdGFydGluZyBmcm9tIHNjcmF0Y2ggYW5kIGRlZmluaW5nIEpTT04gUG9pbnRl
ciBhZ2FpbiBJIHdvdWxkIGFyZ3VlIGZvciBkaXN0aW5ndWlzaGluZyBhcnJheSBpbmRpY2VzIGFu
ZCBvYmplY3QgbmFtZXMgaW4gdGhlIHN5bnRheC4gRm9yIGluc3RhbmNlLCBwcmVmaXggYW4gb2Jq
ZWN0IG5hbWUgd2l0aCAiLyIgYW5kIGFuIGFycmF5IGluZGV4IHdpdGggIjoiLg0KDQogICBqc29u
LXBvaW50ZXIgPSAqc2VnbWVudA0KICAgc2VnbWVudCA9ICIvIiBuYW1lICAvICAiOiIgaW5kZXgN
CiAgIG5hbWUgPSAqKCB1bmVzY2FwZWQgLyBlc2NhcGVkICkNCiAgIHVuZXNjYXBlZCA9ICV4MDAt
MkUgLyAleDMwLTM5IC8gJXgzQi03RCAvICV4N0YtMTBGRkZGDQogICBlc2NhcGVkID0gIn4iICgg
IjAiIC8gIjEiIC8gIjIiICkNCiAgIGluZGV4ID0gIjAiIC8gJXgzMS0zOSAqKCV4MzAtMzkpIC8g
Ii0iDQoNCjEuIEl0IG1ha2VzIHBhcnNpbmcgbWFyZ2luYWxseSBoYXJkZXI6IHlvdSBjYW5ub3Qg
anVzdCBzcGxpdCBvbiAiLyIgYW5kIHVuZXNjYXBlIGVhY2ggc2VnbWVudC4NCjIuIEl0IGRvZXNu
J3QgbWFrZSBtdWNoIGRpZmZlcmVuY2UgZm9yIHNlbGVjdGluZyBhIHZhbHVlIGZyb20gc29tZSBK
U09OLCBvciBmb3IgZmluZGluZyBhIHNwb3QgdG8gaW5zZXJ0IGEgbmV3IHZhbHVlLg0KMy4gSXQg
d291bGQgYWxsb3cgeW91IHRvIGF1dG9tYXRpY2FsbHkgY3JlYXRlIG9iamVjdCAqb3IgYXJyYXkq
IGFuY2VzdG9ycyB3aGVuIHNldHRpbmcgYSBuZXcgdmFsdWUgKGVnIGFkZGluZyAyMyBhdCAvYTow
L2I6MCB0byB7fSBjb3VsZCBnaXZlIHsiYSI6W3siYiI6WzIzXX1dfSkuDQo0LiBJdCBtaWdodCBl
bmNvdXJhZ2UgYmV0dGVyIHZhbGlkYXRpb24gb2YgcG9pbnRlcnMsIGJ1dCB0aGF0IGlzIHByb2Jh
Ymx5IHdpc2hmdWwgdGhpbmtpbmcuDQoNCkJ1dCBKU09OIFBvaW50ZXIgZHJhZnRzIGhhdmUgdXNl
ZCB0aGUgL3tuYW1lfGluZGV4fSBmb3JtYXQgZm9yIGEgeWVhci4gVGhlcmUgYXJlIGEgYnVuY2gg
b2YgaW1wbGVtZW50YXRpb25zLiBUaGUgZGlmZmVyZW5jZSBpcyBtaW5vciBpbiBtb3N0IGNpcmN1
bXN0YW5jZXMuIFNvIHdoaWxlIEkgd291bGQgYmUgaGFwcHkgdG8gY2hhbmdlLCBJIGFtIGFsc28g
Y29tZm9ydGFibGUgc3RheWluZyB3aXRoIHRoZSBjdXJyZW50IHBvaW50ZXIgc3ludGF4Lg0KDQoN
Cj4gVGhlcmUncyBubyBnb29kIHJlYXNvbiBmb3IgaXQgdG8gYmUgdGhhdCB3YXksIGlzIHRoZXJl
Pw0KDQpJIGRvbid0IHRoaW5rIHNvLg0KIA0KLS0NCkphbWVzIE1hbmdlcg0K

From ben@nostrum.com  Tue Dec 18 12:14:48 2012
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 ACB7521F86D6; Tue, 18 Dec 2012 12:14:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpf4p2m+Gs-U; Tue, 18 Dec 2012 12:14:48 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2764B21F85D1; Tue, 18 Dec 2012 12:14:47 -0800 (PST)
Received: from [10.0.1.14] (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 qBIKEk7J031269 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Dec 2012 14:14:47 -0600 (CST) (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-ietf-karp-routing-tcp-analysis-06
Date: Tue, 18 Dec 2012 14:14:49 -0600
Message-Id: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com>
To: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <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: Tue, 18 Dec 2012 20:14:48 -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-karp-routing-tcp-analysis-07
Reviewer: Ben Campbell
Review Date: 2012-12-18
IESG Telechat date: 2012-12-20

Summary: Ready for publication as an informational RFC. There are still =
a couple of nits that might be worth consideration prior to final =
publication.

Note: This review is incremental to my review of version 05 at last =
call. All of my comments in that review have been resolved except as =
described in this message.

** Major issues:

None

** Minor issues:

None

** Nits/editorial comments:

-- The 2119 paragraph was removed, but there's still an orphaned 2119 =
entry in the informational reference section.

-- There's a new IANA considerations section. However, I suggest it =
contain a full sentence to the effect of "This document makes no =
requests of IANA" rather than simply "None".  (OTOH, this may get =
removed before final publication anyway...)



From nick@inex.ie  Tue Dec 18 14:12:49 2012
Return-Path: <nick@inex.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 0187821F8602; Tue, 18 Dec 2012 14:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_73=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d86HkjU-5MDq; Tue, 18 Dec 2012 14:12:48 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id A810921F84FD; Tue, 18 Dec 2012 14:12:46 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:5ca5:acc:abce:62e4]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBIMB0jY027671 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 18 Dec 2012 22:11:05 GMT (envelope-from nick@inex.ie)
Message-ID: <50D0EA56.3050308@inex.ie>
Date: Tue, 18 Dec 2012 22:12:38 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com>
In-Reply-To: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <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: Tue, 18 Dec 2012 22:12:49 -0000

On 18/12/2012 20:14, Ben Campbell wrote:
> ** Nits/editorial comments:
>
> -- The 2119 paragraph was removed, but there's still an orphaned 2119 entry in the informational reference section.

I'm not sure that this was a good idea.  There are a lot of "has to"s in
this text, and it's not clear to me whether they are phrased like that as a
way of getting around 2119, or what's going on.  Whatever the reason, "has
to" sounds very informal and probably not suitable for a document like
this.  Could we have some clarification as to why "has to" doesn't mean
"MUST" (or even "SHOULD").

--

-   protocol stack from CPU-utilization based attacks.TCP Robustness
+   protocol stack from CPU-utilization based attacks. TCP Robustness

--

I have a general issue with the statement "TCP MD5 [RFC2385] has been
obsoleted by TCP-AO [RFC5925]."  At this time, I'm not aware of any live
TCP-AO implementations.  So while I understand that md5 is effectively
obsolete from the specification point of view, from the point of view of
operational reality it's still the only show in town (no-one uses ipsec for
this).

Secondly, as a general comment about the TCP MD5 option, no-one that I know
uses it as a serious security mechanism, but instead as a means of putting
the equivalent of a padlock on the barn door.  This does two things: 1. it
stops bgp sessions from being accidentally re-used (e.g. at IXPs or on
commercial providers who are re-using access ports), and 2. it simply
raises the bar in terms of difficulty.  If your barnyard door has a
padlock, and the one beside doesn't, the average lazy human being will
attempt to poke at the one which doesn't.

>From an operational view, i would generally see the difference between
tcp/md5 and tcp/sha1 (via tcp-ao) as being similar to the difference
between a 5 pin and a 7 pin barrel lock.  Both look like a lock on the
outside, and the thief is probably going to smash a window to get in
anyway, or look for the key which the owners left under the mat.

--

There is a second operational issue which may merit mention here, namely
the issue of ensuring that whatever session layer authentication is
implemented on an actual network device, that it doesn't create more
problems than it solves.  Specifically, if session layer authentication is
pushed too far down the protocol stack, cryptographic authentication can
occur before other basic checks which might be a whole pile less CPU
intensive.  There was a scare about this several years ago when it turned
out that a well-known vendor had implemented tcp md5 checksumming before
more basic tcp session checks (e.g. seq numbers, ttl, etc).  In the event,
this turned out to be a red herring because md5 is sufficiently gentle on
the CPU that it didn't make much difference in reality.

However, there is cryptographic value in using more computationally
intensive hashing algorithms, and if routers (which often have relatively
slow general CPUs or route-processor CPUs) were to get trashed with a large
flood of packets which were signed with a cpu-intensive hashing algorithm,
and if the checksum were to be implemented in the wrong place in the TCP
stack, then this could become an actual problem.

I don't know whether these things should be noted in the draft.

--

It may be useful to consider whether to acknowledge the existence of rfc
6192 in the context of providing a link to what other steps might be useful
to secure routers.

--

>    pairs of routers when using TCP MD5.  It is well known that the
>    longer the same key is used, the greater the chance that it can be
>    guessed or exposed

I'm split between {{cn}} and [[Wikipedia:OBVIOUS]].  Hmmm, life's little
decisions.

--

>    Routers lack comprehensive key management and keys derived from it
>    that they can use to authenticate data.

clumsy wording (and grammatically incorrect).

--

>    Authentication, tamper protection, and encryption all require the use

should that second comma be dropped?  Not sure what the ietf style dictates.

--

>    Authentication, tamper protection, and encryption all require the use
>    of keys by sender and receiver.  An automated KMP therefore has to
>    include a way to distribute MKT between two end points with little or
>    no administration overhead.  It has to cover automatic key rollover.

"has to" has to become "MUST", shouldn't it?

Also, the third sentence is a semantic repeat of the second - and much
easier to understand, too.

--

-    that, where PCEs are discovered and not configured, the PCC cannot
+    that where PCEs are discovered and not configured, the PCC cannot

--

-   [draft-zheng-mpls-ldp-hello-crypto-auth-04] suggest a new
+   [draft-zheng-mpls-ldp-hello-crypto-auth-04] suggests a new

--

>             An LSR can reduce the threat of spoofed Extended Hellos by
>    filtering them and accepting Hellos from sources permitted by an
>    access lists.

"permitted by an access list".

--

>  However, performing the filtering using access lists
>    requires LSR resource, and the LSR is still vulnerable to the IP
>    source address spoofing.

This is a little clumsy.  Maybe rephrase as: "However, filtering with
access lists requires LSR resources, and the LSR may still be vulnerable to
IP source address spoofing."

"may" rather than is.  This will depend on the iACL policy of the network.

--

> Spoofed Hello messages are observed and reported as real
>    problem in production networks.

s/problem/problems/

{{cn}}

--

>    The Message Authentication Codes (MACs) used by TCP MD5 option, is
>    considered too weak

oops, grammar.

--

> Cryptographic research suggests that both these
>    MAC algorithms defined are fairly secure.

Today's "fairly secure" algorithms are tomorrow's swiss cheese:

> http://www.eetimes.com/electronics-news/4051745/Chinese-researchers-compromise-SHA-1-hashing-algorithm

I would explicitly avoid the use of ".* secure", and if the authors feel
the need to make any statement about them, that it should be prefixed by
woolly, hand-wavey, get-out-of-jail-free phrases, e.g. "at the time of
authorship, there are no publicly known attacks on this algorithm which
reduce the strength to complexity of less than 1 in X", or however
crypto-heads like to phrase that sort of thing.  Right now, that phrase is
headed towards algorithmic oblivion.

--

> LDP [RFC5036] does not provide any security
>    mechanisms for use with Hello messages except for some configuration
>    which may help protect against bogus discovery events.  These
>    configurations include directly connected links and interfaces.

suggest rewording:

LDP [RFC5036] does not provide any security mechanisms for use with Hello
messages, although operational workarounds may be implemented such as
using directly interfaces.

--

There are possibly more nits in there - I haven't exhaustively gone through
all the text, but it needs a good shake-down by a style editor.

Otherwise I like this draft and think it has merit as a general
informational overview.

Nick


From jmh@joelhalpern.com  Tue Dec 18 14:26:20 2012
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 0783B21E8054; Tue, 18 Dec 2012 14:26:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.888
X-Spam-Level: 
X-Spam-Status: No, score=-101.888 tagged_above=-999 required=5 tests=[AWL=-0.222, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_73=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2TxxUC06rYG9; Tue, 18 Dec 2012 14:26:19 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1F93C21E8039; Tue, 18 Dec 2012 14:26:19 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 26666A397E; Tue, 18 Dec 2012 14:26:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 56E021C0524; Tue, 18 Dec 2012 14:26:17 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-81.clppva.east.verizon.net [70.106.135.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id ECC1D1C005A; Tue, 18 Dec 2012 14:26:15 -0800 (PST)
Message-ID: <50D0ED83.3090700@joelhalpern.com>
Date: Tue, 18 Dec 2012 17:26:11 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie>
In-Reply-To: <50D0EA56.3050308@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "karp@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: Tue, 18 Dec 2012 22:26:20 -0000

Nick, I appreciate that you have read this document and commented.

Two general questions:
1) Can you be more specific about where you see unclear language usage? 
  It is hard to fix a general coment.

2) A number of your comments seem to be about general router security. 
Many of them would see far more appicable to RFC 6518.  This document is 
just about changes to protect TCP sessions (yes, what we are concerned 
about are the TCP sessions used by routers.)  Can you take a look at 
your comments, and tell us which ones are applicable to this document, 
and which ones should be held for when the community is ready to revise 
RFC 6518?

Thank you,
Joel

On 12/18/2012 5:12 PM, Nick Hilliard wrote:
> On 18/12/2012 20:14, Ben Campbell wrote:
>> ** Nits/editorial comments:
>>
>> -- The 2119 paragraph was removed, but there's still an orphaned 2119 entry in the informational reference section.
>
> I'm not sure that this was a good idea.  There are a lot of "has to"s in
> this text, and it's not clear to me whether they are phrased like that as a
> way of getting around 2119, or what's going on.  Whatever the reason, "has
> to" sounds very informal and probably not suitable for a document like
> this.  Could we have some clarification as to why "has to" doesn't mean
> "MUST" (or even "SHOULD").
>
> --
>
> -   protocol stack from CPU-utilization based attacks.TCP Robustness
> +   protocol stack from CPU-utilization based attacks. TCP Robustness
>
> --
>
> I have a general issue with the statement "TCP MD5 [RFC2385] has been
> obsoleted by TCP-AO [RFC5925]."  At this time, I'm not aware of any live
> TCP-AO implementations.  So while I understand that md5 is effectively
> obsolete from the specification point of view, from the point of view of
> operational reality it's still the only show in town (no-one uses ipsec for
> this).
>
> Secondly, as a general comment about the TCP MD5 option, no-one that I know
> uses it as a serious security mechanism, but instead as a means of putting
> the equivalent of a padlock on the barn door.  This does two things: 1. it
> stops bgp sessions from being accidentally re-used (e.g. at IXPs or on
> commercial providers who are re-using access ports), and 2. it simply
> raises the bar in terms of difficulty.  If your barnyard door has a
> padlock, and the one beside doesn't, the average lazy human being will
> attempt to poke at the one which doesn't.
>
>>From an operational view, i would generally see the difference between
> tcp/md5 and tcp/sha1 (via tcp-ao) as being similar to the difference
> between a 5 pin and a 7 pin barrel lock.  Both look like a lock on the
> outside, and the thief is probably going to smash a window to get in
> anyway, or look for the key which the owners left under the mat.
>
> --
>
> There is a second operational issue which may merit mention here, namely
> the issue of ensuring that whatever session layer authentication is
> implemented on an actual network device, that it doesn't create more
> problems than it solves.  Specifically, if session layer authentication is
> pushed too far down the protocol stack, cryptographic authentication can
> occur before other basic checks which might be a whole pile less CPU
> intensive.  There was a scare about this several years ago when it turned
> out that a well-known vendor had implemented tcp md5 checksumming before
> more basic tcp session checks (e.g. seq numbers, ttl, etc).  In the event,
> this turned out to be a red herring because md5 is sufficiently gentle on
> the CPU that it didn't make much difference in reality.
>
> However, there is cryptographic value in using more computationally
> intensive hashing algorithms, and if routers (which often have relatively
> slow general CPUs or route-processor CPUs) were to get trashed with a large
> flood of packets which were signed with a cpu-intensive hashing algorithm,
> and if the checksum were to be implemented in the wrong place in the TCP
> stack, then this could become an actual problem.
>
> I don't know whether these things should be noted in the draft.
>
> --
>
> It may be useful to consider whether to acknowledge the existence of rfc
> 6192 in the context of providing a link to what other steps might be useful
> to secure routers.
>
> --
>
>>     pairs of routers when using TCP MD5.  It is well known that the
>>     longer the same key is used, the greater the chance that it can be
>>     guessed or exposed
>
> I'm split between {{cn}} and [[Wikipedia:OBVIOUS]].  Hmmm, life's little
> decisions.
>
> --
>
>>     Routers lack comprehensive key management and keys derived from it
>>     that they can use to authenticate data.
>
> clumsy wording (and grammatically incorrect).
>
> --
>
>>     Authentication, tamper protection, and encryption all require the use
>
> should that second comma be dropped?  Not sure what the ietf style dictates.
>
> --
>
>>     Authentication, tamper protection, and encryption all require the use
>>     of keys by sender and receiver.  An automated KMP therefore has to
>>     include a way to distribute MKT between two end points with little or
>>     no administration overhead.  It has to cover automatic key rollover.
>
> "has to" has to become "MUST", shouldn't it?
>
> Also, the third sentence is a semantic repeat of the second - and much
> easier to understand, too.
>
> --
>
> -    that, where PCEs are discovered and not configured, the PCC cannot
> +    that where PCEs are discovered and not configured, the PCC cannot
>
> --
>
> -   [draft-zheng-mpls-ldp-hello-crypto-auth-04] suggest a new
> +   [draft-zheng-mpls-ldp-hello-crypto-auth-04] suggests a new
>
> --
>
>>              An LSR can reduce the threat of spoofed Extended Hellos by
>>     filtering them and accepting Hellos from sources permitted by an
>>     access lists.
>
> "permitted by an access list".
>
> --
>
>>   However, performing the filtering using access lists
>>     requires LSR resource, and the LSR is still vulnerable to the IP
>>     source address spoofing.
>
> This is a little clumsy.  Maybe rephrase as: "However, filtering with
> access lists requires LSR resources, and the LSR may still be vulnerable to
> IP source address spoofing."
>
> "may" rather than is.  This will depend on the iACL policy of the network.
>
> --
>
>> Spoofed Hello messages are observed and reported as real
>>     problem in production networks.
>
> s/problem/problems/
>
> {{cn}}
>
> --
>
>>     The Message Authentication Codes (MACs) used by TCP MD5 option, is
>>     considered too weak
>
> oops, grammar.
>
> --
>
>> Cryptographic research suggests that both these
>>     MAC algorithms defined are fairly secure.
>
> Today's "fairly secure" algorithms are tomorrow's swiss cheese:
>
>> http://www.eetimes.com/electronics-news/4051745/Chinese-researchers-compromise-SHA-1-hashing-algorithm
>
> I would explicitly avoid the use of ".* secure", and if the authors feel
> the need to make any statement about them, that it should be prefixed by
> woolly, hand-wavey, get-out-of-jail-free phrases, e.g. "at the time of
> authorship, there are no publicly known attacks on this algorithm which
> reduce the strength to complexity of less than 1 in X", or however
> crypto-heads like to phrase that sort of thing.  Right now, that phrase is
> headed towards algorithmic oblivion.
>
> --
>
>> LDP [RFC5036] does not provide any security
>>     mechanisms for use with Hello messages except for some configuration
>>     which may help protect against bogus discovery events.  These
>>     configurations include directly connected links and interfaces.
>
> suggest rewording:
>
> LDP [RFC5036] does not provide any security mechanisms for use with Hello
> messages, although operational workarounds may be implemented such as
> using directly interfaces.
>
> --
>
> There are possibly more nits in there - I haven't exhaustively gone through
> all the text, but it needs a good shake-down by a style editor.
>
> Otherwise I like this draft and think it has merit as a general
> informational overview.
>
> Nick
>
>

From ben@nostrum.com  Tue Dec 18 14:50:13 2012
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 39C0021E8047; Tue, 18 Dec 2012 14:50:13 -0800 (PST)
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, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y2oNf1kfmyj3; Tue, 18 Dec 2012 14:50:12 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id F0EE021E8045; Tue, 18 Dec 2012 14:50:11 -0800 (PST)
Received: from [10.0.1.14] (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 qBIMo6lw048047 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 18 Dec 2012 16:50:08 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <50D0EA56.3050308@inex.ie>
Date: Tue, 18 Dec 2012 16:50:08 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <566F175C-1DD4-414A-AB7D-27BF33156694@nostrum.com>
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <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: Tue, 18 Dec 2012 22:50:13 -0000

I think Nick's email was a review of the document in general, rather =
than commentary on my review in particular. But since it was addressed =
to me, I do have one comment in response:

On Dec 18, 2012, at 4:12 PM, Nick Hilliard <nick@inex.ie> wrote:

> On 18/12/2012 20:14, Ben Campbell wrote:
>> ** Nits/editorial comments:
>>=20
>> -- The 2119 paragraph was removed, but there's still an orphaned 2119 =
entry in the informational reference section.
>=20
> I'm not sure that this was a good idea.  There are a lot of "has to"s =
in
> this text, and it's not clear to me whether they are phrased like that =
as a
> way of getting around 2119, or what's going on.  Whatever the reason, =
"has
> to" sounds very informal and probably not suitable for a document like
> this.  Could we have some clarification as to why "has to" doesn't =
mean
> "MUST" (or even "SHOULD").

I don't think so. This draft does not establish a standard, or define a =
protocol. While I don't speak for the authors, I don't think it's =
intended to make normative statements about anything. The language is =
descriptive, not prescriptive.

(I agree "has to" is an awkward substitute for the non-normative "must". =
I agree that "must" should generally be avoided when there can be =
confusion about the normativeness of a statement. I'm not sure that's =
the case here, since the whole doc is non-normative. And I think we =
could find better language even when the confusion is possible.)




From mnot@mnot.net  Tue Dec 18 19:19:12 2012
Return-Path: <mnot@mnot.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 7328411E8099 for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 19:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.772
X-Spam-Level: 
X-Spam-Status: No, score=-103.772 tagged_above=-999 required=5 tests=[AWL=-1.173, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACdttSN77-fj for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 19:19:11 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 30BE711E8097 for <ietf@ietf.org>; Tue, 18 Dec 2012 19:19:10 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.33.170]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 81403509B7; Tue, 18 Dec 2012 22:19:09 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Last Call: <draft-ietf-appsawg-json-patch-08.txt> (JSON Patch) to Proposed Standard
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p1pq2cleqx.fsf@d72933.na.sas.com>
Date: Wed, 19 Dec 2012 14:19:06 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE2A982D-4897-4AE2-B5DE-59B168750290@mnot.net>
References: <p1pq2cleqx.fsf@d72933.na.sas.com>
To: David J. Biesack <David.Biesack@sas.com>
X-Mailer: Apple Mail (2.1499)
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, 19 Dec 2012 03:19:12 -0000

In SVN; thanks.


On 15/12/2012, at 4:34 AM, David J. Biesack <David.Biesack@sas.com> =
wrote:

>=20
> "4.4.  move" states
>=20
>   The target location MUST NOT be part of the location defined by
>   "from"; i.e., a location cannot be moved into one of its children.
>=20
> This constraint is backwards. I.e. to disallow moving into a child,=20
>=20
> { "op": "move", "from": "/a/b/c", "path": "/a/b/c/d" }
>=20
> this should read:
>=20
>   The "from" location MUST NOT be a proper prefix of the "path" =
location;
>   i.e., a location cannot be moved into one of its children.
>=20
> I suggest using "proper prefix" instead of just "part of". For =
example,
> "/a/b/c" is "part of" "q/a/b/c" but such a move should be allowed
> because it is not a proper prefix.
>=20
> As currently stated, moving a value UP would be disallowed. Below, the =
target location is part of the "from" :
>=20
> { "op": "move", "from": "/a/b/c/d", "path": "/a/b/c" }
>=20
> --=20
> David J. Biesack | Principal API Architect, SAS | @davidbiesack | =
919-531-7771 | www.sas.com
>=20

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




From d3e3e3@gmail.com  Wed Dec 19 07:54:43 2012
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 5BB1621F8598; Wed, 19 Dec 2012 07:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.44
X-Spam-Level: 
X-Spam-Status: No, score=-103.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00YYhvGhbUGr; Wed, 19 Dec 2012 07:54:42 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by ietfa.amsl.com (Postfix) with ESMTP id 5DDDB21F857D; Wed, 19 Dec 2012 07:54:42 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id k10so3018730iea.15 for <multiple recipients>; Wed, 19 Dec 2012 07:54:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=XaZaCyNIZCIjMuhUPFPtT4V3K9BpxqAT/aw4mxq2Yxg=; b=RbL9qvcSYb+e4tddO68c6/MyhRM5M2n5kDiYt9nRO+cm+UlDksz7kChxmgVYxqUBny ksvhsrXBRPJlh/vj6gSNiD/+Nra6VseURThMdyK034ATICzifx3RF1xsUPxWCnMuF4KF zIpvk39Y0mT98BwOSWQkvDx+CKejsSRmSm7u4smSvyNy/O5EWF3cc/vzp2oJm+i8twVN pQCrzF9cZ2oWCawbLkuaqXRWPypjaw4PbSic32oIVemjszp9vdYJ0J/WbXCR2Vr2RQW0 c+aknY7NS9NHPNWQUZ0UoBORd94ZGSZlWm7KTq+93ZyB+f5WHSoC2KOsJ7k+pqTWOxf+ 8kQQ==
Received: by 10.43.124.130 with SMTP id go2mr6325918icc.8.1355932481799; Wed, 19 Dec 2012 07:54:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.28.209 with HTTP; Wed, 19 Dec 2012 07:54:21 -0800 (PST)
In-Reply-To: <201212120043.qBC0hjW7067663@skyhighway.com>
References: <20121211145829.3754.44253.idtracker@ietfa.amsl.com> <201212120043.qBC0hjW7067663@skyhighway.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 19 Dec 2012 10:54:21 -0500
Message-ID: <CAF4+nEF4ijXKn+eV7SJCagg-5bgP0ehT2hXKc54s1EUatZEkeA@mail.gmail.com>
Subject: Re: [trill] Last Call: <draft-ietf-trill-oam-req-04.txt> (Requirements for Operations, Administration and Maintenance (OAM) in TRILL (Transparent Interconnection of Lots of Links)) to Informational RFC
To: gayle noble <windy_1@skyhighway.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@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, 19 Dec 2012 15:54:43 -0000

Hi Gayle,

On Tue, Dec 11, 2012 at 7:43 PM, gayle noble <windy_1@skyhighway.com> wrote:
> Very well written!! No spelling errors! No grammatical errors! Only one
> sentence, in my opinion,  could be rephrased for clarity
> 4.1. Data Plane
>  RBridges MUST have the ability to identify OAM frames destined for them or
> which require processing by the OAM plane from normal data frames.
> [Might be clearer if it was [RBridges MUST have the ability to identify OAM
> frames from normal data frames when the OAM frames are destined for them or
> require processing by the OAM plane.]]

Thanks for the praise!
I think that your suggested wording could be improved by replacing the
word "identify" with the word "distinguish".

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

> gayle

From housley@vigilsec.com  Wed Dec 19 10:10:57 2012
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 CBEDD21F882E for <ietf@ietfa.amsl.com>; Wed, 19 Dec 2012 10:10:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.657
X-Spam-Level: 
X-Spam-Status: No, score=-101.657 tagged_above=-999 required=5 tests=[AWL=-0.917, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YcgfpDluK6Nz for <ietf@ietfa.amsl.com>; Wed, 19 Dec 2012 10:10:57 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E0ED321F87F4 for <ietf@ietf.org>; Wed, 19 Dec 2012 10:10:56 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 8FD2B9A4002 for <ietf@ietf.org>; Wed, 19 Dec 2012 13:10:56 -0500 (EST)
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 BrhYGKJnkL42 for <ietf@ietf.org>; Wed, 19 Dec 2012 13:10:42 -0500 (EST)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4874C9A400D for <ietf@ietf.org>; Wed, 19 Dec 2012 13:10:55 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
Subject: Internet Hall of Fame Celebrates Internet Leaders: Second Annual Induction Ceremony Set for June 2013 in Istanbul, Turkey
Date: Wed, 19 Dec 2012 13:10:54 -0500
To: IETF <ietf@ietf.org>
Message-Id: <102489A7-1F1E-4D5E-ADDF-9D3E4C761F9F@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1085)
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: Wed, 19 Dec 2012 18:10:58 -0000

h=
ttp://www.internetsociety.org/news/internet-hall-fame-celebrates-internet-=
leaders-second-annual-induction-ceremony-set-june-2013

You may know someone that deserves to be nominated ...

Russ

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

Internet Hall of Fame Celebrates Internet Leaders: Second Annual =
Induction Ceremony Set for June 2013 in Istanbul, Turkey=20

Inductee Nominations Open January 11

[Washington, D.C. and Geneva, Switzerland] =96 Building on the historic =
foundation it established earlier this year, the Internet Hall of Fame =
will once again help make history in 2013 when it honors individuals who =
have been important to the Internet=92s open development and growth. The =
Internet Society today announced that nominations for the second annual =
awards will open on January 11, and the 2013 inductees will be announced =
and honored at a ceremony held June 26, 2013 in Istanbul, Turkey.=20

This year=92s Internet Hall of Fame will continue the important =
tradition of celebrating Internet visionaries, innovators, and leaders =
from around the world who have made significant contributions to the =
development and advancement of the open, global Internet.=20

This year=92s nomination process is open to the public and the =
nomination form will be available on the Internet Hall of Fame website, =
www.internethalloffame.org, starting January 11, 2013. Nominees are =
considered for induction into one of the three categories:=20

* Pioneers Circle: recognizing individuals instrumental in the early =
design and development of the Internet.

* Innovators: recognizing individuals who made outstanding =
technological, commercial, or policy advances and helped to expand the =
Internet=92s reach.

* Global Connectors: recognizing individuals who have made major =
contributions to the growth, connectivity, and use of the Internet, =
either on a global scale or within a specific region or community.

=93The Internet Hall of Fame recognizes the extraordinary people who =
have helped to shape the Internet into the most successful global =
platform for communication, social, and economic development ever seen,=94=
 said Internet Society President and CEO Lynn St. Amour. =93We look =
forward to the second year and recognizing individuals from across the =
world for their passions, innovations, and commitments to the Internet =
and its role in making their communities =96 and the world =96 a better =
place.=94

The inaugural Internet Hall of Fame inductees were announced in April =
2012 in Geneva, Switzerland, in conjunction with the Internet Society=92s =
20th anniversary celebration and Global INET event, which brought =
together Internet experts and enthusiasts to discuss the Internet=92s =
future. The Internet Hall of Fame will be held annually on a global =
rotation. The 2013 Internet Hall of Fame ceremony will be co-located =
with several other Internet Society regional events in Istanbul, Turkey, =
June 25-26, 2013.


From amorris@amsl.com  Wed Dec 19 12:55:16 2012
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 44E6D21F868E for <ietf@ietfa.amsl.com>; Wed, 19 Dec 2012 12:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VQZHES8zPnt9 for <ietf@ietfa.amsl.com>; Wed, 19 Dec 2012 12:55:15 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id D9DAE21F867B for <ietf@ietf.org>; Wed, 19 Dec 2012 12:55:15 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id C2EA812797E for <ietf@ietf.org>; Wed, 19 Dec 2012 12:55:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qg2iMHGw5JW3 for <ietf@ietf.org>; Wed, 19 Dec 2012 12:55:15 -0800 (PST)
Received: from [192.168.1.107] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c8a.amsl.com (Postfix) with ESMTPSA id 9415412796D for <ietf@ietf.org>; Wed, 19 Dec 2012 12:55:15 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Happy Holidays & Winter Break Notice
Date: Wed, 19 Dec 2012 12:54:49 -0800
Message-Id: <1CAC13D8-50DC-49BF-AAB3-B664BFE651B5@amsl.com>
To: ietf list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
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: Wed, 19 Dec 2012 20:55:16 -0000

Happy Holidays from the IETF Secretariat! Since we cannot send each and =
every one of you a holiday card, we opted to make a holiday video for =
your viewing enjoyment: =
http://www.youtube.com/watch?v=3D-YR-d3JHYec&feature=3Dyoutu.be

Please note that the AMS offices will be closed for holiday break from =
Dec 24 through Jan 1. However, we will be checking email for any urgent =
issues. =20

Thank you for a great 2012, and we look forward to working with you in =
the new year!

Regards,

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 ben@nostrum.com  Wed Dec 19 13:15:01 2012
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 0C04C21F85EE; Wed, 19 Dec 2012 13:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cvP2--umsxYW; Wed, 19 Dec 2012 13:15:00 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4885021F8578; Wed, 19 Dec 2012 13:15:00 -0800 (PST)
Received: from [172.20.10.2] (mobile-166-137-149-039.mycingular.net [166.137.149.39]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qBJLEwQO002499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 19 Dec 2012 15:14:59 -0600 (CST) (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-ietf-dhc-relay-id-suboption-11
Date: Wed, 19 Dec 2012 15:14:58 -0600
Message-Id: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com>
To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 166.137.149.39 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <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, 19 Dec 2012 21:15:01 -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-dhc-relay-id-suboption-11
Reviewer: Ben Campbell
Review Date: 2012-12-19
IETF LC End Date: 2013-01-07

Summary: This draft is basically ready for publication as a proposed =
standard. However, there is one comment from a prior review that I am =
not sure whether is resolved.

Major issues:

None

Minor issues:

-- In Sean Turner's 2009 review of version 07 of the document [ =
http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ], he =
made the following comment:

> In the security considerations it says look to RFC 3046 and
> RFC 4030 for security considerations and then says SHOULD use the =
relay
> agent authentication option from RFC 4030.  RFC 3046 is targeted at
> network infrastructures that are "trusted and secure" and RFC 4030
> allows the relay agent to be part of this trusted and secure network.
> If an implementation doesn't use the relay agent authentication =
option,
> then the relay agent can't be part of the "trusted and secure" =
network.
>  This makes me think that the relay agent authentication option from
> RFC 4030 ought to be a MUST not a SHOULD?

I can't tell from the resulting conversation if that comment is =
addressed in the current text. Additional text has been added, but the =
SHOULD remains. I'm willing to accept it has been addressed if the =
author's say so--I only mention it to make sure it didn't fall through a =
crack.

Nits/editorial comments:

-- section 5, last paragraph:

I suggest removing the scare quotes around "stability". If there are =
concerns about whether such stability is real, it would be better to say =
that directly.

-- informative references:

draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07





From conte@isoc.org  Wed Dec 19 14:04:26 2012
Return-Path: <conte@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 C946121F8577 for <ietf@ietfa.amsl.com>; Wed, 19 Dec 2012 14:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.265
X-Spam-Level: 
X-Spam-Status: No, score=-103.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hG6ut8WJoprb for <ietf@ietfa.amsl.com>; Wed, 19 Dec 2012 14:04:20 -0800 (PST)
Received: from smtp177.dfw.emailsrvr.com (smtp177.dfw.emailsrvr.com [67.192.241.177]) by ietfa.amsl.com (Postfix) with ESMTP id A001E21F8479 for <ietf@ietf.org>; Wed, 19 Dec 2012 14:04:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp7.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 267A2258470; Wed, 19 Dec 2012 17:04:20 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp7.relay.dfw1a.emailsrvr.com (Authenticated sender: conte-AT-isoc.org) with ESMTPSA id DC66E258467;  Wed, 19 Dec 2012 17:04:19 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Happy Holidays & Winter Break Notice
From: Steve Conte <conte@isoc.org>
In-Reply-To: <1CAC13D8-50DC-49BF-AAB3-B664BFE651B5@amsl.com>
Date: Wed, 19 Dec 2012 14:04:19 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <5B0CDE4D-35F1-44E3-91E8-83409289391A@isoc.org>
References: <1CAC13D8-50DC-49BF-AAB3-B664BFE651B5@amsl.com>
To: Alexa Morris <amorris@amsl.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf 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, 19 Dec 2012 22:04:26 -0000

Super Awesome!

Thanks AMS for everything that you do for the IETF!

Happy Holidays

Steve

On Dec 19, 2012, at 12:54 PM, Alexa Morris <amorris@amsl.com> wrote:

> Happy Holidays from the IETF Secretariat! Since we cannot send each =
and every one of you a holiday card, we opted to make a holiday video =
for your viewing enjoyment: =
http://www.youtube.com/watch?v=3D-YR-d3JHYec&feature=3Dyoutu.be
>=20
> Please note that the AMS offices will be closed for holiday break from =
Dec 24 through Jan 1. However, we will be checking email for any urgent =
issues. =20
>=20
> Thank you for a great 2012, and we look forward to working with you in =
the new year!
>=20
> Regards,
>=20
> Alexa
>=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
>=20
> Managed by Association Management Solutions (AMS)
> Forum Management, Meeting and Event Planning
> www.amsl.com <http://www.amsl.com/>
>=20

-----
Steve Conte
Internet Leadership Programmes
The Internet Society
conte@isoc.org





From nick@inex.ie  Wed Dec 19 14:26:35 2012
Return-Path: <nick@inex.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 0A09D21F8584; Wed, 19 Dec 2012 14:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3JeKCYuiK1A; Wed, 19 Dec 2012 14:26:34 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 46BE521F8530; Wed, 19 Dec 2012 14:26:33 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:41e8:aae1:8461:f339]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBJMOk7s039936 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 22:24:51 GMT (envelope-from nick@inex.ie)
Message-ID: <50D23F11.8060901@inex.ie>
Date: Wed, 19 Dec 2012 22:26:25 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <566F175C-1DD4-414A-AB7D-27BF33156694@nostrum.com>
In-Reply-To: <566F175C-1DD4-414A-AB7D-27BF33156694@nostrum.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "gen-art@ietf.org Review Team" <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, 19 Dec 2012 22:26:35 -0000

On 18/12/2012 22:50, Ben Campbell wrote:
> I think Nick's email was a review of the document in general, 

yes, sorry, it was.  I hit reply when I saw the subject line.

> I don't think so. This draft does not establish a standard, or define a
> protocol. While I don't speak for the authors, I don't think it's
> intended to make normative statements about anything. The language is
> descriptive, not prescriptive.

ok, noted.

> (I agree "has to" is an awkward substitute for the non-normative "must".
> I agree that "must" should generally be avoided when there can be
> confusion about the normativeness of a statement. I'm not sure that's
> the case here, since the whole doc is non-normative. And I think we
> could find better language even when the confusion is possible.)

"needs to"?  "ought to"?  It's all massively context dependent though.
What's needed are some words / phrases which are defined to have local
imperative scope only or else nonlocal informative "must" - but yeah it's
messy and generally will involve nontrivial wordsmithing to work around
what is meant.

Nick


From nick@inex.ie  Wed Dec 19 15:14:25 2012
Return-Path: <nick@inex.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 E85AA21F892A; Wed, 19 Dec 2012 15:14:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4laReO8tpOI; Wed, 19 Dec 2012 15:14:25 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id A16C721F88F1; Wed, 19 Dec 2012 15:14:23 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:41e8:aae1:8461:f339]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBJNCVHM040156 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 23:12:37 GMT (envelope-from nick@inex.ie)
Message-ID: <50D24A43.6050608@inex.ie>
Date: Wed, 19 Dec 2012 23:14:11 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <50D0ED83.3090700@joelhalpern.com>
In-Reply-To: <50D0ED83.3090700@joelhalpern.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "karp@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: Wed, 19 Dec 2012 23:14:26 -0000

On 18/12/2012 22:26, Joel M. Halpern wrote:
> Nick, I appreciate that you have read this document and commented.
> 
> Two general questions:
> 1) Can you be more specific about where you see unclear language usage?  It
> is hard to fix a general coment.

I was referring to the use of "has to", but the phrase only appears three
times so maybe it's not going to be a large amount of work to eradicate it.
 This might work:

s/has to/needs to/g

I overestimated to myself the number of times it appeared by flicking back
and forwards through the document when looking at it last night.

> 2) A number of your comments seem to be about general router security. Many
> of them would see far more appicable to RFC 6518.  This document is just
> about changes to protect TCP sessions (yes, what we are concerned about are
> the TCP sessions used by routers.)  Can you take a look at your comments,
> and tell us which ones are applicable to this document, and which ones
> should be held for when the community is ready to revise RFC 6518?

6518 looks like a roadmap to me.  I don't see any of these comments as
being especially relevant to that document.

There are 3 general suggestions and the rest of the issues are either style
or syntax editing issues, and I think they are all relevant to this
document.  These suggestions are:

1:

>> I have a general issue with the statement "TCP MD5 [RFC2385] has been
>> obsoleted by TCP-AO [RFC5925]."  At this time, I'm not aware of any live
>> TCP-AO implementations.  So while I understand that md5 is effectively
>> obsolete from the specification point of view, from the point of view of
>> operational reality it's still the only show in town (no-one uses ipsec for
>> this).

We don't have running code for the new protocol, but we have very wide
deployment for the older protocol.  So I question how appropriate it is to
make a statement on whether the new protocol has obsoleted the old one.
I'm not familiar enough with ietf nous to know whether this is relevant to
a document like this.  Wearing my operator hat, it looks a little odd,
that's all.

2:

>> There is a second operational issue which may merit mention here, namely
>> the issue of ensuring that whatever session layer authentication is
>> implemented on an actual network device, that it doesn't create more
>> problems than it solves.  Specifically, if session layer authentication is
>> pushed too far down the protocol stack, cryptographic authentication can
>> occur before other basic checks which might be a whole pile less CPU
>> intensive.  There was a scare about this several years ago when it turned
>> out that a well-known vendor had implemented tcp md5 checksumming before
>> more basic tcp session checks (e.g. seq numbers, ttl, etc).  In the event,
>> this turned out to be a red herring because md5 is sufficiently gentle on
>> the CPU that it didn't make much difference in reality.
>>
>> However, there is cryptographic value in using more computationally
>> intensive hashing algorithms, and if routers (which often have relatively
>> slow general CPUs or route-processor CPUs) were to get trashed with a large
>> flood of packets which were signed with a cpu-intensive hashing algorithm,
>> and if the checksum were to be implemented in the wrong place in the TCP
>> stack, then this could become an actual problem.

Whatever a router manufacturer does in terms of implementation, they need
to be careful when writing code to ensure that they don't accidentally open
up other attack vectors by implementing transport layer security badly.  It
almost happened once before, and this could have caused damage at the time
if we had had been using a computationally expensive algorithm like openbsd
bcrypt instead of md5.

3:

>> It may be useful to consider whether to acknowledge the existence of rfc
>> 6192 in the context of providing a link to what other steps might be useful
>> to secure routers.

What I'm suggesting here is a single sentence around the first paragraph in
section 2.1 to say that while it's outside the context of transport
security, there's more to protecting routers than cryptography - and then
provide a link to 6192 as an informative reference to someone who might be
interested in the more general area router security.

General router security is a large subject which is not particularly
pertinent to keying and authentication, but a random operator who happens
to read this ID when it's published might appreciate the pointer.

Nick


From nick@inex.ie  Wed Dec 19 15:21:04 2012
Return-Path: <nick@inex.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 72CA721F892A; Wed, 19 Dec 2012 15:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.54
X-Spam-Level: 
X-Spam-Status: No, score=-2.54 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ynRRuOmsL7dI; Wed, 19 Dec 2012 15:20:58 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 38D9221F8899; Wed, 19 Dec 2012 15:20:55 -0800 (PST)
X-Envelope-To: karp@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100:41e8:aae1:8461:f339]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id qBJNJ9VM040188 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 19 Dec 2012 23:19:15 GMT (envelope-from nick@inex.ie)
Message-ID: <50D24BD1.4070801@inex.ie>
Date: Wed, 19 Dec 2012 23:20:49 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Anantha Ramaiah <ananth@nttmcl.com>
Subject: Re: [karp] Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <50D0ED83.3090700@joelhalpern.com> <CAFZUbhenPyaDoknGafGd4SOXOUVo5VpbohjC8D5rB21iB0v1xQ@mail.gmail.com>
In-Reply-To: <CAFZUbhenPyaDoknGafGd4SOXOUVo5VpbohjC8D5rB21iB0v1xQ@mail.gmail.com>
X-Enigmail-Version: 1.4.6
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "karp@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: Wed, 19 Dec 2012 23:21:04 -0000

On 18/12/2012 23:15, Anantha Ramaiah wrote:
> Also TCP MD5 with periodic key rollover can make the life harder for TCP
> MD5 based collision attacks.

there is no facility in rfc 2385 for automatic key rollover, which means
that any key changes must be done manually.  I've come across gratuitous
key rollover happening exactly once in my career: namely where (as far as I
understand) a particular company had used the same MD5 key for all ebgp
peering sessions worldwide.  They eventually decided that this wasn't such
a good idea and subsequently changed keys whenever they changed routers /
bgp sessions / did port upgrades / etc.  Other than that, I've never come
across a case of someone wanting to proactively change a session key
because it seemed to be a good idea.  Just sayin'.

Nick

From jmh@joelhalpern.com  Thu Dec 20 06:17:02 2012
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 0F20C21F88C7; Thu, 20 Dec 2012 06:17:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.125
X-Spam-Level: 
X-Spam-Status: No, score=-102.125 tagged_above=-999 required=5 tests=[AWL=0.140, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X4XPro-O0F6X; Thu, 20 Dec 2012 06:17:01 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 579D621F84F8; Thu, 20 Dec 2012 06:17:01 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id B8ABCA3679; Thu, 20 Dec 2012 06:17:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 8D1551C2B48; Thu, 20 Dec 2012 06:17:00 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-135-81.clppva.east.verizon.net [70.106.135.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 499D31C07AC; Thu, 20 Dec 2012 06:16:59 -0800 (PST)
Message-ID: <50D31DD6.5080100@joelhalpern.com>
Date: Thu, 20 Dec 2012 09:16:54 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <50D0ED83.3090700@joelhalpern.com> <50D24A43.6050608@inex.ie>
In-Reply-To: <50D24A43.6050608@inex.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "karp@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: Thu, 20 Dec 2012 14:17:02 -0000

Thank you Nick.
With regard to the suggest text replacement of "has to" with "needs to", 
if you think that will help, lets go wit it (at then let the RFC Editor 
tell us if it doesn't work.)

With regard to obsoleting TCP-MD5, that is what the RFCs say.  The 
TCP-MD5 is obsoleted by the TCP-AO RFC.  Further, the security folks are 
quite adamant that we should be shifting our recommendations, and where 
possible our practice.  If there are not yep implementations, we need to 
be pushing folks harder to get them.

If I understand your next item properly, you are asking that we add a 
sentence about the fact that implementation of security mechanisms needs 
to be doe carefully, so as not to make things worse.  Seems easy to do 
and can't hurt, so we should do so.

And equally, noting that security is more than cryptography, and more 
than signatures, is probably sensible.

Authors, WG, can we live with these?  I would think so.

Yours,
Joel

On 12/19/2012 6:14 PM, Nick Hilliard wrote:
> On 18/12/2012 22:26, Joel M. Halpern wrote:
>> Nick, I appreciate that you have read this document and commented.
>>
>> Two general questions:
>> 1) Can you be more specific about where you see unclear language usage?  It
>> is hard to fix a general coment.
>
> I was referring to the use of "has to", but the phrase only appears three
> times so maybe it's not going to be a large amount of work to eradicate it.
>   This might work:
>
> s/has to/needs to/g
>
> I overestimated to myself the number of times it appeared by flicking back
> and forwards through the document when looking at it last night.
>
>> 2) A number of your comments seem to be about general router security. Many
>> of them would see far more appicable to RFC 6518.  This document is just
>> about changes to protect TCP sessions (yes, what we are concerned about are
>> the TCP sessions used by routers.)  Can you take a look at your comments,
>> and tell us which ones are applicable to this document, and which ones
>> should be held for when the community is ready to revise RFC 6518?
>
> 6518 looks like a roadmap to me.  I don't see any of these comments as
> being especially relevant to that document.
>
> There are 3 general suggestions and the rest of the issues are either style
> or syntax editing issues, and I think they are all relevant to this
> document.  These suggestions are:
>
> 1:
>
>>> I have a general issue with the statement "TCP MD5 [RFC2385] has been
>>> obsoleted by TCP-AO [RFC5925]."  At this time, I'm not aware of any live
>>> TCP-AO implementations.  So while I understand that md5 is effectively
>>> obsolete from the specification point of view, from the point of view of
>>> operational reality it's still the only show in town (no-one uses ipsec for
>>> this).
>
> We don't have running code for the new protocol, but we have very wide
> deployment for the older protocol.  So I question how appropriate it is to
> make a statement on whether the new protocol has obsoleted the old one.
> I'm not familiar enough with ietf nous to know whether this is relevant to
> a document like this.  Wearing my operator hat, it looks a little odd,
> that's all.
>
> 2:
>
>>> There is a second operational issue which may merit mention here, namely
>>> the issue of ensuring that whatever session layer authentication is
>>> implemented on an actual network device, that it doesn't create more
>>> problems than it solves.  Specifically, if session layer authentication is
>>> pushed too far down the protocol stack, cryptographic authentication can
>>> occur before other basic checks which might be a whole pile less CPU
>>> intensive.  There was a scare about this several years ago when it turned
>>> out that a well-known vendor had implemented tcp md5 checksumming before
>>> more basic tcp session checks (e.g. seq numbers, ttl, etc).  In the event,
>>> this turned out to be a red herring because md5 is sufficiently gentle on
>>> the CPU that it didn't make much difference in reality.
>>>
>>> However, there is cryptographic value in using more computationally
>>> intensive hashing algorithms, and if routers (which often have relatively
>>> slow general CPUs or route-processor CPUs) were to get trashed with a large
>>> flood of packets which were signed with a cpu-intensive hashing algorithm,
>>> and if the checksum were to be implemented in the wrong place in the TCP
>>> stack, then this could become an actual problem.
>
> Whatever a router manufacturer does in terms of implementation, they need
> to be careful when writing code to ensure that they don't accidentally open
> up other attack vectors by implementing transport layer security badly.  It
> almost happened once before, and this could have caused damage at the time
> if we had had been using a computationally expensive algorithm like openbsd
> bcrypt instead of md5.
>
> 3:
>
>>> It may be useful to consider whether to acknowledge the existence of rfc
>>> 6192 in the context of providing a link to what other steps might be useful
>>> to secure routers.
>
> What I'm suggesting here is a single sentence around the first paragraph in
> section 2.1 to say that while it's outside the context of transport
> security, there's more to protecting routers than cryptography - and then
> provide a link to 6192 as an informative reference to someone who might be
> interested in the more general area router security.
>
> General router security is a large subject which is not particularly
> pertinent to keying and authentication, but a random operator who happens
> to read this ID when it's published might appreciate the pointer.
>
> Nick
>
>

From ananth@nttmcl.com  Tue Dec 18 15:15:44 2012
Return-Path: <ananth@nttmcl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419DC21E8045 for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 15:15:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level: 
X-Spam-Status: No, score=-1.843 tagged_above=-999 required=5 tests=[AWL=-1.133, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OqT-+pc5bRvb for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 15:15:42 -0800 (PST)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by ietfa.amsl.com (Postfix) with ESMTP id 5BDB021F86C2 for <ietf@ietf.org>; Tue, 18 Dec 2012 15:15:42 -0800 (PST)
Received: by mail-vc0-f169.google.com with SMTP id gb23so1655859vcb.0 for <ietf@ietf.org>; Tue, 18 Dec 2012 15:15:41 -0800 (PST)
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=DddHo5pyWh4QpU43phRHSG4mES1vXpZ5dgbk81NsXGo=; b=IzjWBCOSI7D3oVOsfdNAJ/YAk/wYigPMUkkckKs6njy0WiijB+tSIa9CrBpUlZ//PA v7vtKwEm6YiXMzTK4swbgtugDYlpH6ItOtxPXBqr6jYsglU5HUxaMMBzRYkU8Ggc+4EC OL8eV3EBjQ1XRWGWYOM2cF3Mr5dd8bw3Psn5YRQOyczG/dUoRZviuIZbwSovmSkNpEBR zhCgSHMPobL5uYa8kJFApAVx5u9Qix9sgxEO8pGF5zqxrNt1SDmkE2nFl2hu0zUIr/JC hnKTnhPKHRId5T0Tf3dvt/kOivpARFucLf5j2U80vqO8RHgR5puTQRJ0POuYa2Qktgr7 +3ZA==
MIME-Version: 1.0
Received: by 10.220.141.6 with SMTP id k6mr5839992vcu.24.1355872541485; Tue, 18 Dec 2012 15:15:41 -0800 (PST)
Received: by 10.220.3.229 with HTTP; Tue, 18 Dec 2012 15:15:41 -0800 (PST)
In-Reply-To: <50D0ED83.3090700@joelhalpern.com>
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <50D0ED83.3090700@joelhalpern.com>
Date: Tue, 18 Dec 2012 15:15:41 -0800
Message-ID: <CAFZUbhenPyaDoknGafGd4SOXOUVo5VpbohjC8D5rB21iB0v1xQ@mail.gmail.com>
Subject: Re: [karp] Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
From: Anantha Ramaiah <ananth@nttmcl.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=f46d04389221322a6504d128ad8e
X-Gm-Message-State: ALoCoQlQ7MASS+ItKy7yKtChC1RbSLNjGcg7KjJQL5g9tIeAR9phKG0HzDH+kDetfiGMZW0bxqBB
X-Mailman-Approved-At: Thu, 20 Dec 2012 08:17:04 -0800
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "karp@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: Tue, 18 Dec 2012 23:15:44 -0000

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

FWIW,
      I have to agree with Nick's observations w.r.t TCP MD5. Especially
the following :-

- TCP MD5 is not universally turned on to protect LDP sessions. It is case
by case. TCP MD5 is better than no security at all. Also TCP MD5 with
periodic key rollover can make the life harder for TCP MD5 based collision
attacks. It is better than TCP-MD5 with no key rollover.

(so, you see the degree of protection varies and the Nick's example of 5
pin versus 7 pin barrel lock, which I like :-)

- I also agree that there are no live TCP-AO implementations to date.
TCP-MD5 on the other hand has been there and still there in many vendors
TCP stacks.

I think it is a good idea to note some the points (esp the CPU utilization
depending on the crypto algorithm of choice etc.,) into the draft. Makes
sense to me.

thanks,
-Anantha


On Tue, Dec 18, 2012 at 2:26 PM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> Nick, I appreciate that you have read this document and commented.
>
> Two general questions:
> 1) Can you be more specific about where you see unclear language usage?
>  It is hard to fix a general coment.
>
> 2) A number of your comments seem to be about general router security.
> Many of them would see far more appicable to RFC 6518.  This document is
> just about changes to protect TCP sessions (yes, what we are concerned
> about are the TCP sessions used by routers.)  Can you take a look at your
> comments, and tell us which ones are applicable to this document, and which
> ones should be held for when the community is ready to revise RFC 6518?
>
> Thank you,
> Joel
>
> On 12/18/2012 5:12 PM, Nick Hilliard wrote:
>
>> On 18/12/2012 20:14, Ben Campbell wrote:
>>
>>> ** Nits/editorial comments:
>>>
>>> -- The 2119 paragraph was removed, but there's still an orphaned 2119
>>> entry in the informational reference section.
>>>
>>
>> I'm not sure that this was a good idea.  There are a lot of "has to"s in
>> this text, and it's not clear to me whether they are phrased like that as
>> a
>> way of getting around 2119, or what's going on.  Whatever the reason, "has
>> to" sounds very informal and probably not suitable for a document like
>> this.  Could we have some clarification as to why "has to" doesn't mean
>> "MUST" (or even "SHOULD").
>>
>> --
>>
>> -   protocol stack from CPU-utilization based attacks.TCP Robustness
>> +   protocol stack from CPU-utilization based attacks. TCP Robustness
>>
>> --
>>
>> I have a general issue with the statement "TCP MD5 [RFC2385] has been
>> obsoleted by TCP-AO [RFC5925]."  At this time, I'm not aware of any live
>> TCP-AO implementations.  So while I understand that md5 is effectively
>> obsolete from the specification point of view, from the point of view of
>> operational reality it's still the only show in town (no-one uses ipsec
>> for
>> this).
>>
>> Secondly, as a general comment about the TCP MD5 option, no-one that I
>> know
>> uses it as a serious security mechanism, but instead as a means of putting
>> the equivalent of a padlock on the barn door.  This does two things: 1. it
>> stops bgp sessions from being accidentally re-used (e.g. at IXPs or on
>> commercial providers who are re-using access ports), and 2. it simply
>> raises the bar in terms of difficulty.  If your barnyard door has a
>> padlock, and the one beside doesn't, the average lazy human being will
>> attempt to poke at the one which doesn't.
>>
>>  From an operational view, i would generally see the difference between
>>>
>> tcp/md5 and tcp/sha1 (via tcp-ao) as being similar to the difference
>> between a 5 pin and a 7 pin barrel lock.  Both look like a lock on the
>> outside, and the thief is probably going to smash a window to get in
>> anyway, or look for the key which the owners left under the mat.
>>
>> --
>>
>> There is a second operational issue which may merit mention here, namely
>> the issue of ensuring that whatever session layer authentication is
>> implemented on an actual network device, that it doesn't create more
>> problems than it solves.  Specifically, if session layer authentication is
>> pushed too far down the protocol stack, cryptographic authentication can
>> occur before other basic checks which might be a whole pile less CPU
>> intensive.  There was a scare about this several years ago when it turned
>> out that a well-known vendor had implemented tcp md5 checksumming before
>> more basic tcp session checks (e.g. seq numbers, ttl, etc).  In the event,
>> this turned out to be a red herring because md5 is sufficiently gentle on
>> the CPU that it didn't make much difference in reality.
>>
>> However, there is cryptographic value in using more computationally
>> intensive hashing algorithms, and if routers (which often have relatively
>> slow general CPUs or route-processor CPUs) were to get trashed with a
>> large
>> flood of packets which were signed with a cpu-intensive hashing algorithm,
>> and if the checksum were to be implemented in the wrong place in the TCP
>> stack, then this could become an actual problem.
>>
>> I don't know whether these things should be noted in the draft.
>>
>> --
>>
>> It may be useful to consider whether to acknowledge the existence of rfc
>> 6192 in the context of providing a link to what other steps might be
>> useful
>> to secure routers.
>>
>> --
>>
>>      pairs of routers when using TCP MD5.  It is well known that the
>>>     longer the same key is used, the greater the chance that it can be
>>>     guessed or exposed
>>>
>>
>> I'm split between {{cn}} and [[Wikipedia:OBVIOUS]].  Hmmm, life's little
>> decisions.
>>
>> --
>>
>>      Routers lack comprehensive key management and keys derived from it
>>>     that they can use to authenticate data.
>>>
>>
>> clumsy wording (and grammatically incorrect).
>>
>> --
>>
>>      Authentication, tamper protection, and encryption all require the use
>>>
>>
>> should that second comma be dropped?  Not sure what the ietf style
>> dictates.
>>
>> --
>>
>>      Authentication, tamper protection, and encryption all require the use
>>>     of keys by sender and receiver.  An automated KMP therefore has to
>>>     include a way to distribute MKT between two end points with little or
>>>     no administration overhead.  It has to cover automatic key rollover.
>>>
>>
>> "has to" has to become "MUST", shouldn't it?
>>
>> Also, the third sentence is a semantic repeat of the second - and much
>> easier to understand, too.
>>
>> --
>>
>> -    that, where PCEs are discovered and not configured, the PCC cannot
>> +    that where PCEs are discovered and not configured, the PCC cannot
>>
>> --
>>
>> -   [draft-zheng-mpls-ldp-hello-**crypto-auth-04] suggest a new
>> +   [draft-zheng-mpls-ldp-hello-**crypto-auth-04] suggests a new
>>
>> --
>>
>>               An LSR can reduce the threat of spoofed Extended Hellos by
>>>     filtering them and accepting Hellos from sources permitted by an
>>>     access lists.
>>>
>>
>> "permitted by an access list".
>>
>> --
>>
>>    However, performing the filtering using access lists
>>>     requires LSR resource, and the LSR is still vulnerable to the IP
>>>     source address spoofing.
>>>
>>
>> This is a little clumsy.  Maybe rephrase as: "However, filtering with
>> access lists requires LSR resources, and the LSR may still be vulnerable
>> to
>> IP source address spoofing."
>>
>> "may" rather than is.  This will depend on the iACL policy of the network.
>>
>> --
>>
>>  Spoofed Hello messages are observed and reported as real
>>>     problem in production networks.
>>>
>>
>> s/problem/problems/
>>
>> {{cn}}
>>
>> --
>>
>>      The Message Authentication Codes (MACs) used by TCP MD5 option, is
>>>     considered too weak
>>>
>>
>> oops, grammar.
>>
>> --
>>
>>  Cryptographic research suggests that both these
>>>     MAC algorithms defined are fairly secure.
>>>
>>
>> Today's "fairly secure" algorithms are tomorrow's swiss cheese:
>>
>>  http://www.eetimes.com/**electronics-news/4051745/**Chinese-researchers-
>>> **compromise-SHA-1-hashing-**algorithm<http://www.eetimes.com/electronics-news/4051745/Chinese-researchers-compromise-SHA-1-hashing-algorithm>
>>>
>>
>> I would explicitly avoid the use of ".* secure", and if the authors feel
>> the need to make any statement about them, that it should be prefixed by
>> woolly, hand-wavey, get-out-of-jail-free phrases, e.g. "at the time of
>> authorship, there are no publicly known attacks on this algorithm which
>> reduce the strength to complexity of less than 1 in X", or however
>> crypto-heads like to phrase that sort of thing.  Right now, that phrase is
>> headed towards algorithmic oblivion.
>>
>> --
>>
>>  LDP [RFC5036] does not provide any security
>>>     mechanisms for use with Hello messages except for some configuration
>>>     which may help protect against bogus discovery events.  These
>>>     configurations include directly connected links and interfaces.
>>>
>>
>> suggest rewording:
>>
>> LDP [RFC5036] does not provide any security mechanisms for use with Hello
>> messages, although operational workarounds may be implemented such as
>> using directly interfaces.
>>
>> --
>>
>> There are possibly more nits in there - I haven't exhaustively gone
>> through
>> all the text, but it needs a good shake-down by a style editor.
>>
>> Otherwise I like this draft and think it has merit as a general
>> informational overview.
>>
>> Nick
>>
>>
>>  ______________________________**_________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/**listinfo/karp<https://www.ietf.org/mailman/listinfo/karp>
>

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

<div><br></div>FWIW,<div>=A0 =A0 =A0 I have to agree with Nick&#39;s observ=
ations w.r.t TCP MD5. Especially the following :-</div><div><br></div><div>=
- TCP MD5 is not universally turned on to protect LDP sessions. It is case =
by case. TCP MD5 is better than no security at all. Also TCP MD5 with perio=
dic key rollover can make the life harder for TCP MD5 based collision attac=
ks. It is better than TCP-MD5 with no key rollover.</div>
<div><br></div><div>(so, you see the degree of protection varies and the Ni=
ck&#39;s example of 5 pin versus 7 pin barrel lock, which I like :-)</div><=
div><br></div><div>- I also agree that there are no live TCP-AO implementat=
ions to date. TCP-MD5 on the other hand has been there and still there in m=
any vendors TCP stacks.</div>
<div><br></div><div>I think it is a good idea to note some the points (esp =
the CPU utilization depending on the crypto algorithm of choice etc.,) into=
 the draft. Makes sense to me.</div><div><br></div><div>thanks,</div><div>
-Anantha</div><div><br><br><div class=3D"gmail_quote">On Tue, Dec 18, 2012 =
at 2:26 PM, Joel M. Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joe=
lhalpern.com" target=3D"_blank">jmh@joelhalpern.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
Nick, I appreciate that you have read this document and commented.<br>
<br>
Two general questions:<br>
1) Can you be more specific about where you see unclear language usage? =A0=
It is hard to fix a general coment.<br>
<br>
2) A number of your comments seem to be about general router security. Many=
 of them would see far more appicable to RFC 6518. =A0This document is just=
 about changes to protect TCP sessions (yes, what we are concerned about ar=
e the TCP sessions used by routers.) =A0Can you take a look at your comment=
s, and tell us which ones are applicable to this document, and which ones s=
hould be held for when the community is ready to revise RFC 6518?<br>

<br>
Thank you,<br>
Joel<br>
<br>
On 12/18/2012 5:12 PM, Nick Hilliard wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 18/12/2012 20:14, Ben Campbell wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
** Nits/editorial comments:<br>
<br>
-- The 2119 paragraph was removed, but there&#39;s still an orphaned 2119 e=
ntry in the informational reference section.<br>
</blockquote>
<br>
I&#39;m not sure that this was a good idea. =A0There are a lot of &quot;has=
 to&quot;s in<br>
this text, and it&#39;s not clear to me whether they are phrased like that =
as a<br>
way of getting around 2119, or what&#39;s going on. =A0Whatever the reason,=
 &quot;has<br>
to&quot; sounds very informal and probably not suitable for a document like=
<br>
this. =A0Could we have some clarification as to why &quot;has to&quot; does=
n&#39;t mean<br>
&quot;MUST&quot; (or even &quot;SHOULD&quot;).<br>
<br>
--<br>
<br>
- =A0 protocol stack from CPU-utilization based attacks.TCP Robustness<br>
+ =A0 protocol stack from CPU-utilization based attacks. TCP Robustness<br>
<br>
--<br>
<br>
I have a general issue with the statement &quot;TCP MD5 [RFC2385] has been<=
br>
obsoleted by TCP-AO [RFC5925].&quot; =A0At this time, I&#39;m not aware of =
any live<br>
TCP-AO implementations. =A0So while I understand that md5 is effectively<br=
>
obsolete from the specification point of view, from the point of view of<br=
>
operational reality it&#39;s still the only show in town (no-one uses ipsec=
 for<br>
this).<br>
<br>
Secondly, as a general comment about the TCP MD5 option, no-one that I know=
<br>
uses it as a serious security mechanism, but instead as a means of putting<=
br>
the equivalent of a padlock on the barn door. =A0This does two things: 1. i=
t<br>
stops bgp sessions from being accidentally re-used (e.g. at IXPs or on<br>
commercial providers who are re-using access ports), and 2. it simply<br>
raises the bar in terms of difficulty. =A0If your barnyard door has a<br>
padlock, and the one beside doesn&#39;t, the average lazy human being will<=
br>
attempt to poke at the one which doesn&#39;t.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
>From an operational view, i would generally see the difference between<br>
</blockquote>
tcp/md5 and tcp/sha1 (via tcp-ao) as being similar to the difference<br>
between a 5 pin and a 7 pin barrel lock. =A0Both look like a lock on the<br=
>
outside, and the thief is probably going to smash a window to get in<br>
anyway, or look for the key which the owners left under the mat.<br>
<br>
--<br>
<br>
There is a second operational issue which may merit mention here, namely<br=
>
the issue of ensuring that whatever session layer authentication is<br>
implemented on an actual network device, that it doesn&#39;t create more<br=
>
problems than it solves. =A0Specifically, if session layer authentication i=
s<br>
pushed too far down the protocol stack, cryptographic authentication can<br=
>
occur before other basic checks which might be a whole pile less CPU<br>
intensive. =A0There was a scare about this several years ago when it turned=
<br>
out that a well-known vendor had implemented tcp md5 checksumming before<br=
>
more basic tcp session checks (e.g. seq numbers, ttl, etc). =A0In the event=
,<br>
this turned out to be a red herring because md5 is sufficiently gentle on<b=
r>
the CPU that it didn&#39;t make much difference in reality.<br>
<br>
However, there is cryptographic value in using more computationally<br>
intensive hashing algorithms, and if routers (which often have relatively<b=
r>
slow general CPUs or route-processor CPUs) were to get trashed with a large=
<br>
flood of packets which were signed with a cpu-intensive hashing algorithm,<=
br>
and if the checksum were to be implemented in the wrong place in the TCP<br=
>
stack, then this could become an actual problem.<br>
<br>
I don&#39;t know whether these things should be noted in the draft.<br>
<br>
--<br>
<br>
It may be useful to consider whether to acknowledge the existence of rfc<br=
>
6192 in the context of providing a link to what other steps might be useful=
<br>
to secure routers.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 pairs of routers when using TCP MD5. =A0It is well known that the<b=
r>
=A0 =A0 longer the same key is used, the greater the chance that it can be<=
br>
=A0 =A0 guessed or exposed<br>
</blockquote>
<br>
I&#39;m split between {{cn}} and [[Wikipedia:OBVIOUS]]. =A0Hmmm, life&#39;s=
 little<br>
decisions.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 Routers lack comprehensive key management and keys derived from it<=
br>
=A0 =A0 that they can use to authenticate data.<br>
</blockquote>
<br>
clumsy wording (and grammatically incorrect).<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 Authentication, tamper protection, and encryption all require the u=
se<br>
</blockquote>
<br>
should that second comma be dropped? =A0Not sure what the ietf style dictat=
es.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 Authentication, tamper protection, and encryption all require the u=
se<br>
=A0 =A0 of keys by sender and receiver. =A0An automated KMP therefore has t=
o<br>
=A0 =A0 include a way to distribute MKT between two end points with little =
or<br>
=A0 =A0 no administration overhead. =A0It has to cover automatic key rollov=
er.<br>
</blockquote>
<br>
&quot;has to&quot; has to become &quot;MUST&quot;, shouldn&#39;t it?<br>
<br>
Also, the third sentence is a semantic repeat of the second - and much<br>
easier to understand, too.<br>
<br>
--<br>
<br>
- =A0 =A0that, where PCEs are discovered and not configured, the PCC cannot=
<br>
+ =A0 =A0that where PCEs are discovered and not configured, the PCC cannot<=
br>
<br>
--<br>
<br>
- =A0 [draft-zheng-mpls-ldp-hello-<u></u>crypto-auth-04] suggest a new<br>
+ =A0 [draft-zheng-mpls-ldp-hello-<u></u>crypto-auth-04] suggests a new<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 =A0 =A0 =A0An LSR can reduce the threat of spoofed Extended=
 Hellos by<br>
=A0 =A0 filtering them and accepting Hellos from sources permitted by an<br=
>
=A0 =A0 access lists.<br>
</blockquote>
<br>
&quot;permitted by an access list&quot;.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 However, performing the filtering using access lists<br>
=A0 =A0 requires LSR resource, and the LSR is still vulnerable to the IP<br=
>
=A0 =A0 source address spoofing.<br>
</blockquote>
<br>
This is a little clumsy. =A0Maybe rephrase as: &quot;However, filtering wit=
h<br>
access lists requires LSR resources, and the LSR may still be vulnerable to=
<br>
IP source address spoofing.&quot;<br>
<br>
&quot;may&quot; rather than is. =A0This will depend on the iACL policy of t=
he network.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Spoofed Hello messages are observed and reported as real<br>
=A0 =A0 problem in production networks.<br>
</blockquote>
<br>
s/problem/problems/<br>
<br>
{{cn}}<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 The Message Authentication Codes (MACs) used by TCP MD5 option, is<=
br>
=A0 =A0 considered too weak<br>
</blockquote>
<br>
oops, grammar.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Cryptographic research suggests that both these<br>
=A0 =A0 MAC algorithms defined are fairly secure.<br>
</blockquote>
<br>
Today&#39;s &quot;fairly secure&quot; algorithms are tomorrow&#39;s swiss c=
heese:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<a href=3D"http://www.eetimes.com/electronics-news/4051745/Chinese-research=
ers-compromise-SHA-1-hashing-algorithm" target=3D"_blank">http://www.eetime=
s.com/<u></u>electronics-news/4051745/<u></u>Chinese-researchers-<u></u>com=
promise-SHA-1-hashing-<u></u>algorithm</a><br>

</blockquote>
<br>
I would explicitly avoid the use of &quot;.* secure&quot;, and if the autho=
rs feel<br>
the need to make any statement about them, that it should be prefixed by<br=
>
woolly, hand-wavey, get-out-of-jail-free phrases, e.g. &quot;at the time of=
<br>
authorship, there are no publicly known attacks on this algorithm which<br>
reduce the strength to complexity of less than 1 in X&quot;, or however<br>
crypto-heads like to phrase that sort of thing. =A0Right now, that phrase i=
s<br>
headed towards algorithmic oblivion.<br>
<br>
--<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
LDP [RFC5036] does not provide any security<br>
=A0 =A0 mechanisms for use with Hello messages except for some configuratio=
n<br>
=A0 =A0 which may help protect against bogus discovery events. =A0These<br>
=A0 =A0 configurations include directly connected links and interfaces.<br>
</blockquote>
<br>
suggest rewording:<br>
<br>
LDP [RFC5036] does not provide any security mechanisms for use with Hello<b=
r>
messages, although operational workarounds may be implemented such as<br>
using directly interfaces.<br>
<br>
--<br>
<br>
There are possibly more nits in there - I haven&#39;t exhaustively gone thr=
ough<br>
all the text, but it needs a good shake-down by a style editor.<br>
<br>
Otherwise I like this draft and think it has merit as a general<br>
informational overview.<br>
<br>
Nick<br>
<br>
<br>
</blockquote>
______________________________<u></u>_________________<br>
karp mailing list<br>
<a href=3D"mailto:karp@ietf.org" target=3D"_blank">karp@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/karp" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/karp</a><br>
</blockquote></div><br></div>

--f46d04389221322a6504d128ad8e--

From mmorley@mpcm.com  Tue Dec 18 17:00:42 2012
Return-Path: <mmorley@mpcm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2D9F21F8830 for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 17:00:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gtPyp6WMv8Lc for <ietf@ietfa.amsl.com>; Tue, 18 Dec 2012 17:00:41 -0800 (PST)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 79E0D21F8828 for <ietf@ietf.org>; Tue, 18 Dec 2012 17:00:41 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id b25so775567qca.3 for <ietf@ietf.org>; Tue, 18 Dec 2012 17:00:41 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=9M1apTBEubjLeegQH0OaUH+Wd2s4r6m/WT1J/J/FK+c=; b=a+Tx5kZnNPuQkFwWU8lRgEdOikKzRXSaGn9Gx9UpuR0yMP53SUOE+Nis2mJGlFs5Uz 3Zazv7yvpzzTjHOU5jo2wU5N+z2/vkF/R3XMsXDJkDkSebkbMnuhF3XN+CziJRChfm8n q3oekPYs5tGFTMEKUGhs5j0qNFEmoMiaYll/k7cIcy59EUmbC/1tj8w59b01il5/yzWU 89n+2+59sGnwynxx/qJjncdizlY/Rm5y4lnvdILRUGaj5m5+bXH/J5tXHBNoIdRQpAgs XeEPCPMerpfi6DBMkVDrDXWHzC6TS09u4hMOBrxr2ZB2xraqzfynNRzQK3Py26rX0bdv DPPg==
MIME-Version: 1.0
Received: by 10.224.17.68 with SMTP id r4mr1719933qaa.21.1355878840835; Tue, 18 Dec 2012 17:00:40 -0800 (PST)
Sender: mmorley@mpcm.com
Received: by 10.49.16.170 with HTTP; Tue, 18 Dec 2012 17:00:40 -0800 (PST)
In-Reply-To: <CABP7Rbc10-B1Fgu5w5LSATWW2vCxdcpERKTi6cbUXgF03ks7Cw@mail.gmail.com>
References: <20121211150057.28223.93310.idtracker@ietfa.amsl.com> <50cb04b9.86df440a.72fe.1e20SMTPIN_ADDED_BROKEN@mx.google.com> <CABP7RbeNsZ_rBWRjou=VG+hBhUKaOz+y1a0sSChwWiHte9znnQ@mail.gmail.com> <50cb5f3c.694c420a.38fb.39afSMTPIN_ADDED_BROKEN@mx.google.com> <CAChr6SxZRc3B_HCbw76kLe2dsRSr43r-gLpfMVnCUfJTrZdTLA@mail.gmail.com> <CABP7RbfA33huBFadMeXTTEt=MkjW8-d4DFH7+GLXGurnm9sSRw@mail.gmail.com> <CAOXDeqpPE4eNy_qJpDPdPHbCQakG9-hDcNZ3Sj9r4kWedByVzQ@mail.gmail.com> <CAChr6SwtS_=iS-k4mJm1vHjEvvGVzay5jDYeGheqsPZqO-89CQ@mail.gmail.com> <EABB8F51-C3B4-49F5-8672-5C2ABAC7043A@mnot.net> <CAChr6Sy-Xc8vC6FabFmdseR7xfQ-6t9hARunWjYgt6FqjmoBWg@mail.gmail.com> <CABP7Rbd7w-7-8+q0T7WciBp6NU7c2uJjmRGiLFjxkc52P5KLdw@mail.gmail.com> <CAChr6SyV-kDLYnDXXjW5GD7KZ1brBYLmvO-5TkODGtcHOf2rmg@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1150408948F@WSMSG3153V.srv.dir.telstra.com> <CABP7Rbc10-B1Fgu5w5LSATWW2vCxdcpERKTi6cbUXgF03ks7Cw@mail.gmail.com>
Date: Tue, 18 Dec 2012 20:00:40 -0500
X-Google-Sender-Auth: o_OH8K1GwtwGxS518AQm2VuXJ0U
Message-ID: <CAOXDeqoGUwOZWW-9kZMv5UmeieggA1rnunASQePm+8a_np-9pA@mail.gmail.com>
Subject: Re: [apps-discuss] Last Call: <draft-ietf-appsawg-json-pointer-07.txt> (JSON Pointer) to Proposed Standard
From: Matthew Morley <matt@mpcm.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: multipart/alternative; boundary=14dae9399b01aa9f7204d12a249b
X-Gm-Message-State: ALoCoQl50EfprhqU77gLCu7KqKFPVlD4dmi2rVDQfQuHU1z4JR/7Z9vgdtb66rbmeqSbINAJgFsU
X-Mailman-Approved-At: Thu, 20 Dec 2012 08:17:04 -0800
Cc: Mark Nottingham <mnot@mnot.net>, "Manger, James H" <James.H.Manger@team.telstra.com>, IETF Discussion <ietf@ietf.org>, IETF Apps Discuss <apps-discuss@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 01:00:42 -0000

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

I do not feel there is a gain from adjusting the syntax, in the role of
JSON Pointer as a stand alone specification. The addition of such a change
adds an implied checking of a list vs a collection, as part of pointer
resolution.

If you are using the pointer as a means to get a value, it makes little
difference in the fact that the value either exists at the end of that path
or it doesn't.  (Get me the value at /a/b/c/2)

If you are using the pointer as a method of identity, again it makes little
difference as only one point can presented by that pointer. (You are at
/a/b/c/2)

For me, these are the primary uses of the JSON Pointer specification.
Rarely is the underlying structure, in practice, of consequence.

Something like JSON-Schema is much better for testing the shapes of JSON
data.

However, I can see the point in such a change when paired with JSON-Patch.
But I still feel that even this is more of an attempt to overload the role
of the pointer, to make it carry additional meaning that should be
expressed in either the test or the operation keywords of that particular
specification.

My vote is to leave the specification syntax as is, and keep it simple to
produce and consume, even at the cost of not being able to infer the
structure of any given step in the pointer without the actual json object
being traversed.

-- 
Matthew P. C. Morley

On Tue, Dec 18, 2012 at 12:24 AM, James M Snell <jasnell@gmail.com> wrote:

> What I'm not clear on, however, is what significant benefit making this
> kind of change would provide. Yes, the syntax can be more verbose and exact
> but it's not clear that the change is worth the cost.
>
> Robert mentioned that the addition of the json-predicates test doubled the
> size of the json-patch file, and yes, I get that.. but if we're talking
> about sending a two-object json-patch document to modify a JSON document
> many times larger than that, it's still worth the extra handful of bytes it
> takes. Sure, if we had a complex patch document consisting of large amounts
> of json-patch and json-predicate objects being applied to an arbitrarily
> structured document, I could understand the concern, but in that case one
> would have to question the wisdom of doing a partial update in the first
> place. JSON-Patch documents are best served small and simple, and the
> inclusion of a json-predicate or two per instance is not going to blow the
> budget on bits on the wire.
>
> So the key question becomes: what added benefit does a more verbose
> pointer syntax provide us? And is there a concrete need for that benefit
> that can be demonstrated?
>
> - James
>
>
> On Mon, Dec 17, 2012 at 9:12 PM, Manger, James H <
> James.H.Manger@team.telstra.com> wrote:
>
>> If we were starting from scratch and defining JSON Pointer again I would
>> argue for distinguishing array indices and object names in the syntax. For
>> instance, prefix an object name with "/" and an array index with ":".
>>
>>    json-pointer = *segment
>>    segment = "/" name  /  ":" index
>>    name = *( unescaped / escaped )
>>    unescaped = %x00-2E / %x30-39 / %x3B-7D / %x7F-10FFFF
>>    escaped = "~" ( "0" / "1" / "2" )
>>    index = "0" / %x31-39 *(%x30-39) / "-"
>>
>> 1. It makes parsing marginally harder: you cannot just split on "/" and
>> unescape each segment.
>> 2. It doesn't make much difference for selecting a value from some JSON,
>> or for finding a spot to insert a new value.
>> 3. It would allow you to automatically create object *or array* ancestors
>> when setting a new value (eg adding 23 at /a:0/b:0 to {} could give
>> {"a":[{"b":[23]}]}).
>> 4. It might encourage better validation of pointers, but that is probably
>> wishful thinking.
>>
>> But JSON Pointer drafts have used the /{name|index} format for a year.
>> There are a bunch of implementations. The difference is minor in most
>> circumstances. So while I would be happy to change, I am also comfortable
>> staying with the current pointer syntax.
>>
>>
>> > There's no good reason for it to be that way, is there?
>>
>> I don't think so.
>>
>> --
>> James Manger
>>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>

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

I do not feel there is a gain from adjusting the syntax, in the role of JSO=
N Pointer as a stand alone specification.=A0The addition of such a change a=
dds an implied=A0checking of a list vs a collection, as part of pointer res=
olution.<br>
<br>If you are using the pointer as a means to get a value, it makes little=
 difference in the fact that the value either exists at the end of that pat=
h or it=A0doesn&#39;t. =A0(Get me the value at /a/b/c/2)<br><br>If you are =
using the pointer as a method of identity, again it makes little difference=
 as only one point can presented by that pointer. (You are at /a/b/c/2)<br>
<br>For me, these are the primary uses of the JSON Pointer specification. R=
arely is the underlying structure, in practice, of=A0consequence.<br><br>So=
mething like JSON-Schema is much better for testing the shapes of JSON data=
.<br>
<div><br></div><div>However, I can see the point in such a change when pair=
ed with JSON-Patch. But I still feel that even this is more of an attempt t=
o overload the role of the pointer, to make it carry additional meaning tha=
t should be expressed in either the test or the operation keywords of that =
particular specification.<br>
<br>My vote is to leave the specification syntax as is, and keep it simple =
to produce and consume, even at the cost of not being able to infer the str=
ucture of any given step in the pointer without the actual json object bein=
g traversed.<br>
<br class=3D"Apple-interchange-newline">--=A0<br>Matthew P. C. Morley<br><b=
r><div class=3D"gmail_quote">On Tue, Dec 18, 2012 at 12:24 AM, James M Snel=
l <span dir=3D"ltr">&lt;<a href=3D"mailto:jasnell@gmail.com" target=3D"_bla=
nk">jasnell@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><font face=3D"courier new,m=
onospace">What I&#39;m not clear on, however, is what significant benefit m=
aking this kind of change would provide. Yes, the syntax can be more verbos=
e and exact but it&#39;s not clear that the change is worth the cost.=A0</f=
ont><div>


<font face=3D"courier new,monospace"><br></font></div><div><font face=3D"co=
urier new,monospace">Robert mentioned that the addition of the json-predica=
tes test doubled the size of the json-patch file, and yes, I get that.. but=
 if we&#39;re talking about sending a two-object json-patch document to mod=
ify a JSON document many times larger than that, it&#39;s still worth the e=
xtra handful of bytes it takes. Sure, if we had a complex patch document co=
nsisting of large amounts of json-patch and json-predicate objects being ap=
plied to an=A0arbitrarily structured document, I could understand the conce=
rn, but in that case one would have to question the wisdom of doing a parti=
al update in the first place. JSON-Patch documents are best served small an=
d simple, and the inclusion of a json-predicate or two per instance is not =
going to blow the budget on bits on the wire.=A0</font></div>


<div><font face=3D"courier new,monospace"><br></font></div><div><font face=
=3D"courier new,monospace">So the key question becomes: what added benefit =
does a more verbose pointer syntax provide us? And is there a concrete need=
 for that benefit that can be demonstrated?</font></div>
<span class=3D"HOEnZb"><font color=3D"#888888">

<div><font face=3D"courier new,monospace"><br></font></div><div><font face=
=3D"courier new,monospace">- James</font></div></font></span></div><div cla=
ss=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">
On Mon, Dec 17, 2012 at 9:12 PM, Manger, James H <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:James.H.Manger@team.telstra.com" target=3D"_blank">James.H.Ma=
nger@team.telstra.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">If we were starting from scratch and definin=
g JSON Pointer again I would argue for distinguishing array indices and obj=
ect names in the syntax. For instance, prefix an object name with &quot;/&q=
uot; and an array index with &quot;:&quot;.<br>



<br>
=A0 =A0json-pointer =3D *segment<br>
=A0 =A0segment =3D &quot;/&quot; name =A0/ =A0&quot;:&quot; index<br>
=A0 =A0name =3D *( unescaped / escaped )<br>
=A0 =A0unescaped =3D %x00-2E / %x30-39 / %x3B-7D / %x7F-10FFFF<br>
=A0 =A0escaped =3D &quot;~&quot; ( &quot;0&quot; / &quot;1&quot; / &quot;2&=
quot; )<br>
=A0 =A0index =3D &quot;0&quot; / %x31-39 *(%x30-39) / &quot;-&quot;<br>
<br>
1. It makes parsing marginally harder: you cannot just split on &quot;/&quo=
t; and unescape each segment.<br>
2. It doesn&#39;t make much difference for selecting a value from some JSON=
, or for finding a spot to insert a new value.<br>
3. It would allow you to automatically create object *or array* ancestors w=
hen setting a new value (eg adding 23 at /a:0/b:0 to {} could give {&quot;a=
&quot;:[{&quot;b&quot;:[23]}]}).<br>
4. It might encourage better validation of pointers, but that is probably w=
ishful thinking.<br>
<br>
But JSON Pointer drafts have used the /{name|index} format for a year. Ther=
e are a bunch of implementations. The difference is minor in most circumsta=
nces. So while I would be happy to change, I am also comfortable staying wi=
th the current pointer syntax.<br>



<div><br>
<br>
&gt; There&#39;s no good reason for it to be that way, is there?<br>
<br>
</div>I don&#39;t think so.<br>
<br>
--<br>
James Manger<br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
apps-discuss mailing list<br>
<a href=3D"mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/apps-discuss" target=3D"_b=
lank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br></blockquot=
e></div>
</div>

--14dae9399b01aa9f7204d12a249b--

From mjethanandani@gmail.com  Thu Dec 20 07:42:29 2012
Return-Path: <mjethanandani@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 9AC8A21F8923; Thu, 20 Dec 2012 07:42:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.338
X-Spam-Level: 
X-Spam-Status: No, score=-3.338 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ig1VaWoeM7kL; Thu, 20 Dec 2012 07:42:29 -0800 (PST)
Received: from mail-da0-f48.google.com (mail-da0-f48.google.com [209.85.210.48]) by ietfa.amsl.com (Postfix) with ESMTP id 004FC21F892E; Thu, 20 Dec 2012 07:42:28 -0800 (PST)
Received: by mail-da0-f48.google.com with SMTP id k18so1594090dae.7 for <multiple recipients>; Thu, 20 Dec 2012 07:42:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=TXTWHivgzz9W9yq1nUSt185y+Ud1jscUEr2GefzlUzk=; b=VArWCB8j1qNdbBXb5+lOm9u1rHDAfHtSyWdWwmiiZNDcSrgr0/Tfllh0yU++yVE46W 0ddpTpUVx07Ahfi9oC1CdixBopqPGMw5COd6488jbzEhBy4RsweYKFzaHcZV6q0TP6+k 0eHm1Ql4LDcuOQA+nS6+6NL84AsqeUaoclg6FkqHGQv+VhsMO16NOO9pQytljyE23YK8 tDSNwjZKdHWdv7AJbFb/Y5l/MoaIpo/nedAvhlfP3QMZYVetGTRVkPZjBFMjIIubSbRt p+Q/CyFi7YgBzxI43qkecuQELqwC7GijVkpgSRRLu04ffl98h5DA6qrPnIcN/tCpngT5 qFoA==
X-Received: by 10.66.81.198 with SMTP id c6mr28488028pay.50.1356018148689; Thu, 20 Dec 2012 07:42:28 -0800 (PST)
Received: from [192.168.1.123] (c-24-6-180-144.hsd1.ca.comcast.net. [24.6.180.144]) by mx.google.com with ESMTPS id o5sm5587281paz.32.2012.12.20.07.42.26 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 20 Dec 2012 07:42:27 -0800 (PST)
Subject: Re: Gen-ART Telechat Review of draft-ietf-karp-routing-tcp-analysis-06
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-14--246177228
From: Mahesh Jethanandani <mjethanandani@gmail.com>
In-Reply-To: <50D31DD6.5080100@joelhalpern.com>
Date: Thu, 20 Dec 2012 07:42:24 -0800
Message-Id: <60A5315E-C898-48D8-BE0F-A57D82A20EE3@gmail.com>
References: <AEDD0F1A-EA31-4C3A-B1BF-BD16C9196740@nostrum.com> <50D0EA56.3050308@inex.ie> <50D0ED83.3090700@joelhalpern.com> <50D24A43.6050608@inex.ie> <50D31DD6.5080100@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Thu, 20 Dec 2012 08:17:04 -0800
Cc: "draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org" <draft-ietf-karp-routing-tcp-analysis.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "karp@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: Thu, 20 Dec 2012 15:42:29 -0000

--Apple-Mail-14--246177228
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Yes.

On Dec 20, 2012, at 6:16 AM, Joel M. Halpern wrote:

> Authors, WG, can we live with these?  I would think so.

Mahesh Jethanandani
mjethanandani@gmail.com




--Apple-Mail-14--246177228
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Yes.<div><br><div><div>On Dec 20, 2012, at 6:16 AM, Joel M. Halpern wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="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; ">Authors, WG, can we live with these? &nbsp;I would think so.</span></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>Mahesh Jethanandani</div><div><a href="mailto:mjethanandani@gmail.com">mjethanandani@gmail.com</a></div><div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></div></body></html>
--Apple-Mail-14--246177228--

From windy_1@skyhighway.com  Wed Dec 19 08:02:18 2012
Return-Path: <windy_1@skyhighway.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C8921F8A90; Wed, 19 Dec 2012 08:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.367
X-Spam-Level: 
X-Spam-Status: No, score=-1.367 tagged_above=-999 required=5 tests=[AWL=1.232,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Psq23l0lUop9; Wed, 19 Dec 2012 08:02:17 -0800 (PST)
Received: from skyhighway.com (skyhighway.com [63.249.82.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7E85521F8A6E; Wed, 19 Dec 2012 08:02:17 -0800 (PST)
Received: from Firefly.skyhighway.com (dsl-63-249-88-160.static.cruzio.com [63.249.88.160]) by skyhighway.com with ESMTP id qBJG2H7O034643; Wed, 19 Dec 2012 08:02:17 -0800 (PST)
Message-Id: <201212191602.qBJG2H7O034643@skyhighway.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 19 Dec 2012 08:02:10 -0800
To: ietf@ietf.org, trill@ietf.org
From: gayle noble <windy_1@skyhighway.com>
Subject: Re: [trill] Last Call: <draft-ietf-trill-oam-req-04.txt> (Requirements for Operations, Administration and Maintenance (OAM) in TRILL (Transparent Interconnection of Lots of Links)) to Informational RFC
In-Reply-To: <CAF4+nEF4ijXKn+eV7SJCagg-5bgP0ehT2hXKc54s1EUatZEkeA@mail.g mail.com>
References: <20121211145829.3754.44253.idtracker@ietfa.amsl.com> <201212120043.qBC0hjW7067663@skyhighway.com> <CAF4+nEF4ijXKn+eV7SJCagg-5bgP0ehT2hXKc54s1EUatZEkeA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Thu, 20 Dec 2012 08:17:49 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2012 16:02:18 -0000

I totally agree with that tweak >*sparkles*<
[RBridges MUST have the ability to distinguish OAM frames from normal 
data frames when the OAM frames are destined for them or require 
processing by the OAM plane.]

Perfect >*bow*<
gayle


At 07:54 AM 12/19/2012, Donald Eastlake wrote:
>Hi Gayle,
>
>On Tue, Dec 11, 2012 at 7:43 PM, gayle noble <windy_1@skyhighway.com> wrote:
> > Very well written!! No spelling errors! No grammatical errors! Only one
> > sentence, in my opinion,  could be rephrased for clarity
> > 4.1. Data Plane
> >  RBridges MUST have the ability to identify OAM frames destined for them or
> > which require processing by the OAM plane from normal data frames.
> > [Might be clearer if it was [RBridges MUST have the ability to identify OAM
> > frames from normal data frames when the OAM frames are destined for them or
> > require processing by the OAM plane.]]
>
>Thanks for the praise!
>I think that your suggested wording could be improved by replacing the
>word "identify" with the word "distinguish".
>
>Donald
>=============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
> > gayle


From rbonica@juniper.net  Thu Dec 20 14:47:46 2012
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 C992521F88DD for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 14:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.352
X-Spam-Level: 
X-Spam-Status: No, score=-103.352 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cI3KXHWQ1Br1 for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 14:47:45 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id C6D6A21F8920 for <ietf@ietf.org>; Thu, 20 Dec 2012 14:47:45 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUNOVkan9qHI6lG9ovkwCIe79gcMnPPL6@postini.com; Thu, 20 Dec 2012 14:47:45 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 20 Dec 2012 14:45:52 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Thu, 20 Dec 2012 14:45:52 -0800
Received: from CO9EHSOBE023.bigfish.com (207.46.163.24) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 20 Dec 2012 14:53:19 -0800
Received: from mail57-co9-R.bigfish.com (10.236.132.240) by CO9EHSOBE023.bigfish.com (10.236.130.86) with Microsoft SMTP Server id 14.1.225.23; Thu, 20 Dec 2012 22:45:51 +0000
Received: from mail57-co9 (localhost [127.0.0.1])	by mail57-co9-R.bigfish.com (Postfix) with ESMTP id EF794C202EC	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Thu, 20 Dec 2012 22:45:50 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -6
X-BigFish: PS-6(zzbb2dI98dI9371I542I1432I1418Izz1de0h1202h1e76h1d1ah1d2ahzz8275ch17326ah8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail57-co9 (localhost.localdomain [127.0.0.1]) by mail57-co9 (MessageSwitch) id 1356043535973444_27127; Thu, 20 Dec 2012 22:45:35 +0000 (UTC)
Received: from CO9EHSMHS030.bigfish.com (unknown [10.236.132.226])	by mail57-co9.bigfish.com (Postfix) with ESMTP id E9113C0004A; Thu, 20 Dec 2012 22:45:35 +0000 (UTC)
Received: from BY2PRD0512HT001.namprd05.prod.outlook.com (157.56.238.5) by CO9EHSMHS030.bigfish.com (10.236.130.40) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 20 Dec 2012 22:45:31 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.183]) by BY2PRD0512HT001.namprd05.prod.outlook.com ([10.255.243.34]) with mapi id 14.16.0245.002; Thu, 20 Dec 2012 22:45:30 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Geoff Huston <gih@apnic.net>
Subject: RE: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Thread-Topic: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Thread-Index: AQHN0a2Axj+tti3hy0eMTTRNNHnpApgiYkAg
Date: Thu, 20 Dec 2012 22:45:30 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501DF3B80@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2501DBADD2@BY2PRD0512MB653.namprd05.prod.outlook.com> <62AB342F-F2C0-4B06-B137-47CB7047BCB2@apnic.net>
In-Reply-To: <62AB342F-F2C0-4B06-B137-47CB7047BCB2@apnic.net>
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%APNIC.NET$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
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, 20 Dec 2012 22:47:46 -0000

Geoff,

I have just posted a new version of the draft, adding a column that disting=
uishes between reservations and allocations. In this version, our goal is t=
o preserve the distinction between reservations and allocations while provi=
ding a single compendium of special addresses.

Please take a look and tell me if we have solved the problem.

                                   Ron


> -----Original Message-----
> From: Geoff Huston [mailto:gih@apnic.net]
> Sent: Monday, December 03, 2012 6:25 PM
> To: Ronald Bonica
> Cc: Randy Bush; IETF Discussion
> Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-
> Purpose Address Registries) to Best Current Practice
>=20
>=20
> On 04/12/2012, at 9:30 AM, Ronald Bonica <rbonica@juniper.net> wrote:
>=20
> > Geoff, Randy,
> >
> > Having reflected on your comments, I think that the two of you may be
> approaching the same problem from two directions. I will try my best to
> articulate the problem. When we agree that we have a common
> understanding of the problem, we can decide whether to fix draft-bonica
> or abandon it.
> >
> > Geoff points out that each of the entries mentioned in draft-bonica
> can be characterized as one of the following:
> >
> > - a special purpose address assignment
> > - a address reservation
> >
> > All compliant IP implementations must respect special purpose address
> assignments. As Randy puts it, special purpose address assignments
> should be baked into IP stacks.
> >
> > However, the same is not true of address reservations. While
> operators may afford special treatment to packets that are sourced from
> or destined to reserved addresses, these treatments should not be baked
> into IP implementations. They should be configurable.
> >
> > Currently, there is nothing in draft-bonica that distinguishes
> between special purpose address assignments and address reservations.
> If we were to continue with this draft, we would have to add a field
> that makes this distinction. Having added that field, we should also
> make clear that that field, and only that field, determines whether an
> address should be baked into IP stacks?
> >
> > Randy, Geoff, have I restated the problem accurately?
> >
>=20
>=20
> I'd use the opposite terminology. e.g.:
>=20
>   - I regard 0.0.0.0/8 as a "reservation", and should be baked into IP
> stacks
>=20
>   - I regard 192.88.99.0/24 as a "special purpose assignment" and is
> configurable by IP stacks.
>=20
> In IPv4 my understanding of the current set of "reservations" are:
>=20
>   0.0.0.0/8
>   127.0.0.0/8
>   169.254.0.0/16
>   224.0.0.0/4
>   240.0.0.0/4
>=20
> All others I would see as being special purpose assignments, given that
> they do not require special baked-in treatment by IP stacks.
>=20
> My personal preference would be to:
>=20
> --  record all special purpose assignments in a special purpose
> assignment registry, such as http://www.iana.org/assignments/iana-ipv4-
> special-registry/iana-ipv4-special-registry.xml for Ipv4
>=20
>=20
> -- record all reservations in the address protocol registry, such as
> http://www.iana.org/assignments/ipv4-address-space/ipv4-address-
> space.xml for Ipv4
>=20
>=20
> regards,
>=20
>    Geoff
>=20
>=20
>=20
>=20



From gih@apnic.net  Thu Dec 20 15:15:12 2012
Return-Path: <gih@apnic.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 2CA7521F8A89 for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 15:15:12 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xw86O1T9RP8K for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 15:15:11 -0800 (PST)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by ietfa.amsl.com (Postfix) with ESMTP id 1096021F8983 for <ietf@ietf.org>; Thu, 20 Dec 2012 15:15:10 -0800 (PST)
Received: from [IPv6:2001:388:1000:110:90c7:d931:423d:474d] (unknown [IPv6:2001:388:1000:110:90c7:d931:423d:474d]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 0F686B6745; Fri, 21 Dec 2012 09:15:07 +1000 (EST)
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=us-ascii
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2501DF3B80@BY2PRD0512MB653.namprd05.prod.outlook.com>
Date: Fri, 21 Dec 2012 10:15:08 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F33523EF-38C5-4049-BC2A-C939D082FFC2@apnic.net>
References: <2CF4CB03E2AA464BA0982EC92A02CE2501DBADD2@BY2PRD0512MB653.namprd05.prod.outlook.com> <62AB342F-F2C0-4B06-B137-47CB7047BCB2@apnic.net> <2CF4CB03E2AA464BA0982EC92A02CE2501DF3B80@BY2PRD0512MB653.namprd05.prod.outlook.com>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1499)
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, 20 Dec 2012 23:15:12 -0000

Hi Ron,

I'm pleased to see the addition of this column and the recognition of =
this distinction between reservations in the protocol's address plan and =
special purpose assignments being made . This is a useful step forward.

Personally, I think that the two sets of addresses belong in different =
registries, but I'm willing to recognise this as a matter of personal =
taste and not a fundamental objection to the further progress of the =
document per se (i.e. for me its more of a matter of registry management =
style - I would advocate the protocol's address plan should be recorded =
in a single registry, and special purpose assignments recorded in a =
special purpose assignment registry)

So: "solved?" For me, it's a 51% solution: solved, but could do better =
:-)

cheers,

   Geoff



=20
On 21/12/2012, at 9:45 AM, Ronald Bonica <rbonica@juniper.net> wrote:

> Geoff,
>=20
> I have just posted a new version of the draft, adding a column that =
distinguishes between reservations and allocations. In this version, our =
goal is to preserve the distinction between reservations and allocations =
while providing a single compendium of special addresses.
>=20
> Please take a look and tell me if we have solved the problem.
>=20
>                                   Ron
>=20
>=20
>> -----Original Message-----
>> From: Geoff Huston [mailto:gih@apnic.net]
>> Sent: Monday, December 03, 2012 6:25 PM
>> To: Ronald Bonica
>> Cc: Randy Bush; IETF Discussion
>> Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> =
(Special-
>> Purpose Address Registries) to Best Current Practice
>>=20
>>=20
>> On 04/12/2012, at 9:30 AM, Ronald Bonica <rbonica@juniper.net> wrote:
>>=20
>>> Geoff, Randy,
>>>=20
>>> Having reflected on your comments, I think that the two of you may =
be
>> approaching the same problem from two directions. I will try my best =
to
>> articulate the problem. When we agree that we have a common
>> understanding of the problem, we can decide whether to fix =
draft-bonica
>> or abandon it.
>>>=20
>>> Geoff points out that each of the entries mentioned in draft-bonica
>> can be characterized as one of the following:
>>>=20
>>> - a special purpose address assignment
>>> - a address reservation
>>>=20
>>> All compliant IP implementations must respect special purpose =
address
>> assignments. As Randy puts it, special purpose address assignments
>> should be baked into IP stacks.
>>>=20
>>> However, the same is not true of address reservations. While
>> operators may afford special treatment to packets that are sourced =
from
>> or destined to reserved addresses, these treatments should not be =
baked
>> into IP implementations. They should be configurable.
>>>=20
>>> Currently, there is nothing in draft-bonica that distinguishes
>> between special purpose address assignments and address reservations.
>> If we were to continue with this draft, we would have to add a field
>> that makes this distinction. Having added that field, we should also
>> make clear that that field, and only that field, determines whether =
an
>> address should be baked into IP stacks?
>>>=20
>>> Randy, Geoff, have I restated the problem accurately?
>>>=20
>>=20
>>=20
>> I'd use the opposite terminology. e.g.:
>>=20
>>  - I regard 0.0.0.0/8 as a "reservation", and should be baked into IP
>> stacks
>>=20
>>  - I regard 192.88.99.0/24 as a "special purpose assignment" and is
>> configurable by IP stacks.
>>=20
>> In IPv4 my understanding of the current set of "reservations" are:
>>=20
>>  0.0.0.0/8
>>  127.0.0.0/8
>>  169.254.0.0/16
>>  224.0.0.0/4
>>  240.0.0.0/4
>>=20
>> All others I would see as being special purpose assignments, given =
that
>> they do not require special baked-in treatment by IP stacks.
>>=20
>> My personal preference would be to:
>>=20
>> --  record all special purpose assignments in a special purpose
>> assignment registry, such as =
http://www.iana.org/assignments/iana-ipv4-
>> special-registry/iana-ipv4-special-registry.xml for Ipv4
>>=20
>>=20
>> -- record all reservations in the address protocol registry, such as
>> http://www.iana.org/assignments/ipv4-address-space/ipv4-address-
>> space.xml for Ipv4
>>=20
>>=20
>> regards,
>>=20
>>   Geoff
>>=20
>>=20
>>=20
>>=20
>=20
>=20

--

Geoff Huston
Chief Scientist, APNIC

+61 7 3858 3100
gih@apnic.net





From presnick@qti.qualcomm.com  Thu Dec 20 15:33:25 2012
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 B659021F8A77 for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 15:33:25 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RU2fykXiDyBZ for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 15:33:24 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id A59C121F8A95 for <ietf@ietf.org>; Thu, 20 Dec 2012 15:33:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1356044731; x=1387580731; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=dPomM+Iux4U810XAjW6MAzQnChShdjC/FqriahGJsPU=; b=LMAvCbPGPnWDlZOVBCZsRwFHAS5MLchoBmrxv6SUtX3ffNJ4qfy4yzn2 4fuaxOD52Im5M+3FREU9e5xl/3T8oVOiWu94L51fKq0KIgPoO55Qq72JJ 1uo8DbPlmccl2Pljr9qZKdnAjYaphsg4y0eLJSoZD/LRYLtfMAdSrPtQI I=;
X-IronPort-AV: E=Sophos;i="4.84,326,1355126400"; d="scan'208";a="12948605"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 20 Dec 2012 15:05:30 -0800
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 20 Dec 2012 15:33:23 -0800
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 20 Dec 2012 15:33:22 -0800
Message-ID: <50D3A040.4090706@qti.qualcomm.com>
Date: Thu, 20 Dec 2012 17:33:20 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt>	(Special-Purpose Address Registries) to Best Current Practice
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121129165519.0a037840@resistor.net>
In-Reply-To: <6.2.5.6.2.20121129165519.0a037840@resistor.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Dec 2012 23:33:25 -0000

I see Ron has gotten back to Geoff and posted a new version of his 
document. Since I've already stuck my nose out with questions before, I 
might as well do so again. (For the record, my DISCUSS on another 
document and the DISCUSS of me and a couple of others on another 
document is what motivated Ron to write this one, so I feel a bit of 
responsibility to make sure this gets done.)

So, some questions for SM:

On 11/29/12 9:22 PM, SM wrote:

> BCP 153 is about Special Use IPv4 addresses.  This intended BCP will 
> create a mishmash as the draft covers both IPv4 and IPv6.  I suggest 
> handling the IP versions in two separate drafts.

I haven't seen anyone jump out of the woodwork in support of splitting 
the document, and the document we've got on the table does it this way. 
Do you think this is important enough to stop the document?

> RFC 5375 is being obsoleted by this draft.  RFC 6598 updates RFC 
> 5375.  Could someone explain that to me (see 
> http://www.rfc-editor.org/errata_search.php?rfc=5375&eid=3309 and the 
> relevant discussion for details)?

I think you've confused the documents. It's 5735, not 5375. So I take it 
this is not relevant, correct?

> The following text is from RFC 3330 which was written by the Internet 
> Assigned Numbers Authority:
>
>   "Throughout its entire history, the Internet has employed a central
>    Internet Assigned Numbers Authority (IANA) responsible for the
>    allocation and assignment of various identifiers needed for the
>    operation of the Internet [RFC1174].  In the case of the IPv4 address
>    space, the IANA allocates parts of the address space to Regional
>    Internet Registries according to their established needs.  These
>    Regional Internet Registries are responsible for the assignment of
>    IPv4 addresses to operators and users of the Internet within their
>    regions.
>
>    [paragraph omitted]
>
>    On an ongoing basis, the IANA has been designated by the IETF to make
>    assignments in support of the Internet Standards Process [RFC2860].
>    Section 4 of this document describes that assignment process."
>
> The text was also present in RFC 5735.  I unfortunately have to object 
> to the disappearance of that text.

This document does not change 2860 and it doesn't change 1174. So this 
policy associated with this text is still in place, whether or not we 
repeat the above paragraphs. Putting this text in seems unimportant and 
I haven't seen support to do so. Can you explain how important this 
objection is? Again, do you see this as a reason not to go forward?

> RFC 5736 provides direction to IANA concerning the creation and 
> management of the IANA IPv4 Special Purpose Address Registry.   The 
> information in RFC 5375 is not obsolete.

We do want 5735 to be obsolete because it is no longer the authoritative 
list of addresses; the registry is. So I think you got that part wrong. 
But you may have a point about *also* obsoleting 5736. I'll leave that 
one to Ron and Ralph.

> From the IANA Considerations Section:

Ron updated this to:

    IANA will update the aforementioned registries as requested in the
    "IANA Considerations" section of an IETF reviewed document.  The
    "IANA Considerations" section must include all of the information
    specified in Section 2.1 of this document.


> RFC 5735 mentions that:
>
>   "Among other things, [RFC2860] requires that protocol parameters be
>    assigned according to the criteria and procedures specified in
>    RFCs, including Proposed, Draft, and full Internet Standards and
>    Best Current Practice documents, and any other RFC that calls for
>    IANA assignment."
>
> This draft changes it.

I don't understand what you mean here. Are you suggesting that this 
document updates 2860, or somehow changes something in 2860? It does not 
AFAICT. Please explain.

pr

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


From d3e3e3@gmail.com  Thu Dec 20 16:57:38 2012
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 F123C21E8034 for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 16:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.38
X-Spam-Level: 
X-Spam-Status: No, score=-103.38 tagged_above=-999 required=5 tests=[AWL=0.219, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8R3r9aIxPTqF for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 16:57:38 -0800 (PST)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id E83A921E8039 for <ietf@ietf.org>; Thu, 20 Dec 2012 16:57:33 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id qd14so5414779ieb.6 for <ietf@ietf.org>; Thu, 20 Dec 2012 16:57:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=nVa7O1fsyY5b0qc9KQ/soWFdec7c54qcAKBEBdR5wtY=; b=p+dBIcDMgie3CM8sxNe4+F4V+/DnBwAVcZBOFBS/n/Y31D82JemLwiCSUMHKuIFnq1 /mTgZyEKukoO+qznMnEFtYAPz9+i5Vm5mFUOmSqcFXxWPy6L159zBy+7c+ck2yAgk1Un /wOGqoFph4es4vo5U1dlVco+aAIWq1xWVcFPhVhklNrqNZX5Ayd2xC2pPgQa3yRtdXCT IlJZ0yjrs05xeVeJI4Q5qoF90syKwUiLvC12YH2ptuYZW9aXyi4kIFyfjZZzCJ3tExzd neUVhR0AhZNR0CuEust6zaFDy5hTRh2qKOmrqx61fijfdEf45Hb9tpLxdx0oX/Ycx3Cj 7qgA==
Received: by 10.43.114.135 with SMTP id fa7mr10445679icc.21.1356051453369; Thu, 20 Dec 2012 16:57:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.28.209 with HTTP; Thu, 20 Dec 2012 16:57:13 -0800 (PST)
In-Reply-To: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 20 Dec 2012 19:57:13 -0500
Message-ID: <CAF4+nEGUr5shY2+BRJJAVPrf8ExbUHzo+u5szKhno6Y8bQ2NRA@mail.gmail.com>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose Address Registries) to Best Current Practice
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: Fri, 21 Dec 2012 00:57:39 -0000

How about changing the title from "Special-Purpose Address Registries"
to "Special-Purpose IP Address Registries".

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


On Thu, Nov 29, 2012 at 3:55 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Special-Purpose Address Registries'
>   <draft-bonica-special-purpose-03.txt> as Best Current Practice
>
> 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-01-02. 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 memo instructs IANA to restructure its IPv4 and IPv6 Special-
>    Purpose Address Registries.  Upon restructuring, the aforementioned
>    registries will record all special-purpose address blocks,
>    maintaining a common set of information regarding each address block.
>
>    This memo updates RFC 5736 and RFC 4773, which define the current
>    structure of the IPv4 and IPv6 Special-Purpose Address Registries.
>    It also obsoletes RFC 5735 and RFC 5156 which document special-
>    purpose address blocks that are not currently, but will in the
>    future, be recorded in the IPv4 and IPv6 Special-Purpose Address
>    Registries.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-bonica-special-purpose/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-bonica-special-purpose/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>

From narten@us.ibm.com  Thu Dec 20 21:53:10 2012
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 CFAB321F89D3 for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 21:53:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTNDn9b7QZqL for <ietf@ietfa.amsl.com>; Thu, 20 Dec 2012 21:53:09 -0800 (PST)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id C223821F89C6 for <ietf@ietf.org>; Thu, 20 Dec 2012 21:53:09 -0800 (PST)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 20 Dec 2012 22:53:08 -0700
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 20 Dec 2012 22:53:07 -0700
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 325283E40039 for <ietf@ietf.org>; Thu, 20 Dec 2012 22:53:02 -0700 (MST)
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 qBL5r6Ur235618 for <ietf@ietf.org>; Thu, 20 Dec 2012 22:53:06 -0700
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 qBL5r5FT006216 for <ietf@ietf.org>; Thu, 20 Dec 2012 22:53:05 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qBL5r5c7006199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 20 Dec 2012 22:53:05 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qBL5r4r0019919 for <ietf@ietf.org>; Fri, 21 Dec 2012 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qBL5r3qf019816 for ietf@ietf.org; Fri, 21 Dec 2012 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201212210553.qBL5r3qf019816@rotala.raleigh.ibm.com>
Date: Fri, 21 Dec 2012 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12122105-2398-0000-0000-00000F46D78A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Dec 2012 05:53:10 -0000

Total of 103 messages in the last 7 days.
 
script run at: Fri Dec 21 00:53:03 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.77% |    8 | 13.01% |   141088 | jasnell@gmail.com
 11.65% |   12 |  7.43% |    80612 | mnot@mnot.net
  3.88% |    4 |  8.67% |    94070 | zhou.sujing@zte.com.cn
  6.80% |    7 |  4.36% |    47268 | david.biesack@sas.com
  2.91% |    3 |  6.78% |    73482 | cmortimore@salesforce.com
  4.85% |    5 |  4.70% |    50929 | sayrer@gmail.com
  4.85% |    5 |  3.59% |    38923 | yaronf.ietf@gmail.com
  3.88% |    4 |  3.16% |    34275 | nick@inex.ie
  3.88% |    4 |  2.61% |    28356 | stephen.farrell@cs.tcd.ie
  3.88% |    4 |  2.35% |    25496 | john-ietf@jck.com
  2.91% |    3 |  2.76% |    29932 | markus.lanthaler@gmx.net
  1.94% |    2 |  3.60% |    39070 | matt@mpcm.com
  2.91% |    3 |  1.74% |    18897 | ben@nostrum.com
  1.94% |    2 |  2.47% |    26797 | ron.even.tlv@gmail.com
  1.94% |    2 |  2.22% |    24098 | jmh@joelhalpern.com
  1.94% |    2 |  2.02% |    21882 | daedulus@btconnect.com
  0.97% |    1 |  2.59% |    28048 | ananth@nttmcl.com
  0.97% |    1 |  2.40% |    25980 | sakimura@gmail.com
  1.94% |    2 |  1.29% |    13980 | moore@network-heretics.com
  1.94% |    2 |  1.23% |    13352 | barryleiba@computer.org
  1.94% |    2 |  1.21% |    13117 | d3e3e3@gmail.com
  0.97% |    1 |  2.02% |    21900 | denis.pinkas@bull.net
  1.94% |    2 |  0.94% |    10208 | randy@psg.com
  0.97% |    1 |  1.56% |    16928 | worley@ariadne.com
  0.97% |    1 |  1.15% |    12483 | william.atwood@concordia.ca
  0.97% |    1 |  0.99% |    10729 | rbonica@juniper.net
  0.97% |    1 |  0.91% |     9894 | dromasca@avaya.com
  0.97% |    1 |  0.87% |     9429 | presnick@qti.qualcomm.com
  0.97% |    1 |  0.85% |     9190 | gih@apnic.net
  0.97% |    1 |  0.84% |     9055 | magnus.westerlund@ericsson.com
  0.97% |    1 |  0.80% |     8711 | pbryan@anode.ca
  0.97% |    1 |  0.77% |     8393 | framefritti@gmail.com
  0.97% |    1 |  0.73% |     7887 | mcquilwp@pobox.com
  0.97% |    1 |  0.73% |     7869 | housley@vigilsec.com
  0.97% |    1 |  0.71% |     7736 | mjethanandani@gmail.com
  0.97% |    1 |  0.71% |     7690 | eosterweil@verisign.com
  0.97% |    1 |  0.69% |     7516 | narten@us.ibm.com
  0.97% |    1 |  0.69% |     7459 | james.h.manger@team.telstra.com
  0.97% |    1 |  0.60% |     6503 | vesely@tana.it
  0.97% |    1 |  0.58% |     6236 | martin.thomson@gmail.com
  0.97% |    1 |  0.55% |     5929 | john@jck.com
  0.97% |    1 |  0.54% |     5874 | conte@isoc.org
  0.97% |    1 |  0.54% |     5827 | windy_1@skyhighway.com
  0.97% |    1 |  0.53% |     5775 | chair@ietf.org
  0.97% |    1 |  0.51% |     5528 | amorris@amsl.com
--------+------+--------+----------+------------------------
100.00% |  103 |100.00% |  1084401 | Total


From sm@resistor.net  Fri Dec 21 00:19:00 2012
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 6A3C721F85D2 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 00:19:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.622
X-Spam-Level: 
X-Spam-Status: No, score=-102.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFSAOwYZJP9h for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 00:18:59 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4BB21F857A for <ietf@ietf.org>; Fri, 21 Dec 2012 00:18:59 -0800 (PST)
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 qBL8Ipm4022263; Fri, 21 Dec 2012 00:18:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1356077937; bh=/9v0JMYHdR0D+NijrYiZmj48xSKNhNlB7oHHRf+DSZw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ltq6GarUBp/0G85QytSoc2hZceuT3/3PPw8hKAglG1wBT5j8JI/oOdlRHUcfy0Vh2 R52hru1m0a78JTl9xllJnAMyzapeZcBTIKDLOXi79gHDdoTFmFDdz16jDfiUoLrrYP pcpEdMqc9yLTkRKiitU7P8UqtlHHVlA//beC0gIM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1356077937; i=@resistor.net; bh=/9v0JMYHdR0D+NijrYiZmj48xSKNhNlB7oHHRf+DSZw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=orTYVwIIlW3a2dDahR7A7wYrKMwZr/xQ7LJ9hLKbBdPQimI3AcumowOAH1P365ao+ axbYjoW2NVFunEE7ZTzlX6VWxy4qyUrda6IFGuBhuQ2xhctoFk5gXneyhMjm2sVh47 PFQ/AoHwNwoG+Yi1aK2iupYgHiL+aXyovdmyLRGI=
Message-Id: <6.2.5.6.2.20121220221257.0a828b40@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Dec 2012 23:33:11 -0800
To: Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt>	(Special-Purpose Address Registries) to Best Current Practice
In-Reply-To: <50D3A040.4090706@qti.qualcomm.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121129165519.0a037840@resistor.net> <50D3A040.4090706@qti.qualcomm.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: Fri, 21 Dec 2012 08:19:00 -0000

Hi Pete,
At 15:33 20-12-2012, Pete Resnick wrote:
>I haven't seen anyone jump out of the woodwork in support of 
>splitting the document, and the document we've got on the table does 
>it this way. Do you think this is important enough to stop the document?

No, as I cannot justify this if I follow to the DISCUSS criteria.

>I think you've confused the documents. It's 5735, not 5375. So I 
>take it this is not relevant, correct?

I used RFC 5735 as an example.  There is a message from the person 
who submitted the erratum at 
http://www.ietf.org/mail-archive/web/v6ops/current/msg13689.html 
The threads of the discussion are at 
http://www.ietf.org/mail-archive/web/v6ops/current/msg13645.html and 
http://www.ietf.org/mail-archive/web/v6ops/current/msg13681.html 
It's difficult for the average reader to understand what is the 
current "standard" when document status, "updates" and "obsoletes" 
requires convoluted tracking.

>This document does not change 2860 and it doesn't change 1174. So 
>this policy associated with this text is still in place, whether or 
>not we repeat the above paragraphs. Putting this text in seems 
>unimportant and I haven't seen support to do so. Can you explain how 
>important this objection is? Again, do you see this as a reason not 
>to go forward?

I missed RFC 1174.  I'll drop the objection as your explanation is convincing.

>We do want 5735 to be obsolete because it is no longer the 
>authoritative list of addresses; the registry is. So I think you got 
>that part wrong. But you may have a point about *also* obsoleting 
>5736. I'll leave that one to Ron and Ralph.

Ok.

>I don't understand what you mean here. Are you suggesting that this 
>document updates 2860, or somehow changes something in 2860? It does 
>not AFAICT. Please explain.

No.  Anyway, the probability of such an update being successful is zero. :-)

Regards,
-sm 


From randy@psg.com  Fri Dec 21 06:45:19 2012
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 C4C7221F84F2 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 06:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Li+s0M3P6qOc for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 06:45:19 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 6341921F84E2 for <ietf@ietf.org>; Fri, 21 Dec 2012 06:45:13 -0800 (PST)
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 1Tm3qY-000Nwv-Hv for ietf@ietf.org; Fri, 21 Dec 2012 14:45:10 +0000
Date: Fri, 21 Dec 2012 09:45:10 -0500
Message-ID: <m2pq23mpl5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: draft-bonica-special-purpose-04.txt
In-Reply-To: <m2fw3s2ii7.wl%randy@psg.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <m2fw3s2ii7.wl%randy@psg.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: Fri, 21 Dec 2012 14:45:19 -0000

i remain confused.  i am not being pedantic just to be a pita.  i really
worry that this document will be used to justtify strange brokenness.

from my 2012.11.29 message:

> are the following definitions
> 
>    o  Routable - A boolean value indicating whether a IP datagram whose
>       destination address is drawn from the allocated special-purpose
>       address block is routable (i.e., may traverse more than a single
>       IP interface)
> 
>    o  Global - A boolean value indicating whether a IP datagram whose
>       destination address is drawn from the allocated special-purpose
>       address block is routable beyond a specified administrative
>       domain.
> 
> intended to be baked in hardware, or are they SHOULDs to operators?  i
> look at RFC 1918 space and 127.0.0.0/8 and am not so sure how hard these
> boundaries are meant to be.  i worry because i think we regret how we
> specified (threw away is more like it) E space.
> 
> does the prefix describes a specific prefix length or a covering range?
> 
> e.g. 192.0.0.0/24 is neither routable nor global, while a subnet,
> 192.0.0.0/29, is routable.  i.e. might i route and forward
> 192.0.0.128/25?

another annoying example.

0.0.0.0/8 is said to be not routable, yet we commonly announce it in bgp
(or igp) and propagate it.  a protocol implmentor reading this document
would be justified in preventing the injection of 0.0.0.0/8 into a
routing protocol.  [ let's not get into that it is commonly in the
fib. ]

randy

From presnick@qti.qualcomm.com  Fri Dec 21 07:08:41 2012
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 2A06E21F8507 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:08:41 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BnOCCp0TGJzr for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:08:40 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 451CD21F8503 for <ietf@ietf.org>; Fri, 21 Dec 2012 07:08:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1356101484; x=1387637484; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=GDdOhB1gj1za+VuE5g4SCAaKWZ7wDoJ/e7iGKZg+SKM=; b=b237maeQYlF/EXG5Mim98NYXNFGr4qyuA82Mljr2PTDv8FQn2q5ExzSB B5LoGQMxkyiwnTQ7i1AdX9RAmBVqkr3PF/kjjqYxESV3f/3TIC+k1WZGP 5iUpWcL85TZSf/CGKEjmIzLLTyOcVMKX7td0Ixyv1h8jgpv9qAXSoC+04 U=;
X-IronPort-AV: E=Sophos;i="4.84,329,1355126400"; d="scan'208";a="13043871"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 21 Dec 2012 06:51:24 -0800
X-IronPort-AV: E=Sophos;i="4.84,329,1355126400"; d="scan'208";a="389873888"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Dec 2012 07:08:39 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 21 Dec 2012 07:08:39 -0800
Message-ID: <50D47B76.7010009@qti.qualcomm.com>
Date: Fri, 21 Dec 2012 09:08:38 -0600
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call:	<draft-bonica-special-purpose-03.txt>	(Special-Purpose Address	Registries) to Best Current Practice
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20121129165519.0a037840@resistor.net>	<50D3A040.4090706@qti.qualcomm.com> <6.2.5.6.2.20121220221257.0a828b40@resistor.net>
In-Reply-To: <6.2.5.6.2.20121220221257.0a828b40@resistor.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: Fri, 21 Dec 2012 15:08:41 -0000

On 12/21/12 1:33 AM, SM wrote:

> I used RFC 5735 as an example.  There is a message from the person who 
> submitted the erratum at 
> http://www.ietf.org/mail-archive/web/v6ops/current/msg13689.html The 
> threads of the discussion are at 
> http://www.ietf.org/mail-archive/web/v6ops/current/msg13645.html and 
> http://www.ietf.org/mail-archive/web/v6ops/current/msg13681.html It's 
> difficult for the average reader to understand what is the current 
> "standard" when document status, "updates" and "obsoletes" requires 
> convoluted tracking.

I am still confused. What is the action item here? Do you think 
something needs to be fixed in this document?

pr

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


From john-ietf@jck.com  Fri Dec 21 07:19:02 2012
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 DD91921F84A1 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:19:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIk2bWoMhTm9 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:19:02 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 58BB221F81FE for <ietf@ietf.org>; Fri, 21 Dec 2012 07:19:02 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Tm4NJ-000FeI-LB; Fri, 21 Dec 2012 10:19:01 -0500
Date: Fri, 21 Dec 2012 10:18:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, IETF Disgust <ietf@ietf.org>
Subject: Re: draft-bonica-special-purpose-04.txt
Message-ID: <28A2D5674B95DFE938946F9C@JcK-HP8200.jck.com>
In-Reply-To: <m2pq23mpl5.wl%randy@psg.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <m2fw3s2ii7.wl%randy@psg.com> <m2pq23mpl5.wl%randy@psg.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, 21 Dec 2012 15:19:03 -0000

--On Friday, December 21, 2012 09:45 -0500 Randy Bush
<randy@psg.com> wrote:

> i remain confused.  i am not being pedantic just to be a pita.
> i really worry that this document will be used to justtify
> strange brokenness.
> 
> from my 2012.11.29 message:
>...
>> e.g. 192.0.0.0/24 is neither routable nor global, while a
>> subnet, 192.0.0.0/29, is routable.  i.e. might i route and
>> forward 192.0.0.128/25?
> 
> another annoying example.
> 
> 0.0.0.0/8 is said to be not routable, yet we commonly announce
> it in bgp (or igp) and propagate it.  a protocol implmentor
> reading this document would be justified in preventing the
> injection of 0.0.0.0/8 into a routing protocol.  [ let's not
> get into that it is commonly in the fib. ]

And a slightly-related one.  At least one prominent ISP is not
giving IPv4 addresses out to its small business customers as
a.b.c.d/N with the boundary router address at the top or bottom
of that range.  Instead, it is giving out a "range" of a.b.c.d -
a.b.c.e (e > d >> 1) and then telling the customer to use
a.b.c.1 as the boundary router address.    Is that prohibited?
Can one route from a.b.c.y to a.b.c.x  (1 << x < d < y < e) and
do any our definitions make that harder or easier?

Like Geoff, I have an opinion about how the registry(/ies)
should be organized but believe that is a matter of taste as
long as the information is correct and clear.   

But anything that defines one of these terms or restates the
definitions must be absolutely precise and clear lest we cause
ourselves real problems down the line.

    john



From ben@nostrum.com  Fri Dec 21 07:40:24 2012
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 3C6E021F85D7; Fri, 21 Dec 2012 07:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNp20WY0A2vh; Fri, 21 Dec 2012 07:40:23 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id AD78321F8ADA; Fri, 21 Dec 2012 07:40:17 -0800 (PST)
Received: from [10.0.1.14] (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 qBLFeGCi096183 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 09:40:16 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
Date: Fri, 21 Dec 2012 09:40:18 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C2DB2B9-B9DD-444B-B760-DED177907291@nostrum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
To: RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, "ietf@ietf.org List" <ietf@ietf.org>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.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, 21 Dec 2012 15:40:24 -0000

Thanks for the timely response, and the background for the security =
language.=20

This brings up one question, however. See inline:=20

Thanks!

Ben.

On Dec 21, 2012, at 6:48 AM, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com> =
wrote:

> Hi Ben,
>=20
> Thank you for your review comments.
> Please find my responses inline below.
>=20
> Regards,
> Ramakrishna DTV.
>=20
>> -----Original Message-----
>> From: Ben Campbell [mailto:ben@nostrum.com]
>> Sent: Thursday, December 20, 2012 2:45 AM
>> To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
>> Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
>> Subject: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
>>=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-dhc-relay-id-suboption-11
>> Reviewer: Ben Campbell
>> Review Date: 2012-12-19
>> IETF LC End Date: 2013-01-07
>>=20
>> Summary: This draft is basically ready for publication as a proposed
>> standard. However, there is one comment from a prior review that I am
>> not sure whether is resolved.
>>=20
>> Major issues:
>>=20
>> None
>>=20
>> Minor issues:
>>=20
>> -- In Sean Turner's 2009 review of version 07 of the document [
>> http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ], =
he
>> made the following comment:
>>=20
>>> In the security considerations it says look to RFC 3046 and
>>> RFC 4030 for security considerations and then says SHOULD use the
>> relay
>>> agent authentication option from RFC 4030.  RFC 3046 is targeted at
>>> network infrastructures that are "trusted and secure" and RFC 4030
>>> allows the relay agent to be part of this trusted and secure =
network.
>>> If an implementation doesn't use the relay agent authentication
>> option,
>>> then the relay agent can't be part of the "trusted and secure"
>> network.
>=20
> RFC3046 created the relay agent information option.
> Relay agent information option exists only in the messages between
> relay agents and DHCP servers. RFC3046 is targeted at network =
infrastructures
> that are "trusted and secure" as far as the paths among relay agents =
and DHCP
> servers is concerned. In many deployments, relay agents and DHCP =
servers
> are under a single administrative control. By careful design and =
engineering
> of the network, it is possible to ensure that the network =
infrastructure
> comprising relay agents and DHCP server is trusted and secure. To =
achieve that,
> RFC4030 may be used but is not a MUST. If not, RFC4030 would already =
be a MUST
> for RFC3046 deployment. But that is not currently the case.

Is the SHOULD use 4030 language a new normative requirement, or is it =
simply describing existing requirements from 3046 or elsewhere?  If it's =
a new normative requirement, then I am fine with your answer and =
withdraw the concern. If not, then it would be better to use descriptive =
rather than normative language in this draft.


>=20
>>> This makes me think that the relay agent authentication option from
>>> RFC 4030 ought to be a MUST not a SHOULD?
>>=20
>> I can't tell from the resulting conversation if that comment is
>> addressed in the current text. Additional text has been added, but =
the
>> SHOULD remains. I'm willing to accept it has been addressed if the
>> author's say so--I only mention it to make sure it didn't fall =
through a
>> crack.
>>=20
>=20
> We have indeed discussed about this comment and addressed it.
>=20
> The following was a related comment from DHC WG Chair (Ted Lemon)
> (http://www.ietf.org/mail-archive/web/gen-art/current/msg04615.html):
>=20
> 	"This document makes no changes to practice that require more or =
less security
> 	than is provided by existing relay agent options in RFC3046. =
Thus, the
> 	security considerations in RFC3046 should be adequate."
>=20
> As Ted mentioned, our draft only proposes a new sub-option for =
relay-agent
> option which was originally created as part of RFC3046. So, the =
security
> considerations for RFC3046 apply to our draft as well. RFC3046 =
deployments may
> use RFC4030 as explained above. So, we indicated in our draft to refer =
to
> both RFC3046 and RFC4030. But there are no specific security issues in =
the
> new relay-id sub-option itself to make RFC4030 a MUST.
>=20
>=20
>> Nits/editorial comments:
>>=20
>> -- section 5, last paragraph:
>>=20
>> I suggest removing the scare quotes around "stability". If there are
>> concerns about whether such stability is real, it would be better to =
say
>> that directly.
>>=20
>=20
> There is no need for these scare quotes. We will remove them.
>=20
>> -- informative references:
>>=20
>> draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07
>=20
> We will update this.
>=20
>>=20
>=20
> **************** CAUTION - Disclaimer *****************
> This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended =
solely
> for the use of the addressee(s). If you are not the intended =
recipient, please
> notify the sender by e-mail and delete the original message. Further, =
you are not
> to copy, disclose, or distribute this e-mail or its contents to any =
other person and
> any such actions are unlawful. This e-mail may contain viruses. =
Infosys has taken
> every reasonable precaution to minimize this risk, but is not liable =
for any damage
> you may sustain as a result of any virus in this e-mail. You should =
carry out your
> own virus checks before opening the e-mail or attachment. Infosys =
reserves the
> right to monitor and review the content of all messages sent to or =
from this e-mail
> address. Messages sent to or from this e-mail address may be stored on =
the
> Infosys e-mail system.
> ***INFOSYS******** End of Disclaimer ********INFOSYS***


From rbonica@juniper.net  Fri Dec 21 07:44:18 2012
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 2538D21F8625 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.357
X-Spam-Level: 
X-Spam-Status: No, score=-103.357 tagged_above=-999 required=5 tests=[AWL=0.110, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B27OtkJK9qld for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:44:14 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5A021F860D for <ietf@ietf.org>; Fri, 21 Dec 2012 07:44:14 -0800 (PST)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUNSDzUgvx3KBXNiWysb9VavkK3PhlSXs@postini.com; Fri, 21 Dec 2012 07:44:14 PST
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 21 Dec 2012 07:42:21 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 21 Dec 2012 07:42:20 -0800
Received: from CH1EHSOBE020.bigfish.com (216.32.181.183) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 21 Dec 2012 07:49:46 -0800
Received: from mail40-ch1-R.bigfish.com (10.43.68.240) by CH1EHSOBE020.bigfish.com (10.43.70.77) with Microsoft SMTP Server id 14.1.225.23; Fri, 21 Dec 2012 15:42:19 +0000
Received: from mail40-ch1 (localhost [127.0.0.1])	by mail40-ch1-R.bigfish.com (Postfix) with ESMTP id 8C5CB3001E5	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 21 Dec 2012 15:42:19 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -40
X-BigFish: PS-40(zz98dI9371I542I1432Ibf3W4015Izz1de0h1202h1e76h1d1ah1d2ahzz1033IL17326ah8275bh8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail40-ch1 (localhost.localdomain [127.0.0.1]) by mail40-ch1 (MessageSwitch) id 1356104538409447_9565; Fri, 21 Dec 2012 15:42:18 +0000 (UTC)
Received: from CH1EHSMHS004.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.244])	by mail40-ch1.bigfish.com (Postfix) with ESMTP id 55800460139;	Fri, 21 Dec 2012 15:42:18 +0000 (UTC)
Received: from BY2PRD0512HT001.namprd05.prod.outlook.com (157.56.238.5) by CH1EHSMHS004.bigfish.com (10.43.70.4) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 21 Dec 2012 15:42:18 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.183]) by BY2PRD0512HT001.namprd05.prod.outlook.com ([10.255.243.34]) with mapi id 14.16.0245.002; Fri, 21 Dec 2012 15:42:17 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Donald Eastlake <d3e3e3@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Thread-Topic: Last Call: <draft-bonica-special-purpose-03.txt> (Special-Purpose	Address Registries) to Best Current Practice
Thread-Index: AQHN3xYcxj+tti3hy0eMTTRNNHnpApgjZS8g
Date: Fri, 21 Dec 2012 15:42:16 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501DF485A@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <CAF4+nEGUr5shY2+BRJJAVPrf8ExbUHzo+u5szKhno6Y8bQ2NRA@mail.gmail.com>
In-Reply-To: <CAF4+nEGUr5shY2+BRJJAVPrf8ExbUHzo+u5szKhno6Y8bQ2NRA@mail.gmail.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%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.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: Fri, 21 Dec 2012 15:44:18 -0000

Sure. I'll catch that in the next rev.

                Ron


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Donald Eastlake
> Sent: Thursday, December 20, 2012 7:57 PM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-bonica-special-purpose-03.txt> (Special-
> Purpose Address Registries) to Best Current Practice
>=20
> How about changing the title from "Special-Purpose Address Registries"
> to "Special-Purpose IP Address Registries".
>=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
>=20
> On Thu, Nov 29, 2012 at 3:55 PM, The IESG <iesg-secretary@ietf.org>
> wrote:
> >
> > The IESG has received a request from an individual submitter to
> > consider the following document:
> > - 'Special-Purpose Address Registries'
> >   <draft-bonica-special-purpose-03.txt> as Best Current Practice
> >
> > 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-01-02. 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 memo instructs IANA to restructure its IPv4 and IPv6 Special-
> >    Purpose Address Registries.  Upon restructuring, the
> aforementioned
> >    registries will record all special-purpose address blocks,
> >    maintaining a common set of information regarding each address
> block.
> >
> >    This memo updates RFC 5736 and RFC 4773, which define the current
> >    structure of the IPv4 and IPv6 Special-Purpose Address Registries.
> >    It also obsoletes RFC 5735 and RFC 5156 which document special-
> >    purpose address blocks that are not currently, but will in the
> >    future, be recorded in the IPv4 and IPv6 Special-Purpose Address
> >    Registries.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-bonica-special-purpose/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-bonica-special-purpose/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >



From ben@nostrum.com  Fri Dec 21 07:45:15 2012
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 98B1F21F8CEC; Fri, 21 Dec 2012 07:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.484
X-Spam-Level: 
X-Spam-Status: No, score=-102.484 tagged_above=-999 required=5 tests=[AWL=0.116, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfaa02TCtIAY; Fri, 21 Dec 2012 07:45:15 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id ADB0621F8C31; Fri, 21 Dec 2012 07:45:14 -0800 (PST)
Received: from [10.0.1.14] (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 qBLFjDUE096742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 09:45:13 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com>
Date: Fri, 21 Dec 2012 09:45:15 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com> <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.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: Fri, 21 Dec 2012 15:45:15 -0000

On Dec 21, 2012, at 8:27 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Dec 21, 2012, at 7:48 AM, RAMAKRISHNADTV =
<RAMAKRISHNADTV@infosys.com> wrote:
>> As Ted mentioned, our draft only proposes a new sub-option for =
relay-agent=20
>> option which was originally created as part of RFC3046. So, the =
security=20
>> considerations for RFC3046 apply to our draft as well. RFC3046 =
deployments may
>> use RFC4030 as explained above. So, we indicated in our draft to =
refer to=20
>> both RFC3046 and RFC4030. But there are no specific security issues =
in the=20
>> new relay-id sub-op
>> tion itself to make RFC4030 a MUST.
>=20
> To put it a bit differently, changing the security considerations for =
RFC3046 is out of scope for this document.   It could certainly be =
argued that the security considerations for RFC3046 are too weak, but if =
that is an argument that someone wants to make, the argument should be =
made in the context of updating RFC3046, not in the context of adding a =
new DHCP relay option.
>=20

Thanks Ted, that makes perfect sense.=20

As I responded separately to Ramakrishna, is the SHOULD use 4030 =
language a new requirement specific to this draft? Or is it just =
describing requirements in 3046 or elsewhere?

Thanks!

Ben.=

From rbonica@juniper.net  Fri Dec 21 07:51:11 2012
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 7CEC121F8625 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.36
X-Spam-Level: 
X-Spam-Status: No, score=-103.36 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mu4yhHQZPIOc for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 07:51:11 -0800 (PST)
Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by ietfa.amsl.com (Postfix) with ESMTP id D8FDD21F85C3 for <ietf@ietf.org>; Fri, 21 Dec 2012 07:51:10 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKUNSFboJiEiLA2WZihGGjiU0xJHkDRL3U@postini.com; Fri, 21 Dec 2012 07:51:10 PST
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 21 Dec 2012 07:49:12 -0800
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 21 Dec 2012 07:49:12 -0800
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.141) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 21 Dec 2012 07:56:38 -0800
Received: from mail51-db3-R.bigfish.com (10.3.81.249) by DB3EHSOBE002.bigfish.com (10.3.84.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 21 Dec 2012 15:49:10 +0000
Received: from mail51-db3 (localhost [127.0.0.1])	by mail51-db3-R.bigfish.com (Postfix) with ESMTP id 2E8422E0161	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 21 Dec 2012 15:49:10 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.238.5; KIP:(null); UIP:(null); (null); H:BY2PRD0512HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -23
X-BigFish: PS-23(zz9371I542I1432Izz1de0h1202h1e76h1d1ah1d2ahzz1033IL8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h1155h)
Received: from mail51-db3 (localhost.localdomain [127.0.0.1]) by mail51-db3 (MessageSwitch) id 135610494794252_28918; Fri, 21 Dec 2012 15:49:07 +0000 (UTC)
Received: from DB3EHSMHS009.bigfish.com (unknown [10.3.81.240])	by mail51-db3.bigfish.com (Postfix) with ESMTP id 0B5F318005A; Fri, 21 Dec 2012 15:49:07 +0000 (UTC)
Received: from BY2PRD0512HT003.namprd05.prod.outlook.com (157.56.238.5) by DB3EHSMHS009.bigfish.com (10.3.87.109) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 21 Dec 2012 15:49:05 +0000
Received: from BY2PRD0512MB653.namprd05.prod.outlook.com ([169.254.5.183]) by BY2PRD0512HT003.namprd05.prod.outlook.com ([10.255.243.36]) with mapi id 14.16.0245.002; Fri, 21 Dec 2012 15:49:04 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Randy Bush <randy@psg.com>, IETF Disgust <ietf@ietf.org>
Subject: RE: draft-bonica-special-purpose-04.txt
Thread-Topic: draft-bonica-special-purpose-04.txt
Thread-Index: AQHN34nnK3aq1YMHUkaRiaBj3e6hRJgjZZ9w
Date: Fri, 21 Dec 2012 15:49:04 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2501DF489D@BY2PRD0512MB653.namprd05.prod.outlook.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <m2fw3s2ii7.wl%randy@psg.com> <m2pq23mpl5.wl%randy@psg.com>
In-Reply-To: <m2pq23mpl5.wl%randy@psg.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%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.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: Fri, 21 Dec 2012 15:51:11 -0000

Hi Randy,

It seems that we need one or both or the following:

- a better title for the new column
- a better definition to be associated with that column

Any suggestions?

              Ron


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Randy Bush
> Sent: Friday, December 21, 2012 9:45 AM
> To: IETF Disgust
> Subject: draft-bonica-special-purpose-04.txt
>=20
> i remain confused.  i am not being pedantic just to be a pita.  i
> really worry that this document will be used to justtify strange
> brokenness.
>=20
> from my 2012.11.29 message:
>=20
> > are the following definitions
> >
> >    o  Routable - A boolean value indicating whether a IP datagram
> whose
> >       destination address is drawn from the allocated special-purpose
> >       address block is routable (i.e., may traverse more than a
> single
> >       IP interface)
> >
> >    o  Global - A boolean value indicating whether a IP datagram whose
> >       destination address is drawn from the allocated special-purpose
> >       address block is routable beyond a specified administrative
> >       domain.
> >
> > intended to be baked in hardware, or are they SHOULDs to operators?
> i
> > look at RFC 1918 space and 127.0.0.0/8 and am not so sure how hard
> > these boundaries are meant to be.  i worry because i think we regret
> > how we specified (threw away is more like it) E space.
> >
> > does the prefix describes a specific prefix length or a covering
> range?
> >
> > e.g. 192.0.0.0/24 is neither routable nor global, while a subnet,
> > 192.0.0.0/29, is routable.  i.e. might i route and forward
> > 192.0.0.128/25?
>=20
> another annoying example.
>=20
> 0.0.0.0/8 is said to be not routable, yet we commonly announce it in
> bgp (or igp) and propagate it.  a protocol implmentor reading this
> document would be justified in preventing the injection of 0.0.0.0/8
> into a routing protocol.  [ let's not get into that it is commonly in
> the fib. ]
>=20
> randy



From ben@nostrum.com  Fri Dec 21 08:37:16 2012
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 07F1221F874E; Fri, 21 Dec 2012 08:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.492
X-Spam-Level: 
X-Spam-Status: No, score=-102.492 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UN6QhA2-z0og; Fri, 21 Dec 2012 08:37:15 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE4B21F872C; Fri, 21 Dec 2012 08:37:15 -0800 (PST)
Received: from [10.0.1.14] (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 qBLGb8tK002567 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 10:37:09 -0600 (CST) (envelope-from ben@nostrum.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B630747441AF5@mbx-01.win.nominum.com>
Date: Fri, 21 Dec 2012 10:37:10 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D859D9D-D1F5-4AD4-855E-9D193A7084B2@nostrum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com> <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com> <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com> <8D23D4052ABE7A4490E77B1A012B630747441AF5@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.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: Fri, 21 Dec 2012 16:37:16 -0000

On Dec 21, 2012, at 10:06 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Dec 21, 2012, at 10:45 AM, Ben Campbell <ben@nostrum.com> wrote:
>> As I responded separately to Ramakrishna, is the SHOULD use 4030 =
language a new requirement specific to this draft? Or is it just =
describing requirements in 3046 or elsewhere?
>=20
> I suppose the authors should really answer this, but I was curious as =
well, and went looking.   I think RFC4030 should have updated RFC3046 to =
add this as a security consideration, but it did not.   However, e.g. =
RFC4243, RFC5010 and RFC5107 do add a similar requirement to their =
security considerations section, so it's probably fair to say that this =
has been informally adopted as appropriate practice for security =
considerations sections.  =20
>=20
> Perhaps we should adopt the practice more formally... :)

Pending the authors' comments, it sounds like it's good as is. (Assuming =
that "adopt[ing] the practice more formally" isn't _this_ draft's =
problem :-)  )

>=20


From peter@akayla.com  Thu Dec 20 09:55:25 2012
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 1D76921F8A58; Thu, 20 Dec 2012 09:55:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuEeQt5NniV7; Thu, 20 Dec 2012 09:55:24 -0800 (PST)
Received: from m1plsmtpa01-08.prod.mesa1.secureserver.net (m1plsmtpa01-08.prod.mesa1.secureserver.net [64.202.165.187]) by ietfa.amsl.com (Postfix) with ESMTP id 373A521F8A56; Thu, 20 Dec 2012 09:55:24 -0800 (PST)
Received: from spectre ([173.8.184.78]) by m1plsmtpa01-08.prod.mesa1.secureserver.net with  id dtvJ1k0061huGat01tvNsd; Thu, 20 Dec 2012 10:55:23 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-avt-rtp-evrc-nw.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-avt-rtp-evrc-nw-0
Date: Thu, 20 Dec 2012 09:55:34 -0800
Message-ID: <049f01cddedb$38f6e0c0$aae4a240$@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: Ac3e2rXiaYaUgbG0Sl+xMZvnSdc1cw==
Content-Language: en-us
X-Mailman-Approved-At: Fri, 21 Dec 2012 09:20:04 -0800
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: Thu, 20 Dec 2012 17:55:25 -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-avt-rtp-evrc-nw-09
Reviewer: Peter Yee
Review Date: Dec-19-2012
IETF LC End Date: Dec-11-2012
IESG Telechat date: Dec-20-2012

Summary: This draft is ready for publication as a Standards Track RFC.



From RAMAKRISHNADTV@infosys.com  Fri Dec 21 04:48:38 2012
Return-Path: <RAMAKRISHNADTV@infosys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19BA21F84FB; Fri, 21 Dec 2012 04:48:38 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TwqIW5rQDMAu; Fri, 21 Dec 2012 04:48:37 -0800 (PST)
Received: from KECGATE08.infosys.com (kecgate08.infosysconsulting.com [122.98.10.33]) by ietfa.amsl.com (Postfix) with ESMTP id EA2D421F84F5; Fri, 21 Dec 2012 04:48:36 -0800 (PST)
X-TM-IMSS-Message-ID: <5051633600276dbe@infosys.com>
Received: from blrkechub01.ad.infosys.com ([10.66.236.41]) by infosys.com ([122.98.10.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 5051633600276dbe ; Fri, 21 Dec 2012 18:23:03 +0530
Received: from BLRKECHUB07.ad.infosys.com (10.66.236.117) by blrkechub01.ad.infosys.com (10.66.236.41) with Microsoft SMTP Server (TLS) id 8.2.176.0; Fri, 21 Dec 2012 18:18:12 +0530
Received: from BLRKECMBX23.ad.infosys.com ([fe80::d9f9:2028:fd8:1e35]) by BLRKECHUB07.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Fri, 21 Dec 2012 18:18:12 +0530
From: RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
To: Ben Campbell <ben@nostrum.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org>
Subject: RE: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i35q1rCmEQ/mUyYBxRcqJiFtpgi7Klw
Date: Fri, 21 Dec 2012 12:48:13 +0000
Message-ID: <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com>
In-Reply-To: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com>
Accept-Language: en-US, en-IN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.236.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Dec 2012 09:20:04 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, Bharat Joshi <bharat_joshi@infosys.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, 21 Dec 2012 12:48:38 -0000

Hi Ben,

Thank you for your review comments. 
Please find my responses inline below.

Regards,
Ramakrishna DTV.

>-----Original Message-----
>From: Ben Campbell [mailto:ben@nostrum.com]
>Sent: Thursday, December 20, 2012 2:45 AM
>To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
>Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
>Subject: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
>
>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-dhc-relay-id-suboption-11
>Reviewer: Ben Campbell
>Review Date: 2012-12-19
>IETF LC End Date: 2013-01-07
>
>Summary: This draft is basically ready for publication as a proposed
>standard. However, there is one comment from a prior review that I am
>not sure whether is resolved.
>
>Major issues:
>
>None
>
>Minor issues:
>
>-- In Sean Turner's 2009 review of version 07 of the document [
>http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ], he
>made the following comment:
>
>> In the security considerations it says look to RFC 3046 and
>> RFC 4030 for security considerations and then says SHOULD use the
>relay
>> agent authentication option from RFC 4030.  RFC 3046 is targeted at
>> network infrastructures that are "trusted and secure" and RFC 4030
>> allows the relay agent to be part of this trusted and secure network.
>> If an implementation doesn't use the relay agent authentication
>option,
>> then the relay agent can't be part of the "trusted and secure"
>network.

RFC3046 created the relay agent information option.
Relay agent information option exists only in the messages between
relay agents and DHCP servers. RFC3046 is targeted at network infrastruct=
ures
that are "trusted and secure" as far as the paths among relay agents and =
DHCP
servers is concerned. In many deployments, relay agents and DHCP servers 
are under a single administrative control. By careful design and engineer=
ing 
of the network, it is possible to ensure that the network infrastructure 
comprising relay agents and DHCP server is trusted and secure. To achieve=
 that,
RFC4030 may be used but is not a MUST. If not, RFC4030 would already be a=
 MUST 
for RFC3046 deployment. But that is not currently the case.

>>  This makes me think that the relay agent authentication option from
>> RFC 4030 ought to be a MUST not a SHOULD?
>
>I can't tell from the resulting conversation if that comment is
>addressed in the current text. Additional text has been added, but the
>SHOULD remains. I'm willing to accept it has been addressed if the
>author's say so--I only mention it to make sure it didn't fall through a
>crack.
>

We have indeed discussed about this comment and addressed it.

The following was a related comment from DHC WG Chair (Ted Lemon) 
(http://www.ietf.org/mail-archive/web/gen-art/current/msg04615.html):

=09"This document makes no changes to practice that require more or less =
security 
=09than is provided by existing relay agent options in RFC3046. Thus, the=
 
=09security considerations in RFC3046 should be adequate."

As Ted mentioned, our draft only proposes a new sub-option for relay-agen=
t 
option which was originally created as part of RFC3046. So, the security 
considerations for RFC3046 apply to our draft as well. RFC3046 deployment=
s may
use RFC4030 as explained above. So, we indicated in our draft to refer to=
 
both RFC3046 and RFC4030. But there are no specific security issues in th=
e 
new relay-id sub-option itself to make RFC4030 a MUST.


>Nits/editorial comments:
>
>-- section 5, last paragraph:
>
>I suggest removing the scare quotes around "stability". If there are
>concerns about whether such stability is real, it would be better to say
>that directly.
>

There is no need for these scare quotes. We will remove them.

>-- informative references:
>
>draft-ietf-dhc-dhcpv4-bulk-leasequery-06 is now 07

We will update this.

>

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

From Ted.Lemon@nominum.com  Fri Dec 21 06:27:25 2012
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 4085221F8CEC; Fri, 21 Dec 2012 06:27:25 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5-M1IimCRLw; Fri, 21 Dec 2012 06:27:24 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 2CDE421F8C93; Fri, 21 Dec 2012 06:27:24 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUNRxyxyV6ezR4sIheTm/JB5fY/f81T6O@postini.com; Fri, 21 Dec 2012 06:27:24 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A8FDB1B812D; Fri, 21 Dec 2012 06:27:23 -0800 (PST)
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 9F1D1190052; Fri, 21 Dec 2012 06:27:23 -0800 (PST) (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; Fri, 21 Dec 2012 06:27:17 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i33Q3+/pWXDrEC14WiRxtRL+pgjvKCAgAAbrIA=
Date: Fri, 21 Dec 2012 14:27:17 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>
In-Reply-To: <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.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: <59F9D6FCA56827488D2004B1DB7EA177@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Dec 2012 09:20:04 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, "ietf@ietf.org List" <ietf@ietf.org>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.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, 21 Dec 2012 14:27:25 -0000

On Dec 21, 2012, at 7:48 AM, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com> wr=
ote:
> As Ted mentioned, our draft only proposes a new sub-option for relay-agen=
t=20
> option which was originally created as part of RFC3046. So, the security=
=20
> considerations for RFC3046 apply to our draft as well. RFC3046 deployment=
s may
> use RFC4030 as explained above. So, we indicated in our draft to refer to=
=20
> both RFC3046 and RFC4030. But there are no specific security issues in th=
e=20
> new relay-id sub-option itself to make RFC4030 a MUST.

To put it a bit differently, changing the security considerations for RFC30=
46 is out of scope for this document.   It could certainly be argued that t=
he security considerations for RFC3046 are too weak, but if that is an argu=
ment that someone wants to make, the argument should be made in the context=
 of updating RFC3046, not in the context of adding a new DHCP relay option.


From Ted.Lemon@nominum.com  Fri Dec 21 08:06:35 2012
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 9F6E521F8802; Fri, 21 Dec 2012 08:06:35 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RjQfGZwdBglx; Fri, 21 Dec 2012 08:06:34 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id 7B49321F86A4; Fri, 21 Dec 2012 08:06:34 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUNSJBq9xiSuHISy1FgkVyq8g2p1bv2hs@postini.com; Fri, 21 Dec 2012 08:06:34 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 4C0511B81E8; Fri, 21 Dec 2012 08:06:30 -0800 (PST)
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 43759190052; Fri, 21 Dec 2012 08:06:30 -0800 (PST) (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; Fri, 21 Dec 2012 08:06:30 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i33Q3+/pWXDrEC14WiRxtRL+pgjvKCAgAAbrICAABXLgIAABe6A
Date: Fri, 21 Dec 2012 16:06:30 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630747441AF5@mbx-01.win.nominum.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com> <8D23D4052ABE7A4490E77B1A012B6307474418FF@mbx-01.win.nominum.com> <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.com>
In-Reply-To: <E1A0312B-2E9A-4FD6-AAAA-8AE03AE4B965@nostrum.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: <051271295785B447A3D42540E88098E3@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 21 Dec 2012 09:20:04 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, Bharat Joshi <bharat_joshi@infosys.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.all@tools.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: Fri, 21 Dec 2012 16:06:36 -0000

On Dec 21, 2012, at 10:45 AM, Ben Campbell <ben@nostrum.com> wrote:
> As I responded separately to Ramakrishna, is the SHOULD use 4030 language=
 a new requirement specific to this draft? Or is it just describing require=
ments in 3046 or elsewhere?

I suppose the authors should really answer this, but I was curious as well,=
 and went looking.   I think RFC4030 should have updated RFC3046 to add thi=
s as a security consideration, but it did not.   However, e.g. RFC4243, RFC=
5010 and RFC5107 do add a similar requirement to their security considerati=
ons section, so it's probably fair to say that this has been informally ado=
pted as appropriate practice for security considerations sections.  =20

Perhaps we should adopt the practice more formally... :)


From btv1==702717fa800==HKaplan@acmepacket.com  Fri Dec 21 10:28:35 2012
Return-Path: <btv1==702717fa800==HKaplan@acmepacket.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C80821F853C for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 10:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.216
X-Spam-Level: 
X-Spam-Status: No, score=-2.216 tagged_above=-999 required=5 tests=[AWL=-0.217, BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79Gfa3B6hoZi for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 10:28:34 -0800 (PST)
Received: from mx2.acmepacket.com (mx2.acmepacket.com [216.41.24.99]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF9521F84FD for <ietf@ietf.org>; Fri, 21 Dec 2012 10:28:34 -0800 (PST)
X-ASG-Debug-ID: 1356114507-03fc2110a84b3ec0001-h9jmKw
Received: from Mail1.acmepacket.com (mail1.acmepacket.com [10.0.0.21]) by mx2.acmepacket.com with ESMTP id 4D73hYgiL0wICG89 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NO); Fri, 21 Dec 2012 13:28:27 -0500 (EST)
X-Barracuda-Envelope-From: HKaplan@acmepacket.com
Received: from MAIL2.acmepacket.com ([169.254.2.174]) by Mail1.acmepacket.com ([169.254.1.77]) with mapi id 14.02.0283.003; Fri, 21 Dec 2012 13:28:26 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating	Fax over IP Capability in the Session Initiation Protocol	(SIP)) to Proposed Standard
Thread-Topic: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating	Fax over IP Capability in the Session Initiation Protocol	(SIP)) to Proposed Standard
X-ASG-Orig-Subj: Re: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating	Fax over IP Capability in the Session Initiation Protocol	(SIP)) to Proposed Standard
Thread-Index: AQHN36j3dhbE+IfSw0qrFP0DgKbkhA==
Date: Fri, 21 Dec 2012 18:28:26 +0000
Message-ID: <CD38BBC6-1E84-4AF6-913B-BABE1BDFC6E0@acmepacket.com>
References: <20121129144602.12454.60016.idtracker@ietfa.amsl.com>
In-Reply-To: <20121129144602.12454.60016.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <45941797CD49A842BB3A53CA7943ED57@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Barracuda-Connect: mail1.acmepacket.com[10.0.0.21]
X-Barracuda-Start-Time: 1356114507
X-Barracuda-Encrypted: AES128-SHA
X-Barracuda-URL: http://216.41.24.99:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at acmepacket.com
X-Barracuda-Spam-Score: 0.00
X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests=BSF_SC0_MISMATCH_TO
X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.2.117670 Rule breakdown below pts rule name              description ---- ---------------------- -------------------------------------------------- 0.00 BSF_SC0_MISMATCH_TO    Envelope rcpt doesn't match header
Cc: "draft-hanes-dispatch-fax-capability@tools.ietf.org" <draft-hanes-dispatch-fax-capability@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, 21 Dec 2012 18:29:03 -0000

Howdy,
I've read the draft and overall it looks good. =20

Some minor comments:
The examples in section 5 of the draft repeatedly show a Via header as foll=
ows:
Via: SIP/2.0/TCP bob-TP@example.com;branch=3Dz9hG4bK309475a2
This is not a legal Via header format, since the sent-by field cannot conta=
in a '@'.  It's meant to be a host or host:port, not a user@host... and mor=
e likely a host:port since this is TCP for this example.

Also, the examples show a Contact URI host of the domain in the REGISTER re=
quest, the same as the target request-URI.  While not technically illegal I=
 guess, it's extremely unusual - the purpose of a REGISTER is to register t=
he Contact URI as the reachable target for the Address of Record, and thus =
the Contact URI should indicate the specific host registering.  I suggest c=
hanging it to:
Contact: <sip:bob-tp@pc33.example.com;transport=3Dtcp>;+sip.fax=3D"t38"

Lastly, the example INVITE at the end of section 5 is malformed, both becau=
se it's missing mandatory headers, and because the From header has no tag p=
aram.

-hadriel


On Nov 29, 2012, at 9:46 AM, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Indicating Fax over IP Capability in the Session Initiation Protocol
>   (SIP)'
>  <draft-hanes-dispatch-fax-capability-06.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 2012-12-27. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document defines and registers with IANA the new 'fax' media
>   feature tag for use with SIP.  Currently, fax calls are
>   indistinguishable from voice at call initiation.  Consequently, fax
>   calls can be routed to SIP user agents that are not fax capable.  A
>   'fax' media feature tag implemented in conjunction with caller
>   preferences allows for more accurate fax call routing.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-hanes-dispatch-fax-capability/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-hanes-dispatch-fax-capability/ballo=
t/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20


From sm@resistor.net  Fri Dec 21 11:02:22 2012
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 E032621F84E6 for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 11:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.621
X-Spam-Level: 
X-Spam-Status: No, score=-102.621 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGAtQ3NGEHnC for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 11:02:21 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE3A721F87E4 for <ietf@ietf.org>; Fri, 21 Dec 2012 11:02:20 -0800 (PST)
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 qBLJ2C2D004621; Fri, 21 Dec 2012 11:02:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1356116539; bh=VCAjRq/tVdx/LwdVfzJxCVmOK1ILdqjxjJ+LenzZs50=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jC/RpHMKOKLksHRjuSUHeEmVUYes+ZFtctDIkYL0siQhouRhNjbJZUcjDUurJadYG whq/2ME9bQrzQhffAD9Gjx4aBiqp2CI5c6I7K+7EtKkwRbscL27ywq4/2a8Rc7T3Fy qGUk8sXvAN+l7bmevUsQxWvUpe6/aYLjOFVhvz/s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1356116539; i=@resistor.net; bh=VCAjRq/tVdx/LwdVfzJxCVmOK1ILdqjxjJ+LenzZs50=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DMwHu3VpMoAXTGNlsNRyG460T3cku5l5rLbxMqdGD5tXz9RRynAKMrvuKBXkFUXH9 0fZ1Quw9vl6y6Vj71ZMmlxSXAe5ug+YzE2MuGxhr9NDXvgoix81eHUqZT+2daWvze6 t/q/q1r5hbB3CdrsmQO8A7YqEhq+bYHV6HSGjFFQ=
Message-Id: <6.2.5.6.2.20121221103719.0c3d8cc8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 21 Dec 2012 10:58:29 -0800
To: Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call:	<draft-bonica-special-purpose-03.txt>	(Special-Purpose Address	Registries) to Best Current Practice
In-Reply-To: <50D47B76.7010009@qti.qualcomm.com>
References: <20121129205534.8983.43593.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121129165519.0a037840@resistor.net> <50D3A040.4090706@qti.qualcomm.com> <6.2.5.6.2.20121220221257.0a828b40@resistor.net> <50D47B76.7010009@qti.qualcomm.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: Fri, 21 Dec 2012 19:02:23 -0000

Hi Pete,
At 07:08 21-12-2012, Pete Resnick wrote:
>I am still confused. What is the action item here? Do you think 
>something needs to be fixed in this document?

It was an explanation instead of an actionable comment.  My 
preference is to deal with the IPv4 and IPv6 registries separately as 
it is easier to explain.  I am okay with not making any changes to 
the document as it is not worth spending more time on it.

Regards,
-sm 


From gsalguei@cisco.com  Fri Dec 21 12:21:09 2012
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 6AFDD21F879E for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 12:21:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.42
X-Spam-Level: 
X-Spam-Status: No, score=-10.42 tagged_above=-999 required=5 tests=[AWL=-0.421, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOxdFeIl5BKG for <ietf@ietfa.amsl.com>; Fri, 21 Dec 2012 12:21:08 -0800 (PST)
Received: from av-tac-rtp.cisco.com (av-tac-rtp.cisco.com [64.102.19.209]) by ietfa.amsl.com (Postfix) with ESMTP id A381821F872C for <ietf@ietf.org>; Fri, 21 Dec 2012 12:21:08 -0800 (PST)
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 qBLKL7h8012434 for <ietf@ietf.org>; Fri, 21 Dec 2012 15:21:07 -0500 (EST)
Received: from rtp-vpn6-996.cisco.com (rtp-vpn6-996.cisco.com [10.82.251.231]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id qBLKL6Mv028053;  Fri, 21 Dec 2012 15:21:06 -0500 (EST)
Subject: Re: Last Call: <draft-hanes-dispatch-fax-capability-06.txt> (Indicating	Fax over IP Capability in the Session Initiation Protocol	(SIP)) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Gonzalo Salgueiro <gsalguei@cisco.com>
In-Reply-To: <CD38BBC6-1E84-4AF6-913B-BABE1BDFC6E0@acmepacket.com>
Date: Fri, 21 Dec 2012 15:21:06 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC582DD0-2FFC-4500-AA25-7F1785CAC825@cisco.com>
References: <20121129144602.12454.60016.idtracker@ietfa.amsl.com> <CD38BBC6-1E84-4AF6-913B-BABE1BDFC6E0@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.1283)
Cc: draft-hanes-dispatch-fax-capability@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: Fri, 21 Dec 2012 20:21:09 -0000

Thanks for the review, Hadriel.  After the IESG review I'll make the =
suggested edits to the SIP headers in the examples.

Cheers,

Gonzalo

On Dec 21, 2012, at 1:28 PM, Hadriel Kaplan wrote:

> Howdy,
> I've read the draft and overall it looks good. =20
>=20
> Some minor comments:
> The examples in section 5 of the draft repeatedly show a Via header as =
follows:
> Via: SIP/2.0/TCP bob-TP@example.com;branch=3Dz9hG4bK309475a2
> This is not a legal Via header format, since the sent-by field cannot =
contain a '@'.  It's meant to be a host or host:port, not a user@host... =
and more likely a host:port since this is TCP for this example.
>=20
> Also, the examples show a Contact URI host of the domain in the =
REGISTER request, the same as the target request-URI.  While not =
technically illegal I guess, it's extremely unusual - the purpose of a =
REGISTER is to register the Contact URI as the reachable target for the =
Address of Record, and thus the Contact URI should indicate the specific =
host registering.  I suggest changing it to:
> Contact: <sip:bob-tp@pc33.example.com;transport=3Dtcp>;+sip.fax=3D"t38"
>=20
> Lastly, the example INVITE at the end of section 5 is malformed, both =
because it's missing mandatory headers, and because the =46rom header =
has no tag param.
>=20
> -hadriel
>=20
>=20
> On Nov 29, 2012, at 9:46 AM, The IESG <iesg-secretary@ietf.org> wrote:
>=20
>>=20
>> The IESG has received a request from an individual submitter to =
consider
>> the following document:
>> - 'Indicating Fax over IP Capability in the Session Initiation =
Protocol
>>  (SIP)'
>> <draft-hanes-dispatch-fax-capability-06.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 2012-12-27. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>  This document defines and registers with IANA the new 'fax' media
>>  feature tag for use with SIP.  Currently, fax calls are
>>  indistinguishable from voice at call initiation.  Consequently, fax
>>  calls can be routed to SIP user agents that are not fax capable.  A
>>  'fax' media feature tag implemented in conjunction with caller
>>  preferences allows for more accurate fax call routing.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-hanes-dispatch-fax-capability/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-hanes-dispatch-fax-capability/ballot=
/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>=20
>=20


From magnus.westerlund@ericsson.com  Wed Dec 26 05:01:42 2012
Return-Path: <magnus.westerlund@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 EEEA121F8CA8; Wed, 26 Dec 2012 05:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.918
X-Spam-Level: 
X-Spam-Status: No, score=-105.918 tagged_above=-999 required=5 tests=[AWL=-0.271, BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.001, J_CHICKENPOX_62=0.6, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tlQ-3-AZdzET; Wed, 26 Dec 2012 05:01:39 -0800 (PST)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2007221F8CA4; Wed, 26 Dec 2012 05:01:37 -0800 (PST)
X-AuditID: c1b4fb30-b7f736d0000010de-61-50daf530dec5
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id A8.9B.04318.035FAD05; Wed, 26 Dec 2012 14:01:36 +0100 (CET)
Received: from ESESSMB309.ericsson.se ([169.254.9.200]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.02.0318.004; Wed, 26 Dec 2012 14:01:35 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "mboned@ietf.org" <mboned@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
Subject: Last Call: <draft-ietf-mboned-auto-multicast-14.txt> (Automatic Multicast Tunneling) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mboned-auto-multicast-14.txt> (Automatic Multicast Tunneling) to Proposed Standard
Thread-Index: Ac3jVcIqcwxiuhgnSx6BeVaaAQVGSw==
Date: Wed, 26 Dec 2012 13:01:35 +0000
Message-ID: <52E4A8FC978E0241AE652516E24CAF000E5FBC@ESESSMB309.ericsson.se>
Accept-Language: sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_52E4A8FC978E0241AE652516E24CAF000E5FBCESESSMB309ericsso_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyM+Jvja7B11sBBlcPylrM+DOR2eLZxvks FlNaTjNafLtyg92BxWPJkp9MAYxRXDYpqTmZZalF+nYJXBmbH7xnKji4ialiy/PTbA2MT34x djFyckgImEh86X3ODGGLSVy4t56ti5GLQ0jgEKPElNWX2SGcJYwS31t3gHWwCVhI3PzRyAZi iwhkS3xvmccKYjMLaEr83joFKM7BISxQIvHvkANESaXEh5aNzBC2nsT+69vBbBYBVYk1KxaC 2bwC3hKXvpwEG8MoICtx//s9FoiR4hKf5z5ggjhOQGLJnvNQh4pKvHz8jxXCVpTYebadGaI+ X+LS42usEDMFJU7OfMIygVF4FpJRs5CUzUJSBhHXk7gxdQobhK0tsWzha2YIW1dixr9DLMji CxjZVzGy5yZm5qSXm29iBEbMwS2/DXYwbrovdohRmoNFSZw33PVCgJBAemJJanZqakFqUXxR aU5q8SFGJg5OqQbGgJfHFvrWuq14tdT4oVv5y9Tnz28tWBDblhC161SR4NUlnlJPrn54dqJs z76k271zxT+Ur5myafZD0ewJn7P/3eD6wMq3grfRci7j/O47YazC8/dbJnrmz/vY8FvFiWm1 4uaH0fO158zekTjzwpn3WzLS7xonKwmapy9RSV+kH+Oix2B3rPNxtBJLcUaioRZzUXEiAHHD D11mAgAA
Cc: "tsv-dir@ietf.org" <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Dec 2012 13:01:42 -0000

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

Hi,

Sorry for being late with this IETF last call comments. I will partly blame=
 the ADs requesting this Transport Directorate review a bit late, the other=
 part is all mine and the holidays. Anyway, I do hope you will consider the=
se issues and comments as I believe I found some serious ones in addition t=
o a number of clarifications that should be made.


Significant Issues:

1. Congestion Control
This is clearly a tunnel establishment protocol of something that is IP tra=
ffic. Thus normally the responsibility for congestion control is with the t=
unnelled traffic. However, I would like argue that this does not apply in t=
his case due to the nature of the tunnelled traffic, i.e. multicast traffic=
 and secondary due to limitations in the tunnel protocol.

Lets start with the second part. This protocol claims to support ASM still =
don't provide a upstream delivery mechanism, i.e. an ASM receiver is not ca=
pable of sending as it should. This prevents several existing mechanism for=
 congestion control that exist in protocols supporting multicast. The first=
 is using RTCP for congestion control in ASM [RFC3550], the second is TCP-F=
riendly Multicast Congestion Control [RFC4654] that can be used in the RMT =
suite of protocols, and I know has been implemented in some NORM implementa=
tion. Thus only strictly receiver based mechanisms, such as Wave and Equati=
on Based Rate Control [RFC3738] are available in this context.

Secondly, many multicast usages are in fact deployed without any congestion=
 control. This based on that the deploying entity controls the scope and au=
thorization for requesting multicast delivery. However, does restrictions d=
oes not apply to AMT delivery of multicast. If the gateway can reach using =
unicast the relay it can be delivered the multicast group from the domain t=
he relay is attached to. Thus, this protocol changes the deployment restric=
tions of multicast which many non-congestion controlled delivery is based o=
n. Instead the non-congestion controlled traffic can now sent over an IP/UD=
P tunnel over Internet where neither relay nor gateway may have any knowled=
ge about the path the traffic may take.

Based on this I would like to see two changes to this protocol specificatio=
n. First a section discussing the issue of congestion control. Secondly, I =
think this protocol should have an applicability statement limiting its dep=
loyment to restricted environments where the relay and gateway deployers ca=
n provide certain resource provisions between the entities to avoid the mul=
ticast traffic affecting other traffic sharing the same bottlenecks in ways=
 not allowed by the network provider.

2. Security

This protocols is frank with it having limited security features and says t=
his is similar to the IGMP and MLD protocols being used. However, I think t=
his is a failure to propoerly consider the threat model. If one uses AMT ov=
er general Internet it will run in a network where the one deploying the mu=
lticast and the relays no longer control requirements on source address ver=
ification or possibilities for traffic separation as they can do within the=
 domains where multicast currently are deployed. The security vulnerabiliti=
es in IGMP and MLD are much more contained and controllable in a LAN enviro=
nment where one has chosen to deploy multicast compared to an Relay exposin=
g this to the whole Internet. Once more I think there is only two choices h=
ere.

A) Beef up the security to general Internet threat model, i.e. at a minimal=
 provide a real model for gateway authentication using identities, not only=
 return routability based verifications.

B) Limit the applicability of AMT to managed environments and make it clear=
 that the relay will need to limit which gateways are allowed to access the=
 relay based on addressing.

Based on the first significant issue with congestion control I expect that =
there is little meaning to do A) unless also one is willing to beef up AMT =
to provide congestion control. Which I think is not according to the design=
 wishes for the protocol designers.

3. Use of Zero Checksum

The AMT specification enables the use of Zero UDP checksum with IPv6, i.e.
draft-ietf-6man-udpchecksums-06<http://datatracker.ietf.org/doc/draft-ietf-=
6man-udpchecksums/> and draft-ietf-6man-udpzero-08<http://datatracker.ietf.=
org/doc/draft-ietf-6man-udpzero/>. Nothing against this in principal. Howev=
er, I have noticed that AMT fails to properly address the failure modes of =
using a zero-checksum. AMT is a typical example of a protocol that actually=
 need active verification of each tunnel that zero-checksum functions. This=
 as AMT is clearly intended to be deployed with its Gateway part in end-hos=
ts and residential network devices or routers. This means the tunnel will p=
ass through both firewalls and NATs on its path between the relay and the g=
ateway. Unless these devices are not upgraded to support zero-checksum in U=
DP for IPv6 the traffic may actually become black holed. The most likely is=
 a simple firewall that has a rule for IPv6/UDP which doesn't allow zero ch=
ecksum as it is against RFC 2460. Thus all the Multicast data packets will =
disappear on route in the tunnel. There is no mechanism in the AMT protocol=
 to detect this and negotiate with the relay so that it will not use the ze=
ro-checksum for this tunnel.

This must be addressed as I see it. If not the AMT will be so brittle that =
it can't be used in a large number of its intended deployments.

4) MTU issues

This document total fails to discuss the issues of MTU blackholing. As the =
IP multicast datagrams as well as the encapsulated IGMP/MLD messages can wi=
th the added tunnel-overhead result in that the sent packet exceeds the MTU=
 of the path, these packets could be black holed. This can potentially resu=
lt in very intermittent transport behavior for the tunnel. Thus, some discu=
ssion of how do handle the MTU issues in this context should be introduced.

I am willing to discuss methods here, but I guess several alternatives exis=
ts and thus which is most appropriate and the level of AMT support for them=
 varies I would like the protocol designers to do a first stab at resolving=
 this.

Other Issues
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

A) The table of content on page 2 should include more levels of headings. M=
ost likely down to 4 is needed to make the TOC usable for finding content i=
n the document.

B) The claimed ASM support
I would like to better understand how one can claim to support ASM when one=
 has no up stream path to inject the ASM group participants traffic. When o=
ne uses ASM one normally does this for a reason and needing the possibility=
 to inject packets into the group. These limitations needs to be clarified.

C) Section 4:

This section indicates is its figures, the ones in Section 4.1.1 and Sectio=
n 4.1.3.1 that the Router Mode IGMP/MLD functions are outside of AMT. Which=
 based on the requirements in Section 5.3.3.4 is not accurate. That impleme=
ntation must be AMT specific to maintain the AMT tunnel to group membership=
 handling

D) Not all figures have handles that can be used to reference.

E) Section 4.1.5.1:


   Similarly, the selection of a unicast Relay address may be source-
   dependent, as a relay contacted by a gateway to supply multicast
   traffic must have native multicast connectivity to the traffic source


I find this statement confusing. There is no support in the protocol for in=
cluding the multicast group(s) which the gateway like to get in the discove=
ry phase of the protocol.

F) AMT Gateway in home router.
One deployment scenario is that the AMT gateway is deployed in the home net=
work router to provide access to multicast groups provided by the ISP. Howe=
ver, the startup procedures in this deployment is unclear. The text appears=
 to indicate that one can both have a gateway implementation that as soon a=
s the router boots it starts doing discovery and requests to have Queries t=
o send to its internal local network. Other suggestions appears to be to wa=
it until some host actually request to join a group. The protocol specifica=
tion appears to do its best to leave very much flexibility and thus produce=
 huge variance in the market.

G) Figure 3:
I find no discussion of Membership Updates to rejoin the groups after the t=
unnel has changed its source address as seen by the relay. This I think sho=
uld have some discussion. Yes, it reasonably clear that you will get traffi=
c just by sending new membership updates over the new tunnel. However, some=
 discussion of the timing between teardown and this membership update shoul=
d be considered. Figure 3 implies it should be sent after the teardown, whi=
ch I think is correct due to the traffic volumes to the NAT most likely cau=
sing the path change.

H) Figure in Section 4.2.2.2
Propose that the external side of the NAT should be marked as the one havin=
g the "e" addresses.

I) Seeing the figure in Section 4.2.2.3 I definitely commented on the Addre=
ss Collision issues. It is made somewhat clearer later on this. But, maybe =
an clearer section 4 sub-section to discuss this general issue that multipl=
e left side host can have the same address as other behind other tunnel-end=
-points and thus there is need in the Relay to hide this from upstream and =
accept it and use the tunnel context to track the different hosts.

J) Section 4.2.2.3:


 To avoid placing an undue burden on the relay platform, the protocol
   specifically allows zero-valued UDP checksums on the multicast data
   messages.  This is not an issue in UDP over IPv4 as the UDP checksum
   field may be set to zero.  However, this is a problem for UDP over
   IPv6 as that protocol requires a valid, non-zero checksum in UDP
   datagrams [RFC2460].  Messages sent over IPv6 with a UDP checksum of
   zero may fail to reach the gateway.  This is a well known issue for
   UDP-based tunneling protocols that is described
   [I-D.ietf-6man-udpzero].  A recommended solution is described in
   [I-D.ietf-6man-udpchecksums].

I think this needs reformulating and I don't understand what is intended
with the last sentence.

K) Section 5.1.1.
"Destination UDP Port -  The IANA-assigned AMT port number."

I find it strange that the protocol is mandating that all traffic is sent
to the IANA assigned port. Why can't the protocol not allow more flexible h=
andling
of the destination port? I find one single thing in the protocol which prev=
ents
usage of an other relay listener port. That is that the Relay Advertisement=
 would
need a port field in addition to the address.

L) Section 5.1.1.4
A 32-bit random value generated by the gateway and echoed by the
   relay in a Relay Advertisement message.

Should the above value make it clear that it preferably should be a
cryptographically random value as defined in RFC 4086?

M) There is lack of specification in Section 5.1.1 of what one does if vers=
ion
is different from 0. This is mentioned in Section 5.3.3.1 but not for gatew=
ays
and not all messages types.

N) Section 5.1.4.8:

   The Querier's Query Interval Code (QQIC) field in the general query
   is used by a relay to specify the time offset a gateway should use to
   schedule a new three-way handshake to refresh the group membership
   state within the relay (current time + Query Interval).

In several places the QQIC and QRV are not made clear that this is defined =
in
the external references for MLD and IGMP.

O) Section 5:
When specifying the bit-fields, please indicate the length of each field in=
 the
text. This is an accessibility question. If you have impaired vision interp=
reting
the figures field length correctly can be different.

P) Section 5.2.2.4:

This section defined what retransmission parameters that one can potentiall=
y
configure. However, the section fails to define what the max or min values =
that
are acceptable are. Wrongly configured retransmission parameters can have s=
ignificant
negative impact on the network by causing bursts or unnecessary traffic.

Q) Section 5.2.3.3:
The gateway may continue to receive Multicast Data messages long
   after the gateway sends a Membership Update message that deletes
   existing group subscriptions.

What is "long" in the above sentence. Are we talking some known number of s=
econds,
a TCP MSL, i.e. 2 min?

R) Section 5.2.3.4.3
   A gateway MAY retransmit a Relay Discovery message if it does not
   receive a matching Relay Advertisement message within some timeout
   period.  If the gateway retransmits the message multiple times, the
   timeout period SHOULD be adjusted to provide an random exponential
   back-off.  The RECOMMENDED timeout is a random value in the range
   [initial_timeout, MIN(initial_timeout * 2^retry_count,
   maximum_timeout)], with a RECOMMENDED initial_timeout of 1 second and
   a RECOMMENDED maximum_timeout of 120 seconds (which is the
   recommended minimum NAT mapping timeout described in [RFC4787]).

I wonder if the above exponential backof is really what is desired. As it r=
andomly
picks the timeout between initial timout value and the 2^retry_count*initia=
l_timeout it
will be both lower biased and also capable of producing timing intervals th=
at doesn't
grow. If one desire to have random timeout to avoid some clock synchronizat=
ion effects
I think an algorithm that is Td =3D MIN(initial_timeout * 2^retry_count,
   maximum_timeout) and where the actual timeout is random*Td and where ran=
dom is a
random value from the uniform distribution in the interval [0.5,1.5]. Will =
both ensure
that the timout between two retransmissions never is less and on average gr=
ows with
a factor two.

This section is also not defining a minimal initial timout value, or any me=
thod for
safely determine a more performant value from a safe initial value. To do a=
 RTT
measurement using the AMT control messages would require some extensions bu=
t
could be a good way of deterimining a better initial value than 0.5 seconds=
 which
would be my recommendation for a default value.

S) Section 5.2.3.4.4

   If a gateway executes the relay discovery procedure at the start of
   each membership update cycle and the relay address returned in the
   latest Relay Advertisement message differs from the address returned
   in a previous Relay Advertisement message, then the gateway SHOULD
   send a Teardown message (if supported) to the old relay address,
   using information from the last Membership Query message received
   from that relay, as described in Section 5.2.3.7.  This behavior is
   illustrated in the following diagram.

This text and the figure after it does not appear to be consistent.
The figure implies a timer that isn't present in the above. The textual
description appears sensitive to flapping anycast routing. I think
the figures indication of some higher timeout before redoing Relay discover=
y
appears much more robust.

T) Section 5.2.3.5.3
See R)
Also this text appears redundant to previous text. Maybe generalize this
into its own section being used in general for all messages needing retrans=
mission

U) Section 5.2.3.5.4
   Querier's Query Interval Code carried by the general-query.  A
   gateway MAY use a smaller timer duration if required to refresh a NAT
   mapping that would otherwise timeout.

Maybe the protocol would rather need a NAT keep-alive message to be sent
from the gateway to the relay. But maybe the Request, Query cycle is light =
weight
enough that this works fine.

V) Section 5.2.3.6.1

o  Insert IGMP or MLD datagrams into a queue for transmission after
      it receives a Membership Query message.

What assumptions of queue depth exist in the above. Clearly the messages in=
 this
queue should expire if they become to old.

X) Section 5.2.3.7
Gateway support for the Teardown message is OPTIONAL but RECOMMENDED.

The above is a very strange usage of RFC 2119 keywords. IF you use the syno=
nyms
then maybe the error of writing it this way is clear.
Gateway MAY support for the Teardown message but SHOULD.

Y) The usage of retransmission versus repetitions are not always clear.
Some of the messages appears to simply need to be repeated QRV number of ti=
mes with
some interval. Others should really be matched with an answer and if not re=
ceived within
timeout retransmitted. Can these two cases be made more clear?

Z) Section 5.3.5
   The hash function RECOMMENDED for use in computing the Response MAC
   is the MD5 hash digest [RFC1321], though hash functions or keyed-hash
   functions of greater cryptographic strength may be used.

I think this points to a security vulnerability. I think it needs to be mad=
e clear
that the MAC MUST be keyed. If it is just a digest, then an attacker can ca=
lculate the
MAC and perform an off-path attack.

This should be made clear also in Section 6.1 to be a requirement.

AA) Section A.1:

Altough this proposals has its advantages I think it might also illustrate =
a
short-coming. First of all 48-bits is quite short for a MAC. I would prefer=
 a
variable length field.

Secondly, doesn't this actually create more material for an attacker to det=
ermine
the key used by the relay?

That was all I have found.

Cheers

Magnus


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

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:=
0;}</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;"><font face=3D"Courier New">Hi,<br>
<br>
Sorry for being late with this IETF last call comments. I will partly blame=
 the ADs requesting this Transport Directorate review a bit late, the other=
 part is all mine and the holidays. Anyway, I do hope you will consider the=
se issues and comments as I believe
 I found some serious ones in addition to a number of clarifications that s=
hould be made.<br>
<br>
<br>
Significant Issues:<br>
<br>
1. Congestion Control<br>
This is clearly a tunnel establishment protocol of something that is IP tra=
ffic. Thus normally the responsibility for congestion control is with the t=
unnelled traffic. However, I would like argue that this does not apply in t=
his case due to the nature of the
 tunnelled traffic, i.e. multicast traffic and secondary due to limitations=
 in the tunnel protocol.
<br>
<br>
Lets start with the second part. This protocol claims to support ASM still =
don't provide a upstream delivery mechanism, i.e. an ASM receiver is not ca=
pable of sending as it should. This prevents several existing mechanism for=
 congestion control that exist in
 protocols supporting multicast. The first is using RTCP for congestion con=
trol in ASM [RFC3550], the second is</font><font face=3D"Courier New" size=
=3D"2"><font size=3D"3">
</font>TCP-Friendly Multicast Congestion Control [RFC4654] that can be used=
 in <font size=3D"2">
the RMT s<font size=3D"2">uite of protocols, and I know <font size=3D"2">ha=
s been implemented in some NORM implementation. Thus only<font size=3D"2"> =
strictly receiver based
<font size=3D"2">mechanisms, such as </font></font></font></font></font></f=
ont><font face=3D"Courier New" size=3D"2"><font size=3D"2"><font size=3D"2"=
><font size=3D"2"><font size=3D"2"><font size=3D"2">Wave and Equation Based=
 Rate Control [RFC3738]</font> are available in
 this context. <br>
<br>
<font size=3D"2">Secondly, <font size=3D"2">many multicast <font size=3D"2"=
>usages are in fact deployed
<font size=3D"2">without any congestion control. This based on that the dep=
loy<font size=3D"2">ing entity controls
<font size=3D"2">the scope <font size=3D"2">and <font size=3D"2"><font size=
=3D"2">authorization</font> for
<font size=3D"2">requesting multicast d<font size=3D"2">elivery. However, <=
font size=3D"2">
does <font size=3D"2">restrictions d<font size=3D"2">oes not apply to AMT d=
elivery of mu<font size=3D"2">lticast. I<font size=3D"2">f the gat<font siz=
e=3D"2">e<font size=3D"2">way can reach
<font size=3D"2">using unicast the relay it can be delivered the multicast =
group from the domain the relay is attached to. Thus<font size=3D"2">, th<f=
ont size=3D"2">is protocol changes the deployment restrictions
<font size=3D"2">of multic<font size=3D"2">ast which many non-congestion co=
ntrolled delivery is based on. Instead the
<font size=3D"2">non-congestion controlled traffic<font size=3D"2"> can</fo=
nt> now sen<font size=3D"2">t over an IP/UDP tunnel over Internet</font></f=
ont></font></font></font></font></font></font></font></font></font></font><=
/font></font></font></font></font></font></font></font></font></font></font=
></font>
 w<font size=3D"2">here neither r<font size=3D"2">elay nor gateway may have=
 any knowledge about the pat<font size=3D"2">h the traffic may take.
<br>
<br>
<font size=3D"2"><font size=3D"2"><font size=3D"2">Based on this I would <f=
ont size=3D"2">
like to see two <font size=3D"2">changes</font> to this protocol specificat=
ion. First a section discussing the issue of congestion control.
<font size=3D"2">Secondly, I think this protocol shou<font size=3D"2">ld ha=
ve an applicability statement limiting its deployment
<font size=3D"2">to restricted <font size=3D"2">environments</font> where t=
he relay and gateway deploy<font size=3D"2">ers can provide
<font size=3D"2">certain resource provisions between the <font size=3D"2">e=
ntiti<font size=3D"2">es to avoid the m<font size=3D"2">ulticast traffic af=
fecting other traffic sharing the same bottlenecks<font size=3D"2"> in ways=
 not allowed by the network
<font size=3D"2">provider. </font></font></font></font></font></font></font=
></font></font></font></font></font></font></font><br>
</font></font></font></font></font></font></font></font><font face=3D"Couri=
er New"><br>
2. Security<br>
<br>
This protocols is frank with it having limited security features and says t=
his is similar to the IGMP and MLD protocols being used. However, I think t=
his is a failure to propoerly consider the threat model. If one uses AMT ov=
er general Internet it will run
 in a network where the one deploying the multicast and the relays no longe=
r control requirements on source address verification or possibilities for =
traffic separation as they can do within the domains where multicast curren=
tly are deployed. The security vulnerabilities
 in IGMP and MLD are much more contained and controllable in a LAN environm=
ent where one has chosen to deploy multicast compared to an Relay exposing =
this to the whole Internet. Once more I think there is only two choices her=
e.<br>
<br>
A) Beef up the security to general Internet threat model, i.e. at a minimal=
 provide a real model for gateway authentication using identities, not only=
 return routability based verifications.
<br>
<br>
B) Limit the applicability of AMT to managed environments and make it clear=
 that the relay will need to limit which gateways are allowed to access the=
 relay based on addressing.
<br>
<br>
Based on the first significant issue with congestion control I expect that =
there is little meaning to do A) unless also one is willing to beef up AMT =
to provide congestion control. Which I think is not according to the design=
 wishes for the protocol designers.<br>
<br>
3. Use of Zero Checksum <br>
<br>
The AMT specification enables the use of Zero UDP checksum with IPv6, i.e. =
</font>
<br>
<font face=3D"Courier New"><a href=3D"http://datatracker.ietf.org/doc/draft=
-ietf-6man-udpchecksums/">draft-ietf-6man-udpchecksums-06</a> and
</font><font face=3D"Courier New"><a href=3D"http://datatracker.ietf.org/do=
c/draft-ietf-6man-udpzero/">draft-ietf-6man-udpzero-08</a>. Nothing against=
 this in principal. However, I have noticed that AMT fails to properly addr=
ess the failure modes of using a zero-checksum.
 AMT is a typical example of a protocol that actually need active verificat=
ion of each tunnel that zero-checksum functions. This as AMT is clearly int=
ended to be deployed with its Gateway part in end-hosts and residential net=
work devices or routers. This means
 the tunnel will pass through both firewalls and NATs on its path between t=
he relay and the gateway. Unless these devices are not upgraded to support =
zero-checksum in UDP for IPv6 the traffic may actually become black holed. =
The most likely is a simple firewall
 that has a rule for IPv6/UDP which doesn't allow zero checksum as it is ag=
ainst RFC 2460. Thus all the Multicast data packets will disappear on route=
 in the tunnel. There is no mechanism in the AMT protocol to detect this an=
d negotiate with the relay so that
 it will not use the zero-checksum for this tunnel. <br>
<br>
This must be addressed as I see it. If not the AMT will be so brittle that =
it can't be used in a large number of its intended deployments.
<br>
<br>
4) MTU issues<br>
<br>
This document total fails to discuss the issues of MTU blackholing. As the =
IP multicast datagrams as well as the encapsulated IGMP/MLD messages can wi=
th the added tunnel-overhead result in that the sent packet exceeds the MTU=
 of the path, these packets could
 be black holed. This can potentially result in very intermittent transport=
 behavior for the tunnel. Thus, some discussion of how do handle the MTU is=
sues in this context should be introduced.
<br>
<br>
I am willing to discuss methods here, but I guess several alternatives exis=
ts and thus which is most appropriate and the level of AMT support for them=
 varies I would like the protocol designers to do a first stab at resolving=
 this.
<br>
<br>
Other Issues<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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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>
<br>
A) The table of content on page 2 should include more levels of headings. M=
ost likely down to 4 is needed to make the TOC usable for finding content i=
n the document.<br>
<br>
B) </font><font face=3D"Courier New"><font face=3D"Courier New">The claimed=
 ASM support<br>
I would like to better understand how one can claim to support ASM when one=
 has no up stream path to inject the ASM group participants traffic. When o=
ne uses ASM one normally does this for a reason and needing the possibility=
 to inject packets into the group.
 These limitations needs to be clarified. </font><br>
<br>
C) Section 4:<br>
<br>
This section indicates is its figures, the ones in Section 4.1.1 and Sectio=
n 4.1.3.1 that the Router Mode IGMP/MLD functions are outside of AMT. Which=
 based on the requirements in Section 5.3.3.4 is not accurate. That impleme=
ntation must be AMT specific to
 maintain the AMT tunnel to group membership handling<br>
<br>
D) Not all figures have handles that can be used to reference.<br>
<br>
E) Section 4.1.5.1: <br>
</font><br>
<pre>   Similarly, the selection of a unicast Relay address may be source-=
=0A=
   dependent, as a relay contacted by a gateway to supply multicast=0A=
   traffic must have native multicast connectivity to the traffic source=0A=
</pre>
<font face=3D"Courier New">I find this statement confusing. There is no sup=
port in the protocol for including the multicast group(s) which the gateway=
 like to get in the discovery phase of the protocol.<br>
<br>
F) AMT Gateway in home router.<br>
One deployment scenario is that the AMT gateway is deployed in the home net=
work router to provide access to multicast groups provided by the ISP. Howe=
ver, the startup procedures in this deployment is unclear. The text appears=
 to indicate that one can both have
 a gateway implementation that as soon as the router boots it starts doing =
discovery and requests to have Queries to send to its internal local networ=
k. Other suggestions appears to be to wait until some host actually request=
 to join a group. The protocol specification
 appears to do its best to leave very much flexibility and thus produce hug=
e variance in the market.
<br>
<br>
G) Figure 3:<br>
I find no discussion of Membership Updates to rejoin the groups after the t=
unnel has changed its source address as seen by the relay. This I think sho=
uld have some discussion. Yes, it reasonably clear that you will get traffi=
c just by sending new membership
 updates over the new tunnel. However, some discussion of the timing betwee=
n teardown and this membership update should be considered. Figure 3 implie=
s it should be sent after the teardown, which I think is correct due to the=
 traffic volumes to the NAT most
 likely causing the path change. <br>
<br>
H) Figure in Section 4.2.2.2<br>
Propose that the external side of the NAT should be marked as the one havin=
g the &quot;e&quot; addresses.<br>
<br>
I) Seeing the figure in Section 4.2.2.3 I definitely commented on the Addre=
ss Collision issues. It is made somewhat clearer later on this. But, maybe =
an clearer section 4 sub-section to discuss this general issue that multipl=
e left side host can have the same
 address as other behind other tunnel-end-points and thus there is need in =
the Relay to hide this from upstream and accept it and use the tunnel conte=
xt to track the different hosts.
<br>
<br>
J) Section 4.2.2.3:<br>
</font><br>
<pre> To avoid placing an undue burden on the relay platform, the protocol=
=0A=
   specifically allows zero-valued UDP checksums on the multicast data=0A=
   messages.  This is not an issue in UDP over IPv4 as the UDP checksum=0A=
   field may be set to zero.  However, this is a problem for UDP over=0A=
   IPv6 as that protocol requires a valid, non-zero checksum in UDP=0A=
   datagrams [RFC2460].  Messages sent over IPv6 with a UDP checksum of=0A=
   zero may fail to reach the gateway.  This is a well known issue for=0A=
   UDP-based tunneling protocols that is described=0A=
   [I-D.ietf-6man-udpzero].  A recommended solution is described in=0A=
   [I-D.ietf-6man-udpchecksums].=0A=
<br>I think this needs reformulating and I don't understand what is intende=
d <br>with the last sentence. <br><br>K) Section 5.1.1.<br>&quot;Destinatio=
n UDP Port -  The IANA-assigned AMT port number.&quot;<br><br>I find it str=
ange that the protocol is mandating that all traffic is sent<br>to the IANA=
 assigned port. Why can't the protocol not allow more flexible handling<br>=
of the destination port? I find one single thing in the protocol which prev=
ents <br>usage of an other relay listener port. That is that the Relay Adve=
rtisement would <br>need a port field in addition to the address.<br><br>L)=
 Section 5.1.1.4<br>A 32-bit random value generated by the gateway and echo=
ed by the=0A=
   relay in a Relay Advertisement message. <br><br>Should the above value m=
ake it clear that it preferably should be a <br>cryptographically random va=
lue as defined in RFC 4086?<br><br>M) There is lack of specification in Sec=
tion 5.1.1 of what one does if version <br>is different from 0. This is men=
tioned in Section 5.3.3.1 but not for gateways <br>and not all messages typ=
es. <br><br>N) Section 5.1.4.8:<br><br>   The Querier's Query Interval Code=
 (QQIC) field in the general query=0A=
   is used by a relay to specify the time offset a gateway should use to=0A=
   schedule a new three-way handshake to refresh the group membership=0A=
   state within the relay (current time &#43; Query Interval).=0A=
<br>In several places the QQIC and QRV are not made clear that this is defi=
ned in <br>the external references for MLD and IGMP. <br><br>O) Section 5:<=
br>When specifying the bit-fields, please indicate the length of each field=
 in the <br>text. This is an accessibility question. If you have impaired v=
ision interpreting<br>the figures field length correctly can be different. =
<br><br>P) Section 5.2.2.4:<br><br>This section defined what retransmission=
 parameters that one can potentially <br>configure. However, the section fa=
ils to define what the max or min values that <br>are acceptable are. Wrong=
ly configured retransmission parameters can have significant<br>negative im=
pact on the network by causing bursts or unnecessary traffic. <br><br>Q) Se=
ction 5.2.3.3:<br>The gateway may continue to receive Multicast Data messag=
es long=0A=
   after the gateway sends a Membership Update message that deletes=0A=
   existing group subscriptions.<br><br>What is &quot;long&quot; in the abo=
ve sentence. Are we talking some known number of seconds, <br>a TCP MSL, i.=
e. 2 min?<br><br>R) Section 5.2.3.4.3<br>   A gateway MAY retransmit a Rela=
y Discovery message if it does not=0A=
   receive a matching Relay Advertisement message within some timeout=0A=
   period.  If the gateway retransmits the message multiple times, the=0A=
   timeout period SHOULD be adjusted to provide an random exponential=0A=
   back-off.  The RECOMMENDED timeout is a random value in the range=0A=
   [initial_timeout, MIN(initial_timeout * 2^retry_count,=0A=
   maximum_timeout)], with a RECOMMENDED initial_timeout of 1 second and=0A=
   a RECOMMENDED maximum_timeout of 120 seconds (which is the=0A=
   recommended minimum NAT mapping timeout described in [RFC4787]).<br><br>=
I wonder if the above exponential backof is really what is desired. As it r=
andomly<br>picks the timeout between initial timout value and the 2^retry_c=
ount*initial_timeout it <br>will be both lower biased and also capable of p=
roducing timing intervals that doesn't <br>grow. If one desire to have rand=
om timeout to avoid some clock synchronization effects<br>I think an algori=
thm that is Td =3D MIN(initial_timeout * 2^retry_count,=0A=
   maximum_timeout) and where the actual timeout is random*Td and where ran=
dom is a <br>random value from the uniform distribution in the interval [0.=
5,1.5]. Will both ensure<br>that the timout between two retransmissions nev=
er is less and on average grows with <br>a factor two. <br><br>This section=
 is also not defining a minimal initial timout value, or any method for <br=
>safely determine a more performant value from a safe initial value. To do =
a RTT <br>measurement using the AMT control messages would require some ext=
ensions but<br>could be a good way of deterimining a better initial value t=
han 0.5 seconds which <br>would be my recommendation for a default value. <=
br><br>S) Section 5.2.3.4.4<br><br>   If a gateway executes the relay disco=
very procedure at the start of=0A=
   each membership update cycle and the relay address returned in the=0A=
   latest Relay Advertisement message differs from the address returned=0A=
   in a previous Relay Advertisement message, then the gateway SHOULD=0A=
   send a Teardown message (if supported) to the old relay address,=0A=
   using information from the last Membership Query message received=0A=
   from that relay, as described in Section 5.2.3.7.  This behavior is=0A=
   illustrated in the following diagram. <br><br>This text and the figure a=
fter it does not appear to be consistent.<br>The figure implies a timer tha=
t isn't present in the above. The textual <br>description appears sensitive=
 to flapping anycast routing. I think<br>the figures indication of some hig=
her timeout before redoing Relay discovery <br>appears much more robust. <b=
r><br>T) Section 5.2.3.5.3<br>See R)<br>Also this text appears redundant to=
 previous text. Maybe generalize this<br>into its own section being used in=
 general for all messages needing retransmission<br><br>U) Section 5.2.3.5.=
4<br>   Querier's Query Interval Code carried by the general-query.  A=0A=
   gateway MAY use a smaller timer duration if required to refresh a NAT=0A=
   mapping that would otherwise timeout. <br><br>Maybe the protocol would r=
ather need a NAT keep-alive message to be sent<br>from the gateway to the r=
elay. But maybe the Request, Query cycle is light weight <br>enough that th=
is works fine. <br><br>V) Section 5.2.3.6.1<br><br>o  Insert IGMP or MLD da=
tagrams into a queue for transmission after=0A=
      it receives a Membership Query message.<br><br>What assumptions of qu=
eue depth exist in the above. Clearly the messages in this <br>queue should=
 expire if they become to old. <br><br>X) Section 5.2.3.7<br>Gateway suppor=
t for the Teardown message is OPTIONAL but RECOMMENDED.<br><br>The above is=
 a very strange usage of RFC 2119 keywords. IF you use the synonyms<br>then=
 maybe the error of writing it this way is clear. <br>Gateway MAY support f=
or the Teardown message but SHOULD. <br><br>Y) The usage of retransmission =
versus repetitions are not always clear.<br>Some of the messages appears to=
 simply need to be repeated QRV number of times with <br>some interval. Oth=
ers should really be matched with an answer and if not received within<br>t=
imeout retransmitted. Can these two cases be made more clear?<br><br>Z) Sec=
tion 5.3.5<br>   The hash function RECOMMENDED for use in computing the Res=
ponse MAC=0A=
   is the MD5 hash digest [RFC1321], though hash functions or keyed-hash=0A=
   functions of greater cryptographic strength may be used.<br>&nbsp;<br>I =
think this points to a security vulnerability. I think it needs to be made =
clear <br>that the MAC MUST be keyed. If it is just a digest, then an attac=
ker can calculate the <br>MAC and perform an off-path attack. <br><br>This =
should be made clear also in Section 6.1 to be a requirement.<br><br>AA) Se=
ction A.1:<br><br>Altough this proposals has its advantages I think it migh=
t also illustrate a <br>short-coming. First of all 48-bits is quite short f=
or a MAC. I would prefer a <br>variable length field.<br><br>Secondly, does=
n't this actually create more material for an attacker to determine<br>the =
key used by the relay?<br><br>That was all I have found. <br><br>Cheers<br>=
<br>Magnus<br><br></pre>
</div>
</body>
</html>

--_000_52E4A8FC978E0241AE652516E24CAF000E5FBCESESSMB309ericsso_--

From iad@ietf.org  Wed Dec 26 08:16:28 2012
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 99CFB21F8CDD; Wed, 26 Dec 2012 08:16:28 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h20qiJM2RAC1; Wed, 26 Dec 2012 08:16:28 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D63F21F8CDA; Wed, 26 Dec 2012 08:16:28 -0800 (PST)
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 93 Venue Announced
X-Test-IDTracker: no
X-IETF-IDTracker: 4.37
Message-ID: <20121226161628.10196.30551.idtracker@ietfa.amsl.com>
Date: Wed, 26 Dec 2012 08:16:28 -0800
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Dec 2012 16:16:28 -0000

The IAOC is pleased to announce Prague as the site for IETF 93 from July 19=
 - 24 2-15.  =

Prague was the site for IETF 68 in 2007 and IETF 80 in 2011.  =


Happy holidays and best wishes for the new year.

Ray Pelletier
IETF Administrative Director

2013
  IETF 86		Orlando		March 10-15			Host: Comcast and NBCUniversal
  IETF 87		Berlin		July 28 - August 2		Sponsors to date:  DENIC, Eurid *
  IETF 88		Vancouver	November 3-8			Host opportunity available *

* Contact Drew Dvorshak for Hosting and Sponsorship information  dvorshak@i=
soc.org

From bharat_joshi@infosys.com  Sun Dec 23 19:34:56 2012
Return-Path: <bharat_joshi@infosys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F4021F8BC4; Sun, 23 Dec 2012 19:34:56 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RhUvuo3-H08E; Sun, 23 Dec 2012 19:34:55 -0800 (PST)
Received: from kecgate06.infosys.com (kecgate06.infosys.com [122.98.14.33]) by ietfa.amsl.com (Postfix) with ESMTP id E625E21F8BB3; Sun, 23 Dec 2012 19:34:53 -0800 (PST)
X-TM-IMSS-Message-ID: <0426e0510027d947@infosys.com>
Received: from blrkechub04.ad.infosys.com ([10.66.236.44]) by infosys.com ([122.98.14.33]) with ESMTP (TREND IMSS SMTP Service 7.1) id 0426e0510027d947 ; Mon, 24 Dec 2012 09:08:06 +0530
Received: from BLRKECHUB10.ad.infosys.com (10.66.236.120) by blrkechub04.ad.infosys.com (10.66.236.44) with Microsoft SMTP Server (TLS) id 8.2.176.0; Mon, 24 Dec 2012 09:04:24 +0530
Received: from BLRKECMBX13.ad.infosys.com ([fe80::c43d:ba67:abc0:11c3]) by blrkechub10.ad.infosys.com ([::1]) with mapi id 14.02.0318.004; Mon, 24 Dec 2012 09:04:23 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: Ben Campbell <ben@nostrum.com>, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com>
Subject: RE: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Topic: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
Thread-Index: AQHN3i35+JDgXE0aqUaOeE64IeAUXJgi2lGAgAAwFACABEXLYw==
Date: Mon, 24 Dec 2012 03:34:23 +0000
Message-ID: <35347FBF2796F94E936EE76C0E6047ED2B643600@BLRKECMBX13.ad.infosys.com>
References: <BE996F07-CFB7-47F5-8B17-FA651C294FA3@nostrum.com> <F2B120E98374B2448745C1117BDA1854238F281F@BLRKECMBX23.ad.infosys.com>, <8C2DB2B9-B9DD-444B-B760-DED177907291@nostrum.com>
In-Reply-To: <8C2DB2B9-B9DD-444B-B760-DED177907291@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.37.13]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 27 Dec 2012 08:08:20 -0800
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org" <draft-ietf-dhc-relay-id-suboption.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: Mon, 24 Dec 2012 03:34:56 -0000

Hi Ben,

        One reply in line.

        We will bring out another revision after taking care of your sugg=
estions once we have some more review comments.

Regards,
Bharat

> Thanks for the timely response, and the background for the security
> language. 
> 
> This brings up one question, however. See inline: 
> 
> Thanks!
> 
> Ben.
> 
> On Dec 21, 2012, at 6:48 AM, RAMAKRISHNADTV <RAMAKRISHNADTV@infosys.com=
>
> wrote:
> 
> > Hi Ben,
> > 
> > Thank you for your review comments.
> > Please find my responses inline below.
> > 
> > Regards,
> > Ramakrishna DTV.
> > 
> >> -----Original Message-----
> >> From: Ben Campbell [mailto:ben@nostrum.com]
> >> Sent: Thursday, December 20, 2012 2:45 AM
> >> To: draft-ietf-dhc-relay-id-suboption.all@tools.ietf.org
> >> Cc: gen-art@ietf.org Review Team; ietf@ietf.org List
> >> Subject: Gen-ART LC Review of draft-ietf-dhc-relay-id-suboption-11
> >> 
> >> I am the assigned Gen-ART reviewer for this draft. For background on
> >> Gen-ART, please see the FAQ at
> >> 
> >> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >> 
> >> Please resolve these comments along with any other Last Call comment=
s
> >> you may receive.
> >> 
> >> Document: draft-ietf-dhc-relay-id-suboption-11
> >> Reviewer: Ben Campbell
> >> Review Date: 2012-12-19
> >> IETF LC End Date: 2013-01-07
> >> 
> >> Summary: This draft is basically ready for publication as a proposed
> >> standard. However, there is one comment from a prior review that I a=
m
> >> not sure whether is resolved.
> >> 
> >> Major issues:
> >> 
> >> None
> >> 
> >> Minor issues:
> >> 
> >> -- In Sean Turner's 2009 review of version 07 of the document [
> >> http://www.ietf.org/mail-archive/web/gen-art/current/msg04614.html ]=
,
> he
> >> made the following comment:
> >> 
> >>> In the security considerations it says look to RFC 3046 and
> >>> RFC 4030 for security considerations and then says SHOULD use the
> >> relay
> >>> agent authentication option from RFC 4030.  RFC 3046 is targeted at
> >>> network infrastructures that are "trusted and secure" and RFC 4030
> >>> allows the relay agent to be part of this trusted and secure
> network.
> >>> If an implementation doesn't use the relay agent authentication
> >> option,
> >>> then the relay agent can't be part of the "trusted and secure"
> >> network.
> > 
> > RFC3046 created the relay agent information option.
> > Relay agent information option exists only in the messages between
> > relay agents and DHCP servers. RFC3046 is targeted at network
> infrastructures
> > that are "trusted and secure" as far as the paths among relay agents
> and DHCP
> > servers is concerned. In many deployments, relay agents and DHCP
> servers
> > are under a single administrative control. By careful design and
> engineering
> > of the network, it is possible to ensure that the network
> infrastructure
> > comprising relay agents and DHCP server is trusted and secure. To
> achieve that,
> > RFC4030 may be used but is not a MUST. If not, RFC4030 would already
> be a MUST
> > for RFC3046 deployment. But that is not currently the case.
> 
> Is the SHOULD use 4030 language a new normative requirement, or is it
> simply describing existing requirements from 3046 or elsewhere?  If it'=
s
> a new normative requirement, then I am fine with your answer and
> withdraw the concern. If not, then it would be better to use descriptiv=
e
> rather than normative language in this draft.
> 

Yes.

Also as mentioned by Ted, this draft is using a language similar to some =
existing RFCs.
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended sol=
ely 
for the use of the addressee(s). If you are not the intended recipient, p=
lease 
notify the sender by e-mail and delete the original message. Further, you=
 are not 
to copy, disclose, or distribute this e-mail or its contents to any other=
 person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys h=
as taken 
every reasonable precaution to minimize this risk, but is not liable for =
any damage 
you may sustain as a result of any virus in this e-mail. You should carry=
 out your 
own virus checks before opening the e-mail or attachment. Infosys reserve=
s the 
right to monitor and review the content of all messages sent to or from t=
his e-mail 
address. Messages sent to or from this e-mail address may be stored on th=
e 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

From vkg@bell-labs.com  Mon Dec 24 11:03:08 2012
Return-Path: <vkg@bell-labs.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 972CD21F85CE; Mon, 24 Dec 2012 11:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.141
X-Spam-Level: 
X-Spam-Status: No, score=-109.141 tagged_above=-999 required=5 tests=[AWL=1.458, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0OVoaeOiV6s; Mon, 24 Dec 2012 11:03:07 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id AED7521F8599; Mon, 24 Dec 2012 11:03:07 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id qBOJ33RA016878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 24 Dec 2012 13:03:04 -0600 (CST)
Received: from umail.lucent.com (umail-ce2.ndc.lucent.com [135.3.40.63]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id qBOJ336a031581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 24 Dec 2012 13:03:03 -0600
Received: from shoonya.ih.lucent.com (shoonya.ih.lucent.com [135.185.237.229]) by umail.lucent.com (8.13.8/TPES) with ESMTP id qBOJ32Q8015232; Mon, 24 Dec 2012 13:03:03 -0600 (CST)
Message-ID: <50D8A750.2020005@bell-labs.com>
Date: Mon, 24 Dec 2012 13:04:48 -0600
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Organization: Bell Laboratories, Alcatel-Lucent
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: [sip-clf] Last Call: <draft-ietf-sipclf-problem-statement-11.txt> (The Common	Log Format (CLF) for the Session Initiation	Protocol (SIP):	Framework and Data Model) to Proposed Standard
References: <20121203204501.12217.39525.idtracker@ietfa.amsl.com> <9904FB1B0159DA42B0B887B7FA8119CA042028@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA042028@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
X-Mailman-Approved-At: Thu, 27 Dec 2012 08:08:20 -0800
Cc: "sip-clf@ietf.org" <sip-clf@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, 24 Dec 2012 19:03:08 -0000

Dan: Thank you for your review of the SIP CLF problem statement
draft.  I appreciate your time and resulting comments.

Please see inline on resolution of your comments.  I will be releasing
an updated version of the draft shortly with the resolutions contained
herein.

On 12/17/2012 10:02 AM, Romascanu, Dan (Dan) wrote:
> Hi,
>
> I believe that this is a good document and I support its approval.
>
> I do have a number of issues which I suggest to take into consideration before approval and publication:
>
> 1. In Section 4:
>
>   The SIP CLF is amenable to easy parsing and lends itself well to
>     creating other innovative tools.
>
> I am not sure what this sentence really says. What does 'easy parsing' mean? The previous paragraph referred to 'quick parsing (i.e., well-delimited fields)' - quick parsing is a relative notion but at least there was an example. Here, I do not know.
>
> What does 'other innovative tools' means escapes me totally. Why 'other'? 'other' than what? And what 'innovative tools' means?

I have changed the text to address your comment.  The change is as
follows:

OLD:

   The SIP CLF is amenable to easy parsing and lends itself well to
   creating other innovative tools.

NEW:

   Due to the structure imposed by delimited fields, the SIP CLF is
   amenable to easy parsing and lends itself well to creating other
   innovative tools such as logfile parsers and trend analytic engines.

> 2. In Section 11
>
>     SIP CLF log files will take up substantive amount of disk space
>     depending on traffic volume at a processing entity and the amount of
>     information being logged.  As such, any organization using SIP CLF
>     should establish operational procedures for file rollovers as
>     appropriate to the needs of the organization.
>
> Procedures for file rollovers is not enough - actually there need to be in place procedures for periodic retrieval of logs before rollover.

Added the phrase "periodic retrieval of logs before rollover" in S11.

> 3. [RFC3261] needs to be a Normative Reference. All this document speaks about logs for SIP, refers to SIP entities, messages, fields in the SIP messages - on short it cannot be understood and the SIP-CLF cannot be implemented without a good reading and understanding of [RFC3261].

I think it is a reasonable position that understanding rfc3261 is a pre-
requsite for implementing SIP CLF.  I have made rfc3261 normative as you
suggest.

Once again, thank you for your time and review of this work.

- vijay
-- 
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
Web:   http://ect.bell-labs.com/who/vkg/

From peter@akayla.com  Wed Dec 26 03:04:37 2012
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 975AA21F8AD2 for <ietf@ietfa.amsl.com>; Wed, 26 Dec 2012 03:04:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IAlKfC8WUTZl for <ietf@ietfa.amsl.com>; Wed, 26 Dec 2012 03:04:37 -0800 (PST)
Received: from smtpauth23.prod.mesa1.secureserver.net (smtpauth23.prod.mesa1.secureserver.net [64.202.165.47]) by ietfa.amsl.com (Postfix) with SMTP id C32D921F8808 for <ietf@ietf.org>; Wed, 26 Dec 2012 03:04:36 -0800 (PST)
Received: (qmail 28466 invoked from network); 26 Dec 2012 11:04:36 -0000
Received: from unknown (173.8.184.78) by smtpauth23.prod.mesa1.secureserver.net (64.202.165.47) with ESMTP; 26 Dec 2012 11:04:34 -0000
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-6man-udpchecksums.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-6man-udpchecksums-06
Date: Wed, 26 Dec 2012 03:05:01 -0800
Message-ID: <000701cde358$da44c6a0$8ece53e0$@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: Ac3jUy70UdbyWm97QlKDE0mhNpITcQ==
Content-Language: en-us
X-Mailman-Approved-At: Thu, 27 Dec 2012 08:08:20 -0800
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: Wed, 26 Dec 2012 11:04:37 -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-6man-udpchecksums-06
Reviewer: Peter Yee
Review Date: Dec-25-2012
IETF LC End Date: Dec-25-2012
IESG Telechat date: Unknown

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

This document provides an update to 2460 to allow the use of zero checksum
UDP packets over IPv6 in certain
cases involving protocols tunneled inside of UDP packets.

Nits:

General: a comma after "i.e." is preferred in American English.

General: it is not necessary to hyphenate "misdelivered" or "misdelivery".

General: put quotes around "Applicability Statement for the use of IPv6 UDP
Datagrams with Zero  Checksums"

Abstract, first sentence: "when" -> "where"

Abstract, second sentence: "protocol" -> "protocols"

Section 1, second paragraph, first sentence: delete the comma after
"packet".

Section 1, fourth paragraph, first sentence: move the comma in "AMT," to
after the reference.

Section 1, fourth paragraph, last sentence: insert "the" after "applicable
in".

Section 3, second sentence: delete the first occurrence of "where".
Consider revising the sentence for clarity.

Section 4, second sentence: "Section" -> "Sections"

Section 4.1, it would be nice, but not necessary to have an enumeration of
the corruption modes.  

Section 4.1, third bullet item, first sentence: a verb is missing here
making the sentence difficult to parse.

Section 4.1, third bullet item, first sentence: "packets" -> "packet"

Section 4.1, third bullet item, third sub-bullet: put commas around "for
example".

Section 4.2, first bullet item, last sentence: this sentence is hard to
understand; consider revising.  (See next comment)

Section 4.2, first bullet item, last sentence: "an" -> "a" and "are" ->
"is"; also not general comment about "misdelivered".

Section 4.2, third bullet item, third sentence: "effect" -> "affect"

Section 4.2, first paragraph after bullet items, first sentence: delete
"this".

Section 4.2, first paragraph after bullet items, third sentence:
"mis-delievery" -> "misdelivery".

Section 4.2, first paragraph after bullet items, third sentence: delete
"that".

Section 4.3, first sentence: "middlebox devices" -> "middleboxes" unless
this a specific usage from I-D.ietf-6man-udpzero.

Section 4.3, second sentence: "needs" -> "need"

Section 5, first paragraph, second sentence: insert "in" after "node
requirements".

Section 5, first paragraph of replacement text, second sentence: delete
"usage for", replace "some" with "certain", and replace second "protocols"
with "those".

Section 5, last paragraph: delete first instance of "the".

Section 6, first bullet item, first sentence: "corruptions" -> "corruption"

Section 6, second bullet item, last sentence: change "This" to "UDP-Lite".

Section 8, first sentence: delete redundant "required".


From narten@us.ibm.com  Thu Dec 27 21:53:10 2012
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 08B0721F8DEA for <ietf@ietfa.amsl.com>; Thu, 27 Dec 2012 21:53:10 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jyYVRUK8POFt for <ietf@ietfa.amsl.com>; Thu, 27 Dec 2012 21:53:09 -0800 (PST)
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by ietfa.amsl.com (Postfix) with ESMTP id 077BB21F8CDE for <ietf@ietf.org>; Thu, 27 Dec 2012 21:53:08 -0800 (PST)
Received: from /spool/local by e31.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, 27 Dec 2012 22:53:06 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 27 Dec 2012 22:53:04 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 416881FF001C for <ietf@ietf.org>; Thu, 27 Dec 2012 22:52:55 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qBS5r3Wf282344 for <ietf@ietf.org>; Thu, 27 Dec 2012 22:53:03 -0700
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qBS5r3nL013005 for <ietf@ietf.org>; Thu, 27 Dec 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qBS5r3pp012987 for <ietf@ietf.org>; Thu, 27 Dec 2012 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qBS5r2Mg010788 for <ietf@ietf.org>; Fri, 28 Dec 2012 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id qBS5r2t8010744 for ietf@ietf.org; Fri, 28 Dec 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201212280553.qBS5r2t8010744@rotala.raleigh.ibm.com>
Date: Fri, 28 Dec 2012 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12122805-7282-0000-0000-0000128C0AA0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Dec 2012 05:53:10 -0000

Total of 22 messages in the last 7 days.
 
script run at: Fri Dec 28 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.55% |    1 | 21.75% |    44263 | magnus.westerlund@ericsson.com
 13.64% |    3 | 11.67% |    23748 | ben@nostrum.com
  9.09% |    2 |  9.32% |    18965 | rbonica@juniper.net
  9.09% |    2 |  6.87% |    13988 | ted.lemon@nominum.com
  9.09% |    2 |  6.43% |    13095 | sm@resistor.net
  9.09% |    2 |  6.11% |    12429 | peter@akayla.com
  4.55% |    1 |  5.14% |    10470 | ramakrishnadtv@infosys.com
  4.55% |    1 |  4.94% |    10047 | bharat_joshi@infosys.com
  4.55% |    1 |  4.31% |     8766 | hkaplan@acmepacket.com
  4.55% |    1 |  4.28% |     8707 | narten@us.ibm.com
  4.55% |    1 |  4.05% |     8249 | vkg@bell-labs.com
  4.55% |    1 |  3.82% |     7773 | gsalguei@cisco.com
  4.55% |    1 |  3.14% |     6391 | presnick@qti.qualcomm.com
  4.55% |    1 |  2.98% |     6057 | john-ietf@jck.com
  4.55% |    1 |  2.90% |     5909 | randy@psg.com
  4.55% |    1 |  2.31% |     4695 | iad@ietf.org
--------+------+--------+----------+------------------------
100.00% |   22 |100.00% |   203552 | Total


From daedulus@btconnect.com  Fri Dec 28 02:05:53 2012
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 EEE3921F8510 for <ietf@ietfa.amsl.com>; Fri, 28 Dec 2012 02:05:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.104
X-Spam-Level: 
X-Spam-Status: No, score=-5.104 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_05=-1.11, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HwYP4jfUKOQu for <ietf@ietfa.amsl.com>; Fri, 28 Dec 2012 02:05:53 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe003.messaging.microsoft.com [65.55.88.13]) by ietfa.amsl.com (Postfix) with ESMTP id 7715B21F84F3 for <ietf@ietf.org>; Fri, 28 Dec 2012 02:05:52 -0800 (PST)
Received: from mail34-tx2-R.bigfish.com (10.9.14.249) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.23; Fri, 28 Dec 2012 10:05:51 +0000
Received: from mail34-tx2 (localhost [127.0.0.1])	by mail34-tx2-R.bigfish.com (Postfix) with ESMTP id 679C72C0187	for <ietf@ietf.org>; Fri, 28 Dec 2012 10:05:51 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(z551biz9371Ic89bhd6eah1521I542Izz1de0h1202h1e76h1d1ah1d2ahzz8275dh1033IL177df4h5eeeK17326ahz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h304l1155h)
Received: from mail34-tx2 (localhost.localdomain [127.0.0.1]) by mail34-tx2 (MessageSwitch) id 1356689100408422_15937; Fri, 28 Dec 2012 10:05:00 +0000 (UTC)
Received: from TX2EHSMHS043.bigfish.com (unknown [10.9.14.244])	by mail34-tx2.bigfish.com (Postfix) with ESMTP id 41F4C3A0079	for <ietf@ietf.org>; Fri, 28 Dec 2012 10:04:59 +0000 (UTC)
Received: from DBXPRD0710HT001.eurprd07.prod.outlook.com (157.56.253.197) by TX2EHSMHS043.bigfish.com (10.9.99.143) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 28 Dec 2012 10:04:59 +0000
Received: from DB3PRD0210HT002.eurprd02.prod.outlook.com (157.56.253.69) by pod51017.outlook.com (10.255.79.164) with Microsoft SMTP Server (TLS) id 14.16.245.2; Fri, 28 Dec 2012 10:04:54 +0000
Message-ID: <00f301cde4e2$807f9880$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: ietf <ietf@ietf.org>
Subject: Fw: Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring
Date: Fri, 28 Dec 2012 10:02:46 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
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.69]
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.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, 28 Dec 2012 10:05:54 -0000

I wonder if anyone else has read and understood this.  I have read it,
but, pdf of a slide show that it is, I could not claim to understand
it - perhaps there is text available that would make it clearer.  I do
see the bit that is like the old, IP, Classful address structure, that
the IETF tried and found wanting, but what that classful structure is
actually used for (and whether or not it will be found wanting), I
cannot tell.

Tom Petch

----- Original Message -----
From: "IAB Chair" <iab-chair@iab.org>
To: <ietf-announce@ietf.org>
Sent: Thursday, December 13, 2012 3:37 AM
Subject: Feedback Requested: Proposed IEEE RAC OUI Tier Restructuring


The IEEE Registration Authority Committee (RAC) has requested IETF
feedback on a proposal for restructuring of the Organizational Unique
Identifier (OUI) within the IEEE 802 Medium Access Control (MAC)
Address.  Information on the proposal is available here:

http://www.ietf.org/iesg/ieee/20120725/RAC_Virtualization_July2012.pdf

http://ieee802.org/secmail/msg15524.html

Comments should be sent to Glenn Parsons <gparsons@ieee.org> and cc=E2=80=
=99d to
iab@iab.org.





From hallam@gmail.com  Fri Dec 28 22:26:58 2012
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 6C3FB21F851E for <ietf@ietfa.amsl.com>; Fri, 28 Dec 2012 22:26:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.362
X-Spam-Level: 
X-Spam-Status: No, score=-2.362 tagged_above=-999 required=5 tests=[AWL=-1.364, BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qfw3isen1kOz for <ietf@ietfa.amsl.com>; Fri, 28 Dec 2012 22:26:57 -0800 (PST)
Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com [209.85.214.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB0D21F843C for <ietf@ietf.org>; Fri, 28 Dec 2012 22:26:57 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id vb8so10139200obc.6 for <ietf@ietf.org>; Fri, 28 Dec 2012 22:26:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=uzvrdHVBCkbq+DozlKpzx2EMmDXl0z+cOMn/5/WWoR8=; b=TNvxmoKp1aMg6zQXNhsY5RPpW5II8lsYRVPQl9M9HshgJdaL9sH/MA4vnIdxEdWLNu v4EtIr/KodFPMv9P0vIP3W4vXLl6U41up04LyTyQoPGe/HIRDR6q6JWJOupecMklEIB0 61gfjlsjgV4KVgMFuISvf5z5hIfNRzwk2FXNtjaRndRgrdHG5EqiixFgmd+3biTaeQJR 4rXionNpTZ/RjIboHJaj//ah8osO5zREedXREB5VFSfmXAEFifsVzPqNCtKcRb0QU9L+ jDNw5AIKVROEdqQnIUeaFpolWsNAsF8Vkc6WHNFRTA2HtF0HErKaIEenKg3C0w3J/Mgc f+ug==
MIME-Version: 1.0
Received: by 10.60.8.199 with SMTP id t7mr16849077oea.26.1356762416736; Fri, 28 Dec 2012 22:26:56 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Fri, 28 Dec 2012 22:26:56 -0800 (PST)
Date: Sat, 29 Dec 2012 01:26:56 -0500
Message-ID: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>
Subject: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ff1ce46e4e7fa04d1f7dd09
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Dec 2012 06:26:58 -0000

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

We seem to have missed a discussion on the outcome of the Dubai WCIT
conference, or rather the lack of one.

The end result was a treaty that 54 countries refused to sign. The
non-signatories being the major developed economies including UK, US,
Japan, Germany, Canada. Many of the signatories have signed with
reservations.

Back at the dawn of the computer industry, IBM was a very late entrant but
it quickly came to dominate the industry by building on the commercial base
it had established in punchcard tabulator machines. There was a real risk
that ITU might have managed to pull off something similar by convincing
governments that there needed to be a global regulatory body for
communications and that the ITU should be that body.

Instead they seem to have pulled off the equivalent of OS/@ and
microchannel architecture which were the marketing moves that were intended
to allow IBM to consolidate its hold on the PC industry but instead lead to
the rise of the Windows and the EISA bus clones.

It now seems reasonably clear that the ITU was an accident of history that
resulted from a particular set of economic and technical limitations. The
ITU was founded when each country had exactly one telephone company and
almost all were government controlled. One country one vote was an
acceptable approach in those days because there was only one telephone
company per country. The telephone companies were the only stakeholders
needed to implement a proposal.

The old telephone system is fading away. It is becoming an Internet
application just as the pocket calculator has become a desktop application.
And as it passes, the institutions it founded are looking for new roles.
There is no particular reason that this must happen.

The stakeholders in the Internet don't even align to countries. My own
employer is relatively small but was founded in the UK, moved its
headquarters to the US and has operations in a dozen more countries and
many times that number of affiliates. The same is even more true of the
likes of Google, Cisco, Apple, IBM, Microsoft etc.

A standards process is a two way negotiation. There are things that I want
other people to implement in their products and there are things that they
want me to implement in mine. The second one is actually rather more
important than the first. Having the process mediated by government
employees does not appear to add any value to the process to me and seems
to be a complete waste of time for them.

What is not a waste of time for governments is to look at the control
points in the technology infrastructures the emerging economy depends on.
Radio spectrum and geostationary orbit slots are finite resources and no
country can afford to be locked out of the new economy because of the lack
of access to them.

There are some control points in the Internet but they are rather less
critical than many imagine. IPv6 address space allocations, DNS zone
management and AIS numbers are arguably control points.

If we can eliminate the control point nature of those resources then the
essential government needs in Internet regulation will have been met and
the need for the ITU to be involved will disappear entirely. There are
still concerns that an ITU-like body could usefully address. A treaty
baring cyber-sabotage would be an important and useful effort that demands
a diplomatic approach.



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

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

We seem to have missed a discussion on the outcome of the Dubai WCIT confer=
ence, or rather the lack of one.<div><br></div><div>The end result was a tr=
eaty that 54 countries refused to sign. The non-signatories being the major=
 developed economies including UK, US, Japan, Germany, Canada. Many of the =
signatories have signed with reservations.</div>
<div><br></div><div>Back at the dawn of the computer industry, IBM was a ve=
ry late entrant but it quickly came to dominate the industry by building on=
 the commercial base it had established in punchcard tabulator machines. Th=
ere was a real risk that ITU might have managed to pull off something simil=
ar by convincing governments that there needed to be a global regulatory bo=
dy for communications and that the ITU should be that body.</div>
<div><br></div><div>Instead they seem to have pulled off the equivalent of =
OS/@ and microchannel architecture which were the marketing moves that were=
 intended to allow IBM to consolidate its hold on the PC industry but inste=
ad lead to the rise of the Windows and the EISA bus clones.=A0</div>
<div><br></div><div>It now seems reasonably clear that the ITU was an accid=
ent of history that resulted from a particular set of economic and technica=
l limitations. The ITU was founded when each country had exactly one teleph=
one company and almost all were government controlled. One country one vote=
 was an acceptable approach in those days because there was only one teleph=
one company per country. The telephone companies were the only stakeholders=
 needed to implement a proposal.</div>
<div><br></div><div>The old telephone system is fading away. It is becoming=
 an Internet application just as the pocket calculator has become a desktop=
 application. And as it passes, the institutions it founded are looking for=
 new roles. There is no particular reason that this must happen.</div>
<div><br clear=3D"all"><div>The stakeholders in the Internet don&#39;t even=
 align to countries. My own employer is relatively small but was founded in=
 the UK, moved its headquarters to the US and has operations in a dozen mor=
e countries and many times that number of=A0affiliates. The same is even mo=
re true of the likes of Google, Cisco, Apple, IBM, Microsoft etc.</div>
<div><br></div><div>A standards process is a two way negotiation. There are=
 things that I want other people to implement in their products and there a=
re things that they want me to implement in mine. The second one is actuall=
y rather more important than the first. Having the process mediated by gove=
rnment employees does not appear to add any value to the process to me and =
seems to be a complete waste of time for them.=A0</div>
<div><br></div><div>What is not a waste of time for governments is to look =
at the control points in the technology infrastructures the emerging econom=
y depends on. Radio spectrum and geostationary orbit slots are finite resou=
rces and no country can afford to be locked out of the new economy because =
of the lack of access to them.</div>
<div><br></div><div>There are some control points in the Internet but they =
are rather less critical than many imagine. IPv6 address space allocations,=
 DNS zone management and AIS numbers are arguably control points.</div>
<div><br></div><div>If we can eliminate the control point nature of those r=
esources then the essential government needs in Internet regulation will ha=
ve been met and the need for the ITU to be involved will disappear entirely=
.=A0There are still concerns that an ITU-like body could usefully address. =
A treaty baring cyber-sabotage would be an important and useful effort that=
 demands a diplomatic approach.</div>
<div><br></div><div><br></div><div><br></div>-- <br>Website: <a href=3D"htt=
p://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--e89a8ff1ce46e4e7fa04d1f7dd09--

From jmamodio@gmail.com  Sat Dec 29 02:43:11 2012
Return-Path: <jmamodio@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 AAB5421F854E for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 02:43:11 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ky3N3Xmj3NiJ for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 02:43:10 -0800 (PST)
Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) by ietfa.amsl.com (Postfix) with ESMTP id 47C5221F8521 for <ietf@ietf.org>; Sat, 29 Dec 2012 02:43:10 -0800 (PST)
Received: by mail-vc0-f173.google.com with SMTP id f13so11470175vcb.4 for <ietf@ietf.org>; Sat, 29 Dec 2012 02:43:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hoBNzPBBMRsUSOa8ndAJZTd7Olaqt7GD+LVES49c2Qg=; b=mo3CboWLk1isNswujUvC4DKQ8oTBMXPhXizloSoWfloPJSoccrDmfVhrZaotK/1ZXB oNM2S7PI73B7FWjjBTSIX7avk7YPE7R0wdzg5Yu0cLiFzMOhjD47tPIr18Bl9I7yl6aG cAFnvpFLh4pIZk430BOGb4O8/Eqe9GMqTXXhPaUJnHHnkxxHH05hahP9x/O/HNyU7Y8u Ce2wj2KEls6uVshumyX0hjf6Em5gHvuR4FuETu3sTkNBSH9PChbGVVM1Ji/cH/Iv5IRE IgwpuTxHNyYZFvH33Cdc4sLIAFveYxGWnCtjgIm4my/n2eV9qyAi4Th1dd8i7tOJatWN K8hw==
MIME-Version: 1.0
Received: by 10.220.238.139 with SMTP id ks11mr54075550vcb.49.1356777789395; Sat, 29 Dec 2012 02:43:09 -0800 (PST)
Received: by 10.58.94.76 with HTTP; Sat, 29 Dec 2012 02:43:09 -0800 (PST)
In-Reply-To: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>
Date: Sat, 29 Dec 2012 04:43:09 -0600
Message-ID: <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Jorge Amodio <jmamodio@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=14dae9cfc84a2d117e04d1fb7274
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, 29 Dec 2012 10:43:11 -0000

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

ITU was founded previously as the International Telegraph Union before AG
Bell's phone was patented, no doubt the evolution of telecommunications and
the Internet puts ITU with its current behavior in the path of becoming
obsolete and extinct, but you can't discount many positive contributions
particularly from the standards section.

As the multistakeholder model and its associated processes, which is far
from perfect, continues to evolve, ITU must be part of the evolution. The
issue is that as an organization they must accommodate and realize that now
they are "part of it" and not "it" anymore.

There is also a big confusion and still lack of a clear consensus on what
"Internet governance" means or entitles, and many take it as "governing the
Internet," hence governments want a piece of the action, and the constant
and many times intended perception that the Internet is controlled by the
USG and its development and evolution is US centric, which I believe at
IETF we know since long time ago is not true. But many countries, and as
you well say those where there was or still is a single telecom operator
and controlled by government, see it that way.

About the countries that signed, not many but most did it with
reservations, and those that didn't sign probably represent 2/3 or more of
the telecom market/industry. An interesting observation after spending
countless hours following the meeting, some of the countries that were
pushing the discussion for a reference to the universal declaration of
human rights are the ones who don't care much about them, particularly in
respect to women, and on the other hand others complaining about
discrimination and restricted access to the Internet are the ones currently
filtering on the big pipes and have the Internet as the first thing on
their list to shutdown during internal turmoil.

The same forces that pushed at WCIT will keep doing the same thing on other
international fora to insist with their Internet governance agenda, the
ITRs will become effective in Jan 2015, two years, which on Internet time
is an eternity, and it will be only valid if those countries that signed
ratify the treaty. Meanwhile packets keep flowing, faster, bigger and with
more destinations, not bad for a packet switching network that was not
supposed to work. (During WCIT I was wondering, could you imagine doing the
webcast via X.25? )

I agree that it is not clear what the outcome of WCIT12 was, but something
that is clear is that ITU needs to evolve, or as Vint characterized them,
the "dinosaurs" will become extinct.

Cheers, Happy Holidays and great start for 2013
Jorge
http://about.me/jamodio



On Sat, Dec 29, 2012 at 12:26 AM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> We seem to have missed a discussion on the outcome of the Dubai WCIT
> conference, or rather the lack of one.
>
> The end result was a treaty that 54 countries refused to sign. The
> non-signatories being the major developed economies including UK, US,
> Japan, Germany, Canada. Many of the signatories have signed with
> reservations.
>
> Back at the dawn of the computer industry, IBM was a very late entrant but
> it quickly came to dominate the industry by building on the commercial base
> it had established in punchcard tabulator machines. There was a real risk
> that ITU might have managed to pull off something similar by convincing
> governments that there needed to be a global regulatory body for
> communications and that the ITU should be that body.
>
> Instead they seem to have pulled off the equivalent of OS/@ and
> microchannel architecture which were the marketing moves that were intended
> to allow IBM to consolidate its hold on the PC industry but instead lead to
> the rise of the Windows and the EISA bus clones.
>
> It now seems reasonably clear that the ITU was an accident of history that
> resulted from a particular set of economic and technical limitations. The
> ITU was founded when each country had exactly one telephone company and
> almost all were government controlled. One country one vote was an
> acceptable approach in those days because there was only one telephone
> company per country. The telephone companies were the only stakeholders
> needed to implement a proposal.
>
> The old telephone system is fading away. It is becoming an Internet
> application just as the pocket calculator has become a desktop application.
> And as it passes, the institutions it founded are looking for new roles.
> There is no particular reason that this must happen.
>
> The stakeholders in the Internet don't even align to countries. My own
> employer is relatively small but was founded in the UK, moved its
> headquarters to the US and has operations in a dozen more countries and
> many times that number of affiliates. The same is even more true of the
> likes of Google, Cisco, Apple, IBM, Microsoft etc.
>
> A standards process is a two way negotiation. There are things that I want
> other people to implement in their products and there are things that they
> want me to implement in mine. The second one is actually rather more
> important than the first. Having the process mediated by government
> employees does not appear to add any value to the process to me and seems
> to be a complete waste of time for them.
>
> What is not a waste of time for governments is to look at the control
> points in the technology infrastructures the emerging economy depends on.
> Radio spectrum and geostationary orbit slots are finite resources and no
> country can afford to be locked out of the new economy because of the lack
> of access to them.
>
> There are some control points in the Internet but they are rather less
> critical than many imagine. IPv6 address space allocations, DNS zone
> management and AIS numbers are arguably control points.
>
> If we can eliminate the control point nature of those resources then the
> essential government needs in Internet regulation will have been met and
> the need for the ITU to be involved will disappear entirely. There are
> still concerns that an ITU-like body could usefully address. A treaty
> baring cyber-sabotage would be an important and useful effort that demands
> a diplomatic approach.
>
>
>
> --
> Website: http://hallambaker.com/
>

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

<div dir=3D"ltr"><br><div style>ITU was founded=A0previously=A0as the Inter=
national Telegraph Union before AG Bell&#39;s phone was patented, no doubt =
the evolution of telecommunications and the Internet puts ITU with its curr=
ent behavior in the path of becoming obsolete and extinct, but you can&#39;=
t discount many positive contributions particularly from the standards sect=
ion.</div>
<div style><br></div><div style>As the multistakeholder model and its assoc=
iated processes, which is far from perfect, continues to evolve, ITU must b=
e part of the evolution. The issue is that as an organization they must acc=
ommodate and realize that now they are &quot;part of it&quot; and not &quot=
;it&quot; anymore.</div>
<div style><br></div><div style>There is also a big confusion and still lac=
k of a clear consensus on what &quot;Internet governance&quot; means or ent=
itles, and many take it as &quot;governing the Internet,&quot; hence govern=
ments want a piece of the action, and the constant and many times intended =
perception that the Internet is controlled by the USG and its development a=
nd evolution is US centric, which I believe at IETF we know since long time=
 ago is not true. But many countries, and as you well say those where there=
 was or still is a single telecom operator and controlled by government, se=
e it that way.</div>
<div style><br></div><div style>About the countries that signed, not many b=
ut most did it with reservations, and those that didn&#39;t sign probably r=
epresent 2/3 or more of the telecom market/industry. An interesting observa=
tion after spending countless hours following the meeting, some of the coun=
tries that were pushing the discussion for a reference to the universal dec=
laration of human rights are the ones who don&#39;t care much about them, p=
articularly in respect to women, and on the other hand others complaining a=
bout discrimination and restricted access to the Internet are the ones curr=
ently filtering on the big pipes and have the Internet as the first thing o=
n their list to shutdown during internal=A0turmoil.</div>
<div style><br></div><div style>The same forces that pushed at WCIT will ke=
ep doing the same thing on other international fora to insist with their In=
ternet governance agenda, the ITRs will become effective in Jan 2015, two y=
ears, which on Internet time is an eternity, and it will be only valid if t=
hose countries that signed ratify the treaty. Meanwhile packets keep flowin=
g, faster, bigger and with more destinations, not bad for a packet switchin=
g network that was not supposed to work. (During WCIT I was wondering, coul=
d you imagine doing the webcast via X.25? )</div>
<div style><br></div><div style>I agree that it is not clear what the outco=
me of WCIT12 was, but something that is clear is that ITU needs to evolve, =
or as Vint=A0characterized=A0them, the &quot;dinosaurs&quot; will become ex=
tinct.</div>
<div style><br></div><div style>Cheers, Happy Holidays and great start for =
2013</div><div style>Jorge</div><div style><a href=3D"http://about.me/jamod=
io">http://about.me/jamodio</a></div><div style><br></div></div><div class=
=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Sat, Dec 29, 2012 at 12:26 AM, Philli=
p Hallam-Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.com" ta=
rget=3D"_blank">hallam@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
We seem to have missed a discussion on the outcome of the Dubai WCIT confer=
ence, or rather the lack of one.<div><br></div><div>The end result was a tr=
eaty that 54 countries refused to sign. The non-signatories being the major=
 developed economies including UK, US, Japan, Germany, Canada. Many of the =
signatories have signed with reservations.</div>

<div><br></div><div>Back at the dawn of the computer industry, IBM was a ve=
ry late entrant but it quickly came to dominate the industry by building on=
 the commercial base it had established in punchcard tabulator machines. Th=
ere was a real risk that ITU might have managed to pull off something simil=
ar by convincing governments that there needed to be a global regulatory bo=
dy for communications and that the ITU should be that body.</div>

<div><br></div><div>Instead they seem to have pulled off the equivalent of =
OS/@ and microchannel architecture which were the marketing moves that were=
 intended to allow IBM to consolidate its hold on the PC industry but inste=
ad lead to the rise of the Windows and the EISA bus clones.=A0</div>

<div><br></div><div>It now seems reasonably clear that the ITU was an accid=
ent of history that resulted from a particular set of economic and technica=
l limitations. The ITU was founded when each country had exactly one teleph=
one company and almost all were government controlled. One country one vote=
 was an acceptable approach in those days because there was only one teleph=
one company per country. The telephone companies were the only stakeholders=
 needed to implement a proposal.</div>

<div><br></div><div>The old telephone system is fading away. It is becoming=
 an Internet application just as the pocket calculator has become a desktop=
 application. And as it passes, the institutions it founded are looking for=
 new roles. There is no particular reason that this must happen.</div>

<div><br clear=3D"all"><div>The stakeholders in the Internet don&#39;t even=
 align to countries. My own employer is relatively small but was founded in=
 the UK, moved its headquarters to the US and has operations in a dozen mor=
e countries and many times that number of=A0affiliates. The same is even mo=
re true of the likes of Google, Cisco, Apple, IBM, Microsoft etc.</div>

<div><br></div><div>A standards process is a two way negotiation. There are=
 things that I want other people to implement in their products and there a=
re things that they want me to implement in mine. The second one is actuall=
y rather more important than the first. Having the process mediated by gove=
rnment employees does not appear to add any value to the process to me and =
seems to be a complete waste of time for them.=A0</div>

<div><br></div><div>What is not a waste of time for governments is to look =
at the control points in the technology infrastructures the emerging econom=
y depends on. Radio spectrum and geostationary orbit slots are finite resou=
rces and no country can afford to be locked out of the new economy because =
of the lack of access to them.</div>

<div><br></div><div>There are some control points in the Internet but they =
are rather less critical than many imagine. IPv6 address space allocations,=
 DNS zone management and AIS numbers are arguably control points.</div>

<div><br></div><div>If we can eliminate the control point nature of those r=
esources then the essential government needs in Internet regulation will ha=
ve been met and the need for the ITU to be involved will disappear entirely=
.=A0There are still concerns that an ITU-like body could usefully address. =
A treaty baring cyber-sabotage would be an important and useful effort that=
 demands a diplomatic approach.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div><br></div><div><br></div>-- <br>Website: <a href=3D"htt=
p://hallambaker.com/" target=3D"_blank">http://hallambaker.com/</a><br>
</font></span></div>
</blockquote></div><br></div>

--14dae9cfc84a2d117e04d1fb7274--

From mohta@necom830.hpcl.titech.ac.jp  Sat Dec 29 04:20:28 2012
Return-Path: <mohta@necom830.hpcl.titech.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 7E46321F84A1 for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 04:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.399
X-Spam-Level: *
X-Spam-Status: No, score=1.399 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SB85GZ9f5rXm for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 04:20:28 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 9FED921F849A for <ietf@ietf.org>; Sat, 29 Dec 2012 04:20:27 -0800 (PST)
Received: (qmail 9887 invoked from network); 29 Dec 2012 12:19:33 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 29 Dec 2012 12:19:33 -0000
Message-ID: <50DEDFAF.4050209@necom830.hpcl.titech.ac.jp>
Date: Sat, 29 Dec 2012 21:18:55 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>
In-Reply-To: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-2022-JP
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, 29 Dec 2012 12:20:28 -0000

Phillip Hallam-Baker wrote:

> The stakeholders in the Internet don't even align to countries. My own
> employer is relatively small but was founded in the UK, moved its
> headquarters to the US and has operations in a dozen more countries and
> many times that number of affiliates. The same is even more true of the
> likes of Google, Cisco, Apple, IBM, Microsoft etc.

You miss the most important stakeholders, the end users aligning
to countries.

						Masataka Ohta

PS

Of course, countries acting as representatives for telephone
companies are just as bad as countries acing as representatives
for ISPs.

From dhc@dcrocker.net  Sat Dec 29 07:18:41 2012
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 66D6921F8623 for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 07:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.185
X-Spam-Level: 
X-Spam-Status: No, score=-4.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdL7xKBFOLnW for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 07:18:40 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 73DD421F85FE for <ietf@ietf.org>; Sat, 29 Dec 2012 07:18:40 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qBTFId0Y020919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sat, 29 Dec 2012 07:18:39 -0800
Message-ID: <50DF09C7.1060009@dcrocker.net>
Date: Sat, 29 Dec 2012 07:18:31 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: travel guide for the next IETF...
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.17]); Sat, 29 Dec 2012 07:18:39 -0800 (PST)
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, 29 Dec 2012 15:18:41 -0000

      Going Beyond Disney in Orlando

      "Quick, name five reasons to go to Orlando. Here are mine: Puerto 
Rican delicacies, alternative cinema, craft beer, African-American 
history and psychic readings..."

 
http://frugaltraveler.blogs.nytimes.com/2012/12/27/going-beyond-disney-in-orlando/?nl=travel&emc=edit_tl_20121229

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From gjshep@gmail.com  Sat Dec 29 07:29:02 2012
Return-Path: <gjshep@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 B475B21F8623 for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 07:29:02 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwXuyejTftcz for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 07:29:02 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADEA21F861B for <ietf@ietf.org>; Sat, 29 Dec 2012 07:29:02 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id k14so10589319oag.28 for <ietf@ietf.org>; Sat, 29 Dec 2012 07:29:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=vMYYy/xQNudcEqCEFKSXr542TogxTnIl/Mar1c/nKHY=; b=K2JG61SimFkj/mhxQphB4j3EF892mT7tl/eS/L1XUawRsWC+uoqqGRd4VSHtM5g3F4 NMTHK+MNiL2m+UPZrC4ei8lNpjvFT3wttBw8B51SelPdfuEOn5TS/kM6SyCEfCprvvxt 4GV1NOg72HobUwsFUL2dh/+XVprnkbrVuKUi/gXqh5JlZYCgTkjoad38kyieEwoLlLXd GIaNgao88J33n/ZeYXiE4BoGpiIOkcgpH55bTCp7tTYKKBJMGF1vm+4eOwx6JTZf7rup 848YU19X6Qajm0Tw7bhjBKFjtRe4JcdNgC049wbhWjAs2Sy/uchnzsfIR0no4iT6LMgj sbJg==
MIME-Version: 1.0
Received: by 10.60.28.133 with SMTP id b5mr17953106oeh.98.1356794941448; Sat, 29 Dec 2012 07:29:01 -0800 (PST)
Received: by 10.76.105.107 with HTTP; Sat, 29 Dec 2012 07:29:01 -0800 (PST)
In-Reply-To: <50DF09C7.1060009@dcrocker.net>
References: <50DF09C7.1060009@dcrocker.net>
Date: Sat, 29 Dec 2012 07:29:01 -0800
Message-ID: <CABFReBovBcHKM-4iRKV_jA5xC8a81h4B=WdOAn5HxJgp+iGhcQ@mail.gmail.com>
Subject: Re: travel guide for the next IETF...
From: Greg Shepherd <gjshep@gmail.com>
To: dcrocker@bbiw.net
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
Reply-To: gjshep@gmail.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: Sat, 29 Dec 2012 15:29:02 -0000

City of Celebration - it's more than just a movie set. Freakiest place on earth.

On Sat, Dec 29, 2012 at 7:18 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>
>      Going Beyond Disney in Orlando
>
>      "Quick, name five reasons to go to Orlando. Here are mine: Puerto Rican
> delicacies, alternative cinema, craft beer, African-American history and
> psychic readings..."
>
>
> http://frugaltraveler.blogs.nytimes.com/2012/12/27/going-beyond-disney-in-orlando/?nl=travel&emc=edit_tl_20121229
>
> d/
> --
>  Dave Crocker
>  Brandenburg InternetWorking
>  bbiw.net

From dhc@dcrocker.net  Sat Dec 29 08:54:21 2012
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 06C1121F86DC for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 08:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level: 
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[AWL=1.207,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGuqxpS4yUnQ for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 08:54:20 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 84EC421F86CD for <ietf@ietf.org>; Sat, 29 Dec 2012 08:54:20 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id qBTGsJjJ022387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 29 Dec 2012 08:54:19 -0800
Message-ID: <50DF2033.4010908@dcrocker.net>
Date: Sat, 29 Dec 2012 08:54:11 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: gjshep@gmail.com
Subject: Re: travel guide for the next IETF...
References: <50DF09C7.1060009@dcrocker.net> <CABFReBovBcHKM-4iRKV_jA5xC8a81h4B=WdOAn5HxJgp+iGhcQ@mail.gmail.com>
In-Reply-To: <CABFReBovBcHKM-4iRKV_jA5xC8a81h4B=WdOAn5HxJgp+iGhcQ@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.17]); Sat, 29 Dec 2012 08:54:19 -0800 (PST)
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: Sat, 29 Dec 2012 16:54:21 -0000

On 12/29/2012 7:29 AM, Greg Shepherd wrote:
> Freakiest place on earth.


uh oh.  now you've invited a debate...

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From hallam@gmail.com  Sat Dec 29 10:19:09 2012
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 2D38B21F85B4 for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 10:19:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.557
X-Spam-Level: 
X-Spam-Status: No, score=-3.557 tagged_above=-999 required=5 tests=[AWL=0.041,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZpCLf3Ld-OX for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 10:19:08 -0800 (PST)
Received: from mail-ob0-f178.google.com (mail-ob0-f178.google.com [209.85.214.178]) by ietfa.amsl.com (Postfix) with ESMTP id C50F221F84A1 for <ietf@ietf.org>; Sat, 29 Dec 2012 10:19:07 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id eh20so10363418obb.23 for <ietf@ietf.org>; Sat, 29 Dec 2012 10:19:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jk9VSbHT8xvqW6WoyQiSpWzVFJty+JV/DeHJ5L2vUJA=; b=t+2KoHEN3EBd4eQkFKupM9pz1XRyuJqP9l7HtWCi58Y7cl5YVE1DkTwZFBIdv+oiFn 6KyNRVyVuSQ3HXK9CbRq4Xms3D2vp+F/DGIxvWxrJ23PsryxRAo5F0GhPxOk6t4FkRpn SJkZhK3EnX0t++LxgPLGLS7MlrvTzMBTErbA0Z6kzA8d6JoWmZDI5x9VrYUZfWtJCb+v KQM0jWVQ32QyaIpCxDWTk0x3BuEg8CS6wr4tDVr5Qy/W39x5cEAvE5mimpmLZnqGYx/H s/2I2jQ4dfzsgrBG594nHHVg+4KlKM+55i+RGk1ndn1hMypaRbTaL2BmpDYCu0vR3HRg p9XA==
MIME-Version: 1.0
Received: by 10.182.43.104 with SMTP id v8mr29985359obl.98.1356805147199; Sat, 29 Dec 2012 10:19:07 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Sat, 29 Dec 2012 10:19:07 -0800 (PST)
In-Reply-To: <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com>
Date: Sat, 29 Dec 2012 13:19:07 -0500
Message-ID: <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jorge Amodio <jmamodio@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04479633d4091304d201d064
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, 29 Dec 2012 18:19:09 -0000

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

On Sat, Dec 29, 2012 at 5:43 AM, Jorge Amodio <jmamodio@gmail.com> wrote:

>
> ITU was founded previously as the International Telegraph Union before AG
> Bell's phone was patented, no doubt the evolution of telecommunications and
> the Internet puts ITU with its current behavior in the path of becoming
> obsolete and extinct, but you can't discount many positive contributions
> particularly from the standards section.
>

The original purpose was to stop consumers from reducing their telegraph
bills by adopting codes.



> As the multistakeholder model and its associated processes, which is far
> from perfect, continues to evolve, ITU must be part of the evolution. The
> issue is that as an organization they must accommodate and realize that now
> they are "part of it" and not "it" anymore.
>

ITU must change if it is to survive. But it was merely a means to an end.
There is no reason that the ITU 'must' be kept in existence for its own
sake.

Tim Berners-Lee has on numerous W3C AC meetings reminded people about the
X-Windows consortium that did its job and then shut down.




> There is also a big confusion and still lack of a clear consensus on what
> "Internet governance" means or entitles, and many take it as "governing the
> Internet," hence governments want a piece of the action, and the constant
> and many times intended perception that the Internet is controlled by the
> USG and its development and evolution is US centric, which I believe at
> IETF we know since long time ago is not true. But many countries, and as
> you well say those where there was or still is a single telecom operator
> and controlled by government, see it that way.
>

Many parts of the world do not understand the difference between a standard
and a regulation or law. Which is why they see control points that don't
worry us. I do not see a problem with the US control of the IPv6 address
supply because I know that it is very very easy to defeat that control.
ICANN is a US corporation and the US government can obviously pass laws
that prevent ICANN/IANA from releasing address blocks that would reach
certain countries no matter what Crocker et. al. say to the contrary. But
absent a deployed BGP security infrastructure, that has no effect since the
rest of the planet is not going to observe a US embargo.

I can see that and most IETF-ers can see that. But the diplomats
representing Russia and China cannot apparently. Which is probably not
surprising given the type of education their upper classes (sorry children
of party bosses) receive.



> About the countries that signed, not many but most did it with
> reservations, and those that didn't sign probably represent 2/3 or more of
> the telecom market/industry. An interesting observation after spending
> countless hours following the meeting, some of the countries that were
> pushing the discussion for a reference to the universal declaration of
> human rights are the ones who don't care much about them, particularly in
> respect to women, and on the other hand others complaining about
> discrimination and restricted access to the Internet are the ones currently
> filtering on the big pipes and have the Internet as the first thing on
> their list to shutdown during internal turmoil.
>

Funny thing about treaties is that the governments that signed the UDHR
with great cynicism sixty years ago started to actually discuss it a
generation later. Now two generations on it is what the entire political
class has grown up with and it is accepted as something the country has
committed to.

A similar thing happened with the first ban on chemical weapons which
actually preceded the first large scale use in WWI. But in the aftermath
the victors realized that breaking the ban could be used as the basis for a
war crimes prosecution. Almost a century later the ban is pretty effective.
The UK is currently hearing a case in the high court arising from the use
of torture in Kenya. Pinochet was put on trial for his crimes in the end.



> The same forces that pushed at WCIT will keep doing the same thing on
> other international fora to insist with their Internet governance agenda,
> the ITRs will become effective in Jan 2015, two years, which on Internet
> time is an eternity, and it will be only valid if those countries that
> signed ratify the treaty. Meanwhile packets keep flowing, faster, bigger
> and with more destinations, not bad for a packet switching network that was
> not supposed to work. (During WCIT I was wondering, could you imagine doing
> the webcast via X.25? )
>

Two years may be longer than some of the unstable regimes have left. I
can't see Syria holding out that long and nor it appears can Russia. The
next dominoes in line are the ex-Soviet republics round the Caspian sea
where having the opposition boiled alive is still considered an acceptable
means of control.



> I agree that it is not clear what the outcome of WCIT12 was, but something
> that is clear is that ITU needs to evolve, or as Vint characterized them,
> the "dinosaurs" will become extinct.
>

I think that what we should be doing is to help the ITU become extinct by
eliminating the technical control points that would make ITU oversight of
Internet governance necessary.

This does not need to entail a great deal of technical changes but does
require that we accept that they do have a valid interest.


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

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

<br><br><div class=3D"gmail_quote">On Sat, Dec 29, 2012 at 5:43 AM, Jorge A=
modio <span dir=3D"ltr">&lt;<a href=3D"mailto:jmamodio@gmail.com" target=3D=
"_blank">jmamodio@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
<div dir=3D"ltr"><br><div>ITU was founded=A0previously=A0as the Internation=
al Telegraph Union before AG Bell&#39;s phone was patented, no doubt the ev=
olution of telecommunications and the Internet puts ITU with its current be=
havior in the path of becoming obsolete and extinct, but you can&#39;t disc=
ount many positive contributions particularly from the standards section.</=
div>
</div></blockquote><div><br></div><div>The original purpose was to stop con=
sumers from reducing their telegraph bills by adopting codes.=A0</div><div>=
<br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div>As the multistakeholder model and its associated proc=
esses, which is far from perfect, continues to evolve, ITU must be part of =
the evolution. The issue is that as an organization they must accommodate a=
nd realize that now they are &quot;part of it&quot; and not &quot;it&quot; =
anymore.</div>
</div></blockquote><div><br></div><div>ITU must change if it is to survive.=
 But it was merely a means to an end. There is no reason that the ITU &#39;=
must&#39; be kept in existence for its own sake.=A0</div><div><br></div><di=
v>
Tim Berners-Lee has on numerous W3C AC meetings reminded people about the X=
-Windows consortium that did its job and then shut down.</div><div><br></di=
v><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div>There is also a big confusion and still lack of a cle=
ar consensus on what &quot;Internet governance&quot; means or entitles, and=
 many take it as &quot;governing the Internet,&quot; hence governments want=
 a piece of the action, and the constant and many times intended perception=
 that the Internet is controlled by the USG and its development and evoluti=
on is US centric, which I believe at IETF we know since long time ago is no=
t true. But many countries, and as you well say those where there was or st=
ill is a single telecom operator and controlled by government, see it that =
way.</div>
</div></blockquote><div><br></div><div>Many parts of the world do not under=
stand the difference between a standard and a regulation or law. Which is w=
hy they see control points that don&#39;t worry us. I do not see a problem =
with the US control of the IPv6 address supply because I know that it is ve=
ry very easy to defeat that control. ICANN is a US corporation and the US g=
overnment can obviously pass laws that prevent ICANN/IANA from releasing ad=
dress blocks that would reach certain countries no matter what Crocker et. =
al. say to the contrary. But absent a deployed BGP security infrastructure,=
 that has no effect since the rest of the planet is not going to observe a =
US embargo.</div>
<div><br></div><div>I can see that and most IETF-ers can see that. But the =
diplomats representing Russia and China cannot apparently. Which is probabl=
y not surprising given the type of education their upper classes (sorry chi=
ldren of party bosses) receive.</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 dir=3D"ltr=
"><div>About the countries that signed, not many but most did it with reser=
vations, and those that didn&#39;t sign probably represent 2/3 or more of t=
he telecom market/industry. An interesting observation after spending count=
less hours following the meeting, some of the countries that were pushing t=
he discussion for a reference to the universal declaration of human rights =
are the ones who don&#39;t care much about them, particularly in respect to=
 women, and on the other hand others complaining about discrimination and r=
estricted access to the Internet are the ones currently filtering on the bi=
g pipes and have the Internet as the first thing on their list to shutdown =
during internal=A0turmoil.</div>
</div></blockquote><div><br></div><div>Funny thing about treaties is that t=
he governments that signed the UDHR with great cynicism sixty years ago sta=
rted to actually discuss it a generation later. Now two generations on it i=
s what the entire political class has grown up with and it is accepted as s=
omething the country has committed to.</div>
<div><br></div><div>A similar thing happened with the first ban on chemical=
 weapons which actually preceded the first large scale use in WWI. But in t=
he aftermath the victors realized that breaking the ban could be used as th=
e basis for a war crimes prosecution. Almost a century later the ban is pre=
tty effective. The UK is currently hearing a case in the high court arising=
 from the use of torture in Kenya. Pinochet was put on trial for his crimes=
 in the end.=A0</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 dir=3D"ltr=
"><div>The same forces that pushed at WCIT will keep doing the same thing o=
n other international fora to insist with their Internet governance agenda,=
 the ITRs will become effective in Jan 2015, two years, which on Internet t=
ime is an eternity, and it will be only valid if those countries that signe=
d ratify the treaty. Meanwhile packets keep flowing, faster, bigger and wit=
h more destinations, not bad for a packet switching network that was not su=
pposed to work. (During WCIT I was wondering, could you imagine doing the w=
ebcast via X.25? )</div>
</div></blockquote><div><br></div><div>Two years may be longer than some of=
 the unstable regimes have left. I can&#39;t see Syria holding out that lon=
g and nor it appears can Russia. The next dominoes in line are the ex-Sovie=
t republics round the Caspian sea where having the opposition boiled alive =
is still considered an acceptable means of control.</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 dir=3D"ltr=
"><div>I agree that it is not clear what the outcome of WCIT12 was, but som=
ething that is clear is that ITU needs to evolve, or as Vint=A0characterize=
d=A0them, the &quot;dinosaurs&quot; will become extinct.</div>
</div></blockquote><div><br></div><div>I think that what we should be doing=
 is to help the ITU become extinct by eliminating the technical control poi=
nts that would make ITU oversight of Internet governance necessary.</div>
<div><br></div><div>This does not need to entail a great deal of technical =
changes but does require that we accept that they do have a valid interest.=
</div><div>=A0</div></div><div><br></div>-- <br>Website: <a href=3D"http://=
hallambaker.com/">http://hallambaker.com/</a><br>


--f46d04479633d4091304d201d064--

From smb@cs.columbia.edu  Sat Dec 29 13:58:29 2012
Return-Path: <smb@cs.columbia.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 9C65421F871A for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 13:58:29 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9inoVX4h34fE for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 13:58:28 -0800 (PST)
Received: from paneer.cc.columbia.edu (paneer.cc.columbia.edu [128.59.29.4]) by ietfa.amsl.com (Postfix) with ESMTP id C694F21F8701 for <ietf@ietf.org>; Sat, 29 Dec 2012 13:58:28 -0800 (PST)
Received: from v146.vpn.iad.rg.net (v146.vpn.iad.rg.net [198.180.150.146]) (user=smb2132 mech=PLAIN bits=0) by paneer.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id qBTLwMMb014389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 29 Dec 2012 16:58:23 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: travel guide for the next IETF...
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <50DF09C7.1060009@dcrocker.net>
Date: Sat, 29 Dec 2012 16:58:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3659710A-502D-44BE-AF1C-2F8D392B6345@cs.columbia.edu>
References: <50DF09C7.1060009@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.4
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, 29 Dec 2012 21:58:29 -0000

On Dec 29, 2012, at 10:18 AM, Dave Crocker <dhc@dcrocker.net> wrote:

>=20
>     Going Beyond Disney in Orlando
>=20
>     "Quick, name five reasons to go to Orlando. Here are mine: Puerto =
Rican delicacies, alternative cinema, craft beer, African-American =
history and psychic readings..."
>=20
> =
http://frugaltraveler.blogs.nytimes.com/2012/12/27/going-beyond-disney-in-=
orlando/?nl=3Dtravel&emc=3Dedit_tl_20121229


During IETF '43, the Mars Climate Orbiter was launched; I wasn't the =
only one who headed east from Orlando on Friday...  Ironically, it was =
lost due to what could be called an error in a protocol implementation: =
https://en.wikipedia.org/wiki/Mars_Climate_Orbiter

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






From paf@frobbit.se  Sat Dec 29 14:46:19 2012
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 ED57621F87D5 for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 14:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 301MEMZepaLR for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 14:46:18 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 1F87621F87D0 for <ietf@ietf.org>; Sat, 29 Dec 2012 14:46:18 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::c537:62a7:fb82:54b9] (unknown [IPv6:2a02:80:3ffc:0:c537:62a7:fb82:54b9]) by mail.frobbit.se (Postfix) with ESMTPSA id BE117216CA; Sat, 29 Dec 2012 23:46:15 +0100 (CET)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5D7253FC-9ABC-4837-A9AF-C8ABDAFDC8C4"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: WCIT outcome?
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
Date: Sat, 29 Dec 2012 23:46:15 +0100
Message-Id: <C7DE076D-3B90-45FF-AC0B-7A6757509F33@frobbit.se>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1499)
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, 29 Dec 2012 22:46:19 -0000

--Apple-Mail=_5D7253FC-9ABC-4837-A9AF-C8ABDAFDC8C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 29 dec 2012, at 19:19, Phillip Hallam-Baker <hallam@gmail.com> wrote:

> ITU must change if it is to survive. But it was merely a means to an =
end. There is no reason that the ITU 'must' be kept in existence for its =
own sake.=20
>=20
> Tim Berners-Lee has on numerous W3C AC meetings reminded people about =
the X-Windows consortium that did its job and then shut down.

There are, IMHO, two major differences between the "old world" and the =
"new world":

In the new world, there are many different SDOs that are, in =
combination, bringing whatever "standards" are needed to the table. In =
the old world, there was only one.

In the new world, "governance" is no longer "by decree", "by =
legislation" or similar. In the new world we use the word =
"collaboration", and that is done via policy development processes that =
are multi stakeholder and bottom up. Like in the RIRs (for IP addresses =
etc), like in ICANN (for domain names) or locally for the various =
(successful) ccTLDs that are out there. And of course in the various =
industry consortia that bring so many valuable specifications to the =
table.

This is, I claim, ratified in the UN context in the outcome we call "The =
Tunis Agenda" and it has come back over and over again. In various =
formats, using slightly different wordings, but always the same theme.

Sometimes, I do though think also IETF participants should think a bit =
more about what the basic principles are for them. Why they fight for =
their views. What could make them give up. What the values are that they =
think are essential. That they are ready to really fight for.

   Patrik F=E4ltstr=F6m
   Chair of ICANN SSAC
   Former member of IESG, IAB etc and delegate of the Swedish Delegation =
at WCIT-12


--Apple-Mail=_5D7253FC-9ABC-4837-A9AF-C8ABDAFDC8C4
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 29 dec 2012, at 19:19, Phillip Hallam-Baker &lt;<a =
href=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"font-family: 'Lucida Sans Typewriter'; =
font-size: medium; 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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">ITU =
must change if it is to survive. But it was merely a means to an end. =
There is no reason that the ITU 'must' be kept in existence for its own =
sake.&nbsp;</div><div style=3D"font-family: 'Lucida Sans Typewriter'; =
font-size: medium; 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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; =
"><br></div><div style=3D"font-family: 'Lucida Sans Typewriter'; =
font-size: medium; 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-text-size-adjust: auto; -webkit-text-stroke-width: 0px; ">Tim =
Berners-Lee has on numerous W3C AC meetings reminded people about the =
X-Windows consortium that did its job and then shut =
down.</div></blockquote><br></div><div>There are, IMHO, two major =
differences between the "old world" and the "new =
world":</div><div><br></div><div>In the new world, there are many =
different SDOs that are, in combination, bringing whatever "standards" =
are needed to the table. In the old world, there was only =
one.</div><div><br></div><div>In the new world, "governance" is no =
longer "by decree", "by legislation" or similar. In the new world we use =
the word "collaboration", and that is done via policy development =
processes that are multi stakeholder and bottom up. Like in the RIRs =
(for IP addresses etc), like in ICANN (for domain names) or locally for =
the various (successful) ccTLDs that are out there. And of course in the =
various industry consortia that bring so many valuable specifications to =
the table.</div><div><br></div><div>This is, I claim, ratified in the UN =
context in the outcome we call "The Tunis Agenda" and it has come back =
over and over again. In various formats, using slightly different =
wordings, but always the same theme.</div><div><br></div><div>Sometimes, =
I do though think also IETF participants should think a bit more about =
what the basic principles are for them. Why they fight for their views. =
What could make them give up. What the values are that they think are =
essential. That they are ready to really fight =
for.</div><div><br></div><div>&nbsp; &nbsp;Patrik =
F=E4ltstr=F6m</div><div>&nbsp; &nbsp;Chair of ICANN =
SSAC</div><div>&nbsp; &nbsp;Former member of IESG, IAB etc and delegate =
of the Swedish Delegation at WCIT-12</div><div><br></div></body></html>=

--Apple-Mail=_5D7253FC-9ABC-4837-A9AF-C8ABDAFDC8C4--

From sm@resistor.net  Sat Dec 29 22:26:02 2012
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 DF63121F882B for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 22:26:02 -0800 (PST)
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.171, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8KTUsgC-8Y3l for <ietf@ietfa.amsl.com>; Sat, 29 Dec 2012 22:26:01 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C17EA21F87DE for <ietf@ietf.org>; Sat, 29 Dec 2012 22:26:00 -0800 (PST)
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 qBU6PhFk011109; Sat, 29 Dec 2012 22:25:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1356848749; bh=K9TDX2l3enNErM9ztHPwCEY++g5V8Ofz/aM+i6tokms=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EySLwqMF6iu71lKOl7LCw3tFOeAZJYAOgiOJoijBJgzBTasqGC0bGoALMy8wvDXAo 21rjgFGgyULpWpKSbQA1qqw2NrAuAYgfq8NNaxXfKGLb2vEPcd1FdsO5UgEiNMWtVj 2negnFVLlUKxu/DWd9suP0/tz09caMtIYsx4FOvU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1356848749; i=@resistor.net; bh=K9TDX2l3enNErM9ztHPwCEY++g5V8Ofz/aM+i6tokms=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CIDYMC19eiEjkTpmhGD21zCD5JnNWR3DlReZPUCo+kuXPqOdOJeOD6yOKx53jhq8z 6e+gnd3XGCBeqJ2OYsuyt1E0YWAF+hcjbdQVhcrqhXb4EpgBlf9oucUvO8Z6pvt+8i JNuLaB2Fa5MmG39erRABH6PEM77BAMbhMPh+qvZA=
Message-Id: <6.2.5.6.2.20121229192941.0aae33e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 29 Dec 2012 22:25:01 -0800
To: Phillip Hallam-Baker <hallam@gmail.com>, Patrik  =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: SM <sm@resistor.net>
Subject: Re: WCIT outcome?
In-Reply-To: <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.g mail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
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, 30 Dec 2012 06:26:03 -0000

At 10:19 29-12-2012, Phillip Hallam-Baker wrote:
>ICANN is a US corporation and the US government=20
>can obviously pass laws that prevent ICANN/IANA=20
>from releasing address blocks that would reach=20
>certain countries no matter what Crocker et. al.=20
>say to the contrary. But absent a deployed BGP security

:-)

At 14:46 29-12-2012, Patrik F=E4ltstr=F6m wrote:
>In the new world, "governance" is no longer "by=20
>decree", "by legislation" or similar. In the new=20
>world we use the word "collaboration", and that=20
>is done via policy development processes that=20
>are multi stakeholder and bottom up. Like in the RIRs (for IP addresses

What people say and what they actually do or mean=20
is often a very different matter.  An individual=20
may have principles (or beliefs).  A stakeholder=20
has interests.  There was an individual who=20
mentioned on an IETF mailing list that he/she=20
disagreed with his/her company's stance.  It's=20
unlikely that a stakeholder would say that.

The collaboration is less about process and more=20
about culture.  In some parts of the new world=20
"governance" is still by legislation, etc.  That=20
could be attributed to cultural or other=20
factors.  The WCIT outcome might be highlighting the fracture.

Regards,
-sm =20


From hallam@gmail.com  Sun Dec 30 05:42:20 2012
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 0A38D21F87FF for <ietf@ietfa.amsl.com>; Sun, 30 Dec 2012 05:42:20 -0800 (PST)
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.027, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock10=0.13]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tltTdaHzkaI for <ietf@ietfa.amsl.com>; Sun, 30 Dec 2012 05:42:18 -0800 (PST)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id AD20A21F87FD for <ietf@ietf.org>; Sun, 30 Dec 2012 05:42:18 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id j1so11149634oag.15 for <ietf@ietf.org>; Sun, 30 Dec 2012 05:42:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HjXVamsnqTF0gYkzZf7FMEnM0BspKJTJzE5eMDWo5nU=; b=Sn+0ks0zEFPpSAWHvIx3tgl7VUaD7/0tgvB9gHha7DT1r6m423yshinp19MM3OAJzu sjVA2+0N4OXD0r2YPzkMtmIbTflaeX8pobAPYzOZ2EVWOO9fmU+uC/067kLexRvKDuWG DTFu+aqzBkGIly5h7Z+mt4LG+dals4t6YcsERcj25KtqhzKtLH8Mt/SxoXXvLX3t663C COxQnVWJCJNz8ftOmHnZak02ImpvdwQEdcpojcqDN7UJyOi0CHR7y9PF3Nlpro2AVHe+ xIzgB5yFQaOXtGuy/dsjnKCX28sFXIe08BSYNxGIAxfSgO2LGTaLhMLHfYlEr4ITp+TE zDCA==
MIME-Version: 1.0
Received: by 10.60.29.193 with SMTP id m1mr19758586oeh.36.1356874937961; Sun, 30 Dec 2012 05:42:17 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Sun, 30 Dec 2012 05:42:17 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20121229192941.0aae33e8@resistor.net>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net>
Date: Sun, 30 Dec 2012 08:42:17 -0500
Message-ID: <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=e89a8ff242a1ae8d5804d2121044
Cc: IETF Discussion Mailing List <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: Sun, 30 Dec 2012 13:42:20 -0000

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

On Sun, Dec 30, 2012 at 1:25 AM, SM <sm@resistor.net> wrote:

> At 10:19 29-12-2012, Phillip Hallam-Baker wrote:
>
>> ICANN is a US corporation and the US government can obviously pass laws
>> that prevent ICANN/IANA from releasing address blocks that would reach
>> certain countries no matter what Crocker et. al. say to the contrary. Bu=
t
>> absent a deployed BGP security
>>
>
> :-)
>
>
> At 14:46 29-12-2012, Patrik F=E4ltstr=F6m wrote:
>
>> In the new world, "governance" is no longer "by decree", "by legislation=
"
>> or similar. In the new world we use the word "collaboration", and that i=
s
>> done via policy development processes that are multi stakeholder and bot=
tom
>> up. Like in the RIRs (for IP addresses
>>
>
> What people say and what they actually do or mean is often a very
> different matter.  An individual may have principles (or beliefs).  A
> stakeholder has interests.  There was an individual who mentioned on an
> IETF mailing list that he/she disagreed with his/her company's stance.
>  It's unlikely that a stakeholder would say that.
>

The reason that rule is useful is that just as it is ridiculous for the US
representative to the ITU to attempt to convey the positions of Comcast and
Google, it is no more practical for one person to represent the position of
Cisco or Microsoft.

Where the problem comes in is when you have a proposal that requires the
active support and participation of stakeholders like VeriSign. When I told
the IETF that DNSSEC would be deployed in dot.com if and only if the opt-in
proposal was accepted, I was stating the official position of a stakeholder
whose participation was essential if DNSSEC was going to be deployed.

It was a really minor change but the reason it was blocked was one
individual had the crazy idea that blocking deployment of DNSSEC would
cause VeriSign to lose dotcom. He was not the only person with that idea
but he was the only person in a position to wreck all progress in the IETF
if he didn't get his way.

For projects like IPv6 the standards development process needs to be better
at identifying the necessary stakeholders and ensuring that enough
essential requirements of enough stakeholders are met. Otherwise we end up
with yet another Proposed Standard RFC that everyone ignores.

The main fault of IETF culture is the idea that the Internet is waiting to
receive everything that we toss over the wall. That is not how I view the
utility of the process. If I want to have fun designing something I invite
at most five people to the brainstorming session then one person writes it
up. The only reason to have more then five people is to seek buy-in from
other stakeholders.

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

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

<br><br><div class=3D"gmail_quote">On Sun, Dec 30, 2012 at 1:25 AM, SM <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@r=
esistor.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">At 10:19 29-12-2012, Phillip 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">
ICANN is a US corporation and the US government can obviously pass laws tha=
t prevent ICANN/IANA from releasing address blocks that would reach certain=
 countries no matter what Crocker et. al. say to the contrary. But absent a=
 deployed BGP security<br>

</blockquote>
<br></div>
:-)<div class=3D"im"><br>
<br>
At 14:46 29-12-2012, Patrik F=E4ltstr=F6m wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In the new world, &quot;governance&quot; is no longer &quot;by decree&quot;=
, &quot;by legislation&quot; or similar. In the new world we use the word &=
quot;collaboration&quot;, and that is done via policy development processes=
 that are multi stakeholder and bottom up. Like in the RIRs (for IP address=
es<br>

</blockquote>
<br></div>
What people say and what they actually do or mean is often a very different=
 matter. =A0An individual may have principles (or beliefs). =A0A stakeholde=
r has interests. =A0There was an individual who mentioned on an IETF mailin=
g list that he/she disagreed with his/her company&#39;s stance. =A0It&#39;s=
 unlikely that a stakeholder would say that.<br>
</blockquote><div><br></div><div>The reason that rule is useful is that jus=
t as it is ridiculous for the US representative to the ITU to attempt to co=
nvey the positions of Comcast and Google, it is no more practical for one p=
erson to represent the position of Cisco or Microsoft.</div>
<div><br></div><div>Where the problem comes in is when you have a proposal =
that requires the active support and participation of stakeholders like Ver=
iSign. When I told the IETF that DNSSEC would be deployed in <a href=3D"htt=
p://dot.com">dot.com</a> if and only if the opt-in proposal was accepted, I=
 was stating the official position of a stakeholder whose participation was=
 essential if DNSSEC was going to be deployed.=A0</div>
<div><br></div><div>It was a really minor change but the reason it was bloc=
ked was one individual had the crazy idea that blocking deployment of DNSSE=
C would cause VeriSign to lose dotcom. He was not the only person with that=
 idea but he was the only person in a position to wreck all progress in the=
 IETF if he didn&#39;t get his way.</div>
<div><br></div><div>For projects like IPv6 the standards development proces=
s needs to be better at identifying the necessary stakeholders and ensuring=
 that enough essential requirements of enough stakeholders are met. Otherwi=
se we end up with yet another Proposed Standard RFC that everyone ignores.<=
/div>
<div><br></div><div>The main fault of IETF culture is the idea that the Int=
ernet is waiting to receive everything that we toss over the wall. That is =
not how I view the utility of the process. If I want to have fun designing =
something I invite at most five people to the brainstorming session then on=
e person writes it up. The only reason to have more then five people is to =
seek buy-in from other stakeholders.</div>
</div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>

--e89a8ff242a1ae8d5804d2121044--

From mohta@necom830.hpcl.titech.ac.jp  Mon Dec 31 03:50:14 2012
Return-Path: <mohta@necom830.hpcl.titech.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 4A5C521F859D for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 03:50:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.655
X-Spam-Level: 
X-Spam-Status: No, score=0.655 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JynWTrMc-xCh for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 03:50:13 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 53A6D21F8539 for <ietf@ietf.org>; Mon, 31 Dec 2012 03:50:11 -0800 (PST)
Received: (qmail 25211 invoked from network); 31 Dec 2012 11:49:52 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 31 Dec 2012 11:49:52 -0000
Message-ID: <50E17B9B.5030404@necom830.hpcl.titech.ac.jp>
Date: Mon, 31 Dec 2012 20:48:43 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: WCIT outcome?
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net>
In-Reply-To: <6.2.5.6.2.20121229192941.0aae33e8@resistor.net>
Content-Type: text/plain; charset=ISO-2022-JP
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, 31 Dec 2012 11:50:14 -0000

SM wrote:

> What people say and what they actually do or mean is often a very 
> different matter.  An individual may have principles (or beliefs).  A 
> stakeholder has interests.  There was an individual who mentioned on an 
> IETF mailing list that he/she disagreed with his/her company's stance.  
> It's unlikely that a stakeholder would say that.

That's how the global routing table has bloated so much because
of requests from ISPs as stakeholders even though it is harmful
to not only end users but also ISPs, which is "fallacy of
composition".

ITU did it better for phone numbers.

						Masataka Ohta

From jeanjour@comcast.net  Mon Dec 31 06:51:14 2012
Return-Path: <jeanjour@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 6947721F853E for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 06:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.306
X-Spam-Level: 
X-Spam-Status: No, score=-100.306 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  HTML_MESSAGE=0.001, RDNS_NONE=0.1, SARE_RMML_Stock10=0.13, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6+fyMh5M8Oqk for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 06:51:13 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 292CA21F851C for <ietf@ietf.org>; Mon, 31 Dec 2012 06:51:12 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta09.westchester.pa.mail.comcast.net with comcast id iCgV1k0021c6gX859ErCgm; Mon, 31 Dec 2012 14:51:12 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta23.westchester.pa.mail.comcast.net with comcast id iErA1k00814WE023jErAmf; Mon, 31 Dec 2012 14:51:12 +0000
Mime-Version: 1.0
Message-Id: <a06240800cd074efd45b8@[10.0.1.3]>
In-Reply-To: <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com>
Date: Mon, 31 Dec 2012 09:51:03 -0500
To: Phillip Hallam-Baker <hallam@gmail.com>, SM <sm@resistor.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: multipart/alternative; boundary="============_-855157025==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1356965472; bh=DE+Gw7JTZ0MvwbKY6DhgID1REY9o2g9+heflOKbd3q0=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=YodEOzdTTCIkJcXIRGJbaZ0d98iYlXVFEdQsKK5oXuoVgIcpZ2QiA1JL7xRQSxpJ9 LGJU94Z9Mrq94NzEX2tgGt4E+2oJcTPc/4VK5tFqD1XbLEYUO+lKrJFeh4HY3vLnb0 99R0OHRmrLTHO+gwSZ0kYWrXNmCl44gzAGh0mwrULL6EZiafgFPW3yfW5jVoHK5GET W/U206WeHVeTeb0Z7AKIpc4gk+nikey9sPcrzqBVgsC4aCo/0BHYPgQHaSdsmHEuS0 0U57oeKXNeG+Nur1Rv1QkY6j2jFQ0aHqBNdojN3EaYy++EFlzR3AtXwGvb4cwMfxHT 6wL/Ej2UV1PXw==
Cc: IETF Discussion Mailing List <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: Mon, 31 Dec 2012 14:51:14 -0000

--============_-855157025==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Phillip,

>
>The reason that rule is useful is that just as it is ridiculous for 
>the US representative to the ITU to attempt to convey the positions 
>of Comcast and Google, it is no more practical for one person to 
>represent the position of Cisco or Microsoft.

Then I take it from this comment that you believe that all forms of 
representative government (and reaching agreements) are ridiculous?

Surely you don't believe that pure democracy will work?  That myth 
had been dispelled 250 years ago.

The process of a representative form for creating agreements seems to 
be (as flawed as it is) about the best we have come up with.

Wrt its application in standards outside the ITU it works the same 
way.  When a voluntary standards organization organizes by country, 
it is to give voice to the small companies as well as the Ciscos and 
Microsofts.  The big guys can send 10s of people (which represents a 
different problem) to meetings all over the world.  The little 
companies can't afford that but they have an interest.  Providing the 
means for them to agree on what their interest is and to make it 
heard is equally important.

It sounds like you are arguing for the hegemony of the robber barons 
moved to the 21stC.

>
>Where the problem comes in is when you have a proposal that requires 
>the active support and participation of stakeholders like VeriSign. 
>When I told the IETF that DNSSEC would be deployed in 
><http://dot.com>dot.com if and only if the opt-in proposal was 
>accepted, I was stating the official position of a stakeholder whose 
>participation was essential if DNSSEC was going to be deployed.
>
>It was a really minor change but the reason it was blocked was one 
>individual had the crazy idea that blocking deployment of DNSSEC 
>would cause VeriSign to lose dotcom. He was not the only person with 
>that idea but he was the only person in a position to wreck all 
>progress in the IETF if he didn't get his way.
>
>For projects like IPv6 the standards development process needs to be 
>better at identifying the necessary stakeholders and ensuring that 
>enough essential requirements of enough stakeholders are met. 
>Otherwise we end up with yet another Proposed Standard RFC that 
>everyone ignores.

I would disagree slightly.  It is not task of the SDO to identify the 
necessary stakeholders but to ensure all of the stakeholder are 
represented at all levels.  The problems you describe above result 
from breaking that rule.

>
>The main fault of IETF culture is the idea that the Internet is 
>waiting to receive everything that we toss over the wall. That is 
>not how I view the utility of the process. If I want to have fun 
>designing something I invite at most five people to the 
>brainstorming session then one person writes it up. The only reason 
>to have more then five people is to seek buy-in from other 
>stakeholders.

Wrt some of your previous comments, I would agree.  When phone 
companies were owned by governments (remember this was often both the 
provider and manufacturer parts of the business) , there might have 
been a reason for ITU to be a treaty organization.  I can see that 
for wireless government involvement is still necessary.  However, 
given that providers are now private (often international) businesses 
it is hard to see wrt standards setting how the topics covered by ITU 
is any different than any other voluntary standards organization.

Over the 30+ years I have been involved in standards it is pretty 
clear that the bottom-up nature of standards creates standards bodies 
among like-minded groups of people.  This seems to be the natural 
occurrence.  I see no problem with this.  There seems to be a 
like-minded group of people who gravitate toward the kinds of 
problems the ITU has traditionally dealt with. Fine.  The market will 
decide whether or not it wants to use them as it does with all 
standards.

The question is what, if anything, is there left relating to wireline 
communication that requires agreement among *governments*?  I can't 
think of much.

One other note:  We are very sloppy in our use of the term 
"Internet." And the ITU hierarchy and their allies have been 
skillfully using this.  We are not distinguishing clearly between the 
internet itself and the *users* (or is it uses?) of the Internet.  It 
appears that most of what they want to regulate or constrain is the 
"uses."  This is equivalent to saying that they want to regulate what 
is said over the phone.  Clearly outside their purview.  But *we* act 
like it isn't.  By not clearly distinguishing between the two in the 
discussions, we have already given up considerable ground.

Take care,
John Day

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

--============_-855157025==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: WCIT outcome?</title></head><body>
<div>Phillip,</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The reason that rule is useful is that
just as it is ridiculous for the US representative to the ITU to
attempt to convey the positions of Comcast and Google, it is no more
practical for one person to represent the position of Cisco or
Microsoft.</blockquote>
<div><br></div>
<div>Then I take it from this comment that you believe that all forms
of representative government (and reaching agreements) are
ridiculous?</div>
<div><br></div>
<div>Surely you don't believe that pure democracy will work?&nbsp;
That myth had been dispelled 250 years ago.</div>
<div><br></div>
<div>The process of a representative form for creating agreements
seems to be (as flawed as it is) about the best we have come up
with.</div>
<div><br></div>
<div>Wrt its application in standards outside the ITU it works the
same way.&nbsp; When a voluntary standards organization organizes by
country, it is to give voice to the small companies as well as the
Ciscos and Microsofts.&nbsp; The big guys can send 10s of people
(which represents a different problem) to meetings all over the
world.&nbsp; The little companies can't afford that but they have an
interest.&nbsp; Providing the means for them to agree on what their
interest is and to make it heard is equally important.</div>
<div><br></div>
<div>It sounds like you are arguing for the hegemony of the robber
barons moved to the 21stC.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Where the problem comes in is when you
have a proposal that requires the active support and participation of
stakeholders like VeriSign. When I told the IETF that DNSSEC would be
deployed in <a href="http://dot.com">dot.com</a> if and only if the
opt-in proposal was accepted, I was stating the official position of a
stakeholder whose participation was essential if DNSSEC was going to
be deployed.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>It was a really minor change but the
reason it was blocked was one individual had the crazy idea that
blocking deployment of DNSSEC would cause VeriSign to lose dotcom. He
was not the only person with that idea but he was the only person in a
position to wreck all progress in the IETF if he didn't get his
way.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>For projects like IPv6 the standards
development process needs to be better at identifying the necessary
stakeholders and ensuring that enough essential requirements of enough
stakeholders are met. Otherwise we end up with yet another Proposed
Standard RFC that everyone ignores.</blockquote>
<div><br></div>
<div>I would disagree slightly.&nbsp; It is not task of the SDO to
identify the necessary stakeholders but to ensure all of the
stakeholder are represented at all levels.&nbsp; The problems you
describe above result from breaking that rule.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>The main fault of IETF culture is the
idea that the Internet is waiting to receive everything that we toss
over the wall. That is not how I view the utility of the process. If I
want to have fun designing something I invite at most five people to
the brainstorming session then one person writes it up. The only
reason to have more then five people is to seek buy-in from other
stakeholders.</blockquote>
<div><br></div>
<div>Wrt some of your previous comments, I would agree.&nbsp; When
phone companies were owned by governments (remember this was often
both the provider and manufacturer parts of the business) , there
might have been a reason for ITU to be a treaty organization.&nbsp; I
can see that for wireless government involvement is still necessary.&nbsp;
However, given that providers are now private (often international)
businesses it is hard to see wrt standards setting how the topics
covered by ITU is any different than any other voluntary standards
organization.</div>
<div><br></div>
<div>Over the 30+ years I have been involved in standards it is pretty
clear that the bottom-up nature of standards creates standards bodies
among like-minded groups of people.&nbsp; This seems to be the natural
occurrence.&nbsp; I see no problem with this.&nbsp; There seems to be
a like-minded group of people who gravitate toward the kinds of
problems the ITU has traditionally dealt with. Fine.&nbsp; The market
will decide whether or not it wants to use them as it does with all
standards.</div>
<div><br></div>
<div>The question is what, if anything, is there left relating to
wireline communication that requires agreement among *governments*?&nbsp;
I can't think of much.</div>
<div><br></div>
<div>One other note:&nbsp; We are very sloppy in our use of the term
&quot;Internet.&quot; And the ITU hierarchy and their allies have been
skillfully using this.&nbsp; We are not distinguishing clearly between
the internet itself and the *users* (or is it uses?) of the Internet.&nbsp;
It appears that most of what they want to regulate or constrain is the
&quot;uses.&quot;&nbsp; This is equivalent to saying that they want to
regulate what is said over the phone.&nbsp; Clearly outside their
purview.&nbsp; But *we* act like it isn't.&nbsp; By not clearly
distinguishing between the two in the discussions, we have already
given up considerable ground.</div>
<div><br></div>
<div>Take care,</div>
<div>John Day</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>--<br>
Website: <a
href="http://hallambaker.com/">http://hallambaker.com/</a></blockquote>
<div><br></div>
</body>
</html>
--============_-855157025==_ma============--

From jgunn6@csc.com  Mon Dec 31 09:01:03 2012
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 065F821F8738; Mon, 31 Dec 2012 09:01:03 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6r8gDHxaacDS; Mon, 31 Dec 2012 09:01:02 -0800 (PST)
Received: from mail170.messagelabs.com (mail170.messagelabs.com [216.82.253.227]) by ietfa.amsl.com (Postfix) with ESMTP id 3521B21F86AB; Mon, 31 Dec 2012 09:01:02 -0800 (PST)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-9.tower-170.messagelabs.com!1356973259!23066691!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.6.1.8; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14698 invoked from network); 31 Dec 2012 17:01:00 -0000
Received: from amer-mta102.csc.com (HELO amer-mta102.csc.com) (20.137.2.88) by server-9.tower-170.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 31 Dec 2012 17:01:00 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta102.csc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id qBVH0wXb017876; Mon, 31 Dec 2012 12:00:59 -0500
In-Reply-To: <50DF09C7.1060009@dcrocker.net>
References: <50DF09C7.1060009@dcrocker.net>
To: dcrocker@bbiw.net
MIME-Version: 1.0
Subject: Re: travel guide for the next IETF...
X-KeepSent: 3EA1F553:45F5C1FF-85257AE5:005C4612; 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: <OF3EA1F553.45F5C1FF-ON85257AE5.005C4612-85257AE5.005D788C@csc.com>
Date: Mon, 31 Dec 2012 12:00:56 -0500
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 12/31/2012 11:56:08 AM, Serialize complete at 12/31/2012 11:56:08 AM
Content-Type: multipart/alternative; boundary="=_alternative 005D784A85257AE5_="
Cc: ietf-bounces@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: Mon, 31 Dec 2012 17:01:03 -0000

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

Daytona Bike Week is March  8 - 17.

Janet

ietf-bounces@ietf.org wrote on 12/29/2012 10:18:31 AM:

> From: Dave Crocker <dhc@dcrocker.net>
> To: IETF Discussion <ietf@ietf.org>
> Date: 12/29/2012 10:18 AM
> Subject: travel guide for the next IETF...
> Sent by: ietf-bounces@ietf.org
> 
> 
>       Going Beyond Disney in Orlando
> 
>       "Quick, name five reasons to go to Orlando. Here are mine: Puerto 
> Rican delicacies, alternative cinema, craft beer, African-American 
> history and psychic readings..."
> 
> 
> http://frugaltraveler.blogs.nytimes.com/2012/12/27/going-beyond-
> disney-in-orlando/?nl=travel&emc=edit_tl_20121229
> 
> d/
> -- 
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net

--=_alternative 005D784A85257AE5_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
Daytona Bike Week is March &nbsp;8 - 17.</font>
<br>
<br><font size=2 face="sans-serif">Janet</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 12/29/2012 10:18:31
AM:<br>
<br>
&gt; From: Dave Crocker &lt;dhc@dcrocker.net&gt;</font></tt>
<br><tt><font size=2>&gt; To: IETF Discussion &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 12/29/2012 10:18 AM</font></tt>
<br><tt><font size=2>&gt; Subject: travel guide for the next IETF...</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; &nbsp; &nbsp; &nbsp; Going Beyond Disney in Orlando<br>
&gt; <br>
&gt; &nbsp; &nbsp; &nbsp; &quot;Quick, name five reasons to go to Orlando.
Here are mine: Puerto <br>
&gt; Rican delicacies, alternative cinema, craft beer, African-American
<br>
&gt; history and psychic readings...&quot;<br>
&gt; <br>
&gt; &nbsp;<br>
&gt; </font></tt><a href="http://frugaltraveler.blogs.nytimes.com/2012/12/27/going-beyond-"><tt><font size=2>http://frugaltraveler.blogs.nytimes.com/2012/12/27/going-beyond-</font></tt></a><tt><font size=2><br>
&gt; disney-in-orlando/?nl=travel&amp;emc=edit_tl_20121229<br>
&gt; <br>
&gt; d/<br>
&gt; -- <br>
&gt; &nbsp; Dave Crocker<br>
&gt; &nbsp; Brandenburg InternetWorking<br>
&gt; &nbsp; bbiw.net<br>
</font></tt>
--=_alternative 005D784A85257AE5_=--

From chair@ietf.org  Mon Dec 31 09:21:45 2012
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 B63D621F87ED; Mon, 31 Dec 2012 09:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.848
X-Spam-Level: 
X-Spam-Status: No, score=-102.848 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwourLVNG6+6; Mon, 31 Dec 2012 09:21:45 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 5706721F85E6; Mon, 31 Dec 2012 09:21:45 -0800 (PST)
Received: from localhost (c8a.amsl.com [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 516CF124557; Mon, 31 Dec 2012 09:21:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QE8HfzGDkRe8; Mon, 31 Dec 2012 09:21:45 -0800 (PST)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id D141E12453F; Mon, 31 Dec 2012 09:21:44 -0800 (PST)
Subject: 30th Anniversary of Transition to TCP/IP
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-34-710181580
From: IETF Chair <chair@ietf.org>
In-Reply-To: <9DA543CE-5AE0-41B9-B0B9-49C6B208CCEE@vigilsec.com>
Date: Mon, 31 Dec 2012 12:21:43 -0500
Message-Id: <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
References: <9DA543CE-5AE0-41B9-B0B9-49C6B208CCEE@vigilsec.com>
To: IETF Announce <ietf-announce@ietf.org>
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, 31 Dec 2012 17:21:45 -0000

--Apple-Mail-34-710181580
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Happy New Year.  It is already 2013 in some part of the world.

The ARPANET transitioned to TCP/IP on 1 January 1983.  That was 30 years =
ago, and it was a huge milestone in the journey toward the Internet as =
we know it.

You can see the transition plan.  Like so many other historic networking =
documents, it is an RFC.  See http://www.rfc-editor.org/rfc/rfc801.txt=20=


Happy New Year,=20
  Russ


--Apple-Mail-34-710181580
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 =
style=3D"font-family: arial, helvetica, sans-serif; font-size: =
10pt"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"">Happy New =
Year. &nbsp;It is already 2013 in some part of the world.</div><div =
class=3D"gmail_default" style=3D""><br></div><div class=3D"gmail_default" =
style=3D"">The ARPANET transitioned to TCP/IP on 1 January 1983. =
&nbsp;That was 30 years ago, and it was a huge milestone in the journey =
toward the Internet as we know it.</div><div class=3D"gmail_default" =
style=3D""><br></div><div class=3D"gmail_default" style=3D"">You can see =
the transition plan. &nbsp;Like so many other historic networking =
documents, it is an RFC. &nbsp;See <a =
href=3D"http://www.rfc-editor.org/rfc/rfc801.txt">http://www.rfc-editor.or=
g/rfc/rfc801.txt</a>&nbsp;</div><div class=3D"gmail_default" =
style=3D""><br></div><div class=3D"gmail_default" style=3D"">Happy New =
Year,&nbsp;</div><div class=3D"gmail_default" style=3D"">&nbsp; =
Russ</div><div class=3D"gmail_default" style=3D""><br></div></div></div>
</body></html>=

--Apple-Mail-34-710181580--

From hallam@gmail.com  Mon Dec 31 10:05:23 2012
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 851F621F8792 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 10:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uFlUPa9QSdpG for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 10:05:22 -0800 (PST)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3AEE321F8781 for <ietf@ietf.org>; Mon, 31 Dec 2012 10:05:22 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id dn14so11685475obc.16 for <ietf@ietf.org>; Mon, 31 Dec 2012 10:05:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7Ql2fqnEEXcKFKkLCjQdd7n+0LU9dCZUiAIY9Y/vWGs=; b=HrI2lmKSN/Kgt6pVIBvpiRN6g/xaX38FODsbWYd59ne7+tyw5Bj8uj1IwRitg7KQ5l Sgk8OJVm7CMlGr+/sNYZjWXOJsDT1YkmmM+bcvxJ50sxSxOoNaKrPMOtoZVJF/xh2K1/ ELzuhQcNsIkeNd0c1uZcSKKboAIOwRCyrjaUuwIeKGam9Kqo8Yn29xpELXH3x8ATK0u/ 1+VsQG9ItU5TlLn1676ztACr4rdziYATDxKF66t4o+Jc6FBCZvPuA3vAWryccUUNuMg0 gOxgtpB1npJSt+Na7VkT/zu/SJTxfiK2FORFJFbDcmH5PG+rCrhSlzM8mqMvfRpd18+8 QfbA==
MIME-Version: 1.0
Received: by 10.182.212.2 with SMTP id ng2mr34110679obc.81.1356977121727; Mon, 31 Dec 2012 10:05:21 -0800 (PST)
Received: by 10.76.19.43 with HTTP; Mon, 31 Dec 2012 10:05:21 -0800 (PST)
In-Reply-To: <a06240800cd074efd45b8@10.0.1.3>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3>
Date: Mon, 31 Dec 2012 13:05:21 -0500
Message-ID: <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com>
Subject: Re: WCIT outcome?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Day <jeanjour@comcast.net>
Content-Type: multipart/alternative; boundary=e89a8f6438f24f142304d229dbef
Cc: SM <sm@resistor.net>, IETF Discussion Mailing List <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: Mon, 31 Dec 2012 18:05:23 -0000

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

On Mon, Dec 31, 2012 at 9:51 AM, John Day <jeanjour@comcast.net> wrote:

> **
> Phillip,
>
>
> The reason that rule is useful is that just as it is ridiculous for the US
> representative to the ITU to attempt to convey the positions of Comcast and
> Google, it is no more practical for one person to represent the position of
> Cisco or Microsoft.
>
>
> Then I take it from this comment that you believe that all forms of
> representative government (and reaching agreements) are ridiculous?
>

MPs and Congressmen are elected decision makers. ITU participants can make
decisions but they are not binding on anyone and only have effect if people
like me choose to implement them.

Representative democracy without the elections part has neither.

And it may have escaped your notice but pretty much every government in the
developed world tries to limit the scope of their authority these days.
They have discovered that they prefer to concentrate their influence on a
narrow scope and thus maximize it.



> Surely you don't believe that pure democracy will work?  That myth had
> been dispelled 250 years ago.
>

I lived in Switzerland for two years. They have a government that passes a
budget. How is yours doing?



> The process of a representative form for creating agreements seems to be
> (as flawed as it is) about the best we have come up with.
>

ITU is not a democratic organization, nor does it aspire to be. So it is
not representative in the slightest. Reciting slogans does not mean they
are applicable



> Wrt its application in standards outside the ITU it works the same way.
> When a voluntary standards organization organizes by country, it is to give
> voice to the small companies as well as the Ciscos and Microsofts.  The big
> guys can send 10s of people (which represents a different problem) to
> meetings all over the world.  The little companies can't afford that but
> they have an interest.  Providing the means for them to agree on what their
> interest is and to make it heard is equally important.
>
> It sounds like you are arguing for the hegemony of the robber barons moved
> to the 21stC.
>

I deal with the world as I find it. It is very difficult to change the
Internet without the support of a Microsoft or a Google or a Cisco. There
are a ten billion endpoints deployed. The real obstacle is the hegemony of
the installed base.

Where the problem comes in is when you have a proposal that requires the
> active support and participation of stakeholders like VeriSign. When I told
> the IETF that DNSSEC would be deployed in dot.com if and only if the
> opt-in proposal was accepted, I was stating the official position of a
> stakeholder whose participation was essential if DNSSEC was going to be
> deployed.
>
>
> It was a really minor change but the reason it was blocked was one
> individual had the crazy idea that blocking deployment of DNSSEC would
> cause VeriSign to lose dotcom. He was not the only person with that idea
> but he was the only person in a position to wreck all progress in the IETF
> if he didn't get his way.
>
> For projects like IPv6 the standards development process needs to be
> better at identifying the necessary stakeholders and ensuring that enough
> essential requirements of enough stakeholders are met. Otherwise we end up
> with yet another Proposed Standard RFC that everyone ignores.
>
>
> I would disagree slightly.  It is not task of the SDO to identify the
> necessary stakeholders but to ensure all of the stakeholder are represented
> at all levels.  The problems you describe above result from breaking that
> rule.
>

I think the idea that the stakeholders want to participate is a mistaken
one. VeriSign particpates in IETF. Some of the backbone providers do. But
many do not.

So the frequent result is that IETF develops a widget and the deployment
showstoppers are only discovered during deployment.

It can get really lonely pointing out to a group of people with some idea
their are bursting to implement that they need to at least talk to the
application providers they need to adopt their idea.

The question is what, if anything, is there left relating to wireline
> communication that requires agreement among *governments*?  I can't think
> of much.
>

They need to come to an agreement to ban cyber-sabotage like they have
banned chemical and biological weapons.

Right now we have a group of US, Russian and Chinese military types all
looking to make their careers at the forefront of the new cyber arms race.
The military managed to piss away trillions of dollars in wealth with their
cold war, now they want to do the same in cyber. The cold war was
ultimately won because the youth of East Germany simply walked away from
the regime.

Like chemical weapons, cyber weapons are far more bark than bite and what
bite there is can hit the attacker. Stuxnet and Flame were crafted to
attack Iran, the vectors were repurposed and targeted at the US days after
they were discovered. We also have the interesting precedent that the UK
has launched a cyber sabotage attack against a nuclear facility declared as
civil and under an IAEA inspection regime.

We can't stop everyone from developing cyber-sabotage capabilities but we
can push efforts that occur so far underground that they can't poison
attempts to deploy effective defenses. The US and Chinese critical
infrastructures may be separate at a physical level but they are tightly
coupled at a logical and economic level. Any weapon that affects one is at
least capable of bringing down the other.


That is the task that the ITU should be addressing. It might as well get
started on it because one consequence of the Dubai debacle is that the
remaining ITU standards efforts have been compromised.

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

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

On Mon, Dec 31, 2012 at 9:51 AM, John Day <span dir=3D"ltr">&lt;<a href=3D"=
mailto:jeanjour@comcast.net" target=3D"_blank">jeanjour@comcast.net</a>&gt;=
</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<u></u>
<div>
<div>Phillip,</div><div class=3D"im">
<div><br></div>
<blockquote type=3D"cite"><br></blockquote>
<blockquote type=3D"cite">The reason that rule is useful is that
just as it is ridiculous for the US representative to the ITU to
attempt to convey the positions of Comcast and Google, it is no more
practical for one person to represent the position of Cisco or
Microsoft.</blockquote>
<div><br></div>
</div><div>Then I take it from this comment that you believe that all forms
of representative government (and reaching agreements) are
ridiculous?</div></div></blockquote><div><br></div><div>MPs and Congressmen=
 are elected decision makers. ITU participants can make decisions but they =
are not binding on anyone and only have effect if people like me choose to =
implement them.</div>
<div><br></div><div>Representative democracy without the elections part has=
 neither.</div><div><br></div><div>And it may have escaped your notice but =
pretty much every government in the developed world tries to limit the scop=
e of their authority these days. They have discovered that they prefer to c=
oncentrate their influence on a narrow scope and thus maximize it.</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>
<div>Surely you don&#39;t believe that pure democracy will work?=A0
That myth had been dispelled 250 years ago.</div></div></blockquote><div><b=
r></div><div>I lived in Switzerland for two years. They have a government t=
hat passes a budget. How is yours doing?</div><div><br></div><div>=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>
<div>The process of a representative form for creating agreements
seems to be (as flawed as it is) about the best we have come up
with.</div></div></blockquote><div><br></div><div>ITU is not a democratic o=
rganization, nor does it aspire to be. So it is not representative in the s=
lightest. Reciting slogans does not mean they are applicable</div><div>
<br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<div>Wrt its application in standards outside the ITU it works the
same way.=A0 When a voluntary standards organization organizes by
country, it is to give voice to the small companies as well as the
Ciscos and Microsofts.=A0 The big guys can send 10s of people
(which represents a different problem) to meetings all over the
world.=A0 The little companies can&#39;t afford that but they have an
interest.=A0 Providing the means for them to agree on what their
interest is and to make it heard is equally important.</div>
<div><br></div>
<div>It sounds like you are arguing for the hegemony of the robber
barons moved to the 21stC.</div></div></blockquote><div><br></div><div>I de=
al with the world as I find it. It is very difficult to change the Internet=
 without the support of a Microsoft or a Google or a Cisco. There are a ten=
 billion endpoints deployed. The real obstacle is the hegemony of the insta=
lled base.</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">
<blockquote type=3D"cite">Where the problem comes in is when you
have a proposal that requires the active support and participation of
stakeholders like VeriSign. When I told the IETF that DNSSEC would be
deployed in <a href=3D"http://dot.com" target=3D"_blank">dot.com</a> if and=
 only if the
opt-in proposal was accepted, I was stating the official position of a
stakeholder whose participation was essential if DNSSEC was going to
be deployed.</blockquote>
<blockquote type=3D"cite"><br></blockquote>
<blockquote type=3D"cite">It was a really minor change but the
reason it was blocked was one individual had the crazy idea that
blocking deployment of DNSSEC would cause VeriSign to lose dotcom. He
was not the only person with that idea but he was the only person in a
position to wreck all progress in the IETF if he didn&#39;t get his
way.</blockquote>
<blockquote type=3D"cite">For projects like IPv6 the standards
development process needs to be better at identifying the necessary
stakeholders and ensuring that enough essential requirements of enough
stakeholders are met. Otherwise we end up with yet another Proposed
Standard RFC that everyone ignores.</blockquote>
<div><br></div>
</div><div>I would disagree slightly.=A0 It is not task of the SDO to
identify the necessary stakeholders but to ensure all of the
stakeholder are represented at all levels.=A0 The problems you
describe above result from breaking that rule.</div></blockquote><div><br><=
/div><div>I think the idea that the stakeholders want to participate is a m=
istaken one. VeriSign particpates in IETF. Some of the backbone providers d=
o. But many do not.</div>
<div><br></div><div>So the frequent result is that IETF develops a widget a=
nd the deployment showstoppers are only discovered during deployment.</div>=
<div><br></div><div>It can get really lonely pointing out to a group of peo=
ple with some idea their are bursting to implement that they need to at lea=
st talk to the application providers they need to adopt their idea.</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><div class=3D"im"><div>T=
he question is what, if anything, is there left relating to
wireline communication that requires agreement among *governments*?=A0
I can&#39;t think of much.</div></div></div></blockquote><div><br></div><di=
v>They need to come to an agreement to ban cyber-sabotage like they have ba=
nned chemical and biological weapons.</div><div><br></div><div>Right now we=
 have a group of US, Russian and Chinese military types all looking to make=
 their careers at the forefront of the new cyber arms race. The military ma=
naged to piss away trillions of dollars in wealth with their cold war, now =
they want to do the same in cyber. The cold war was ultimately won because =
the youth of East Germany simply walked away from the regime.</div>
</div><br clear=3D"all"><div>Like chemical weapons, cyber weapons are far m=
ore bark than bite and what bite there is can hit the attacker. Stuxnet and=
 Flame were crafted to attack Iran, the vectors were repurposed and targete=
d at the US days after they were discovered. We also have the interesting p=
recedent that the UK has launched a cyber sabotage attack against a nuclear=
 facility declared as civil and under an IAEA inspection regime.</div>
<div><br></div><div>We can&#39;t stop everyone from developing cyber-sabota=
ge capabilities but we can push efforts that occur so far underground that =
they can&#39;t poison attempts to deploy effective defenses. The US and Chi=
nese critical infrastructures may be separate at a physical level but they =
are tightly coupled at a logical and economic level. Any weapon that affect=
s one is at least capable of bringing down the other.</div>
<div><br></div><div><br></div><div>That is the task that the ITU should be =
addressing. It might as well get started on it because one consequence of t=
he Dubai debacle is that the remaining ITU standards efforts have been comp=
romised.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>

--e89a8f6438f24f142304d229dbef--

From ndonnang@isoc-cameroon.org  Mon Dec 31 10:40:53 2012
Return-Path: <ndonnang@isoc-cameroon.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 3D29821F8767 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 10:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.315
X-Spam-Level: 
X-Spam-Status: No, score=0.315 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_BL_SPAMCOP_NET=1.96, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYk1GC5-2DTC for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 10:40:52 -0800 (PST)
Received: from gateway05.websitewelcome.com (gateway05.websitewelcome.com [67.18.16.77]) by ietfa.amsl.com (Postfix) with ESMTP id B874821F870C for <ietf@ietf.org>; Mon, 31 Dec 2012 10:40:52 -0800 (PST)
Received: by gateway05.websitewelcome.com (Postfix, from userid 5007) id 2F3FDC1CECE3; Mon, 31 Dec 2012 12:40:52 -0600 (CST)
Received: from pathfinder.websitewelcome.com (pathfinder.websitewelcome.com [74.54.78.50]) by gateway05.websitewelcome.com (Postfix) with ESMTP id 245DFC1CECAB for <ietf@ietf.org>; Mon, 31 Dec 2012 12:40:52 -0600 (CST)
Received: from [195.24.199.34] (port=51472 helo=[127.0.0.1]) by pathfinder.websitewelcome.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80) (envelope-from <ndonnang@isoc-cameroon.org>) id 1TpkI5-0001WV-Tq; Mon, 31 Dec 2012 12:40:50 -0600
Message-ID: <50E1DC2C.8020406@isoc-cameroon.org>
Date: Mon, 31 Dec 2012 19:40:44 +0100
From: Victor Ndonnang <ndonnang@isoc-cameroon.org>
Organization: ISOC Cameroon Chapter
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: 30th Anniversary of Transition to TCP/IP
References: <9DA543CE-5AE0-41B9-B0B9-49C6B208CCEE@vigilsec.com> <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
In-Reply-To: <B2E21F96-6487-437C-826E-00F610729D22@ietf.org>
Content-Type: multipart/mixed; boundary="------------080006040504070408090301"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - pathfinder.websitewelcome.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - isoc-cameroon.org
X-BWhitelist: no
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([127.0.0.1]) [195.24.199.34]:51472
X-Source-Auth: ndonnang@isoc-cameroon.org
X-Email-Count: 1
X-Source-Cap: aXNvY2NhbTtuZG9ubmFuZztwYXRoZmluZGVyLndlYnNpdGV3ZWxjb21lLmNvbQ==
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ndonnang@isoc-cameroon.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, 31 Dec 2012 18:40:53 -0000

This is a multi-part message in MIME format.
--------------080006040504070408090301
Content-Type: multipart/alternative;
 boundary="------------040409010802090602040709"


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

Great one!
Happy and prosperous New Year 2013 to the entire IETF Community. The 
Internet works because of your great work. Thanks!
Victor Ndonnang.

On 31/12/2012 18:21, IETF Chair wrote:
> Happy New Year.  It is already 2013 in some part of the world.
>
> The ARPANET transitioned to TCP/IP on 1 January 1983.  That was 30 
> years ago, and it was a huge milestone in the journey toward the 
> Internet as we know it.
>
> You can see the transition plan.  Like so many other historic 
> networking documents, it is an RFC.  See 
> http://www.rfc-editor.org/rfc/rfc801.txt
>
> Happy New Year,
>   Russ
>


--------------040409010802090602040709
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">
    Great one!<br>
    Happy and prosperous New Year 2013 to the entire IETF Community. The
    Internet works because of your great work. Thanks!<br>
    Victor Ndonnang.<br>
    <br>
    <div class="moz-cite-prefix">On 31/12/2012 18:21, IETF Chair wrote:<br>
    </div>
    <blockquote cite="mid:B2E21F96-6487-437C-826E-00F610729D22@ietf.org"
      type="cite">
      <div style="font-family: arial, helvetica, sans-serif; font-size:
        10pt">
        <div dir="ltr">
          <div class="gmail_default" style="">Happy New Year. &nbsp;It is
            already 2013 in some part of the world.</div>
          <div class="gmail_default" style=""><br>
          </div>
          <div class="gmail_default" style="">The ARPANET transitioned
            to TCP/IP on 1 January 1983. &nbsp;That was 30 years ago, and it
            was a huge milestone in the journey toward the Internet as
            we know it.</div>
          <div class="gmail_default" style=""><br>
          </div>
          <div class="gmail_default" style="">You can see the transition
            plan. &nbsp;Like so many other historic networking documents, it
            is an RFC. &nbsp;See <a moz-do-not-send="true"
              href="http://www.rfc-editor.org/rfc/rfc801.txt">http://www.rfc-editor.org/rfc/rfc801.txt</a>&nbsp;</div>
          <div class="gmail_default" style=""><br>
          </div>
          <div class="gmail_default" style="">Happy New Year,&nbsp;</div>
          <div class="gmail_default" style="">&nbsp; Russ</div>
          <div class="gmail_default" style=""><br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------040409010802090602040709--

--------------080006040504070408090301
Content-Type: text/x-vcard; charset=utf-8;
 name="ndonnang.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="ndonnang.vcf"

begin:vcard
fn:Victor Ndonnang
n:Ndonnang;Victor
org:ISOC Cameroon Chapter
adr:;;;Yaounde;;B.P. 8149;Cameroon
email;internet:ndonnang@isoc-cameroon.org
title:Secretary General
tel;cell:+237 77750724
url:www.isoc.cm
version:2.1
end:vcard


--------------080006040504070408090301--

From jnc@mercury.lcs.mit.edu  Mon Dec 31 11:27:18 2012
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 6221721F884D for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 11:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.144
X-Spam-Level: 
X-Spam-Status: No, score=-5.144 tagged_above=-999 required=5 tests=[AWL=-1.145, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjKaZiZPH8KT for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 11:27:17 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8211D21F884A for <ietf@ietf.org>; Mon, 31 Dec 2012 11:27:17 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0AF8218C092; Mon, 31 Dec 2012 14:27:16 -0500 (EST)
To: ietf@ietf.org
Subject: Re: 30th Anniversary of Transition to TCP/IP
Message-Id: <20121231192716.0AF8218C092@mercury.lcs.mit.edu>
Date: Mon, 31 Dec 2012 14:27:16 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: internet-history@postel.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: Mon, 31 Dec 2012 19:27:18 -0000

    > From: IETF Chair <chair@ietf.org>

    > The ARPANET transitioned to TCP/IP on 1 January 1983. That was 30 years
    > ago,

It's very hard indeed to fully grasp that it's only been 30 years. My kids
(now roughly 20) live in what is in some ways an entirely different world to
the one I grew up in.

Many technologies have had profound impacts in a short time (my parents were
born shortly after the dawn of flight, and in their late middle age saw
people landing on the Moon); and train, telegraph and telephone all each had
tremendous impact, but I'm not sure any have had quite as much as this
internetting stuff.

It's been quite a ride.

	Noel

From jeanjour@comcast.net  Mon Dec 31 13:09:52 2012
Return-Path: <jeanjour@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 E752921F8500 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 13:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.371
X-Spam-Level: 
X-Spam-Status: No, score=-100.371 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, HTML_MESSAGE=0.001, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8iKNsrnnRk3 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 13:09:51 -0800 (PST)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id DD48121F86D4 for <ietf@ietf.org>; Mon, 31 Dec 2012 13:09:50 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta07.westchester.pa.mail.comcast.net with comcast id iM9V1k0011ei1Bg57M9qaA; Mon, 31 Dec 2012 21:09:50 +0000
Received: from [10.0.1.3] ([98.229.211.49]) by omta24.westchester.pa.mail.comcast.net with comcast id iM9o1k01M14WE023kM9pfK; Mon, 31 Dec 2012 21:09:50 +0000
Mime-Version: 1.0
Message-Id: <a06240809cd0799fee029@[10.0.1.3]>
In-Reply-To: <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com>
References: <CAMm+Lwh2cHRY+Dk2_SDtZZmUbPcgRpP89u3DHUcniJDrKrX_pw@mail.gmail.com> <CAMzo+1a0-90dnjnvs48a9DcNN9DY_edF5hH0__4XRuCaLHtL6Q@mail.gmail.com> <CAMm+LwjzjLc2-=4EdxwHOi21B3dOBUohYc5hhXZHL_Pk+iBBmQ@mail.gmail.com> <6.2.5.6.2.20121229192941.0aae33e8@resistor.net> <CAMm+LwiC0xtJU4vnGFPvAG4VKZdj7Tf3LfW0+pzwxKWTegRREw@mail.gmail.com> <a06240800cd074efd45b8@10.0.1.3> <CAMm+Lwiq+DCzXw572wKs78DG+XzYsJtwCVSPvNuVHSrT=Cr2nA@mail.gmail.com>
Date: Mon, 31 Dec 2012 16:08:42 -0500
To: Phillip Hallam-Baker <hallam@gmail.com>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: WCIT outcome?
Content-Type: multipart/alternative; boundary="============_-855134307==_ma============"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1356988190; bh=63T6O7syaYlKlKi8MO7JF+RC4ic+cL2HUbbyTxIJme0=; h=Received:Received:Mime-Version:Message-Id:Date:To:From:Subject: Content-Type; b=V3feEtiqIyMuhEu62OjlvAS1i71Xe6wWRarQ4maECooBC8ilC6CCm3sVPUjkBgAm8 9nUPfLhDTEl6WmlffIcJO04CxbmMX0/NsLEFLM5Q1opL8OzHlEYvasZ0t9b/4Qd7OF g2HVlTwFwdyhkgpWFaeIOImvrSFM6KE0U/jyJ4RkCqihakFUMtAvyhl+GoIkXB9aea nLq9Kbk0lpYWRbzu1zzX7BQ++VvLhY7iBP8eFD+ZG5/344FKR9YAvrKLtr9tZwP/48 lVMGoxy2YdJWTyO/Oge2XCmbJzwuP9URDFotl5fL5fykAFDIA5KxKQBYUK2jHu7Y0y gmFdo5NsbOS8w==
Cc: SM <sm@resistor.net>, IETF Discussion Mailing List <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: Mon, 31 Dec 2012 21:09:53 -0000

--============_-855134307==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:
>On Mon, Dec 31, 2012 at 9:51 AM, John Day 
><<mailto:jeanjour@comcast.net>jeanjour@comcast.net> wrote:
>
>Phillip,
>
>>
>The reason that rule is useful is that just as it is ridiculous for 
>the US representative to the ITU to attempt to convey the positions 
>of Comcast and Google, it is no more practical for one person to 
>represent the position of Cisco or Microsoft.
>
>
>Then I take it from this comment that you believe that all forms of 
>representative government (and reaching agreements) are ridiculous?
>
>
>MPs and Congressmen are elected decision makers. ITU participants 
>can make decisions but they are not binding on anyone and only have 
>effect if people like me choose to implement them.

This was my point. The standards part of ITU is just like any other 
standards organization. But there are other things it does which are 
not like this, e.g. spectrum allocation.  There are other aspects 
with respect to tariffs that are binding on signatories.

>
>Representative democracy without the elections part has neither.

Neither of what?

>
>And it may have escaped your notice but pretty much every government 
>in the developed world tries to limit the scope of their authority 
>these days. They have discovered that they prefer to concentrate 
>their influence on a narrow scope and thus maximize it.

That also was my point, if you had read to the bottom.  In fact, I 
would suggest that the delegations of the developed world made a 
mistake assuming that the scope of the ITU was the same as it always 
had been.  By doing this, they gave up ground they didn't need to.

>
>
>
>Surely you don't believe that pure democracy will work?  That myth 
>had been dispelled 250 years ago.
>
>
>I lived in Switzerland for two years. They have a government that 
>passes a budget. How is yours doing?
>
>

I am sorry but I am not sure what Switzerland has to do with this 
discussion.  Last time I looked they had a republic (representative) 
form of government not a pure democracy.  No one every claimed it was 
efficient.

>
>The process of a representative form for creating agreements seems 
>to be (as flawed as it is) about the best we have come up with.
>
>
>ITU is not a democratic organization, nor does it aspire to be. So 
>it is not representative in the slightest. Reciting slogans does not 
>mean they are applicable

No one claimed it was.  In fact, quite the opposite.  I claimed it 
was organized as a republic form, which does what it is members vote 
on.  It turns out its members are countries.  (As I indicated below, 
I am not sure in the changed circumstances this is appropriate.) 
Actually one thing you seem to have missed, which I thought you would 
have jumped all over.  Generally, ITU meetings require unanimity to 
have a consensus.  This time they went with a simple majority.  I 
would have thought this would have created a fair amount of 
consternation.

>
>
>Wrt its application in standards outside the ITU it works the same 
>way.  When a voluntary standards organization organizes by country, 
>it is to give voice to the small companies as well as the Ciscos and 
>Microsofts.  The big guys can send 10s of people (which represents a 
>different problem) to meetings all over the world.  The little 
>companies can't afford that but they have an interest.  Providing 
>the means for them to agree on what their interest is and to make it 
>heard is equally important.
>
>It sounds like you are arguing for the hegemony of the robber barons 
>moved to the 21stC.
>
>
>I deal with the world as I find it. It is very difficult to change 
>the Internet without the support of a Microsoft or a Google or a 
>Cisco. There are a ten billion endpoints deployed. The real obstacle 
>is the hegemony of the installed base.

;-)  Why is that daunting?  ;-)  I hear that excuse often.  If we had 
had that attitude when we started this effort 40 years ago.  We would 
still be patching the PSTN.  There would be no Internet. Do you think 
the Internet was a success because we convinced IBM and AT&T it was a 
good idea?!!  I am sorry to see that the younger generation is so 
faint of heart.  Can't take a little challenge!

Actually, it isn't the ITU that is in the way.  It is the structure 
of the IETF that gives the big players such power.

>
>>Where the problem comes in is when you have a proposal that 
>>requires the active support and participation of stakeholders like 
>>VeriSign. When I told the IETF that DNSSEC would be deployed in 
>><http://dot.com>dot.com if and only if the opt-in proposal was 
>>accepted, I was stating the official position of a stakeholder 
>>whose participation was essential if DNSSEC was going to be 
>>deployed.
>>
>>
>>It was a really minor change but the reason it was blocked was one 
>>individual had the crazy idea that blocking deployment of DNSSEC 
>>would cause VeriSign to lose dotcom. He was not the only person 
>>with that idea but he was the only person in a position to wreck 
>>all progress in the IETF if he didn't get his way.
>>
>>For projects like IPv6 the standards development process needs to 
>>be better at identifying the necessary stakeholders and ensuring 
>>that enough essential requirements of enough stakeholders are met. 
>>Otherwise we end up with yet another Proposed Standard RFC that 
>>everyone ignores.
>>
>
>I would disagree slightly.  It is not task of the SDO to identify 
>the necessary stakeholders but to ensure all of the stakeholder are 
>represented at all levels.  The problems you describe above result 
>from breaking that rule.
>
>
>I think the idea that the stakeholders want to participate is a 
>mistaken one. VeriSign particpates in IETF. Some of the backbone 
>providers do. But many do not.

Self-fulfilling prophecy.  The structure of the IETF makes it 
difficult to impossible.  So why should they waste their time?

>
>So the frequent result is that IETF develops a widget and the 
>deployment showstoppers are only discovered during deployment.

That is just bad design.  I am not sure I would admit to that if I 
were you.  It doesn't look good.  Indicates that the IETF does not 
understand its constituency.

>
>It can get really lonely pointing out to a group of people with some 
>idea their are bursting to implement that they need to at least talk 
>to the application providers they need to adopt their idea.

Why?  The WCTU said, never marry drunkard to reform him.  They will 
find out soon enough.

>
>The question is what, if anything, is there left relating to 
>wireline communication that requires agreement among *governments*? 
>I can't think of much.
>
>
>They need to come to an agreement to ban cyber-sabotage like they 
>have banned chemical and biological weapons.

Do they?  Don't you think it is interesting that the countries crying 
loudest for this are the source of much of it and have sufficiently 
authoritarian regimes that they could shut down next week if they 
wanted?

It is far from clear to me that such an agreement would be worth the 
paper it was written on, unless it is possible to prove (which we 
can't in 99% of the cases) that it was a State that mounted the 
attack.

>
>Right now we have a group of US, Russian and Chinese military types 
>all looking to make their careers at the forefront of the new cyber 
>arms race. The military managed to piss away trillions of dollars in 
>wealth with their cold war, now they want to do the same in cyber. 
>The cold war was ultimately won because the youth of East Germany 
>simply walked away from the regime.

You really believe that?!  The cold war was won, because Gorbachev 
*chose* not to repeat the response to the Hungarian and Czech revolts 
of '56 and '68.  Tian An Men provides a good counter-example.  You 
need to read Lutwack's Coup d'Etat: A Practical Handbook.   Walking 
away isn't sufficient.

>
>Like chemical weapons, cyber weapons are far more bark than bite and 
>what bite there is can hit the attacker. Stuxnet and Flame were 
>crafted to attack Iran, the vectors were repurposed and targeted at 
>the US days after they were discovered. We also have the interesting 
>precedent that the UK has launched a cyber sabotage attack against a 
>nuclear facility declared as civil and under an IAEA inspection 
>regime.
>
>We can't stop everyone from developing cyber-sabotage capabilities 
>but we can push efforts that occur so far underground that they 
>can't poison attempts to deploy effective defenses. The US and 
>Chinese critical infrastructures may be separate at a physical level 
>but they are tightly coupled at a logical and economic level. Any 
>weapon that affects one is at least capable of bringing down the 
>other.

This was another point I made although not specifically on 
cyber-security. If you look closely at these kinds of attacks they 
have little or nothing to do with the functioning of the *Internet.* 
They have a lot more to do with what the Internet is used for.  (This 
is like saying the ITU has some sort of authority over what is said 
over the phone. Not something I think is a good idea, although 
apparently you do.)  Which tells us why the authoritarian regimes are 
so big on pushing it.  They see cyber-security treaties as a means to 
increase their control for domestic suppression and isolate their 
populations.  Support it if you want, but I certainly would think 
twice about it.

>
>That is the task that the ITU should be addressing.

Gawd! I hope not.

>  It might as well get started on it because one consequence of the 
>Dubai debacle is that the remaining ITU standards efforts have been 
>compromised.

The ITU standards efforts were unaffected and irrelevant to what 
happened in Dubai. which is too bad.  For 30+ years, I have described 
their standards efforts as targeted a market window 15 minutes in the 
future.  Even before you get to how badly flawed they are 
technically.  The ITU standards effort is just another ho-hum 
voluntary standards group like the IETF, or IEEE, or ASTM, or EIA, or 
ICAO, or even ISO.

Take care,
John Day
--============_-855134307==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re: WCIT outcome?</title></head><body>
<div>At 1:05 PM -0500 12/31/12, Phillip Hallam-Baker wrote:</div>
<blockquote type="cite" cite>On Mon, Dec 31, 2012 at 9:51 AM, John Day
&lt;<a href="mailto:jeanjour@comcast.net">jeanjour@comcast.net</a>&gt;
wrote:<br>
<blockquote>Phillip,</blockquote>
<blockquote><br>
<blockquote type="cite" cite><br></blockquote>
</blockquote>
<blockquote>
<blockquote>The reason that rule is useful is that just as it is
ridiculous for the US representative to the ITU to attempt to convey
the positions of Comcast and Google, it is no more practical for one
person to represent the position of Cisco or Microsoft.<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>Then I take it from this comment that you believe that all
forms of representative government (and reaching agreements) are
ridiculous?<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>MPs and Congressmen are elected decision
makers. ITU participants can make decisions but they are not binding
on anyone and only have effect if people like me choose to implement
them.</blockquote>
<div><br></div>
<div>This was my point. The standards part of ITU is just like any
other standards organization. But there are other things it does which
are not like this, e.g. spectrum allocation.&nbsp; There are other
aspects with respect to tariffs that are binding on signatories.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Representative democracy without the
elections part has neither.</blockquote>
<div><br>
Neither of what?<br>
</div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>And it may have escaped your notice but
pretty much every government in the developed world tries to limit the
scope of their authority these days. They have discovered that they
prefer to concentrate their influence on a narrow scope and thus
maximize it.</blockquote>
<div><br></div>
<div>That also was my point, if you had read to the bottom.&nbsp; In
fact, I would suggest that the delegations of the developed world made
a mistake assuming that the scope of the ITU was the same as it always
had been.&nbsp; By doing this, they gave up ground they didn't need
to.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;<br>
<blockquote>Surely you don't believe that pure democracy will work?&nbsp;
That myth had been dispelled 250 years ago.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I lived in Switzerland for two years.
They have a government that passes a budget. How is yours
doing?</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>&nbsp;</blockquote>
<div><br></div>
<div>I am sorry but I am not sure what Switzerland has to do with this
discussion.&nbsp; Last time I looked they had a republic
(representative) form of government not a pure democracy.&nbsp; No one
every claimed it was efficient.</div>
<div><br></div>
<blockquote type="cite" cite><br>
<blockquote>The process of a representative form for creating
agreements seems to be (as flawed as it is) about the best we have
come up with.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>ITU is not a democratic organization, nor
does it aspire to be. So it is not representative in the slightest.
Reciting slogans does not mean they are applicable</blockquote>
<div><br></div>
<div>No one claimed it was.&nbsp; In fact, quite the opposite.&nbsp; I
claimed it was organized as a republic form, which does what it is
members vote on.&nbsp; It turns out its members are countries.&nbsp;
(As I indicated below, I am not sure in the changed circumstances this
is appropriate.)&nbsp; Actually one thing you seem to have missed,
which I thought you would have jumped all over.&nbsp; Generally, ITU
meetings require unanimity to have a consensus.&nbsp; This time they
went with a simple majority.&nbsp; I would have thought this would
have created a fair amount of consternation.</div>
<div><br></div>
<blockquote type="cite" cite>&nbsp;<br>
<blockquote>Wrt its application in standards outside the ITU it works
the same way.&nbsp; When a voluntary standards organization organizes
by country, it is to give voice to the small companies as well as the
Ciscos and Microsofts.&nbsp; The big guys can send 10s of people
(which represents a different problem) to meetings all over the
world.&nbsp; The little companies can't afford that but they have an
interest.&nbsp; Providing the means for them to agree on what their
interest is and to make it heard is equally important.</blockquote>
<blockquote><br></blockquote>
<blockquote>It sounds like you are arguing for the hegemony of the
robber barons moved to the 21stC.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I deal with the world as I find it. It is
very difficult to change the Internet without the support of a
Microsoft or a Google or a Cisco. There are a ten billion endpoints
deployed. The real obstacle is the hegemony of the installed
base.</blockquote>
<div><br></div>
<div>;-)&nbsp; Why is that daunting?&nbsp; ;-)&nbsp; I hear that
excuse often.&nbsp; If we had had that attitude when we started this
effort 40 years ago.&nbsp; We would still be patching the PSTN.&nbsp;
There would be no Internet. Do you think the Internet was a success
because we convinced IBM and AT&amp;T it was a good idea?!!&nbsp; I am
sorry to see that the younger generation is so faint of heart.&nbsp;
Can't take a little challenge! </div>
<div><br></div>
<div>Actually, it isn't the ITU that is in the way.&nbsp; It is the
structure of the IETF that gives the big players such power.</div>
<div><br></div>
<blockquote type="cite" cite><br>
<blockquote type="cite" cite>
<blockquote>Where the problem comes in is when you have a proposal
that requires the active support and participation of stakeholders
like VeriSign. When I told the IETF that DNSSEC would be deployed in <a
href="http://dot.com">dot.com</a> if and only if the opt-in proposal
was accepted, I was stating the official position of a stakeholder
whose participation was essential if DNSSEC was going to be
deployed.<br>
</blockquote>
<blockquote><br></blockquote>
<blockquote>It was a really minor change but the reason it was blocked
was one individual had the crazy idea that blocking deployment of
DNSSEC would cause VeriSign to lose dotcom. He was not the only person
with that idea but he was the only person in a position to wreck all
progress in the IETF if he didn't get his way.<br>
</blockquote>
<blockquote>For projects like IPv6 the standards development process
needs to be better at identifying the necessary stakeholders and
ensuring that enough essential requirements of enough stakeholders are
met. Otherwise we end up with yet another Proposed Standard RFC that
everyone ignores.<br>
</blockquote>
</blockquote>
<blockquote><br></blockquote>
<blockquote>I would disagree slightly.&nbsp; It is not task of the SDO
to identify the necessary stakeholders but to ensure all of the
stakeholder are represented at all levels.&nbsp; The problems you
describe above result from breaking that rule.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>I think the idea that the stakeholders
want to participate is a mistaken one. VeriSign particpates in IETF.
Some of the backbone providers do. But many do not.</blockquote>
<div><br></div>
<div>Self-fulfilling prophecy.&nbsp; The structure of the IETF makes
it difficult to impossible.&nbsp; So why should they waste their
time?</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>So the frequent result is that IETF
develops a widget and the deployment showstoppers are only discovered
during deployment.</blockquote>
<div><br></div>
<div>That is just bad design.&nbsp; I am not sure I would admit to
that if I were you.&nbsp; It doesn't look good.&nbsp; Indicates that
the IETF does not understand its constituency.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>It can get really lonely pointing out to
a group of people with some idea their are bursting to implement that
they need to at least talk to the application providers they need to
adopt their idea.</blockquote>
<div><br></div>
<div>Why?&nbsp; The WCTU said, never marry drunkard to reform him.&nbsp;
They will find out soon enough.</div>
<div><br></div>
<blockquote type="cite" cite><br>
<blockquote>The question is what, if anything, is there left relating
to wireline communication that requires agreement among
*governments*?&nbsp; I can't think of much.<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>They need to come to an agreement to ban
cyber-sabotage like they have banned chemical and biological
weapons.</blockquote>
<div><br></div>
<div>Do they?&nbsp; Don't you think it is interesting that the
countries crying loudest for this are the source of much of it and
have sufficiently authoritarian regimes that they could shut down next
week if they wanted?</div>
<div><br></div>
<div>It is far from clear to me that such an agreement would be worth
the paper it was written on, unless it is possible to prove (which we
can't in 99% of the cases) that it was a State that mounted the
attack. </div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Right now we have a group of US, Russian
and Chinese military types all looking to make their careers at the
forefront of the new cyber arms race. The military managed to piss
away trillions of dollars in wealth with their cold war, now they want
to do the same in cyber. The cold war was ultimately won because the
youth of East Germany simply walked away from the regime.</blockquote>
<div><br></div>
<div>You really believe that?!&nbsp; The cold war was won, because
Gorbachev *chose* not to repeat the response to the Hungarian and
Czech revolts of '56 and '68.&nbsp; Tian An Men provides a good
counter-example.&nbsp; You need to read Lutwack's Coup d'Etat: A
Practical Handbook.&nbsp;&nbsp; Walking away isn't sufficient.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>Like chemical weapons, cyber weapons are
far more bark than bite and what bite there is can hit the attacker.
Stuxnet and Flame were crafted to attack Iran, the vectors were
repurposed and targeted at the US days after they were discovered. We
also have the interesting precedent that the UK has launched a cyber
sabotage attack against a nuclear facility declared as civil and under
an IAEA inspection regime.</blockquote>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>We can't stop everyone from developing
cyber-sabotage capabilities but we can push efforts that occur so far
underground that they can't poison attempts to deploy effective
defenses. The US and Chinese critical infrastructures may be separate
at a physical level but they are tightly coupled at a logical and
economic level. Any weapon that affects one is at least capable of
bringing down the other.</blockquote>
<div><br></div>
<div>This was another point I made although not specifically on
cyber-security. If you look closely at these kinds of attacks they
have little or nothing to do with the functioning of the *Internet.*&nbsp;
They have a lot more to do with what the Internet is used for.&nbsp;
(This is like saying the ITU has some sort of authority over what is
said over the phone. Not something I think is a good idea, although
apparently you do.)&nbsp; Which tells us why the authoritarian regimes
are so big on pushing it.&nbsp; They see cyber-security treaties as a
means to increase their control for domestic suppression and isolate
their populations.&nbsp; Support it if you want, but I certainly would
think twice about it.</div>
<div><br></div>
<blockquote type="cite" cite><br></blockquote>
<blockquote type="cite" cite>That is the task that the ITU should be
addressing.</blockquote>
<div><br></div>
<div>Gawd! I hope not.</div>
<div><br></div>
<blockquote type="cite" cite>&nbsp;It might as well get started on it
because one consequence of the Dubai debacle is that the remaining ITU
standards efforts have been compromised.</blockquote>
<div><br></div>
<div>The ITU standards efforts were unaffected and irrelevant to what
happened in Dubai. which is too bad.&nbsp; For 30+ years, I have
described their standards efforts as targeted a market window 15
minutes in the future.&nbsp; Even before you get to how badly flawed
they are technically.&nbsp; The ITU standards effort is just another
ho-hum voluntary standards group like the IETF, or IEEE, or ASTM, or
EIA, or ICAO, or even ISO.</div>
<div><br></div>
<div>Take care,</div>
<div>John Day</div>
</body>
</html>
--============_-855134307==_ma============--

From lixia@cs.ucla.edu  Mon Dec 31 13:12:40 2012
Return-Path: <lixia@cs.ucla.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 E71D521F8905 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 13:12:40 -0800 (PST)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SFVmPzmOtmhO for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 13:12:40 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 0837921F884A for <ietf@ietf.org>; Mon, 31 Dec 2012 13:12:40 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id D7AE5A60002; Mon, 31 Dec 2012 13:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu
Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBs7BI+w4QWD; Mon, 31 Dec 2012 13:12:39 -0800 (PST)
Received: from [10.0.1.4] (cpe-76-174-95-149.socal.res.rr.com [76.174.95.149]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 1E2C4A60001; Mon, 31 Dec 2012 13:12:38 -0800 (PST)
Subject: Re: 30th Anniversary of Transition to TCP/IP
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <20121231192716.0AF8218C092@mercury.lcs.mit.edu>
Date: Mon, 31 Dec 2012 13:12:37 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <ABD5F28D-36F9-46E3-8A2D-167C44F8F78E@cs.ucla.edu>
References: <20121231192716.0AF8218C092@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1283)
Cc: internet-history@postel.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, 31 Dec 2012 21:12:41 -0000

On Dec 31, 2012, at 11:27 AM, Noel Chiappa wrote:

>> From: IETF Chair <chair@ietf.org>
>=20
>> The ARPANET transitioned to TCP/IP on 1 January 1983. That was 30 =
years
>> ago,
>=20
> It's very hard indeed to fully grasp that it's only been 30 years. My =
kids
> (now roughly 20) live in what is in some ways an entirely different =
world to
> the one I grew up in.
>=20
> Many technologies have had profound impacts in a short time (my =
parents were
> born shortly after the dawn of flight, and in their late middle age =
saw
> people landing on the Moon); and train, telegraph and telephone all =
each had
> tremendous impact, but I'm not sure any have had quite as much as this
> internetting stuff.

agree, both in terms of how much impact, and how big part of the society =
impacted.


>=20
> It's been quite a ride.
>=20
> 	Noel


From randy@psg.com  Mon Dec 31 14:21:06 2012
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 CC78721F8648 for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 14:21:06 -0800 (PST)
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]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MDJngyWkkSBG for <ietf@ietfa.amsl.com>; Mon, 31 Dec 2012 14:21:06 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 71A1321F8623 for <ietf@ietf.org>; Mon, 31 Dec 2012 14:21:06 -0800 (PST)
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 1Tpnj5-000J6i-I4; Mon, 31 Dec 2012 22:20:55 +0000
Date: Tue, 01 Jan 2013 07:20:53 +0900
Message-ID: <m2pq1pdfsq.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Paul Vixie <paul@redbarn.org>
Subject: Re: [ih] 30th Anniversary of Transition to TCP/IP
In-Reply-To: <50E1EC65.8030205@redbarn.org>
References: <20121231192716.0AF8218C092@mercury.lcs.mit.edu> <50E1EC65.8030205@redbarn.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: internet-history@postel.org, 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, 31 Dec 2012 22:21:06 -0000

> born in 1963, i felt throughout the 70's and 80's that i had been born
> too late, that all the fun stuff had been done already. now in the
> 10's i feel like we're just getting going and that i was probably born
> too soon, that all the fun stuff is coming 50 years from now.

if you missed the '60s, indeed you were born too late.

we watched the moon landing with our host's great grandmother who grew
up with gas lighting in her home.

the pace accelerates.  technology advances more and more rapidly.
civilization?  not so much.

randy
