
From hsantos@isdg.net  Wed May  1 03:16:22 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2669B21F8E96 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 03:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.426
X-Spam-Level: 
X-Spam-Status: No, score=-102.426 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6-trqRv8It5 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 03:16:18 -0700 (PDT)
Received: from ntbbs.santronics.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C5AEC21F8E8E for <ietf@ietf.org>; Wed,  1 May 2013 03:16:16 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5705; t=1367403371; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=d2EAr52 /KoRdyKjJvbTfzSXdxK8=; b=vCZ+SzpEJSfRoIT4nK1Wsu4bMJdpeWGlDSK12IZ hMLlxddzL0b0zwdjNFVPogWruyOScKijNvHyYniGC6Yk2d3Wo4X5ela6RLZvOWVb uHxBymBRmfLV1xlhTXn0G9ylEgEYQ7YTCfSzgtkY41mUGgxvg0wTHsPpduoiWsbe AJww=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 01 May 2013 06:16:11 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1902087900.7284.2740; Wed, 01 May 2013 06:16:11 -0400
Message-ID: <5180EB14.2020601@isdg.net>
Date: Wed, 01 May 2013 06:14:44 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu>
In-Reply-To: <tslhain34vj.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 10:16:22 -0000

The problem I have is not so much with the decision to deprecate SPF 
rrtype, it will remove this particular SPF protocol dual SPF/TXT call 
overhead in the network, but more so about what it says for future 
applications.

There will no incentive to design DNS applications with specific types, 
or it will always be a specific sub-domain TXT record.  Is that good or bad?

In many ways, the industry has gotten "comfortable" with overall 
non-compiled, non-binary, text-based applications. Improvements in 
hardware and software has made it all feasible.

Consider that once upon a time Microsoft's Caller-ID Policy (now 
SenderID) considered XML-formatted TXT record before merging with SPF. [1]

Consider that a SMTP receiver is now faced with new overheads and 
redundancy with at least 4-8 DNS Calls, and except for one, they are all 
TXT:

o RFC5321 SMTP level (before DATA state)

   - Growth in PTR requirement (rDNS) for connecting SMTP client,
   - SPF HELO/EHLO domain check (optional) (RFC4408),
   - SPF MAIL FROM domain check (RFC4408)
     - SPF MAIL FROM SUBMITTER domain check (RFC4405)

o RFC5321 SMTP level (DATA) or RFC5322 Post Acceptance processing:

   - DKIM Trust Domain public key check (RFC6376)
      - ADSP Author Domain Policy check (RFC5617)
      - VBR Trust Domain Check (RFC5518)
   - SenderID PRA domain check (RFC4406/4407)
   - Possible future new fast track DMARC proposal [2]

And they all have one common application need; get domain 
attributes/information.

Lets consider that these new TXT applications are authored by the same 
few folks with the same engineering mindset to use TXT since it is the 
most practical and offers the fastest entry point to the market and 
proof of concept.

There are many integration issues to consider.  We should look at a 
better solution where minimal calls can be made to extract domain 
operational information. I have a few ideas in this area and have even 
drafted yet another TXT-based solution.  What the above redundant domain 
information lookup did do was force us to redesign, update and single 
source our DNS resolutions across all components in our 
application/service servers.  That is because many of the above open 
source protocols come with libraries with their own DNS resolvers 
clients software. So we wrote our own and implemented each of the above 
protocols to use a single DNS API.  This allowed us to offer a local DNS 
cache to remove all overhead in the redundancy.  This also remove most 
of any doubt with customer's uplink DNS resolvers which can be behaving 
differently - a big savings in support cost.

I would like to have the option to support the SPF rrtype when and if we 
implement RFC4408BIS as deployment options to customers.  There are 
already new changes to the spec that will promote implementation changes 
(Accepting SPF Failed Message deployment option and a new 
Authentication-Result: trace header).

I believe the decision to pull SFP rrtype at this time (for RFC4408BIS) 
was premature and would like to see the design opportunity to support 
not only SPF rrtype but others.  I suggest to keep the migration path in 
RFC4408BIS with new implementation details.

I would also like to believe that the IETF can help get the DNS 
infrastructure updated to help support these modern DNS application 
requirements.  To my surprise, Microsoft DNS v5.0 which is what we have 
for our primary DNS server on a Windows 2003 machine, does not support 
RFC 3597 "Handling of Unknown DNS Resource Record (RR) Types" and it did 
not offer a method to add new ones.

Why is that?  Don't they have a stake in all this too? Are they reading 
these IETF forums?

Maybe this could be a plenary topic for you guys to talk about at these 
IETF meetings - "Supporting new DNS Applications: Improving the Quality 
of the DNS infrastructure."

--
HLS

[1] nslookup -query=txt _ep.hotmail.com

Non-authoritative answer:
_ep.hotmail.com text =

"<ep xmlns='http://ms.net/1' 
testing='true'><out><m><indirect>list1._ep.hotmail.com</indirect><indirect>list2._ep.hotmail.com</indirect><indirect>list3._ep.hotmail.com</indirect></m></out></ep>"

[2] http://www.dmarc.org/draft-dmarc-base-00-02.txt
[3] http://tools.ietf.org/html/rfc3597


On 4/30/2013 8:45 PM, Sam Hartman wrote:
> I think I understand this issue well enough to comment and so I will.
>
> 1) I totally believe it is reasonable to consider operational challenges
> when designing protocols. "Just upgrade your infrastructure, just use
> another registrar, just upgrade the infrastructure of the people you
> communicate with," are not generally reasonable advice to give people;
> ingoring these concerns tend to lead to things that cannot be deployed.
>
> 2) I think it's fine to come up with a solution that   is harder to
> implement because it is easier to deploy given the sorts of concerns in
> 1.
>
> 3) having reviewed the DNS arguments, I generally would recommend txt
> records with distinct owner names over new RR types for most
> protocols. I understand there are residual issues with that approach.
>
> 4) Using txt RRs the way SPF does--where the owner name is shared
> potentially with other applications is kind of unfortunate.  I don't
> know it's unfortunate enough to push for the SPF RR. But the issues
> people have brought up with regard to updates and RR order are very
> real.
> But so are the operational issues with SPF.
>
> So my personal opinion is that this is a valid discussion to be having
> even if we're having it again in IETF LC.  However, to be successful we
> need to get new participants and to ad more respect for arguments to the
> discussion.
>
>


From vesely@tana.it  Wed May  1 04:54:41 2013
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 8540D21F8682 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 04:54:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.75
X-Spam-Level: 
X-Spam-Status: No, score=-4.75 tagged_above=-999 required=5 tests=[AWL=-0.031,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eKuXABIGWvBE for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 04:54:37 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 1377C21F854E for <ietf@ietf.org>; Wed,  1 May 2013 04:54:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367409274; bh=ah6cS/Xv66vd2l11TSxjQvJ7S0EvzP5VIYj7wExXmCw=; l=1055; h=Date:From:To:References:In-Reply-To; b=EJTVwA2bK4xheJVRplYxym6K1uBj7CewM95MnQNMTaT9Tc0xxy3KF6fAuJqgGyQhy q5GBXdFqMGTzwW+skky+DUhMYBvB5zSIlEQgQ/D3r97nh6Xjbe7PA65iZFwGUq/+n3 woB9B/IOZACJB9KQMl591Jkz+/Gd9IAEdn0Tctpo=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Wed, 01 May 2013 13:54:34 +0200 id 00000000005DC035.000000005181027A.00004E30
Message-ID: <5181027A.6030203@tana.it>
Date: Wed, 01 May 2013 13:54:34 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <517FFBAB.3030107@dcrocker.net> <D6317B91-E7EB-499F-BBBF-A78CB44569F9@virtualized.org> <5180099A.8010405@dcrocker.net> <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org>
In-Reply-To: <EA2545BD-3060-462B-95CE-36DB5DA3511D@virtualized.org>
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: Wed, 01 May 2013 11:54:41 -0000

On Tue 30/Apr/2013 21:54:11 +0200 David Conrad wrote:
> On Apr 30, 2013, at 11:12 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>>> What is the IETF-approved timeframe in which "the market" is
>>> allowed to accept/reject a particular technology?
>>
>> I've no idea what the lower limit is or should be, but I'm quite
>> sure that 7 years exceeds it by a very comfortable margin.
> 
> By that logic we should abandon IPv6, DNSSEC, EDNS0, etc.

If it is possible to get exactly the same functionality without using
them, I guess we should.

The DNS community would do SPFBIS a favor if they try and understand
the current status of email authentication, and regard SPF as a set of
(missed) requirements rather than a means to trace a path that is not
paved yet.

If the next version of the SPF protocol (v=spf{>1}) will ever come
out, a better use of the DNS will be possible if the DNS will have met
those requirements by then.  That does not depend on whether we insist
on an unworkable specification in the -bis of the current version.

From vesely@tana.it  Wed May  1 06:07:00 2013
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 E14C921E80E8 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 06:06:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level: 
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z2hF6u5HHrnc for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 06:06:55 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 0C84721E80CD for <ietf@ietf.org>; Wed,  1 May 2013 06:05:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367413549; bh=N2QPRPVX8H08M6pJLEG8FHpvEEedgokC3EaAtE9c/cA=; l=562; h=Date:From:To:References:In-Reply-To; b=C6r11/n24s77yX1jqEmjrEY1DezQ8vs7r7i/ei7R5NYhCsssknpbLzY6LHTAnOQYu osNma+TLgomV8TgkMncn3Qu/7e6VXJ5M4Obi6TlyGBdc8N/hlnJv2oLKOzCj9yg7Di s8zwscyc1qtWZ0EhsaoTs8AIm3vt0OCtlvkuhehI=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Wed, 01 May 2013 15:05:49 +0200 id 00000000005DC039.000000005181132D.000017C4
Message-ID: <5181132C.3020601@tana.it>
Date: Wed, 01 May 2013 15:05:48 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us>
In-Reply-To: <517FFB33.30902@dougbarton.us>
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: Wed, 01 May 2013 13:07:00 -0000

On Tue 30/Apr/2013 19:11:15 +0200 Doug Barton wrote:
> On 04/30/2013 09:28 AM, Alessandro Vesely wrote:

>> While it's too late for SPF, we can learn this lesson.
> 
> As has been repeatedly pointed out in the discussion on both dnsext
> and spfbis, it is NOT too late for SPF. The way forward is simple:

The results of 4408 indicate we erred.  To persist is diabolical.

> 5. When the next version of the SPF protocol (v=spf{>1}) comes out
> make it SPF/99 only.

Why should a record of type SPF have the string "spf" in it?  Are
there precedents?

From presnick@qti.qualcomm.com  Wed May  1 06:44:08 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED6F421F9F28 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 06:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.307
X-Spam-Level: 
X-Spam-Status: No, score=-105.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDKKkyzpCVgx for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 06:44:03 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id C85E421F9F30 for <ietf@ietf.org>; Wed,  1 May 2013 06:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1367415843; x=1398951843; h=message-id:date:from:mime-version:cc:subject:references: in-reply-to:content-transfer-encoding; bh=X5FOY2S8W4ZMidd/3PcqdDwWXjJfuc+XvmjXY07jClI=; b=ujGVW9ZJN9ScMTjdQ3MkcsMRh0qy6O5t+atSdG9+xh86i7R+eCkJFJT+ p4dWAQ5rH5YEe8fRrKpTLohKtaGrLIzEeD+k8UlvQ8IOc5Vrb/uaKKXfz H+CeHQxvEZ2akyM2GZTh4hpEy1yxEyV8IoaoIi+d9K3z5728nHAtWyFIV c=;
X-IronPort-AV: E=Sophos;i="4.87,589,1363158000"; d="scan'208";a="43264043"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 01 May 2013 06:44:03 -0700
X-IronPort-AV: E=Sophos;i="4.87,588,1363158000"; d="scan'208";a="476980719"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 01 May 2013 06:44:03 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 1 May 2013 06:44:03 -0700
Message-ID: <51811C20.5040305@qti.qualcomm.com>
Date: Wed, 1 May 2013 08:44:00 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Blind reply-alls (Was: Obsoleting SPF RRTYPE)
References: <20130425013317.36729.qmail@joyce.lan>	<4272263.gKzvRQiTlr@scott-latitude-e6320>	<517C8994.2080102@gathman.org>	<1457820.oICsLp4n8g@scott-latitude-e6320>	<20130428195221.GA27654@besserwisser.org>	<8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com>	<517DAB89.8000409@gathman.org>	<8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com>	<517E90A6.6090108@gathman.org>	<8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com>	<517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net>	<20130429230742.3D2833339511@drugs.dv.isc.org>	<517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us>	<CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com>	<A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu>
In-Reply-To: <tslhain34vj.fsf@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
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: Wed, 01 May 2013 13:44:08 -0000

On 4/30/13 7:45 PM, Sam Hartman wrote:
> So my personal opinion is that this is a valid discussion to be having
> even if we're having it again in IETF LC.

Folks,

This document is *not* in IETF LC. A particular WG member, who was 
apparently upset with the tone of the argument on the SPFBIS and DNSEXT 
list, expressed his upset by cross-posting to the IETF list, claiming 
this had something to do with the "IETF Diversity" topic.

Then a bunch of other SPFBIS and DNSEXT folks blindly used "Reply-All", 
resulting in us all seeing this discussion.

I will leave it to the chairs/sergeants-of-arms of the respective lists 
to decide how they want to deal with this, but personally I think this 
discussion is not useful to have on the IETF list at the moment and 
suggest that folks be more careful of their use of "Reply-All". I also 
suggest that cross-posting to a new list without noting that in the body 
of the message is bad netiquette.

pr

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


From jari.arkko@piuha.net  Wed May  1 08:33:59 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 084FB21F98B1 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 08:33:59 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qfOUxPR8zvmI for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 08:33:54 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AD91521F98A6 for <ietf@ietf.org>; Wed,  1 May 2013 08:33:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C65AD2CC53; Wed,  1 May 2013 18:33:50 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jh0wHa4oCiOU; Wed,  1 May 2013 18:33:49 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 681E22CC48; Wed,  1 May 2013 18:33:48 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: call for ideas: tail-heavy IETF process
Date: Wed, 1 May 2013 08:33:47 -0700
Message-Id: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
To: IETF list <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 15:33:59 -0000

I wrote a blog article about how we do a fairly significant amount of =
reviews and changes in the late stages of the IETF process. Next week =
the IESG will be having a retreat in Dublin, Ireland. As we brought this =
topic to our agenda, Pete and I wanted to raise the issue here and call =
for feedback & ideas for improving the situation with all of you.

http://www.ietf.org/blog/2013/05/balancing-the-process/

Jari


From mcr@sandelman.ca  Wed May  1 09:34:26 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A48D121F9894 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 09:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KrfAQH4brJQS for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 09:34:25 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id BF81721F9A05 for <ietf@ietf.org>; Wed,  1 May 2013 09:34:20 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 879842016D for <ietf@ietf.org>; Wed,  1 May 2013 12:45:12 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 7CDA863A62; Wed,  1 May 2013 12:33:47 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6EDB363A61 for <ietf@ietf.org>; Wed,  1 May 2013 12:33:47 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF list <ietf@ietf.org>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
Date: Wed, 01 May 2013 12:33:47 -0400
Message-ID: <32577.1367426027@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 16:34:26 -0000

<#part sign=pgpmime>

>>>>> "Jari" == Jari Arkko <jari.arkko@piuha.net> writes:
    Jari> I wrote a blog article about how we do a fairly significant
    Jari> amount of reviews and changes in the late stages of the IETF
    Jari> process. Next week the IESG will be having a retreat in
    Jari> Dublin, Ireland. As we brought this topic to our agenda, Pete
    Jari> and I wanted to raise the issue here and call for feedback &
    Jari> ideas for improving the situation with all of you. 

    Jari> http://www.ietf.org/blog/2013/05/balancing-the-process/

I'll repeat what has been said repeatedly in the newtrk and related
discussions.  The step from ID to "RFC" is too large because we are
essentially always aiming for "STD" rather than "PS".

If we are unwilling to bring "RFC" back to a place were it does not
equal STD, then we need to create a new category of document which
amounts to "fully baked ID".  Things like IANA allocations could occur
at that point.


In the days of dot-boom it was not unusual to see widespread
implementation very early in the ID process and even interop and
experimental deployment.   While this still occurs for quite a number of
things (and sometimes it's a problem that the ID can not be changed as a
result), there is an equal amount of "wait for the RFC to come out".


I believe that we probably need to simply do less.  
Or perhaps we've reached the n^2 overhead problem, and since resources
are less(%), if we can't increase resources allocated to overhead, then
it's time to reduce n:  the IETF should fork and/or shard somehow.


(%)-it's not just about $$ invested, it's also, I think, that after
    many years of caffeine and sugar, many of us are simply 
    immune to their effects, and/or have given them up.


(2)-by adding an intermediate step in the "ID" process, I haven't
    removed the "heavy" part of the process, I've just redefined the
    process so that it's no longer at the "tail" of the process.
    This is, I admit, akin to adjusting the definition of unemployment.

    But, we can all agree when an ID is baked enough for the WG to
    consider it deployable, then we will actually get to the "running
    code" part sooner, which frankly is the only real way to get
    real experience.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	



From cabo@tzi.org  Wed May  1 09:39:24 2013
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 EDEE721F9A53 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 09:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.219
X-Spam-Level: 
X-Spam-Status: No, score=-106.219 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H2nf69+ySb67 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 09:39:19 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 74B6621F9A55 for <ietf@ietf.org>; Wed,  1 May 2013 09:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r41GdAQv023082; Wed, 1 May 2013 18:39:10 +0200 (CEST)
Received: from [192.168.217.135] (p5489335C.dip0.t-ipconnect.de [84.137.51.92]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id EFA2031F4; Wed,  1 May 2013 18:39:09 +0200 (CEST)
Subject: Re: call for ideas: tail-heavy IETF process
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <32577.1367426027@sandelman.ca>
Date: Wed, 1 May 2013 18:39:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1503)
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, 01 May 2013 16:39:25 -0000

On May 1, 2013, at 18:33, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:

> we need to create a new category of document which
> amounts to "fully baked ID"

Yes.  (I'm not sure it's a category, it might just be a stage.)

There is a stage in the development of a protocol where I no longer want =
to hear "it's just a draft, so we can change anything at will".

This would also be a good time to bring in the cross-area review.

Gr=FC=DFe, Carsten


From stpeter@stpeter.im  Wed May  1 10:11:19 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A544021F9A7C for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YeoFKfiRohTX for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:11:13 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E0EAB21F9A8A for <ietf@ietf.org>; Wed,  1 May 2013 10:11:13 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.234]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8B3AB40010; Wed,  1 May 2013 11:22:29 -0600 (MDT)
Message-ID: <51814CAF.1040307@stpeter.im>
Date: Wed, 01 May 2013 11:11:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org>
In-Reply-To: <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 01 May 2013 17:11:19 -0000

On 5/1/13 10:39 AM, Carsten Bormann wrote:
> On May 1, 2013, at 18:33, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> 
>> we need to create a new category of document which amounts to
>> "fully baked ID"
> 
> Yes.  (I'm not sure it's a category, it might just be a stage.)

Isn't that Proposed Standard?

Peter

From paul.hoffman@vpnc.org  Wed May  1 10:27:05 2013
Return-Path: <paul.hoffman@vpnc.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 EFB9E21F9A07 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MPbNLJDgS19S for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:27:05 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 913D921F99FF for <ietf@ietf.org>; Wed,  1 May 2013 10:27:05 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r41HR3IT005071 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 May 2013 10:27:04 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51814CAF.1040307@stpeter.im>
Date: Wed, 1 May 2013 10:27:03 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1503)
Cc: Carsten Bormann <cabo@tzi.org>, 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, 01 May 2013 17:27:06 -0000

On May 1, 2013, at 10:11 AM, Peter Saint-Andre <stpeter@stpeter.im> =
wrote:

> On 5/1/13 10:39 AM, Carsten Bormann wrote:
>> On May 1, 2013, at 18:33, Michael Richardson <mcr+ietf@sandelman.ca>
>> wrote:
>>=20
>>> we need to create a new category of document which amounts to
>>> "fully baked ID"
>>=20
>> Yes.  (I'm not sure it's a category, it might just be a stage.)
>=20
> Isn't that Proposed Standard?

No, it very clearly isn't. To get from "the last version of this draft" =
to "Proposed Standard" takes many months, significant involvement of an =
AD, and some involvement of all ADs. All of that has costs.

--Paul Hoffman=

From stpeter@stpeter.im  Wed May  1 10:35:36 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 177FF21F989A for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:35:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqK3AR2wtiRI for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:35:30 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 410BA21F902A for <ietf@ietf.org>; Wed,  1 May 2013 10:35:30 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.235]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 58F49E826C; Wed,  1 May 2013 11:46:46 -0600 (MDT)
Message-ID: <51815260.6000002@stpeter.im>
Date: Wed, 01 May 2013 11:35:28 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org>
In-Reply-To: <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Carsten Bormann <cabo@tzi.org>, 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, 01 May 2013 17:35:36 -0000

On 5/1/13 11:27 AM, Paul Hoffman wrote:
> On May 1, 2013, at 10:11 AM, Peter Saint-Andre <stpeter@stpeter.im>
> wrote:
> 
>> On 5/1/13 10:39 AM, Carsten Bormann wrote:
>>> On May 1, 2013, at 18:33, Michael Richardson
>>> <mcr+ietf@sandelman.ca> wrote:
>>> 
>>>> we need to create a new category of document which amounts to 
>>>> "fully baked ID"
>>> 
>>> Yes.  (I'm not sure it's a category, it might just be a stage.)
>> 
>> Isn't that Proposed Standard?
> 
> No, it very clearly isn't. To get from "the last version of this
> draft" to "Proposed Standard" takes many months, significant
> involvement of an AD, and some involvement of all ADs. All of that
> has costs.

Sorry: oughtn't that be Proposed Standard?

Peter

From hartmans@mit.edu  Wed May  1 10:44:15 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C11E21F9AB5 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P8v61MCGe1Zb for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:44:09 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 700E321F98F1 for <ietf@ietf.org>; Wed,  1 May 2013 10:44:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id BD07220407; Wed,  1 May 2013 13:41:52 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEhAuFcblhew; Wed,  1 May 2013 13:41:51 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed,  1 May 2013 13:41:51 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 585EA4499; Wed,  1 May 2013 13:44:02 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca>
Date: Wed, 01 May 2013 13:44:02 -0400
In-Reply-To: <32577.1367426027@sandelman.ca> (Michael Richardson's message of "Wed, 01 May 2013 12:33:47 -0400")
Message-ID: <tslobcuy4rh.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: 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, 01 May 2013 17:44:15 -0000

>>>>> "Michael" == Michael Richardson <mcr+ietf@sandelman.ca> writes:


    Michael> If we are unwilling to bring "RFC" back to a place were it
    Michael> does not equal STD, then we need to create a new category
    Michael> of document which amounts to "fully baked ID".  Things like
    Michael> IANA allocations could occur at that point.


Hi.  Could you clearly articulate why you want this category and what
you hope it will do and not do?  I tried to respond with my thoughts
about this but realized that I don't understand your goals well enough
to provide more than a poorly considered reaction.

From dhc@dcrocker.net  Wed May  1 11:00:21 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FBC221F9A49 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.581
X-Spam-Level: 
X-Spam-Status: No, score=-6.581 tagged_above=-999 required=5 tests=[AWL=0.018,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K797jfz9splm for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:00:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B245D21F9A20 for <ietf@ietf.org>; Wed,  1 May 2013 11:00:10 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r41I06tW032733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 1 May 2013 11:00:10 -0700
Message-ID: <5181581E.9010501@dcrocker.net>
Date: Wed, 01 May 2013 10:59:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 01 May 2013 11:00:10 -0700 (PDT)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 18:00:21 -0000

The blog nicely classes the problem as being too heavy-weight during 
final stages.  The quick discussion thread seems focused on adding a 
moment at which the draft specification is considered 'baked'.

I think that's still too late.

Certainly it could be useful, but it's still very late in the process.

Specification development usually does -- and certainly ought to -- 
formulate basic design ideas or approaches that motivate the details in 
a specification.  A good specification will include discussion of this, 
and I think the typical and most significant hashing and re-hashing that 
happens in later stages is about the design issues.

While basic design revisions can happen at any time in a process, I'll 
suggest that a specification effort should be asked to document its 
interesting design choices early, and circulate /these/ for external 
review, iterating later if basic choices are changed.

I suspect that an earlier exercise at summarizing functional goals and 
design approaches and issues will have a number of benefits, beyond 
enabling earlier external review.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From mcr@sandelman.ca  Wed May  1 11:12:03 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 498C521F96EA for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q62NWH-YEtfM for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:12:02 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 7CE6B21F940B for <ietf@ietf.org>; Wed,  1 May 2013 11:12:02 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 27CB42016D; Wed,  1 May 2013 14:22:56 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 6DE3563A62; Wed,  1 May 2013 14:11:30 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 569B563A61; Wed,  1 May 2013 14:11:30 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <tslobcuy4rh.fsf@mit.edu>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <tslobcuy4rh.fsf@mit.edu>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 01 May 2013 14:11:30 -0400
Message-ID: <18409.1367431890@sandelman.ca>
Sender: mcr@sandelman.ca
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, 01 May 2013 18:12:03 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Sam" =3D=3D Sam Hartman <hartmans-ietf@mit.edu> writes:
    Michael> If we are unwilling to bring "RFC" back to a place were it
    Michael> does not equal STD, then we need to create a new category
    Michael> of document which amounts to "fully baked ID".  Things like
    Michael> IANA allocations could occur at that point.

    Sam> Hi.  Could you clearly articulate why you want this category and w=
hat
    Sam> you hope it will do and not do?  I tried to respond with my though=
ts
    Sam> about this but realized that I don't understand your goals well en=
ough
    Sam> to provide more than a poorly considered reaction.

It's what Carsten said.

1) this idea is baked enough for cross-area review to make sense.
2) the protocol is not going to change significantly, one could
   implement.
3) any future changes need thus to take into account impact on
   existing implementations... BUT that doesn't mean that we can't
   change things.

It's what PS *ought* to have been, and what "RFC"s were prior to
1990 or so.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUYFa0oqHRg3pndX9AQJ2lwQA1LBeomf1eHJrrYRvTsnKZaHort4OIeT3
ucckGP4vtdvH2p3oAhCaIpQpnim1Q+Dn+eKMNV+5k5HwTKdAfUdC5vUiauNaimEz
eivVLC8VUVckhL+E9lVTuFU2oQD1RJFmrbbfOSQqV1BpU0i8VN8pIX+BbB5wHAzQ
ah9L1LjyMvA=
=ssMv
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Wed May  1 11:17:03 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE8221F9840 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:17:03 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hl4b1rIEleUf for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:16:58 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id C0B4321F9633 for <ietf@ietf.org>; Wed,  1 May 2013 11:16:58 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 4B6872016D for <ietf@ietf.org>; Wed,  1 May 2013 14:27:51 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id D85DC63A62; Wed,  1 May 2013 14:16:25 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C737563A61 for <ietf@ietf.org>; Wed,  1 May 2013 14:16:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF list <ietf@ietf.org>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <5181581E.9010501@dcrocker.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 01 May 2013 14:16:25 -0400
Message-ID: <19317.1367432185@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 18:17:04 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Dave" =3D=3D Dave Crocker <dhc@dcrocker.net> writes:
    Dave> I think that's still too late.

    Dave> Certainly it could be useful, but it's still very late in the
    Dave> process.=20

It's too late for Internet Changing Things (BGP4, TCP, IPv6 Header Options)=
..

It's still too early for things we know little about
(SPF, IPsecME AD VPN, all the LLN stuff)..=20

just to name a few, there are lots of examples I know.

The problem is partly that we apply the same process regardless of
impact... The review is therefore too late for Internet Changing Things,
and way to heavy for new things that are more self-contained.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUYFb+YqHRg3pndX9AQJMXQP6A6jaek3yuHibX5av+bXnn2YsLI+85YkA
aDx8sWsvw4qS486vgLJ529PnOYd9b4xwRi6COGeB8A1FA4m1PHQMVHJQLS7q9zju
mbwt1vODBqNQu1UrUfp8lCyZLXEjoT+MjrBhpqblWIO2uFOdgVVaykzWYYCpjIpT
gHCqhHnakDc=
=AsqP
-----END PGP SIGNATURE-----
--=-=-=--

From hartmans@mit.edu  Wed May  1 11:19:46 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1DBF21F9AD6 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:19:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBOwf6rOdhxx for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 11:19:40 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 2105621F9AD0 for <ietf@ietf.org>; Wed,  1 May 2013 11:19:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 59EA020409; Wed,  1 May 2013 14:17:28 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EoZrLQu15MEr; Wed,  1 May 2013 14:17:27 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed,  1 May 2013 14:17:27 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 905FF4499; Wed,  1 May 2013 14:19:38 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <tslobcuy4rh.fsf@mit.edu> <18409.1367431890@sandelman.ca>
Date: Wed, 01 May 2013 14:19:38 -0400
In-Reply-To: <18409.1367431890@sandelman.ca> (Michael Richardson's message of "Wed, 01 May 2013 14:11:30 -0400")
Message-ID: <tslli7yv9z9.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: Sam Hartman <hartmans-ietf@mit.edu>, 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, 01 May 2013 18:19:46 -0000

OK.


>1) this idea is baked enough for cross-area review to make sense.
>2) the protocol is not going to change significantly, one could
>   implement.
>3) any future changes need thus to take into account impact on
>   existing implementations... BUT that doesn't mean that we can't
>   change things.

I'm very nervous about changes to the process of this form.

I'd support doing this sort of categorization as an advisory label.
For example if people wanted to get together and somehow track what
documents were fully baked as a service to the community and see how
useful it was, I'd support that.

I am strongly against making something like this a formal part of the
process without something informal like that first and without
significant experience with the informal something.

From abdussalambaryun@gmail.com  Wed May  1 12:03:13 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32EA221F9737 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:03:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.974
X-Spam-Level: 
X-Spam-Status: No, score=-1.974 tagged_above=-999 required=5 tests=[AWL=0.625,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mY-QJwsbrIsk for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:03:12 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF1221F9AEA for <ietf@ietf.org>; Wed,  1 May 2013 12:02:49 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id xa7so865833pbc.19 for <ietf@ietf.org>; Wed, 01 May 2013 12:02:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=X5GXrjaO+A+XHWnaWLcizId941FKYqInaV+cTZh0L0E=; b=TXGMBsGDECu7w1Edh+ncVB5mUV1JHhokldJh4B61abN38geneSc06S6ieHCjZOXesl T/Sk5fHNL04ULMNq5orR1Y1niA3QmNOp3hMjpBED4ZWCFsnlvbuzfafJZ52QIan4jn2S vqrtZ4eKKJEEZpsByemjDMb43JYBTlwla6GEvLEVLTe+AJ26VJ2+AIL4ybTWU37e+zzj ng9Woy46AXF0oKHa3WEuvg87k7SR/5clG7zteSsHGEiljVRGbsD44t4GnpkjJzumW9qB HNLEwGIAyADBOMzLHKbsJe1+71HW0S5K2noFNKYLCNqQhIynf0yuelxSWPSHYSYXUiGP xURQ==
MIME-Version: 1.0
X-Received: by 10.66.74.170 with SMTP id u10mr6299371pav.202.1367434968973; Wed, 01 May 2013 12:02:48 -0700 (PDT)
Received: by 10.68.230.35 with HTTP; Wed, 1 May 2013 12:02:48 -0700 (PDT)
Date: Wed, 1 May 2013 20:02:48 +0100
Message-ID: <CADnDZ88LZXkjDB7dvZcFgrM4Co9cf=u+az0Ow4Ds6R1vyEy2bQ@mail.gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "jari.arkko@piuha.net" <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=f46d042e006b944b6104dbacc31a
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, 01 May 2013 19:03:13 -0000

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

Hi Jari,

Thanks for the blog, and I agree with it. My ideas are below and sorry if
not short,

 I may not have the full solution because never met participants in
meeting, but I think the source of the problem is as follows:
1- Many technical people feel better to discuss face to face (f2f) than
discuss on the list, so many decisions still not discussed well on the list.
2- Editors do most of their work off-line, which is not right IMO. Editors
mostly feel they own the WG I-D and they can edit without WG objection, but
if one participant objects, they say no one supports you.
3- ADs review the I-D which they communicate with their WG, but not much
summary to the community in the IETF Last Call. Why not the AD describes
the I-D to community to make more people involved to *review* or *use*.
4- Participant only join a review if interested, but who will do the effort
to make other areas or WGs interested.
5-Are the WGs of same Area working as a team, and do they thing the I-Ds
produced have interaction, or is it only the ADs that should think of these
things.
6- Usually participants are bussy so they may not got time to review, but
hopefully the WG chairs do review or find who can.
7- When reviewer comments to IESG, there is no much reflect/reply from the
same body which can be seen, was the comments received?
8- Many meetings in IETF not managed well. I think that it needs time
management that serve WG milstones. Some chairs don't mention milestones in
every meeting for discussion.

The *solutions*, may be but I am not sure it can *work*, (we may need some
one that knows the culture, or who can change it):

1- WGs Chairs and ADs should find ways to reduce repeated work done, should
encourage participants (sometimes discouraged to review because no follow
ups).
2- Use the IETF tracker tools to attach discussions to I-Ds. Most
discussions are lost into translation or location or bussiness.
3- You need to acknowledge participants efforts. IMHO, it is strange that
someone edits a draft for the WG and does not acknowledge efforts, then why
is this organisation named IETF. What makes it worse is that thoes efforts
are volunteering, so is it difficult to acknowledge few reviewers. Only if
you have more than 10 reviewers you may excuse by writting *thanks to the
WG*, how can editors thank the WG while only few participated.
4- Some Chairs don't give enough time/discussion for new I-D reviews (this
is difficult task that the chair should try to know when is enough), if
someone request to get more time, it is very easy to say there was no
consensus of one objection. If editors have a tiny point they are able to
make their thoughts through I-D without consensus.
5- The milestones of the WGs charters MUST be discussed, followed or
updated. All meetings should include milestones discussions. I think it is
not much followed/updated (slow to change). If we have slow progress to
milestones then we are progressing slowly not efficiently. Slow is not bad
but not having clear/presented future objectives is.
6- The IESG should mention the input comments they got in their evaluation
discussion of the I-D. IESG calls for reviews but does not reflect to
comments or to the general comments recieved. I see that only the authors
of the I-D commenting on my review to IESG, which I think is wrong. If
participants comments are not in the evaluation discussion why is the
effort done.

Best Regards
AB

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

<div dir=3D"ltr"><div>Hi Jari,</div><div>=A0</div><div>Thanks for the blog,=
 and I agree with it. My ideas are below and sorry if not short,</div><div>=
=A0</div><div>=A0I may not have the full solution because never met partici=
pants in meeting, but I think the source of the problem is as follows:</div=
>
<div>1- Many technical people feel better to discuss face to face (f2f) tha=
n discuss on the list, so many decisions still not discussed well on the li=
st.</div><div>2- Editors do most of their work off-line, which is not right=
 IMO. Editors mostly feel they own the WG I-D and they can edit without WG =
objection, but if one participant objects, they say no one supports you.</d=
iv>
<div>3- ADs review the I-D which they communicate with their WG, but not mu=
ch summary to the community in the IETF Last Call. Why not the AD describes=
 the I-D to community to make more people involved to *review* or *use*.</d=
iv>
<div>4- Participant only join a review if interested, but who will do the e=
ffort to make other areas or WGs interested.</div><div>5-Are the WGs of sam=
e Area working as a team, and do they thing the I-Ds produced have interact=
ion, or is it only the ADs that should think of these things.</div>
<div>6- Usually participants are bussy so they may not got time to review, =
but hopefully the WG chairs do review or find who can.</div><div>7- When re=
viewer comments to IESG, there is no much reflect/reply from the same body =
which can be seen, was the=A0comments received?</div>
<div>8- Many meetings in IETF not managed well. I think that it needs time =
management that serve WG milstones. Some chairs don&#39;t mention milestone=
s in every meeting for discussion.</div><div>=A0</div><div>The *solutions*,=
 may be but I am not sure it can *work*, (we may need some one that knows t=
he culture, or who can change it):</div>
<div>=A0</div><div>1- WGs Chairs and ADs should find ways to reduce repeate=
d work done, should encourage participants (sometimes=A0discouraged to revi=
ew because no follow ups).</div><div>2- Use the=A0IETF tracker tools to att=
ach discussions to I-Ds. Most discussions are lost into translation or loca=
tion or bussiness.</div>
<div>3- You need to acknowledge participants efforts. IMHO, it is strange t=
hat someone edits a draft for the WG and does not acknowledge efforts, then=
 why is this organisation named IETF. What makes it worse is that thoes eff=
orts are volunteering, so is it difficult to acknowledge few reviewers. Onl=
y if you have more than 10 reviewers you may excuse by writting *thanks to =
the WG*, how can editors thank the WG while only few participated.</div>
<div><div>4- Some Chairs don&#39;t give enough time/discussion for new I-D =
reviews (this is difficult task that the chair should try to know when is e=
nough), if someone request to get more time, it is very easy to say there w=
as no consensus of one objection. If editors have a tiny point they are abl=
e to make their thoughts through I-D without consensus.</div>
<div>5- The milestones of the WGs charters MUST be=A0discussed, followed or=
 updated. All meetings should include milestones discussions.=A0I think it =
is not much followed/updated (slow to change). If we have slow progress to =
milestones then we are progressing slowly not efficiently. Slow is not bad =
but not having clear/presented future objectives is.</div>
<div>6- The IESG should mention the input comments they got in their evalua=
tion discussion of the I-D. IESG calls for reviews but does=A0not reflect t=
o comments or to the general comments recieved. I see that only the authors=
 of the I-D commenting on my review to IESG, which I think is wrong.=A0If p=
articipants comments are not in the evaluation discussion why is the effort=
 done.</div>
</div><div>=A0</div><div>Best Regards</div><div>AB</div><div>=A0</div><div>=
=A0</div><div>=A0</div><div>=A0</div><div>=A0</div></div>

--f46d042e006b944b6104dbacc31a--

From sm@resistor.net  Wed May  1 12:21:04 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5EC21F9A2F for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G5LROJRw6qVK for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:21:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A7B21F9A2A for <ietf@ietf.org>; Wed,  1 May 2013 12:21:02 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r41JKtCS008574; Wed, 1 May 2013 12:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367436061; bh=5yKpUDLl3hVy8cRhdKa8L9M0ojJt03w/NkbUPAEo4Ls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Bp1e4WkhgAP6WWb7HdqcsyD0UX/v9Eu+PttOwjknubKIj2jEKjuMKceVFbtp9bgBT dYyWnDI+7KjlKkLJlYhlNjnSr+pSYh88tEsrdozDA70V219YmyHoeaJdLbf5XpzlzZ mbrOWQuPUH4wY5/Auld7UZ3ZROkX0I8VObTqigBE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367436061; i=@resistor.net; bh=5yKpUDLl3hVy8cRhdKa8L9M0ojJt03w/NkbUPAEo4Ls=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xokT40KTSAwxrMNIK3vRp04nvqkgxGkNp8bc2eG3vEEMjmflIcQ5JR9ZC5vwh3lG3 27ciIUdk/D5ifp0segiYjMO8dgNbA8S1/du/ucrAaP7CQoDV6wJiv8X5xQ/QmSSbpB 236MFTWZTq6ldJBm/eb+TlOrriHmdQTet37wx5lU=
Message-Id: <6.2.5.6.2.20130501102120.0c7fbec0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 May 2013 12:19:15 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 19:21:04 -0000

At 08:33 01-05-2013, Jari Arkko wrote:
>I wrote a blog article about how we do a fairly significant amount 
>of reviews and changes in the late stages of the IETF process. Next 
>week the IESG will be having a retreat in Dublin, Ireland. As we 
>brought this topic to our agenda, Pete and I wanted to raise the 
>issue here and call for feedback & ideas for improving the situation 
>with all of you.
>
>http://www.ietf.org/blog/2013/05/balancing-the-process/

Here's my write-up:

  (a) Why should the document be a Proposed Standard?

      Because the intended status says so.

  (b) Describe the depth and breath of review.

      Yes.

  (c) Does the document require review from other areas?

      No.

  (d) Describe the consensus.

      Yes.  I ignored the stupid comments.

There IESG is faced with the inevitable choice of either turning a 
blind eye or discussing about the document.  The later raises late 
surprises.  The simple fix is for the IESG not to discuss about the 
document. :-)  The not-so-simple fix is for the IESG to find out 
where the WG failure occurred and take remedial action.  It's 
politically incorrect to fire WG Chairs.  That constrains the 
remedial action to a slap on the wrist [1].

Who is going to do all these early cross-area reviewing?  Is all that 
work for free?

The executive summary is that the working group is not working.  The 
Last Call does not work.  The directorate/team reviews is a 
work-around [2] to fix that.

Regards,
-sm

1. If someone gives you a slap on the wrist, it is a mild punishment.
2. a plan or method to circumvent a problem without eliminating it. 


From cabo@tzi.org  Wed May  1 12:33:01 2013
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 8878721F9A56 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:33:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.221
X-Spam-Level: 
X-Spam-Status: No, score=-106.221 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHdtLQgscRj6 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:32:55 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 2BEF921F9AF2 for <ietf@ietf.org>; Wed,  1 May 2013 12:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r41JWmeE022815; Wed, 1 May 2013 21:32:48 +0200 (CEST)
Received: from [192.168.217.135] (p5489335C.dip0.t-ipconnect.de [84.137.51.92]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 11F6632CF; Wed,  1 May 2013 21:32:48 +0200 (CEST)
Subject: Re: call for ideas: tail-heavy IETF process
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <18409.1367431890@sandelman.ca>
Date: Wed, 1 May 2013 21:32:45 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E1FBBB9-852D-4749-B246-B59C17F61928@tzi.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <tslobcuy4rh.fsf@mit.edu> <18409.1367431890@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1503)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, 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, 01 May 2013 19:33:01 -0000

On May 1, 2013, at 20:11, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:

> It's what PS *ought* to have been, and what "RFC"s were prior to
> 1990 or so.

One problem is certainly the cognitive barrier imposed by the RFC =
process.
-- RFCs never change, so you want to get them right;
-- there is a two-month editorial process in front of the publication;
etc. etc.

So I don't think changing the process leading up to the RFCs is really =
going to change that much.

Having a label for a "baked" I-D, maybe some publicly visible directory =
for them, but retaining the I-D's fast change capability for editorial =
changes (and fixes that turn out to be necessary), would work better.

I also like what Sam said: Try this out first as an informal addendum to =
what we have and what works.

Gr=FC=DFe, Carsten


From kathleen.moriarty@emc.com  Wed May  1 12:41:55 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10F9721F96FA for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNJvaMGGatea for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:41:49 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id C121221F96B4 for <ietf@ietf.org>; Wed,  1 May 2013 12:41:48 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r41JflgP003116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 May 2013 15:41:47 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 1 May 2013 15:41:27 -0400
Received: from mxhub13.corp.emc.com (mxhub13.corp.emc.com [128.222.70.234]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r41JfQax017026; Wed, 1 May 2013 15:41:26 -0400
Received: from mx15a.corp.emc.com ([169.254.1.81]) by mxhub13.corp.emc.com ([128.222.70.234]) with mapi; Wed, 1 May 2013 15:41:26 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Carsten Bormann <cabo@tzi.org>, Michael Richardson <mcr+ietf@sandelman.ca>
Date: Wed, 1 May 2013 15:41:25 -0400
Subject: RE: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: Ac5GovaS8jkO/tzcT1e8/IvpMlQSDQAAIt2A
Message-ID: <F5063677821E3B4F81ACFB7905573F24DAA99C3B@MX15A.corp.emc.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <tslobcuy4rh.fsf@mit.edu> <18409.1367431890@sandelman.ca> <0E1FBBB9-852D-4749-B246-B59C17F61928@tzi.org>
In-Reply-To: <0E1FBBB9-852D-4749-B246-B59C17F61928@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: Sam Hartman <hartmans-ietf@mit.edu>, 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, 01 May 2013 19:41:55 -0000

How about having a running list (or registry) of IETF RFCs that have become=
 the "de-facto" standards? =20

Best regards,
Kathleen

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Car=
sten Bormann
Sent: Wednesday, May 01, 2013 3:33 PM
To: Michael Richardson
Cc: Sam Hartman; IETF list
Subject: Re: call for ideas: tail-heavy IETF process

On May 1, 2013, at 20:11, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

> It's what PS *ought* to have been, and what "RFC"s were prior to
> 1990 or so.

One problem is certainly the cognitive barrier imposed by the RFC process.
-- RFCs never change, so you want to get them right;
-- there is a two-month editorial process in front of the publication;
etc. etc.

So I don't think changing the process leading up to the RFCs is really goin=
g to change that much.

Having a label for a "baked" I-D, maybe some publicly visible directory for=
 them, but retaining the I-D's fast change capability for editorial changes=
 (and fixes that turn out to be necessary), would work better.

I also like what Sam said: Try this out first as an informal addendum to wh=
at we have and what works.

Gr=FC=DFe, Carsten



From mcr@sandelman.ca  Wed May  1 12:58:42 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CFFE21F99B3 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:58:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DnwCniffzlV for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 12:58:41 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id C552A21F99A4 for <ietf@ietf.org>; Wed,  1 May 2013 12:58:41 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 779DC2016D; Wed,  1 May 2013 16:09:34 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id D802763A62; Wed,  1 May 2013 15:58:08 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C7D3C63A61; Wed,  1 May 2013 15:58:08 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DAA99C3B@MX15A.corp.emc.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <tslobcuy4rh.fsf@mit.edu> <18409.1367431890@sandelman.ca> <0E1FBBB9-852D-4749-B246-B59C17F61928@tzi.org> <F5063677821E3B4F81ACFB7905573F24DAA99C3B@MX15A.corp.emc.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 01 May 2013 15:58:08 -0400
Message-ID: <5701.1367438288@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Carsten Bormann <cabo@tzi.org>, Sam Hartman <hartmans-ietf@mit.edu>, 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, 01 May 2013 19:58:42 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Moriarty," =3D=3D Moriarty, Kathleen <kathleen.moriarty@emc.com> wri=
tes:
    Moriarty> How about having a running list (or registry) of IETF RFCs
    Moriarty> that have become the "de-facto" standards?=20=20=20=20

So, the STD series is pretty exactly this.

Newtrk also proposed more than one level of this.

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUYFz0IqHRg3pndX9AQIEEAP9Ed1/32RKnDcvGx2+k51Qes+lWwx2O9zx
15BuHecqYU1wLcuJA9eNyaT7lkvcrj0jpiC+RsV2zjWagd3fWw71IkK1Jf6z1Tc6
+qi05L2XcQxG67SFHM4bzlT/V2z/Utik/SdL4gKYDDG+KGPLWXQnCRdGLYDU3JXQ
gKn/g1HTHVg=
=8Ur+
-----END PGP SIGNATURE-----
--=-=-=--

From brian.e.carpenter@gmail.com  Wed May  1 13:05:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8B4221F9ADD for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 13:05:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ikhI02is+D8 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 13:05:32 -0700 (PDT)
Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) by ietfa.amsl.com (Postfix) with ESMTP id 871B321F9ACD for <ietf@ietf.org>; Wed,  1 May 2013 13:05:32 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id g10so974266pdj.34 for <ietf@ietf.org>; Wed, 01 May 2013 13:05:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2j49e4XPd45OjK8UtJr/w3a/TqKz1CgwRaBP5EuNPtQ=; b=qohHn9XBWukwazfC0/6m2fAD1AZos6NpaCrbphLZvXPISrNtKVXT/t8zAIw5lkOTE1 Fihcp5TnzZHHINiTlOSyHb6Y4wHaPFoG0YOWhf6HpD4DlzIB3EPnqxeIZFTmc7/D/pk4 Y7Kwx0/3KbJkh7wE77gHQKi886r3pc/M4NIK6F43CW8I6Moqq7t7m4D1UY+QTpBBLFuY XW6Ljd5Xdcr8yJAgkIMNFpAAXsgqQK93c87noEoq24Kt6lWJDdrlADTsctwDWGGVDn9B 6Qf7z7wWPJqXGpEnovQw6SemCtKesZhZ6mQri2iNwnFf4Xi+ivd2mos8aoEp8DyjIaxw Estg==
X-Received: by 10.68.164.33 with SMTP id yn1mr5710334pbb.71.1367438732299; Wed, 01 May 2013 13:05:32 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id cp1sm4114390pbc.42.2013.05.01.13.05.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 May 2013 13:05:31 -0700 (PDT)
Message-ID: <5181758E.5070008@gmail.com>
Date: Thu, 02 May 2013 08:05:34 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net>
In-Reply-To: <5181581E.9010501@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 01 May 2013 20:05:40 -0000

On 02/05/2013 05:59, Dave Crocker wrote:
> 
> The blog nicely classes the problem as being too heavy-weight during
> final stages.  The quick discussion thread seems focused on adding a
> moment at which the draft specification is considered 'baked'.
> 
> I think that's still too late.

What, you agree with your younger self?

http://tools.ietf.org/html/draft-carpenter-icar-sirs-01

Apart from the non-diverse acronym, I still think that proposal
was a good one.

    Brian

From dhc@dcrocker.net  Wed May  1 13:17:37 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D7021F99D8 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 13:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level: 
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id avxR0gBOwsfM for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 13:17:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7985421F99A9 for <ietf@ietf.org>; Wed,  1 May 2013 13:17:33 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r41KHRFS004033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 1 May 2013 13:17:30 -0700
Message-ID: <51817843.2000702@dcrocker.net>
Date: Wed, 01 May 2013 13:17:07 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com>
In-Reply-To: <5181758E.5070008@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 01 May 2013 13:17:30 -0700 (PDT)
Cc: dcrocker@bbiw.net, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 May 2013 20:17:37 -0000

On 5/1/2013 1:05 PM, Brian E Carpenter wrote:
> On 02/05/2013 05:59, Dave Crocker wrote:
>>
>> The blog nicely classes the problem as being too heavy-weight during
>> final stages.  The quick discussion thread seems focused on adding a
>> moment at which the draft specification is considered 'baked'.
>>
>> I think that's still too late.
>
> What, you agree with your younger self?
>
> http://tools.ietf.org/html/draft-carpenter-icar-sirs-01

I really dislike being consistent, and always have.


> Apart from the non-diverse acronym, I still think that proposal
> was a good one.

Me too.  Could be interesting to, ummmm, review it for updating...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From swb@internet2.edu  Wed May  1 14:00:26 2013
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 16EB021F9AF8 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.307
X-Spam-Level: 
X-Spam-Status: No, score=-7.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GRDR7Un61-Q8 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:00:19 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id C12A421F9AF2 for <ietf@ietf.org>; Wed,  1 May 2013 14:00:16 -0700 (PDT)
Received: from mail62-co9-R.bigfish.com (10.236.132.235) by CO9EHSOBE006.bigfish.com (10.236.130.69) with Microsoft SMTP Server id 14.1.225.23; Wed, 1 May 2013 21:00:16 +0000
Received: from mail62-co9 (localhost [127.0.0.1])	by mail62-co9-R.bigfish.com (Postfix) with ESMTP id 255B9A2033E	for <ietf@ietf.org>; Wed,  1 May 2013 21:00:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.85; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0811HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 14
X-BigFish: S14(zzzz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h93fhe5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1889i1724k1b1cn1b1bi1155h)
Received: from mail62-co9 (localhost.localdomain [127.0.0.1]) by mail62-co9 (MessageSwitch) id 1367442014408181_9434; Wed,  1 May 2013 21:00:14 +0000 (UTC)
Received: from CO9EHSMHS002.bigfish.com (unknown [10.236.132.253])	by mail62-co9.bigfish.com (Postfix) with ESMTP id 6178FA00048	for <ietf@ietf.org>; Wed,  1 May 2013 21:00:14 +0000 (UTC)
Received: from CH1PRD0811HT003.namprd08.prod.outlook.com (157.56.245.85) by CO9EHSMHS002.bigfish.com (10.236.130.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 1 May 2013 21:00:13 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.155.38) with Microsoft SMTP Server (TLS) id 14.16.305.3; Wed, 1 May 2013 21:00:11 +0000
Message-ID: <51818258.6000303@internet2.edu>
Date: Wed, 1 May 2013 17:00:08 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
CC: IETF list <ietf@ietf.org>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com>
In-Reply-To: <5181758E.5070008@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.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, 01 May 2013 21:00:26 -0000

A draft does get cross-area review, at least once, often more than once.
 Some drafts in some WGs get it earlier than others, by explicit
invitation.  Others don't get it until the latest they can, when they go
to last call ... but a process point for cross-area review during WG
handling, already exists.  It's just optional.  I did like SIRS, and the
equivalent of SIRS exists -- in the informal relationships that are all
through the IETF.

You can make the option more explicit, you could even make it mandatory,
but doing so won't speed up draft processing at all and will probably
make it slower.  One of the IETF's problems is not the problem under
discussion but unconscious assumptions about the standards process.
People think of last call as near the end of the process.  It's time to
abandon that outdated view and recognize that so-called "last" call is
not as close to the end as it used to be, that it's a bit closer to the
middle ... and that that's really okay.  Really.  Some other SDOs have
their process structured that way.  Let's rename "last call" to
something like "IETF review" and stop giving people the wrong
expectations.  Review outside the WG is vital, can be done repeatedly,
and must be done by the whole IETF at least once.

Scott



From Ted.Lemon@nominum.com  Wed May  1 14:10:54 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07F4A21F9B21 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:10:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYpIYcURS1-Y for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:10:46 -0700 (PDT)
Received: from exprod7og113.obsmtp.com (exprod7og113.obsmtp.com [64.18.2.179]) by ietfa.amsl.com (Postfix) with ESMTP id 7F28221F9B27 for <ietf@ietf.org>; Wed,  1 May 2013 14:10:46 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob113.postini.com ([64.18.6.12]) with SMTP ID DSNKUYGE1ptyqGHPrU4y7YfI9P4WT8a+tMb6@postini.com; Wed, 01 May 2013 14:10:46 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 00F6A1B8177 for <ietf@ietf.org>; Wed,  1 May 2013 14:10:46 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id EC924190061; Wed,  1 May 2013 14:10:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 1 May 2013 14:10:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Scott Brim <swb@internet2.edu>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pjxE7gAgAAjGACAAA8/AIAAAveA
Date: Wed, 1 May 2013 21:10:45 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077516B8B5@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com> <51818258.6000303@internet2.edu>
In-Reply-To: <51818258.6000303@internet2.edu>
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: <1606BEEBDAFC4F409904754C00A2FFF7@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 01 May 2013 21:10:55 -0000

On May 1, 2013, at 5:00 PM, Scott Brim <swb@internet2.edu> wrote:
> Let's rename "last call" to
> something like "IETF review" and stop giving people the wrong
> expectations.  Review outside the WG is vital, can be done repeatedly,
> and must be done by the whole IETF at least once.

Yup.   The term "last call" is traditional, and I feel a bit of attachment =
to it, but I think your observation here is exactly correct: we ought not t=
o think of the IETF last call as the end of the process.

However, that is a bit of a problem, because I think it's fairly rare for d=
ocuments to get additional "review" at last call time.   Changing the name =
probably won't fix that.


From rdroms.ietf@gmail.com  Wed May  1 14:43:26 2013
Return-Path: <rdroms.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 1C09121F9B4C for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6G7rgslXPJzq for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:43:25 -0700 (PDT)
Received: from mail-qc0-x22e.google.com (mail-qc0-x22e.google.com [IPv6:2607:f8b0:400d:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id EAD2821F9B49 for <ietf@ietf.org>; Wed,  1 May 2013 14:43:24 -0700 (PDT)
Received: by mail-qc0-f174.google.com with SMTP id z24so881937qcq.19 for <ietf@ietf.org>; Wed, 01 May 2013 14:43:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=5Pgbt162SnIFuvwTeuVylEnzXf13Gw+ibehW2HU143I=; b=vUSo3UyULy0zRMOsIHkCtE54VPXxC7PbCjIwInZQcHIsBDeRe0YzVvhakr47wsmqlB biLQMbAl+G/vvh7zXopn2Mh/ApahjPeESLBvcwK16qWo662+nWSsFPz6b+dA/wFoYMhZ mUQZUPCha/RqW+G0knmb499GrcJdpzIAjlUGTt0CtuYU0ychkktuTNK6Ihe8D40GM6SW pSUZHL2A+dAkRVJk8fYGNlzInmHrb07uTp7XxxFgUb4y0sXmlLMofjtEe4jFF1j+yBzL on/gKfNrzAnnpKSVQebjuaSLEw84Rz5VhdAj5mbz6ar+gmxCc6Vys7fUmsD0mVO8MLsN eAwQ==
X-Received: by 10.224.3.135 with SMTP id 7mr5502351qan.10.1367444604058; Wed, 01 May 2013 14:43:24 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:f498:2d88:9574:c7d? ([2001:420:2481:20:f498:2d88:9574:c7d]) by mx.google.com with ESMTPSA id m8sm7326093qav.8.2013.05.01.14.43.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 May 2013 14:43:23 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <5181581E.9010501@dcrocker.net>
Date: Wed, 1 May 2013 17:43:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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, 01 May 2013 21:43:26 -0000

On May 1, 2013, at 1:59 PM 5/1/13, Dave Crocker <dhc@dcrocker.net> =
wrote:

>=20
> The blog nicely classes the problem as being too heavy-weight during =
final stages.  The quick discussion thread seems focused on adding a =
moment at which the draft specification is considered 'baked'.
>=20
> I think that's still too late.

...and not useful unless the diverse review and changes to the document =
take place much earlier in the process to make sure the document is =
"baked."  Declaring done doesn't make it so.

>=20
> Certainly it could be useful, but it's still very late in the process.

As Jari wrote, we often bury the heavy tail of the process in a limited =
discussion among IESG and the document authors.

The tail is heavy in two different ways:

* significant review and modification takes place in IESG review, after =
the WG and the IETF have declared the document done
* the burden of the review, managing the discussion, making sure any =
changes fix the problem and don't break anything else often falls on the =
IESG and even a single AD

>=20
> Specification development usually does -- and certainly ought to -- =
formulate basic design ideas or approaches that motivate the details in =
a specification.  A good specification will include discussion of this, =
and I think the typical and most significant hashing and re-hashing that =
happens in later stages is about the design issues.
>=20
> While basic design revisions can happen at any time in a process, I'll =
suggest that a specification effort should be asked to document its =
interesting design choices early, and circulate /these/ for external =
review, iterating later if basic choices are changed.
>=20
> I suspect that an earlier exercise at summarizing functional goals and =
design approaches and issues will have a number of benefits, beyond =
enabling earlier external review.

Dave - excellent idea.  A summary that explains the "why" first, that =
promotes early cross-area review or otherwise expands the set of people =
that look at and understand the nature of the problem and the structure =
of the specification will allow for earlier review and lighter-weight =
correction of problems.

>=20
> d/

- Ralph

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


From rdroms.ietf@gmail.com  Wed May  1 14:47:22 2013
Return-Path: <rdroms.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 11FBE21F9B20 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.6
X-Spam-Level: 
X-Spam-Status: No, score=-103.6 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, GB_I_INVITATION=-2, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VeRnCbN+1xSI for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 14:47:21 -0700 (PDT)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 79BAE21F9B17 for <ietf@ietf.org>; Wed,  1 May 2013 14:47:21 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id hg5so1008338qab.4 for <ietf@ietf.org>; Wed, 01 May 2013 14:47:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=rjsZ0o4BuHNgplcx+8YSSGeibQi+P/2zLNFpjmdOGmU=; b=s9dJ6l9mJUqar+n8/CH1ESdWvkMz66fyKrzTWqV+8iOi6OIWH2E1Oh8Q47lXZQmG9A 4U/3f7ZpDPwdVIrpgRChHC3AdTPLCxHMOh4ms7Nu5eo1H9gH5ukCA1NS+n8mqJfDTqt0 x7t1eQiKuwYq49Ujz8HFrP0853JKFhq95zyQujuQi6MmEE7+QBkVIfSxJYb0VgLODr5k WF8VLbjfArN5Wba5okdGh+iHKtU3hMPXdDXWjn9L7FETckiIl53z6/xUFN+oznbxD29s mDmtSENHWYKsZB8txukdUism2JTXJBa1cLsq2mXM8ZnFMFHRM/3RRcv0uJWoYOgsVl6k 2R2g==
X-Received: by 10.229.0.199 with SMTP id 7mr1693856qcc.141.1367444840866; Wed, 01 May 2013 14:47:20 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:f498:2d88:9574:c7d? ([2001:420:2481:20:f498:2d88:9574:c7d]) by mx.google.com with ESMTPSA id i5sm7485355qaf.0.2013.05.01.14.47.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 May 2013 14:47:19 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <51818258.6000303@internet2.edu>
Date: Wed, 1 May 2013 17:47:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <855FF13B-7E85-443A-ACE0-CA10B348C4F9@gmail.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com> <51818258.6000303@internet2.edu>
To: Scott Brim <swb@internet2.edu>
X-Mailer: Apple Mail (2.1503)
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, 01 May 2013 21:47:22 -0000

On May 1, 2013, at 5:00 PM 5/1/13, Scott Brim <swb@internet2.edu> wrote:

> A draft does get cross-area review, at least once, often more than =
once.
> Some drafts in some WGs get it earlier than others, by explicit
> invitation.  Others don't get it until the latest they can, when they =
go
> to last call ... but a process point for cross-area review during WG
> handling, already exists.  It's just optional.  I did like SIRS, and =
the
> equivalent of SIRS exists -- in the informal relationships that are =
all
> through the IETF.
>=20
> You can make the option more explicit, you could even make it =
mandatory,
> but doing so won't speed up draft processing at all and will probably
> make it slower.  One of the IETF's problems is not the problem under
> discussion but unconscious assumptions about the standards process.
> People think of last call as near the end of the process.  It's time =
to
> abandon that outdated view and recognize that so-called "last" call is
> not as close to the end as it used to be, that it's a bit closer to =
the
> middle ... and that that's really okay.  Really.  Some other SDOs have
> their process structured that way.  Let's rename "last call" to
> something like "IETF review" and stop giving people the wrong
> expectations.  Review outside the WG is vital, can be done repeatedly,
> and must be done by the whole IETF at least once.

At the same time, we have to emphasize that "IETF review" means "a =
significant group of people have to look at this document really, really =
carefully to make sure it's right and report the results of their =
review".  It doesn't mean "well, it looks OK and the IESG is going to =
give a really, really careful review anyway so I don't need to worry =
about it".

Perhaps some of the directorate reviews ought to happen much earlier in =
the process?

>=20
> Scott

- Ralph

>=20
>=20


From elwynd@dial.pipex.com  Wed May  1 15:13:44 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A16E21F9B21 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 15:13:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6S2OXd4hkh3U for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 15:13:39 -0700 (PDT)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by ietfa.amsl.com (Postfix) with ESMTP id 165CF21F9B0E for <ietf@ietf.org>; Wed,  1 May 2013 15:13:38 -0700 (PDT)
X-Trace: 566464312/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/81.187.254.249/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 81.187.254.249
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEEAOqSgVFRu/75/2dsb2JhbABSgz6DN7tpgRKDEwEBBR0GFToCBAEQCxgCAgUWCwICCQMCAQIBRQYNAQcBAYgMCK5HkEeBI41/B4I/gRMDlymBJoRbizCDDg
X-IronPort-AV: E=Sophos;i="4.87,591,1363132800"; d="scan'208";a="566464312"
X-IP-Direction: OUT
Received: from weee-pc2.folly.org.uk (HELO [81.187.254.249]) ([81.187.254.249]) by smtp.pipex.tiscali.co.uk with ESMTP; 01 May 2013 23:13:32 +0100
Message-ID: <5181938C.9090005@dial.pipex.com>
Date: Wed, 01 May 2013 23:13:32 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com>
In-Reply-To: <5181758E.5070008@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dcrocker@bbiw.net, 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, 01 May 2013 22:13:44 -0000

On 01/05/13 21:05, Brian E Carpenter wrote:
> On 02/05/2013 05:59, Dave Crocker wrote:
>> The blog nicely classes the problem as being too heavy-weight during
>> final stages.  The quick discussion thread seems focused on adding a
>> moment at which the draft specification is considered 'baked'.
>>
>> I think that's still too late.
> What, you agree with your younger self?
>
> http://tools.ietf.org/html/draft-carpenter-icar-sirs-01
>
> Apart from the non-diverse acronym, I still think that proposal
> was a good one.
>
>      Brian
Rereading the background document that lead to the SIRS proposal is also 
worthwhile:
http://tools.ietf.org/html/draft-ietf-problem-issue-statement-00

I think the views in sections A.2.6. to A.2.9 are still pretty much 
applicable; judging from recent comments some people still think the 
situation with the IESG is a 'battle of wills'.

I guess one way of summarising this whole problem might be:
We set on a group of people (a WG) who by definition are supposed to 
work in 'common mode' on a particular problem in what is mostly a closed 
bubble. It's perhaps not entirely surprising that what comes out at IETF 
Last Call time has more than its fair share of 'common mode failures', 
symptoms of groupthink and blinkered views of the overall requirements 
for effective operation in the wider Internet.

The comments in the 'problem' draft and the SIRS proposal reflect an 
attempt to suggest how the closed bubble can be kept in contact with the 
wider world.  However, getting the relationship between outside 
reviewers and the WG teams right would be non-trivial - not to mention a 
significant organisational effort and a load on the reviewers.  To be 
honest, AFAIK we have never attempted to quantify how much extra effort 
(if any) a SIRS-like exercise would require as compared with the 
existing directorate reviews.

Personally, I don't believe that we should attempt to categorise some 
I-Ds as more significant than others.  This requires 20-20 hindsight 
with which we are certainly not equipped.

/Elwyn
BTW
Re the diversity discussion: take a look at the editorial panel on the 
problem draft - ok, its only along one of the dimensions.

Jari might also remember a contribution he made to 'problem':
>     o  WG process is too slow, because of feeping creaturism, deadlocked
>        conflicts or lack of worker bandwidth (Jari Arkko)
I can certainly agree on the feeping creaturism!

/E


From elwynd@dial.pipex.com  Wed May  1 15:15:59 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29C5121F9B46 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 15:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tBL7-Pmx6ZLe for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 15:15:59 -0700 (PDT)
Received: from mk-outboundfilter-5.mail.uk.tiscali.com (mk-outboundfilter-5.mail.uk.tiscali.com [212.74.114.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDA1E21F9AAD for <ietf@ietf.org>; Wed,  1 May 2013 15:15:52 -0700 (PDT)
X-Trace: 625067762/mk-outboundfilter-5.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/81.187.254.249/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 81.187.254.249
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEEAOqSgVFRu/75/2dsb2JhbABSgz6DN7tpgRKDEwEBBR0GFToCBAEQCxgCAgUWCwICCQMCAQIBRQYNAQcBAYgMCK5HkEeBI41/B4I/gRMDlymBJoRbizCDDg
X-IronPort-AV: E=Sophos;i="4.87,591,1363132800"; d="scan'208";a="625067762"
X-IP-Direction: OUT
Received: from weee-pc2.folly.org.uk (HELO [81.187.254.249]) ([81.187.254.249]) by smtp.pipex.tiscali.co.uk with ESMTP; 01 May 2013 23:11:33 +0100
Message-ID: <51819315.9080107@dial.pipex.com>
Date: Wed, 01 May 2013 23:11:33 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com>
In-Reply-To: <5181758E.5070008@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dcrocker@bbiw.net, 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, 01 May 2013 22:15:59 -0000

On 01/05/13 21:05, Brian E Carpenter wrote:
> On 02/05/2013 05:59, Dave Crocker wrote:
>> The blog nicely classes the problem as being too heavy-weight during
>> final stages.  The quick discussion thread seems focused on adding a
>> moment at which the draft specification is considered 'baked'.
>>
>> I think that's still too late.
> What, you agree with your younger self?
>
> http://tools.ietf.org/html/draft-carpenter-icar-sirs-01
>
> Apart from the non-diverse acronym, I still think that proposal
> was a good one.
>
>      Brian
Rereading the background document that lead to the SIRS proposal is also 
worthwhile:
http://tools.ietf.org/html/draft-ietf-problem-issue-statement-00

I think the views in sections A.2.6. to A.2.9 are still pretty much 
applicable; judging from recent comments some people still think the 
situation with the IESG is a 'battle of wills'.

I guess one way of summarising this whole problem might be:
We set on a group of people (a WG) who by definition are supposed to 
work in 'common mode' on a particular problem in what is mostly a closed 
bubble. It's perhaps not entirely surprising that what comes out at IETF 
Last Call time has more than its fair share of 'common mode failures', 
symptoms of groupthink and blinkered views of the overall requirements 
for effective operation in the wider Internet.

The comments in the 'problem' draft and the SIRS proposal reflect an 
attempt to suggest how the closed bubble can be kept in contact with the 
wider world.  However, getting the relationship between outside 
reviewers and the WG teams right would be non-trivial - not to mention a 
significant organisational effort and a load on the reviewers.  To be 
honest, AFAIK we have never attempted to quantify how much extra effort 
(if any) a SIRS-like exercise would require as compared with the 
existing directorate reviews.

Personally, I don't believe that we should attempt to categorise some 
I-Ds as more significant than others.  This requires 20-20 hindsight 
with which we are certainly not equipped.

/Elwyn
BTW
Re the diversity discussion: take a look at the editorial panel on the 
problem draft - ok, its only along one of the dimensions.

Jari might also remember a contribution he made to 'problem':
>     o  WG process is too slow, because of feeping creaturism, deadlocked
>        conflicts or lack of worker bandwidth (Jari Arkko)
I can certainly agree on the feeping creaturism!

/E


From swb@internet2.edu  Wed May  1 15:46:51 2013
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 C8F7921F9B55 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 15:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.953
X-Spam-Level: 
X-Spam-Status: No, score=-6.953 tagged_above=-999 required=5 tests=[AWL=-0.354, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gC0nDNQEONW3 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 15:46:45 -0700 (PDT)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 367A021F9B4C for <ietf@ietf.org>; Wed,  1 May 2013 15:46:44 -0700 (PDT)
Received: from mail73-co9-R.bigfish.com (10.236.132.254) by CO9EHSOBE003.bigfish.com (10.236.130.66) with Microsoft SMTP Server id 14.1.225.23; Wed, 1 May 2013 22:46:43 +0000
Received: from mail73-co9 (localhost [127.0.0.1])	by mail73-co9-R.bigfish.com (Postfix) with ESMTP id 8558C440210; Wed,  1 May 2013 22:46:43 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.237.101; KIP:(null); UIP:(null); IPV:NLI; H:BY2PRD0810HT001.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 6
X-BigFish: S6(zzbb2dI98dI9371I1432Izz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzz8275chz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1b1cn1b1bi1155h)
Received: from mail73-co9 (localhost.localdomain [127.0.0.1]) by mail73-co9 (MessageSwitch) id 1367448402102036_28177; Wed,  1 May 2013 22:46:42 +0000 (UTC)
Received: from CO9EHSMHS003.bigfish.com (unknown [10.236.132.233])	by mail73-co9.bigfish.com (Postfix) with ESMTP id 1627DA0057; Wed,  1 May 2013 22:46:42 +0000 (UTC)
Received: from BY2PRD0810HT001.namprd08.prod.outlook.com (157.56.237.101) by CO9EHSMHS003.bigfish.com (10.236.130.13) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 1 May 2013 22:46:42 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.94.36) with Microsoft SMTP Server (TLS) id 14.16.305.3; Wed, 1 May 2013 22:46:35 +0000
Message-ID: <51819B49.8070909@internet2.edu>
Date: Wed, 1 May 2013 18:46:33 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com>
In-Reply-To: <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.edu
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net, 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, 01 May 2013 22:46:51 -0000

On 05/01/13 17:43, Ralph Droms allegedly wrote:
> On May 1, 2013, at 1:59 PM 5/1/13, Dave Crocker <dhc@dcrocker.net> wrote:
>> I suspect that an earlier exercise at summarizing functional goals and design approaches and issues will have a number of benefits, beyond enabling earlier external review.
> 
> Dave - excellent idea.  A summary that explains the "why" first, that promotes early cross-area review or otherwise expands the set of people that look at and understand the nature of the problem and the structure of the specification will allow for earlier review and lighter-weight correction of problems.

I forgot to say I like that a lot too.  The proponents should be doing
that by some means anyway within the WG.


From lars@netapp.com  Wed May  1 22:22:06 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2303621F9A54 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 22:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.49
X-Spam-Level: 
X-Spam-Status: No, score=-10.49 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFbutdJf6EcG for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 22:21:57 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id B7CB621F9A26 for <ietf@ietf.org>; Wed,  1 May 2013 22:21:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,593,1363158000"; d="scan'208";a="47208735"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 01 May 2013 22:21:56 -0700
Received: from vmwexceht02-prd.hq.netapp.com (vmwexceht02-prd.hq.netapp.com [10.106.76.240]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r425LsVE028720; Wed, 1 May 2013 22:21:55 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.71]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.02.0342.003; Wed, 1 May 2013 22:21:54 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFPLPwfihLgC0i+UMled/haT5jw+6SAgAABgICAAAjzgIAABG+AgAACWgCAAMVfgA==
Date: Thu, 2 May 2013 05:21:54 +0000
Message-ID: <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im>
In-Reply-To: <51815260.6000002@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.114]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D65FD3B07E54F84483A4CC35805F84D2@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>, 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: Thu, 02 May 2013 05:22:06 -0000

On May 1, 2013, at 19:35, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> Sorry: oughtn't that be Proposed Standard?

Yep, it ought to.

Crazy idea: Call a draft PS when it completes WG last-call and give it an R=
FC number, call it something else when it passes IESG review (draft standar=
d? :-) and republish the RFC. When there is interop experience, call it ful=
l standard and republish as needed.

Yeah, all kinds of issues, but if we created a new thing here in between WG=
LC and PS, the broader industry would never understand.

Lars=

From Martin.Stiemerling@neclab.eu  Wed May  1 23:32:43 2013
Return-Path: <Martin.Stiemerling@neclab.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD0421F99AE for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 23:32:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level: 
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DV3iX9ceINh for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 23:32:39 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id E06C921F89BA for <ietf@ietf.org>; Wed,  1 May 2013 23:32:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 29379103F27; Thu,  2 May 2013 08:32:36 +0200 (CEST)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hP9ihSMoxmsj; Thu,  2 May 2013 08:32:36 +0200 (CEST)
Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 05730103F24; Thu,  2 May 2013 08:32:21 +0200 (CEST)
Received: from [10.1.1.190] (10.1.1.190) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 2 May 2013 08:32:20 +0200
Message-ID: <51820874.3030006@neclab.eu>
Date: Thu, 2 May 2013 08:32:20 +0200
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com> <517FE160.4090909@neclab.eu> <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com>
In-Reply-To: <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.1.1.190]
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 06:32:43 -0000

Hi Yoav,

On 04/30/2013 08:09 PM, Yoav Nir wrote:
> Hi Martin,
>
> On Apr 30, 2013, at 6:21 PM, Martin Stiemerling
> <martin.stiemerling@neclab.eu> wrote:
>
>> Hi Ted,
>>
>> On 04/30/2013 01:19 AM, Ted Hardie wrote:
>>> So, this page: http://www.ietf.org/iesg/members.html still has
>>> TBD listed for one of the transport ADs.  Is there a projected
>>> date for appointment at this point?
>>>
>>> Forgive the broad distribution of the question, but it's not
>>> clear whether this question is solely directed at the nomcom, the
>>> IESG, the IAB or the community at large.
>>
>> It is the NOMCOM and the IAB as confirming body.
>>
>
> While this is true, we've been aware of a problem for three months
> now, and we're not aware of any resolution or of any attempt to
> resolve the issue. We know that there are several candidates (Still
> listed on the NomCom website) and for some reason (which we can only
> guess at) none of them is being appointed.
>
> Will that seat remain vacant for a year? Two years? Is there some
> flaw in the process that prevents this issue from being resolved?
>
> Inquiring minds want to know

Indeed and you might imagine who is eagerly wanting for a result.

However, I do not have the answers to your questions, i.e., I am the 
wrong person to ask or answer.

   Martin


-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014

From sm@resistor.net  Thu May  2 00:59:43 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF4CA21F859D for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 00:59:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EuBPYUe4WpaB for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 00:59:43 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D012021F8596 for <ietf@ietf.org>; Thu,  2 May 2013 00:59:42 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r427xF16018113; Thu, 2 May 2013 00:59:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367481562; bh=pnv29Cbh+nKVk3Y9WfzXNR1rMSiiRz62ruKFoL3CKA8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aM0WSQ2G6MmxEi4tvOablh4pgZmhOg0/QhBGYtGqzhifMKtEZ3Ax7lkPkaZOA5X5+ f6jQnIoeUqvhcjZ0gGm4aORoWtT8IxHsRL7qpb/yc9VFcNdRYm0ZPP6uwGcMr3eUCU boUuAWwSgBe0uQ5zvfE96zN0UFdjD96ix12GTH9g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367481562; i=@resistor.net; bh=pnv29Cbh+nKVk3Y9WfzXNR1rMSiiRz62ruKFoL3CKA8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hzKY5jpXw0ME/7dMjZWhvjzSypDHZFwnvK3kBKd90F0XOa+CQFuhVCIA4gB0h8rOt 43PJiehwvfEMc9yufs+OvvuShNtuJoS4ZGbP/yJAr96yi2YC+U5OG4OQDbUeTv7Gf7 NsqMWIcd4aKLxHVYZ0q9t+wir9m0caMlHD3lZ0MM=
Message-Id: <6.2.5.6.2.20130501233948.0c9eef70@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 May 2013 00:58:57 -0700
To: Matt Lepinski <mlepinski@bbn.com>, Allison Mankin <amankin@verisign.com>
From: SM <sm@resistor.net>
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
In-Reply-To: <51820874.3030006@neclab.eu>
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com> <517FE160.4090909@neclab.eu> <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com> <51820874.3030006@neclab.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Ted Hardie <ted.ietf@gmail.com>, ietf@ietf.org, Martin Stiemerling <martin.stiemerling@neclab.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 07:59:44 -0000

Hi Matt, Allison,
At 23:32 01-05-2013, Martin Stiemerling wrote:
>However, I do not have the answers to your questions, i.e., I am the 
>wrong person to ask or answer.

:-)

The NomCom Chair posted a statement on March 9 [1] where it is mentioned that:

   "The Nomcom will continue its work until all open positions are filled."

There is an open position which has not been filled.  Is NomCom 2012 
still continuing its work?

The IETF usually has a NomCom Chair.  Who is the current NomCom Chair [2]?

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg77720.html
2. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg11412.html 


From vesely@tana.it  Thu May  2 02:00:59 2013
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 A770921F9803 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 02:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.744
X-Spam-Level: 
X-Spam-Status: No, score=-4.744 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLyTHMG3I5Xy for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 02:00:55 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 8C62C21F9423 for <ietf@ietf.org>; Thu,  2 May 2013 02:00:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367485253; bh=QbP5f5g/7W+XCAUd1kSd+boKnNNdm67Xxi1LrWc4y/k=; l=1802; h=Date:From:To:References:In-Reply-To; b=kZfe2o5Ev0vhcIR/axTXFDfjgnjsoALmYK353Lp0c0QA93kNkcERwrk0qI4klRj25 Yydm6/boZb0UOcmY3mhxVtgZCePHAvjoAnNitWKNS+9C9bVyjsN6c+kJVVaEBMQmI6 SxjTWj1H8xPTZgrMkZDD2/EifeJl2eA/yIP1Ks9E=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Thu, 02 May 2013 11:00:53 +0200 id 00000000005DC039.0000000051822B45.00002715
Message-ID: <51822B44.7090107@tana.it>
Date: Thu, 02 May 2013 11:00:52 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <C83D1AA8-4F8E-4304-8A7A-3EE3ED2B1F9F@neustar.biz>
In-Reply-To: <C83D1AA8-4F8E-4304-8A7A-3EE3ED2B1F9F@neustar.biz>
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, 02 May 2013 09:00:59 -0000

On Tue 30/Apr/2013 20:02:11 +0200 Edward Lewis wrote:
> On Apr 30, 2013, at 12:28, Alessandro Vesely wrote:
>> ...The basic fact that killed the SPF type is the ability to use
>> TXT as a replacement.  There must be an analogous of Gresham's
>> law:  "Bad types drive out good ones."
> 
> I disagree with the assertion that what killed SPF is "the ability
> to use TXT as a replacement."   It has nothing to do with one
> option being superior to the other, it was the lack of technical
> incentive to switch from one to the other.

I'm not following:  Either one option is superior to the other, or
they are more or less equally fit.  In the latter case, it becomes a
question of taste and there is no technical incentive.

> I post this in the sense that if the root cause is not understood,
> no solution will stick.  Here is a message with my recounting of
> what led us to this point:
> 
> http://www.ietf.org/mail-archive/web/dnsext/current/msg12681.html

I agree that security shackles are different from provisioning.  Yet,
their effects on deployment are similar:  They are part of those minor
problems that always have to be faced when introducing something new.
 Such problems are only faced and overcome if the new type provides
some added value, which SPF over TXT does not.

> I don't see the death of SPF has a harbinger of things to come.
> There's a strong case to be made the failure happened before 2004
> and the root cause has since been corrected by changing the RRTYPE
> type allocation policies.  Still that fix was too late to ever let
> SPF sprout wings.

Type allocation policy isn't but one requirement for new types.  To
check the syntax and the semantics of data records, and to
conveniently format them on the wire would make for real added value.

From vesely@tana.it  Thu May  2 02:20:33 2013
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 3288721F9954 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 02:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.742
X-Spam-Level: 
X-Spam-Status: No, score=-4.742 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoopatAQRwvz for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 02:20:23 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 744DC21F8960 for <ietf@ietf.org>; Thu,  2 May 2013 02:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367486422; bh=ZWqm/R3DYbwi1mcjwIxsW3dOesj5sIAi4ILLoKUBes4=; l=1369; h=Date:From:To:References:In-Reply-To; b=Vr/1wTJfGJG/ZuZDqE+rIGE6TKBqKBqWuOY91bFEW/jAVScQU1s6jQ6BadoUeuUf/ eXAAsR5Bx3IsSoR8zTaLVoUxN0JVcW+BUdkUQrCekLv8ARTdavOZDH6UdlSOEopNv4 8m5lSusM9EoAtI35+yin43CS1c41LrTvzLiXt784=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Thu, 02 May 2013 11:20:22 +0200 id 00000000005DC039.0000000051822FD6.00007FAA
Message-ID: <51822FD6.1080805@tana.it>
Date: Thu, 02 May 2013 11:20:22 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org>
In-Reply-To: <20130501010455.DE040336241D@drugs.dv.isc.org>
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, 02 May 2013 09:20:33 -0000

On Wed 01/May/2013 03:04:52 +0200 Mark Andrews wrote:
> In message <517FF144.5040600@tana.it>, Alessandro Vesely writes:
>> On Tue 30/Apr/2013 01:07:42 +0200 Mark Andrews wrote:
>>> 
>>> SPF is techically superior to TXT is lots of ways.
>>> 
>>> [...]
>>> 
>>> For TXT you need to lookup the existing RRset, extract
>>> the v=spf1 record from it.  You then need to create a
>>> UPDATE message to delete just that record as well as add
>>> the new TXT record.   You then have to hope that no one
>>> else is performing a simultaneous update as you may get
>>> two TXT v=spf1 records in the RRset.
>> 
>> That's true, except that one has TXT records anyway.
> 
> 	nsupdate
> 	update del example.com SPF
> 	update add example.com 3600 SPF v=spf1 ....
> 	send
> 
> [intricacies of doing so in the face of multiple TXT records elided]

Thanks for the examples.

> I'm sure I could come up with a more compact way of identifying
> a spf record but it wouldn't be needed if people published type
> SPF.

You must mean "if people published SPF _only_".

What percentage of NS servers use dynamic updates primarily?  (I only
happened to use nsupdate occasionally, e.g. to fix dhcp hiccups.)

Switching to fully dynamic management would be a major evolutionary
step for DNS, and it will certainly make the arguments for strong DNS
typing more stringent.

From vesely@tana.it  Thu May  2 03:24:42 2013
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 9D70A21F9910 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 03:24:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.74
X-Spam-Level: 
X-Spam-Status: No, score=-4.74 tagged_above=-999 required=5 tests=[AWL=-0.021,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MeYgGHZZ+Bcx for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 03:24:38 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF5021F9972 for <ietf@ietf.org>; Thu,  2 May 2013 03:24:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1367490276; bh=Swe/NfII2dtOlrQYqM8crfXP4/JZnMxHL7HH9SaHqns=; l=1169; h=Date:From:To:References:In-Reply-To; b=RN11hT6GFrBttwcLOLTQO1ste0yg6lLRUeOERogos7ZBhRILTe5Zqq8+hpjNA89Fg CvMsBZh89iFygvK19VzsK8UFKrBz+5aBh1TQHjwFa4lqQmJQ1pvdEJzTsEJ4uh8J6y r5+rmktxlOtXx4VZCjTPL1aPQW1fQv7VPemFdy/k=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.101] (pcale.tana [172.25.197.101]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wmail.tana.it with ESMTPSA; Thu, 02 May 2013 12:24:36 +0200 id 00000000005DC048.0000000051823EE4.00002B24
Message-ID: <51823EE4.8020001@tana.it>
Date: Thu, 02 May 2013 12:24:36 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: What's a reasonable and non-discriminatory patent license?
References: <20130429031450.99734.qmail@joyce.lan>
In-Reply-To: <20130429031450.99734.qmail@joyce.lan>
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, 02 May 2013 10:24:42 -0000

On Mon 29/Apr/2013 05:14:50 +0200 John Levine wrote:
> The Patently-O blog has a new guest post by Jorge Contreras, who among
> other things is the IETF's lawyer, on a recent court decision about
> how to determine what's an appropriate RAND royalty rate for
> standard-essential patents.  The patents and standards in question
> aren't from the IETF (they're ITU H.264 and IEEE 801.11) but the
> article is highly relevant to the patent issues that crop up here.
> 
> Jorge writes well and it's quite readable.
> 
> http://www.patentlyo.com/patent/2013/04/so-thats-what-rand-means-a-brief-report-on-the-findings-of-fact-and-conclusions-of-law-in-microsoft-v-motorola.html

However modified, the "Georgia-Pacific" method itself is based on a
royalty calculated as a "percentage of footage actually sold or volume
of actual sales".  How does that apply to free software?
Arithmetically, N*0$*p% is zero for any N and p%.  What am I missing?

IANAL, but given the role that software and open source software in
particular bear in our standardization process, I'd suggest that such
zero product rule be explicitly mentioned in an IETF's definition of RAND.

From daedulus@btconnect.com  Thu May  2 03:52:15 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2952521F9947 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 03:52:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.007
X-Spam-Level: 
X-Spam-Status: No, score=-4.007 tagged_above=-999 required=5 tests=[AWL=2.592,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKrCVMCgTTQa for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 03:52:09 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id CE3F021F9981 for <ietf@ietf.org>; Thu,  2 May 2013 03:52:07 -0700 (PDT)
Received: from mail228-tx2-R.bigfish.com (10.9.14.227) by TX2EHSOBE010.bigfish.com (10.9.40.30) with Microsoft SMTP Server id 14.1.225.23; Thu, 2 May 2013 10:52:07 +0000
Received: from mail228-tx2 (localhost [127.0.0.1])	by mail228-tx2-R.bigfish.com (Postfix) with ESMTP id 07B09380087; Thu,  2 May 2013 10:52:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.69; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0711HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -13
X-BigFish: PS-13(zz9371I542Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz17326ah8275bh8275dh8275ch1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail228-tx2 (localhost.localdomain [127.0.0.1]) by mail228-tx2 (MessageSwitch) id 1367491925431203_25281; Thu,  2 May 2013 10:52:05 +0000 (UTC)
Received: from TX2EHSMHS022.bigfish.com (unknown [10.9.14.232])	by mail228-tx2.bigfish.com (Postfix) with ESMTP id 66F79BC0055; Thu,  2 May 2013 10:52:05 +0000 (UTC)
Received: from AMXPRD0711HT003.eurprd07.prod.outlook.com (157.56.250.69) by TX2EHSMHS022.bigfish.com (10.9.99.122) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 2 May 2013 10:52:05 +0000
Received: from DB3PRD0511HT003.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.242.9.164) with Microsoft SMTP Server (TLS) id 14.16.305.3; Thu, 2 May 2013 10:51:49 +0000
Message-ID: <001d01ce4722$56582340$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Jari Arkko <jari.arkko@piuha.net>, IETF list <ietf@ietf.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
Date: Thu, 2 May 2013 11:46:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.213]
X-FOPE-CRA-SourceIpAddress: 157.56.250.69
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: presnick@qti.qualcomm.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: jari.arkko@piuha.net
X-OriginatorOrg: btconnect.com
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 10:52:15 -0000

----- Original Message -----
From: "Jari Arkko" <jari.arkko@piuha.net>
To: "IETF list" <ietf@ietf.org>
Cc: "Pete Resnick" <presnick@qti.qualcomm.com>
Sent: Wednesday, May 01, 2013 4:33 PM
Subject: call for ideas: tail-heavy IETF process


I wrote a blog article about how we do a fairly significant amount of
reviews and changes in the late stages of the IETF process. Next week
the IESG will be having a retreat in Dublin, Ireland. As we brought this
topic to our agenda, Pete and I wanted to raise the issue here and call
for feedback & ideas for improving the situation with all of you.

<tp>

Well, yes, any engineer knows that the later in the process changes are
made, the more costly they are, so the key is getting the early stages
right.  But what are we doing wrong?  We need feedback about what the
DISCUSSes are, what might we have done at eg WG Adoption of an I-D to
forestall the later DISCUSS.

Are some Areas or WG better than others?  A statistical analysis would
help here, who to learn from, who not to; the graph suggests to me that
there is a steadily rising trend of DISCUSSes per document except when
there is a recession, when there is a step fall in them, but I do not
see any action I can take to make a difference from this observation.

Tom Petch


http://www.ietf.org/blog/2013/05/balancing-the-process/

Jari




From mansaxel@besserwisser.org  Thu May  2 03:53:52 2013
Return-Path: <mansaxel@besserwisser.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 03D4B21F99B4 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 03:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.825
X-Spam-Level: 
X-Spam-Status: No, score=-1.825 tagged_above=-999 required=5 tests=[AWL=0.475,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ijV-KQGetCpq for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 03:53:51 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 779BB21F999E for <ietf@ietf.org>; Thu,  2 May 2013 03:53:50 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id CCDFA9EF0; Thu,  2 May 2013 12:53:47 +0200 (CEST)
Date: Thu, 2 May 2013 12:53:47 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
Message-ID: <20130502105347.GA24847@besserwisser.org>
References: <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ibTvN161/egqYuK8"
Content-Disposition: inline
In-Reply-To: <51822FD6.1080805@tana.it>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 02 May 2013 10:53:52 -0000

--ibTvN161/egqYuK8
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE Date: Thu, May 02, 201=
3 at 11:20:22AM +0200 Quoting Alessandro Vesely (vesely@tana.it):

> What percentage of NS servers use dynamic updates primarily?  (I only
> happened to use nsupdate occasionally, e.g. to fix dhcp hiccups.)

Every Active Directory installation is using dynamic DNS. And while the
unwillingness of that particular vendor to handle unknown RRtypes or add
specific support for SPF is a baffling mystery to the rest of the world,
they can and do change -- they have a prototype DNSSEC implementation
in recent versions complete with a large bunch of new RRtypes.
=20
> Switching to fully dynamic management would be a major evolutionary
> step for DNS, and it will certainly make the arguments for strong DNS
> typing more stringent.

Since year 2000 and the initial release of Active Directory that has
as a matter of fact happened. The typing argument has always been valid
=66rom a design perspective; now there is an operational requirement.

/M=C3=A5ns, whose $dayjob includes running AD DNS, but using BIND and Unbou=
nd.=20
--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Does someone from PEORIA have a SHORTER ATTENTION span than me?

--ibTvN161/egqYuK8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlGCRbsACgkQ02/pMZDM1cU1uACglv8iqNmuoF15tvyjbgc5pP41
q9EAoIJO4y7pVn95AAQqgVgEMnOOGYlT
=NBHU
-----END PGP SIGNATURE-----

--ibTvN161/egqYuK8--

From mcr@sandelman.ca  Thu May  2 06:33:20 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3452121F8935 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 06:33:20 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RNigstdVi9U2 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 06:33:15 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id D873F21F87FB for <ietf@ietf.org>; Thu,  2 May 2013 06:33:12 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 539AD20168 for <ietf@ietf.org>; Thu,  2 May 2013 09:44:08 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 98DB563A62; Thu,  2 May 2013 09:32:39 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8955E638E8 for <ietf@ietf.org>; Thu,  2 May 2013 09:32:39 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
In-Reply-To: <6.2.5.6.2.20130501233948.0c9eef70@resistor.net>
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com> <517FE160.4090909@neclab.eu> <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com> <51820874.3030006@neclab.eu> <6.2.5.6.2.20130501233948.0c9eef70@resistor.net>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 02 May 2013 09:32:39 -0400
Message-ID: <1220.1367501559@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 13:33:20 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "SM" =3D=3D SM  <sm@resistor.net> writes:
    SM> There is an open position which has not been filled.  Is NomCom
    SM> 2012 still continuing its work?

    SM> The IETF usually has a NomCom Chair.  Who is the current NomCom
    SM> Chair [2]?=20

The nomcom chair continues to do the work.
The nomcom is in fact meeting in 28 minutes to discuss some issues
resulting from an action that was taken.

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUYJq94qHRg3pndX9AQL2pAQAtnr1uq0VIr2BZ88ps/+Yt03JKXG0EifE
hw2k1boUKIlvM3Tz7xV0vFdnTRM/4LlToi8KkszkkjkNxEr2UcftZbaL3dQlIxhY
UOqk7i+KE9r50vR+G7iXGPPRkvlujv3c4hkI7MlPR2xhj13WozpAONvpIU0pNqyr
AX2pEUTQU3o=
=I7oy
-----END PGP SIGNATURE-----
--=-=-=--

From Francis.Dupont@fdupont.fr  Thu May  2 06:47:59 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A8E21F8624 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 06:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mD4i+916KuAl for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 06:47:59 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id ABFAC21F85C3 for <ietf@ietf.org>; Thu,  2 May 2013 06:47:58 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r42DldXE063126; Thu, 2 May 2013 15:47:39 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201305021347.r42DldXE063126@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: call for ideas: tail-heavy IETF process 
In-reply-to: Your message of Wed, 01 May 2013 12:33:47 EDT. <32577.1367426027@sandelman.ca> 
Date: Thu, 02 May 2013 15:47:39 +0200
Sender: Francis.Dupont@fdupont.fr
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: Thu, 02 May 2013 13:47:59 -0000

 In your previous mail you wrote:

>  If we are unwilling to bring "RFC" back to a place were it does not
>  equal STD, then we need to create a new category of document which
>  amounts to "fully baked ID".  Things like IANA allocations could occur
>  at that point.

=> IMHO the last point (IANA allocations) is a critical detail.

>  In the days of dot-boom it was not unusual to see widespread
>  implementation very early in the ID process and even interop and
>  experimental deployment.   While this still occurs for quite a number of
>  things (and sometimes it's a problem that the ID can not be changed as a
>  result), there is an equal amount of "wait for the RFC to come out".

=> as an implementor of early specs I very often get a problem with
the to-be-done IANA allocations: if it is not a concern for a lab
prototype, I enforce the strict policy to *never* make an official
distrib with support, etc, using not officially allocated by IANA
code points. I believe I have not to explain the reason of this policy.
Note this concern does not go very well with the "running code" principle,
this is why I'd like to see Jarri's issue solved, even currently I
don't agree (or disagree) with Michael's proposal.

Thanks

Francis.Dupont@fdupont.fr

PS: I like the SIRS idea even the gen-art review team (which can be seen
as a lightweight prototype of it) can lead me to believe it won't happen
in the real world (i.e., I'd like to be wrong :-), mainly because it
supposes an amount of skilled manpower we don't have.

From lear@cisco.com  Thu May  2 07:53:21 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C00521F8D05 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 07:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W7U2h67mz0Bn for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 07:53:14 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id CCDA021F8D13 for <ietf@ietf.org>; Thu,  2 May 2013 07:53:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9609; q=dns/txt; s=iport; t=1367506394; x=1368715994; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=45reRRiOhIPtW8nieMw86Ko8KWMpDy3b6PpLgsQiy64=; b=SezkWbbpyG1qX7blHHKQ5RlWXsF8OAaRGAMAXxv5sfSV+zJsRHd0BH3K SmWh/9kxxVW/SRDlHgupR3K0eaCnQRVg1DszC79LeyyYIsZkrpvTAt+cD lX4zz2cuP+G1UTkODkSdMJ8GATairHw4JHWZxWu2DCcTymHHckyHZr23C E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEGAEF9glGQ/khL/2dsb2JhbABSgweDboVetg9/FnSCHwEBAQQYC1UBEAsYCRYIAwICCQMCAQIBKwkRBg0BBQIBARCHeLBAkGqPJgeCQIETA5Ncg0+RMoMPOg
X-IronPort-AV: E=Sophos;i="4.87,597,1363132800";  d="scan'208,217";a="153562044"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 02 May 2013 14:53:12 +0000
Received: from mctiny.local ([10.61.197.59]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r42Er9DB024362 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 May 2013 14:53:09 GMT
Message-ID: <51827DD5.4010402@cisco.com>
Date: Thu, 02 May 2013 16:53:09 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <CAL0qLwY3NAtkcznaLf-aNrKtSQLFdrPy4JV=Vmbic5kYB-wfew@mail.gmail.com>
In-Reply-To: <CAL0qLwY3NAtkcznaLf-aNrKtSQLFdrPy4JV=Vmbic5kYB-wfew@mail.gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------030707060100020808050401"
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: Thu, 02 May 2013 14:53:21 -0000

This is a multi-part message in MIME format.
--------------030707060100020808050401
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

And here we come to a conflict between what we as a community would
like, versus what the market decides.  This leads to a few questions:

1.  Do we have to make a decision at any point from a protocol
standpoint that the market has in fact made a decision?  I ask this
question because I performed an experiment along these lines some years
ago, finding quite a number of proposed standards that were nowhere to
be seen on the 'net.  Earlier we saw discussion about simplifying code
bases, but generally a developer  makes that decision, not the IETF.

2.  What are the timescales involved?  Is it fair to treat IPv6 the same
as a new DHCP option or a DNS RR?  What are the parameters?  One could
reasonably argue with the benefit of hindsight that there was no way we
would see IPv6 adoption until we ran out of IPv4 addresses.  For DNS
RRs, there are some common inhibitors.

3.  What can be done by the IETF to improve likelihood of adoption, and
conversely what should we not bang our heads against?

Eliot



On 5/1/13 7:03 AM, Murray S. Kucherawy wrote:
> On Tue, Apr 30, 2013 at 12:52 PM, David Conrad <drc@virtualized.org
> <mailto:drc@virtualized.org>> wrote:
>
>     SPF using TXT and hence, SPFBIS forces the uniquification of the
>     DNS response into the application instead of in the DNS library.
>     Given the ordering of individual TXT RRs within an RRset is not
>     guaranteed, I suspect the chances that every application is going
>     to do that parsing correctly is relatively low (btw, the example
>     in 3.3 in spfbis-14 is a bit misleading: assuming "second string"
>     is in a separate TXT RR (which is implied), the concatenation
>     might be "second stringv=spf1 ..... first").  The more interesting
>     bit is if/when another protocol uses TXT at the same ownername.
>
>
> Yes, I understand all of that, and I've written code to deal with it. 
> It's not rocket science.
>  
>
>     The RR has been allocated and it is supported in most DNS servers
>     and resolver libraries in one form or another.  Provisioning
>     systems take much longer, but that isn't surprising and shouldn't
>     be an argument to deprecate (if it is, we might as well close the
>     RRtype registry for new entries).
>
>
> We're not only talking about provisioning systems here.  We're also
> talking about interference with queries and replies at the DNS
> protocol level.  The survey work done for RFC6686 showed that
> something on the order of thousands of domains in the sample set
> suffered from this.  It is a very real issue for a deployed protocol.
>  
>
>     In the past, the IETF used to make decisions based on long-term
>     technical/architectural correctness, even in the face of pragmatic
>     complications (e.g., the choice to mandate strong crypto despite
>     real world challenges some companies faced in exporting that
>     crypto in products). In this particular case, there seems to be an
>     argument to explicitly disallow the long-term
>     technically/architecturally correct approach because some folks
>     choose not to add an RR to their zone files or support that RR in
>     their provisioning systems.  As I said in DNSEXT, this seems like
>     the wrong approach to me.
>
>
> All things being equal, I would agree with you.  And if SPF were
> starting anew today, I suspect I might have a different opinion.  The
> question, then, is the weight of the mitigating circumstances, which
> obviously the two communities evaluate quite differently.
>
> -MSK


--------------030707060100020808050401
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    And here we come to a conflict between what we as a community would
    like, versus what the market decides.Â  This leads to a few
    questions:<br>
    <br>
    1.Â  Do we have to make a decision at any point from a protocol
    standpoint that the market has in fact made a decision?Â  I ask this
    question because I performed an experiment along these lines some
    years ago, finding quite a number of proposed standards that were
    nowhere to be seen on the 'net.Â  Earlier we saw discussion about
    simplifying code bases, but generally a developerÂ  makes that
    decision, not the IETF.<br>
    <br>
    2.Â  What are the timescales involved?Â  Is it fair to treat IPv6 the
    same as a new DHCP option or a DNS RR?Â  What are the parameters?Â 
    One could reasonably argue with the benefit of hindsight that there
    was no way we would see IPv6 adoption until we ran out of IPv4
    addresses.Â  For DNS RRs, there are some common inhibitors.<br>
    <br>
    3.Â  What can be done by the IETF to improve likelihood of adoption,
    and conversely what should we not bang our heads against?<br>
    <br>
    Eliot<br>
    <br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 5/1/13 7:03 AM, Murray S. Kucherawy
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAL0qLwY3NAtkcznaLf-aNrKtSQLFdrPy4JV=Vmbic5kYB-wfew@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">On Tue, Apr 30, 2013 at 12:52 PM, David Conrad <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:drc@virtualized.org" target="_blank">drc@virtualized.org</a>&gt;</span>
        wrote:<br>
        <div class="gmail_extra">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">SPF
              using TXT and hence, SPFBIS forces the uniquification of
              the DNS response into the application instead of in the
              DNS library. Given the ordering of individual TXT RRs
              within an RRset is not guaranteed, I suspect the chances
              that every application is going to do that parsing
              correctly is relatively low (btw, the example in 3.3 in
              spfbis-14 is a bit misleading: assuming "second string" is
              in a separate TXT RR (which is implied), the concatenation
              might be "second stringv=spf1 ..... first"). Â The more
              interesting bit is if/when another protocol uses TXT at
              the same ownername.<br>
            </blockquote>
            <div><br>
            </div>
            <div>Yes, I understand all of that, and I've written code to
              deal with it.Â  It's not rocket science.<br>
              Â <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="im">The RR has been allocated and it is
                supported in most DNS servers and resolver libraries in
                one form or another. Â Provisioning systems take much
                longer, but that isn't surprising and shouldn't be an
                argument to deprecate (if it is, we might as well close
                the RRtype registry for new entries).<br>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>We're not only talking about provisioning systems
              here.Â  We're also talking about interference with queries
              and replies at the DNS protocol level.Â  The survey work
              done for RFC6686 showed that something on the order of
              thousands of domains in the sample set suffered from
              this.Â  It is a very real issue for a deployed protocol.<br>
              Â <br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              In the past, the IETF used to make decisions based on
              long-term technical/architectural correctness, even in the
              face of pragmatic complications (e.g., the choice to
              mandate strong crypto despite real world challenges some
              companies faced in exporting that crypto in products). In
              this particular case, there seems to be an argument to
              explicitly disallow the long-term
              technically/architecturally correct approach because some
              folks choose not to add an RR to their zone files or
              support that RR in their provisioning systems. Â As I said
              in DNSEXT, this seems like the wrong approach to me.<br>
            </blockquote>
            <div><br>
            </div>
            <div>All things being equal, I would agree with you.Â  And if
              SPF were starting anew today, I suspect I might have a
              different opinion.Â  The question, then, is the weight of
              the mitigating circumstances, which obviously the two
              communities evaluate quite differently.<br>
              <br>
            </div>
            <div>-MSK<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------030707060100020808050401--

From fred@cisco.com  Thu May  2 07:54:42 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1956821F84B2 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 07:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.486
X-Spam-Level: 
X-Spam-Status: No, score=-110.486 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtHgCYBWg4+E for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 07:54:36 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 701DC21F863B for <ietf@ietf.org>; Thu,  2 May 2013 07:54:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2115; q=dns/txt; s=iport; t=1367506476; x=1368716076; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=CKRa9dwetl8lc8ZdHfQDytzOQwpJXklQjHxz0UyFxYE=; b=eXHEO4C7+JkXuIfJfmDOoT323aMlvc8ExRxrs8QjajFmi5vFweweZFA6 bvf+ExxR9PpJ7Orl+Kk7SZAFG3ogs2nfi8Uks8oLn12q1Eehd5gjMaxEO x3xHuGJsVDu5U3tFsjafgcbsJbELfvlC86ZJhKo6JBoZeAqAmwdLTiwV1 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFALR9glGtJV2b/2dsb2JhbABSgwe/W38WdIIfAQEBAwE6MQkFBQ0BKhRCJwQODRECh2sGwS2NcoEDMYJ5YQOoXYMNgic
X-IronPort-AV: E=Sophos;i="4.87,597,1363132800"; d="scan'208";a="205691865"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP; 02 May 2013 14:54:34 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r42EsYmX002511 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 May 2013 14:54:34 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Thu, 2 May 2013 09:54:33 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Long review tail
Thread-Topic: Long review tail
Thread-Index: AQHOR0T0Oy/2VZI1w0KRKLMgoAiumQ==
Date: Thu, 2 May 2013 14:54:32 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B830783@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13E8C4CA64243A429142EF86E0279989@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org> list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 14:54:42 -0000

I your blog, you wrote:

> Having been involved in the process for many years, often the bigger chan=
ges at this stage relate to cross-area issues, or the fact that the careful=
 reviews from the IETF last call, directorates, and 15 ADs often represents=
 a significant increase in the number of non-WG people looking at the docum=
ent.

If I may make a suggestion, I suspect that the problem statement suggests i=
ts own solution: get cross-area reviewers involved in the working group pro=
cess earlier. There is a trade-off in that, of course, which is that if the=
 cross-area review happens too early it may happen on a document that isn't=
 really ready for cross-area review. But bottom line, that's what you need =
to have.

As a working group chair, what I have done on a number of occasions is ask =
one directorate or another (usually the security directorate, which is not =
to pick on them but to be frank) to review a document that I think has need=
 of their expertise. This has not, in my history, been fruitful; I have got=
ten a few responses, but not many. If there were a way to request those tha=
t would in fact result in reviews, I would include it in my standard WGLC p=
rocess, and I suspect that would have a salubrious effect.

The other thing that I might suggest is a comment I have made before: if in=
 the opinion of the IESG a document needs a lot of work (e.g., non-trivial =
changes), return it to the working group. I know of, due to some spam I rec=
eived a few months ago, an editorial service in London that will for a smal=
l fee (a common IETF document would be perhaps 100 pounds) review and updat=
e a document; pointing the option out to a working group chair might be as =
useful a response as any. Corporate technical writing services might also b=
e called in. Whatever the technical issues a document has, the place for th=
em to *not* be worked out is with an AD simply holding the document hostage=
; it is to say it needs work and send it back for the work.

Both of those would be likely to simplify the life of an AD as well.=

From stephen.farrell@cs.tcd.ie  Thu May  2 08:13:11 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF1F21F8E2C for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.476
X-Spam-Level: 
X-Spam-Status: No, score=-103.476 tagged_above=-999 required=5 tests=[AWL=-0.877, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qoi2IfI53FMR for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:13:06 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id D865A21F8EC6 for <ietf@ietf.org>; Thu,  2 May 2013 08:13:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AB2F6BE88; Thu,  2 May 2013 16:12:37 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hHHfM-S2Mt1k; Thu,  2 May 2013 16:12:37 +0100 (IST)
Received: from [IPv6:2001:770:10:203:cdfc:bf00:7a90:e70e] (unknown [IPv6:2001:770:10:203:cdfc:bf00:7a90:e70e]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 876BCBE47; Thu,  2 May 2013 16:12:37 +0100 (IST)
Message-ID: <51828266.6040303@cs.tcd.ie>
Date: Thu, 02 May 2013 16:12:38 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Long review tail
References: <8C48B86A895913448548E6D15DA7553B830783@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B830783@xmb-rcd-x09.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org> list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 15:13:12 -0000

On 05/02/2013 03:54 PM, Fred Baker (fred) wrote:
> I your blog, you wrote:
> 
>> Having been involved in the process for many years, often the bigger changes at this stage relate to cross-area issues, or the fact that the careful reviews from the IETF last call, directorates, and 15 ADs often represents a significant increase in the number of non-WG people looking at the document.
> 
> If I may make a suggestion, I suspect that the problem statement suggests its own solution: get cross-area reviewers involved in the working group process earlier. There is a trade-off in that, of course, which is that if the cross-area review happens too early it may happen on a document that isn't really ready for cross-area review. But bottom line, that's what you need to have.
> 
> As a working group chair, what I have done on a number of occasions is ask one directorate or another (usually the security directorate, which is not to pick on them but to be frank) to review a document that I think has need of their expertise. This has not, in my history, been fruitful; I have gotten a few responses, but not many. If there were a way to request those that would in fact result in reviews, I would include it in my standard WGLC process, and I suspect that would have a salubrious effect.

As a data point, Sean and I discussed this with folks at the secdir
lunch in Orlando. We currently get about 80% of IETF LC documents
that actually get reviews by secdir, and many of those are very
useful to the ADs, though it is late in the process for the authors
and WGs. So we've a 20% dropped-review rate and that's been stable
for quite a while even with secdir membership changes.

When asked if more could be done, (without any specific proposal
for what to do) the response was that increasing the workload
would maybe lead to a significant drop in that 80% figure since
secdir folks are also busy with their day-jobs. So increasing
the workload for reviewers is tricky.

Trying to shift the workload to earlier in the process is certainly
worth a look, but also has risks. It would increase the reviewer
workload since the best reviews generally involve a bunch of follow
up mails, and extending that over months takes more of the
reviewers time. I suspect the rate of dropped-reviews might also
increase if documents are reviewed too early. OTOH, for the
authors and WG, this does seem like it'd be better.

I guess if this were easy, we'd have solved it already;-)

> The other thing that I might suggest is a comment I have made before: if in the opinion of the IESG a document needs a lot of work (e.g., non-trivial changes), return it to the working group. I know of, due to some spam I received a few months ago, an editorial service in London that will for a small fee (a common IETF document would be perhaps 100 pounds) review and update a document; pointing the option out to a working group chair might be as useful a response as any. Corporate technical writing services might also be called in. Whatever the technical issues a document has, the place for them to *not* be worked out is with an AD simply holding the document hostage; it is to say it needs work and send it back for the work.

I fully agree with that.

S

PS: If a WG chair ask Sean or I for an early review we do usually
stick that into the secdir rotation. At the moment that's ok since
its not that common, but if we got lots of them it might become an
issue.

> Both of those would be likely to simplify the life of an AD as well.
> 

From hsantos@isdg.net  Thu May  2 08:15:01 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A88C921F8A11 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:15:01 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o73oHF56I8Wm for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:14:56 -0700 (PDT)
Received: from listserv.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 452AD21F8EAF for <ietf@ietf.org>; Thu,  2 May 2013 08:14:55 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2586; t=1367507686; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=TenvAUE JxtswspPjMGkAdYVCsmg=; b=IatCCeDQJ4WFQ9UjX9YSomqOUw74Z7sRQB7WLu5 gYVFtK9WuJuetnXHqbo+f6aHH84QoGmx9RL6CvRti9JDFTuoVBzQKL8F3XWgltvK ikMnkBmrMi1WSDec4GvRlUC9rweN3knCF/a66+P3Lch3FDK+cEd6RXtbpGw/8h5a 5x3Y=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 02 May 2013 11:14:46 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2006400838.8430.1752; Thu, 02 May 2013 11:14:45 -0400
Message-ID: <5182828C.3040200@isdg.net>
Date: Thu, 02 May 2013 11:13:16 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Balancing the Process  (Was: Obsoleting SPF RRTYPE)
References: <20130425013317.36729.qmail@joyce.lan>	<4272263.gKzvRQiTlr@scott-latitude-e6320>	<517C8994.2080102@gathman.org>	<1457820.oICsLp4n8g@scott-latitude-e6320>	<20130428195221.GA27654@besserwisser.org>	<8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com>	<517DAB89.8000409@gathman.org>	<8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com>	<517E90A6.6090108@gathman.org>	<8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com>	<517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net>	<20130429230742.3D2833339511@drugs.dv.isc.org>	<517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us>	<CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com>	<A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu> <51811C20.5040305@qti.qualcomm.com>
In-Reply-To: <51811C20.5040305@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 15:15:01 -0000

Mr. Resnick,  for the record, I wasn't upset. Believe it or not, I was 
actually applying an suggestion posted last month or so here with the 
IETF diversity talks to help get a major WG issue resolved, one with a 
near surety of an appeal, resolved and addressed much faster and hence 
avoid a waste of time on the behalf of all.

How appropo, that a topic of "balancing of process" as being considered. 
   It is one thing I believe the IETF needs and can be actually apply 
today. Yes, I don't agree with the negative tone taken in SPFBIS where 
in effect, an attempt to shut down communications and indirectly 
personally attack posters occurred and the advocates of the SPF RRTYPE 
removal (incidentally, a SPEC change which I believe was prohibited by 
the charter), basically blowing off advocates of a RFC4408 status quo. 
If you believe that was proper, I think we have a WG problem.

Overall, I believe this (keep the migration path) is the proper 
compromise to resolve the issue, and I believe that this particular 
issue is industry-wide important to resolve with across the board 
engineering input. It *SHOULD NOT* be reserved only to the applications 
SPFBIS group especially when we know what the DNS community will say 
about this and has said so since MARID 2003 and again last year in IETF 
and DNSOPs. I was simply hoping to help "Balance the process" then as I 
was attempted to do again.  If I was in error for trying to get a 
serious issue resolve, then please accept my apology.

Sincerely,

Hector Santos

On 5/1/2013 9:44 AM, Pete Resnick wrote:
> On 4/30/13 7:45 PM, Sam Hartman wrote:
>> So my personal opinion is that this is a valid discussion to be having
>> even if we're having it again in IETF LC.
>
> Folks,
>
> This document is *not* in IETF LC. A particular WG member, who was
> apparently upset with the tone of the argument on the SPFBIS and DNSEXT
> list, expressed his upset by cross-posting to the IETF list, claiming
> this had something to do with the "IETF Diversity" topic.
>
> Then a bunch of other SPFBIS and DNSEXT folks blindly used "Reply-All",
> resulting in us all seeing this discussion.
>
> I will leave it to the chairs/sergeants-of-arms of the respective lists
> to decide how they want to deal with this, but personally I think this
> discussion is not useful to have on the IETF list at the moment and
> suggest that folks be more careful of their use of "Reply-All". I also
> suggest that cross-posting to a new list without noting that in the body
> of the message is bad netiquette.
>
> pr
>


From fred@cisco.com  Thu May  2 08:19:50 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D055321F8E9A for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.542
X-Spam-Level: 
X-Spam-Status: No, score=-110.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vx3dYn4IHsN5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:19:45 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 50ED421F8C20 for <ietf@ietf.org>; Thu,  2 May 2013 08:19:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=555; q=dns/txt; s=iport; t=1367507985; x=1368717585; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=q1b2C+IdyigopkD29g5CzRBYYgrduP1/1gOjQxFUvig=; b=jPDAebHpL9OrFM+Doc5QuVQ6hhzNi1Frn9mm4/pCaq9SfF7s0UrqNhxs FOEQdXidazBVmDDN7DUMKD6L5bM8+kWEwgocIp/0kOFC+9YBW7F1oSCyr vNMjoFzCkHbK6WMsvrVVPISwFlL8U5twWR6OsYlTCN6+e0L400JpQecJw A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIFAAaDglGtJXHA/2dsb2JhbABSgweDJ7w0fxZ0gh8BAQEDAXkFCwIBCCIkMiUCBA4FCId+BsE+jnMCMQeCcmEDiF+ffoMNgic
X-IronPort-AV: E=Sophos;i="4.87,597,1363132800"; d="scan'208";a="205670982"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-7.cisco.com with ESMTP; 02 May 2013 15:19:44 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r42FJiwa024324 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 May 2013 15:19:44 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.83]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.02.0318.004; Thu, 2 May 2013 10:19:44 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Long review tail
Thread-Topic: Long review tail
Thread-Index: AQHOR0T0Oy/2VZI1w0KRKLMgoAiumZjyVD4AgAAB9wA=
Date: Thu, 2 May 2013 15:19:43 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8308A2@xmb-rcd-x09.cisco.com>
References: <8C48B86A895913448548E6D15DA7553B830783@xmb-rcd-x09.cisco.com> <51828266.6040303@cs.tcd.ie>
In-Reply-To: <51828266.6040303@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <12928B3DC94A0B4B825184203A62D23D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org> list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 15:19:50 -0000

On May 2, 2013, at 8:12 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
 wrote:

> When asked if more could be done, (without any specific proposal
> for what to do) the response was that increasing the workload
> would maybe lead to a significant drop in that 80% figure since
> secdir folks are also busy with their day-jobs. So increasing
> the workload for reviewers is tricky.

Sounds like we need more security reviewers. Easier said than done, I know.=
 I might suggest polling people who have done documents in the security are=
a.=

From allison.mankin@gmail.com  Thu May  2 08:21:20 2013
Return-Path: <allison.mankin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53DAE21F8F26 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ljxlfv1qMRDP for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:21:19 -0700 (PDT)
Received: from mail-bk0-x22f.google.com (mail-bk0-x22f.google.com [IPv6:2a00:1450:4008:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id EDE1621F8EA5 for <ietf@ietf.org>; Thu,  2 May 2013 08:21:17 -0700 (PDT)
Received: by mail-bk0-f47.google.com with SMTP id jg9so308673bkc.6 for <ietf@ietf.org>; Thu, 02 May 2013 08:21:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=EVV5CLw+8yISsgTqia2hp4WQkv0maG/y9naAKivzcRA=; b=q0Rl2EDUm0pub5GN8yLPHntecAVaZiulKCWf9GSUtQymRiTwP6F+sAtjDvI4zZ/1ei nf81/FluhNJEEEaGoN0nrFyiuHsOQ9QeGulTLW5siLnvL8ibGWPiQK6xSY8oCEJLRunG rsbxpGIZ3RnHfxDPWY5R3l04OKeyubzHR3wkLqBnjuKtfOEarO13kO8Xv6dPFAL2H1M2 Ym8rCDCCOV0gw42I5XTsuhHh/6/tbG6FiVCutChqsmf8ShW2rsOcSoDWcS1ZlElmhWXu Gp0ch7cCC4IaaCHY5UUMYRbluQVzrJt0/DR0s52oyUtJcZkPas0+40iJoND2kd8zNqy5 +Dgg==
MIME-Version: 1.0
X-Received: by 10.204.98.77 with SMTP id p13mr2302285bkn.86.1367508076924; Thu, 02 May 2013 08:21:16 -0700 (PDT)
Received: by 10.204.225.15 with HTTP; Thu, 2 May 2013 08:21:16 -0700 (PDT)
Received: by 10.204.225.15 with HTTP; Thu, 2 May 2013 08:21:16 -0700 (PDT)
Date: Thu, 2 May 2013 11:21:16 -0400
Message-ID: <CAP8yD=vHeY72cHTg8t-Yco0_pdTadmM8po89Kv_UeHMi-uLL-Q@mail.gmail.com>
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
From: Allison Mankin <allison.mankin@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=089e011609e827e93b04dbbdc9aa
Cc: Ted Hardie <ted.ietf@gmail.com>, Allison Mankin <amankin@verisign.com>, ietf@ietf.org, Matt Lepinski <mlepinski@bbn.com>, Martin Stiemerling <martin.stiemerling@neclab.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 15:21:20 -0000

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

I'm glad folks have brought this up.

I contacted Jari about this the other day and he has advised me to get
started on the 2013 nomcom volunteer recruiting now, even though we have a
period of overlap with the 2012 nomcom. This happened at least once before;
we have an overriding concern not to cause the 2013 schedule to slip.

I'll be sending out a first volunteer-rousing message in the next day or so.

Allison

On May 2, 2013, at 3:58 AM, SM wrote:

)

The NomCom Chair posted a statement on March 9 [1] where it is mentioned
that:

"The Nomcom will continue its work until all open positions are filled."

There is an open position which has not been filled. Is NomCom 2012 still
continuing its work?

The IETF usually has a NomCom Chair. Who is the current NomCom Chair [2]?

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

<p>I&#39;m glad folks have brought this up.</p>
<p>I contacted Jari about this the other day and he has advised me to get s=
tarted on the 2013 nomcom volunteer recruiting now, even though we have a p=
eriod of overlap with the 2012 nomcom. This happened at least once before; =
we have an overriding concern not to cause the 2013 schedule to slip.</p>

<p>I&#39;ll be sending out a first volunteer-rousing message in the next da=
y or so.</p>
<p>Allison</p>
<p>On May 2, 2013, at 3:58 AM, SM wrote:</p>
<p> )</p>
<p>The NomCom Chair posted a statement on March 9 [1] where it is mentioned=
 that:</p>
<p>&quot;The Nomcom will continue its work until all open positions are fil=
led.&quot;</p>
<p>There is an open position which has not been filled. Is NomCom 2012 stil=
l continuing its work?</p>
<p>The IETF usually has a NomCom Chair. Who is the current NomCom Chair [2]=
?</p>

--089e011609e827e93b04dbbdc9aa--

From amankin@verisign.com  Thu May  2 04:51:49 2013
Return-Path: <amankin@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 C87D721F98E3 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 04:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tvYXkZ81v1s5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 04:51:44 -0700 (PDT)
Received: from exprod6og118.obsmtp.com (exprod6og118.obsmtp.com [64.18.1.233]) by ietfa.amsl.com (Postfix) with ESMTP id D9A1121F9656 for <ietf@ietf.org>; Thu,  2 May 2013 04:50:26 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob118.postini.com ([64.18.5.12]) with SMTP ID DSNKUYJTAtBRFgGPde6GdhP66D4yLIdmtV+I@postini.com; Thu, 02 May 2013 04:50:50 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r42BoMHC006294 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 May 2013 07:50:22 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Thu, 2 May 2013 07:50:21 -0400
From: "Mankin, Allison" <amankin@verisign.com>
To: SM <sm@resistor.net>
Subject: Re: Do we have an estimated date for completing the IESG  selection process for this year?
Thread-Topic: Do we have an estimated date for completing the IESG selection process for this year?
Thread-Index: AQHORwsHF0VhIMmcQ06uPaLK+QayZZjyC2sA
Date: Thu, 2 May 2013 11:50:21 +0000
Message-ID: <E245BD46-F6D8-4FA1-A462-C0339DAF128B@verisign.com>
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com> <517FE160.4090909@neclab.eu> <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com> <51820874.3030006@neclab.eu> <6.2.5.6.2.20130501233948.0c9eef70@resistor.net>
In-Reply-To: <6.2.5.6.2.20130501233948.0c9eef70@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0E26AE88C9A94C4F8EB5313D1C6C9B1F@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 02 May 2013 08:27:11 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, "<ietf@ietf.org>" <ietf@ietf.org>, Matt Lepinski <mlepinski@bbn.com>, Martin Stiemerling <martin.stiemerling@neclab.eu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 11:51:49 -0000

Hi,

I contacted Jari about this the other day and he has advised me to get star=
ted on the 2013 nomcom volunteer recruiting now, even though we have a peri=
od of overlap with the 2012 nomcom.  This happened at least once before; we=
 have an overriding concern not to cause the 2013 schedule to slip.

I'll be sending out a first volunteer-rousing message in the next day or so=
.

Allison

On May 2, 2013, at 3:58 AM, SM <sm@resistor.net>
 wrote:

> Hi Matt, Allison,
> At 23:32 01-05-2013, Martin Stiemerling wrote:
>> However, I do not have the answers to your questions, i.e., I am the wro=
ng person to ask or answer.
>=20
> :-)
>=20
> The NomCom Chair posted a statement on March 9 [1] where it is mentioned =
that:
>=20
>  "The Nomcom will continue its work until all open positions are filled."
>=20
> There is an open position which has not been filled.  Is NomCom 2012 stil=
l continuing its work?
>=20
> The IETF usually has a NomCom Chair.  Who is the current NomCom Chair [2]=
?
>=20
> Regards,
> -sm
>=20
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg77720.html
> 2. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg11412.ht=
ml=20


From andy@yumaworks.com  Wed May  1 10:19:11 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A64B21F98A0 for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id joDLu3ytfYnP for <ietf@ietfa.amsl.com>; Wed,  1 May 2013 10:19:10 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 94C5B21F9897 for <ietf@ietf.org>; Wed,  1 May 2013 10:19:10 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id 9so2163132iec.22 for <ietf@ietf.org>; Wed, 01 May 2013 10:19:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=6Hfn1+mp3b6Cu8z8eao6j95Y+uAvsQ4kHk2a20IS4lk=; b=Yr3ZbpWXoaBiPxMXNmn2nf6MXnS5Zs47tB7P4kVjeydqTiiwzqE3SBG9nWwuB5Q4CX JY27NbXJ5FjVTMotYlLQ0LfV5v384yNO4YfRVG1wq1mnnwJVomzrAky3KVBoaVkw6w2O t0h/IVL/pA5jsH+ZfKvGHSrHssbLM0ZYK8dzz+bnrjkjlIVlxYzgtitXdIvCMrwjWJ0s ur8t1fTc4yDBVRcN5NKPWVEKOVJq4oJhtEthr7qTlH7W5wxjxEaoi2KLGhDUd/KpwzgG uYnDJH0y4lY+sUuw+iZAxX3tgz8fqJyZ6c2iSmihmO1neMEQELKabv1iDbssy8C+pvpS 5thg==
MIME-Version: 1.0
X-Received: by 10.50.114.195 with SMTP id ji3mr2127985igb.67.1367428750004; Wed, 01 May 2013 10:19:10 -0700 (PDT)
Received: by 10.231.125.202 with HTTP; Wed, 1 May 2013 10:19:09 -0700 (PDT)
In-Reply-To: <32577.1367426027@sandelman.ca>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca>
Date: Wed, 1 May 2013 10:19:09 -0700
Message-ID: <CABCOCHQXnqvH9esMSAXnv7mm6nPuK=ZvWdpSzh3DGMg1+2KPsA@mail.gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
From: Andy Bierman <andy@yumaworks.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=089e0122ac46e6634a04dbab5048
X-Gm-Message-State: ALoCoQlncPcUF4QlfGfi3e/u/7isIKQ2mMlwTEGs0dNGjbeSQCIHVuMe5VvnrLpUeXx9wUzyEVke
X-Mailman-Approved-At: Thu, 02 May 2013 08:27:11 -0700
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, 01 May 2013 17:19:11 -0000

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

On Wed, May 1, 2013 at 9:33 AM, Michael Richardson <mcr+ietf@sandelman.ca>wrote:

> <#part sign=pgpmime>
>
> >>>>> "Jari" == Jari Arkko <jari.arkko@piuha.net> writes:
>     Jari> I wrote a blog article about how we do a fairly significant
>     Jari> amount of reviews and changes in the late stages of the IETF
>     Jari> process. Next week the IESG will be having a retreat in
>     Jari> Dublin, Ireland. As we brought this topic to our agenda, Pete
>     Jari> and I wanted to raise the issue here and call for feedback &
>     Jari> ideas for improving the situation with all of you.
>
>     Jari> http://www.ietf.org/blog/2013/05/balancing-the-process/
>
> I'll repeat what has been said repeatedly in the newtrk and related
> discussions.  The step from ID to "RFC" is too large because we are
> essentially always aiming for "STD" rather than "PS".
>
>

I don't think this helps.  We want the highest quality documents
possible for developers to translate into implementations.

IMO, the answer is to identify cross-area issues early,
and more importantly, get early cross-area reviewers to help
avoid bad decisions that won't make it through IESG review.
Maybe a cross-area expert needs to join a design team
for awhile to make sure good decisions are made.

The ADs need to make sure these early reviews get
staffed and completed.  Maybe additional people
(directorate?) helps manage this process.


Andy



If we are unwilling to bring "RFC" back to a place were it does not
> equal STD, then we need to create a new category of document which
> amounts to "fully baked ID".  Things like IANA allocations could occur
> at that point.
>
>
> In the days of dot-boom it was not unusual to see widespread
> implementation very early in the ID process and even interop and
> experimental deployment.   While this still occurs for quite a number of
> things (and sometimes it's a problem that the ID can not be changed as a
> result), there is an equal amount of "wait for the RFC to come out".
>
>
> I believe that we probably need to simply do less.
> Or perhaps we've reached the n^2 overhead problem, and since resources
> are less(%), if we can't increase resources allocated to overhead, then
> it's time to reduce n:  the IETF should fork and/or shard somehow.
>
>
> (%)-it's not just about $$ invested, it's also, I think, that after
>     many years of caffeine and sugar, many of us are simply
>     immune to their effects, and/or have given them up.
>
>
> (2)-by adding an intermediate step in the "ID" process, I haven't
>     removed the "heavy" part of the process, I've just redefined the
>     process so that it's no longer at the "tail" of the process.
>     This is, I admit, akin to adjusting the definition of unemployment.
>
>     But, we can all agree when an ID is baked enough for the WG to
>     consider it deployable, then we will actually get to the "running
>     code" part sooner, which frankly is the only real way to get
>     real experience.
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh
> networks [
> ]   Michael Richardson, Sandelman Software Works        | network
> architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails
>    [
>
>
>
>

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

<br><br><div class=3D"gmail_quote">On Wed, May 1, 2013 at 9:33 AM, Michael =
Richardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" t=
arget=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
&lt;#part sign=3Dpgpmime&gt;<br>
<br>
&gt;&gt;&gt;&gt;&gt; &quot;Jari&quot; =3D=3D Jari Arkko &lt;<a href=3D"mail=
to:jari.arkko@piuha.net">jari.arkko@piuha.net</a>&gt; writes:<br>
=A0 =A0 Jari&gt; I wrote a blog article about how we do a fairly significan=
t<br>
=A0 =A0 Jari&gt; amount of reviews and changes in the late stages of the IE=
TF<br>
=A0 =A0 Jari&gt; process. Next week the IESG will be having a retreat in<br=
>
=A0 =A0 Jari&gt; Dublin, Ireland. As we brought this topic to our agenda, P=
ete<br>
=A0 =A0 Jari&gt; and I wanted to raise the issue here and call for feedback=
 &amp;<br>
=A0 =A0 Jari&gt; ideas for improving the situation with all of you.<br>
<br>
=A0 =A0 Jari&gt; <a href=3D"http://www.ietf.org/blog/2013/05/balancing-the-=
process/" target=3D"_blank">http://www.ietf.org/blog/2013/05/balancing-the-=
process/</a><br>
<br>
I&#39;ll repeat what has been said repeatedly in the newtrk and related<br>
discussions. =A0The step from ID to &quot;RFC&quot; is too large because we=
 are<br>
essentially always aiming for &quot;STD&quot; rather than &quot;PS&quot;.<b=
r>
<br></blockquote><div><br></div><div><br></div><div>I don&#39;t think this =
helps. =A0We want the highest quality documents</div><div>possible for deve=
lopers to translate into implementations.</div><div><br></div><div>IMO, the=
 answer is to identify cross-area issues early,</div>
<div>and more importantly, get early cross-area reviewers to help</div><div=
>avoid bad decisions that won&#39;t make it through IESG review.</div><div>=
Maybe a cross-area expert needs to join a design team</div><div>for awhile =
to make sure good decisions are made.</div>
<div><br></div><div>The ADs need to make sure these early reviews get</div>=
<div>staffed and completed. =A0Maybe additional people</div><div>(directora=
te?) helps manage this process.</div><div><br></div><div><br></div><div>And=
y</div>
<div><br></div><div><br></div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
If we are unwilling to bring &quot;RFC&quot; back to a place were it does n=
ot<br>
equal STD, then we need to create a new category of document which<br>
amounts to &quot;fully baked ID&quot;. =A0Things like IANA allocations coul=
d occur<br>
at that point.<br>
<br>
<br>
In the days of dot-boom it was not unusual to see widespread<br>
implementation very early in the ID process and even interop and<br>
experimental deployment. =A0 While this still occurs for quite a number of<=
br>
things (and sometimes it&#39;s a problem that the ID can not be changed as =
a<br>
result), there is an equal amount of &quot;wait for the RFC to come out&quo=
t;.<br>
<br>
<br>
I believe that we probably need to simply do less.<br>
Or perhaps we&#39;ve reached the n^2 overhead problem, and since resources<=
br>
are less(%), if we can&#39;t increase resources allocated to overhead, then=
<br>
it&#39;s time to reduce n: =A0the IETF should fork and/or shard somehow.<br=
>
<br>
<br>
(%)-it&#39;s not just about $$ invested, it&#39;s also, I think, that after=
<br>
=A0 =A0 many years of caffeine and sugar, many of us are simply<br>
=A0 =A0 immune to their effects, and/or have given them up.<br>
<br>
<br>
(2)-by adding an intermediate step in the &quot;ID&quot; process, I haven&#=
39;t<br>
=A0 =A0 removed the &quot;heavy&quot; part of the process, I&#39;ve just re=
defined the<br>
=A0 =A0 process so that it&#39;s no longer at the &quot;tail&quot; of the p=
rocess.<br>
=A0 =A0 This is, I admit, akin to adjusting the definition of unemployment.=
<br>
<br>
=A0 =A0 But, we can all agree when an ID is baked enough for the WG to<br>
=A0 =A0 consider it deployable, then we will actually get to the &quot;runn=
ing<br>
=A0 =A0 code&quot; part sooner, which frankly is the only real way to get<b=
r>
=A0 =A0 real experience.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
] =A0 =A0 =A0 =A0 =A0 =A0 =A0 Never tell me the odds! =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 | ipv6 mesh networks [<br>
] =A0 Michael Richardson, Sandelman Software Works =A0 =A0 =A0 =A0| network=
 architect =A0[<br>
] =A0 =A0 <a href=3D"mailto:mcr@sandelman.ca">mcr@sandelman.ca</a> =A0<a hr=
ef=3D"http://www.sandelman.ca/" target=3D"_blank">http://www.sandelman.ca/<=
/a> =A0 =A0 =A0 =A0| =A0 ruby on rails =A0 =A0[<br>
<br>
<br>
<br>
</font></span></blockquote></div><br>

--089e0122ac46e6634a04dbab5048--

From leo.liubing@huawei.com  Thu May  2 04:02:48 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 314B621F99A2; Thu,  2 May 2013 04:02:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2o2wosR0FX7m; Thu,  2 May 2013 04:02:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4A92421F97D9; Thu,  2 May 2013 04:02:42 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ASJ52063; Thu, 02 May 2013 11:02:40 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 2 May 2013 12:01:40 +0100
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Thu, 2 May 2013 12:02:34 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.13]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.01.0323.007; Thu, 2 May 2013 19:02:31 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>
Subject: RE: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
Thread-Topic: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
Thread-Index: AQHORcBlVceOTpKzJEa6ksAFu9J9J5jxsrWw
Date: Thu, 2 May 2013 11:02:30 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com>
In-Reply-To: <517FF231.3080700@nostrum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 02 May 2013 08:27:12 -0700
Cc: "gen-art@ietf.org" <gen-art@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: Thu, 02 May 2013 11:02:48 -0000

Hi, Robert

Thanks a lot for your continuous careful review.
Please see replies inline.

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Wednesday, May 01, 2013 12:33 AM
> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>=20
> Document: draft-ietf-6renum-gap-analysis-05.txt
> Reviewer: Robert Sparks
> Review Date: April 1, 2013
> IETF LC End Date: April 10, 2013
> IESG Telechat date: May 16, 2013
>=20
> Summary: Ready with nits (that border on minor issues)
>=20
> This update improved the readability significantly, and addressed my
> major concern about being able to build a list of the gaps. Thank you.
>=20
> There are a few issues from my last call review that are still not
> addressed.
> I have left the classification of minor issue vs nits the same as the
> original review to make referring to the earlier review easier,
> but please consider all of these Nits. The IESG will need to decide
> whether to escalate them.
>=20
> I've trimmed away the points that were addressed.
>=20
> On 4/1/13 3:46 PM, Robert Sparks wrote:
> > ----------------------
> > Minor issues:
> >
> > The document currently references
> > draft-chown-v6ops-renumber-thinkabout several times.
> > That document is long expired (2006). It would be better to simply
> > restate what is
> > important from that document here and reference it only once in the
> > acknowlegements
> > rather than send the reader off to read it.
> This version still references that long expired draft. There was also
> conversation on apps-discuss
> about making that reference normative. IMHO, this is not the right way
> to treat the RFC series, and
> strongly encourage moving the text that you want to reference into
> something that will
> become an RFC.

[Bing] Maybe Brian's suggestion of putting some texts into an appendix is a=
 good way. We'll discuss this problem when make the next time update.

> > Should section 8 belong to some other document? It looks like
> > operational renumbering
> > advice/considerations, but doesn't seem to be exploring renumbering
> > gaps, except for
> > the very short section 8.2 which says "we need a better mechanism"
> > without much explanation.
> Afaict, this wasn't addressed at all. In particular, "we need a better
> mechanism" is still all that
> section 8.2 says.

[Bing] Sorry for leaving it out. Will do in next update.

> >
> > Section 5.1, first bullet. The list below "the impact of ambiguous M/O
> > flags" says things like
> > "there is no standard" and "it is unspecified". I think you are trying
> > to say that there is
> > ambiguity in what's written, not that nothing's written. This entire
> > list would benefit from
> > being recast in terms of what needs to be done (what are the gaps?).
> This text remains unmodified.

[Bing] We made revision focusing on explaining "what are the gaps", but the=
 texts change was omitted, will do in next update.

> > ----------------------
> > Nits/editorial comments:
> >
> > There are a few sentences ending with "etc." in the document. Please
> > consider deleting the
> > word from the list - it doesn't help each sentence make its point.
> There were some changes, but mostly these still exist. I'll leave
> pressing this point further to the RFC Editor.

[Bing] A professional language/editorial check would be helpful.=20

> >
> > Seciton 7.1: The first bullet does not parse. If I guess its meaning
> > correctly
> > (that it would be benificial to tell hosts that local DNS has been
> > updated and
> > they may want to make fresh queries), please be careful with the
> > wording. The
> > hosts don't know which names are likely to resolve locally.
> This text remained unchanged, and when coming back to the document for a
> re-review
> (which is somewhat like coming back to an RFC you've read before just
> for reference),
> it's even harder to understand what it's trying to say than it was when
> reading the document
> linearly.
>=20
> I think you are trying to say
> "A notification mechanism may be needed to indicate _to_ hosts that a
> renumbering event has _changed how local recursive DNS servers will
> respond_. That mechanism may also need to indicate that such a change
> will happen at a specific time in the future."

[Bing] I think it's a better description. Will update, thanks much.=20

>=20
> >
> > Section 7.1, third bullet - This isn't obviously about notification.
> > Why is it
> > in this section? What's the gap this is trying to identify?
> This text was unchanged.

[Bing] For example, if border routers enabled egress filtering based on the=
 SIP, then the router need to know the renumbering events on some internal =
nodes. We'll make it clear in the next version.

> > Section 9.4 - what is it about these that make them gaps, much less
> > unsolvable gaps.
> > Is this discussion in the wrong section of the document?
> This is now section 10.3 and is mostly unchanged. It's still not clear
> why this discussion is in the "unsolvable gaps" section.

[Bing] We considered the two points (ID/Locator overloading in transport la=
yer & address caching in app layer ) are too fundamental that might not be =
proper to modify them just in terms of renumbering.

Best regards,
Bing

From stephen.farrell@cs.tcd.ie  Thu May  2 08:32:25 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B28021F8FD6 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.626
X-Spam-Level: 
X-Spam-Status: No, score=-103.626 tagged_above=-999 required=5 tests=[AWL=-1.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fhrlNUVthBZX for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 08:31:43 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 79CB721F86F7 for <ietf@ietf.org>; Thu,  2 May 2013 08:31:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CF1BCBE9A; Thu,  2 May 2013 16:31:20 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjmAAzueiuwY; Thu,  2 May 2013 16:31:20 +0100 (IST)
Received: from [IPv6:2001:770:10:203:cdfc:bf00:7a90:e70e] (unknown [IPv6:2001:770:10:203:cdfc:bf00:7a90:e70e]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 7494EBE8E; Thu,  2 May 2013 16:31:20 +0100 (IST)
Message-ID: <518286C9.2000501@cs.tcd.ie>
Date: Thu, 02 May 2013 16:31:21 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Long review tail
References: <8C48B86A895913448548E6D15DA7553B830783@xmb-rcd-x09.cisco.com> <51828266.6040303@cs.tcd.ie> <8C48B86A895913448548E6D15DA7553B8308A2@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8308A2@xmb-rcd-x09.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org> list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 15:32:25 -0000

On 05/02/2013 04:19 PM, Fred Baker (fred) wrote:
> 
> On May 2, 2013, at 8:12 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
>  wrote:
> 
>> When asked if more could be done, (without any specific proposal
>> for what to do) the response was that increasing the workload
>> would maybe lead to a significant drop in that 80% figure since
>> secdir folks are also busy with their day-jobs. So increasing
>> the workload for reviewers is tricky.
> 
> Sounds like we need more security reviewers. Easier said than done, I know. I might suggest polling people who have done documents in the security area.
> 

Worth a look. We already have quite a few though. [1]

S.

[1] http://trac.tools.ietf.org/area/sec/trac/wiki/SecDirReviewers

From sm@elandsys.com  Thu May  2 09:05:13 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89D1421F901F for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 09:05:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mLwSWOwxFgOW for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 09:05:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 620EF21F8FFC for <ietf@ietf.org>; Thu,  2 May 2013 09:05:12 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.136.99]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r42G4kXC011198 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 May 2013 09:04:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367510700; bh=CtM9etWIHoYawXcKkDiq4FnHdNHrrguprDi2HSl/p38=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2J2cpy/lxg6upNkHVJp/1kaAO2+tWYbWd7BIiBTQBxYa+25GqMa5G35EM+/sAFEB6 vDhbWOJOeBQ996+X5LxYrUagy+dz4sOiMdohHKiTDOnb4FGJbt/lGAUPbnrroGL1Vf qnY0xeVx1vxQBQXJTP85YAfmGt68Mj5lvl60MsKg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367510700; i=@elandsys.com; bh=CtM9etWIHoYawXcKkDiq4FnHdNHrrguprDi2HSl/p38=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pHVQCBkPnagXnN++kpzU1w9j61RuKzvBfkW9+cmQ9rz6dY341zhAMSkxfBnsicOui fuGZ1urEhEqD7kLyAgE5uj2Lt5T8YIgIz/jYXRqgHFYLgLKJnIRsmnFwz3ehlgGp1X hH+FVt2I/U2DrVYV/4Ua+FFJMG6QwzsGtR4SfO8I=
Message-Id: <6.2.5.6.2.20130502060904.0b38f518@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 May 2013 09:02:08 -0700
To: Alessandro Vesely <vesely@tana.it>, Doug Barton <dougb@dougbarton.us>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: A note about draft-ietf-spfbis-4408bis (was: [spfbis] [dnsext] Obsoleting SPF RRTYPE)
In-Reply-To: <51822FD6.1080805@tana.it>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 16:05:13 -0000

Hi Alessandro, Doug,

My task is to keep draft-ietf-spfbis-4408bis moving forward and to 
maintains a critical and technical perspective of the draft.  The two 
weeks Working Group Last Call for draft-ietf-spfbis-4408bis-14 was 
announced on April 9, 2013 [1].  The document shepherd review was 
posted to the SPFBIS mailing list on April 23 [2].

I wasn't sure about some text in Section 5 of the draft.  I posted a 
question to the 6MAN mailing list [3].  I posted another question 
about the DNS Parameters registry to the DNSEXT mailing list 
[4].  The replies to that question generated about 200 messages on 
the DNSEXT and SPFBIS mailing lists.  I read all these messages while 
following up on the document shepherd review.  In my individual 
opinion there was a concern about "Obsoleting SPF RRTYPE".  A message 
[5] about the topic was posted to the ietf@ietf.org mailing list on 
April 29 while the topic was being discussed on the SPFBIS mailing 
list.   There was a message about shutting down the thread on the 
SPFBIS mailing list.  I humbly suggested [6] leaving the matter to 
the SPFBIS WG Chairs.  I discussed the matter with Andrew Sullivan on 
April 30.  A message [7] was posted to the SPFBIS mailing list after that.

I read the message posted by Doug Barton about an IETF Last Call 
objection [8].  I'll comment about the path of the 
draft-ietf-spfbis-4408bis.  There are issues which were raised during 
the Working Group Last Call.  There are also three directorate/team 
reviews.    If the issues and reviews are addressed there will be a 
publication request for draft-ietf-spfbis-4408bis.  The Responsible 
Area Director will likely review the draft.  If that step is cleared 
there will be a Last Call announcement for 
draft-ietf-spfbis-4408bis.  If anyone has any objection I suggest 
raising it during the Last Call.

If you have any questions about the above please let me know so that 
we can talk about it.

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/spfbis/current/msg03347.html
2. http://www.ietf.org/mail-archive/web/spfbis/current/msg03414.html
3. http://www.ietf.org/mail-archive/web/ipv6/current/msg17638.html
4. http://www.ietf.org/mail-archive/web/dnsext/current/msg13025.html
5. http://www.ietf.org/mail-archive/web/ietf/current/msg78927.html
6. http://www.ietf.org/mail-archive/web/spfbis/current/msg03663.html
7. http://www.ietf.org/mail-archive/web/spfbis/current/msg03681.html
8. http://www.ietf.org/mail-archive/web/ietf/current/msg78955.html


From cabo@tzi.org  Thu May  2 09:17:30 2013
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 05D6821F9104 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 09:17:30 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 893h4JbaQXiE for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 09:17:24 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id E1F6321F90CD for <ietf@ietf.org>; Thu,  2 May 2013 09:17:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r42GHECP025246; Thu, 2 May 2013 18:17:14 +0200 (CEST)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 3C0D0396D; Thu,  2 May 2013 18:17:14 +0200 (CEST)
Subject: Re: call for ideas: tail-heavy IETF process
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com>
Date: Thu, 2 May 2013 18:17:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im> <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1503)
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Thu, 02 May 2013 16:17:30 -0000

On May 2, 2013, at 07:21, "Eggert, Lars" <lars@netapp.com> wrote:

> Yeah, all kinds of issues, but if we created a new thing here in =
between WGLC and PS, the broader industry would never understand.

That is a matter of naming and marketing ("candidate RFC"?).

The "this is baked, go and implement it" signal to the outside is only =
one aspect, though.

The other two things that were mentioned:
-- get the cross-area review going;
-- get the numbers (IANA).

As we are seeing e.g., with MPL (ROLL WG) right now, the latter can go =
wrong (aspects of the protocol still change, the allocation has to =
change with it).
But that isn't too much of a cost in most cases.

Re the cross-area review:  Doing it earlier doesn't mean doing more.  In =
theory.
In practice, not-really-baked stuff comes up and needs to be reviewed n =
times.
(As an appsdir reviewer, I have seen that happen.)

I think the WGLC is the wrong process step to define something as baked.
-- too late, because there may still be some (identifiable) random =
corner that the WG wants to fix;
-- too early, because the WG may be deluded or mismanaged.
Much better would be a simple collusion between WG chairs and sponsoring =
AD.
(In any sensible WG, you would still involve the WG, of course.)

Gr=FC=DFe, Carsten


From hannes.tschofenig@gmx.net  Thu May  2 11:15:05 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54AF221F9075 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 11:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.448
X-Spam-Level: 
X-Spam-Status: No, score=-102.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C90+d3z+V6Fw for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 11:15:00 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD2321F905B for <ietf@ietf.org>; Thu,  2 May 2013 11:14:59 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.29]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0La1J5-1UAxUQ3AEv-00llPS for <ietf@ietf.org>; Thu, 02 May 2013 20:14:47 +0200
Received: (qmail invoked by alias); 02 May 2013 18:14:47 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp029) with SMTP; 02 May 2013 20:14:47 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/Ai6RCIm3AQzb+WSKABESZQPLEQU6yDSg5p8p2An AaL0Quxc7Z6Pzg
Message-ID: <5182AD0F.4010204@gmx.net>
Date: Thu, 02 May 2013 21:14:39 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Thu, 02 May 2013 18:15:05 -0000

Hi Jari, Hi Pete,

three issues come to my mind:

a) From several past discussions it is clear that we are not really able 
(maybe not willing) to change our processes. Even the smallest change 
faces a lot of resistance. Due to the resistance our response is to 
back-off and we solve a different problem instead.

Recent example: Look at the discussion from late last year that was 
triggered by the interactions regarding the WhatWG and Ian Hickson. This 
was a discussion about our long document production process. Some time 
later the discussions shifted to the discussion of an experiment to 
shorten the last call when running code is available, which then did not 
go anywhere and was only recently resurrected.

b) There is no interest to research where delay really happen. Your 
statistics just tell that there is delay but not why (of course). From 
my own experience I noticed that there are many reasons for delay and I 
am not sure I can blame it to the IESG reviews for most of the delay. It 
is only during the IESG review phase when the problems surface that 
could have been tackled much earlier.

Without looking at a number of cases we might focus on the wrong issues. 
Maybe, but I am not sure, there is something that can be generalized 
from some individual cases.

I am happy to work with someone else to go through a couple of different 
IETF activities that did not really go as planned to "reconstruct" what 
went wrong. I suggested this in the past but it is of course not 
fashionable and exciting.

c) For a number of IETF activities it does not matter whether they take 
a long time because the deployment phase that happens afterwards will 
take 5 times longer (in the positive case). The timing matters and even 
if something takes much longer than expected it might still be too early 
or does not meet the expectations of the community. I would rather 
prefer to spent more time on a topic and do it properly (and by properly 
I do not only focus on the standardization work but also on the 
outreach) than to publish documents quickly to have good statistics. 
Finding a common understanding and reaching conclusions with many 
different parties just takes a long time. Finding an agreement among 
your close friends is easy. In essence, we do not only want "good" 
standards but we also want those that make the Internet work better.

Ciao
Hannes

PS: I just want to add that I still dislike DISCUSSes that make me 
re-write documents just because an English native speaker believes 
(probably rightfully so) that he knows how to write the text better (or 
at least in a different way). (hint, hint)

On 05/01/2013 06:33 PM, Jari Arkko wrote:
> I wrote a blog article about how we do a fairly significant amount of
> reviews and changes in the late stages of the IETF process. Next week
> the IESG will be having a retreat in Dublin, Ireland. As we brought
> this topic to our agenda, Pete and I wanted to raise the issue here
> and call for feedback & ideas for improving the situation with all of
> you.
>
> http://www.ietf.org/blog/2013/05/balancing-the-process/
>
> Jari
>


From ynir@checkpoint.com  Thu May  2 12:16:32 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0F3E21F8B38 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:16:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o1aRMv9bOK8Q for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:16:27 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 84C3721F8640 for <ietf@ietf.org>; Thu,  2 May 2013 12:16:26 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r42JGGxB022822; Thu, 2 May 2013 22:16:24 +0300
X-CheckPoint: {5182BA32-2D-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Thu, 2 May 2013 22:16:16 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Do we have an estimated date for completing the IESG selection process for this year?
Thread-Topic: Do we have an estimated date for completing the IESG selection process for this year?
Thread-Index: AQHORzmo/yYkCE7k+EC1z0xAW5S1h5jyEkyA
Date: Thu, 2 May 2013 19:16:15 +0000
Message-ID: <18AF3FA5-B627-49FA-B165-FF3E485749CD@checkpoint.com>
References: <CA+9kkMDLprWdE3P3DHbkdn3_isTyu6xuaizcnghaKcsEZuE=_g@mail.gmail.com> <517FE160.4090909@neclab.eu> <8C7F42A8-9E8F-4953-866D-8D268EF9C52B@checkpoint.com> <51820874.3030006@neclab.eu> <6.2.5.6.2.20130501233948.0c9eef70@resistor.net> <1220.1367501559@sandelman.ca>
In-Reply-To: <1220.1367501559@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.112]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 1176a4256b3b09e7b26d484be786e6a6ad294f62bb
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FF628884C81D6D47B05A1D1D67868CAE@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 19:16:32 -0000

On May 2, 2013, at 4:32 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrot=
e:

>=20
>>>>>> "SM" =3D=3D SM  <sm@resistor.net> writes:
>    SM> There is an open position which has not been filled.  Is NomCom
>    SM> 2012 still continuing its work?
>=20
>    SM> The IETF usually has a NomCom Chair.  Who is the current NomCom
>    SM> Chair [2]?=20
>=20
> The nomcom chair continues to do the work.
> The nomcom is in fact meeting in 28 minutes to discuss some issues
> resulting from an action that was taken.
>=20

Ah. And reading Matt's announcement from an hour and a half ago, I guess we=
 know about the action and the issues :)

Yoav


From presnick@qti.qualcomm.com  Thu May  2 12:18:18 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E79621F8C9B for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.384
X-Spam-Level: 
X-Spam-Status: No, score=-106.384 tagged_above=-999 required=5 tests=[AWL=0.215, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8-lAAsXO1Ty for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:18:14 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 06A7221F8D13 for <ietf@ietf.org>; Thu,  2 May 2013 12:18:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1367522294; x=1399058294; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=aR3PfwhXHWZw1uDNn22fNhSUKcQMGB56jeL0xkg+6DQ=; b=wg8tD5E2wG49fHuiMeO1u2nR6z5Py9uE6PL68ioz3gBFghpHVt0dfn8j 565U0EuE6W3iu9R4ed0ty1M+lS81ikbOxCr2R+gQWD1n40rX/BFbXg23t 1KcE7ubJicIPsVZYLy+UEFqJFsHms4v0+mrrm6RTB/sPgN5QaojeU0ULl M=;
X-IronPort-AV: E=Sophos;i="4.87,597,1363158000"; d="scan'208";a="43721370"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 02 May 2013 12:18:13 -0700
X-IronPort-AV: E=Sophos;i="4.87,597,1363158000"; d="scan'208";a="442024380"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 May 2013 12:18:13 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Thu, 2 May 2013 12:18:13 -0700
Message-ID: <5182BBF2.1000009@qti.qualcomm.com>
Date: Thu, 2 May 2013 14:18:10 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net>
In-Reply-To: <5182AD0F.4010204@gmx.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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: Thu, 02 May 2013 19:18:19 -0000

One quick thing:

On 5/2/13 1:14 PM, Hannes Tschofenig wrote:
> From several past discussions it is clear that we are not really able 
> (maybe not willing) to change our processes.

Note that although we did ask the bigger question, the more central 
question relates to what we on the IESG can do all by ourselves (without 
making changes to the formal processes) that we can discuss during our 
IESG meeting next week. So don't limit your thinking to things that 
require process changes; suggested behavior changes on the part of ADs 
are also useful.

> PS: I just want to add that I still dislike DISCUSSes that make me 
> re-write documents just because an English native speaker believes 
> (probably rightfully so) that he knows how to write the text better 
> (or at least in a different way). (hint, hint)

We were supposed to have gotten that hint before. Sometimes we are slow. 
Reminding us is a good thing. :-)

Thanks for your other comments.

pr

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


From dougb@dougbarton.us  Thu May  2 12:22:05 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 906D721F8C9B for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E42jWXj+Txid for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:22:05 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 12AD321F8C69 for <ietf@ietf.org>; Thu,  2 May 2013 12:22:05 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:ac03:33e5:1d63:5739] (unknown [IPv6:2001:470:d:5e7:ac03:33e5:1d63:5739]) by dougbarton.us (Postfix) with ESMTPSA id 3529622B3F; Thu,  2 May 2013 19:22:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1367522524; bh=ecZuH0yeoVOj7BfvKHtnb2rujlEgaa4xV5iO7pqDzzY=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=oPhhFZ8YYoM/3FheX+jfXNg1tPwV+AsDLnEHkOYeN/Pt9j0zOCeH2sovmmfB5KYzV uyMqL/kfOJVqQjqi9E5WGlO24OMiUdHgxuwFiW+CYxWRJGCT825KcoFSISd08KIrXV Rhw+Bn7jRc9ojkSGdeB+1+0xnbGS34rFpcqfATzU=
Message-ID: <5182BCDB.5080100@dougbarton.us>
Date: Thu, 02 May 2013 12:22:03 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net>
In-Reply-To: <6.2.5.6.2.20130502060904.0b38f518@resistor.net>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Andrew Sullivan <ajs@crankycanuck.ca>, 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, 02 May 2013 19:22:05 -0000

On 5/2/2013 9:02 AM, S Moonesamy wrote:
> If anyone has any objection I suggest raising it during the Last Call.

Given that you can be 100% confident that the issue will be raised 
during IETF LC, wouldn't it be better to hash it out in the WG (as we 
have attempted to do)? Or is the WG's position, "we have no intention of 
dealing with this unless we're forced to?"

I'm fully sympathetic with your collective desire to move the process 
forward, and finish your document. The problem is that as it stands the 
document contains a course of action that is not only bad on its face, 
but contrary to a basic architectural principle adopted 4 years ago in 
5507.

Doug


From ajs@anvilwalrusden.com  Thu May  2 12:50:34 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8361E21F8E5F for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwQ7nsLG77Y7 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 12:50:25 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACE321F8C1A for <ietf@ietf.org>; Thu,  2 May 2013 12:50:22 -0700 (PDT)
Received: from crankycanuck.ca (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 7816A8A035 for <ietf@ietf.org>; Thu,  2 May 2013 19:50:20 +0000 (UTC)
Date: Thu, 2 May 2013 15:50:16 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: A note about draft-ietf-spfbis-4408bis
Message-ID: <20130502195015.GA323@crankycanuck.ca>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5182BCDB.5080100@dougbarton.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 19:50:34 -0000

Doug,

No hat.

On Thu, May 02, 2013 at 12:22:03PM -0700, Doug Barton wrote:
> Given that you can be 100% confident that the issue will be raised
> during IETF LC, wouldn't it be better to hash it out in the WG (as
> we have attempted to do)? Or is the WG's position, "we have no
> intention of dealing with this unless we're forced to?"

We _have_ hashed this out in the WG.  As I have noted to you -- now on
three separate lists -- the problem is that we have an actual
interoperability bug in RFC 4408, and we need to fix it.  The WG
evaluated the various alternatives for how to solve that, and having
performed the evaluation the group came to the conclusion that, _in
this specific case_, deprecating RRTYPE 99 is the most reasonable
course of action.

I am not happy about this, but other analyses do not seem to be
supported by any facts, nor by any argument that leads to the
conclusion that an arrangement we would all like better has any chance
of deployment.  This is just a plain fact of the Internet, I think,
and if you think it's not I would like some evidence, please.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From martin.thomson@gmail.com  Thu May  2 13:25:10 2013
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EA9621F8CA0 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 13:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oEkvvvjgk8QT for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 13:25:10 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C38E421F8AD1 for <ietf@ietf.org>; Thu,  2 May 2013 13:25:09 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id s43so823437wey.34 for <ietf@ietf.org>; Thu, 02 May 2013 13:25:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZBIbjb0rCic1u9Bsw+364Mpz5/KmEKFyj7nhhWTY5tc=; b=xBVGdp7jz5/PTcXHeTf66OB0JK+PuzAzK8J+gOPM88FZrCZX0roB+i6CpPiXsp8q0x tVpqLm7oOzd2/V/POSZ4VAE9lLCRYVSzEgCHwrWM57perq5zPF8+YtX2Gpsz1DbWiJFZ 9lky9DLpeVz6HE2gdlabAtv8RGt3YqCqxNy1+7Qvo6WEtMNa8cLyX5ZYfG4DvJixXeTT jL/QJXmYZ1vAmmYTDjLWM+nboHptrtZNXbVVti3+5ne2eZK/+13TYjXl2wIfQJ/WZuaR uo6nvew45nfDV+dZu95/M1Un4qNknrghg3r01wOyTvoIG8IErbTBuZ61J5vvx9IE0V/J ArDg==
MIME-Version: 1.0
X-Received: by 10.194.78.204 with SMTP id d12mr10184907wjx.42.1367526308958; Thu, 02 May 2013 13:25:08 -0700 (PDT)
Received: by 10.194.33.102 with HTTP; Thu, 2 May 2013 13:25:08 -0700 (PDT)
In-Reply-To: <5182AD0F.4010204@gmx.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net>
Date: Thu, 2 May 2013 13:25:08 -0700
Message-ID: <CABkgnnUGjo=XGE9V=7SW=HSgCkbHbtpHuM0w=yeZc2xddK8geA@mail.gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
From: Martin Thomson <martin.thomson@gmail.com>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Content-Type: text/plain; charset=UTF-8
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Thu, 02 May 2013 20:25:10 -0000

Hannes Tschofenig <hannes.tschofenig@gmx.net> wrote:
> There is no interest to research where delay really happen.

This is an important point.  We might want to measure before we cut.

> [...] From my
> own experience I noticed that there are many reasons for delay and I am not
> sure I can blame it to the IESG reviews for most of the delay.

My experience is similar, though not uniformly.  For the most part,
time spent in IESG processing has been short relative to the value
provided, in my opinion.

From john@jlc.net  Thu May  2 13:29:41 2013
Return-Path: <john@jlc.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 39E5F21F8D29 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 13:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.486
X-Spam-Level: 
X-Spam-Status: No, score=-106.486 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Q9MQ2YGaUa5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 13:29:37 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id E296921F8C69 for <ietf@ietf.org>; Thu,  2 May 2013 13:29:36 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 010C033C23; Thu,  2 May 2013 16:29:36 -0400 (EDT)
Date: Thu, 2 May 2013 16:29:36 -0400
From: John Leslie <john@jlc.net>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <20130502202936.GG23227@verdi>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <5182BBF2.1000009@qti.qualcomm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5182BBF2.1000009@qti.qualcomm.com>
User-Agent: Mutt/1.4.1i
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: Thu, 02 May 2013 20:29:41 -0000

Pete Resnick <presnick@qti.qualcomm.com> wrote:
> 
> Note that although we did ask the bigger question, the more central 
> question relates to what we on the IESG can do all by ourselves (without 
> making changes to the formal processes) that we can discuss during our 
> IESG meeting next week. So don't limit your thinking to things that 
> require process changes; suggested behavior changes on the part of ADs 
> are also useful.

   The ADs could do worse than starting from the SIRS draft:

tools.ietf.org/html/draft-carpenter-icar-sirs-01

but as I read through it, I find a number of issues which I'd advise
_not_ trying to resolve. For example:

- All reviews public: not always a good idea;

- Normally posted to WG list: often a bad idea -- to easy for them to
  start a flame-war;

- Standardized summary message: these may be a very poor choice for
  early reviews;

- Selection process: it's far more important that the IESG be comfortable
  with each member.

   OTOH it contains items which SHOULD be taken seriously:

- No change to formal process;

- Formal process to add SIRS members;

- Inactive members fall off the SIRS list;

- WG may request a particular member;

- WG should request more than one reviewer;

- Earlier reviews should consider architectural questions;

- Three review cycle per document should be the minimum.

====

   I also note the overlapping discussion of DNS type SPF...
From: Doug Barton <dougb@dougbarton.us>
> 
> Given that you can be 100% confident that the issue will be raised
> during IETF LC, wouldn't it be better to hash it out in the WG (as we
> have attempted to do)? Or is the WG's position, "we have no intention of
> dealing with this unless we're forced to?"

   In this case, hashing it out on the WG list at this stage seems a
_bad_ idea. If we had gotten a SIRS review right at the beginning, it
could perhaps be discussed on the WG list; but by now it's doubtful
any discussion would change anyone's mind. (And, of course, if the WG
had chosen only SIRS reviewers that agreed with their preferred way
of resolving the issue, the issue _wouldn't_ have been resolved early
in the process...)

   This is on it's way to being a poster-child "late surprise". :^(

> I'm fully sympathetic with your collective desire to move the process
> forward, and finish your document. The problem is that as it stands the
> document contains a course of action that is not only bad on its face,
> but contrary to a basic architectural principle adopted 4 years ago in
> 5507.

  BTW, I agree with Doug Barton that deprecating type SPF has some serious
negatives. The IESG will have to balance WG rough-consensus against
architectural principles; and I see no resolution that won't invite
appeals. :^(

   In a properly designed early-review situation, the issue would have
surfaced early; and it's possible it could have been resolved before
too many folks' positions had hardened...

--
John Leslie <john@jlc.net>  

From brian.e.carpenter@gmail.com  Thu May  2 13:59:37 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94C1021F8B2B for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 13:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.899
X-Spam-Level: 
X-Spam-Status: No, score=-102.899 tagged_above=-999 required=5 tests=[AWL=0.700, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hya7a8+Z6Laj for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 13:59:33 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id E54F421F8A38 for <ietf@ietf.org>; Thu,  2 May 2013 13:59:32 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id jh10so562250pab.31 for <ietf@ietf.org>; Thu, 02 May 2013 13:59:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=nXLHQ8G94kH7lncqH+CR8kO9ylmN2p0DdKAgOqYkAY8=; b=Z9p4cBzLDHZ7nGXKziRu0lpFjxQkBCrBsaJ2v7vqoUvoA6XFMum16pLdeHH/bc+skP UX0abNDwnTKVaMgDUYqL0GZAsxc2PFTDSPgpzeOiLy6fjpf/6vNtY2c23mPTZkANNqMb nkr28r2NZHf+ejmo5rJuuw4Pp2Wd7bb3ZChjPWIgl8KMZiF0qeJm8ua/36HghOjzWQPl raxcIl/18gnH5+2crMwReTjNvjaUncYMzrCPJ0b4rJb54+n4Xq1TM+/b+qY+09OkV1nk kuksz6qtgG9BVmzZFIGDiDNlkYfglvYJ91K3+7MY0IVxsumR4p2z99Uj3NGNCX2W43Ze KcsQ==
X-Received: by 10.66.26.166 with SMTP id m6mr11770672pag.68.1367528372632; Thu, 02 May 2013 13:59:32 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id 10sm8596497pbr.45.2013.05.02.13.59.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 13:59:29 -0700 (PDT)
Message-ID: <5182D3B8.1030304@gmail.com>
Date: Fri, 03 May 2013 08:59:36 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<5182AD0F.4010204@gmx.net> <5182BBF2.1000009@qti.qualcomm.com> <20130502202936.GG23227@verdi>
In-Reply-To: <20130502202936.GG23227@verdi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Thu, 02 May 2013 20:59:37 -0000

Would people like to see a new version of the SIRS draft?

In addition to the questions John raised below, Francis
and others mentioned: lack of reviewers. Also there is the
question of overlap with Area review teams such as secdir,
and there is accumulated experience from Gen-ART (RFC 6385).

Regards
   Brian

On 03/05/2013 08:29, John Leslie wrote:
> Pete Resnick <presnick@qti.qualcomm.com> wrote:
>> Note that although we did ask the bigger question, the more central 
>> question relates to what we on the IESG can do all by ourselves (without 
>> making changes to the formal processes) that we can discuss during our 
>> IESG meeting next week. So don't limit your thinking to things that 
>> require process changes; suggested behavior changes on the part of ADs 
>> are also useful.
> 
>    The ADs could do worse than starting from the SIRS draft:
> 
> tools.ietf.org/html/draft-carpenter-icar-sirs-01
> 
> but as I read through it, I find a number of issues which I'd advise
> _not_ trying to resolve. For example:
> 
> - All reviews public: not always a good idea;
> 
> - Normally posted to WG list: often a bad idea -- to easy for them to
>   start a flame-war;
> 
> - Standardized summary message: these may be a very poor choice for
>   early reviews;
> 
> - Selection process: it's far more important that the IESG be comfortable
>   with each member.
> 
>    OTOH it contains items which SHOULD be taken seriously:
> 
> - No change to formal process;
> 
> - Formal process to add SIRS members;
> 
> - Inactive members fall off the SIRS list;
> 
> - WG may request a particular member;
> 
> - WG should request more than one reviewer;
> 
> - Earlier reviews should consider architectural questions;
> 
> - Three review cycle per document should be the minimum.
> 
> ====
> 
>    I also note the overlapping discussion of DNS type SPF...
> From: Doug Barton <dougb@dougbarton.us>
>> Given that you can be 100% confident that the issue will be raised
>> during IETF LC, wouldn't it be better to hash it out in the WG (as we
>> have attempted to do)? Or is the WG's position, "we have no intention of
>> dealing with this unless we're forced to?"
> 
>    In this case, hashing it out on the WG list at this stage seems a
> _bad_ idea. If we had gotten a SIRS review right at the beginning, it
> could perhaps be discussed on the WG list; but by now it's doubtful
> any discussion would change anyone's mind. (And, of course, if the WG
> had chosen only SIRS reviewers that agreed with their preferred way
> of resolving the issue, the issue _wouldn't_ have been resolved early
> in the process...)
> 
>    This is on it's way to being a poster-child "late surprise". :^(
> 
>> I'm fully sympathetic with your collective desire to move the process
>> forward, and finish your document. The problem is that as it stands the
>> document contains a course of action that is not only bad on its face,
>> but contrary to a basic architectural principle adopted 4 years ago in
>> 5507.
> 
>   BTW, I agree with Doug Barton that deprecating type SPF has some serious
> negatives. The IESG will have to balance WG rough-consensus against
> architectural principles; and I see no resolution that won't invite
> appeals. :^(
> 
>    In a properly designed early-review situation, the issue would have
> surfaced early; and it's possible it could have been resolved before
> too many folks' positions had hardened...
> 
> --
> John Leslie <john@jlc.net>  
> 

From Francis.Dupont@fdupont.fr  Thu May  2 14:38:41 2013
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D82C21F8F06 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 14:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DSNt2-hC0KMM for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 14:38:40 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 0333421F8F1E for <ietf@ietf.org>; Thu,  2 May 2013 14:38:39 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id r42LcAvv092384; Thu, 2 May 2013 23:38:10 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201305022138.r42LcAvv092384@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: call for ideas: tail-heavy IETF process 
In-reply-to: Your message of Wed, 01 May 2013 10:19:09 PDT. <CABCOCHQXnqvH9esMSAXnv7mm6nPuK=ZvWdpSzh3DGMg1+2KPsA@mail.gmail.com> 
Date: Thu, 02 May 2013 23:38:10 +0200
Sender: Francis.Dupont@fdupont.fr
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: Thu, 02 May 2013 21:38:41 -0000

 In your previous mail you wrote:

>  We want the highest quality documents possible for developers to
>  translate into implementations.

=> I am afraid this statement is not fully consistent.

Regards

Francis.Dupont@fdupont.fr

PS: note it is not an attack against you: in fact you gave a good summary
of the deeper issue.

From yaronf.ietf@gmail.com  Thu May  2 14:41:01 2013
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 DD8D121F8F01 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 14:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3N3ZvjzdAZr for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 14:41:01 -0700 (PDT)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id E875421F8EE8 for <ietf@ietf.org>; Thu,  2 May 2013 14:40:56 -0700 (PDT)
Received: by mail-we0-f171.google.com with SMTP id u7so872475wey.30 for <ietf@ietf.org>; Thu, 02 May 2013 14:40:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=m0TNytzGBQE6Y0CRxoKa59eZuzH8y+u+AgsvJpk0vjo=; b=Xqk7OtNeybIRvsve0xsjXD/vygcd0ZpcxrooQQEh5/dJ53qVXtQRvWWcQDpY+kKp04 QMyrJZKo7GuyCjSxh8/5f83qEGIRYMgoOZbkdL8tvtPX+CkG1CY19kNp0dqDfEEvMmIY ykZhMfK04tKw6obwkjnO0vLTP4T+R4bEW8n1KcGQi3ScHr/xauktNhJoI0rWtRXD5bln 1434cRuq2dZHc+ksmINKOneGaTZfDGhX7u68I9lhr4b7QJ60PXYXwLXyxUbyEmSO6s1A 744gRobpwgaJP8MV2f6hYTlES/cXbnavywTAgBLNB4l8cbjfi4QPEPJ8rQ42RLqwSq77 ofsQ==
X-Received: by 10.194.171.74 with SMTP id as10mr10546229wjc.0.1367530855677; Thu, 02 May 2013 14:40:55 -0700 (PDT)
Received: from [10.0.0.3] (bzq-79-177-103-167.red.bezeqint.net. [79.177.103.167]) by mx.google.com with ESMTPSA id eu18sm31062980wid.1.2013.05.02.14.40.54 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 May 2013 14:40:54 -0700 (PDT)
Message-ID: <5182DD64.7040205@gmail.com>
Date: Fri, 03 May 2013 00:40:52 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Language editing (was: tails and such)
References: <mailman.21.1367521206.21891.ietf@ietf.org>
In-Reply-To: <mailman.21.1367521206.21891.ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 21:41:02 -0000

As a non-native English speaker, but a language pedant nonetheless, I 
can empathize with people who put Discusses on badly written documents.

I suggest that we budget for a number of WG drafts per year (say, 20 
IETF-wide) to go through professional, paid-for heavy-duty editing, with 
these goals in mind:

- Improve the readability of some of published documents, because if a 
document is *really* badly written, even the RFC Editor team will not 
save it.
- Improve the level of review, because people can understand the 
document better if they don't need to dig through incorrect or "strange" 
language.
- Allow more non-native speakers to participate in our primary activity 
(back to our "diversity" discussion).

I would suggest that the editing step should take place just before WG 
Last Call, upon a request by a WG chair and with AD approval.

Thanks,
	Yaron

> Date: Thu, 02 May 2013 21:14:39 +0300
> From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
> To: Jari Arkko <jari.arkko@piuha.net>
> Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF list
> 	<ietf@ietf.org>
> Subject: Re: call for ideas: tail-heavy IETF process
> Message-ID: <5182AD0F.4010204@gmx.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
[...]

>
> PS: I just want to add that I still dislike DISCUSSes that make me
> re-write documents just because an English native speaker believes
> (probably rightfully so) that he knows how to write the text better (or
> at least in a different way). (hint, hint)
>

From joelja@bogus.com  Thu May  2 14:49:28 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D2B21F8640 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 14:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1MM3BXpBG1Rt for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 14:49:28 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 51D2521F8619 for <ietf@ietf.org>; Thu,  2 May 2013 14:49:28 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r42LnMWf020273 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 2 May 2013 21:49:22 GMT (envelope-from joelja@bogus.com)
Message-ID: <5182DF5D.3010509@bogus.com>
Date: Thu, 02 May 2013 14:49:17 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net>
In-Reply-To: <5182AD0F.4010204@gmx.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.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 02 May 2013 21:49:22 +0000 (UTC)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Thu, 02 May 2013 21:49:28 -0000

On 5/2/13 11:14 AM, Hannes Tschofenig wrote:
>
> b) There is no interest to research where delay really happen. Your 
> statistics just tell that there is delay but not why (of course). From 
> my own experience I noticed that there are many reasons for delay and 
> I am not sure I can blame it to the IESG reviews for most of the 
> delay. It is only during the IESG review phase when the problems 
> surface that could have been tackled much earlier.
>
> Without looking at a number of cases we might focus on the wrong 
> issues. Maybe, but I am not sure, there is something that can be 
> generalized from some individual cases.
>
> I am happy to work with someone else to go through a couple of 
> different IETF activities that did not really go as planned to 
> "reconstruct" what went wrong. I suggested this in the past but it is 
> of course not fashionable and exciting.
>
The big delays on documents in my queue (e.g. one's that I inherited) 
are almost exclusively of author or wg holds the token again or blocked 
on some other document variety.  the tail is pretty long, whether it's 
heavy or not for a visibile minority of drafts.


From petithug@acm.org  Thu May  2 15:03:53 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0A5221F849C for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 15:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.548
X-Spam-Level: 
X-Spam-Status: No, score=-102.548 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvlKShdjIOux for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 15:03:52 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 1FF1221F84F9 for <ietf@ietf.org>; Thu,  2 May 2013 15:03:51 -0700 (PDT)
Received: from [IPv6:2601:9:4bc0:1f:187a:57c9:420d:940a] (unknown [IPv6:2601:9:4bc0:1f:187a:57c9:420d:940a]) (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 CD6D320148; Fri,  3 May 2013 00:03:49 +0200 (CEST)
Message-ID: <5182E2A8.50800@acm.org>
Date: Thu, 02 May 2013 15:03:20 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com>
In-Reply-To: <5182DD64.7040205@gmail.com>
X-Enigmail-Version: 1.4.1
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: Thu, 02 May 2013 22:03:53 -0000

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

On 05/02/2013 02:40 PM, Yaron Sheffer wrote:
> As a non-native English speaker, but a language pedant nonetheless, I can 
> empathize with people who put Discusses on badly written documents.
> 
> I suggest that we budget for a number of WG drafts per year (say, 20
> IETF-wide) to go through professional, paid-for heavy-duty editing, with
> these goals in mind:
> 
> - Improve the readability of some of published documents, because if a
> document is *really* badly written, even the RFC Editor team will not save
> it. - Improve the level of review, because people can understand the
> document better if they don't need to dig through incorrect or "strange"
> language. - Allow more non-native speakers to participate in our primary
> activity (back to our "diversity" discussion).
> 
> I would suggest that the editing step should take place just before WG
> Last Call, upon a request by a WG chair and with AD approval.

An alternative would be to have the RFC-editor doing copyediting of I-Ds for a
fee.  Depending on the cost, I would use such service for my I-Ds.  That would
be good for everybody:  I would spend less time trying to make my text legible
and more making the protocol described in it better.  And because the document
would have been copy-edited by the same people that will publish the RFC,
that's less work at the end.

> 
> Thanks, Yaron
> 
>> Date: Thu, 02 May 2013 21:14:39 +0300 From: Hannes Tschofenig
>> <hannes.tschofenig@gmx.net> To: Jari Arkko <jari.arkko@piuha.net> Cc:
>> Pete Resnick <presnick@qti.qualcomm.com>, IETF list <ietf@ietf.org> 
>> Subject: Re: call for ideas: tail-heavy IETF process Message-ID:
>> <5182AD0F.4010204@gmx.net> Content-Type: text/plain; charset=ISO-8859-1;
>> format=flowed
>> 
> [...]
> 
>> 
>> PS: I just want to add that I still dislike DISCUSSes that make me 
>> re-write documents just because an English native speaker believes 
>> (probably rightfully so) that he knows how to write the text better (or 
>> at least in a different way). (hint, hint)
>> 
> 


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

iQIcBAEBCAAGBQJRguKnAAoJECnERZXWan7ExYAP/jBHSXFuARqFZkcR9JWIRnfa
qkMEVbZfZA15K7w+1nDAbEfxRWRI+Y2wIqyHegcG3EwS+2GbAY9C+/uNACs5iwSK
5VpSPvYYkkYvA4tniIkPewDyHhpVJlsG1GRN7WGGptKnPt+x2FLijO3ZU1UwEXVo
16vuKJu/tCPLxOhDHOUsNd5B16+ag3y0MwKVcCN+b11EKEmUUXhxGwYESaZipdzS
da1TNcYIaaL2M2bpVEZM+hhnN+5w34hEikf6oXCZQPgH+ycHSL/acT0ufuV9FpE1
VWnGfmaWMngkSd7kvTlcbjUvVpiqx54re2JczdRvRqImjlzMl03tkPmEjniZncg5
mKDw3JX+jGGDySTFvK//Ra+1xQrpjjfHv1Cwslt2GFhytPTWnEIlakIihtNbU92w
UQo0x/c4EGGxm8LYELF7bS5/bwvHUIu9xL7EA2FUKLF1u/LybwMeN9QpL3cbwXmy
xdjFpqd0Zhih8NxF8gI8TUB7ydlJuDZe97+u6qLZXI2MVds5AnwuVbBi2+pJXWsf
IEpRBp1lBLJJZ7TuLfKe7pWA5lLMElvJ+ZvY4Ie2j8ZIAQg0X9YyFF6J7vhpidBq
T+3jIuiDyJDTNVFKgWIU2MzCmYC5HjzlKArE4cwoAFG1g/I8tU2D6mCMc5vFIBuE
so0gffGYiRoVBiEtwCkz
=RZa/
-----END PGP SIGNATURE-----

From jari.arkko@piuha.net  Thu May  2 15:26:07 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E63A21F8E6E for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 15:26:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ttDpAba2eUn6 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 15:26:02 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD1121F8EAC for <ietf@ietf.org>; Thu,  2 May 2013 15:26:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A86F62CC56; Fri,  3 May 2013 01:26:01 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0CdM88NXY5K4; Fri,  3 May 2013 01:26:00 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id B99CF2CC48; Fri,  3 May 2013 01:25:59 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <5182AD0F.4010204@gmx.net>
Date: Thu, 2 May 2013 18:25:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1503)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Thu, 02 May 2013 22:26:07 -0000

Hannes,

Regarding your point about process changes I agree that we've struggled =
there. But for some reason I'm quite optimistic that we can do the right =
changes. Regarding your point on deployment time being even longer, my =
observation has been that most changes have the "right" time, and that =
doing things too far before or too far after makes a big impact on the =
deployment time. In other words, a long IETF development time can and =
has increased deployment time, or even caused a new function to not be =
deployed. But I agree that mere time at the IETF is not what we want to =
look at.

Anyway, I wanted to respond more in depth on the your below point:

> b) There is no interest to research where delay really happen. Your =
statistics just tell that there is delay but not why (of course). =46rom =
my own experience I noticed that there are many reasons for delay and I =
am not sure I can blame it to the IESG reviews for most of the delay. It =
is only during the IESG review phase when the problems surface that =
could have been tackled much earlier.

I agree of course that looking at where the issues are is very =
important, and would support work on that.

However, I did want to point out that when I said "tail-heavy", I did =
*not* necessarily mean delay. I meant that a lot of activity is going =
on, many document changes, and much review is going on. Obviously in =
some cases this translates to delay as well.

But the delay was really not my main concern. Primarily because I think =
other issues such as transparency to the working group or late surprises =
are more fundamental issues than mere timing. But also because I =
actually *do* have some statistics that seem to indicate that, overall, =
the last phase still goes through pretty quickly. Look at =
http://www.arkko.com/tools/lifecycle/wgdocs.html and compare the WG, =
IESG, and RFC editor times in the first graph. The WG time dominates. (I =
said "seem to indicate" because the results are pretty dated and I'm not =
really sure how valid they are, but they match at least my intuitive =
experience.) Not saying delay reduction wouldn't be useful, the overall =
times are still very long, and the IETF last call - IESG time is still a =
significant component. Just that delay would not be my primary concern.

Joel wrote:

> The big delays on documents in my queue (e.g. one's that I inherited) =
are almost exclusively of author or wg holds the token again or blocked =
on some other document variety.  the tail is pretty long, whether it's =
heavy or not for a visibile minority of drafts.

That matches also my intuition, as well as some other statistics that =
I've collected. In other words, most of the time we are waiting for a =
document change as the tracker state is revised ID needed. But of =
course, I don't know why we really are waiting for a document change, it =
could of course be that there are cases where the request for a change =
was unnecessary.

Jari


From dhc@dcrocker.net  Thu May  2 15:59:11 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4F5021F8D14 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 15:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.583
X-Spam-Level: 
X-Spam-Status: No, score=-6.583 tagged_above=-999 required=5 tests=[AWL=0.016,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmFkct1aThAW for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 15:59:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 65DA921F8CE2 for <ietf@ietf.org>; Thu,  2 May 2013 15:59:06 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r42Mwtpw001027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 May 2013 15:59:03 -0700
Message-ID: <5182EFA3.30400@dcrocker.net>
Date: Thu, 02 May 2013 15:58:43 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net>
In-Reply-To: <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 02 May 2013 15:59:05 -0700 (PDT)
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 22:59:11 -0000

On 5/2/2013 3:25 PM, Jari Arkko wrote:
> But the delay was really not my main concern. Primarily because I think other issues such as transparency to the working group or late surprises are more fundamental issues than mere timing. But also because I actually*do*  have some statistics that seem to indicate that, overall, the last phase still goes through pretty quickly. Look athttp://www.arkko.com/tools/lifecycle/wgdocs.html  and compare the WG, IESG, and RFC editor times in the first graph. The WG time dominates. (I said "seem to indicate" because the results are pretty dated and I'm not really sure how valid they are, but they match at least my intuitive experience.) Not saying delay reduction wouldn't be useful, the overall times are still very long, and the IETF last call - IESG time is still a significant component. Just that delay would not be my primary


Jari,

Very interesting set of graphs.  Thanks!


Doing very rough eyeballing of the "left side" averages against the 
"right side" averages -- that is, considering how things have changed 
over the last 10 years -- it looks like:

      Working groups were taking around 500 days and now take around 600.

      The IESG was taking around 200 days and now takes around 110.

      The RFC then and now takes around 100 days (with lots of variation 
between the then and the now, of course.)

      Considering the 'now' set of relationships among the phases, The 
IESG is adding about 20% on top of the working group, and the RFC Editor 
is adding another 20% on top of the working group.  In other words, once 
a working group considers itself done, they are probably only around 70% 
done...

      The total, today appears to be around 3 years to get a 
specification developed and published.  That's for one document, not the 
set of them that might be needed to produce a useful service...

A basic question, then, is whether we think these absolute numbers and 
these proportions of time are reasonable and appropriate for the IETF to 
be/remain effective?

If we don't, what should reasonable numbers look like?


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stpeter@stpeter.im  Thu May  2 16:13:14 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 818BF21F8F1E for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 16:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2U3Sn20coAg4 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 16:13:10 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id F000921F8691 for <ietf@ietf.org>; Thu,  2 May 2013 16:13:09 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4C4914001C; Thu,  2 May 2013 17:24:30 -0600 (MDT)
Message-ID: <5182F307.60107@stpeter.im>
Date: Thu, 02 May 2013 17:13:11 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org>
In-Reply-To: <5182E2A8.50800@acm.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Yaron Sheffer <yaronf.ietf@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: Thu, 02 May 2013 23:13:14 -0000

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

On 5/2/13 4:03 PM, Marc Petit-Huguenin wrote:
> On 05/02/2013 02:40 PM, Yaron Sheffer wrote:
>> As a non-native English speaker, but a language pedant
>> nonetheless, I can empathize with people who put Discusses on
>> badly written documents.
> 
>> I suggest that we budget for a number of WG drafts per year (say,
>> 20 IETF-wide) to go through professional, paid-for heavy-duty
>> editing, with these goals in mind:
> 
>> - Improve the readability of some of published documents, because
>> if a document is *really* badly written, even the RFC Editor team
>> will not save it. - Improve the level of review, because people
>> can understand the document better if they don't need to dig
>> through incorrect or "strange" language. - Allow more non-native
>> speakers to participate in our primary activity (back to our
>> "diversity" discussion).
> 
>> I would suggest that the editing step should take place just
>> before WG Last Call, upon a request by a WG chair and with AD
>> approval.
> 
> An alternative would be to have the RFC-editor doing copyediting of
> I-Ds for a fee.  Depending on the cost, I would use such service
> for my I-Ds.  That would be good for everybody:  I would spend less
> time trying to make my text legible and more making the protocol
> described in it better.  And because the document would have been
> copy-edited by the same people that will publish the RFC, that's
> less work at the end.

Instead of imposing even more work on the RFC Editor team, I suggest
that you find someone in the WG, in your company, in the IETF
community (etc.) to help with the language issues. I did this recently
with a document in one of the WGs where I'm active and it worked quite
well (especially if the document is under source control and you can
just send a patch).

Peter


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRgvMHAAoJEOoGpJErxa2p1WkP/Ao11JgbfdPk1+r5psycC4yW
hc9qCTZeJEuXHHEG5mFLXyuEugkL1LKDjH7TAHql3o28iRYi1P+0LnR4l4Eg27u8
Rfk8TrQ3pE0EHOiMhtX9b1G718iyQAR6bxjBJhR0Sc6f5Y2x4drqZQd4xwHggNCz
uKp58+mrEizUBM3V6+JtCJAQj/mOv3HVbbSij8yWWYvJzuOP1nJ+rqEaI/0lBct5
rkWrefJogtxRHIrwALKmV+BYV99MyDzmm4kwZj+rDzqy/epq77FkqvZUms9EkLZW
HYLWE9RL/onV+XOLbjkSIvjqjCgKdaS1FpMH6zqYidNN491bLAQacyI0QS9d6dGw
9AbDMf1uTxWcfWyB4LrwFFVyA8ZVCWO+1d5up+LSRgfGR/u0WhbyiaJqN0JKy10t
0yJ30+4rwsYjtzsOWy1Zggn8bD4uXXdyjbw8X6Ze69A8ChBlIqticIf4mEd12qSO
E6k8SqtsoX17QmEU8oa7RwNaIbQ59txVju0NHEDlYreBKdHeRrki1SuK5+VrOJAg
yTqzNkpJskgwFukSfLBiX446c4luXkQ4XoSWT3NdkqxIq2ikpXh3WU2p0WgDTM+G
EreYmGTQXP9YV2Ieb+nMsj1pNbD0gB5a8CpXWLe859IIu2ga1uCcxo99LqPymNJB
hmkU2s1OJ2xuR1/d5Anx
=JEpp
-----END PGP SIGNATURE-----

From randy@psg.com  Thu May  2 16:25:51 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9785121F8F9E for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 16:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.289
X-Spam-Level: 
X-Spam-Status: No, score=-2.289 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJ2VqJiUfG0y for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 16:25:51 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 34E0321F8F2F for <ietf@ietf.org>; Thu,  2 May 2013 16:25:51 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UY2so-0008wI-HS; Thu, 02 May 2013 23:25:50 +0000
Date: Thu, 02 May 2013 16:25:50 -0700
Message-ID: <m28v3xm0ap.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Dave Crocker <dhc@dcrocker.net>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <5182EFA3.30400@dcrocker.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.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 list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 May 2013 23:25:51 -0000

>       Working groups were taking around 500 days and now take around 600.
> 
>       The IESG was taking around 200 days and now takes around 110.
> 
>       The RFC then and now takes around 100 days (with lots of variation 
> 	between the then and the now, of course.)
> 
>  Considering the 'now' set of relationships among the phases, The IESG
> is adding about 20% on top of the working group, and the RFC Editor is
> adding another 20% on top of the working group.  In other words, once
> a working group considers itself done, they are probably only around
> 70% done...
> 
> The total, today appears to be around 3 years to get a specification
> developed and published.  That's for one document, not the set of them
> that might be needed to produce a useful service...
> 
> A basic question, then, is whether we think these absolute numbers and
> these proportions of time are reasonable and appropriate for the IETF
> to be/remain effective?

seems pretty reasonable to me.  from personal experience, the iesg and
rfced add useful value.  

being in a many-year process of getting a technology through the
saussage machine, it's the wg that feels to me to be the most
inefficient part of the process.  i attribute this to email not being
the best medium, and meetings being too short and too far between.  but
that is purely subjective.

randy

From sm@elandsys.com  Thu May  2 16:34:47 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 899AB21F8F3C for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 16:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4dSIIDLmbLFz for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 16:34:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E49B021F8F41 for <ietf@ietf.org>; Thu,  2 May 2013 16:34:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.136.99]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r42NYPOK006098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 May 2013 16:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367537679; bh=jKcbUCFmVirb3kvo3QO7/MwcCDU0wNqarQSwsIEbWQE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=PGhblavJLZ5vSL2NYckUqBurToKhjFWGnhsoMxcVFphgTo3kt7xE8K4lF3H89xyxG dwQHlVdIlIqN5oDz9F51nY28AN12g6BbxMtc4yna7UIwyG7eNpZSnRTcycOLbgVlQB yYXVJG3KDfSa1S7dThSTHL1HvucvhI9fPJc+jTTw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367537679; i=@elandsys.com; bh=jKcbUCFmVirb3kvo3QO7/MwcCDU0wNqarQSwsIEbWQE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zqAC6PQ5jXFzGx5s5hQhsGcfaP3vZ7rYq2Rc4VIeD1VpJuoAHdKBlBXWW4X2u592a gqFrfpU63yGPfXW/vjk7xVp96/a1LItOj05r11X+yLBK2jeBSDKM/7urQd7525jldp 86wdctItKoBnA03Yl6fNkUhwVjm0TXGaQFL7dIF0=
Message-Id: <6.2.5.6.2.20130502124018.0d00f990@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 May 2013 16:29:07 -0700
To: Doug Barton <dougb@dougbarton.us>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-Reply-To: <5182BCDB.5080100@dougbarton.us>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Andrew Sullivan <ajs@crankycanuck.ca>, 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, 02 May 2013 23:34:47 -0000

Hi Doug,
At 12:22 02-05-2013, Doug Barton wrote:
>Given that you can be 100% confident that the issue will be raised 
>during IETF LC, wouldn't it be better to hash it out in the WG (as 
>we have attempted to do)? Or is the WG's position, "we have no 
>intention of dealing with this unless we're forced to?"

This is an individual opinion.  It has been mentioned on the SPFBIS 
mailing list that:

   If someone provides an argument together with a good explanation it is not
   going to be ignored no matter how vocal other SPFBIS WG participants are.

The SPFBIS WG Chairs mentioned that:

   "There has been an enormous number of messages lately discussing the
    planned deprecation of the SPF RRTYPE and whether TXT is an appropriate
   thing to use and if it is whether the SPF use of it is ok."

and

   "If you are tempted to say more, we ask that you identify the specific
    point that you think has not been addressed and talk only about
    that.  Other arguments have been made clearly, we believe, and do not
    need additional repetition."

My intent is not "I have no intention of dealing with this unless I 
am forced to".

>I'm fully sympathetic with your collective desire to move the 
>process forward, and finish your document. The problem is that as it 
>stands the document contains a course of action that is not only bad 
>on its face, but contrary to a basic architectural principle adopted 
>4 years ago in 5507.

I have read RFC 5507.  My desire is not to move the draft forward no 
matter what.  If I merely wanted to finish the draft I would have 
done a cursory review.

Several WG participants, including you if I am not mistaken, have 
attempted to hash out the issue in the working group.  It's not that 
there weren't any good arguments.  A Last Call can sometimes help 
bring in fresh perspectives.

Regards,
S. Moonesamy 


From cabo@tzi.org  Thu May  2 18:41:20 2013
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 592EB21F8FF8 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.225
X-Spam-Level: 
X-Spam-Status: No, score=-106.225 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mt5eVA29AkMl for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:41:12 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id EF27E21F8FF5 for <ietf@ietf.org>; Thu,  2 May 2013 18:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r431f50H009140; Fri, 3 May 2013 03:41:05 +0200 (CEST)
Received: from [192.168.217.105] (p54893001.dip0.t-ipconnect.de [84.137.48.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 567BF3ACA; Fri,  3 May 2013 03:41:05 +0200 (CEST)
Subject: Re: Language editing
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5182F307.60107@stpeter.im>
Date: Fri, 3 May 2013 03:41:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <87A766ED-1C28-4B7A-B0A9-36FBA91734F3@tzi.org>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1503)
Cc: ietf@ietf.org, Yaron Sheffer <yaronf.ietf@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: Fri, 03 May 2013 01:41:20 -0000

On May 3, 2013, at 01:13, Peter Saint-Andre <stpeter@stpeter.im> wrote:

> source control

I don't think it has been emphasized enough how important that is from a =
document quality perspective.

More importantly for this discussion, it also somewhat mitigates the =
document editor as a choking point.

People who aren't aware of it should look at the httpbis github =
experiment.
The pull request is a powerful model of WG collaboration.

Gr=FC=DFe, Carsten


From Ted.Lemon@nominum.com  Thu May  2 18:47:30 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D38221F901D for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fOxLV02izGS for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:47:24 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id D668D21F9017 for <ietf@ietf.org>; Thu,  2 May 2013 18:47:23 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUYMXK5BRf5Zq6bOll75LeMRKAodX+xTp@postini.com; Thu, 02 May 2013 18:47:23 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 865581B80AF for <ietf@ietf.org>; Thu,  2 May 2013 18:47:23 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7FEFD190061; Thu,  2 May 2013 18:47:23 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 2 May 2013 18:47:18 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pjyqieAgABGOYCAAAklgIAALxmA
Date: Fri, 3 May 2013 01:47:17 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077516DE7C@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net>
In-Reply-To: <5182EFA3.30400@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C4502C603B943D44BF0FC79ED424BC1A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Fri, 03 May 2013 01:47:30 -0000

On May 2, 2013, at 6:58 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>     The RFC then and now takes around 100 days (with lots of variation be=
tween the then and the now, of course.)

Bear in mind that one of the delays that can occur and is credited to the R=
FC editor is author delays in AUTH48; I think another is document dependenc=
ies: a document that has passed IESG review may wait indefinitely in the RF=
C editor queue until the documents it depends on are published.

Jari, does your graph include that time?


From dhc@dcrocker.net  Thu May  2 18:48:11 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EBB421F8FF8 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.584
X-Spam-Level: 
X-Spam-Status: No, score=-6.584 tagged_above=-999 required=5 tests=[AWL=0.015,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tCov7p7CKfv for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:48:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1E1C421F902B for <ietf@ietf.org>; Thu,  2 May 2013 18:48:06 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r431lu3M006781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 2 May 2013 18:48:04 -0700
Message-ID: <51831741.4000904@dcrocker.net>
Date: Thu, 02 May 2013 18:47:45 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im>
In-Reply-To: <5182F307.60107@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 02 May 2013 18:48:06 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 01:48:11 -0000

On 5/2/2013 4:13 PM, Peter Saint-Andre wrote:
> Instead of imposing even more work on the RFC Editor team, I suggest
> that you find someone in the WG, in your company, in the IETF
> community (etc.) to help with the language issues. I did this recently
> with a document in one of the WGs where I'm active and it worked quite
> well (especially if the document is under source control and you can
> just send a patch).


+1

This goes beyond the simple-but-expensive matter of having the work done 
by the RFC Editor.

With every opportunity, we should move work to the people who want its 
result.

IETF work that is successful has community support.  The community wants 
it and demonstrates this by working on it.  That can (and I think 
should) include ensuring basic writing quality.

If the community does not have enough interest in the work to write it 
well, it has bigger problems that won't be remedied by more RFC Editor 
effort...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Thu May  2 18:50:38 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F7421F9057 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:50:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNQCLqD-2Sy5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:50:32 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id 37C1C21F8FF8 for <ietf@ietf.org>; Thu,  2 May 2013 18:50:32 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUYMX5z18vM+fop0e0aqscPdSC8l1xvSh@postini.com; Thu, 02 May 2013 18:50:32 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C60DB1B8186 for <ietf@ietf.org>; Thu,  2 May 2013 18:50:31 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id BE8EA190061; Thu,  2 May 2013 18:50:31 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 2 May 2013 18:50:31 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Language editing
Thread-Topic: Language editing
Thread-Index: AQHOR4D2OpvPpm3rFUu8RbD6TMQer5jy+5GAgAApUQCAAAKkgA==
Date: Fri, 3 May 2013 01:50:31 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077516DEE5@mbx-01.win.nominum.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <87A766ED-1C28-4B7A-B0A9-36FBA91734F3@tzi.org>
In-Reply-To: <87A766ED-1C28-4B7A-B0A9-36FBA91734F3@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <2339E055722D3C4AAA6F7A567BD4DBC4@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 01:50:39 -0000

On May 2, 2013, at 9:41 PM, Carsten Bormann <cabo@tzi.org> wrote:
> People who aren't aware of it should look at the httpbis github experimen=
t.
> The pull request is a powerful model of WG collaboration.

Several authors in the dhc working group have been doing the same thing, to=
 good effect.


From Ted.Lemon@nominum.com  Thu May  2 18:53:00 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E41A21F9058 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.592
X-Spam-Level: 
X-Spam-Status: No, score=-106.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HO8+fSQG3EYS for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:52:53 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 28F1821F9057 for <ietf@ietf.org>; Thu,  2 May 2013 18:52:53 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUYMYdCmnTeMCHx89LWAXBTpCmprrpcOa@postini.com; Thu, 02 May 2013 18:52:53 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BB18F1B8188 for <ietf@ietf.org>; Thu,  2 May 2013 18:52:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B18E8190061; Thu,  2 May 2013 18:52:52 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 2 May 2013 18:52:52 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: Language editing
Thread-Topic: Language editing
Thread-Index: AQHOR4D2OpvPpm3rFUu8RbD6TMQer5jy+5GAgAArL4CAAAFuAA==
Date: Fri, 3 May 2013 01:52:52 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077516DF2D@mbx-01.win.nominum.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <51831741.4000904@dcrocker.net>
In-Reply-To: <51831741.4000904@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8FC1EF204819D94BB2B5A894ACB4540E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 01:53:00 -0000

On May 2, 2013, at 9:47 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> If the community does not have enough interest in the work to write it we=
ll, it has bigger problems that won't be remedied by more RFC Editor effort=
...

Also worth considering is that if a document is hard to read, it is hard to=
 review, and hence gets less review.   This can result in a really anemic W=
GLC, serious errors caught at the tail end of the process or not at all, or=
 just a document that is not as useful as it could have been.


From marka@isc.org  Thu May  2 18:56:32 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6185821F8FF5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:56:32 -0700 (PDT)
X-Quarantine-ID: <knSR7ynsn0m6>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id knSR7ynsn0m6 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 18:56:31 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB7621F8554 for <ietf@ietf.org>; Thu,  2 May 2013 18:56:28 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id C4E62C9423; Fri,  3 May 2013 01:56:23 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367546188; bh=j9RGXpmgPlztBvbDyEhRm/DOUdKjZPBGQC0YFIAKvcM=; h=To:Cc:cc:From:References:Subject:In-reply-to:Date; b=ZRPrysB7+WQx4NK7DwmNYonBmtocnkA1XL/dwxpcpetdQpx5Z29kvEmqFWEabrEsQ xVW4do47qgCc34nazhHZe+riP2gQH0MMyYOEvSGstaRBdzBI4i8eAAr320svr82IY3 bZG33033gYj86K/ZvoJ0dnlaEB+WnSFI9rmum7GE=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Fri,  3 May 2013 01:56:23 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:c965:93d8:730d:faf3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 3FFEB216C40; Fri,  3 May 2013 01:56:23 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id E520433A79C0; Fri,  3 May 2013 11:56:20 +1000 (EST)
To: Hector Santos <hsantos@isdg.net>
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu> <51811C20.5040305@qti.qualcomm.com> <5182828C.3040200@isdg.net>
Subject: Re: Balancing the Process (Was: Obsoleting SPF RRTYPE)
In-reply-to: Your message of "Thu, 02 May 2013 11:13:16 -0400." <5182828C.3040200@isdg.net>
Date: Fri, 03 May 2013 11:56:20 +1000
Message-Id: <20130503015620.E520433A79C0@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: Pete Resnick <presnick@qti.qualcomm.com>, hostmaster@earthlink.net, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 01:56:32 -0000

In message <5182828C.3040200@isdg.net>, Hector Santos writes:
> Mr. Resnick,  for the record, I wasn't upset. Believe it or not, I was 
> actually applying an suggestion posted last month or so here with the 
> IETF diversity talks to help get a major WG issue resolved, one with a 
> near surety of an appeal, resolved and addressed much faster and hence 
> avoid a waste of time on the behalf of all.
> 
> How appropo, that a topic of "balancing of process" as being considered. 
>    It is one thing I believe the IETF needs and can be actually apply 
> today. Yes, I don't agree with the negative tone taken in SPFBIS where 
> in effect, an attempt to shut down communications and indirectly 
> personally attack posters occurred and the advocates of the SPF RRTYPE 
> removal (incidentally, a SPEC change which I believe was prohibited by 
> the charter), basically blowing off advocates of a RFC4408 status quo. 
> If you believe that was proper, I think we have a WG problem.
> 
> Overall, I believe this (keep the migration path) is the proper 
> compromise to resolve the issue, and I believe that this particular 
> issue is industry-wide important to resolve with across the board 
> engineering input. It *SHOULD NOT* be reserved only to the applications 
> SPFBIS group especially when we know what the DNS community will say 
> about this and has said so since MARID 2003 and again last year in IETF 
> and DNSOPs. I was simply hoping to help "Balance the process" then as I 
> was attempted to do again.  If I was in error for trying to get a 
> serious issue resolve, then please accept my apology.
> 
> Sincerely,
> 
> Hector Santos

One of the questions is how to deal with vendors that claim to ship
a product which is in compliance with the protcol when they are
not.

The DNS protocol has a error code for when you do not understand a
query, FORMERR.  It also has a error code for when you do not
implement part of the protocol, NOTIMP.

With RFC 103[45] you have three choices as a developer when you get
a query type you don't know about.

1. Treat it as a FORMERR.
2. Treat it as a NOTIMP.
3. Treat it as a opaque data.

Now in my book it isn't a FORMERR as you can understand the question
even if you can't deal with it.  NOTIMP is a reasonable response
though I believe the intent in RFC 103[45] was to treat it as opaque
data query which is what RFC 3597 says to do.

Nowhere in RFC 103[45] does it say DO NOT RESPOND to the query yet
we have DNS vendors that ship products that do just that and are
claiming that they conform to the protocol.

For a example of a set of servers that does this see earthlink.net's
servers.

Query for HINFO/earthlink.net at the authoritative servers for
earthlink.net (itchy.earthlink.net and scratchy.earthlink.net) and
you will not get a response.  A RFC 103[45] compliant server should
know about HINFO.  It should also be capable of returning a NOERROR
NODATA response for that query and it fact will if you ask for a
non-existent TXT record at a name it serves.

How do we deal with sites?
How do we deal with vendors that ship such product?

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From Ted.Lemon@nominum.com  Thu May  2 19:07:29 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8151F21F910E for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:07:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O61QTYZ+oEIM for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:07:22 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 3856121F904B for <ietf@ietf.org>; Thu,  2 May 2013 19:07:22 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUYMb2dcW2S6sdKnW8shB58rLGm92/xtS@postini.com; Thu, 02 May 2013 19:07:22 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id BB9321B8188 for <ietf@ietf.org>; Thu,  2 May 2013 19:07:21 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id B3F49190061; Thu,  2 May 2013 19:07:21 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 2 May 2013 19:07:21 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: Balancing the Process (Was: Obsoleting SPF RRTYPE)
Thread-Topic: Balancing the Process (Was: Obsoleting SPF RRTYPE)
Thread-Index: AQHOR6F2XM+nGMT9zEKl30ocE3oylJjzK/gA
Date: Fri, 3 May 2013 02:07:21 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077516DFAD@mbx-01.win.nominum.com>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu> <51811C20.5040305@qti.qualcomm.com> <5182828C.3040200@isdg.net> <20130503015620.E520433A79C0@drugs.dv.isc.org>
In-Reply-To: <20130503015620.E520433A79C0@drugs.dv.isc.org>
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: <AE772CBCD438AD408977D986478EC228@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 02:07:29 -0000

On May 2, 2013, at 9:56 PM, Mark Andrews <marka@isc.org> wrote:
> How do we deal with sites?
> How do we deal with vendors that ship such product?

I say we punch 'em.

Seriously, the IETF doesn't have an enforcement arm.   It's up to buyers to=
 check to see that what they are buying is protocol compliant, and often th=
ey either fail to even try, or don't really know how.

What you can do as a DNS vendor, if you want to beat up other vendors with =
non-compliant products, is to produce a validation test suite and start pro=
moting it.   Is there a vendor that does this now?   If so, you could just =
use theirs, assuming it's free.   Start boasting in your advertising that y=
our product is standards compliant.

Now that you're done with that, get started on all the middleboxes that are=
 made by vendors who are not "DNS vendors".

The good news is that the ocean is warmer than it was even ten years ago, s=
o boiling it is somewhat less work than it used to be.


From petithug@acm.org  Thu May  2 19:14:08 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4184821F888C for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:14:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QHBzqSdaVNB1 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:14:07 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 539A021F8763 for <ietf@ietf.org>; Thu,  2 May 2013 19:14:05 -0700 (PDT)
Received: from [IPv6:2601:9:4bc0:1f:187a:57c9:420d:940a] (unknown [IPv6:2601:9:4bc0:1f:187a:57c9:420d:940a]) (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 311BA209E7; Fri,  3 May 2013 04:14:03 +0200 (CEST)
Message-ID: <51831D53.6030608@acm.org>
Date: Thu, 02 May 2013 19:13:39 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <87A766ED-1C28-4B7A-B0A9-36FBA91734F3@tzi.org>
In-Reply-To: <87A766ED-1C28-4B7A-B0A9-36FBA91734F3@tzi.org>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Yaron Sheffer <yaronf.ietf@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: Fri, 03 May 2013 02:14:08 -0000

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

On 05/02/2013 06:41 PM, Carsten Bormann wrote:
> On May 3, 2013, at 01:13, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> 
>> source control
> 
> I don't think it has been emphasized enough how important that is from a
> document quality perspective.
> 
> More importantly for this discussion, it also somewhat mitigates the
> document editor as a choking point.
> 
> People who aren't aware of it should look at the httpbis github
> experiment. The pull request is a powerful model of WG collaboration.

Friends do not let friends use github.

The pull request in github does not handle rebasing correctly.  The github Web
interface is useless, and you have to use the RESTful API for anything a bit
sophisticated.  I know, I spent 2 months of hell editing
draft-ietf-p2psip-base with this piece of crap.

Gerrit is far better at anything github does.  Unfortunately there is no
public repository supporting Gerrit and that's a shame.  People interested in
trying Gerrit can contact me directly.

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

iQIcBAEBCAAGBQJRgx1RAAoJECnERZXWan7E8WIP/1nqqexAn6mh6HH1ZKO05Qre
Xh2F5hfe50i/UgU9jqJdPNwbjJEK6nwY5vX++6kGGQwAgMLypkrAmRW3atPs+vBf
hlr0PmRhgZWpkvZicJKKkZIVPVpudR4BnvzESLGdIvZ9I7p8pnZOfmKbn8uFjyHt
6q02Ust7FZBxbSAU6AxO5DqO3AjljnhhGeRpeKMRi3aSGr3RlO5dxQ6SWhDYi50G
miflfV1ytc/jOzOk80smZAN5/89DHikNEhmx/2m9mMJGDVOM8PebZeTETKFKXnJO
4FtO3rlY3/4WTRFYE7Q/djjsvqaiZOfGV7kSsdosT0NeO8xK0XO3qaNzvKYZFeLA
OSmb55NFf1mXBwT+CQI8vlrMkHiHNCS+bEAg2vtbNaUKB1g268C6/3tJUn+wJX90
EZinlfgQ4oQAPJZfhn8z4ARVtxuQZhWIfHCPNqZR3CRoDjOmWFDslyNpijHsEoXe
g7fKSkO9nu84V9bYBnGs44mG4zLdT4AgMT1sIEnW09UkuPAlX8H2wJmYrMeViXwb
s1qvmDU2tw/5UsppwtuSjfGCTD6vGwUWyeM4xQX7fszOk7qV8arcE5S/W2z/FghZ
otkFX5eFBmSRRAn98OzzC4LBZmpxPm6ItEcrEcwJFeRyzYdEjDOJZl+O0EBx0MpD
rxZCi/Ugf1IXG16VZPOO
=HnH9
-----END PGP SIGNATURE-----

From jari.arkko@piuha.net  Thu May  2 19:14:20 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA04121F89D5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:14:20 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRgewmjwn7oe for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:14:15 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4A48D21F8CDD for <ietf@ietf.org>; Thu,  2 May 2013 19:14:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C75212CC53; Fri,  3 May 2013 05:14:11 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9gcXJeCwCa0; Fri,  3 May 2013 05:14:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 851A12CC48; Fri,  3 May 2013 05:14:10 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077516DE7C@mbx-01.win.nominum.com>
Date: Thu, 2 May 2013 22:14:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE3569C3-F5E9-424A-BAE6-68F2796A60E6@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B63077516DE7C@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1503)
Cc: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, 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: Fri, 03 May 2013 02:14:20 -0000

Ted,

> Bear in mind that one of the delays that can occur and is credited to =
the RFC editor is author delays in AUTH48; I think another is document =
dependencies: a document that has passed IESG review may wait =
indefinitely in the RFC editor queue until the documents it depends on =
are published.
>=20
> Jari, does your graph include that time?

Yes - RFC editor time includes AUTH48 time, just as the IESG time =
includes waiting for revised ID from the authors.

In any case, please do not look at the numbers in too much detail. They =
haven't really been validated too much, and again, are from an old run. =
Working to get some better numbers when I have spare time=85

Jari



From marka@isc.org  Thu May  2 19:48:22 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D8C721F8F9E for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:48:22 -0700 (PDT)
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.076,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DpJ68Z22OLXV for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 19:48:21 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 53FBC21F8EAA for <ietf@ietf.org>; Thu,  2 May 2013 19:48:21 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 6C3BB5F98E7; Fri,  3 May 2013 02:48:09 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367549300; bh=sDhm8RDt4sArCoH3I84lgXejk5BFFvoSAN6kQHNn2vI=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=AItUgNiOhnLhg95ehfkBevhOkCzdBhgtibQgObcke050ttjP+eqK0qx4y8If8GdM0 13p3+01a1v03/2tRfmL6jdbq++83FPUvv+/Jx81CoqPZAzJGjZlz3mLojRKs412L85 A7pl7Lp+skDUuCMqInHg4xFVqOShz1APKo0193Nw=
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:c965:93d8:730d:faf3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 99466216C40; Fri,  3 May 2013 02:48:07 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 7B82B33A7C2E; Fri,  3 May 2013 12:48:05 +1000 (EST)
To: Ted Lemon <Ted.Lemon@nominum.com>
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu> <51811C20.5040305@qti.qualcomm.com> <5182828C.3040200@isdg.net> <20130503015620.E520433A79C0@drugs.dv.isc.org> <8D23D4052ABE7A4490E77B1A012B63077516DFAD@mbx-01.win.nominum.com>
Subject: Re: Balancing the Process (Was: Obsoleting SPF RRTYPE)
In-reply-to: Your message of "Fri, 03 May 2013 02:07:21 +0000." <8D23D4052ABE7A4490E77B1A012B63077516DFAD@mbx-01.win.nominum.com>
Date: Fri, 03 May 2013 12:48:05 +1000
Message-Id: <20130503024805.7B82B33A7C2E@drugs.dv.isc.org>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 02:48:22 -0000

In message <8D23D4052ABE7A4490E77B1A012B63077516DFAD@mbx-01.win.nominum.com>, Ted Lemon writes:
> On May 2, 2013, at 9:56 PM, Mark Andrews <marka@isc.org> wrote:
> > How do we deal with sites?
> > How do we deal with vendors that ship such product?
>
> I say we punch 'em.
>
> Seriously, the IETF doesn't have an enforcement arm.   It's up to buyers
> to check to see that what they are buying is protocol compliant, and
> often they either fail to even try, or don't really know how.

When the literature says it is a DNS server how is the buyer to
know it isn't a complete DNS server?  And even if they know it is
not a complete DNS server would they know the impact of deploying
it?

> What you can do as a DNS vendor, if you want to beat up other vendors
> with non-compliant products, is to produce a validation test suite and
> start promoting it.   Is there a vendor that does this now?   If so, you
> could just use theirs, assuming it's free.   Start boasting in your
> advertising that your product is standards compliant.

Which just adds more noise.  Now if a recognised standards body was
to do the tests then it might have some effect.

Should we be using RFC 1033's complaint's procedures?  How can
we get TLDs to do step 5 when steps 1 though 4 fail?

COMPLAINTS

   These are the suggested steps you should take if you are having
   problems that you believe are caused by someone else's name server:


   1.  Complain privately to the responsible person for the domain.  You
   can find their mailing address in the SOA record for the domain.

   2.  Complain publicly to the responsible person for the domain.

   3.  Ask the NIC for the administrative person responsible for the
   domain.  Complain.  You can also find domain contacts on the NIC in
   the file NETINFO:DOMAIN-CONTACTS.TXT

   4.  Complain to the parent domain authorities.

   5.  Ask the parent authorities to excommunicate the domain.


> Now that you're done with that, get started on all the middleboxes that
> are made by vendors who are not "DNS vendors".

Middle boxes are a little easier to deal with as they are usually at the
client end not the server end.
 
> The good news is that the ocean is warmer than it was even ten years ago,
> so boiling it is somewhat less work than it used to be.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From randy@psg.com  Thu May  2 20:44:28 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7565221F9017 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 20:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.392
X-Spam-Level: 
X-Spam-Status: No, score=-2.392 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4CON6nBT9PUW for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 20:44:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 52D9621F8689 for <ietf@ietf.org>; Thu,  2 May 2013 20:44:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UY6uz-000BeL-Ih for ietf@ietf.org; Fri, 03 May 2013 03:44:21 +0000
Date: Thu, 02 May 2013 20:44:21 -0700
Message-ID: <m21u9on2wa.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF discussion list <ietf@ietf.org>
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
In-Reply-To: <C83D1AA8-4F8E-4304-8A7A-3EE3ED2B1F9F@neustar.biz>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <C83D1AA8-4F8E-4304-8A7A-3EE3ED2B1F9F@neustar.biz>
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, 03 May 2013 03:44:28 -0000

seems to me that
  o spf is still used, whether we think it is a good idea or not
  o spf is using the spf rrtype
  o we don't shoot an rrtype which is still being used
  o overloading txt with a whole lot of things we don't like is
    stupid++ for soooo many reasons

if you don't like spf, then *convince* folk to use something better.
until then, find something better to do with your copious spare time.

randy

From narten@us.ibm.com  Thu May  2 21:53:24 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 557FC21F92F5 for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 21:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAVE4QK7oSxQ for <ietf@ietfa.amsl.com>; Thu,  2 May 2013 21:53:09 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id EB5DC21F92C5 for <ietf@ietf.org>; Thu,  2 May 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 00:53:07 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 00:53:06 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 8517A6E8040 for <ietf@ietf.org>; Fri,  3 May 2013 00:53:02 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r434r5VP313852 for <ietf@ietf.org>; Fri, 3 May 2013 00:53:05 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r434r5PX008971 for <ietf@ietf.org>; Fri, 3 May 2013 01:53:05 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r434r42o008951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 3 May 2013 01:53:05 -0300
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r434r4Xv010565 for <ietf@ietf.org>; Fri, 3 May 2013 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.6/8.14.6/Submit) id r434r3Cb010543 for ietf@ietf.org; Fri, 3 May 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201305030453.r434r3Cb010543@rotala.raleigh.ibm.com>
Date: Fri, 03 May 2013 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050304-9360-0000-0000-0000120287C7
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 04:53:24 -0000

Total of 226 messages in the last 7 days.
 
script run at: Fri May  3 00:53:03 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.08% |   16 |  6.62% |   118279 | dhc@dcrocker.net
  3.54% |    8 |  3.01% |    53739 | vesely@tana.it
  3.54% |    8 |  3.01% |    53683 | ted.lemon@nominum.com
  3.10% |    7 |  3.27% |    58437 | mstjohns@comcast.net
  2.65% |    6 |  3.25% |    58037 | abdussalambaryun@gmail.com
  3.10% |    7 |  2.78% |    49615 | hartmans-ietf@mit.edu
  2.65% |    6 |  2.98% |    53257 | marka@isc.org
  2.65% |    6 |  2.63% |    47042 | john-ietf@jck.com
  2.65% |    6 |  2.25% |    40249 | brian.e.carpenter@gmail.com
  2.65% |    6 |  2.16% |    38663 | mcr+ietf@sandelman.ca
  2.21% |    5 |  2.52% |    45015 | rjsparks@nostrum.com
  1.33% |    3 |  2.78% |    49662 | bclaise@cisco.com
  2.21% |    5 |  1.82% |    32465 | sm@resistor.net
  1.77% |    4 |  1.88% |    33577 | stbryant@cisco.com
  1.33% |    3 |  2.29% |    40956 | yaronf.ietf@gmail.com
  1.77% |    4 |  1.74% |    31013 | sm+ietf@elandsys.com
  1.33% |    3 |  2.17% |    38828 | ron.even.tlv@gmail.com
  1.77% |    4 |  1.73% |    30888 | adrian@olddog.co.uk
  1.77% |    4 |  1.70% |    30432 | rdroms.ietf@gmail.com
  1.33% |    3 |  1.89% |    33774 | mbj@tail-f.com
  1.77% |    4 |  1.42% |    25424 | jari.arkko@piuha.net
  1.77% |    4 |  1.39% |    24880 | drc@virtualized.org
  1.77% |    4 |  1.32% |    23552 | cabo@tzi.org
  1.77% |    4 |  1.27% |    22638 | randy@psg.com
  1.33% |    3 |  1.51% |    27063 | daedulus@btconnect.com
  1.33% |    3 |  1.47% |    26319 | hsantos@isdg.net
  1.33% |    3 |  1.31% |    23482 | huitema@microsoft.com
  1.33% |    3 |  1.19% |    21193 | fred@cisco.com
  0.88% |    2 |  1.57% |    27991 | superuser@gmail.com
  1.33% |    3 |  1.12% |    20073 | stephen.farrell@cs.tcd.ie
  1.33% |    3 |  1.08% |    19212 | fgont@si6networks.com
  0.88% |    2 |  1.43% |    25595 | volz@cisco.com
  1.33% |    3 |  0.99% |    17645 | stpeter@stpeter.im
  0.88% |    2 |  1.34% |    23906 | david.black@emc.com
  0.88% |    2 |  1.10% |    19607 | mohamed.boucadair@orange.com
  0.88% |    2 |  0.87% |    15599 | dougb@dougbarton.us
  0.88% |    2 |  0.86% |    15394 | elwynd@dial.pipex.com
  0.88% |    2 |  0.81% |    14531 | petithug@acm.org
  0.88% |    2 |  0.81% |    14489 | mrw@lilacglade.org
  0.88% |    2 |  0.78% |    13979 | swb@internet2.edu
  0.88% |    2 |  0.77% |    13822 | presnick@qti.qualcomm.com
  0.88% |    2 |  0.73% |    13020 | dharkins@lounge.org
  0.88% |    2 |  0.73% |    12958 | joelja@bogus.com
  0.88% |    2 |  0.71% |    12677 | scott@kitterman.com
  0.88% |    2 |  0.71% |    12675 | martin.stiemerling@neclab.eu
  0.88% |    2 |  0.70% |    12569 | ole@cisco.com
  0.44% |    1 |  1.15% |    20467 | cpignata@cisco.com
  0.88% |    2 |  0.70% |    12419 | ynir@checkpoint.com
  0.88% |    2 |  0.69% |    12365 | iab-chair@iab.org
  0.88% |    2 |  0.67% |    12024 | lars@netapp.com
  0.88% |    2 |  0.58% |    10320 | francis.dupont@fdupont.fr
  0.44% |    1 |  0.91% |    16207 | acooper@cdt.org
  0.44% |    1 |  0.88% |    15662 | lear@cisco.com
  0.44% |    1 |  0.76% |    13588 | andy@yumaworks.com
  0.44% |    1 |  0.63% |    11197 | leo.liubing@huawei.com
  0.44% |    1 |  0.58% |    10389 | ed.lewis@neustar.biz
  0.44% |    1 |  0.55% |     9818 | barryleiba@computer.org
  0.44% |    1 |  0.49% |     8714 | narten@us.ibm.com
  0.44% |    1 |  0.49% |     8683 | jdrake@juniper.net
  0.44% |    1 |  0.48% |     8605 | johnsonhammond2@hushmail.com
  0.44% |    1 |  0.46% |     8216 | dmm@1-4-5.net
  0.44% |    1 |  0.46% |     8174 | glenzorn@gmail.com
  0.44% |    1 |  0.45% |     8012 | hannes.tschofenig@gmx.net
  0.44% |    1 |  0.43% |     7678 | tbray@textuality.com
  0.44% |    1 |  0.41% |     7363 | john@jlc.net
  0.44% |    1 |  0.41% |     7302 | jabley@hopcount.ca
  0.44% |    1 |  0.40% |     7156 | allison.mankin@gmail.com
  0.44% |    1 |  0.40% |     7127 | lhotka@nic.cz
  0.44% |    1 |  0.38% |     6843 | amankin@verisign.com
  0.44% |    1 |  0.38% |     6814 | warren@kumari.net
  0.44% |    1 |  0.38% |     6754 | kathleen.moriarty@emc.com
  0.44% |    1 |  0.37% |     6694 | mansaxel@besserwisser.org
  0.44% |    1 |  0.37% |     6533 | melinda.shore@gmail.com
  0.44% |    1 |  0.36% |     6419 | chair@ietf.org
  0.44% |    1 |  0.36% |     6398 | lberger@labn.net
  0.44% |    1 |  0.36% |     6366 | randy_presuhn@mindspring.com
  0.44% |    1 |  0.34% |     6090 | otroan@employees.org
  0.44% |    1 |  0.34% |     6034 | ted.ietf@gmail.com
  0.44% |    1 |  0.34% |     6020 | josh.howlett@ja.net
  0.44% |    1 |  0.33% |     5967 | ajs@anvilwalrusden.com
  0.44% |    1 |  0.33% |     5946 | johnl@taugh.com
  0.44% |    1 |  0.33% |     5930 | derhoermi@gmx.net
  0.44% |    1 |  0.33% |     5909 | worley@ariadne.com
  0.44% |    1 |  0.33% |     5895 | mnot@mnot.net
  0.44% |    1 |  0.32% |     5674 | martin.thomson@gmail.com
  0.44% |    1 |  0.31% |     5468 | paul.hoffman@vpnc.org
  0.44% |    1 |  0.29% |     5204 | mrex@sap.com
--------+------+--------+----------+------------------------
100.00% |  226 |100.00% |  1786348 | Total


From daedulus@btconnect.com  Fri May  3 01:30:31 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27CC821F94FD for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 01:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xU-arNmJ3vqK for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 01:30:26 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe004.messaging.microsoft.com [216.32.181.184]) by ietfa.amsl.com (Postfix) with ESMTP id 1B48921F9457 for <ietf@ietf.org>; Fri,  3 May 2013 01:30:26 -0700 (PDT)
Received: from mail137-ch1-R.bigfish.com (10.43.68.251) by CH1EHSOBE009.bigfish.com (10.43.70.59) with Microsoft SMTP Server id 14.1.225.23; Fri, 3 May 2013 08:30:25 +0000
Received: from mail137-ch1 (localhost [127.0.0.1])	by mail137-ch1-R.bigfish.com (Postfix) with ESMTP id 32B4D400247; Fri,  3 May 2013 08:30:25 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(z569dhzbb2dI98dI9371I542I1432Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz17326ah1954cbh8275bh8275dh8275ch1033ILz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail137-ch1 (localhost.localdomain [127.0.0.1]) by mail137-ch1 (MessageSwitch) id 1367569823129969_16454; Fri,  3 May 2013 08:30:23 +0000 (UTC)
Received: from CH1EHSMHS033.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.251])	by mail137-ch1.bigfish.com (Postfix) with ESMTP id 134894A0048;	Fri,  3 May 2013 08:30:23 +0000 (UTC)
Received: from DB3PRD0710HT005.eurprd07.prod.outlook.com (157.56.253.85) by CH1EHSMHS033.bigfish.com (10.43.70.33) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 3 May 2013 08:30:22 +0000
Received: from pc6 (86.166.98.191) by pod51017.outlook.com (10.255.75.40) with Microsoft SMTP Server (TLS) id 14.16.305.3; Fri, 3 May 2013 08:30:07 +0000
Message-ID: <008f01ce47d7$b4992840$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Marc Petit-Huguenin <petithug@acm.org>
References: <mailman.21.1367521206.21891.ietf@ietf.org><5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im>
Subject: Re: Language editing
Date: Fri, 3 May 2013 09:24:39 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.166.98.191]
X-FOPE-CRA-SourceIpAddress: 157.56.253.85
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: yaronf.ietf@gmail.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: stpeter@stpeter.im
X-FOPE-BFA-RECEIVER: petithug@acm.org
X-OriginatorOrg: btconnect.com
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 08:30:31 -0000

----- Original Message -----
From: "Peter Saint-Andre" <stpeter@stpeter.im>
To: "Marc Petit-Huguenin" <petithug@acm.org>
Cc: "Yaron Sheffer" <yaronf.ietf@gmail.com>; <ietf@ietf.org>
Sent: Friday, May 03, 2013 12:13 AM
>
> On 5/2/13 4:03 PM, Marc Petit-Huguenin wrote:
> > On 05/02/2013 02:40 PM, Yaron Sheffer wrote:
> > An alternative would be to have the RFC-editor doing copyediting of
> > I-Ds for a fee.  Depending on the cost, I would use such service
> > for my I-Ds.  That would be good for everybody:  I would spend less
> > time trying to make my text legible and more making the protocol
> > described in it better.  And because the document would have been
> > copy-edited by the same people that will publish the RFC, that's
> > less work at the end.
>
> Instead of imposing even more work on the RFC Editor team, I suggest
> that you find someone in the WG, in your company, in the IETF
> community (etc.) to help with the language issues. I did this recently
> with a document in one of the WGs where I'm active and it worked quite
> well (especially if the document is under source control and you can
> just send a patch).

Ah, there's the rub.

I have done this on a number of occasions for a variety of people and
editing the text file of an I-D is almost trivial compared to then
incorporating the amendments, some agreed, some debated, some rejected,
into the XML, in doing so introducing the need for further amendments
(problem generates change generates problem generates ... the cycle
beloved of all software developers).

We really do need a tool, the like of which I was using 40 years ago
when writing code, that allows patches to be applied independently and
temporarily to see what it then looks like and if agreed that it looks
good, incorporating them permanently into the source (XML).  Ideally
such a tool would reverse engineer the amended text into XML patches as
well - text is so much easier to work with than XML (or any other markup
language).

Tom Petch

> Peter
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJRgvMHAAoJEOoGpJErxa2p1WkP/Ao11JgbfdPk1+r5psycC4yW
> hc9qCTZeJEuXHHEG5mFLXyuEugkL1LKDjH7TAHql3o28iRYi1P+0LnR4l4Eg27u8
> Rfk8TrQ3pE0EHOiMhtX9b1G718iyQAR6bxjBJhR0Sc6f5Y2x4drqZQd4xwHggNCz
> uKp58+mrEizUBM3V6+JtCJAQj/mOv3HVbbSij8yWWYvJzuOP1nJ+rqEaI/0lBct5
> rkWrefJogtxRHIrwALKmV+BYV99MyDzmm4kwZj+rDzqy/epq77FkqvZUms9EkLZW
> HYLWE9RL/onV+XOLbjkSIvjqjCgKdaS1FpMH6zqYidNN491bLAQacyI0QS9d6dGw
> 9AbDMf1uTxWcfWyB4LrwFFVyA8ZVCWO+1d5up+LSRgfGR/u0WhbyiaJqN0JKy10t
> 0yJ30+4rwsYjtzsOWy1Zggn8bD4uXXdyjbw8X6Ze69A8ChBlIqticIf4mEd12qSO
> E6k8SqtsoX17QmEU8oa7RwNaIbQ59txVju0NHEDlYreBKdHeRrki1SuK5+VrOJAg
> yTqzNkpJskgwFukSfLBiX446c4luXkQ4XoSWT3NdkqxIq2ikpXh3WU2p0WgDTM+G
> EreYmGTQXP9YV2Ieb+nMsj1pNbD0gB5a8CpXWLe859IIu2ga1uCcxo99LqPymNJB
> hmkU2s1OJ2xuR1/d5Anx
> =JEpp
> -----END PGP SIGNATURE-----
>



From cabo@tzi.org  Fri May  3 01:38:13 2013
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 69A8D21F9501 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 01:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level: 
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uNA-MsYX-qka for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 01:38:07 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 5823921F9488 for <ietf@ietf.org>; Fri,  3 May 2013 01:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r438bsB4007210; Fri, 3 May 2013 10:37:54 +0200 (CEST)
Received: from [109.41.180.1] (ip-109-41-180-1.web.vodafone.de [109.41.180.1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8B5E43C51; Fri,  3 May 2013 10:37:54 +0200 (CEST)
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <008f01ce47d7$b4992840$4001a8c0@gateway.2wire.net>
In-Reply-To: <008f01ce47d7$b4992840$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <7FF0D71F-E8F1-487C-8968-6802A953052D@tzi.org>
X-Mailer: iPad Mail (10B329)
From: TZI <cabo@tzi.org>
Subject: Re: Language editing
Date: Fri, 3 May 2013 10:37:53 +0200
To: "t.p." <daedulus@btconnect.com>
Cc: ietf <ietf@ietf.org>, Yaron Sheffer <yaronf.ietf@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: Fri, 03 May 2013 08:38:13 -0000

> We really do need a tool, the like of which I was using 40 years ago
> when writing code, that allows patches to be applied independently

that's what pull requests (or gerrit) are about.

> and
> temporarily to see what it then looks like and if agreed that it looks
> good, incorporating them permanently into the source (XML).  Ideally
> such a tool would reverse engineer the amended text into XML patches as
> well - text is so much easier to work with than XML (or any other markup
> language).

try writing the draft in markdown and using Miek Gieben's or my tool (kramdo=
wn-rfc2629) to convert into XML.

it is so much easier to collaborate in markdown...

Gr=C3=BC=C3=9Fe, Carsten


From Ted.Lemon@nominum.com  Fri May  3 03:52:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4093C21F95D0 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 03:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.593
X-Spam-Level: 
X-Spam-Status: No, score=-106.593 tagged_above=-999 required=5 tests=[AWL=0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jn4jww2yIK7i for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 03:51:54 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by ietfa.amsl.com (Postfix) with ESMTP id B022021F93FC for <ietf@ietf.org>; Fri,  3 May 2013 03:51:54 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP ID DSNKUYOWylIjp6dPpFEcKEuPYTZucCPKaujL@postini.com; Fri, 03 May 2013 03:51:54 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id C1C2D1B8189 for <ietf@ietf.org>; Fri,  3 May 2013 03:51:53 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id AF5E3190061; Fri,  3 May 2013 03:51:53 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 3 May 2013 03:51:53 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: t.p. <daedulus@btconnect.com>
Subject: Re: Language editing
Thread-Topic: Language editing
Thread-Index: AQHOR4D2OpvPpm3rFUu8RbD6TMQer5jy+5GAgAAmb2OAAJzIgA==
Date: Fri, 3 May 2013 10:51:53 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077516E4C9@mbx-01.win.nominum.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org><5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <008f01ce47d7$b4992840$4001a8c0@gateway.2wire.net>
In-Reply-To: <008f01ce47d7$b4992840$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <18DAF8CFEA4BC54BA7D170DCC93E5604@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>, Yaron Sheffer <yaronf.ietf@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: Fri, 03 May 2013 10:52:03 -0000

On May 3, 2013, at 4:24 AM, t.p. <daedulus@btconnect.com> wrote:
> We really do need a tool, the like of which I was using 40 years ago
> when writing code, that allows patches to be applied independently and
> temporarily to see what it then looks like and if agreed that it looks
> good, incorporating them permanently into the source (XML).  Ideally
> such a tool would reverse engineer the amended text into XML patches as
> well - text is so much easier to work with than XML (or any other markup
> language).

Actually, what I'd like to see is a change approval process, where I can go=
 in and make the edits I want to the document, submit those, and then the d=
ocument editors can just go down the list of changes approving them or not.=
   I guess that's not too different from what you said, but with a better U=
I.


From swb@internet2.edu  Fri May  3 04:09:11 2013
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 1115B21F84CA for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 04:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.276
X-Spam-Level: 
X-Spam-Status: No, score=-5.276 tagged_above=-999 required=5 tests=[AWL=-1.677, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhVEKqUIzd3e for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 04:09:05 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) by ietfa.amsl.com (Postfix) with ESMTP id 733D321F84EF for <ietf@ietf.org>; Fri,  3 May 2013 04:09:05 -0700 (PDT)
Received: from mail20-ch1-R.bigfish.com (10.43.68.228) by CH1EHSOBE014.bigfish.com (10.43.70.64) with Microsoft SMTP Server id 14.1.225.23; Fri, 3 May 2013 11:08:55 +0000
Received: from mail20-ch1 (localhost [127.0.0.1])	by mail20-ch1-R.bigfish.com (Postfix) with ESMTP id 752BD20045B; Fri,  3 May 2013 11:08:55 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.241.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0810HT004.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -1
X-BigFish: S-1(z569dhzbb2dI98dI154cP9371Izz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzz17326ah8275chz2dh2a8h668h839h93fhd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1b1cn1b1bi1155h)
Received: from mail20-ch1 (localhost.localdomain [127.0.0.1]) by mail20-ch1 (MessageSwitch) id 1367579324958187_17999; Fri,  3 May 2013 11:08:44 +0000 (UTC)
Received: from CH1EHSMHS041.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.244])	by mail20-ch1.bigfish.com (Postfix) with ESMTP id E42184401A0;	Fri,  3 May 2013 11:08:44 +0000 (UTC)
Received: from BL2PRD0810HT004.namprd08.prod.outlook.com (157.56.241.101) by CH1EHSMHS041.bigfish.com (10.43.69.250) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 3 May 2013 11:08:44 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.110.39) with Microsoft SMTP Server (TLS) id 14.16.305.3; Fri, 3 May 2013 11:08:43 +0000
Message-ID: <51839ABA.4010406@internet2.edu>
Date: Fri, 3 May 2013 07:08:42 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org>
In-Reply-To: <5182E2A8.50800@acm.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.edu
Cc: Yaron Sheffer <yaronf.ietf@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: Fri, 03 May 2013 11:09:11 -0000

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

On 05/02/2013 02:40 PM, Yaron Sheffer wrote:
> I suggest that we budget for a number of WG drafts per year (say,
> 20 IETF-wide) to go through professional, paid-for heavy-duty
> editing

My experience is that unless the editors have some background in
protocols, this takes a surprising amount of effort, explaining it to
them and catching _their_ mistaken assumptions (which can be subtle).
 However,

On 05/02/13 19:13, Peter Saint-Andre allegedly wrote:
> Instead of imposing even more work on the RFC Editor team, I
> suggest that you find someone in the WG, in your company, in the
> IETF community (etc.) to help with the language issues.

... then you have quality control issues, uncertainty who to turn to,
finding someone who not only appears to be good but actually is, etc.

So how about a pool of volunteer editors, aka GEN-AET, with developed
reputations?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlGDmroACgkQF0TR2hENFASGtACfYHQB29sSh9CUxg9NfLLzGtuW
7DMAoJnyyfb3KVXJaCcnOERlMuHiXLtx
=YEaW
-----END PGP SIGNATURE-----


From jouni.nospam@gmail.com  Fri May  3 04:11:25 2013
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F8E21F95E6 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 04:11:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HYrqIlTfbUrj for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 04:11:24 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 24F9B21F9015 for <ietf@ietf.org>; Fri,  3 May 2013 04:11:23 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id eh20so1389785lab.22 for <ietf@ietf.org>; Fri, 03 May 2013 04:11:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=pWYa0d3FdXWysPZCjRrd8gyl4ACU/myveL6Yd1UCcZQ=; b=m63dTmuDnz4rkBxhWaubFyHvo3SZ5XVOV2rZlTpIdaoL51Owb4S4cf5fqiKCEeWLgq Q7APyMleBBCIjdOgCx/kDjgQucHIKlGBp6PgYy/1KfArTrF+pHEFd683IMBoX/E3SUU+ T9w7pcJq6P+6V/VZWNTEZnvc/5mlUbwHkFC2727VoxVaHMexPgB3NK+i9mE0XQVhCifg oAkC6tKLAPjVOgrF/FHMlwyT1krN+OXhG92HG1WuulF06lqLUG2GQNFM93DUMzQU3tK/ ULYINCD0cVLlZ1KThdFE/AEzr61pRGhl54Z2anFbU/3ZomcnFzWqmo2urNhrJ1wgYydm TuDg==
X-Received: by 10.112.145.72 with SMTP id ss8mr3397646lbb.12.1367579482888; Fri, 03 May 2013 04:11:22 -0700 (PDT)
Received: from [192.168.250.126] ([194.100.71.98]) by mx.google.com with ESMTPSA id g4sm435574lbe.0.2013.05.03.04.11.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 04:11:21 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Jouni Korhonen <jouni.nospam@gmail.com>
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
Date: Fri, 3 May 2013 14:11:20 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <26DB641A-4C5B-451B-9C23-8EB535B7E8A3@gmail.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1503)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Fri, 03 May 2013 11:11:25 -0000

Jari,

This was an interesting (and a needed) writeup. I also want to share
my view as an IETF newbie who has had a chance to experience IETF
document process a few times. Sorry for chiming in late..

For the most part I got the feeling that we have the right tools and
a working process already in place. It is mostly about how we treat
the process and adjust our habits to it.

The thing I dislike is when you ship a camel into IESG and a horse
comes out.. and everybody is like "what happened?" ;-) My approach
would be simple. If a document gets x DISCUSSes out of y or even a
single DISCUSS would substantially change the technical solution of
the document, ship it back to the WG - always, no questions asked. The
document is not ready and we are wasting IESG's time. The technical
work belongs to the WG. Obviously this begs for a much higher
threshold for an AD to give a document a DISCUSS instead of a COMMENT.

Then about the habits. =46rom my limited experience, folks are used to
the think "the document will anyway be reviewed, reworked and can be
finished in the IESG" and that occasionally shows. I want to believe
this habit changes if the document must be ready for real before
leaving the WG.

The cross area directorate reviews are great and should have even
more weight than they have today. And here is what I would like to
see to change slightly. The directorate & expert reviews should all
be done before sending the document out of the WG into the IESG.
Probably the IETF LC should also happen before sending the document
out of the WG.

My Z$0.02,
	Jouni


On May 1, 2013, at 6:33 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> I wrote a blog article about how we do a fairly significant amount of =
reviews and changes in the late stages of the IETF process. Next week =
the IESG will be having a retreat in Dublin, Ireland. As we brought this =
topic to our agenda, Pete and I wanted to raise the issue here and call =
for feedback & ideas for improving the situation with all of you.
>=20
> http://www.ietf.org/blog/2013/05/balancing-the-process/
>=20
> Jari
>=20


From daedulus@btconnect.com  Fri May  3 04:58:22 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA7921F95F1 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 04:58:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.121
X-Spam-Level: 
X-Spam-Status: No, score=-3.121 tagged_above=-999 required=5 tests=[AWL=0.478,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-FPR8IpZ4pV for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 04:58:16 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe006.messaging.microsoft.com [216.32.180.189]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC0D21F86FA for <ietf@ietf.org>; Fri,  3 May 2013 04:58:15 -0700 (PDT)
Received: from mail72-co1-R.bigfish.com (10.243.78.234) by CO1EHSOBE011.bigfish.com (10.243.66.74) with Microsoft SMTP Server id 14.1.225.23; Fri, 3 May 2013 11:58:15 +0000
Received: from mail72-co1 (localhost [127.0.0.1])	by mail72-co1-R.bigfish.com (Postfix) with ESMTP id 264CE9A049B; Fri,  3 May 2013 11:58:15 +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: -13
X-BigFish: PS-13(z569dhz9371Ic89bh542Izz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275bh8275dh1033ILz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail72-co1 (localhost.localdomain [127.0.0.1]) by mail72-co1 (MessageSwitch) id 1367582293816478_23283; Fri,  3 May 2013 11:58:13 +0000 (UTC)
Received: from CO1EHSMHS027.bigfish.com (unknown [10.243.78.225])	by mail72-co1.bigfish.com (Postfix) with ESMTP id C1B581C004E; Fri,  3 May 2013 11:58:13 +0000 (UTC)
Received: from DB3PRD0710HT001.eurprd07.prod.outlook.com (157.56.253.85) by CO1EHSMHS027.bigfish.com (10.243.66.37) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 3 May 2013 11:58:13 +0000
Received: from AMXPRD0310HT005.eurprd03.prod.outlook.com (157.56.248.133) by pod51017.outlook.com (10.255.75.36) with Microsoft SMTP Server (TLS) id 14.16.305.3; Fri, 3 May 2013 11:58:00 +0000
Message-ID: <004d01ce47f4$bf09b5c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: TZI <cabo@tzi.org>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <008f01ce47d7$b4992840$4001a8c0@gateway.2wire.net> <7FF0D71F-E8F1-487C-8968-6802A953052D@tzi.org>
Subject: Re: Language editing
Date: Fri, 3 May 2013 12:52:36 +0100
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.248.133]
X-FOPE-CRA-SourceIpAddress: 157.56.253.85
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: yaronf.ietf@gmail.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: petithug@acm.org
X-FOPE-BFA-RECEIVER: cabo@tzi.org
X-FOPE-BFA-RECEIVER: stpeter@stpeter.im
Content-Transfer-Encoding: quoted-printable
X-OriginatorOrg: btconnect.com
Cc: ietf <ietf@ietf.org>, Yaron Sheffer <yaronf.ietf@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: Fri, 03 May 2013 11:58:22 -0000

---- Original Message -----
From: "TZI" <cabo@tzi.org>
To: "t.p." <daedulus@btconnect.com>
Cc: "Peter Saint-Andre" <stpeter@stpeter.im>; "Marc Petit-Huguenin"
<petithug@acm.org>; "Yaron Sheffer" <yaronf.ietf@gmail.com>; "ietf"
<ietf@ietf.org>
Sent: Friday, May 03, 2013 9:37 AM
Subject: Re: Language editing


> We really do need a tool, the like of which I was using 40 years ago
> when writing code, that allows patches to be applied independently

that's what pull requests (or gerrit) are about.

> and
> temporarily to see what it then looks like and if agreed that it looks
> good, incorporating them permanently into the source (XML).  Ideally
> such a tool would reverse engineer the amended text into XML patches
as
> well - text is so much easier to work with than XML (or any other
markup
> language).

try writing the draft in markdown and using Miek Gieben's or my tool
(kramdown-rfc2629) to convert into XML.

it is so much easier to collaborate in markdown...

<tp>
Right, but the context is that after many years and several rounds of
editing, the I-D is ready for Last Call and someone who may not have
been previously involved in the editing goes through and proposes
enhancements for legibility.  It needs to be an available on the IETF
website tool and easy enough for many to use without much education.

Tom Petch

Gr=C3=BC=C3=9Fe, Carsten




From narten@us.ibm.com  Fri May  3 05:59:19 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBD9B21F845E for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 05:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.449
X-Spam-Level: 
X-Spam-Status: No, score=-110.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcGvTbSdzC3P for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 05:59:13 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id DA1F421F8411 for <ietf@ietf.org>; Fri,  3 May 2013 05:59:12 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 08:59:12 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 08:59:09 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 777856E8028 for <ietf@ietf.org>; Fri,  3 May 2013 08:59:05 -0400 (EDT)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r43Cx81f301216 for <ietf@ietf.org>; Fri, 3 May 2013 08:59:08 -0400
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 r43Cx72p024340 for <ietf@ietf.org>; Fri, 3 May 2013 06:59:07 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-147-40.mts.ibm.com [9.49.147.40]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r43Cx6MY024175 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 06:59:07 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r43Cx5l9015836; Fri, 3 May 2013 08:59:05 -0400
Message-Id: <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <32577.1367426027@sandelman.ca>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca>
Comments: In-reply-to Michael Richardson <mcr+ietf@sandelman.ca> message dated "Wed, 01 May 2013 12:33:47 -0400."
Date: Fri, 03 May 2013 08:59:04 -0400
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050312-7182-0000-0000-000006867AB7
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: Fri, 03 May 2013 12:59:20 -0000

Just a few points...

Michael Richardson <mcr+ietf@sandelman.ca> writes:

> I'll repeat what has been said repeatedly in the newtrk and related
> discussions.  The step from ID to "RFC" is too large because we are
> essentially always aiming for "STD" rather than "PS".

> If we are unwilling to bring "RFC" back to a place were it does not
> equal STD, then we need to create a new category of document which
> amounts to "fully baked ID".  Things like IANA allocations could occur
> at that point.

> In the days of dot-boom it was not unusual to see widespread
> implementation very early in the ID process and even interop and
> experimental deployment.   While this still occurs for quite a number of
> things (and sometimes it's a problem that the ID can not be changed as a
> result), there is an equal amount of "wait for the RFC to come out".

I suspect there is a bit of rose colored reminiscing of history.

The world has changed, significantly.

For example, there has been massive consolidation in industry. There
simply are fewer entities doing implementations today. 15 years ago,
it was common to see a half dozen or more implementations from
different (often smaller) entities, even before a document got out of
a WG. Nowadays, the cost of doing an implementation (for a company) is
in some sense much higher, and business realities make companies
*very* selective in what they implement and put into a product.

I suspect that the notion that if the IETF published documents more
quickly industry would implement them more quickly/frequently is
wishful thinking.

Michael Richardson <mcr+ietf@sandelman.ca> writes:
> It's what Carsten said.

> 1) this idea is baked enough for cross-area review to make sense.
> 2) the protocol is not going to change significantly, one could
>    implement.
> 3) any future changes need thus to take into account impact on
>    existing implementations... BUT that doesn't mean that we can't
>    change things.

Like it or not, 2 and 3 are contradictory. From an interoperability
perspective, the difference between "not change significantly" and
"change a lot" is irrelevant once you have deployments. Change (in the
behavior or wire format) is change and breaks interoperability, no
matter how big or small.

Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:

> b) There is no interest to research where delay really happen.

I don't think that is true. Jari has pointed to his work. I think
there is actually quite a lot of understanding of where the delays
are. But fixing them is really really hard. Blaming the "tail end" or
"the IESG" for the problems has always been the easy target. The
reality (IMO) is that the place where improvements are needed is
within the WG and on having authors be more responsive. But history
suggests there are no easy fixes here.

Randy Bush <randy@psg.com> writes:

> > A basic question, then, is whether we think these absolute numbers and
> > these proportions of time are reasonable and appropriate for the IETF
> > to be/remain effective?

> seems pretty reasonable to me.  from personal experience, the iesg and
> rfced add useful value.

+1

Like everyone, I wish things moved more quickly, but every attempt
I've ever seen that tries to speed things up ends up reducing the
quality or having some other undesirable side effect.

The bottom line is that getting a good spec requires iteration, and
reviews from a broad set of parties. That is best done
*sequentially*. And given the limited cycles the (volunteer) community
as a whole has, you can't easily change these dynamics. We've seen
many attempts to reduce the overall time by trying to overlap reviews
and steps, but that has the side effect of losing *sequential*
*iteration* (where each new review reviews the previous set of
additions/changes). IMO, overlapping steps is dangerous and leads to
poor quality.

> being in a many-year process of getting a technology through the
> saussage machine, it's the wg that feels to me to be the most
> inefficient part of the process.  i attribute this to email not being
> the best medium, and meetings being too short and too far between.  but
> that is purely subjective.

If you want to speed up the process, focus on how to *increase* the
amount of iteration you get (i.e., revised drafts) while at the same
time *reducing* the time between revised drafts.

If you look at the delays documents encounter (both in WG and in IESG
review), the killer is long times between document revisions. Focus on
understanding the *why* behind that and what steps could be taken to
make improvements.

And finally, a big reason the IESG review is where things happen is
that it *really* is the last time one has to verify that a document is
ready to go. With the limited cycles we all have, there will always be
a tendancy to not deal with a document until the point of "this is
your last chance". Nothing like a *real* deadline to motivate people
to finally deal with a document, before it's too late.

Thomas


From stephen.farrell@cs.tcd.ie  Fri May  3 06:28:23 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA28E21F8A0C for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 06:28:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.677
X-Spam-Level: 
X-Spam-Status: No, score=-103.677 tagged_above=-999 required=5 tests=[AWL=-1.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ly1-yr0X5Q1L for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 06:28:18 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id E69E521F9644 for <ietf@ietf.org>; Fri,  3 May 2013 06:28:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5A695BEB0; Fri,  3 May 2013 14:27:54 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxxBEtskjaVd; Fri,  3 May 2013 14:27:54 +0100 (IST)
Received: from [IPv6:2001:770:10:203:2080:f244:5ffe:95de] (unknown [IPv6:2001:770:10:203:2080:f244:5ffe:95de]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 56037BEAF; Fri,  3 May 2013 14:27:53 +0100 (IST)
Message-ID: <5183BB59.7090206@cs.tcd.ie>
Date: Fri, 03 May 2013 14:27:53 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Fri, 03 May 2013 13:28:24 -0000

On 05/03/2013 01:59 PM, Thomas Narten wrote:
> 
> If you look at the delays documents encounter (both in WG and in IESG
> review), the killer is long times between document revisions. Focus on
> understanding the *why* behind that and what steps could be taken to
> make improvements.

Good point. I guess the obvious answers are "not enough
cycles" and, for newer authors, uncertainty about how to
get stuff done, but are there other less obvious answers?
(Input here might really help the IESG discussion btw since
in the nature of things, we're less likely to realise what
newer or less frequent participants find problematic.)

S.

From narten@us.ibm.com  Fri May  3 07:14:13 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5918A21F87CB for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.524
X-Spam-Level: 
X-Spam-Status: No, score=-110.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zFzFbGTgSgeM for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:14:06 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF0221F870F for <ietf@ietf.org>; Fri,  3 May 2013 07:14:06 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 10:14:05 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 10:14:04 -0400
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id A5B26C90045 for <ietf@ietf.org>; Fri,  3 May 2013 10:14:03 -0400 (EDT)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r43EE3MB55378056 for <ietf@ietf.org>; Fri, 3 May 2013 10:14:03 -0400
Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r43EE2wm025840 for <ietf@ietf.org>; Fri, 3 May 2013 11:14:02 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-49-147-40.mts.ibm.com [9.49.147.40]) by d01av02.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r43EE18C025741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 11:14:02 -0300
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r43EDwkq027639; Fri, 3 May 2013 10:13:58 -0400
Message-Id: <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <5183BB59.7090206@cs.tcd.ie>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie>
Comments: In-reply-to Stephen Farrell <stephen.farrell@cs.tcd.ie> message dated "Fri, 03 May 2013 14:27:53 +0100."
Date: Fri, 03 May 2013 10:13:58 -0400
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050314-5806-0000-0000-000020FD2FB8
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: Fri, 03 May 2013 14:14:13 -0000

> Good point. I guess the obvious answers are "not enough
> cycles" and, for newer authors, uncertainty about how to
> get stuff done, but are there other less obvious answers?
> (Input here might really help the IESG discussion btw since
> in the nature of things, we're less likely to realise what
> newer or less frequent participants find problematic.)

One possible step is to have WG Chairs be *managers*, like they are
supposed to be. That means the equivalent of having project plans. For
a given document, come up with a (reasonable, pragmatic, workable)
schedule for getting reviews, discussion, revision, repeat. And then
get committments from parties (authors, reviewers, etc.) to
deliver. And followup if they don't...

The current cycle too often seems to be more like "new version
posted". Wait if anyone reviews. Some reviews eventually, maybe. Oh,
IETF meeting coming, time for a revision. But with meeting
approaching, there are a zillion docs and cycles are limited.  Rather
haphazard, with too many documents effectively only being revised once
per meeting cycle.

WGs make the most progress when authors respond quickly (within days)
to reviews, and do so on the list discussing possible text
revisions. You get much quicker and substantive discussion that way
and it becomes clear whether folk are converging.

Contrast that with "ask for reviews". Wait a month or two. New
document appears that says "this reflects comments we got, go
read". Delays between review/response tend to feed upon
themselves. Folk forget context, etc., making it more of an effort to
go back and remember their reviews, etc.

Too much of WG activites are "best effort" where volunteers (who are
busy and may not actually have the experience to do things optimally)
are expected magically to just know how things are supposed to work
make progress. Reality is a bit different.

Two concrete suggestions:

1) have WGs do the managing role more proactively
2) mentor authors and others a bit more to encourage them how best to
operate

Thomas


From adrian@olddog.co.uk  Fri May  3 07:20:36 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB8121F9661 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcY4cVqCTBnb for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:20:30 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 3141221F9357 for <ietf@ietf.org>; Fri,  3 May 2013 07:20:26 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r43EKJsT022799;  Fri, 3 May 2013 15:20:23 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r43EKH1e022769 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 May 2013 15:20:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Thomas Narten'" <narten@us.ibm.com>, "'Stephen Farrell'" <stephen.farrell@cs.tcd.ie>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<32577.1367426027@sandelman.ca>	<201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>	<5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
Subject: RE: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 15:20:16 +0100
Message-ID: <04a601ce4809$5679a000$036ce000$@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: AQKYyBhEoNBNJ3MPVKuNyDDagY8byQGPmImJAoVjNqoCWVDxGgGC+2YGlx73mTA=
Content-Language: en-gb
Cc: 'IETF list' <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: Fri, 03 May 2013 14:20:36 -0000

Well said, Thomas. 

> Two concrete suggestions:
> 
> 1) have WGs do the managing role more proactively
> 2) mentor authors and others a bit more to encourage them how best to
> operate

Which I suspect means...

0) have ADs manage/mentor the WG chairs more proactively.

Almost certainly a case of "if I had less work to do I would have more time to
do the things that would reduce my workload."  :-)

WG chairs might like to comment, but I suspect that one lunchtime training
session every four months does not constitute proactive management.

Adrian


From rpelletier@isoc.org  Fri May  3 07:29:42 2013
Return-Path: <rpelletier@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 3D9C921F965D for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.144
X-Spam-Level: 
X-Spam-Status: No, score=-101.144 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sH57eRMbROlu for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:29:30 -0700 (PDT)
Received: from smtp110.ord1c.emailsrvr.com (smtp110.ord1c.emailsrvr.com [108.166.43.110]) by ietfa.amsl.com (Postfix) with ESMTP id D923221F962E for <ietf@ietf.org>; Fri,  3 May 2013 07:29:22 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 6090198143; Fri,  3 May 2013 10:29:22 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 150559813F;  Fri,  3 May 2013 10:29:22 -0400 (EDT)
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
X-Mailer: iPhone Mail (10B329)
From: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 10:29:22 -0400
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Cc: Thomas Narten <narten@us.ibm.com>, 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: Fri, 03 May 2013 14:29:42 -0000

On May 3, 2013, at 10:20 AM, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> Well said, Thomas.=20
>=20
>> Two concrete suggestions:
>>=20
>> 1) have WGs do the managing role more proactively

Provide WG Chairs the monitoring tools they need to be proactive - Action Tr=
acker, what do I need to do today data tracker  views.  Same for AD.=20

Same for authors and their mentors, if any.=20

Ray


>> 2) mentor authors and others a bit more to encourage them how best to
>> operate
>=20
> Which I suspect means...
>=20
> 0) have ADs manage/mentor the WG chairs more proactively.
>=20
> Almost certainly a case of "if I had less work to do I would have more tim=
e to
> do the things that would reduce my workload."  :-)
>=20
> WG chairs might like to comment, but I suspect that one lunchtime training=

> session every four months does not constitute proactive management.
>=20
> Adrian
>=20

From narten@us.ibm.com  Fri May  3 07:33:08 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2496521F8681 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:33:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.549
X-Spam-Level: 
X-Spam-Status: No, score=-110.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFqJs1fEIsA8 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:33:01 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 476F421F86BB for <ietf@ietf.org>; Fri,  3 May 2013 07:33:01 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 10:33:00 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 10:32:58 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 514C36E8044 for <ietf@ietf.org>; Fri,  3 May 2013 10:32:54 -0400 (EDT)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r43EWv4S299626 for <ietf@ietf.org>; Fri, 3 May 2013 10:32:57 -0400
Received: from d01av05.pok.ibm.com (loopback [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r43EWuF5023403 for <ietf@ietf.org>; Fri, 3 May 2013 10:32:57 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-49-147-40.mts.ibm.com [9.49.147.40]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r43EWuqo023357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 10:32:56 -0400
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r43EWov1030152; Fri, 3 May 2013 10:32:50 -0400
Message-Id: <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: adrian@olddog.co.uk
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
Comments: In-reply-to "Adrian Farrel" <adrian@olddog.co.uk> message dated "Fri, 03 May 2013 15:20:16 +0100."
Date: Fri, 03 May 2013 10:32:50 -0400
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050314-5806-0000-0000-000020FD4EEA
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: Fri, 03 May 2013 14:33:08 -0000

"Adrian Farrel" <adrian@olddog.co.uk> writes:

> Well said, Thomas. 

> > Two concrete suggestions:
> > 
> > 1) have WGs do the managing role more proactively
> > 2) mentor authors and others a bit more to encourage them how best to
> > operate

> Which I suspect means...

> 0) have ADs manage/mentor the WG chairs more proactively.

Absolutely. But that is why the nomcom is supposed to select ADs that
have *management* capabilities as well as technical skills.

> Almost certainly a case of "if I had less work to do I would have
> more time to do the things that would reduce my workload."  :-)

Well, this is why you get paid the big bucks.

Not to put too fine a point on in, but ADs need to manage their time,
and they need to balance between the immediate and the long term. They
have to do *both*, and especially NOT neglect longer-term stuff that
will have real and signficant, but not immediate benefits.

> WG chairs might like to comment, but I suspect that one lunchtime training
> session every four months does not constitute proactive management.

This would help and could be part of a comprehensive approach. But ADs
also need to lay down expectations on WG chairs, and *grade* and
*evaluate* WG Chair performance. WG chairs also don't have
cycles... And ADs seem reluctant to step in and make management
changes that really often are needed to change the dynamices within
WGs that are not delivering...

Thomas


From dhc@dcrocker.net  Fri May  3 07:37:33 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7CF21F9617 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:37:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.585
X-Spam-Level: 
X-Spam-Status: No, score=-6.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2RZGwcVOOrpS for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 07:37:28 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8D21621F87E0 for <ietf@ietf.org>; Fri,  3 May 2013 07:37:28 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r43EbGVh017255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 3 May 2013 07:37:25 -0700
Message-ID: <5183CB90.7030900@dcrocker.net>
Date: Fri, 03 May 2013 07:37:04 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
In-Reply-To: <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 03 May 2013 07:37:28 -0700 (PDT)
Cc: Thomas Narten <narten@us.ibm.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 14:37:33 -0000

On 5/3/2013 7:29 AM, Ray Pelletier wrote:
> Provide WG Chairs the monitoring tools they need to be proactive - Action Tracker, what do I need to do today data tracker  views.  Same for AD.
>
> Same for authors and their mentors, if any.


Probably none of the above.

The IETF already provides pretty good tools.  They could always be 
better, of course, but they almost certainly aren't essential.

The issue with providing management assistance is to focus on managing 
the work.  That's an organizational orientation, not just a tracking 
thing.  It's about getting clarity of the work to be done and of getting 
folks to do the work of contributing, writing, reviewing, and debating 
in a timely manner, and achieving forward progress in a timely manner.

Few working groups have enough detail to juggle to make this something 
that hinges on the tools.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From elwynd@dial.pipex.com  Fri May  3 08:39:51 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BE3E21F8E49 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 08:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yi+H0K+MPWpi for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 08:39:31 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id A26A821F9668 for <ietf@ietf.org>; Fri,  3 May 2013 07:58:25 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1UYHR3-0002TR-8G; Fri, 03 May 2013 15:58:13 +0100
Subject: Re: call for ideas: tail-heavy IETF process
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
In-Reply-To: <5183BB59.7090206@cs.tcd.ie>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie>
Content-Type: text/plain
Date: Fri, 03 May 2013 15:51:13 +0100
Message-Id: <1367592673.5273.8980.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: Thomas Narten <narten@us.ibm.com>, 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: Fri, 03 May 2013 15:39:51 -0000

On Fri, 2013-05-03 at 14:27 +0100, Stephen Farrell wrote:
> On 05/03/2013 01:59 PM, Thomas Narten wrote:
> > 
> > If you look at the delays documents encounter (both in WG and in IESG
> > review), the killer is long times between document revisions. Focus on
> > understanding the *why* behind that and what steps could be taken to
> > make improvements.
> 
> Good point. I guess the obvious answers are "not enough
> cycles" 
and not enough "concentrated cycles" - designing and documenting a
protocol in my experience requires a longish period of undisturbed
concentration by the person with the editing crayon, and responsive,
deep and immediate review by co-authors to generate fast turn round
reviews of versions.
Its hard enough keeping the in-brain implementation of the protocol
running accurately day-by-day.  If there are gaps of weeks rebooting the
implementation wastes precious concentrated time.  Probably putting a
few people with no other commitments in a isolated space generates
fastest results. Maybe we could get ISOC to provide a retreat space (or
one per continent) for protocol designers?
> and, for newer authors, uncertainty about how to
> get stuff done, but are there other less obvious answers?
> (Input here might really help the IESG discussion btw since
> in the nature of things, we're less likely to realise what
> newer or less frequent participants find problematic.)
One thing that might help:
We have directorates and review panels.  Can we distil any/more of their
wisdom into checklists/guidance for protocol writers?
Some is already there (not a complete list):
BCP 72 for security considerations 
BCP 41 on congestion control
BCP 61 on Strong Security Requirements
Some stuff in RFC 6385 for gen-art

[Some of this is getting a bit long in the tooth.]

So what do you ...
- think about when designing the security aspects/transport congestion
aspects/... of a new protocol?
- what triggers alarm bells/gold stars when you are reviewing the
general principles/security aspects/congestion/ABNF/state
machines/mib/xml/extensibility/.... of a draft?

Regards,
Elwyn

> 
> S.


From presnick@qti.qualcomm.com  Fri May  3 09:12:26 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9808B21F9BF3 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 09:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.818
X-Spam-Level: 
X-Spam-Status: No, score=-105.818 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pyWnDrly3Am for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 09:12:19 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id A650521F990B for <ietf@ietf.org>; Fri,  3 May 2013 08:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1367593936; x=1399129936; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gfTfYlydAu9WY+7VqhtdSIMiOTpD8HM7QcHxRm6bF14=; b=IUaCWuNQoOJ/p17yvSOAL/FdsxQHQtKsH7YA8KfoXet7ZXqa3kTyQjyt lYAMEFUdicbtKA9Ptfx/SEVDJ1em/OviKJG0XGJcVxB+gyusFlj511pXJ 7h0AX5bONG+UpqVtxF3TnXexzCH3x3mowj6zLr4J8eovJkfkWylRayCB2 w=;
X-IronPort-AV: E=Sophos;i="4.87,605,1363158000"; d="scan'208";a="44016419"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine02.qualcomm.com with ESMTP; 03 May 2013 08:12:16 -0700
X-IronPort-AV: E=Sophos;i="4.87,605,1363158000"; d="scan'208";a="442477489"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 May 2013 08:12:15 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 3 May 2013 08:12:15 -0700
Message-ID: <5183D3CB.60702@qti.qualcomm.com>
Date: Fri, 3 May 2013 10:12:11 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<32577.1367426027@sandelman.ca>	<201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>	<5183BB59.7090206@cs.tcd.ie>	<201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>	<04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: adrian@olddog.co.uk, '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: Fri, 03 May 2013 16:12:26 -0000

On 5/3/13 9:32 AM, Thomas Narten wrote:

> Not to put too fine a point on in, but ADs need to manage their time,
> and they need to balance between the immediate and the long term. They
> have to do *both*, and especially NOT neglect longer-term stuff that
> will have real and signficant, but not immediate benefits.
>    

Interesting. For the most part, I agree with the above. And I think we 
have been neglecting some of the longer-term stuff. But earlier:

On 5/3/13 7:59 AM, Thomas Narten wrote:

> Like everyone, I wish things moved more quickly, but every attempt
> I've ever seen that tries to speed things up ends up reducing the
> quality or having some other undesirable side effect.
>    

Can you talk a bit more about this, including some examples?

I'm trying to reconcile the concern that we "end up reducing the 
quality" and  that we "NOT neglect longer-term stuff that will have real 
and significant, but not immediate benefits." ADs have finite resources 
and can't accomplish both immediate and longer-term stuff maximally all 
of the time. My inclination would be to say, "If they are in conflict, 
weight the longer-term over the immediate, even if that might result in 
some reducing of quality on any single document." Am I over-reading your 
earlier message to say that you think the weighting should go toward the 
immediate? I think we agree that doing the longer-term stuff will end up 
with increased quality over the long term, but doing more of the 
longer-term stuff is sure to reduce the amount of time spent on 
immediate, which means document reviews and therefore some short term 
lowering of quality. Is that OK, or is that an example of the kind of 
thing we've attempted that ends up with bad results?

pr

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


From rdroms.ietf@gmail.com  Fri May  3 09:27:30 2013
Return-Path: <rdroms.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 40B9F21F89E2 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 09:27:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.933
X-Spam-Level: 
X-Spam-Status: No, score=-102.933 tagged_above=-999 required=5 tests=[AWL=-0.334, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w4zUFWhRRQPr for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 09:27:29 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0D97B21F979D for <ietf@ietf.org>; Fri,  3 May 2013 08:34:54 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id b25so777462qca.13 for <ietf@ietf.org>; Fri, 03 May 2013 08:34:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=8dor+rJhZ5lCCTN/h+Kbkl4p85VgCf/PDzDTM8z5uO8=; b=xV7CZYknRz98zWp8+GzHldVJBW4nyX3ffqJxTXFGDzJLW7GQ58JHoNzCSz2K2+Dp7M OINJaRfZJD2S7Jwd91isS7ebhbDtoA+5u6aTPsxVJXiDLNWzYG+Fvlvfs0IDlqaURBFG g9GPzwa1cR8heT956XwVd2KhT5jYJ2l1tb2nigx6inoUHWcOc9OIAEvAkqGdhxE4geIn 0OJIozK2rUnVLgxoIziiRdXyYcR6CM6eBi+6OD537W3Y8864qfybEKz0Q9TuFmxvSgKX KaUR37I7zIGwtk73okSIx9NQJqfbZRhXRhuIuxUWE4v0RXWe+EBqLeApfgV+kyNbg1/X 0YWg==
X-Received: by 10.49.14.135 with SMTP id p7mr14479190qec.57.1367595294455; Fri, 03 May 2013 08:34:54 -0700 (PDT)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPSA id i5sm18476104qaf.0.2013.05.03.08.34.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 08:34:51 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Language editing
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <51831741.4000904@dcrocker.net>
Date: Fri, 3 May 2013 11:34:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD86CE51-1912-400C-87F2-C6460AC3BC5D@gmail.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <5182F307.60107@stpeter.im> <51831741.4000904@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
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, 03 May 2013 16:27:30 -0000

On May 2, 2013, at 9:47 PM 5/2/13, Dave Crocker <dhc@dcrocker.net> =
wrote:

> On 5/2/2013 4:13 PM, Peter Saint-Andre wrote:
>> Instead of imposing even more work on the RFC Editor team, I suggest
>> that you find someone in the WG, in your company, in the IETF
>> community (etc.) to help with the language issues. I did this =
recently
>> with a document in one of the WGs where I'm active and it worked =
quite
>> well (especially if the document is under source control and you can
>> just send a patch).
>=20
>=20
> +1
>=20
> This goes beyond the simple-but-expensive matter of having the work =
done by the RFC Editor.
>=20
> With every opportunity, we should move work to the people who want its =
result.

Dave, I agree with you and you make a very important point, that applies =
broadly to this conversation.

In particular, it should be the responsibility of the interested parties =
to engage community support, and it should be the responsibility of the =
community to put effort into producing a document that meets =
requirements of basic writing quality.

>=20
> IETF work that is successful has community support.  The community =
wants it and demonstrates this by working on it.  That can (and I think =
should) include ensuring basic writing quality.

If you'll allow me to dive into process issues and solution engineering =
briefly, these writing quality issues should be caught well before the =
document reaches the IESG, in the abstract to ensure that the =
responsibility (and the work) in producing publishable documents rests =
with the people who want the document published, and pragmatically =
because a DISCUSS position of "returned for improvement in writing =
quality" is at the edge of what can be handled through routine =
processes.

>=20
> If the community does not have enough interest in the work to write it =
well, it has bigger problems that won't be remedied by more RFC Editor =
effort...

Yup.

>=20
> d/

- Ralph

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


From adrian@olddog.co.uk  Fri May  3 10:17:14 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44C4C21F973D for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O98mGSN-NDuw for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:16:49 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id B378F21F95F9 for <ietf@ietf.org>; Fri,  3 May 2013 08:59:26 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r43FxHr8031475;  Fri, 3 May 2013 16:59:17 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r43FxGeL031465 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 May 2013 16:59:16 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ray Pelletier'" <rpelletier@isoc.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
In-Reply-To: <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
Subject: RE: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 16:59:15 +0100
Message-ID: <04d801ce4817$29bf3e90$7d3dbbb0$@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: AQKYyBhEoNBNJ3MPVKuNyDDagY8byQGPmImJAoVjNqoCWVDxGgGC+2YGApKHHrIDAZeQIZbycqfw
Content-Language: en-gb
Cc: 'Thomas Narten' <narten@us.ibm.com>, 'IETF list' <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: Fri, 03 May 2013 17:17:14 -0000

> >> 1) have WGs do the managing role more proactively
> 
> Provide WG Chairs the monitoring tools they need to be proactive - Action
> Tracker, what do I need to do today data tracker  views.  Same for AD.
> 
> Same for authors and their mentors, if any.

Wouldn't work for me. YMMV.

Adrian


From john@jlc.net  Fri May  3 10:23:37 2013
Return-Path: <john@jlc.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 7D65821F8AF8 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:23:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104
X-Spam-Level: 
X-Spam-Status: No, score=-104 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbm4GE-rMdKG for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:23:31 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1F721F978E for <ietf@ietf.org>; Fri,  3 May 2013 09:52:27 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 12CFF33C27; Fri,  3 May 2013 12:52:26 -0400 (EDT)
Date: Fri, 3 May 2013 12:52:26 -0400
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <20130503165226.GN23227@verdi>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org> <5183CB90.7030900@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5183CB90.7030900@dcrocker.net>
User-Agent: Mutt/1.4.1i
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: Fri, 03 May 2013 17:23:37 -0000

Dave Crocker <dhc@dcrocker.net> wrote:
> On 5/3/2013 7:29 AM, Ray Pelletier wrote:
> 
>> Provide WG Chairs the monitoring tools they need to be proactive - Action 
>> Tracker, what do I need to do today data tracker  views.  Same for AD.
>>
>> Same for authors and their mentors, if any.
> 
> The IETF already provides pretty good tools.  They could always be 
> better, of course, but they almost certainly aren't essential.

   That much is probably true.

> The issue with providing management assistance is to focus on managing 
> the work.  That's an organizational orientation, not just a tracking 
> thing.  It's about getting clarity of the work to be done and of getting 
> folks to do the work of contributing, writing, reviewing, and debating 
> in a timely manner, and achieving forward progress in a timely manner.

   That much is true.

> Few working groups have enough detail to juggle to make this something 
> that hinges on the tools.

   That, alas, is not true.

   I subscribe to a number of WG lists where they find a issue tracker
_quite_ essential to their work. And to most folks, the issue tracker
output is more confusing than helpful: you're never quite sure which
issue number something belongs under.

   The lists I subscribe to have as work items drafts where nothing
happens until IETF-week deadlines (and sometimes not even then!).

   It seems _very_ likely that some automated tools to point out the
inactivity would help...

--
John Leslie <john@jlc.net>

From randy@psg.com  Fri May  3 10:31:05 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488BC21F87B7 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:31:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1MoELJTOYI3I for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:31:04 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id C649921F99A8 for <ietf@ietf.org>; Fri,  3 May 2013 09:08:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UYIX8-000Gev-Pf; Fri, 03 May 2013 16:08:31 +0000
Date: Fri, 03 May 2013 09:08:30 -0700
Message-ID: <m2k3ngkpvl.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
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, 03 May 2013 17:31:05 -0000

> One possible step is to have WG Chairs be *managers*, like they are
> supposed to be.
> ...
> The current cycle too often seems to be more like "new version
> posted".  Wait if anyone reviews.  Some reviews eventually, maybe. Oh,
> IETF meeting coming, time for a revision.

with wg chairs taking multiple months to do the simplest of button
pushes, authors slow down so that they get the most out of that oh so
rare button push.

randy

From warren@kumari.net  Fri May  3 10:33:33 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAE5F21F86D3 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J3w4oXZnb90I for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:33:27 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA47521F97B7 for <ietf@ietf.org>; Fri,  3 May 2013 10:02:01 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.117]) by vimes.kumari.net (Postfix) with ESMTPSA id 958B21B405DF; Fri,  3 May 2013 13:01:55 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Re: Balancing the Process (Was: Obsoleting SPF RRTYPE)
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <20130503015620.E520433A79C0@drugs.dv.isc.org>
Date: Fri, 3 May 2013 13:01:55 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <86172038-8F62-4508-8199-BE4C16906A65@kumari.net>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu> <51811C20.5040305@qti.qualcomm.com> <5182828C.3040200@isdg.net> <20130503015620.E520433A79C0@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1503)
Cc: Pete Resnick <presnick@qti.qualcomm.com>, hostmaster@earthlink.net, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:33:34 -0000

On May 2, 2013, at 9:56 PM, Mark Andrews <marka@isc.org> wrote:

>=20
> In message <5182828C.3040200@isdg.net>, Hector Santos writes:
>> Mr. Resnick,  for the record, I wasn't upset. Believe it or not, I =
was=20
>> actually applying an suggestion posted last month or so here with the=20=

>> IETF diversity talks to help get a major WG issue resolved, one with =
a=20
>> near surety of an appeal, resolved and addressed much faster and =
hence=20
>> avoid a waste of time on the behalf of all.
>>=20
>> How appropo, that a topic of "balancing of process" as being =
considered.=20
>>   It is one thing I believe the IETF needs and can be actually apply=20=

>> today. Yes, I don't agree with the negative tone taken in SPFBIS =
where=20
>> in effect, an attempt to shut down communications and indirectly=20
>> personally attack posters occurred and the advocates of the SPF =
RRTYPE=20
>> removal (incidentally, a SPEC change which I believe was prohibited =
by=20
>> the charter), basically blowing off advocates of a RFC4408 status =
quo.=20
>> If you believe that was proper, I think we have a WG problem.
>>=20
>> Overall, I believe this (keep the migration path) is the proper=20
>> compromise to resolve the issue, and I believe that this particular=20=

>> issue is industry-wide important to resolve with across the board=20
>> engineering input. It *SHOULD NOT* be reserved only to the =
applications=20
>> SPFBIS group especially when we know what the DNS community will say=20=

>> about this and has said so since MARID 2003 and again last year in =
IETF=20
>> and DNSOPs. I was simply hoping to help "Balance the process" then as =
I=20
>> was attempted to do again.  If I was in error for trying to get a=20
>> serious issue resolve, then please accept my apology.
>>=20
>> Sincerely,
>>=20
>> Hector Santos
>=20
> One of the questions is how to deal with vendors that claim to ship
> a product which is in compliance with the protcol when they are
> not.
>=20
> The DNS protocol has a error code for when you do not understand a
> query, FORMERR.  It also has a error code for when you do not
> implement part of the protocol, NOTIMP.
>=20
> With RFC 103[45] you have three choices as a developer when you get
> a query type you don't know about.
>=20
> 1. Treat it as a FORMERR.
> 2. Treat it as a NOTIMP.
> 3. Treat it as a opaque data.
>=20
> Now in my book it isn't a FORMERR as you can understand the question
> even if you can't deal with it.  NOTIMP is a reasonable response
> though I believe the intent in RFC 103[45] was to treat it as opaque
> data query which is what RFC 3597 says to do.
>=20
> Nowhere in RFC 103[45] does it say DO NOT RESPOND to the query yet
> we have DNS vendors that ship products that do just that and are
> claiming that they conform to the protocol.
>=20
> For a example of a set of servers that does this see earthlink.net's
> servers.
>=20
> Query for HINFO/earthlink.net at the authoritative servers for
> earthlink.net (itchy.earthlink.net and scratchy.earthlink.net) and
> you will not get a response.  A RFC 103[45] compliant server should
> know about HINFO.  It should also be capable of returning a NOERROR
> NODATA response for that query and it fact will if you ask for a
> non-existent TXT record at a name it serves.
>=20
> How do we deal with sites?
> How do we deal with vendors that ship such product?

Unless the caffeine just hasn't sunk in yet, it works for me:

wmbt-macbookair:Preferences wkumari$ dig HINFO earthlink.net =
@scratchy.earthlink.net

; <<>> DiG 9.8.3-P1 <<>> HINFO earthlink.net @scratchy.earthlink.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1906
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;earthlink.net.			IN	HINFO

;; AUTHORITY SECTION:
earthlink.net.		1800	IN	SOA	itchy.earthlink.net. =
hostmaster.earthlink.net. 2013042602 3600 300 2592000 1800

;; Query time: 51 msec
;; SERVER: 207.69.188.197#53(207.69.188.197)
;; WHEN: Fri May  3 12:59:50 2013
;; MSG SIZE  rcvd: 84

So, maybe the way you fix such sites / deal with vendors that ship such =
products is you post to ietf@ietf.org and cc hostmaster@site?

:-P
W


>=20
> Mark
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>=20

--
Hope is not a strategy.
      --  Ben Treynor, Google



From narten@us.ibm.com  Fri May  3 10:36:40 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D3AC21F8EC9 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108
X-Spam-Level: 
X-Spam-Status: No, score=-108 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XkkfKfCrVgKW for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:36:32 -0700 (PDT)
Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by ietfa.amsl.com (Postfix) with ESMTP id CC90221F9764 for <ietf@ietf.org>; Fri,  3 May 2013 10:15:18 -0700 (PDT)
Received: from /spool/local by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 11:15:16 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 11:15:13 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 801651FF0026 for <ietf@ietf.org>; Fri,  3 May 2013 11:10:07 -0600 (MDT)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r43HErlK084720 for <ietf@ietf.org>; Fri, 3 May 2013 11:14:56 -0600
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 r43HEqkw005503 for <ietf@ietf.org>; Fri, 3 May 2013 11:14:52 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-147-40.mts.ibm.com [9.49.147.40]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r43HEigj004682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 11:14:46 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r43HEajN019853; Fri, 3 May 2013 13:14:37 -0400
Message-Id: <201305031714.r43HEajN019853@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
Comments: In-reply-to Ray Pelletier <rpelletier@isoc.org> message dated "Fri, 03 May 2013 10:29:22 -0400."
Date: Fri, 03 May 2013 13:14:36 -0400
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050317-7606-0000-0000-00000B0FE5D8
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, 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: Fri, 03 May 2013 17:36:40 -0000

Ray Pelletier <rpelletier@isoc.org> writes:

> Provide WG Chairs the monitoring tools they need to be proactive -
>  Action Tracker, what do I need to do today data tracker views.
>  Same for AD.

> Same for authors and their mentors, if any.

Tools may help in some cases (IESG, chairs), but the fundamental
problem is not tools. It's about work culture, setting proper
expectations (and communicating them to everyone), and having
accountability and followup to fix things when stuff isn't happening.

Thomas


From daedulus@btconnect.com  Fri May  3 10:37:48 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1D2821F9745 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zpP5VCX8-2QY for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:37:42 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 08ABF21F97DB for <ietf@ietf.org>; Fri,  3 May 2013 10:22:04 -0700 (PDT)
Received: from mail135-va3-R.bigfish.com (10.7.14.235) by VA3EHSOBE006.bigfish.com (10.7.40.26) with Microsoft SMTP Server id 14.1.225.23; Fri, 3 May 2013 17:21:50 +0000
Received: from mail135-va3 (localhost [127.0.0.1])	by mail135-va3-R.bigfish.com (Postfix) with ESMTP id 46E85140269; Fri,  3 May 2013 17:21:50 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zz98dI9371I542I1432I168aJzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275bh8275dh1033ILz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail135-va3 (localhost.localdomain [127.0.0.1]) by mail135-va3 (MessageSwitch) id 1367601708637011_10419; Fri,  3 May 2013 17:21:48 +0000 (UTC)
Received: from VA3EHSMHS009.bigfish.com (unknown [10.7.14.244])	by mail135-va3.bigfish.com (Postfix) with ESMTP id 9641042012C; Fri,  3 May 2013 17:21:48 +0000 (UTC)
Received: from DBXPRD0711HT002.eurprd07.prod.outlook.com (157.56.254.181) by VA3EHSMHS009.bigfish.com (10.7.99.19) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 3 May 2013 17:21:48 +0000
Received: from AMXPRD0310HT002.eurprd03.prod.outlook.com (157.56.248.133) by pod51017.outlook.com (10.255.178.35) with Microsoft SMTP Server (TLS) id 14.16.305.3; Fri, 3 May 2013 17:21:46 +0000
Message-ID: <02d901ce4821$f9ee7cc0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Ray Pelletier <rpelletier@isoc.org>, <adrian@olddog.co.uk>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net><32577.1367426027@sandelman.ca><201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com><5183BB59.7090206@cs.tcd.ie><201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com><04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org>
Subject: Re: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 18:14:59 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.133]
X-OriginatorOrg: btconnect.com
Cc: Thomas Narten <narten@us.ibm.com>, 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: Fri, 03 May 2013 17:37:49 -0000

----- Original Message -----
From: "Ray Pelletier" <rpelletier@isoc.org>
To: <adrian@olddog.co.uk>
Cc: "Thomas Narten" <narten@us.ibm.com>; "IETF list" <ietf@ietf.org>
Sent: Friday, May 03, 2013 3:29 PM

On May 3, 2013, at 10:20 AM, "Adrian Farrel" <adrian@olddog.co.uk>
wrote:

> Well said, Thomas.
>
>> Two concrete suggestions:
>>
>> 1) have WGs do the managing role more proactively

Provide WG Chairs the monitoring tools they need to be proactive -
Action Tracker, what do I need to do today data tracker  views.  Same
for AD.

<tp>

Such as a list once a month, sent to the list of each active WG, of the
state change, if any, in the I-Ds which have been accepted by the WG as
work items, giving the date at which the last state change occurred.
State is not just the IESG type tracker state, but also a new revision
of the I-D.

I know how useful I find this from the WG Chairs who produce it already.

Tom Petch


Same for authors and their mentors, if any.

Ray


>> 2) mentor authors and others a bit more to encourage them how best to
>> operate
>
> Which I suspect means...
>
> 0) have ADs manage/mentor the WG chairs more proactively.
>
> Almost certainly a case of "if I had less work to do I would have more
time to
> do the things that would reduce my workload."  :-)
>
> WG chairs might like to comment, but I suspect that one lunchtime
training
> session every four months does not constitute proactive management.
>
> Adrian
>



From narten@us.ibm.com  Fri May  3 10:40:13 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF1321F9348 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108
X-Spam-Level: 
X-Spam-Status: No, score=-108 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srwRLAhoxiw6 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:40:06 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 04CD321F9748 for <ietf@ietf.org>; Fri,  3 May 2013 10:29:28 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 11:29:28 -0600
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 11:29:26 -0600
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 26FB86E8041 for <ietf@ietf.org>; Fri,  3 May 2013 13:29:23 -0400 (EDT)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r43HTPVc178888 for <ietf@ietf.org>; Fri, 3 May 2013 13:29:25 -0400
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 r43HTOFv018261 for <ietf@ietf.org>; Fri, 3 May 2013 11:29:24 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-147-40.mts.ibm.com [9.49.147.40]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r43HTNp1018150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 11:29:24 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r43HTMPk021875; Fri, 3 May 2013 13:29:22 -0400
Message-Id: <201305031729.r43HTMPk021875@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: dcrocker@bbiw.net
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <5183CB90.7030900@dcrocker.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org> <5183CB90.7030900@dcrocker.net>
Comments: In-reply-to Dave Crocker <dhc@dcrocker.net> message dated "Fri, 03 May 2013 07:37:04 -0700."
Date: Fri, 03 May 2013 13:29:22 -0400
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050317-3620-0000-0000-000002525C46
Cc: IETF list <ietf@ietf.org>, "adrian@olddog.co.uk" <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: Fri, 03 May 2013 17:40:13 -0000

Dave Crocker <dhc@dcrocker.net> writes:

> The issue with providing management assistance is to focus on
> managing the work.  That's an organizational orientation, not just a
> tracking thing.  It's about getting clarity of the work to be done
> and of getting folks to do the work of contributing, writing,
> reviewing, and debating in a timely manner, and achieving forward
> progress in a timely manner.

> Few working groups have enough detail to juggle to make this
> something that hinges on the tools.

Strongly agree here.

Let me expand further on "work plan" and  "project management".

It needs to be done on a per-document basis. I.e., Wouldn't it be nice
if every WG document was revised 3 times between meetings? I bet that
alone would change dynamics (assuming there were substantive
changes)...

But it extends to the WG as a whole.  WGs have a finite number of
cycles. There are always a small number of core players (whether
editor, reviewer, etc.), and if you spread their resources too thinly,
a WG starts having problems.

Few WGs acknowledge that and try to manage it. Managing it means:

1) identifying core documents that are priority, and minimizing
distractions that will take cycles away from the priority
deliverables.

2) It may mean making concious decisions not to work on some documente
*yet* in order to concentrate resources where it matters

3) it means tying the work plan directly back to the charter. If the
two aren't in sync, one or both need changing.

4) It means recognizing that there are real limits to how many
documents a WG can (credibly) work on at any one time. (Too many WGs
have lots of marginal documents that suck cycles away from the
critical ones.) How many WGs say "no" to marginal documents?

Thomas


From mcr@sandelman.ca  Fri May  3 10:40:35 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3505D21F8673 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKgCEGO4mZS2 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:40:34 -0700 (PDT)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 216E321F8E6D for <ietf@ietf.org>; Fri,  3 May 2013 10:31:54 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5A4D62016D; Fri,  3 May 2013 13:42:54 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 1276AA9984; Fri,  3 May 2013 13:31:20 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id EBD4A63A6C; Fri,  3 May 2013 13:31:20 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 03 May 2013 13:31:20 -0400
Message-ID: <30759.1367602280@sandelman.ca>
Sender: mcr@sandelman.ca
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: Fri, 03 May 2013 17:40:35 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Thomas" =3D=3D Thomas Narten <narten@us.ibm.com> writes:
    Thomas> The current cycle too often seems to be more like "new
    Thomas> version posted". Wait if anyone reviews. Some reviews
    Thomas> eventually, maybe. Oh, IETF meeting coming, time for a
    Thomas> revision. But with meeting approaching, there are a zillion
    Thomas> docs and cycles are limited.  Rather haphazard, with too
    Thomas> many documents effectively only being revised once per
    Thomas> meeting cycle.

I would like to suggest that the IESG Review be done in public on the WG
mailing list.    I've been a WG co-chair for just over a year now, and
I'm truly astounded by what happens behind the scenes.=20=20

It's not the substance, it's the quantity, and the lack of WG view of
it.   I think that this substantially and quite negatively contributes
to the "fix it during IESG review", and therefore to the IESG workload.

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUYP0aIqHRg3pndX9AQIAQwQAvV/jV33o4dXrUGlVQZ3kl6SIkUQJYs8g
ggGwnXKV8Cm0JXjdWed8y7ucxhBoZ7z0kgD8+AktkwbTWoVnjLxmApGHozRGOqz+
4V5wuwYfYWvfBOstEpl3gYmelLT8eKIq6syhHkVbKNnV0E/iFuSNzxpmwiO5CNCR
hwWBDEbN8M8=
=pKdF
-----END PGP SIGNATURE-----
--=-=-=--

From alh-ietf@tndh.net  Fri May  3 10:44:38 2013
Return-Path: <alh-ietf@tndh.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 CE32921F845E for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:44:38 -0700 (PDT)
X-Quarantine-ID: <QVXVRHvzR4Ah>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: 1.239
X-Spam-Level: *
X-Spam-Status: No, score=1.239 tagged_above=-999 required=5 tests=[NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVXVRHvzR4Ah for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:44:38 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 9339521F968F for <ietf@ietf.org>; Fri,  3 May 2013 10:41:40 -0700 (PDT)
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1UYJyz-0005Rz-94; Fri, 03 May 2013 10:41:30 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Pete Resnick'" <presnick@qti.qualcomm.com>, "'Thomas Narten'" <narten@us.ibm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<32577.1367426027@sandelman.ca>	<201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>	<5183BB59.7090206@cs.tcd.ie>	<201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>	<04a601ce4809$5679a000$036ce000$@olddog.co.uk>	<201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <5183D3CB.60702@qti.qualcomm.com>
In-Reply-To: <5183D3CB.60702@qti.qualcomm.com>
Subject: RE: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 10:41:21 -0700
Message-ID: <00e001ce4825$6cad2740$460775c0$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKYyBhEoNBNJ3MPVKuNyDDagY8byQGPmImJAoVjNqoCWVDxGgGC+2YGApKHHrICSJvMmAHSSHO4lum6DBA=
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false
Cc: adrian@olddog.co.uk, '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: Fri, 03 May 2013 17:44:38 -0000

Pete Resnick wrote:
...
> On 5/3/13 7:59 AM, Thomas Narten wrote:
> 
> > Like everyone, I wish things moved more quickly, but every attempt
> > I've ever seen that tries to speed things up ends up reducing the
> > quality or having some other undesirable side effect.
> >
> 
> Can you talk a bit more about this, including some examples?
> 
> I'm trying to reconcile the concern that we "end up reducing the quality"
and
> that we "NOT neglect longer-term stuff that will have real and
significant, but
> not immediate benefits." ADs have finite resources and can't accomplish
> both immediate and longer-term stuff maximally all of the time. My
> inclination would be to say, "If they are in conflict, weight the
longer-term
> over the immediate, even if that might result in some reducing of quality
on
> any single document." Am I over-reading your earlier message to say that
> you think the weighting should go toward the immediate? I think we agree
> that doing the longer-term stuff will end up with increased quality over
the
> long term, but doing more of the longer-term stuff is sure to reduce the
> amount of time spent on immediate, which means document reviews and
> therefore some short term lowering of quality. Is that OK, or is that an
> example of the kind of thing we've attempted that ends up with bad
results?
> 

Pete,

I would agree with you that weighting longer term is the 'right thing', but
given that people wait for an RFC number to implement, and then take the
position that RFC (PS) == STD, you never get to the longer term because the
bar is set so high on the first hurdle that it becomes impossible for people
to justify the effort to go for the next one.



When the I-D series was introduced specifically to deal with the issue of
RFC == STD, we didn't get it right. In hind sight we should have done
something more like the IEEE does with 802.11, and explicitly put a big
DRAFT: in the title. Industry doesn't seem to get confused about DRAFT: N or
DRAFT: AC, and still deploys, then moves on with full standards. We could
still do that, and likely get motivation to move a DRAFT: to PS (remove the
DRAFT: from the title) by wider review and deployment. I realize this is
really doing nothing more than introducing an extra step in the process, but
in some ways it is more of a formalization of the expected behavior at the
first RFC step. One could go so far as to not remove DRAFT: until the spec
met DS, and move the default  from PS to DS at the same time as removing the
extra step from the process. One could really get crazy and just remove DS
from the list, because nobody understands what that one is for anyway, and
then when the DRAFT: gets removed from the title it is really the STD people
are expecting ... ;)

In any case I don't see 60/40 as a tail-heavy process. If the WG time were
cut in half and the IESG/RFC-editor time stayed the same, maybe it would be
tail-heavy, but realistically more 'balanced'.  At the end of the day, the
only way to reduce the time at IESG review is to have a document with clear
objectives up front that the document can be evaluated against, and for the
WG to put a quality document in their hands. Too often the WG takes so long
that the objectives drift, if they were even clearly stated up front, and
comments like "you have to have been involved in the mail thread" show up
during review. If something is not clear in the document, and it was cleared
up in a meeting or on the mail list, that clarification needs to get moved
into the document or subsequent reviewers / implementers will never get it,
and the result is delay and/or poor quality documents. 

Tony


From rdroms.ietf@gmail.com  Fri May  3 10:45:21 2013
Return-Path: <rdroms.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 94BB221F8414 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LuGvQABsyCGZ for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:45:20 -0700 (PDT)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 9936021F842B for <ietf@ietf.org>; Fri,  3 May 2013 10:43:41 -0700 (PDT)
Received: by mail-qc0-f175.google.com with SMTP id u28so345975qcs.34 for <ietf@ietf.org>; Fri, 03 May 2013 10:43:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=6KNCUVOBhLoGtgy6YeXUh+8yv3U0pPNMOMjkEzO5R8w=; b=ox9ldcxX/Kr47YsXYe22NEc76T2ExOZQHmHePE+mvy1VStoOy5hLRl2PA6wiJrKf6/ UYIh/PJ+lamRUBTgZx7I0ylCCyl6B5RPSpVagVEbLHCY6fmg0fLwkj7MQKRhfUHIJca6 yJ1oAc549Y0Y6kiFzN9JXl5LJgDrRsBYV7nxSgZoBUKqZrJwGYYQrPNEdCm6b/ykePFy Emn9zutbVnSzUzXwGinEhQqnjTtN1fy8fgmzX2YXTMsso5dandSA4LZFb7gqo2a//SG9 O0CrKFC6QTwUIc2i9iWSU9euGC9nH7LuqNwKNBJ/ij3JSZSGskZR4aSOZGx5kX37LGTw cRsA==
X-Received: by 10.229.164.79 with SMTP id d15mr4875728qcy.3.1367603020978; Fri, 03 May 2013 10:43:40 -0700 (PDT)
Received: from [161.44.65.173] ([161.44.65.173]) by mx.google.com with ESMTPSA id bv6sm19068033qab.5.2013.05.03.10.43.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 10:43:39 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
Date: Fri, 3 May 2013 13:43:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1557AD51-D095-4FF3-9459-C4A0C9957797@gmail.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1503)
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: Fri, 03 May 2013 17:45:21 -0000

On May 3, 2013, at 8:59 AM 5/3/13, Thomas Narten <narten@us.ibm.com> =
wrote:

> Just a few points...
>=20
> Michael Richardson <mcr+ietf@sandelman.ca> writes:
>=20
>> I'll repeat what has been said repeatedly in the newtrk and related
>> discussions.  The step from ID to "RFC" is too large because we are
>> essentially always aiming for "STD" rather than "PS".
>=20
>> If we are unwilling to bring "RFC" back to a place were it does not
>> equal STD, then we need to create a new category of document which
>> amounts to "fully baked ID".  Things like IANA allocations could =
occur
>> at that point.
>=20
>> In the days of dot-boom it was not unusual to see widespread
>> implementation very early in the ID process and even interop and
>> experimental deployment.   While this still occurs for quite a number =
of
>> things (and sometimes it's a problem that the ID can not be changed =
as a
>> result), there is an equal amount of "wait for the RFC to come out".
>=20
> I suspect there is a bit of rose colored reminiscing of history.
>=20
> The world has changed, significantly.
>=20
> For example, there has been massive consolidation in industry. There
> simply are fewer entities doing implementations today. 15 years ago,
> it was common to see a half dozen or more implementations from
> different (often smaller) entities, even before a document got out of
> a WG. Nowadays, the cost of doing an implementation (for a company) is
> in some sense much higher, and business realities make companies
> *very* selective in what they implement and put into a product.

Adding a little detail - those implementations have to be prototypes, =
with the implementing entities willing to make changes in the code prior =
to shipping product. Once the code has been shipped to customers, there =
is a lot of resistance to making changes to the specification. =20

> I suspect that the notion that if the IETF published documents more
> quickly industry would implement them more quickly/frequently is
> wishful thinking.
>=20
> Michael Richardson <mcr+ietf@sandelman.ca> writes:
>> It's what Carsten said.
>=20
>> 1) this idea is baked enough for cross-area review to make sense.
>> 2) the protocol is not going to change significantly, one could
>>   implement.
>> 3) any future changes need thus to take into account impact on
>>   existing implementations... BUT that doesn't mean that we can't
>>   change things.
>=20
> Like it or not, 2 and 3 are contradictory. =46rom an interoperability
> perspective, the difference between "not change significantly" and
> "change a lot" is irrelevant once you have deployments. Change (in the
> behavior or wire format) is change and breaks interoperability, no
> matter how big or small.

Right, so declaring a document a "fully baked ID" might have the =
perverse effect of freezing specifications at a point where there are =
still problems.

The key issues are the investment in an implementation, the cost of =
updating an implementation and, perhaps most importantly, the cost of =
making changes to code that has been shipped in products.

>=20
> Hannes Tschofenig <hannes.tschofenig@gmx.net> writes:
>=20
>> b) There is no interest to research where delay really happen.
>=20
> I don't think that is true. Jari has pointed to his work. I think
> there is actually quite a lot of understanding of where the delays
> are. But fixing them is really really hard. Blaming the "tail end" or
> "the IESG" for the problems has always been the easy target. The
> reality (IMO) is that the place where improvements are needed is
> within the WG and on having authors be more responsive. But history
> suggests there are no easy fixes here.
>=20
> Randy Bush <randy@psg.com> writes:
>=20
>>> A basic question, then, is whether we think these absolute numbers =
and
>>> these proportions of time are reasonable and appropriate for the =
IETF
>>> to be/remain effective?
>=20
>> seems pretty reasonable to me.  from personal experience, the iesg =
and
>> rfced add useful value.
>=20
> +1

It would be interesting to understand the cost of that useful value, and =
whether the same useful value could be provided elsewhere at reduced =
cost.

"Cost" in this case can be tricky - the useful value in IESG review =
comes at the cost of asking the members of the IESG to invest 10s of =
hours per week in careful review of every document.  That time =
requirement contributes to the notion that being an AD is a full time =
job, which in return reduces the diversity of the pool of candidates =
willing to volunteer for an AD position.

So, there is useful value, but can we get that same value by =
distributing the load out to the larger community?

>=20
> Like everyone, I wish things moved more quickly, but every attempt
> I've ever seen that tries to speed things up ends up reducing the
> quality or having some other undesirable side effect.
>=20
> The bottom line is that getting a good spec requires iteration, and
> reviews from a broad set of parties. That is best done
> *sequentially*. And given the limited cycles the (volunteer) community
> as a whole has, you can't easily change these dynamics. We've seen
> many attempts to reduce the overall time by trying to overlap reviews
> and steps, but that has the side effect of losing *sequential*
> *iteration* (where each new review reviews the previous set of
> additions/changes). IMO, overlapping steps is dangerous and leads to
> poor quality.
>=20
>> being in a many-year process of getting a technology through the
>> saussage machine, it's the wg that feels to me to be the most
>> inefficient part of the process.  i attribute this to email not being
>> the best medium, and meetings being too short and too far between.  =
but
>> that is purely subjective.
>=20
> If you want to speed up the process, focus on how to *increase* the
> amount of iteration you get (i.e., revised drafts) while at the same
> time *reducing* the time between revised drafts.
>=20
> If you look at the delays documents encounter (both in WG and in IESG
> review), the killer is long times between document revisions. Focus on
> understanding the *why* behind that and what steps could be taken to
> make improvements.

This claim sounds right to me.  Can we document it?

The long delays, I'll bet, can be a result of a feedback loop - a long =
delay before a new revision is might tend to increase the number of =
changes in the new rev and the details of the draft have dropped out of =
short-term memory for those who are following the draft.  So, reviewing =
the new rev becomes lower priority and there's a longer delay before =
comments are published.  In general, the draft seems less important and =
gets a lower priority...
>=20
> And finally, a big reason the IESG review is where things happen is
> that it *really* is the last time one has to verify that a document is
> ready to go. With the limited cycles we all have, there will always be
> a tendancy to not deal with a document until the point of "this is
> your last chance". Nothing like a *real* deadline to motivate people
> to finally deal with a document, before it's too late.

And, I'll suggest there is a lack of accountability toward everyone who =
was supposed to have contributed to a document that is ready to publish =
when it gets to the IESG .

Suppose, for a moment, the IESG approved a document for publication with =
a serious technical flaw?  Who would be accountable?

A large percentage of documents reviewed by the IESG receive at least =
one DISCUSS position.  What are the consequences to the document =
authors, the WG and the IETF?

- Ralph

>=20
> Thomas
>=20


From envite@rolamasao.org  Fri May  3 10:54:58 2013
Return-Path: <envite@rolamasao.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 6683E21F93FC for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.037
X-Spam-Level: ****
X-Spam-Status: No, score=4.037 tagged_above=-999 required=5 tests=[AWL=0.300,  FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, HELO_MISMATCH_ORG=0.611, HOST_EQ_STATIC=1.172, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5fT-YYb-Wlrs for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 10:54:53 -0700 (PDT)
Received: from rolamasao.org (68.167.216.87.static.jazztel.es [87.216.167.68]) by ietfa.amsl.com (Postfix) with ESMTP id F3F5D21F853D for <ietf@ietf.org>; Fri,  3 May 2013 10:54:52 -0700 (PDT)
Received: from tochox.localnet (localhost [IPv6:::1]) by rolamasao.org (Postfix_t) with ESMTPSA id A93DC11EDA for <ietf@ietf.org>; Fri,  3 May 2013 18:54:51 +0100 (WEST)
From: Noel David Torres =?iso-8859-1?q?Ta=F1o?= <envite@rolamasao.org>
To: ietf@ietf.org
Subject: Re: [spfbis] [dnsext] Obsoleting SPF RRTYPE
Date: Fri, 3 May 2013 18:54:46 +0100
User-Agent: KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; )
References: <20130425013317.36729.qmail@joyce.lan> <CAL0qLwY3NAtkcznaLf-aNrKtSQLFdrPy4JV=Vmbic5kYB-wfew@mail.gmail.com> <51827DD5.4010402@cisco.com>
In-Reply-To: <51827DD5.4010402@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2878309.ABbv3JIxdq"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201305031854.47094.envite@rolamasao.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 17:54:58 -0000

--nextPart2878309.ABbv3JIxdq
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit

On Jueves, 2 de mayo de 2013 15:53:09 Eliot Lear wrote:
> 3.  What can be done by the IETF to improve likelihood of adoption, and
> conversely what should we not bang our heads against?

Amend the Wikipedia article about SPF, where it states that it is TXT only?

-------------------------
A: Because it breaks the logical flow of discussion.
Q: Why is top posting bad?

--nextPart2878309.ABbv3JIxdq
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEUEABECAAYFAlGD+ecACgkQcLQA8+7Hw3I4+ACVF3sl2fWhEUZc54r6T1pKRnsu
GACfRXk4+PKretpUzJrIdmAOZa44ZmE=
=pWen
-----END PGP SIGNATURE-----

--nextPart2878309.ABbv3JIxdq--

From worley@shell01.TheWorld.com  Fri May  3 11:03:28 2013
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 DC9C821F96E9 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:03:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.117
X-Spam-Level: 
X-Spam-Status: No, score=0.117 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=1.117]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJ2EiSL0zRrY for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:03:23 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 8244521F96E8 for <ietf@ietf.org>; Fri,  3 May 2013 11:03:22 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r43I1wKF018113; Fri, 3 May 2013 14:02:01 -0400
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 r43I1uaO4043491; Fri, 3 May 2013 14:01:56 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r43I1ufu4053966; Fri, 3 May 2013 14:01:56 -0400 (EDT)
Date: Fri, 3 May 2013 14:01:56 -0400 (EDT)
Message-Id: <201305031801.r43I1ufu4053966@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Scott Brim <swb@internet2.edu>
In-reply-to: <51839ABA.4010406@internet2.edu> (swb@internet2.edu)
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 18:03:29 -0000

> From: Scott Brim <swb@internet2.edu>
> 
> My experience is that unless the editors have some background in
> protocols, this takes a surprising amount of effort, explaining it to
> them and catching _their_ mistaken assumptions (which can be subtle).

I'm told that the CCITT maintains a staff of technical writers.
Certainly, the *writing* in their standards is better.

Dale

From presnick@qti.qualcomm.com  Fri May  3 11:04:35 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F240B21F9707 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aoRHyqzmjYRS for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:04:31 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id BCFDC21F9718 for <ietf@ietf.org>; Fri,  3 May 2013 11:04:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1367604271; x=1399140271; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=f5vghkoMZKxsHwOvhmOTKofDK1tun6DQZaDwBhBWZAM=; b=tzAyDugNJU174G2Qdg5AmNdTKDbwokrDm/nkYXPmc6zDfVR6CM/x/Q52 jMVHF3QjIFIG8H7TB4hDTd/6tGXdEkDaBwmLMd5j4n0LgUO7tOKGbC4tp o87XzguNiYJeRjKmmbFsuDPmLK9aKYU7VuCKRjWMYDliFHq7cWf96I2hV k=;
X-IronPort-AV: E=Sophos;i="4.87,606,1363158000"; d="scan'208";a="38078379"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 03 May 2013 11:04:31 -0700
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 May 2013 11:04:30 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 3 May 2013 11:04:30 -0700
Message-ID: <5183FC29.8040804@qti.qualcomm.com>
Date: Fri, 3 May 2013 13:04:25 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Tony Hain <alh-ietf@tndh.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<32577.1367426027@sandelman.ca>	<201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>	<5183BB59.7090206@cs.tcd.ie>	<201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>	<04a601ce4809$5679a000$036ce000$@olddog.co.uk>	<201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>	<5183D3CB.60702@qti.qualcomm.com> <00e001ce4825$6cad2740$460775c0$@tndh.net>
In-Reply-To: <00e001ce4825$6cad2740$460775c0$@tndh.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: 'Thomas Narten' <narten@us.ibm.com>, adrian@olddog.co.uk, '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: Fri, 03 May 2013 18:04:36 -0000

Not disagreeing with your message, but a couple of clarifying points:

On 5/3/13 12:41 PM, Tony Hain wrote:

> I would agree with you that weighting longer term is the 'right thing', but
> given that people wait for an RFC number to implement, and then take the
> position that RFC (PS) == STD, you never get to the longer term because the
> bar is set so high on the first hurdle that it becomes impossible for people
> to justify the effort to go for the next one.
>    

When Thomas said "longer-term", I took him to mean *all* of the things 
that are longer time horizon, like management/mentoring of WGs and 
chairs, doing more early cross-area participation (including by ADs) in 
the design of and work on protocols (not just review), etc. In 
particular, I didn't understand him to mean longer-term as having 
anything to do with advancement on the standards track. I think the 
above longer-term goals are important. I think movement along the 
standards track will be the outcome if we get to working well, but not a 
goal in-and-of itself.

> In any case I don't see 60/40 as a tail-heavy process. If the WG time were
> cut in half and the IESG/RFC-editor time stayed the same, maybe it would be
> tail-heavy, but realistically more 'balanced'.
>    

I'll point you to Jari's excellent reminder that "time" is probably the 
least of the heaviness on the tail end. What is tail heavy is the work 
investment: We do WG last call reviews, IETF-wide Last Call reviews, 
directorate reviews, IESG reviews, all at the end of the process. We 
spend scant little energy (of the wider IETF community and leadership) 
on early design reviews and protocol development early and in the middle 
of the document process. As Jari said, that model ends us up with late 
surprises, lack of transparency, etc., and probably uses much more 
energy overall than if we invested it earlier in the process. Sure, this 
can translate to delays, but that's only one (maybe minor) effect of 
being tail-heavy.

pr

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


From johnl@iecc.com  Fri May  3 11:53:25 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D52B21F8A48 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.9
X-Spam-Level: 
X-Spam-Status: No, score=-109.9 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlqAGZKhLwHe for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:53:20 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 3982721F8202 for <ietf@ietf.org>; Fri,  3 May 2013 11:53:19 -0700 (PDT)
Received: (qmail 47102 invoked from network); 3 May 2013 18:53:18 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 May 2013 18:53:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5184079e.xn--yuvv84g.k1305; i=johnl@user.iecc.com; bh=uAn0cqRKgT3gf/ViLd8Bzo62i6JCL9FyPYZFTN87Yks=; b=jzis7FE4C6+q7y5ZxPDpBDqqCOpe8hrZgLlWg7Laa+5qBwb+IyrZTyPJ4b8jGJ8cg+audmpCRyyL8BfnDsdUNM4t7EI3ze9MbXS9EkKVdU4YRvt5qxjbSGCOGh2jUuPdwT3Ccs7RFRZkEkGOgOGZPlMI6QU3/QNhK238WRNbtYw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=5184079e.xn--yuvv84g.k1305; olt=johnl@user.iecc.com; bh=uAn0cqRKgT3gf/ViLd8Bzo62i6JCL9FyPYZFTN87Yks=; b=G6VPBxj609jVnjEdmKbaipUjyC/ZJX4yei2IsE7uXz9E3jngu8I/eU4psSDX1K1fajEBm/79pBsAwMNbt8OtS/GII0W9J/204iaTNaPdboKDjGzwEc1K5lMwh7V68vqu/zHd1n0kpx6c2haM+UJ1TxnVL+13oHyDjtGU+r1VjDQ=
Date: 3 May 2013 18:52:55 -0000
Message-ID: <20130503185255.41269.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Last Call: Change the status of DKIM (RFC 6376) to Internet Standard
In-Reply-To: <20130503162119.31310.96671.idtracker@ietfa.amsl.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 18:53:27 -0000

I use DKIM via two independent implementations, perl Mail::DKIM to
sign outgoing mail, and C language opendkim to check incoming mail in
the SMTP daemon.  It is a mature protocol and the implmentations
interoperate with no problems I've ever seen.

I support promoting 6376 to Internet Standard.

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 alh-ietf@tndh.net  Fri May  3 12:04:31 2013
Return-Path: <alh-ietf@tndh.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 A9FE221F8494 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:04:29 -0700 (PDT)
X-Quarantine-ID: <sIjUdWCKok+r>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -0.061
X-Spam-Level: 
X-Spam-Status: No, score=-0.061 tagged_above=-999 required=5 tests=[AWL=1.299,  BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIjUdWCKok+r for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:04:25 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 540A721F84A6 for <ietf@ietf.org>; Fri,  3 May 2013 12:04:04 -0700 (PDT)
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1UYLGM-0006a3-2B; Fri, 03 May 2013 12:03:28 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Pete Resnick'" <presnick@qti.qualcomm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<32577.1367426027@sandelman.ca>	<201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>	<5183BB59.7090206@cs.tcd.ie>	<201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>	<04a601ce4809$5679a000$036ce000$@olddog.co.uk>	<201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>	<5183D3CB.60702@qti.qualcomm.com> <00e001ce4825$6cad2740$460775c0$@tndh.net> <5183FC29.8040804@qti.qualcomm.com>
In-Reply-To: <5183FC29.8040804@qti.qualcomm.com>
Subject: RE: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 12:03:22 -0700
Message-ID: <00f901ce4830$e1b13440$a5139cc0$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKYyBhEoNBNJ3MPVKuNyDDagY8byQGPmImJAoVjNqoCWVDxGgGC+2YGApKHHrICSJvMmAHSSHO4AWmMVHQC453QmJbHZmDw
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false
Cc: 'Thomas Narten' <narten@us.ibm.com>, adrian@olddog.co.uk, '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: Fri, 03 May 2013 19:04:32 -0000

Pete Resnick wrote:
> Not disagreeing with your message, but a couple of clarifying points:
> 
> On 5/3/13 12:41 PM, Tony Hain wrote:
> 
> > I would agree with you that weighting longer term is the 'right
> > thing', but given that people wait for an RFC number to implement, and
> > then take the position that RFC (PS) == STD, you never get to the
> > longer term because the bar is set so high on the first hurdle that it
> > becomes impossible for people to justify the effort to go for the next
one.
> >
> 
> When Thomas said "longer-term", I took him to mean *all* of the things
that
> are longer time horizon, like management/mentoring of WGs and chairs,
> doing more early cross-area participation (including by ADs) in the design
of
> and work on protocols (not just review), etc. In particular, I didn't
understand
> him to mean longer-term as having anything to do with advancement on the
> standards track. I think the above longer-term goals are important. I
think
> movement along the standards track will be the outcome if we get to
> working well, but not a goal in-and-of itself.

I actually view all of the housekeeping activities as short term. Thomas
will have to state what he meant.

> 
> > In any case I don't see 60/40 as a tail-heavy process. If the WG time
> > were cut in half and the IESG/RFC-editor time stayed the same, maybe
> > it would be tail-heavy, but realistically more 'balanced'.
> >
> 
> I'll point you to Jari's excellent reminder that "time" is probably the
least of
> the heaviness on the tail end. What is tail heavy is the work
> investment: We do WG last call reviews, IETF-wide Last Call reviews,
> directorate reviews, IESG reviews, all at the end of the process. We spend
> scant little energy (of the wider IETF community and leadership) on early
> design reviews and protocol development early and in the middle of the
> document process. As Jari said, that model ends us up with late surprises,
> lack of transparency, etc., and probably uses much more energy overall
than
> if we invested it earlier in the process. Sure, this can translate to
delays, but
> that's only one (maybe minor) effect of being tail-heavy.

While I agree that it would appear to be a heavy workload, that is just
because it is concentrated enough to see. If you actually did all the work
across all the participants to review every document at every iteration,
nothing would get done. Even when the IETF was ~60 people creating a few
documents a year, reviews happened late, and changes were made. Yes earlier
comments from outside the WG will reduce overall surprise and workload, but
finding the right reviewers is tricky.

One could require that every BOF be presented to every Open Area meeting,
then required public comment from every other AD before being allowed to
form a WG. This would front load the review and raise general awareness
about what is being discussed. Unfortunately since that event and resulting
documents are half a decade apart, potential reviewers have long since
forgotten any concerns they might have had, and need to start fresh anyway.
For long standing WGs one could consider doing the same at every charter
change, but again, document movement within the WG needs to be faster for
any of that to matter. 

The only way I can see to reduce the time from BOF to RFC is to reduce the
public expectation on the quality of that initial document which will get
wide review and initial implementation.  We should be talking about ~ 3
years to get to STD, not the initial draft that gets review beyond the WG.
In practice what we have today is functionally STD at initial publication,
so there is a very concentrated effort at one point in time. If the process
to get from WG I-D to initial RFC was basically a sanity-check, the detailed
IESG and cross-area review could be spread out during implementation prior
to the update that removed the DRAFT: status. Realistically though, human
nature would take over and nothing would happen until the WG tried to take
that step and we would be having the same discussion about tail work load. 

Bottom line, we need a signal to other areas that a WG document is ready for
serious in depth review, and a document title change seems to be what people
are looking for. At the same time WGs need to do a better job of spreading
awareness earlier in the process to get comments from those that have
different perspectives, then actually listen to them during document
development. Surprise comes from being isolated, and/or shouting down voices
that later come back during review to highlight flaws. If the process to get
to DRAFT: status was less burdensome, documents would move more quickly and
less effort would have gone into the flawed document before it got seriously
reviewed. 

Tony




From doug.mtview@gmail.com  Fri May  3 12:05:05 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C2C21F96B4; Fri,  3 May 2013 12:05:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3MCrOj4ZGL7g; Fri,  3 May 2013 12:05:04 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE5E21F84A6; Fri,  3 May 2013 12:04:57 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id uo1so1043754pbc.34 for <multiple recipients>; Fri, 03 May 2013 12:04:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:date:message-id:cc:to :mime-version:x-mailer; bh=KDXmzyOdJ/a0Xghkhq7dxRaU+nn9HIrESFqLLKxxb+4=; b=aAsFEhtWcU9+Z6MQ7US16+Suw//fqZz2mP000HcyqXEOtuNDzIcMEWICVpw1MMhS0q Anp1a/sqh8agXFHAIjqz/hNUE4fOVO3KrDE850SSAyjZuXqLevd+w73ydPSO/ekgACUU Z6th/lq+FawNycgfTb+pwMu58z/N79KfpWW64DzBKjWtTaIx2ZE49ToJUfCKl991cjhy ltXgWR/ovMxAvXn4KZRsv3YP01Ka/+++IWJGwfbTVH9zXAXQXKzb6lAO9MFuQ7bqrO0M e4Cwf7ZIEwNjqun7HcCjX/DXcKjtgd5V0g0x4WHjGnrA03Bc1xVBNeT/JWFuPV3Cajek jw4Q==
X-Received: by 10.66.166.107 with SMTP id zf11mr16195044pab.166.1367607896894;  Fri, 03 May 2013 12:04:56 -0700 (PDT)
Received: from ?IPv6:2601:9:3180:3e:6977:cc82:b053:faf8? ([2601:9:3180:3e:6977:cc82:b053:faf8]) by mx.google.com with ESMTPSA id ih1sm12634971pbb.44.2013.05.03.12.04.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 12:04:55 -0700 (PDT)
From: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_438BAF92-9972-44B6-8856-17D48DA59C61"
Subject: Effects on DNS can be severe
Date: Fri, 3 May 2013 12:04:53 -0700
Message-Id: <363177C4-6D23-48C1-9609-226A9B55EAAD@gmail.com>
To: "<ietf@ietf.org> IETF" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Cc: "dnsext@ietf.org" <dnsext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 19:05:05 -0000

--Apple-Mail=_438BAF92-9972-44B6-8856-17D48DA59C61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear ietf and dnsext,

I apologies for posting this ahead of the wg last call.

Over many years at attempting to change the course of the SPF process, =
this effort appears to have been futile.
It seems many even feel the present spfbis document represents current =
practices.  It does not, from the perspective of macros.
I have written an I-D that I fully expect SPF proponents will denounce =
and so I have left that wg alone. =20

Here is a draft written in hopes of placing these concerns into a =
broader scope--
http://tools.ietf.org/html/draft-otis-ipv6-email-authent-00

Two references in this draft  did not carry over in the same manner as =
in the tcl script? =20
Until remedied, here are the links missing in this i-d:

[I-D.otis-spf-dos-exploit]
http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01

[v6-BGP-Rpts]
http://bgp.potaroo.net/v6/as6447/

SPF can pose serious threats, that when confronted, few solutions are =
available.  I have been able to convince some of the larger providers of =
this concern, who in returned offered assurances the macro extensions in =
their SPF libraries are removed and in doing so have not seen any =
problems.

This is a serious effort at addressing a security concern, please read =
this draft from that perspective.

Regards,
Douglas Otis


--Apple-Mail=_438BAF92-9972-44B6-8856-17D48DA59C61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear =
ietf and dnsext,<br><div><br></div><div>I apologies for posting this =
ahead of the wg last call.</div><div><br></div><div>Over many years at =
attempting to change the course of the SPF process, this effort appears =
to have been futile.</div><div>It seems many even feel the present =
spfbis document represents current practices. &nbsp;It does not, from =
the perspective of macros.</div><div>I have written an I-D that I fully =
expect SPF proponents will denounce and so I have left that wg alone. =
&nbsp;</div><div><br></div><div>Here is a draft written in hopes of =
placing these concerns into a broader scope--</div><div><a =
href=3D"http://tools.ietf.org/html/draft-otis-ipv6-email-authent-00">http:=
//tools.ietf.org/html/draft-otis-ipv6-email-authent-00</a></div><div><br><=
/div><div>Two references in this draft &nbsp;did not carry over in the =
same manner as in the tcl script? &nbsp;</div><div>Until remedied, here =
are the links missing in this i-d:</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01">[I-D.oti=
s-spf-dos-exploit]</a></div><div><a =
href=3D"http://tools.ietf.org/html/draft-otis-spf-dos-exploit-01">http://t=
ools.ietf.org/html/draft-otis-spf-dos-exploit-01</a></div><div><br></div><=
div><a =
href=3D"http://bgp.potaroo.net/v6/as6447/">[v6-BGP-Rpts]</a></div><div><a =
href=3D"http://bgp.potaroo.net/v6/as6447/">http://bgp.potaroo.net/v6/as644=
7/</a></div><div><br></div><div>SPF can pose serious threats, that when =
confronted, few solutions are available. &nbsp;I have been able to =
convince some of the larger providers of this concern, who in returned =
offered assurances the macro extensions in their SPF libraries are =
removed and in doing so have not seen any =
problems.</div><div><br></div><div>This is a serious effort at =
addressing a security concern, please read this draft from that =
perspective.</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div></body></html>=

--Apple-Mail=_438BAF92-9972-44B6-8856-17D48DA59C61--

From scott@kitterman.com  Fri May  3 12:21:53 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5F021F8B65 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MK-ZUaWT7LFA for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:21:48 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id BE53D21F8B49 for <ietf@ietf.org>; Fri,  3 May 2013 12:21:47 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 3D27F20E40FD; Fri,  3 May 2013 15:21:44 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367608904; bh=ajBhEbZGmJt8nMLCbSlE7BWP121mXaCVKYMaaPhQRtw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=g+48OXLEdohwve04To/wE7BC++HFppSy0BmzGZ89GiJmgb6KVN42CCBDlyDMUFqGW qG/11RICqiqPVSIINYQJt34NQqer3AnKTdYl8wSynrQ8jYJiSzBdADsKdi36FDtodP LrcgGyfRecZ99nvi1VCwbz5xdKeZzSebq5UmZM1A=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 223B020E4076;  Fri,  3 May 2013 15:21:43 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Effects on DNS can be severe
Date: Fri, 03 May 2013 15:21:41 -0400
Message-ID: <3298537.JHFMKpXVjX@scott-latitude-e6320>
User-Agent: KMail/4.10.2 (Linux/3.8.0-19-generic; KDE/4.10.2; i686; ; )
In-Reply-To: <363177C4-6D23-48C1-9609-226A9B55EAAD@gmail.com>
References: <363177C4-6D23-48C1-9609-226A9B55EAAD@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 19:21:53 -0000

On Friday, May 03, 2013 12:04:53 PM Douglas Otis wrote:
...
> Over many years at attempting to change the course of the SPF process, this
> effort appears to have been futile.
...

It does seem a bit odd for you to claim you're being ignored when the largest 
change in SPF processing limits contained in 4408bis was your suggestion.  An 
alternate interpretation to consider is that the working group fully 
considered your inputs and incorporated those that were appropriate 
technically and in scope for the charter.

Scott K

From narten@us.ibm.com  Fri May  3 12:40:54 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0D921F8FEB for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:40:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.68
X-Spam-Level: 
X-Spam-Status: No, score=-108.68 tagged_above=-999 required=5 tests=[AWL=0.679, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIjvX4sZ05un for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:40:48 -0700 (PDT)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 2354921F8FBE for <ietf@ietf.org>; Fri,  3 May 2013 12:40:48 -0700 (PDT)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 3 May 2013 13:40:47 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 3 May 2013 13:40:46 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id EF9023E40066 for <ietf@ietf.org>; Fri,  3 May 2013 13:40:11 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r43JeO2v111672 for <ietf@ietf.org>; Fri, 3 May 2013 13:40:24 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r43JhKKo004528 for <ietf@ietf.org>; Fri, 3 May 2013 13:43:20 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-49-147-40.mts.ibm.com [9.49.147.40]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r43JhI6w004376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 13:43:20 -0600
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r43JeKYV008499; Fri, 3 May 2013 15:40:20 -0400
Message-Id: <201305031940.r43JeKYV008499@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <5183D3CB.60702@qti.qualcomm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <5183D3CB.60702@qti.qualcomm.com>
Comments: In-reply-to Pete Resnick <presnick@qti.qualcomm.com> message dated "Fri, 03 May 2013 10:12:11 -0500."
Date: Fri, 03 May 2013 15:40:20 -0400
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13050319-2876-0000-0000-0000084287AA
Cc: adrian@olddog.co.uk, '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: Fri, 03 May 2013 19:40:55 -0000

Pete Resnick <presnick@qti.qualcomm.com> writes:

> On 5/3/13 7:59 AM, Thomas Narten wrote:

> > Like everyone, I wish things moved more quickly, but every attempt
> > I've ever seen that tries to speed things up ends up reducing the
> > quality or having some other undesirable side effect.
> >    

> Can you talk a bit more about this, including some examples?

Sorry, what I had in mind here was what I'll call process
tweaks. Attempts at changing the process to speed reviews, dispense
with reviews, overlap reviews, etc.

No, our processes aren't perfect. But we have bigger problems that are
not due to process that we'd do better to focus on rather than trying
to tweak the process in (IMO) minor ways. We should focussing more on
*root* *causes* and what concrete, pragmatic steps can be taken to
mitigate them.

> I'm trying to reconcile the concern that we "end up reducing the 
> quality"

Again, I was thinking of proposals for process (or operational)
changes that attempt to shorten things by overlapping or removing
reviews or steps, trying to get the IESG to do less review (e.g., "ADs
should only review looking at topics that are defined by their area")
and otherwise focus on the *process* as being the problem.

> and  that we "NOT neglect longer-term stuff that will have real 
> and significant, but not immediate benefits." ADs have finite resources 
> and can't accomplish both immediate and longer-term stuff maximally all 
> of the time. My inclination would be to say, "If they are in conflict, 
> weight the longer-term over the immediate, even if that might result in 
> some reducing of quality on any single document." Am I over-reading your 
> earlier message to say that you think the weighting should go toward the 
> immediate?

You have it right. And I meant "longer-term stuff" in a general
sense. There are many topics that are not immediate, but could be
important long term.

Spend enough time on long term so that it is not neglected. You have
to do both. But you must also MUST do long term stuff.

> I think we agree that doing the longer-term stuff will end up 
> with increased quality over the long term, but doing more of the 
> longer-term stuff is sure to reduce the amount of time spent on 
> immediate, which means document reviews and therefore some short term 
> lowering of quality. Is that OK, or is that an example of the kind of 
> thing we've attempted that ends up with bad results?

It's easy to fall back to the comfort zone, which is doing the
bi-weekly document reviews and such. I.e., the day-to-day operational
stuff.

What's more important to the IETF? Spending time on one questionable
(but quite possibly irrelevant) document to make it better before it gets
published? Or getting the IETF as a whole to work better and more
efficiently and produce better product?

Thomas


From doug.mtview@gmail.com  Fri May  3 12:46:56 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF03321F8518 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:46:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kRnUq9evEMqz for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 12:46:56 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 4E29121F8517 for <ietf@ietf.org>; Fri,  3 May 2013 12:46:56 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq8so1056489pbb.5 for <ietf@ietf.org>; Fri, 03 May 2013 12:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=mc5fSpOSh4gBoSDRiHUL8HW/+inkfm95UKl8sHKVu4g=; b=S+paFrZnjHzW8MBK2ko9lcP5STyKBAs117a4uJfXolpyC5CAX3dPhtHxHoDlhaOEzK bzFDjVb0E33kv1ROHMDw72bVZ+cJjtEL/pLF6KYQBxtCb7PCixoYsorNTZDErmjwNGnG 7+odayD4jTgsjAwYm1veOUuhHI7xWYlkXTJ5uzjEUwTe5nxWwRt0MkK0kFh8eL1FT0Kn BqGzHh51l8OuFGDNCUmLr6k+GclGVoTSuTQ1xe6CTN3mIE3S7GiNeEOTpTjI61c2hNIE JLCR8iIFnSdoKIvwl9Ow9ZWjQCPahr8LhIvpg31Rfy2h3XKMJ5tCp+LAtHTi/ROIhHh5 /Nuw==
X-Received: by 10.66.171.11 with SMTP id aq11mr16444664pac.24.1367610416077; Fri, 03 May 2013 12:46:56 -0700 (PDT)
Received: from [192.168.1.194] (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPSA id bs3sm12756093pbb.36.2013.05.03.12.46.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 12:46:55 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Effects on DNS can be severe
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <3298537.JHFMKpXVjX@scott-latitude-e6320>
Date: Fri, 3 May 2013 12:46:52 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E1F11CA7-AFEA-4A75-8E0D-89968CA9F37A@gmail.com>
References: <363177C4-6D23-48C1-9609-226A9B55EAAD@gmail.com> <3298537.JHFMKpXVjX@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1503)
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, 03 May 2013 19:46:56 -0000

On May 3, 2013, at 12:21 PM, Scott Kitterman <scott@kitterman.com> =
wrote:

> On Friday, May 03, 2013 12:04:53 PM Douglas Otis wrote:
> ...
>> Over many years at attempting to change the course of the SPF =
process, this
>> effort appears to have been futile.
> ...
>=20
> It does seem a bit odd for you to claim you're being ignored when the =
largest=20
> change in SPF processing limits contained in 4408bis was your =
suggestion.  An=20
> alternate interpretation to consider is that the working group fully=20=

> considered your inputs and incorporated those that were appropriate=20
> technically and in scope for the charter.

Dear Scott,


This was not directly part of the IETF process, as my input there was =
ignored.

As I recall, removal of unlimited recursion occurred after a =
presentation made in Boston to the Open Group.

As with unlimited recursion, the need for the macro functions are also =
negligible while posing real risks. This is a serious security concern =
still needing to be addressed.

Regards,
Douglas Otis

   =20=

From scott@kitterman.com  Fri May  3 13:00:29 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46FC221F8B18 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 13:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.855
X-Spam-Level: 
X-Spam-Status: No, score=-1.855 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N1CdlNZEyvzy for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 13:00:24 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id CAD3821F87CB for <ietf@ietf.org>; Fri,  3 May 2013 13:00:24 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 48DE020E40FD; Fri,  3 May 2013 16:00:24 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367611224; bh=EQ9HRC4/89o9WMzuCPbyip0S2lmLqp4kX1UsHfNVcCo=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jx5hbAlzo4/zZyKyVmdyLeXk6IjqYThOBidBAr+z0Oy8L9Jkh6lqRpkTqJUWwv9Rd VWHD9+xd6q/OKznRr1QfJuC/YMA6Vgsqlm5U7uybzISZXx3xu5Wxp+yoY/yUcUabzg Eff2rKsrqyhXhGU6YAOJEJyaLOTrqw2E/KTq2Cmc=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 3112D20E4076;  Fri,  3 May 2013 16:00:23 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Effects on DNS can be severe
Date: Fri, 03 May 2013 16:00:23 -0400
Message-ID: <1445721.H3Uv9hlO9Q@scott-latitude-e6320>
User-Agent: KMail/4.10.2 (Linux/3.8.0-19-generic; KDE/4.10.2; i686; ; )
In-Reply-To: <E1F11CA7-AFEA-4A75-8E0D-89968CA9F37A@gmail.com>
References: <363177C4-6D23-48C1-9609-226A9B55EAAD@gmail.com> <3298537.JHFMKpXVjX@scott-latitude-e6320> <E1F11CA7-AFEA-4A75-8E0D-89968CA9F37A@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 20:00:29 -0000

On Friday, May 03, 2013 12:46:52 PM Douglas Otis wrote:
> On May 3, 2013, at 12:21 PM, Scott Kitterman <scott@kitterman.com> wrote:
> > On Friday, May 03, 2013 12:04:53 PM Douglas Otis wrote:
> > ...
> > 
> >> Over many years at attempting to change the course of the SPF process,
> >> this
> >> effort appears to have been futile.
> > 
> > ...
> > 
> > It does seem a bit odd for you to claim you're being ignored when the
> > largest change in SPF processing limits contained in 4408bis was your
> > suggestion.  An alternate interpretation to consider is that the working
> > group fully considered your inputs and incorporated those that were
> > appropriate technically and in scope for the charter.
> 
> Dear Scott,
> 
> 
> This was not directly part of the IETF process, as my input there was
> ignored.
> 
> As I recall, removal of unlimited recursion occurred after a presentation
> made in Boston to the Open Group.

I assume you are referring to some of the pre-IETF activities for SPF.  
Recursion based processing limits don't appear in RFC 4408 (and also not in 
4408bis).

> As with unlimited recursion, the need for the macro functions are also
> negligible while posing real risks. This is a serious security concern
> still needing to be addressed.

This was discussed in the working group and tracked in the WG issue tracker:

http://trac.tools.ietf.org/wg/spfbis/trac/ticket/24

The change mentioned in the ticket is a direct result of your input to spfbis 
(referenced in the ticket).

As far as I can tell, this is just a case of "the working group came to a 
different conclusion, so I'll whine about it on the main list".

Scott K

From alh-ietf@tndh.net  Fri May  3 14:11:39 2013
Return-Path: <alh-ietf@tndh.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 6DEF621F85DB for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:11:39 -0700 (PDT)
X-Quarantine-ID: <hBX+TbiQADOv>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -1.33
X-Spam-Level: 
X-Spam-Status: No, score=-1.33 tagged_above=-999 required=5 tests=[AWL=1.270,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hBX+TbiQADOv for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:11:38 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 90B0A21F856D for <ietf@ietf.org>; Fri,  3 May 2013 14:11:38 -0700 (PDT)
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1UYNGK-0008Jq-8c; Fri, 03 May 2013 14:11:34 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Scott Kitterman'" <scott@kitterman.com>, <ietf@ietf.org>
Subject: RE: Effects on DNS can be severe &&& Re: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 14:11:28 -0700
Message-ID: <010601ce4842$c7041ce0$550c56a0$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5IQV5LDaX/jbpURJeCC5oPq5tdqg==
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 21:11:39 -0000

Scott, 

See the thread about Re: call for ideas: tail-heavy IETF process for
discussion about wider review at an earlier point in the process. Also, just
because there is a discussion on issue-tracker does not mean the document is
'high quality'. If there is an explicit trade-off being made, the main
document needs to address that directly so subsequent reviewers and
implementers know what and why.

I have not followed this discussion, but my cursory read of the tracker
ticket shows the WG blew off the issue by claiming that historical
unsophisticated attacks can be easily thwarted, while completely ignoring
the case where the target domains exist. Aborting an amplification attack on
failures does not do anything about the case where an attacker goes to the
trouble to make sure all the quires will return valid answers. Either the
issue-tracker discussion is inadequate, or this is exactly the kind of thing
that adds excess delay and workload to the IESG review process.

FWIW: id-otis-spf is an incoherent collection of issues. I can see why a WG
might have trouble parsing it, and come out with a different answer than
what was expected. That said, wider review requires a simpler problem
statement and understanding of what resources are being traded against
others, and for security issues in particular, a comprehensive set of attack
scenarios and mitigations. 

Tony


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Scott Kitterman
> Sent: Friday, May 03, 2013 1:00 PM
> To: ietf@ietf.org
> Subject: Re: Effects on DNS can be severe
> 
> On Friday, May 03, 2013 12:46:52 PM Douglas Otis wrote:
> > On May 3, 2013, at 12:21 PM, Scott Kitterman <scott@kitterman.com>
> wrote:
> > > On Friday, May 03, 2013 12:04:53 PM Douglas Otis wrote:
> > > ...
> > >
> > >> Over many years at attempting to change the course of the SPF
> > >> process, this effort appears to have been futile.
> > >
> > > ...
> > >
> > > It does seem a bit odd for you to claim you're being ignored when
> > > the largest change in SPF processing limits contained in 4408bis was
> > > your suggestion.  An alternate interpretation to consider is that
> > > the working group fully considered your inputs and incorporated
> > > those that were appropriate technically and in scope for the charter.
> >
> > Dear Scott,
> >
> >
> > This was not directly part of the IETF process, as my input there was
> > ignored.
> >
> > As I recall, removal of unlimited recursion occurred after a
> > presentation made in Boston to the Open Group.
> 
> I assume you are referring to some of the pre-IETF activities for SPF.
> Recursion based processing limits don't appear in RFC 4408 (and also not
in
> 4408bis).
> 
> > As with unlimited recursion, the need for the macro functions are also
> > negligible while posing real risks. This is a serious security concern
> > still needing to be addressed.
> 
> This was discussed in the working group and tracked in the WG issue
tracker:
> 
> http://trac.tools.ietf.org/wg/spfbis/trac/ticket/24
> 
> The change mentioned in the ticket is a direct result of your input to
spfbis
> (referenced in the ticket).
> 
> As far as I can tell, this is just a case of "the working group came to a
different
> conclusion, so I'll whine about it on the main list".
> 
> Scott K


From superuser@gmail.com  Fri May  3 14:15:45 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D06921F85EE for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MATLu86fGaiu for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:15:44 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id A42EA21F85DB for <ietf@ietf.org>; Fri,  3 May 2013 14:15:38 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id h11so1142045wiv.4 for <ietf@ietf.org>; Fri, 03 May 2013 14:15:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Hnhm+3BZsPLg/wDnJ3UehTXXWnc6OtqwiKrWHbDx8Fg=; b=Ia1sLWkM8GpKmq3g2+IStU1FLaxKVTvvh3SkW6FYgOCJZRSnIxeAXO/GQkni97n0sx 6gTy+2mp6I4jfN7CZJe7rISp0dxznjbN5tFu+CFLsTCtbA9f1XVfZg2uBLn9cI661/0T Y9rlAmR57dOX/YmghZnSv931wj13Ku+mh8Xk5kAZovnJaUNYaloaM6h6muDLZk9dORaK gEXZ3Xi08SuUGOanqc8hrQ3oFfSLvq/yXS1Zy+I6ZGpnjwXA6V6tGJNnGNQMissw14xj 0l/bnN15u/8yPP90jX0J0k9STpmPGJURO/0iVoOBbT4x4nAosszrH5v2HDFICOspejh3 eWRg==
MIME-Version: 1.0
X-Received: by 10.194.93.68 with SMTP id cs4mr16211097wjb.17.1367615736879; Fri, 03 May 2013 14:15:36 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Fri, 3 May 2013 14:15:36 -0700 (PDT)
In-Reply-To: <20130503185255.41269.qmail@joyce.lan>
References: <20130503162119.31310.96671.idtracker@ietfa.amsl.com> <20130503185255.41269.qmail@joyce.lan>
Date: Fri, 3 May 2013 14:15:36 -0700
Message-ID: <CAL0qLwb15qTP8UNM0+DzD_GS4=ZDU8XdjR0KO+Z_H-MBmepXgA@mail.gmail.com>
Subject: Re: Last Call: Change the status of DKIM (RFC 6376) to Internet Standard
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=047d7b5d8cff2fa3ba04dbd6da66
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 21:15:45 -0000

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

What he said, except that I don't run the perl thing.  :-)

+1.


On Fri, May 3, 2013 at 11:52 AM, John Levine <johnl@taugh.com> wrote:

> I use DKIM via two independent implementations, perl Mail::DKIM to
> sign outgoing mail, and C language opendkim to check incoming mail in
> the SMTP daemon.  It is a mature protocol and the implmentations
> interoperate with no problems I've ever seen.
>
> I support promoting 6376 to Internet Standard.
>
> 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
>
>

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

<div dir=3D"ltr">What he said, except that I don&#39;t run the perl thing.=
=A0 :-)<br><br>+1.<br></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Fri, May 3, 2013 at 11:52 AM, John Levine <span dir=3D"=
ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@taugh.c=
om</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I use DKIM via two independent implementatio=
ns, perl Mail::DKIM to<br>
sign outgoing mail, and C language opendkim to check incoming mail in<br>
the SMTP daemon. =A0It is a mature protocol and the implmentations<br>
interoperate with no problems I&#39;ve ever seen.<br>
<br>
I support promoting 6376 to Internet Standard.<br>
<br>
Regards,<br>
John Levine, <a href=3D"mailto:johnl@iecc.com">johnl@iecc.com</a>, Primary =
Perpetrator of &quot;The Internet for Dummies&quot;,<br>
Please consider the environment before reading this e-mail. <a href=3D"http=
://jl.ly" target=3D"_blank">http://jl.ly</a><br>
<br>
</blockquote></div><br></div>

--047d7b5d8cff2fa3ba04dbd6da66--

From yaronf.ietf@gmail.com  Fri May  3 14:22:37 2013
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 E45E121F8763 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMZu2maUsVw2 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:22:36 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id BBBF821F8619 for <ietf@ietf.org>; Fri,  3 May 2013 14:22:34 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id t9so1658792wey.24 for <ietf@ietf.org>; Fri, 03 May 2013 14:22:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9HNM1N+pLU8kgnGUVEQ0HklFSu/0HmahkC+mbA0+U3U=; b=0D/Ts9ixmhNjUmnCg9hvUujsz7Q+4mVzEzkfgud8DO2qStfWPvLSBq5mM/RP1oaco4 YWwZT1fMTSOdRRHfUmGe2jzTHzOc8Xv7t7lDJwRgYJpHlEYs5ZdbrwqgYrEmY8jHyR8C 7xojROThHYqiy1ivIaMN9zOHzN+KVl3xY/8jTR2laGb/gdyLv5U9FP8HnZ+lMa2cKfCd VAb3O34zKUbHo2v7XwU0tL+gWTWloUYK1cEGlLbJ0Gi/HBR7gAJyd6ropT1LA4cakow0 p+aZiE+bv1eNin9c8ZBFMeB+4h5/uqIhfgcrNx8o7gVnOtU8O4EkZVqjlW0N1q/uAQhl PcKw==
X-Received: by 10.180.212.46 with SMTP id nh14mr31895727wic.26.1367616153892;  Fri, 03 May 2013 14:22:33 -0700 (PDT)
Received: from [10.0.0.3] (bzq-79-177-103-167.red.bezeqint.net. [79.177.103.167]) by mx.google.com with ESMTPSA id ge7sm46677051wic.0.2013.05.03.14.22.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 14:22:33 -0700 (PDT)
Message-ID: <51842A94.6060505@gmail.com>
Date: Sat, 04 May 2013 00:22:28 +0300
From: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Scott Brim <swb@internet2.edu>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu>
In-Reply-To: <51839ABA.4010406@internet2.edu>
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: Fri, 03 May 2013 21:22:37 -0000

GEN-ART is a good example, but actual document editing is much more work 
and arguably, less rewarding than a review. So I think this can only 
succeed with professional (=paid) editors.

Thanks,
	Yaron

>
> On 05/02/2013 02:40 PM, Yaron Sheffer wrote:
>> I suggest that we budget for a number of WG drafts per year (say,
>> 20 IETF-wide) to go through professional, paid-for heavy-duty
>> editing
>
> My experience is that unless the editors have some background in
> protocols, this takes a surprising amount of effort, explaining it to
> them and catching _their_ mistaken assumptions (which can be subtle).
>   However,
>
> On 05/02/13 19:13, Peter Saint-Andre allegedly wrote:
>> Instead of imposing even more work on the RFC Editor team, I
>> suggest that you find someone in the WG, in your company, in the
>> IETF community (etc.) to help with the language issues.
>
> ... then you have quality control issues, uncertainty who to turn to,
> finding someone who not only appears to be good but actually is, etc.
>
> So how about a pool of volunteer editors, aka GEN-AET, with developed
> reputations?

From barryleiba.mailing.lists@gmail.com  Fri May  3 14:39:38 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B355421F8DCF for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zMFSzNKX3-k6 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:39:38 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3FC21F8BDE for <ietf@ietf.org>; Fri,  3 May 2013 14:39:37 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id ox1so1951367veb.32 for <ietf@ietf.org>; Fri, 03 May 2013 14:39:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HrP22ktUn3mW8eYb37O8cIYaNlsV3P+OsDmj2owW9dI=; b=DFCdDZOrlW+HUtfJ7n3BeaLP9t9j15TZRa/JAZ6jwsKYyLLK+aUDQbMzxaAluaXYoN 9xtTAQKjV1zXn+tnwbumvsCXi8XpJeJCDLhI0Qs4NAEjzSScMbeI1T+jYqAy/TguMajW PfbUp0JYqU0eoOWNaK0tJDlUsBzL7Nv+MiUiSho2/+aGuc47ijcIBsjP7kvCXjqIrQre L/E6gdE8g+NrUoATcvnE3rlwjAazN/RAjsNmakHzsxK13ekvr67/Mp7IMFazuSyn511X YWfN5ni25fkOYTIE4CV3JgautIP+HfRwdtjZUH8KJUPzoQFKC0yhwQIJPX1YmKLoLEkH VrVg==
MIME-Version: 1.0
X-Received: by 10.52.93.179 with SMTP id cv19mr3678031vdb.20.1367617177507; Fri, 03 May 2013 14:39:37 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Fri, 3 May 2013 14:39:37 -0700 (PDT)
In-Reply-To: <30759.1367602280@sandelman.ca>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <30759.1367602280@sandelman.ca>
Date: Fri, 3 May 2013 17:39:37 -0400
X-Google-Sender-Auth: N6Dt-CnBcsk--xRd6ODL0SBC4q4
Message-ID: <CAC4RtVCtULhM3FqNsY4rGPdoed4iSCnJVUgCODczFr_jZgr9Gw@mail.gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
From: Barry Leiba <barryleiba@computer.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Thomas Narten <narten@us.ibm.com>, 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: Fri, 03 May 2013 21:39:38 -0000

> I would like to suggest that the IESG Review be done in public on the WG
> mailing list.    I've been a WG co-chair for just over a year now, and
> I'm truly astounded by what happens behind the scenes.
>
> It's not the substance, it's the quantity, and the lack of WG view of
> it.   I think that this substantially and quite negatively contributes
> to the "fix it during IESG review", and therefore to the IESG workload.

Pete and I suggested this to the App chairs in Orlando (see here:
http://www.ietf.org/proceedings/86/slides/slides-86-appsawg-4.pdf ),
and we are currently trying it out with draft-ietf-core-coap, which is
scheduled for the 16 May IESG telechat (see
http://datatracker.ietf.org/doc/draft-ietf-core-coap/ and note that
I've set the "Send notices to" field to include the working group
mailing list).

It appears to be working very well, and I'd like to try it on more
documents in more working groups.  Perhaps some day it will be the
normal way to operate; we'll have to see.

Barry, Applications AD

From dougb@dougbarton.us  Fri May  3 14:55:36 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 988A121F9113 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IXMecFpr0U9I for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 14:55:33 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 976BB21F925A for <ietf@ietf.org>; Fri,  3 May 2013 14:55:30 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id ECFFD22B62 for <ietf@ietf.org>; Fri,  3 May 2013 21:55:29 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1367618130; bh=NpEkFm9lw7fTFj5Nr4EHsdDXHWBMJTIF4rMSr1vZZWM=; h=Date:From:To:Subject:References:In-Reply-To; b=oyiufGQ9W+zZgL3GmQC9hvylq+tO3reyn0BkVt63lR9fQCJQp5ZNC8opQsBvpBVTZ myWxg4NQTrjguoJ2+G6gNDFsg4pNLobwVp3m26BjW3QVpUjoX8tbiuHNGC0Xy5h9NZ O02HqBNNlGPU8dUFJMqWehorpNtehHtwQ4C8Z4AE=
Message-ID: <51843251.3070906@dougbarton.us>
Date: Fri, 03 May 2013 14:55:29 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com>
In-Reply-To: <51842A94.6060505@gmail.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 21:55:36 -0000

On 05/03/2013 02:22 PM, Yaron Sheffer wrote:
> GEN-ART is a good example, but actual document editing is much more work
> and arguably, less rewarding than a review. So I think this can only
> succeed with professional (=paid) editors.

I'm not sure that's the right conclusion to draw.

In the past I have done extremely detailed copy editing for drafts that 
I was particularly excited about, and wanted to help become RFCs. In 
exactly 1 case that work was warmly received by the author. In all the 
other cases I was met with reactions anywhere from mild disinterest to 
open hostility. In the most extreme example I was told on the list that 
my efforts were not welcome, would not be incorporated into any future 
drafts, and that I should not be trying to do the RFC Editor's job for 
them. I was also accused in private of trying to make the author look 
stupid. As a result of the at best generally apathetic reaction I no 
longer bother doing that kind of detailed copy editing when I review 
drafts.

The conclusion I have drawn (based in part on my own limited experience, 
and in part in seeing the same thing played out in IETF LC) is that as a 
community we do not place sufficient value on high quality work at late 
stages in the process. This is unfortunate on several levels. First, 
while I have the highest respect for the quality of work that the RFC 
Editor does it's not realistic to expect them to catch everything. And 
even if we were willing to fund the next-highest level of 
review/editing, in the best case scenario that kind of work usually 
incurs additional delays due to having to go back and forth with the 
authors, WG, etc. But I think more importantly, by not engaging in a 
better class of refinement at the WG level we miss the opportunity to 
help bring everyone's skill set up to a higher level.

There is a serious caveat to this though, we do not want to generate a 
perception that "only perfect English text need apply." We should make 
clear that _initial_ versions of drafts can and should be submitted even 
if the prose isn't yet publishable. But we should also make clear that 
help will be provided to _get_ the text up to snuff, and we should value 
that goal as an institution.

Doug


From brian.e.carpenter@gmail.com  Fri May  3 15:04:52 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8091721F9301 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:04:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.149
X-Spam-Level: 
X-Spam-Status: No, score=-103.149 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zcDuYBUp7PAz for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:04:46 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id B085521F9164 for <ietf@ietf.org>; Fri,  3 May 2013 15:04:46 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa10so1129844pad.33 for <ietf@ietf.org>; Fri, 03 May 2013 15:04:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OV039MnE3z62Fy77Lcx/YgZdN8F2rixsmkrcGTKWYm8=; b=AqTujZVfJlqQNHcCUCzgucuvmg7n1fqzm/Monw20y4oJpIpEqfYYp6h8sjzDTdk3d5 gn5v1k76pce7GIpNBBiWdzH57ElfSyzfnixrOUi3wbBtlK0AjJWZvsT8IbsanafU3WKZ Txi2S6fw5+Qp8/kGU2nJ6geIb48a8Bp8ARIZQtzPTfmtDou4pbxxb8OweOa1w6dWb/4F p6vCZAgR8P/aTgzrQd1VKR1VhWT/FYGL0RbjhMz+BxNAYjEEQIxdGjHdXHyvlWoaNf6Z JekeYdrVF2c06I83qEUGD0AmxlNIri7UiCo8v+QRoaZA0+s366olxGB20q2Izg8bemlh Ib2A==
X-Received: by 10.66.161.69 with SMTP id xq5mr16890016pab.136.1367618685949; Fri, 03 May 2013 15:04:45 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id cp1sm13091146pbc.42.2013.05.03.15.04.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 15:04:44 -0700 (PDT)
Message-ID: <51843485.90802@gmail.com>
Date: Sat, 04 May 2013 10:04:53 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org>	<5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org>	<51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com>
In-Reply-To: <51842A94.6060505@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 22:04:52 -0000

On 04/05/2013 09:22, Yaron Sheffer wrote:
> GEN-ART is a good example, but actual document editing is much more work
> and arguably, less rewarding than a review. So I think this can only
> succeed with professional (=paid) editors.

I think I disagree, if we can find the knack of effective crowd-sourcing.
We do after all have several hundred native English speakers active
in the IETF, which would mean each one would have to volunteer for
less than one draft per year and we'd be done.

I don't know how much experience you have with professional editors.
Apart from the RFC Editor crew, my experience has been "mixed". Somebody
a year or three ago (the last time we had this exact same discussion)
pointed out the differences between copy-editors and technical editors.
One difference is that the latter are much more expensive. Copy-editors
tend to be rule-driven; technical editors are supposed to understand
the material.

    Brian

From scott@kitterman.com  Fri May  3 15:07:01 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BD2721F8519 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level: 
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OO-gQhWc1N5t for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:06:57 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 320D921F8525 for <ietf@ietf.org>; Fri,  3 May 2013 15:06:55 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 98F5920E40FD; Fri,  3 May 2013 18:06:54 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367618814; bh=QUho3EgyFgDwO3OHoi70V3ARzpOhH1/c8LshreAfoQQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j4yFiWwbccS4sMnkpwhOA9CPhVNw9cLeFV3iS8kQyZ1ONa4I4OBRqim2R4H+g8nKb WuRVA8QTWmjW+t5XLhp/x5wspin5OfbWNtZQpol6+RpxRnv32/oJsYSIl6aGFB/OTe 7mukb2xIYxhiO/VdMfLLZIlMjBeRvTA8Wm+Kz6/c=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 8144020E4076;  Fri,  3 May 2013 18:06:54 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Effects on DNS can be severe &&& Re: call for ideas: tail-heavy IETF process
Date: Fri, 03 May 2013 18:06:53 -0400
Message-ID: <1929317.DYanfU0SHh@scott-latitude-e6320>
User-Agent: KMail/4.10.2 (Linux/3.8.0-19-generic; KDE/4.10.2; i686; ; )
In-Reply-To: <010601ce4842$c7041ce0$550c56a0$@tndh.net>
References: <010601ce4842$c7041ce0$550c56a0$@tndh.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 22:07:01 -0000

There's been a details review of his draft done when it was published, if you 
want something more coherent to read:

http://www.openspf.org/draft-otis-spf-dos-exploit_Analysis

In the more than half decade since, the issue has been discussed and reviewed 
many times.  In the pre-IETF phase of SPF development the processing limits 
were very different and, in my opinion, inherently risky.  The changed 
processing limits is probably the most important technical difference between 
RFC 4408 and the pre-IETF drafts.  To the extent there is a significant 
problem, I think the changes in RFC 4408 substantially mitigated it and the 
4408bis draft goes a bit further.

We did have an extensive discussion about SPF macros and if they should be 
removed.  The conclusion of the working group was that given our charter and 
the facts available, they should not.  

Doug's claim not to have participated is not correct.  All you have to do is 
look at the mailing list archive.  It's true that he seems to have stopped at 
some point, but having submitted issues to a WG that were reviewed and that 
ultimately impacted the text in the draft is not at all not participating.

Finally, I don't think it's reasonable for a draft to document internally why 
various decisions were made.  It needs to document the results of the WG 
efforts.  4408bis is long enough already and all the working group discussions 
are documented for people who are interested.

Scott K

On Friday, May 03, 2013 02:11:28 PM Tony Hain wrote:
> Scott,
> 
> See the thread about Re: call for ideas: tail-heavy IETF process for
> discussion about wider review at an earlier point in the process. Also, just
> because there is a discussion on issue-tracker does not mean the document
> is 'high quality'. If there is an explicit trade-off being made, the main
> document needs to address that directly so subsequent reviewers and
> implementers know what and why.
> 
> I have not followed this discussion, but my cursory read of the tracker
> ticket shows the WG blew off the issue by claiming that historical
> unsophisticated attacks can be easily thwarted, while completely ignoring
> the case where the target domains exist. Aborting an amplification attack on
> failures does not do anything about the case where an attacker goes to the
> trouble to make sure all the quires will return valid answers. Either the
> issue-tracker discussion is inadequate, or this is exactly the kind of
> thing that adds excess delay and workload to the IESG review process.
> 
> FWIW: id-otis-spf is an incoherent collection of issues. I can see why a WG
> might have trouble parsing it, and come out with a different answer than
> what was expected. That said, wider review requires a simpler problem
> statement and understanding of what resources are being traded against
> others, and for security issues in particular, a comprehensive set of attack
> scenarios and mitigations.
> 
> Tony
> 
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Scott Kitterman
> > Sent: Friday, May 03, 2013 1:00 PM
> > To: ietf@ietf.org
> > Subject: Re: Effects on DNS can be severe
> > 
> > On Friday, May 03, 2013 12:46:52 PM Douglas Otis wrote:
> > > On May 3, 2013, at 12:21 PM, Scott Kitterman <scott@kitterman.com>
> > 
> > wrote:
> > > > On Friday, May 03, 2013 12:04:53 PM Douglas Otis wrote:
> > > > ...
> > > > 
> > > >> Over many years at attempting to change the course of the SPF
> > > >> process, this effort appears to have been futile.
> > > > 
> > > > ...
> > > > 
> > > > It does seem a bit odd for you to claim you're being ignored when
> > > > the largest change in SPF processing limits contained in 4408bis was
> > > > your suggestion.  An alternate interpretation to consider is that
> > > > the working group fully considered your inputs and incorporated
> > > > those that were appropriate technically and in scope for the charter.
> > > 
> > > Dear Scott,
> > > 
> > > 
> > > This was not directly part of the IETF process, as my input there was
> > > ignored.
> > > 
> > > As I recall, removal of unlimited recursion occurred after a
> > > presentation made in Boston to the Open Group.
> > 
> > I assume you are referring to some of the pre-IETF activities for SPF.
> > Recursion based processing limits don't appear in RFC 4408 (and also not
> 
> in
> 
> > 4408bis).
> > 
> > > As with unlimited recursion, the need for the macro functions are also
> > > negligible while posing real risks. This is a serious security concern
> > > still needing to be addressed.
> > 
> > This was discussed in the working group and tracked in the WG issue
> 
> tracker:
> > http://trac.tools.ietf.org/wg/spfbis/trac/ticket/24
> > 
> > The change mentioned in the ticket is a direct result of your input to
> 
> spfbis
> 
> > (referenced in the ticket).
> > 
> > As far as I can tell, this is just a case of "the working group came to a
> 
> different
> 
> > conclusion, so I'll whine about it on the main list".
> > 
> > Scott K

From hsantos@isdg.net  Fri May  3 15:12:10 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4B821F8BE9 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMC3vtyhMQGg for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:12:05 -0700 (PDT)
Received: from mail.catinthebox.net (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCBB21F8E51 for <ietf@ietf.org>; Fri,  3 May 2013 15:12:05 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2326; t=1367619120; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=3NRhRmc lxxBtpYDlH13AmoliP7c=; b=I8O8LNWK75nrMEXn9C1YJHFAl7aXZ9XP6o04nl8 rqktSxMzcVJE4++j79kqDYsf2IhhtTOpEw62j/PBaiTy9tLS97fKS3v0LXUmJ+/K nGUrNx4/2IWFtygNHlcJJExk6Jen04VH5nDJQkr9bnbC7UNbwPvycuKmKaJqhMSS owA0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 03 May 2013 18:12:00 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2117834006.9851.5212; Fri, 03 May 2013 18:11:59 -0400
Message-ID: <518435D5.5040601@isdg.net>
Date: Fri, 03 May 2013 18:10:29 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 22:12:10 -0000

May I suggest that the IETF produce a web site for gathering IETF 
participants profiles and even resumes.  It can have a questionnaire to 
extract the valuable information that will help maximize the IETF/IESG 
efforts.  The "Business Information" (BI) can then be leveraged by ADs, 
WGs (and other IETF/IESG leaders) to recruits/invite participants for 
various projects, reviews, etc.  It will have many win-wins for all.  We 
should consider there are as much, and perhaps even more IETF man-years 
in people that never attended meetings but were active for many years, 
nonetheless, in their various IETF protocol interest areas.

The structure of this questionnaire will be important to be successful 
and beneficial.

Sincerely,

Hector Santos


On 5/3/2013 10:32 AM, Thomas Narten wrote:
> "Adrian Farrel" <adrian@olddog.co.uk> writes:
>
>> Well said, Thomas.
>
>>> Two concrete suggestions:
>>>
>>> 1) have WGs do the managing role more proactively
>>> 2) mentor authors and others a bit more to encourage them how best to
>>> operate
>
>> Which I suspect means...
>
>> 0) have ADs manage/mentor the WG chairs more proactively.
>
> Absolutely. But that is why the nomcom is supposed to select ADs that
> have *management* capabilities as well as technical skills.
>
>> Almost certainly a case of "if I had less work to do I would have
>> more time to do the things that would reduce my workload."  :-)
>
> Well, this is why you get paid the big bucks.
>
> Not to put too fine a point on in, but ADs need to manage their time,
> and they need to balance between the immediate and the long term. They
> have to do *both*, and especially NOT neglect longer-term stuff that
> will have real and signficant, but not immediate benefits.
>
>> WG chairs might like to comment, but I suspect that one lunchtime training
>> session every four months does not constitute proactive management.
>
> This would help and could be part of a comprehensive approach. But ADs
> also need to lay down expectations on WG chairs, and *grade* and
> *evaluate* WG Chair performance. WG chairs also don't have
> cycles... And ADs seem reluctant to step in and make management
> changes that really often are needed to change the dynamices within
> WGs that are not delivering...
>
> Thomas
>
>
>


From doug.mtview@gmail.com  Fri May  3 15:40:06 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB02521F8D6A for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rddvVS1LRyTV for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:40:02 -0700 (PDT)
Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by ietfa.amsl.com (Postfix) with ESMTP id E39AA21F84F2 for <ietf@ietf.org>; Fri,  3 May 2013 15:40:01 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id t10so1137215pdi.39 for <ietf@ietf.org>; Fri, 03 May 2013 15:40:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=c2gVvGrcm9s4caJ6WahN2ygcVKnCnRFiLux2y6hW91U=; b=um2/Wr1yOjTLGL3JzdFghPCu2cdL7EdYyESRok2XdmibvOhUoNuQ/03rLuO5pqhk9Z TsP0PXOv+/zn+0T6wO3eaCMO4YrVyIEA88KY9hbHScurK0fUUSxu/LI+nSy8pLy7wpp/ eUJenGQ3JHk1tpjh+oxPEI1+3SQpy4sZsg7Y2LCai7wx/facxnPJxnTnDtG1mlg8JKCJ CiuPs1aCzTyvlJKwVj8a17or56lvEJk1rb8DU33YBKugZzE5iD8mXLu0yTtcO+T8akXo YwXVlcU5YY1gAoNitlyXbRgBTBIr/3kjlzwg150XTG1nxctKfnSnutyQIFXe8kS3/P6F gccg==
X-Received: by 10.66.7.202 with SMTP id l10mr16590517paa.176.1367620801653; Fri, 03 May 2013 15:40:01 -0700 (PDT)
Received: from [192.168.1.194] (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPSA id ea15sm14448170pad.16.2013.05.03.15.39.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 May 2013 15:40:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Effects on DNS can be severe
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <1445721.H3Uv9hlO9Q@scott-latitude-e6320>
Date: Fri, 3 May 2013 15:39:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <64F803DB-06EB-415B-8C89-924AFD50C065@gmail.com>
References: <363177C4-6D23-48C1-9609-226A9B55EAAD@gmail.com> <3298537.JHFMKpXVjX@scott-latitude-e6320> <E1F11CA7-AFEA-4A75-8E0D-89968CA9F37A@gmail.com> <1445721.H3Uv9hlO9Q@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1503)
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, 03 May 2013 22:40:07 -0000

On May 3, 2013, at 1:00 PM, Scott Kitterman <scott@kitterman.com> wrote:

> On Friday, May 03, 2013 12:46:52 PM Douglas Otis wrote:
>> On May 3, 2013, at 12:21 PM, Scott Kitterman <scott@kitterman.com> =
wrote:
>>> On Friday, May 03, 2013 12:04:53 PM Douglas Otis wrote:
>>> ...
>>>=20
>>>> Over many years at attempting to change the course of the SPF =
process,
>>>> this
>>>> effort appears to have been futile.
>>>=20
>>> ...
>>>=20
>>> It does seem a bit odd for you to claim you're being ignored when =
the
>>> largest change in SPF processing limits contained in 4408bis was =
your
>>> suggestion.  An alternate interpretation to consider is that the =
working
>>> group fully considered your inputs and incorporated those that were
>>> appropriate technically and in scope for the charter.
>>=20
>> Dear Scott,
>>=20
>>=20
>> This was not directly part of the IETF process, as my input there was
>> ignored.
>>=20
>> As I recall, removal of unlimited recursion occurred after a =
presentation
>> made in Boston to the Open Group.
>=20
> I assume you are referring to some of the pre-IETF activities for SPF. =
=20
> Recursion based processing limits don't appear in RFC 4408 (and also =
not in=20
> 4408bis).
>=20
>> As with unlimited recursion, the need for the macro functions are =
also
>> negligible while posing real risks. This is a serious security =
concern
>> still needing to be addressed.
>=20
> This was discussed in the working group and tracked in the WG issue =
tracker:
>=20
> http://trac.tools.ietf.org/wg/spfbis/trac/ticket/24
>=20
> The change mentioned in the ticket is a direct result of your input to =
spfbis=20
> (referenced in the ticket).
>=20
> As far as I can tell, this is just a case of "the working group came =
to a=20
> different conclusion, so I'll whine about it on the main list".

Dear Scott,

While the recommendation may have helped, there is a trend of large =
websites publishing synthetic domains as an alternative to web cookies. =
This overcomes the suggested fix. A similar issue applies to SPF reverse =
namespace macro expansion consuming connection resources, especially in =
regard to IPv6.  In the end, the domain is still not authenticated, the =
number of transactions remain excessive and inhibit meaningful =
mitigation. Nothing justifies active content in DNS resource records =
distributed with email.  Macros are not needed and seldom if ever are =
used in this regard.  Simply put, SPF macros are not safe.  DKIM as =
specified is not safe. Open IPv6 email can not be defended.  The IETF =
needs to seek better and fairer remedies.

Regards,
Douglas Otis






From derhoermi@gmx.net  Fri May  3 15:49:26 2013
Return-Path: <derhoermi@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 F34E921F8EEC for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+BSZ5aG-hIe for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 15:49:21 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 45ED421F8696 for <ietf@ietf.org>; Fri,  3 May 2013 15:49:21 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.16]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0McCWP-1Upmml1fqJ-00JbtU for <ietf@ietf.org>; Sat, 04 May 2013 00:49:20 +0200
Received: (qmail invoked by alias); 03 May 2013 22:49:20 -0000
Received: from p5B231932.dip0.t-ipconnect.de (EHLO netb.Speedport_W_700V) [91.35.25.50] by mail.gmx.net (mp016) with SMTP; 04 May 2013 00:49:20 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1/sWsNhj+fsIjX/70mHCmfkiVBWRJpGAYSsSVBZOS /KhT7ULjhNWTMi
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
Date: Sat, 04 May 2013 00:49:23 +0200
Message-ID: <1nf8o8hec4qrgb0a041mgql1js0ng33b7r@hive.bjoern.hoehrmann.de>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net>
In-Reply-To: <518435D5.5040601@isdg.net>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-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: Fri, 03 May 2013 22:49:26 -0000

* Hector Santos wrote:
>May I suggest that the IETF produce a web site for gathering IETF 
>participants profiles and even resumes.  It can have a questionnaire to 
>extract the valuable information that will help maximize the IETF/IESG 
>efforts.  The "Business Information" (BI) can then be leveraged by ADs, 
>WGs (and other IETF/IESG leaders) to recruits/invite participants for 
>various projects, reviews, etc.  It will have many win-wins for all.  We 
>should consider there are as much, and perhaps even more IETF man-years 
>in people that never attended meetings but were active for many years, 
>nonetheless, in their various IETF protocol interest areas.
>
>The structure of this questionnaire will be important to be successful 
>and beneficial.

+1
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From dougb@dougbarton.us  Fri May  3 16:19:44 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A7D21F8F7B for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 16:19:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6z8yJWDLmr03 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 16:19:39 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id D6A1621F8EB1 for <ietf@ietf.org>; Fri,  3 May 2013 16:19:39 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id 6F45C22B62 for <ietf@ietf.org>; Fri,  3 May 2013 23:19:39 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1367623179; bh=a1D4jGd0HXWWlPoQtWvjAjvMW5tgSVRJOMXTsH41mYE=; h=Date:From:To:Subject:References:In-Reply-To; b=OfiaU65jnuMH/GEh5kwNxx7eFQ0DmQiBAZrIQRk35SdX1MhvA6wKd0zxZxTX56otM rBFi22fk14E6fl//qK2scDpSKE6nS14213zPD1bbFk66sYusicyzNR13e1wFVEk3Fp O4s6iLEecAroMwCmgRI2fJvj8vWeidgJ++Acsivo=
Message-ID: <5184460B.2050907@dougbarton.us>
Date: Fri, 03 May 2013 16:19:39 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A note about draft-ietf-spfbis-4408bis
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca>
In-Reply-To: <20130502195015.GA323@crankycanuck.ca>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2013 23:19:44 -0000

Andrew (and Pete, since he raised a similar issue),

On 05/02/2013 12:50 PM, Andrew Sullivan wrote:
> Doug,
>
> No hat.
>
> On Thu, May 02, 2013 at 12:22:03PM -0700, Doug Barton wrote:
>> Given that you can be 100% confident that the issue will be raised
>> during IETF LC, wouldn't it be better to hash it out in the WG (as
>> we have attempted to do)? Or is the WG's position, "we have no
>> intention of dealing with this unless we're forced to?"
>
> We _have_ hashed this out in the WG.  As I have noted to you -- now on
> three separate lists -- the problem is that we have an actual
> interoperability bug in RFC 4408, and we need to fix it.  The WG
> evaluated the various alternatives for how to solve that, and having
> performed the evaluation the group came to the conclusion that, _in
> this specific case_, deprecating RRTYPE 99 is the most reasonable
> course of action.

I understand the conclusion the WG has come to, and I have a pretty good 
understanding as to why. At Pete's request I reviewed the threads 
related to this issue in the spfbis archive. I also understand that the 
WG (which you co-chaired, although I will accept your "no hat" statement 
above at face value) desperately wants this issue to go away.

The problem is that the WG came to a very bad conclusion. A conclusion 
that is not only bad for SPF, it's bad for the future of innovation in 
the DNS, contrary to 5507, and arguably contrary to the group's own 
charter.

I am not saying that the WG members (or chairs) should be given the 
wet-noodle treatment over having reached a bad decision, but what is 
cross-area review for if not to catch cases where the WG echo 
chamber/tunnel vision/what have you -- resulted in a bad outcome?

It would be different if the right solution were hard, or if I were the 
only one objecting. But neither is true.

> I am not happy about this, but other analyses do not seem to be
> supported by any facts,

I'm not sure what facts you're looking for beyond what I've already 
provided. But in no particular order:

1. "Deprecate SPF/99" is in violation of 5507
2. Numerous people smarter than I have pointed out detailed technical 
reasons why overloading TXT generally, and particularly at the zone 
apex, is a horrible idea.

Furthermore, 2 of us presented detailed analyses of the arguments raised 
in spfbis, and found them severely lacking. In summary, "We tried doing 
SPF/99 10 years ago and it didn't work, so we stopped." I (and others) 
have several times now offered detailed responses explaining that in a 
post-3597 world that shouldn't be an issue anymore. "There are still 
some firewalls or other middleboxes that don't handle DNS properly" is a 
truism, but as pointed out by myself and Mark Andrews the value of 
"some" has been reduced to the margins by IPv6 and DNSSEC. Both that 
issue, and the issue of updating provisioning systems are things that 
need to be dealt with, but they are going to be true for whatever 
advances we want to make in the DNS. As an organization we have stated 
that we're not willing to be held hostage to those issues (5507), a 
position with which I maintain full agreement and support.

Further-furthermore, after I suggested that the way forward is to query 
SPF/99 first, it came to light that 2 of the major implementations 
(Mail::SPF and libspf2) _already do that_. A fact that the WG seems to 
be conveniently ignoring.

Frankly at this point I'm wondering what the fuss is about.

> nor by any argument that leads to the
> conclusion that an arrangement we would all like better has any chance
> of deployment.

If your argument here is, "The SPF literati have spoken, don't intend to 
change, and wish you to stop bothering them by pointing out that they've 
come to the wrong conclusion," I'm sure you can imagine my response. 
However, given that 2 of the major implementations _have already 
switched to doing what I suggested_, what we're really talking about 
here is winning over the hearts and minds of "the masses" who do this 
stuff, write up the docs, etc. Personally I can't think of a better way 
to continue that ball rolling than to publish an spfbis document that 
documents how to do v=spf1 the way it should have been done in the first 
place, and specifies that future versions of SPF will be SPF/99 only.

Doug


From sm@elandsys.com  Fri May  3 16:37:47 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7AF221F8D27 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 16:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Omu0HtVWItGk for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 16:37:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0639321F8B8F for <ietf@ietf.org>; Fri,  3 May 2013 16:37:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.131.245]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r43NbYLe027291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 May 2013 16:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367624266; bh=Va6o8Bbe4lAsyLW52wlUshLS8icSYXG/Tst2o7WeWPw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cynkj42x4ckqBDZNqi3dykD13YWGer771d62BzJpX9tCkDNBAqu2sP+c5oZMwBByP TQJMIa8JoXh3qrNDNAx3U+MzTDfzQ9PTFeBvQHJ/i8szWmQAj2T6ehM+8EMiR5LY29 Jm/yMGUM5GmOJlcLFeiIkynNbFgyJJHQegc6Kfcw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367624266; i=@elandsys.com; bh=Va6o8Bbe4lAsyLW52wlUshLS8icSYXG/Tst2o7WeWPw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OBV5pLPbvF/yOwtfPV51nQ6kavaRdNbm0vNkqLkoay4lRTYqxEAjBaqW5MwAnzlKg //mzq68/PmkMpehV6MjyKenaCZNUogP1PI4+xxgr9AQ80UtQsTWGTJazE4J+8kgfGz 2n/XwoaICzW6F1m7HO5nw4KiQULfoL4N6n42pyis=
Message-Id: <6.2.5.6.2.20130503142947.0b885cb0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 03 May 2013 16:25:11 -0700
To: Tony Hain <alh-ietf@tndh.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Effects on DNS can be severe &&& Re: call for ideas: tail-heavy IETF process
In-Reply-To: <010601ce4842$c7041ce0$550c56a0$@tndh.net>
References: <010601ce4842$c7041ce0$550c56a0$@tndh.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: Fri, 03 May 2013 23:37:47 -0000

Hi Tony,
At 14:11 03-05-2013, Tony Hain wrote:
>See the thread about Re: call for ideas: tail-heavy IETF process for
>discussion about wider review at an earlier point in the process. Also, just
>because there is a discussion on issue-tracker does not mean the document is
>'high quality'. If there is an explicit trade-off being made, the main
>document needs to address that directly so subsequent reviewers and
>implementers know what and why.

Yes.

>I have not followed this discussion, but my cursory read of the tracker
>ticket shows the WG blew off the issue by claiming that historical
>unsophisticated attacks can be easily thwarted, while completely ignoring
>the case where the target domains exist. Aborting an amplification attack on
>failures does not do anything about the case where an attacker goes to the
>trouble to make sure all the quires will return valid answers. Either the
>issue-tracker discussion is inadequate, or this is exactly the kind of thing
>that adds excess delay and workload to the IESG review process.

It seems that the above is related to Issue #24 [1].  I posted a 
rough summary of the initial discussion [2].  I took a look at the 
IETF 83 minutes and I found "DNS amplification attacks" [3] 
mentioned.  There was a message from Andrew Sullivan [4].

A working group may decide to blow off the issue if it wants.  The 
issue can be listed in the write-up.

Regards,
S. Moonesamy

1. http://www.ietf.org/mail-archive/web/spfbis/current/msg00906.html
2. http://www.ietf.org/mail-archive/web/spfbis/current/msg00847.html
3. http://www.ietf.org/proceedings/83/minutes/minutes-83-spfbis.txt
4. http://www.ietf.org/mail-archive/web/spfbis/current/msg00944.html 


From joelja@bogus.com  Fri May  3 16:59:17 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2736F21F8F0D for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 16:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xz+Rat8GU2bx for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 16:59:16 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A4AEC21F848A for <ietf@ietf.org>; Fri,  3 May 2013 16:59:16 -0700 (PDT)
Received: from joels-MacBook-Air.local (50-0-150-57.dsl.static.sonic.net [50.0.150.57]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r43NxDGB044722 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 3 May 2013 23:59:14 GMT (envelope-from joelja@bogus.com)
Message-ID: <51844F52.5050206@bogus.com>
Date: Fri, 03 May 2013 16:59:14 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org>	<5182DD64.7040205@gmail.com>	<5182E2A8.50800@acm.org>	<51839ABA.4010406@internet2.edu>	<51842A94.6060505@gmail.com> <51843485.90802@gmail.com>
In-Reply-To: <51843485.90802@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 03 May 2013 23:59:14 +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: Fri, 03 May 2013 23:59:17 -0000

On 5/3/13 3:04 PM, Brian E Carpenter wrote:
> On 04/05/2013 09:22, Yaron Sheffer wrote:
>> GEN-ART is a good example, but actual document editing is much more work
>> and arguably, less rewarding than a review. So I think this can only
>> succeed with professional (=paid) editors.
> I think I disagree, if we can find the knack of effective crowd-sourcing.
> We do after all have several hundred native English speakers active
> in the IETF, which would mean each one would have to volunteer for
> less than one draft per year and we'd be done.
Variously as an individual contributor, shepherd and chair I have asked 
for source text so that I could provide large copy edits which the 
authors could then apply at their leisure. I have also asked for 
volunteers to help with heavy edits. IMHO polishing a document for 
consumption is a very useful form of contribution, which doesn't 
necessarily require either deep technical background in the area or 
personal involvement in the draft.
> I don't know how much experience you have with professional editors.
> Apart from the RFC Editor crew, my experience has been "mixed". Somebody
> a year or three ago (the last time we had this exact same discussion)
> pointed out the differences between copy-editors and technical editors.
> One difference is that the latter are much more expensive. Copy-editors
> tend to be rule-driven; technical editors are supposed to understand
> the material.
Most working group participants already have a deeper background in the 
area and familiarity with the jargon than a copy-editor.
>
>      Brian
>


From alh-ietf@tndh.net  Fri May  3 17:37:07 2013
Return-Path: <alh-ietf@tndh.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 0AFD821F8696 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 17:37:07 -0700 (PDT)
X-Quarantine-ID: <d+BBQXXFx4hs>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -1.754
X-Spam-Level: 
X-Spam-Status: No, score=-1.754 tagged_above=-999 required=5 tests=[AWL=0.847,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d+BBQXXFx4hs for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 17:37:06 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 59E3521F85DB for <ietf@ietf.org>; Fri,  3 May 2013 17:37:06 -0700 (PDT)
Received: from express.tndh.local ([2001:470:e930:1240:20d:56ff:fe04:4c0a] helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1UYQTD-000B5C-RT; Fri, 03 May 2013 17:37:05 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'S Moonesamy'" <sm+ietf@elandsys.com>
References: <010601ce4842$c7041ce0$550c56a0$@tndh.net> <6.2.5.6.2.20130503142947.0b885cb0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130503142947.0b885cb0@resistor.net>
Subject: RE: Effects on DNS can be severe &&& Re: call for ideas: tail-heavy IETF process
Date: Fri, 3 May 2013 17:36:59 -0700
Message-ID: <011001ce485f$7d3ac6a0$77b053e0$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIOC7na8uZCYc5zz7oNOhYD+W5USAEXBOG4mGvs3yA=
Content-Language: en-us
X-SA-Exim-Connect-IP: 2001:470:e930:1240:20d:56ff:fe04:4c0a
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to false
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, 04 May 2013 00:37:07 -0000

S Moonesamy wrote:
> ...
> 
> >I have not followed this discussion, but my cursory read of the tracker
> >ticket shows the WG blew off the issue by claiming that historical
> >unsophisticated attacks can be easily thwarted, while completely
> >ignoring the case where the target domains exist. Aborting an
> >amplification attack on failures does not do anything about the case
> >where an attacker goes to the trouble to make sure all the quires will
> >return valid answers. Either the issue-tracker discussion is
> >inadequate, or this is exactly the kind of thing that adds excess delay
and
> workload to the IESG review process.
> 
> It seems that the above is related to Issue #24 [1].  I posted a rough
summary
> of the initial discussion [2].  I took a look at the IETF 83 minutes and I
found
> "DNS amplification attacks" [3] mentioned.  There was a message from
> Andrew Sullivan [4].
> 
> A working group may decide to blow off the issue if it wants.  The issue
can
> be listed in the write-up.

Yes it can, and they often do. The question in this case is more about the
way that was documented, and Douglas' effective call for a wider review of
the decision. It may simply be the wording in the issue tracker, but reading
that the effective message is: 
   "a security issue was raised, and a subset of the potential attack is
easily mitigated, therefore the WG is dropping it"
There may well be more to it, and I said I have not been following it. The
point is that 'outside reviewers' will not be immersed in past discussion,
so what and why should be clear. I purposefully tied this to the ongoing
IESG process discussion, because it is a prime example of why post-WG
discussions take longer than expected, and may result in changes. 

Tony





From marka@isc.org  Fri May  3 17:51:16 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 491AE21F8B8F for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 17:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QbKlei3WcbV for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 17:51:14 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id C76C921F8B5F for <ietf@ietf.org>; Fri,  3 May 2013 17:51:12 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 483B4C947D; Sat,  4 May 2013 00:51:04 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367628672; bh=ZGQRGeLnF8uOkuCHSqMm8OItPiorcwI0b3Va1AVBTJg=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=c4v6RvEgeQ3Vlz0wzyQFsKTOc4PJhEI/LA36gLXftNyXaAhP1lzOUSpNpOPNrsHwa HrlVnWaGHYqAGZ1bs4X6RmmVVa48DNuRhl9L6Xdlxoku/k3pAkL7WWBvUnyBQX6ycH 1f0qTHrQ/3au6+bfuRrElaMlvCxdcOKpASyCZ1xY=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Sat,  4 May 2013 00:51:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 87948216C40; Sat,  4 May 2013 00:51:03 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 4A4EA33E4543; Sat,  4 May 2013 10:49:39 +1000 (EST)
To: Warren Kumari <warren@kumari.net>
From: Mark Andrews <marka@isc.org>
References: <20130425013317.36729.qmail@joyce.lan> <4272263.gKzvRQiTlr@scott-latitude-e6320> <517C8994.2080102@gathman.org> <1457820.oICsLp4n8g@scott-latitude-e6320> <20130428195221.GA27654@besserwisser.org> <8D23D4052ABE7A4490E77B1A012B630775165072@mbx-01.win.nominum.com> <517DAB89.8000409@gathman.org> <8D23D4052ABE7A4490E77B1A012B63077516524E@mbx-01.win.nominum.com> <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <517FFB33.30902@dougbarton.us> <CAL0qLwZi+NtPru1b_mmJ3jw3dSwVaQ7RDVSQAVYWQFJUJh9DHA@mail.gmail.com> <A16DD867-53BC-4184-981E-363933674F9D@virtualized.org> <tslhain34vj.fsf@mit.edu> <51811C20.5040305@qti.qualcomm.com> <5182828C.3040200@isdg.net> <20130503015620.E520433A79C0@drugs.dv.isc.org> <86172038-8F62-4508-8199-BE4C16906A65@kumari.net>
Subject: Re: [IETF] Re: Balancing the Process (Was: Obsoleting SPF RRTYPE)
In-reply-to: Your message of "Fri, 03 May 2013 13:01:55 -0400." <86172038-8F62-4508-8199-BE4C16906A65@kumari.net>
Date: Sat, 04 May 2013 10:49:34 +1000
Message-Id: <20130504004940.4A4EA33E4543@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 00:51:17 -0000

In message <86172038-8F62-4508-8199-BE4C16906A65@kumari.net>, Warren Kumari writes:
>
> On May 2, 2013, at 9:56 PM, Mark Andrews <marka@isc.org> wrote:
>
> >
> > In message <5182828C.3040200@isdg.net>, Hector Santos writes:
> >> Mr. Resnick,  for the record, I wasn't upset. Believe it or not, I was
> >> actually applying an suggestion posted last month or so here with the
> >> IETF diversity talks to help get a major WG issue resolved, one with a
> >> near surety of an appeal, resolved and addressed much faster and hence
> >> avoid a waste of time on the behalf of all.
> >>
> >> How appropo, that a topic of "balancing of process" as being
> considered.
> >>   It is one thing I believe the IETF needs and can be actually apply
> >> today. Yes, I don't agree with the negative tone taken in SPFBIS where
> >> in effect, an attempt to shut down communications and indirectly
> >> personally attack posters occurred and the advocates of the SPF RRTYPE
> >> removal (incidentally, a SPEC change which I believe was prohibited by
> >> the charter), basically blowing off advocates of a RFC4408 status quo.
> >> If you believe that was proper, I think we have a WG problem.
> >>
> >> Overall, I believe this (keep the migration path) is the proper
> >> compromise to resolve the issue, and I believe that this particular
> >> issue is industry-wide important to resolve with across the board
> >> engineering input. It *SHOULD NOT* be reserved only to the
> applications
> >> SPFBIS group especially when we know what the DNS community will say
> >> about this and has said so since MARID 2003 and again last year in
> IETF
> >> and DNSOPs. I was simply hoping to help "Balance the process" then as
> I
> >> was attempted to do again.  If I was in error for trying to get a
> >> serious issue resolve, then please accept my apology.
> >>
> >> Sincerely,
> >>
> >> Hector Santos
> >
> > One of the questions is how to deal with vendors that claim to ship
> > a product which is in compliance with the protcol when they are
> > not.
> >
> > The DNS protocol has a error code for when you do not understand a
> > query, FORMERR.  It also has a error code for when you do not
> > implement part of the protocol, NOTIMP.
> >
> > With RFC 103[45] you have three choices as a developer when you get
> > a query type you don't know about.
> >
> > 1. Treat it as a FORMERR.
> > 2. Treat it as a NOTIMP.
> > 3. Treat it as a opaque data.
> >
> > Now in my book it isn't a FORMERR as you can understand the question
> > even if you can't deal with it.  NOTIMP is a reasonable response
> > though I believe the intent in RFC 103[45] was to treat it as opaque
> > data query which is what RFC 3597 says to do.
> >
> > Nowhere in RFC 103[45] does it say DO NOT RESPOND to the query yet
> > we have DNS vendors that ship products that do just that and are
> > claiming that they conform to the protocol.
> >
> > For a example of a set of servers that does this see earthlink.net's
> > servers.
> >
> > Query for HINFO/earthlink.net at the authoritative servers for
> > earthlink.net (itchy.earthlink.net and scratchy.earthlink.net) and
> > you will not get a response.  A RFC 103[45] compliant server should
> > know about HINFO.  It should also be capable of returning a NOERROR
> > NODATA response for that query and it fact will if you ask for a
> > non-existent TXT record at a name it serves.
> >
> > How do we deal with sites?
> > How do we deal with vendors that ship such product?
>
> Unless the caffeine just hasn't sunk in yet, it works for me:
>
> wmbt-macbookair:Preferences wkumari$ dig HINFO earthlink.net
> @scratchy.earthlink.net
>
> ; <<>> DiG 9.8.3-P1 <<>> HINFO earthlink.net @scratchy.earthlink.net
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1906
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;earthlink.net.			IN	HINFO
>
> ;; AUTHORITY SECTION:
> earthlink.net.		1800	IN	SOA	itchy.earthlink.net.
> hostmaster.earthlink.net. 2013042602 3600 300 2592000 1800
>
> ;; Query time: 51 msec
> ;; SERVER: 207.69.188.197#53(207.69.188.197)
> ;; WHEN: Fri May  3 12:59:50 2013
> ;; MSG SIZE  rcvd: 84
>
> So, maybe the way you fix such sites / deal with vendors that ship such
> products is you post to ietf@ietf.org and cc hostmaster@site?
>
> :-P
> W

Did you see the bounce that came back from hostmaster@earthlink.net?

You follow the link in that email and there is no where to report
the problem.  None of the options offered was really sensible though
I did open a chat window and report the problem.  I doubt it will
have much effect.

Whois doesn't help.  Same bouncing email address or one needs to
make a international phone call to report the problem.

And no it still doesn't work, below, from where I am in the world
not that ietf@ is the right place to diagnose this specific issue.

Earthlink.net isn't the only zone, it is just a example.

The ones in a position to make a difference are the registries and
registrars.  They can test the nameservers when they are registered
and annually there after.  They can also remove the delegation if
a detected problem is not fixed in a timely manner.

One shouldn't be allowed to register a non compliant nameserver,
where not responding to arbitary query types is a form of non
compliance.  Similar non compliance is returning a SOA record other
that that for the delegated zone in a negative answer.

These are the two errors that most impact on the ability to deploy
new types.  They are also things that are not usually checked for.

Yes this is a attempt to clean up the commons.

Mark

[drugs:~/git/bind9] marka% dig soa earthlink.net @scratchy.earthlink.net

; <<>> DiG 9.9.3-S1rc2 <<>> soa earthlink.net @scratchy.earthlink.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39882
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;earthlink.net.			IN	SOA

;; ANSWER SECTION:
earthlink.net.		1800	IN	SOA	itchy.earthlink.net. hostmaster.earthlink.net. 2013042602 3600 300 2592000 1800

;; AUTHORITY SECTION:
earthlink.net.		1800	IN	NS	itchy.earthlink.net.
earthlink.net.		1800	IN	NS	scratchy.earthlink.net.

;; ADDITIONAL SECTION:
itchy.earthlink.net.	1800	IN	A	207.69.188.196
scratchy.earthlink.net.	1800	IN	A	207.69.188.197

;; Query time: 241 msec
;; SERVER: 207.69.188.197#53(207.69.188.197)
;; WHEN: Sat May 04 09:49:15 EST 2013
;; MSG SIZE  rcvd: 164

[drugs:~/git/bind9] marka% dig hinfo earthlink.net @scratchy.earthlink.net

; <<>> DiG 9.9.3-S1rc2 <<>> hinfo earthlink.net @scratchy.earthlink.net
;; global options: +cmd
;; connection timed out; no servers could be reached
[drugs:~/git/bind9] marka% traceroute  scratchy.earthlink.net
traceroute to scratchy.earthlink.net (207.69.188.197), 64 hops max, 52 byte packets
 1  192.168.191.233 (192.168.191.233)  1.498 ms  1.435 ms  1.139 ms
 2  10.72.0.1 (10.72.0.1)  30.066 ms  18.106 ms  19.995 ms
 3  bla2-ge0-0-1.gw.optusnet.com.au (198.142.160.185)  26.258 ms  26.529 ms  21.209 ms
 4  * * *
 5  bla5-ge13-0.gw.optusnet.com.au (211.29.125.249)  27.672 ms  34.851 ms  38.224 ms
 6  203.208.131.57 (203.208.131.57)  181.029 ms  161.411 ms  181.544 ms
 7  las-b3-link.telia.net (80.239.167.189)  163.015 ms  177.855 ms  189.488 ms
 8  las-bb1-link.telia.net (213.155.131.84)  179.306 ms  179.604 ms
    las-bb1-link.telia.net (213.155.134.252)  226.815 ms
 9  ae8.edge1.losangeles.level3.net (4.68.70.129)  169.711 ms  171.338 ms  174.650 ms
10  vlan90.csw4.losangeles1.level3.net (4.69.144.254)  234.904 ms
    vlan60.csw1.losangeles1.level3.net (4.69.144.62)  246.798 ms  228.503 ms
11  ae-62-62.ebr2.losangeles1.level3.net (4.69.137.17)  227.185 ms
    ae-82-82.ebr2.losangeles1.level3.net (4.69.137.25)  237.125 ms  229.297 ms
12  ae-3-3.ebr3.dallas1.level3.net (4.69.132.78)  242.771 ms  244.128 ms  231.012 ms
13  ae-7-7.ebr3.atlanta2.level3.net (4.69.134.22)  311.533 ms  230.136 ms  235.348 ms
14  ae-63-63.ebr1.atlanta2.level3.net (4.69.148.242)  225.662 ms
    ae-73-73.ebr2.atlanta2.level3.net (4.69.148.254)  273.549 ms
    ae-63-63.ebr1.atlanta2.level3.net (4.69.148.242)  239.239 ms
15  ae-26-52.car2.atlanta2.level3.net (4.69.150.70)  242.421 ms
    ae-16-51.car2.atlanta2.level3.net (4.69.150.6)  237.273 ms
    ae-26-52.car2.atlanta2.level3.net (4.69.150.70)  238.109 ms
16  earthlink-i.car2.atlanta2.level3.net (4.71.254.14)  251.459 ms  335.603 ms  239.819 ms
17  cor01-vl-10.ga-atlanta0.ne.earthlink.net (207.69.223.158)  240.427 ms  270.848 ms  228.444 ms
18  * * *
19  * * *
20  * * *
21  * * *
^C
[drugs:~/git/bind9] marka% 


> > Mark
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> >
>
> --
> Hope is not a strategy.
>       --  Ben Treynor, Google
>
>

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From peter@akayla.com  Fri May  3 23:26:15 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 812AA21F8935; Fri,  3 May 2013 23:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDMl+eutx2ct; Fri,  3 May 2013 23:26:10 -0700 (PDT)
Received: from p3plsmtpa08-10.prod.phx3.secureserver.net (p3plsmtpa08-10.prod.phx3.secureserver.net [173.201.193.111]) by ietfa.amsl.com (Postfix) with ESMTP id BBD3121F9027; Fri,  3 May 2013 23:26:10 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-10.prod.phx3.secureserver.net with  id XiS41l00D1huGat01iS5ml; Fri, 03 May 2013 23:26:09 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-netmod-ip-cfg.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-netmod-ip-cfg-09
Date: Fri, 3 May 2013 23:26:07 -0700
Message-ID: <05fd01ce4890$45f5cbf0$d1e163d0$@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: Ac5Ijf7f2lgl5gtAS46HdVoU7WmpFw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 06:26:15 -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-netmod-ip-cfg-09
Reviewer: Peter Yee
Review Date: May-03-2013
IETF LC End Date: May-03-2013
IESG Telechat date: May-16-2013

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

The abstract says it pretty well: This document defines a YANG data model
for management of IP implementations.

Major issues:

Minor issues:

Nits:

Page 7, bottom: The code copyright date says 2012.  Update it to 2013.

Page 10, in leaf phys-address, the description has an incorrect spelling of
"neighbor".

General: where a description of phys-address is given, in both cases it says
"The physical level address...".  It might be more correct to state "The
link layer address..." for most but not all cases.  

That's it.  Everything appears consistent within the limits of my
understanding of YANG.

		-Peter Yee




From sm@elandsys.com  Sat May  4 01:45:46 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7614621F9425 for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 01:45:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHTr3ZYTRUKh for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 01:45:45 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE16121F93AA for <ietf@ietf.org>; Sat,  4 May 2013 01:45:45 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.42]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r448jVHZ013211 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 4 May 2013 01:45:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367657142; bh=S3zgw8c0DkMlb8EjKwhHPyg5wgcF+CUiRnlzzsOMIdY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=We+38LBWeO9CLvJa/xroAQ7EGpPnPHVoE8RMuRozrl2YQfVVPAV6V7hKkeLkn3llM V7ArIGhJuPa4I/G5otCT8YEmov5jbDTwvYvAzXYah9i25X0cyqm2fthFrGIQeGqEIN 14uWDLJpVoiGXnDZZdUsfeZrPD2njjKurhVqhCvU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367657142; i=@elandsys.com; bh=S3zgw8c0DkMlb8EjKwhHPyg5wgcF+CUiRnlzzsOMIdY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lhSCz1RW0g8PNm2vx89GzftEziO7ewl0KxJYfniSaSwmDpF3hedavYXthlHG2yOEi 3U92PsWUO9FqqCli/u6DJYMEM0/EAI7lEif4eP7upYTvtxlsXqPtl5bdUr0KHbbBWI vzl27Evqxj7by2MWoIrejr9K2f4rcLwQImYLNDz8=
Message-Id: <6.2.5.6.2.20130503233627.0ae33708@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 04 May 2013 01:44:52 -0700
To: Tony Hain <alh-ietf@tndh.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Effects on DNS can be severe &&& Re: call for ideas:  tail-heavy IETF process
In-Reply-To: <011001ce485f$7d3ac6a0$77b053e0$@tndh.net>
References: <010601ce4842$c7041ce0$550c56a0$@tndh.net> <6.2.5.6.2.20130503142947.0b885cb0@resistor.net> <011001ce485f$7d3ac6a0$77b053e0$@tndh.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 08:45:46 -0000

Hi Tony,
At 17:36 03-05-2013, Tony Hain wrote:
>Yes it can, and they often do. The question in this case is more about the
>way that was documented, and Douglas' effective call for a wider review of
>the decision. It may simply be the wording in the issue tracker, but reading
>that the effective message is:
>    "a security issue was raised, and a subset of the potential attack is
>easily mitigated, therefore the WG is dropping it"

Yes.  I would add a little more than so that the external reviewer 
can assess whether the potential attack is easily mitigated.

>There may well be more to it, and I said I have not been following it. The
>point is that 'outside reviewers' will not be immersed in past discussion,
>so what and why should be clear. I purposefully tied this to the ongoing
>IESG process discussion, because it is a prime example of why post-WG
>discussions take longer than expected, and may result in changes.

It is difficult for someone who joins a working group in the middle 
of a discussion to understand what happened.  It's a lot of work for 
the external reviewer.  The external reviewer has to decide whether 
to take the word of the author when the latter says "it has been 
discussed".  An IESG member would probably generate a DISCUSS.  The 
working group might respond angrily.  The effect is excessive delay 
for an issue which could easily have been resolved.  In terms of IETF 
time there are four persons having to deal with it.  It is a prime 
example of tail-heavy.

Regards,
S. Moonesamy 


From sm@elandsys.com  Sat May  4 11:38:12 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC9021F9633 for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 11:38:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZzyRggLVvhPr for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 11:38:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23E0B21F962C for <ietf@ietf.org>; Sat,  4 May 2013 11:38:11 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.42]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r44Ibuvs025366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 4 May 2013 11:38:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367692687; bh=K/w5h0dhC9F6qe92ykG0RiAfLk7Ko7qGUjCmVqTUobw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nPwjXl9iw9Z2dGOcNwxfgCZqqHdtYwXE9AxQTrzRY9OPU1k9n3z0QCiwkUDawOGxE FUcVP5Rx9h1b/wBILuiA7ymTJD3cxLKWuf2hX58fgoxzMC9Wdq6MUutV6XPQCUmxpt kb06/aWWWUu4YaNeEj8HxacJTbpPHbPDfLo9ENW8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367692687; i=@elandsys.com; bh=K/w5h0dhC9F6qe92ykG0RiAfLk7Ko7qGUjCmVqTUobw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nAsJIK0+PTBsW8zcD5L5XMVSpJxQ5+v+abc7q3C36Q740Gk7Hr6VvlxGAz7UYVnAD V9Tk8fY1y19xVKjweUrlz6ffRufCAen8gxdw+M+3n96Irq+eaFGxux3UM7VTpsPN+N vn6UbnhgsNshDUX86lpkzyQJLq9CQvR48X/MzNLE=
Message-Id: <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 04 May 2013 11:36:43 -0700
To: Doug Barton <dougb@dougbarton.us>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-Reply-To: <5184460B.2050907@dougbarton.us>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us>
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, 04 May 2013 18:38:12 -0000

Hi Doug,
At 16:19 03-05-2013, Doug Barton wrote:
>I am not saying that the WG members (or chairs) should be given the 
>wet-noodle treatment over having reached a bad decision, but what is 
>cross-area review for if not to catch cases where the WG echo 
>chamber/tunnel vision/what have you -- resulted in a bad outcome?

I'll try explain the problem as I saw it.

  (a) You should have both X and Y

  (b) You must have either X or Y

  (c) If you have X and Y they must be identical

  (d) I can ask you for either X or Y, or for both X and Y

Regards,
S. Moonesamy 


From marka@isc.org  Sat May  4 15:14:03 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF07B21F969A for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 15:14:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id acUwa+GWhy2b for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 15:14:03 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id EE9D021F9699 for <ietf@ietf.org>; Sat,  4 May 2013 15:14:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id B393D5F98E7; Sat,  4 May 2013 22:13:46 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367705638; bh=qN+dfQUGeX2QESrCC7NrO1QOM2kZAuuVGrhLAbjTak4=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=gUHjTrFNLx3Lg0xPdk6lJ3bZKRm6D88jjuNAcQBD/mup/ckjN5VskrMM8g/pDa7wf GEj1+0r3gf4FiCqGZ2LxJVW/kDWdMYv3wI9ysE0lpeDHWRLDWGo3HtLDltLvnkjRdE evERQ6S/pmzDgKvnZ6SBvbiVkXyAmVvIAfAjbzys=
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d99c:b15d:8457:cc13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id BFDF5216C40; Sat,  4 May 2013 22:13:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 5E8DE33E70FE; Sun,  5 May 2013 08:13:31 +1000 (EST)
To: S Moonesamy <sm+ietf@elandsys.com>
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Sat, 04 May 2013 11:36:43 -0700." <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net>
Date: Sun, 05 May 2013 08:13:29 +1000
Message-Id: <20130504221332.5E8DE33E70FE@drugs.dv.isc.org>
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, 04 May 2013 22:14:03 -0000

In message <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net>, S Moonesamy writes:
> Hi Doug,
> At 16:19 03-05-2013, Doug Barton wrote:
> >I am not saying that the WG members (or chairs) should be given the 
> >wet-noodle treatment over having reached a bad decision, but what is 
> >cross-area review for if not to catch cases where the WG echo 
> >chamber/tunnel vision/what have you -- resulted in a bad outcome?
> 
> I'll try explain the problem as I saw it.
> 
>   (a) You should have both X and Y
> 
>   (b) You must have either X or Y
> 
>   (c) If you have X and Y they must be identical
> 
>   (d) I can ask you for either X or Y, or for both X and Y
> 
> Regards,
> S. Moonesamy 
> 

The DNS does not guarentee that the result of 2 consecutive
queries for the same data will be the same even to the same
server (cache or authoritative).

RFC 4408 says that *data* MUST be the same if both records are
present in the zone.  It the operator breaks that MUST then you get
inconsistent results.  Note this is no different to changing the
contents of the record.  You will get inconsistent result while the
record are in transition.

For the client side you assume the MUST is being honoured as there
is no way (other than to ask a * query directly to the authoritative
servers) to check that this is so.  You take the first result which
returns *data* and use it.

This was never a real problem.  Not all MUSTs need to be checked.

Note DNSSEC also has MUSTs about what the server side need to do
which the client side cannot check.  This is the nature of DNS.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Sat May  4 16:12:23 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5F121F9699 for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 16:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[AWL=-0.647, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qn9f4celEVaM for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 16:12:22 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1E221F96E8 for <ietf@ietf.org>; Sat,  4 May 2013 15:58:27 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id C86F5C941E; Sat,  4 May 2013 22:57:50 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367708275; bh=raJnG6dCoM88a3fKXgJM08EL8R0e+qRjBC9lnkj0sco=; h=Cc:From:References:Subject:In-reply-to:Date; b=NFZTpIFkRBC6bgPDjX9THlHBzgURCdEWEDzbhR2rEC0JMqVluA4eIsnaBItT66tFe ST3sVkz8WdnSrqC52L+YEvQIw1p3xabquT6J/Ad9ukYbKhItGH7H6D0nPzN0rMGadW vODrGI4hTtG9FnJ0ttUM2ReCZIh6X8ktYnQ66wjk=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Sat,  4 May 2013 22:57:50 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d99c:b15d:8457:cc13]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 8C042216C40; Sat,  4 May 2013 22:57:50 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 68DE733E7216; Sun,  5 May 2013 08:57:48 +1000 (EST)
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Sun, 05 May 2013 08:13:29 +1000." <20130504221332.5E8DE33E70FE@drugs.dv.isc.org>
Date: Sun, 05 May 2013 08:57:48 +1000
Message-Id: <20130504225748.68DE733E7216@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 23:12:23 -0000

In message <20130504221332.5E8DE33E70FE@drugs.dv.isc.org>, Mark Andrews writes:
> 
> In message <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net>, S Moonesamy writes:
> > Hi Doug,
> > At 16:19 03-05-2013, Doug Barton wrote:
> > >I am not saying that the WG members (or chairs) should be given the 
> > >wet-noodle treatment over having reached a bad decision, but what is 
> > >cross-area review for if not to catch cases where the WG echo 
> > >chamber/tunnel vision/what have you -- resulted in a bad outcome?
> > 
> > I'll try explain the problem as I saw it.
> > 
> >   (a) You should have both X and Y
> > 
> >   (b) You must have either X or Y
> > 
> >   (c) If you have X and Y they must be identical
> > 
> >   (d) I can ask you for either X or Y, or for both X and Y

      (e) X is only for backwards compatibility.

> > 
> > Regards,
> > S. Moonesamy 

The publisher can choose to interoperate with everyone by publishing
both.

The client side can choose to interoperate with everyone by looking
for both.

Both side can choose their level of interoperability.  There is no
bug.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Sat May  4 16:26:28 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1874121F89A6 for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 16:26:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AkDqxiWq57Hf for <ietf@ietfa.amsl.com>; Sat,  4 May 2013 16:26:27 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id D7FE821F8F58 for <ietf@ietf.org>; Sat,  4 May 2013 16:26:26 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 60CE0C941E; Sat,  4 May 2013 23:26:21 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367709986; bh=D8sElvu2XtbuL7GAJXjLVvl5BCbANTGTVeVavxQB0uk=; h=Cc:From:References:Subject:In-reply-to:Date; b=Txn0ieW03CsJVy3ic0dNOTsQlo22PJXyz/xG5bZDLbbrYUt9+ohgwDy3Uyih3fGYG ixe0o4OOPYw0SNtInlU2bekH8PaGMTP5rBS9G8JP5e5Z7MPrUMG9Y7VGoCEqpSl2qD XEOrFeCwbqDdnlGDf/LjoC2ZDRmt7sY9bQAI43Q4=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Sat,  4 May 2013 23:26:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 0463A216C40; Sat,  4 May 2013 23:26:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B623233E7487; Sun,  5 May 2013 09:26:16 +1000 (EST)
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org> <20130504225748.68DE733E7216@drugs.dv.isc.org>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Sun, 05 May 2013 08:57:48 +1000." <20130504225748.68DE733E7216@drugs.dv.isc.org>
Date: Sun, 05 May 2013 09:26:16 +1000
Message-Id: <20130504232616.B623233E7487@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2013 23:26:28 -0000

In message <20130504225748.68DE733E7216@drugs.dv.isc.org>, Mark Andrews writes:
> 
> In message <20130504221332.5E8DE33E70FE@drugs.dv.isc.org>, Mark Andrews writes:
> > 
> > In message <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net>, S Moonesamy writes:
> > > Hi Doug,
> > > At 16:19 03-05-2013, Doug Barton wrote:
> > > >I am not saying that the WG members (or chairs) should be given the 
> > > >wet-noodle treatment over having reached a bad decision, but what is 
> > > >cross-area review for if not to catch cases where the WG echo 
> > > >chamber/tunnel vision/what have you -- resulted in a bad outcome?
> > > 
> > > I'll try explain the problem as I saw it.
> > > 
> > >   (a) You should have both X and Y
> > > 
> > >   (b) You must have either X or Y
> > > 
> > >   (c) If you have X and Y they must be identical
> > > 
> > >   (d) I can ask you for either X or Y, or for both X and Y
> 
>       (e) X is only for backwards compatibility.
> 
> > > 
> > > Regards,
> > > S. Moonesamy 
> 
> The publisher can choose to interoperate with everyone by publishing
> both.
> 
> The client side can choose to interoperate with everyone by looking
> for both.
> 
> Both side can choose their level of interoperability.  There is no
> bug.

Additionally it supports all implementions from pre RFC 4088 through
to the desired end state of type SPF only.

B.T.W. the next point releases of named (at rc2 now) warns if SHOULD
have both is not being done.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From hannes.tschofenig@gmx.net  Sun May  5 02:12:20 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24BD321F8D2E for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ul-BNNfgNpz7 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:12:14 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id B19BA21F87D2 for <ietf@ietf.org>; Sun,  5 May 2013 02:12:13 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MBYme-1Ug2Fm2AbO-00ASI8 for <ietf@ietf.org>; Sun, 05 May 2013 11:12:12 +0200
Received: (qmail invoked by alias); 05 May 2013 09:12:12 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp010) with SMTP; 05 May 2013 11:12:12 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/dthMCO87dmmx4Ij8tOzoTN4bpcD+PcpSxZjQebc 12pT1Ma4NZU/9r
Message-ID: <51862268.8060504@gmx.net>
Date: Sun, 05 May 2013 12:12:08 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Sun, 05 May 2013 09:12:20 -0000

On 05/03/2013 03:59 PM, Thomas Narten wrote:
>> b) There is no interest to research where delay really happen.
> I don't think that is true. Jari has pointed to his work. I think
> there is actually quite a lot of understanding of where the delays
> are. But fixing them is really really hard. Blaming the "tail end" or
> "the IESG" for the problems has always been the easy target. The
> reality (IMO) is that the place where improvements are needed is
> within the WG and on having authors be more responsive. But history
> suggests there are no easy fixes here.

The type of data I am looking for is different to what Jari provides.
I want to know what the real reasons are, which requires you to look at 
the individual documents and their history. Ultimately there are people 
working on these documents and each individual topic has it's own 
challenges contributing to delay, quality, etc.

Regarding your statement about the lower number of implementations it 
really depends what technology you look at. There are differences in 
terms of layers (with lower layer protocols you are less likely to see 
lots of implementations than with high layer protocols), and the 
dependencies a specific technology has (a feature that depends on 10 
other things to be implemented and deployed will see fewer 
implementations).

An example: in JOSE and in OAuth you see a larger number of 
implementations already at an early stage of the document work. How many 
of those will then ultimately get updated to the published RFCs remains 
to be seen.



From hannes.tschofenig@gmx.net  Sun May  5 02:23:40 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5626F21F8EBB for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p5C5cmo5-3AN for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:23:34 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 37AA121F8C98 for <ietf@ietf.org>; Sun,  5 May 2013 02:23:34 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.30]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MbNJC-1UpU6z0lAS-00Imgm for <ietf@ietf.org>; Sun, 05 May 2013 11:23:33 +0200
Received: (qmail invoked by alias); 05 May 2013 09:23:32 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp030) with SMTP; 05 May 2013 11:23:32 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1/bXCNuAw/b6OvcLPBWUy5DFSHqZHMLZFsLzAVTvp M38xI90wW/kiAj
Message-ID: <5186250F.5060409@gmx.net>
Date: Sun, 05 May 2013 12:23:27 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
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: Sun, 05 May 2013 09:23:40 -0000

Thomas, this all sounds very easy and reasonable. Unfortunately, it does 
not work that way (as you might recall from your own WG chair experience).

Both chairs and WG participants are very busy and so they do not 
follow-up on the tasks they had agreed on earlier.

Since everything is done on a volunteer basis you cannot force anyone to 
do something. Additionally, there are lots of unexpected developments 
happening during the WG time.

Just look at the efforts on getting slides for WG sessions ahead of time 
and meeting minutes soon after the meeting.

Ciao
Hannes

PS: I personally found regular conference calls quite helpful to talk to 
folks and to check the current status.

On 05/03/2013 05:13 PM, Thomas Narten wrote:
>> Good point. I guess the obvious answers are "not enough
>> cycles" and, for newer authors, uncertainty about how to
>> get stuff done, but are there other less obvious answers?
>> (Input here might really help the IESG discussion btw since
>> in the nature of things, we're less likely to realise what
>> newer or less frequent participants find problematic.)
>
> One possible step is to have WG Chairs be *managers*, like they are
> supposed to be. That means the equivalent of having project plans. For
> a given document, come up with a (reasonable, pragmatic, workable)
> schedule for getting reviews, discussion, revision, repeat. And then
> get committments from parties (authors, reviewers, etc.) to
> deliver. And followup if they don't...
>
> The current cycle too often seems to be more like "new version
> posted". Wait if anyone reviews. Some reviews eventually, maybe. Oh,
> IETF meeting coming, time for a revision. But with meeting
> approaching, there are a zillion docs and cycles are limited.  Rather
> haphazard, with too many documents effectively only being revised once
> per meeting cycle.
>
> WGs make the most progress when authors respond quickly (within days)
> to reviews, and do so on the list discussing possible text
> revisions. You get much quicker and substantive discussion that way
> and it becomes clear whether folk are converging.
>
> Contrast that with "ask for reviews". Wait a month or two. New
> document appears that says "this reflects comments we got, go
> read". Delays between review/response tend to feed upon
> themselves. Folk forget context, etc., making it more of an effort to
> go back and remember their reviews, etc.
>
> Too much of WG activites are "best effort" where volunteers (who are
> busy and may not actually have the experience to do things optimally)
> are expected magically to just know how things are supposed to work
> make progress. Reality is a bit different.
>
> Two concrete suggestions:
>
> 1) have WGs do the managing role more proactively
> 2) mentor authors and others a bit more to encourage them how best to
> operate
>
> Thomas
>


From hannes.tschofenig@gmx.net  Sun May  5 02:24:02 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 281C321F8FE3 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xba01QiMUs5d for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:23:56 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id DADFA21F9058 for <ietf@ietf.org>; Sun,  5 May 2013 02:23:53 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.30]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0LqGSs-1U4HJx0I1A-00dmt6 for <ietf@ietf.org>; Sun, 05 May 2013 11:23:53 +0200
Received: (qmail invoked by alias); 05 May 2013 09:23:52 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp030) with SMTP; 05 May 2013 11:23:52 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+tLgYmJ82t8rfseJdj72A83pTxocEUCnEBKZas/U vEBSYPmynwRrkW
Message-ID: <51862522.5080408@gmx.net>
Date: Sun, 05 May 2013 12:23:46 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net>
In-Reply-To: <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Sun, 05 May 2013 09:24:02 -0000

On 05/03/2013 01:25 AM, Jari Arkko wrote:
> However, I did want to point out that when I said "tail-heavy", I
> did*not*  necessarily mean delay. I meant that a lot of activity is
> going on, many document changes, and much review is going on.
> Obviously in some cases this translates to delay as well.

In my own document writing experience I agree that there have been a lot 
of document changes because you have to address the review comments. The 
question is (and I wouldn't want to answer that without surveying 
various documents) what difference these changes make in terms of 
interoperability and easier deployment.

> But the delay was really not my main concern. Primarily because I
> think other issues such as transparency to the working group or late
> surprises are more fundamental issues than mere timing.

While the DISCUSSes are available in the tracker most working group 
participants do not pay attention to the tracker itself but they rather 
follow the mailing list. Unless someone (e.g., draft author or WG 
chairs) forward the comments to the list they do not get a lot of 
attention.

For example, I am active in the GEOPRIV working group and I did not 
realize that the technical solution for conveying location in DHCP was 
re-written during the IESG review phase. Maybe I missed the notes to the 
mailing list from the draft authors but I just didn't realize it. It was 
a surprise to me.

I personally would prefer to have all the discusses also sent to the 
working group automatically.

From hannes.tschofenig@gmx.net  Sun May  5 02:27:29 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C82821F8FD6 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:27:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5T6kMsBEb+O for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 02:27:23 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1AA21F8C98 for <ietf@ietf.org>; Sun,  5 May 2013 02:27:22 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.33]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Lex3B-1UDsCk1qf9-00qhVJ for <ietf@ietf.org>; Sun, 05 May 2013 11:27:21 +0200
Received: (qmail invoked by alias); 05 May 2013 09:27:21 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp033) with SMTP; 05 May 2013 11:27:21 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19ULWFU7NxU2YQKoz7Yoj/TcMMlBHDAiZ1LnZ2R5B l5KmONP0B0mJz+
Message-ID: <518625F4.4010305@gmx.net>
Date: Sun, 05 May 2013 12:27:16 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org> <5183CB90.7030900@dcrocker.net> <20130503165226.GN23227@verdi>
In-Reply-To: <20130503165226.GN23227@verdi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: dcrocker@bbiw.net, 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: Sun, 05 May 2013 09:27:29 -0000

On 05/03/2013 07:52 PM, John Leslie wrote:
> Dave Crocker <dhc@dcrocker.net> wrote:
>> On 5/3/2013 7:29 AM, Ray Pelletier wrote:
>>
>>> Provide WG Chairs the monitoring tools they need to be proactive - Action
>>> Tracker, what do I need to do today data tracker  views.  Same for AD.
>>>
>>> Same for authors and their mentors, if any.
>>
>> The IETF already provides pretty good tools.  They could always be
>> better, of course, but they almost certainly aren't essential.
>
>     That much is probably true.


I would have always hoped to have a tools where I can register the 
persons who said that they do a review and then get them reminded 
automatically.

>
>> The issue with providing management assistance is to focus on managing
>> the work.  That's an organizational orientation, not just a tracking
>> thing.  It's about getting clarity of the work to be done and of getting
>> folks to do the work of contributing, writing, reviewing, and debating
>> in a timely manner, and achieving forward progress in a timely manner.
>
>     That much is true.
>
>> Few working groups have enough detail to juggle to make this something
>> that hinges on the tools.
>
>     That, alas, is not true.
>
>     I subscribe to a number of WG lists where they find a issue tracker
> _quite_ essential to their work. And to most folks, the issue tracker
> output is more confusing than helpful: you're never quite sure which
> issue number something belongs under.

I got the same impression. It may work fine for software projects...
>
>     The lists I subscribe to have as work items drafts where nothing
> happens until IETF-week deadlines (and sometimes not even then!).

Yup.



From joelja@bogus.com  Sun May  5 03:24:16 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 038D621F8FE3 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.607
X-Spam-Level: 
X-Spam-Status: No, score=-101.607 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJFHGbpmFO4t for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:24:15 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 926EC21F8FD6 for <ietf@ietf.org>; Sun,  5 May 2013 03:24:15 -0700 (PDT)
Received: from joels-MacBook-Air.local (no-reverse-dns.mlnet.ie [31.216.236.149] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r45AO9ir063870 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 5 May 2013 10:24:13 GMT (envelope-from joelja@bogus.com)
Message-ID: <51857D11.4030406@bogus.com>
Date: Sat, 04 May 2013 14:26:41 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>, Scott Brim <swb@internet2.edu>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com>	<51818258.6000303@internet2.edu> <8D23D4052ABE7A4490E77B1A012B63077516B8B5@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077516B8B5@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 05 May 2013 10:24:15 +0000 (UTC)
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: Sun, 05 May 2013 10:24:16 -0000

On 5/1/13 2:10 PM, Ted Lemon wrote:
> On May 1, 2013, at 5:00 PM, Scott Brim <swb@internet2.edu> wrote:
>> Let's rename "last call" to
>> something like "IETF review" and stop giving people the wrong
>> expectations.  Review outside the WG is vital, can be done repeatedly,
>> and must be done by the whole IETF at least once.
> Yup.   The term "last call" is traditional, and I feel a bit of attachment to it, but I think your observation here is exactly correct: we ought not to think of the IETF last call as the end of the process.
>
> However, that is a bit of a problem, because I think it's fairly rare for documents to get additional "review" at last call time.   Changing the name probably won't fix that.
It feels like unless something is particularly controversial that the 
likelihood of it getting useful review other than solicited ones during 
last call has actually gone down. If it's fully cooked, and sometime it 
seems that they aren't, that lack of commentary does not indicate 
consensus  or readiness in particular.

>


From bclaise@cisco.com  Sun May  5 03:38:40 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F94F21F8FE5 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=0.301, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gEGv-WJSf7+p for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:38:35 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0B021F89A6 for <ietf@ietf.org>; Sun,  5 May 2013 03:38:28 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45AcQwg021175; Sun, 5 May 2013 12:38:26 +0200 (CEST)
Received: from [10.61.90.41] (ams3-vpn-dhcp6698.cisco.com [10.61.90.41]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45Abh13004347; Sun, 5 May 2013 12:37:58 +0200 (CEST)
Message-ID: <51863677.7010807@cisco.com>
Date: Sun, 05 May 2013 12:37:43 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im> <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com> <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org>
In-Reply-To: <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Sun, 05 May 2013 10:38:40 -0000

On 2/05/2013 18:17, Carsten Bormann wrote:
> On May 2, 2013, at 07:21, "Eggert, Lars" <lars@netapp.com> wrote:
>
>> Yeah, all kinds of issues, but if we created a new thing here in between WGLC and PS, the broader industry would never understand.
> That is a matter of naming and marketing ("candidate RFC"?).
There is already some misconception between I-RFC and Standards Tracks RFC.
I don't believe that adding a new name/category would help: instead it 
would add to the confusion.

Regards, Benoit

>
> The "this is baked, go and implement it" signal to the outside is only one aspect, though.
>
> The other two things that were mentioned:
> -- get the cross-area review going;
> -- get the numbers (IANA).
>
> As we are seeing e.g., with MPL (ROLL WG) right now, the latter can go wrong (aspects of the protocol still change, the allocation has to change with it).
> But that isn't too much of a cost in most cases.
>
> Re the cross-area review:  Doing it earlier doesn't mean doing more.  In theory.
> In practice, not-really-baked stuff comes up and needs to be reviewed n times.
> (As an appsdir reviewer, I have seen that happen.)
>
> I think the WGLC is the wrong process step to define something as baked.
> -- too late, because there may still be some (identifiable) random corner that the WG wants to fix;
> -- too early, because the WG may be deluded or mismanaged.
> Much better would be a simple collusion between WG chairs and sponsoring AD.
> (In any sensible WG, you would still involve the WG, of course.)
>
> Grüße, Carsten
>
>
>


From Ted.Lemon@nominum.com  Sun May  5 03:44:49 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E3221F90AF for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eTrfqkSPod7v for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:44:43 -0700 (PDT)
Received: from exprod7og114.obsmtp.com (exprod7og114.obsmtp.com [64.18.2.215]) by ietfa.amsl.com (Postfix) with ESMTP id DBDB821F909A for <ietf@ietf.org>; Sun,  5 May 2013 03:44:42 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob114.postini.com ([64.18.6.12]) with SMTP ID DSNKUYY4Grlw+5BNnNNaXiCXVCfWnGDFOUcH@postini.com; Sun, 05 May 2013 03:44:42 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5E2141B80DF for <ietf@ietf.org>; Sun,  5 May 2013 03:44:42 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 52F41190060; Sun,  5 May 2013 03:44:42 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Sun, 5 May 2013 03:44:42 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pjxE7gAgAAjGACAAA8/AIAAAveAgAS7coCAAN7tAA==
Date: Sun, 5 May 2013 10:44:41 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630775170CD1@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5181758E.5070008@gmail.com> <51818258.6000303@internet2.edu> <8D23D4052ABE7A4490E77B1A012B63077516B8B5@mbx-01.win.nominum.com> <51857D11.4030406@bogus.com>
In-Reply-To: <51857D11.4030406@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <18C24C27DAEB534E9BA0DECFD00F34D2@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Sun, 05 May 2013 10:44:49 -0000

On May 4, 2013, at 10:26 PM, joel jaeggli <joelja@bogus.com> wrote:
>> However, that is a bit of a problem, because I think it's fairly rare fo=
r documents to get additional "review" at last call time.   Changing the na=
me probably won't fix that.
> It feels like unless something is particularly controversial that the lik=
elihood of it getting useful review other than solicited ones during last c=
all has actually gone down. If it's fully cooked, and sometime it seems tha=
t they aren't, that lack of commentary does not indicate consensus  or read=
iness in particular.

By "last call time" I was referring to IETF last call, not WGLC.   I am pai=
nfully familiar with "we'll do a WGLC to see if we can get some review."


From bclaise@cisco.com  Sun May  5 03:51:26 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A00321F91A0 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.449
X-Spam-Level: 
X-Spam-Status: No, score=-10.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOxi2WAUZJNM for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 03:51:21 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 404F121F9195 for <ietf@ietf.org>; Sun,  5 May 2013 03:51:13 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45Ap8JL022264; Sun, 5 May 2013 12:51:08 +0200 (CEST)
Received: from [10.61.90.41] (ams3-vpn-dhcp6698.cisco.com [10.61.90.41]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45AoH6t009999; Sun, 5 May 2013 12:50:38 +0200 (CEST)
Message-ID: <51863969.70208@cisco.com>
Date: Sun, 05 May 2013 12:50:17 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
In-Reply-To: <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sun, 05 May 2013 10:51:26 -0000

Thomas,
>> Good point. I guess the obvious answers are "not enough
>> cycles" and, for newer authors, uncertainty about how to
>> get stuff done, but are there other less obvious answers?
>> (Input here might really help the IESG discussion btw since
>> in the nature of things, we're less likely to realise what
>> newer or less frequent participants find problematic.)
> One possible step is to have WG Chairs be *managers*, like they are
> supposed to be. That means the equivalent of having project plans. For
> a given document, come up with a (reasonable, pragmatic, workable)
> schedule for getting reviews, discussion, revision, repeat. And then
> get committments from parties (authors, reviewers, etc.) to
> deliver. And followup if they don't...
Replace WG chairs by document shepherd in your email, and I would say "+ 
1" to your entire email.

Regards, Benoit
>
> The current cycle too often seems to be more like "new version
> posted". Wait if anyone reviews. Some reviews eventually, maybe. Oh,
> IETF meeting coming, time for a revision. But with meeting
> approaching, there are a zillion docs and cycles are limited.  Rather
> haphazard, with too many documents effectively only being revised once
> per meeting cycle.
>
> WGs make the most progress when authors respond quickly (within days)
> to reviews, and do so on the list discussing possible text
> revisions. You get much quicker and substantive discussion that way
> and it becomes clear whether folk are converging.
>
> Contrast that with "ask for reviews". Wait a month or two. New
> document appears that says "this reflects comments we got, go
> read". Delays between review/response tend to feed upon
> themselves. Folk forget context, etc., making it more of an effort to
> go back and remember their reviews, etc.
>
> Too much of WG activites are "best effort" where volunteers (who are
> busy and may not actually have the experience to do things optimally)
> are expected magically to just know how things are supposed to work
> make progress. Reality is a bit different.
>
> Two concrete suggestions:
>
> 1) have WGs do the managing role more proactively
> 2) mentor authors and others a bit more to encourage them how best to
> operate
>
> Thomas
>
>


From bclaise@cisco.com  Sun May  5 04:48:24 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DFC21F8B49 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 04:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.499
X-Spam-Level: 
X-Spam-Status: No, score=-10.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlWJog8MAZcu for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 04:48:18 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABF421F8C98 for <ietf@ietf.org>; Sun,  5 May 2013 04:48:18 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45BmASw027061; Sun, 5 May 2013 13:48:10 +0200 (CEST)
Received: from [10.61.90.41] (ams3-vpn-dhcp6698.cisco.com [10.61.90.41]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45BlNHC013067; Sun, 5 May 2013 13:47:33 +0200 (CEST)
Message-ID: <518646CA.3080603@cisco.com>
Date: Sun, 05 May 2013 13:47:22 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com>
In-Reply-To: <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net, 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: Sun, 05 May 2013 11:48:24 -0000

> On May 1, 2013, at 1:59 PM 5/1/13, Dave Crocker <dhc@dcrocker.net> wrote:
>
>> The blog nicely classes the problem as being too heavy-weight during final stages.  The quick discussion thread seems focused on adding a moment at which the draft specification is considered 'baked'.
>>
>> I think that's still too late.
> ...and not useful unless the diverse review and changes to the document take place much earlier in the process to make sure the document is "baked."  Declaring done doesn't make it so.
>
>> Certainly it could be useful, but it's still very late in the process.
> As Jari wrote, we often bury the heavy tail of the process in a limited discussion among IESG and the document authors.
>
> The tail is heavy in two different ways:
>
> * significant review and modification takes place in IESG review, after the WG and the IETF have declared the document done
> * the burden of the review, managing the discussion, making sure any changes fix the problem and don't break anything else often falls on the IESG and even a single AD
When the write-up is done, the WG perception is that their work is done.
Some reviews that come after that, and specifically the IESG ones, are 
considered as coming from trouble-makers.
We should change that perception.
I'm all in favor to keep the WG involved for any reviews: directorate, 
IETF LC, IESG. Currently, we lack consistency wrt where the feedback is 
sent (we're working on that). Now, I feel it's going to imply more 
follow-up work for the ADs as the discussions might take longer. This is 
where the document shepherd could help.

Regards, Benoit

From hannes.tschofenig@gmx.net  Sun May  5 04:54:55 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E652821F9343 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 04:54:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FuSQqLnvabzp for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 04:54:51 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 45D7621F9330 for <ietf@ietf.org>; Sun,  5 May 2013 04:54:51 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.35]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MbNJC-1UpOU22QnE-00Immy for <ietf@ietf.org>; Sun, 05 May 2013 13:54:50 +0200
Received: (qmail invoked by alias); 05 May 2013 11:54:50 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp035) with SMTP; 05 May 2013 13:54:50 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+cmztQccmcU3R64bHHlrmYSnBBaRiBHwTFZfVVcD yIaHFu7s6W6gsF
Message-ID: <51864888.8080802@gmx.net>
Date: Sun, 05 May 2013 14:54:48 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im> <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com> <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org> <51863677.7010807@cisco.com>
In-Reply-To: <51863677.7010807@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>, 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: Sun, 05 May 2013 11:54:56 -0000

On 05/05/2013 01:37 PM, Benoit Claise wrote:
> On 2/05/2013 18:17, Carsten Bormann wrote:
>> On May 2, 2013, at 07:21, "Eggert, Lars" <lars@netapp.com> wrote:
>>
>>> Yeah, all kinds of issues, but if we created a new thing here in
>>> between WGLC and PS, the broader industry would never understand.
>> That is a matter of naming and marketing ("candidate RFC"?).
> There is already some misconception between I-RFC and Standards Tracks RFC.
> I don't believe that adding a new name/category would help: instead it
> would add to the confusion.
>
> Regards, Benoit

Interesting that you mention this.

A note from a recent experience: Together with Olaf we are participating 
in a European Multistakeholder Platform for ICT standardization, see 
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:C:2011:349:0004:0006:EN:PDF

The aim of this group is to find out how to reference IETF RFC (and 
standards from other organizations, like the W3C) since the European 
Commission seems to be unable to just reference standards beyond a small 
set of organizations (such as ETSI).

As you can imagine, the different types of RFCs are not that easy to 
understand for those who do not participate actively in the IETF. 
Getting others to understand the different streams, the various document 
types and different standards is already difficult and maybe there is 
room for simplification here.


From hannes.tschofenig@gmx.net  Sun May  5 05:00:14 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C049421F9346 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 05:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YA9EybaykV3c for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 05:00:09 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id A58E421F9345 for <ietf@ietf.org>; Sun,  5 May 2013 05:00:08 -0700 (PDT)
Received: from mailout-de.gmx.net ([10.1.76.32]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0LpiUy-1U2fnV44m6-00fOff for <ietf@ietf.org>; Sun, 05 May 2013 14:00:08 +0200
Received: (qmail invoked by alias); 05 May 2013 12:00:07 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.200]) [88.115.219.140] by mail.gmx.net (mp032) with SMTP; 05 May 2013 14:00:07 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19PAyl5knVPb6q+VN48sd037Bovq8L4GEHALLGov2 pKaH+xt3cvr8jV
Message-ID: <518649C1.1060206@gmx.net>
Date: Sun, 05 May 2013 15:00:01 +0300
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com> <518646CA.3080603@cisco.com>
In-Reply-To: <518646CA.3080603@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF list <ietf@ietf.org>, 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, 05 May 2013 12:00:14 -0000

On 05/05/2013 02:47 PM, Benoit Claise wrote:
>> The tail is heavy in two different ways:
>>
>> * significant review and modification takes place in IESG review,
>> after the WG and the IETF have declared the document done
>> * the burden of the review, managing the discussion, making sure any
>> changes fix the problem and don't break anything else often falls on
>> the IESG and even a single AD
> When the write-up is done, the WG perception is that their work is done.
> Some reviews that come after that, and specifically the IESG ones, are
> considered as coming from trouble-makers.
> We should change that perception.
> I'm all in favor to keep the WG involved for any reviews: directorate,
> IETF LC, IESG. Currently, we lack consistency wrt where the feedback is
> sent (we're working on that). Now, I feel it's going to imply more
> follow-up work for the ADs as the discussions might take longer. This is
> where the document shepherd could help.

Benoit,

while it is desirable to get wider reviews happen earlier in the process 
there is obviously a challenge: You don't want to ask for reviews before 
the document is stable and you cannot ask many times since good reviews 
are "expensive".

As you indicate there is the perception that the document work is 
finished when the document gets sent to the IESG (maybe because the 
discussions that happen afterwards are less visible).

One approach is to increase visibility of the IESG discussions (and the 
feedback from various review teams) to the working group and the other 
approach is to get AD feedback earlier to the working group.

Ciao
Hannes



From bclaise@cisco.com  Sun May  5 05:18:50 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C1521F930C for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 05:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.523
X-Spam-Level: 
X-Spam-Status: No, score=-10.523 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RtfWzMmWCp8b for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 05:18:45 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 821F021F90AF for <ietf@ietf.org>; Sun,  5 May 2013 05:18:45 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45CIgA3029695; Sun, 5 May 2013 14:18:43 +0200 (CEST)
Received: from [10.61.214.244] ([10.61.214.244]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r45CHkZ9003675; Sun, 5 May 2013 14:17:57 +0200 (CEST)
Message-ID: <51864DEA.201@cisco.com>
Date: Sun, 05 May 2013 14:17:46 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jouni Korhonen <jouni.nospam@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <26DB641A-4C5B-451B-9C23-8EB535B7E8A3@gmail.com>
In-Reply-To: <26DB641A-4C5B-451B-9C23-8EB535B7E8A3@gmail.com>
Content-Type: multipart/alternative; boundary="------------090000000205020007050408"
Cc: Pete Resnick <presnick@qti.qualcomm.com>, 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: Sun, 05 May 2013 12:18:50 -0000

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

Hi Jouni,
> Jari,
>
> This was an interesting (and a needed) writeup. I also want to share
> my view as an IETF newbie who has had a chance to experience IETF
> document process a few times. Sorry for chiming in late..
>
> For the most part I got the feeling that we have the right tools and
> a working process already in place. It is mostly about how we treat
> the process and adjust our habits to it.
>
> The thing I dislike is when you ship a camel into IESG and a horse
> comes out.. and everybody is like "what happened?" ;-) My approach
> would be simple. If a document gets x DISCUSSes out of y or even a
> single DISCUSS would substantially change the technical solution of
> the document, ship it back to the WG - always, no questions asked. The
> document is not ready and we are wasting IESG's time.
Agreed. This is something that the IESG should be more often.
> The technical
> work belongs to the WG. Obviously this begs for a much higher
> threshold for an AD to give a document a DISCUSS instead of a COMMENT.
>
> Then about the habits. From my limited experience, folks are used to
> the think "the document will anyway be reviewed, reworked and can be
> finished in the IESG" and that occasionally shows. I want to believe
> this habit changes if the document must be ready for real before
> leaving the WG.
>
> The cross area directorate reviews are great and should have even
> more weight than they have today. And here is what I would like to
> see to change slightly. The directorate & expert reviews should all
> be done before sending the document out of the WG into the IESG.
> Probably the IETF LC should also happen before sending the document
> out of the WG.
Agreed.
This is a practical solution for the previous email I sent:

    When the write-up is done, the WG perception is that their work is
    done.
    Some reviews that come after that, and specifically the IESG ones,
    are considered as coming from trouble-makers.
    We should change that perception.
    I'm all in favor to keep the WG involved for any reviews:
    directorate, IETF LC, IESG. Currently, we lack consistency wrt where
    the feedback is sent (we're working on that). Now, I feel it's going
    to imply more follow-up work for the ADs as the discussions might
    take longer. This is where the document shepherd could help. 

Regards, Benoit
>
> My Z$0.02,
> 	Jouni
>
>
> On May 1, 2013, at 6:33 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
>
>> I wrote a blog article about how we do a fairly significant amount of reviews and changes in the late stages of the IETF process. Next week the IESG will be having a retreat in Dublin, Ireland. As we brought this topic to our agenda, Pete and I wanted to raise the issue here and call for feedback & ideas for improving the situation with all of you.
>>
>> http://www.ietf.org/blog/2013/05/balancing-the-process/
>>
>> Jari
>>
>
>


--------------090000000205020007050408
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Jouni,<br>
    </div>
    <blockquote
      cite="mid:26DB641A-4C5B-451B-9C23-8EB535B7E8A3@gmail.com"
      type="cite">
      <pre wrap="">
Jari,

This was an interesting (and a needed) writeup. I also want to share
my view as an IETF newbie who has had a chance to experience IETF
document process a few times. Sorry for chiming in late..

For the most part I got the feeling that we have the right tools and
a working process already in place. It is mostly about how we treat
the process and adjust our habits to it.

The thing I dislike is when you ship a camel into IESG and a horse
comes out.. and everybody is like "what happened?" ;-) My approach
would be simple. If a document gets x DISCUSSes out of y or even a
single DISCUSS would substantially change the technical solution of
the document, ship it back to the WG - always, no questions asked. The
document is not ready and we are wasting IESG's time. </pre>
    </blockquote>
    Agreed. This is something that the IESG should be more often.<br>
    <blockquote
      cite="mid:26DB641A-4C5B-451B-9C23-8EB535B7E8A3@gmail.com"
      type="cite">
      <pre wrap="">The technical
work belongs to the WG. Obviously this begs for a much higher
threshold for an AD to give a document a DISCUSS instead of a COMMENT.

Then about the habits. From my limited experience, folks are used to
the think "the document will anyway be reviewed, reworked and can be
finished in the IESG" and that occasionally shows. I want to believe
this habit changes if the document must be ready for real before
leaving the WG.

The cross area directorate reviews are great and should have even
more weight than they have today. And here is what I would like to
see to change slightly. The directorate &amp; expert reviews should all
be done before sending the document out of the WG into the IESG.
Probably the IETF LC should also happen before sending the document
out of the WG.</pre>
    </blockquote>
    Agreed.<br>
    This is a practical solution for the previous email I sent:<br>
    <blockquote>When the write-up is done, the WG perception is that
      their work is done.
      <br>
      Some reviews that come after that, and specifically the IESG ones,
      are considered as coming from trouble-makers.
      <br>
      We should change that perception.
      <br>
      I'm all in favor to keep the WG involved for any reviews:
      directorate, IETF LC, IESG. Currently, we lack consistency wrt
      where the feedback is sent (we're working on that). Now, I feel
      it's going to imply more follow-up work for the ADs as the
      discussions might take longer. This is where the document shepherd
      could help.
    </blockquote>
    Regards, Benoit<br>
    <blockquote
      cite="mid:26DB641A-4C5B-451B-9C23-8EB535B7E8A3@gmail.com"
      type="cite">
      <pre wrap="">

My Z$0.02,
	Jouni


On May 1, 2013, at 6:33 PM, Jari Arkko <a class="moz-txt-link-rfc2396E" href="mailto:jari.arkko@piuha.net">&lt;jari.arkko@piuha.net&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">I wrote a blog article about how we do a fairly significant amount of reviews and changes in the late stages of the IETF process. Next week the IESG will be having a retreat in Dublin, Ireland. As we brought this topic to our agenda, Pete and I wanted to raise the issue here and call for feedback &amp; ideas for improving the situation with all of you.

<a class="moz-txt-link-freetext" href="http://www.ietf.org/blog/2013/05/balancing-the-process/">http://www.ietf.org/blog/2013/05/balancing-the-process/</a>

Jari

</pre>
      </blockquote>
      <pre wrap="">


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090000000205020007050408--

From swb@internet2.edu  Sun May  5 05:39:11 2013
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 D959F21F935A for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 05:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwNyAULmm8mQ for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 05:39:02 -0700 (PDT)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe002.messaging.microsoft.com [65.55.88.12]) by ietfa.amsl.com (Postfix) with ESMTP id 73D8521F933B for <ietf@ietf.org>; Sun,  5 May 2013 05:39:02 -0700 (PDT)
Received: from mail43-tx2-R.bigfish.com (10.9.14.239) by TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id 14.1.225.23; Sun, 5 May 2013 12:39:01 +0000
Received: from mail43-tx2 (localhost [127.0.0.1])	by mail43-tx2-R.bigfish.com (Postfix) with ESMTP id 81E774A0977; Sun,  5 May 2013 12:39:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.85; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0811HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 8
X-BigFish: S8(zzbb2dI98dIzz1f42h1fc6h1d77h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h947hd25he5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h1765h18e1h190ch1946h19b4h19c3h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1b1cn1b1bi1155h)
Received: from mail43-tx2 (localhost.localdomain [127.0.0.1]) by mail43-tx2 (MessageSwitch) id 1367757539509622_14469; Sun,  5 May 2013 12:38:59 +0000 (UTC)
Received: from TX2EHSMHS022.bigfish.com (unknown [10.9.14.233])	by mail43-tx2.bigfish.com (Postfix) with ESMTP id 6D9032A004F; Sun,  5 May 2013 12:38:59 +0000 (UTC)
Received: from CH1PRD0811HT003.namprd08.prod.outlook.com (157.56.245.85) by TX2EHSMHS022.bigfish.com (10.9.99.122) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 5 May 2013 12:38:59 +0000
Received: from swbi2mbp.local (67.241.75.185) by pod51019.outlook.com (10.255.155.38) with Microsoft SMTP Server (TLS) id 14.16.305.3; Sun, 5 May 2013 12:38:58 +0000
Message-ID: <518652E0.7010908@internet2.edu>
Date: Sun, 5 May 2013 08:38:56 -0400
From: Scott Brim <swb@internet2.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5181581E.9010501@dcrocker.net> <5C5ACA6F-1060-4E84-81E5-7B9A7E0E8721@gmail.com> <518646CA.3080603@cisco.com> <518649C1.1060206@gmx.net>
In-Reply-To: <518649C1.1060206@gmx.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [67.241.75.185]
X-OriginatorOrg: internet2.edu
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF list <ietf@ietf.org>, 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, 05 May 2013 12:39:11 -0000

On 05/05/13 08:00, Hannes Tschofenig allegedly wrote:
> while it is desirable to get wider reviews happen earlier in the process
> there is obviously a challenge: You don't want to ask for reviews before
> the document is stable and you cannot ask many times since good reviews
> are "expensive".

There have been several attempts at defining "snapshot" review points,
but afaict working groups rarely feel like a draft is ready for review
until they think it's finished.



From john-ietf@jck.com  Sun May  5 07:34:19 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C72F21F9375 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 07:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABlwy3MI-24o for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 07:34:14 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 00AB421F92F7 for <ietf@ietf.org>; Sun,  5 May 2013 07:34:13 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZ00y-000Nvu-2p; Sun, 05 May 2013 10:34:12 -0400
X-Vipre-Scanned: 035CC79E002C31035CC8EB-TDI
Date: Sun, 05 May 2013 10:34:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Hector Santos <hsantos@isdg.net>, ietf@ietf.org
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF	process]
Message-ID: <14484A135FE38D1C0DE3E705@[192.168.1.128]>
In-Reply-To: <518435D5.5040601@isdg.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 May 2013 14:34:19 -0000

--On Friday, May 03, 2013 18:10 -0400 Hector Santos
<hsantos@isdg.net> wrote:

> May I suggest that the IETF produce a web site for gathering
> IETF participants profiles and even resumes.  It can have a
> questionnaire to extract the valuable information that will
> help maximize the IETF/IESG efforts.  The "Business
> Information" (BI) can then be leveraged by ADs, WGs (and other
> IETF/IESG leaders) to recruits/invite participants for various
> projects, reviews, etc.  It will have many win-wins for all.
> We should consider there are as much, and perhaps even more
> IETF man-years in people that never attended meetings but were
> active for many years, nonetheless, in their various IETF
> protocol interest areas.
> 
> The structure of this questionnaire will be important to be
> successful and beneficial.

Hector,

I can see the advantages of statements of interests and maybe
qualifications.   Moving beyond that to profiles and especially
resumes would give me fairly serious concerns about privacy for
those who supply the information and about inappropriate
pressures (even if unintentional) on those who do not.   There
might even be some analogies to the reasons we keep information
flow to the Nomcom confidential.  There would be clear
advantages to not doing so but, so far, the community has
concluded that, on balance, confidentiality is the wiser course.

best,
   john


From sm@elandsys.com  Sun May  5 11:05:32 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2176D21F9713 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 11:05:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cso8qxTrTk65 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 11:05:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3B121F9712 for <ietf@ietf.org>; Sun,  5 May 2013 11:05:27 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.234.42]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r45I5E8H025502 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 May 2013 11:05:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367777125; bh=Y99SIpund5JM1bx/LxMqcVO77TBSm+K5J6s2RIaNDN4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NCSbh6huN0IG3qWUfEy6HvAOU+vjBH8HV15SNYLjp1GUVc7S05z/EdED9wDNn9ZhB JwkQSQTZtpkmErzB2egVvgryLTWv0CcKHsK9+TaGCMMibX3+EEhWqH/waa/JLOeKVx UFC7IjxQbzqQVPmpMvA4LndKv8ACW0mZpR0kz9lw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1367777125; i=@elandsys.com; bh=Y99SIpund5JM1bx/LxMqcVO77TBSm+K5J6s2RIaNDN4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ht34pxiS4HYDSXOkd/W+cxsYNlFOWSsoMTIJDnqFkz/ch2UHvAUsslok0WzQjgaYy sCrq0zydLkIrJ+55YbeMI6Fa6Nl/wKiYpRr4Jftftb9uoRIc9AQR5LJkQIknWdKcIf 7zp/y34q9EqIjQ7ymlVjE4337tJikfOybEc2fye8=
Message-Id: <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 05 May 2013 08:58:21 -0700
To: Mark Andrews <marka@isc.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-Reply-To: <20130504225748.68DE733E7216@drugs.dv.isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org> <20130504225748.68DE733E7216@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2013 18:05:32 -0000

Hi Mark,
At 15:57 04-05-2013, Mark Andrews wrote:
>The publisher can choose to interoperate with everyone by publishing
>both.
>
>The client side can choose to interoperate with everyone by looking
>for both.
>
>Both side can choose their level of interoperability.  There is no
>bug.

Thanks for the feedback.

Based on the quoted text I would write the text as:

   (i)  you must have X and Y where X and Y are identical.

   (ii) I ask you for both X and Y (see [1] for example).

Item (i) is a combination of the previous items (a) and (c).  Item 
(ii) is the last part of previous item (d).

At 16:26 04-05-2013, Mark Andrews wrote:
>Additionally it supports all implementions from pre RFC 4088 through
>to the desired end state of type SPF only.
>
>B.T.W. the next point releases of named (at rc2 now) warns if SHOULD
>have both is not being done.

Noted.

Regards,
S. Moonesamy

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


From john-ietf@jck.com  Sun May  5 11:32:26 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD3421F96F1 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 11:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XhLJWEmIbmqc for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 11:32:21 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 496FE21F9673 for <ietf@ietf.org>; Sun,  5 May 2013 11:32:21 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZ3jQ-000OjH-AF; Sun, 05 May 2013 14:32:20 -0400
Date: Sun, 05 May 2013 14:32:19 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Yaron Sheffer <yaronf.ietf@gmail.com>
Subject: Re: Language editing
Message-ID: <D80C0D989A6138451CD9F852@[192.168.1.128]>
In-Reply-To: <51843485.90802@gmail.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com>	<5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu>	<51842A94.6060505@gmail.com> <51843485.90802@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 May 2013 18:32:26 -0000

--On Saturday, May 04, 2013 10:04 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 04/05/2013 09:22, Yaron Sheffer wrote:
>> GEN-ART is a good example, but actual document editing is
>> much more work and arguably, less rewarding than a review. So
>> I think this can only succeed with professional (=paid)
>> editors.
> 
> I think I disagree, if we can find the knack of effective
> crowd-sourcing. We do after all have several hundred native
> English speakers active in the IETF, which would mean each one
> would have to volunteer for less than one draft per year and
> we'd be done.

And what we have found more times than I care to think about --
and I've found even more times than that when trying to read
undergraduate papers -- is that "native English speaker" does
not imply "ability to write good, clear, coherent technical
English".  In addition, the IETF includes a reasonable number of
people whose first language is not English but whose ability to
write high-quality technical documents in English generally
exceeds that of our typical native speaker.   So my first
concern is that we not start making plans based on the
population of native speakers -- if we are going to find
volunteers to pretend to be technical editors, or assess the
population of such people, we had better base our assumptions on
the right set of skills.

> I don't know how much experience you have with professional
> editors. Apart from the RFC Editor crew, my experience has
> been "mixed". Somebody a year or three ago (the last time we
> had this exact same discussion) pointed out the differences
> between copy-editors and technical editors. One difference is
> that the latter are much more expensive. Copy-editors tend to
> be rule-driven; technical editors are supposed to understand
> the material.

To be a little more precise, technical editors are supposed to
understand the nature of technical documents, to have good
intuitions about what is clear and precise and what isn't, and
so on.  Specific subject-matter expertise is yet another layer
of requirement and something we would be unlikely to find far
outside the relevant WG or Area.  I think the distinction
between copy editors and technical editors is very significant
(and I might have been the one who made the comment to which you
refer).  But one should not confuse that distinction with the
observation that there are probably as large a proportion of
poor editors who can't deal with material that requires some
skill (in either subcategory) in the world as there are poor
engineers who can't competently handle actual systems design
issues.

Having shepherded (and kicked, clawed, and dragged) a number of
documents through the system in the last few years that were
written by people whose engineering and protocol design skills
far exceeded their [English] technical writing skills, I'm less
optimistic about volunteer editing than several others seem to
be.  If a WG has surplus people with good technical editing
skills to pair with authors who may be better about the
technical details or tracking the WG discussions and getting
them into to document, then that is great.  But I have certainly
worked in or chaired WGs when there are no such people to spare
or who will volunteer.  In addition, it is really hard for
someone who cares enough about the subject matter of the WG to
be able to edit or translate a draft into good, clear, technical
English without injecting their own opinions about areas where
the original I-D may be unclear -- perhaps it is even harder
than writing the document with careful attention to WG consensus.

My guess is that we are going to need a mixed strategy that
involves volunteer (and adequately skilled) editors where we can
find them, professional technical editors where necessary (and a
good model for how they get paid), and oversight of the whole
process by the RFC Editor as well as relevant WG Chairs, ADs,
and the IESG.  We are also going to need to be much more clear
about what level of quality we, as a community (not just the
IESG), want and will insist on before a document goes into Last
Call.  

I've always hoped that the standard could be "absolutely clear
about what is being specified, but everything else can be fixed
by the RFC Editor after approval".  But that requirement is more
easily stated that interpreted and used: I've seen text in
documents that I thought were that good nit-picked by the IESG
and edited by large committees and, with other documents, not
fixed (or even made worse) by the RFC Editor.

There are probably no easy and comprehensive solutions or magic
bullets.

   john
> 
>     Brian





From hsantos@isdg.net  Sun May  5 12:03:43 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8C1F21F9729 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 12:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.518
X-Spam-Level: 
X-Spam-Status: No, score=-101.518 tagged_above=-999 required=5 tests=[AWL=-1.081, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OiEp8oBmpy1R for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 12:03:38 -0700 (PDT)
Received: from mail.catinthebox.net (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id A4F2021F9703 for <ietf@ietf.org>; Sun,  5 May 2013 12:03:38 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2116; t=1367780609; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=UgbLLvP kolOeWEZXG7gmaq18AmA=; b=rBKFvYl2dBxVYPovAsaX/SZZYSdRxd1Z3/Qoe6B gmGHEAA4p09J4/9THiCxyBQIQrIJNkC6RMpSCOhTl8GvHXKEG58cm5A92No+7V16 DiHbmbnpGxRWsXL3TZCURO4+saU86VOhMVvWVqS3Hdr8hm//LWWygtgjg22ngOxU BeLY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 05 May 2013 15:03:29 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2279321764.12305.3648; Sun, 05 May 2013 15:03:29 -0400
Message-ID: <5186ACA4.6060204@isdg.net>
Date: Sun, 05 May 2013 15:01:56 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org> <20130504225748.68DE733E7216@drugs.dv.isc.org> <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130505082013.0adbbe40@elandnews.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: Sun, 05 May 2013 19:03:44 -0000

On 5/5/2013 11:58 AM, S Moonesamy wrote:
> Hi Mark,
> At 15:57 04-05-2013, Mark Andrews wrote:
>> The publisher can choose to interoperate with everyone by publishing
>> both.
>>
>> The client side can choose to interoperate with everyone by looking
>> for both.
>>
>> Both side can choose their level of interoperability.  There is no
>> bug.
>
> Thanks for the feedback.
>
> Based on the quoted text I would write the text as:
>
>    (i)  you must have X and Y where X and Y are identical.
>
>    (ii) I ask you for both X and Y (see [1] for example).
>
> Item (i) is a combination of the previous items (a) and (c).  Item (ii)
> is the last part of previous item (d).

Overall, IMV, this is common sense migration path logic used in many 
concepts:

    Try X first,
    Fallback to Y second;

Where X is the preferred protocol *PATH*.  It is implicit that the data 
is functionally equivalent. I have used a nomenclature of X/Y to signify 
this logic. I thought it was implicit.  In fact, for BIS, I posted an 
issue [1] suggesting a clarification on its tip of using a "Parallel" 
method.  Ultimately, and in theory, this complexity would not be 
necessary, but it may be the only practical solution if there is slow 
resolutions on the existing DNS query barriers.

I guess there is no concern about having dual SPF/TXT calls, either in 
series or in parallel, if there are no delays. The way I long time 
viewed it, the SPF overhead, high redundancy and waste is based on:

   - NXDOMAIN
   - NOERROR
   - Relaxed SPF policies (No Payoff)

I expected the overhead would be short term as more records as published 
and more domains began to switch to -ALL operations.  After 10 years, 
with a slow growth climb, today, I see a 20% SPF rejection rate at our 
support site:

    http://www.winserver.com/SpamStats

Our implementation does not perform HELO/EHLO SPF checking by default 
since it is historically high incorrect value, and the return path SPF 
domain checking is done after the RCPT TO field is validated. This delay 
in SPF processing lowers the SPF DNS overhead by 60%.

--
HLS



From john-ietf@jck.com  Sun May  5 14:23:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75E3D21F9763 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 14:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O47UFZN9yUhC for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 14:23:41 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 67A5121F9762 for <ietf@ietf.org>; Sun,  5 May 2013 14:23:35 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZ6Oz-000PTh-Ex; Sun, 05 May 2013 17:23:25 -0400
Date: Sun, 05 May 2013 17:23:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <635576BE738E49593C8E6A6D@[192.168.1.128]>
In-Reply-To: <201305031729.r43HTMPk021875@cichlid.raleigh.ibm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org> <5183CB90.7030900@dcrocker.net> <201305031729.r43HTMPk021875@cichlid.raleigh.ibm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: adrian@olddog.co.uk, dcrocker@bbiw.net, 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: Sun, 05 May 2013 21:23:46 -0000

--On Friday, May 03, 2013 13:29 -0400 Thomas Narten
<narten@us.ibm.com> wrote:

> Let me expand further on "work plan" and  "project management".
>...
> But it extends to the WG as a whole.  WGs have a finite number
> of cycles. [...] if you spread their
> resources too thinly, a WG starts having problems.
> 
> Few WGs acknowledge that and try to manage it. Managing it
> means:
> 
> 1) identifying core documents that are priority, and minimizing
> distractions that will take cycles away from the priority
> deliverables.
> 
> 2) It may mean making concious decisions not to work on some
> documente *yet* in order to concentrate resources where it
> matters
> 
> 3) it means tying the work plan directly back to the charter.
> If the two aren't in sync, one or both need changing.
> 
> 4) It means recognizing that there are real limits to how many
> documents a WG can (credibly) work on at any one time. (Too
> many WGs have lots of marginal documents that suck cycles away
> from the critical ones.) How many WGs say "no" to marginal
> documents?

If one replaces "WG with AD" and then "document" with "WG", one
sees another part of the problem.  It seems to me that we need
to either:

	* reduce expectations of what a given AD is supposed to
	do with WGs and documents  or
	
	* reduce the number of workload-weighted WGs that an AD
	is expected to "manage".

If we don't do one or the other, this discussion's increased
expectations for mentoring, management, and keeping track of the
big picture and long-term issues are unrealistic: neither
ongoing overload nor lurching from one near-crisis to the next
are a good basis for getting either good management or strategic
thinking done.

SIRS has been mentioned as an old idea that we haven't tried.
But, when one starts looking at AD load, there are other
proposals around too: ones to put limits on the number of WGs
and others to change the review process so that we don't expect
the same people to manage WGs, advocate for them, take the lead
in advocating their output, and then do the evaluations.  There
are reasons to believe that combination would not be ideal under
the best of circumstances but, if we are going to expect more
attention to WG oversight and mentoring, it gets worse.

Along the same lines, it seems to me that we need to be able to
trust WG Chairs to correctly understand and monitor both WG
consensus and agreements reached after Last Call.  If that isn't
realistic, we probably need better-trained WG Chairs or
replacement WG Chairs, not more work for the ADs.  In
particular, as another piece of the end game, I think AUTH48
ought to be able to be managed by WG Chairs and authors, with a
general understanding that substantive issues have to go back to
the WG and no AD involvement except in very exceptional cases.

Finally, there are a few things that we used to do, that were
helpful, and that were abandoned due to industry evolution and
changes in priorities.  The original idea of a Proposed Standard
as a fairly rough specification that would be used for study and
evaluation on the basis of implementation experience, not a spec
from which products were built, is one that has been mentioned
(although not quite in that way).   The other one that occurs to
me --done rarely but to good effect-- was to identify WGs who
are doing design work with broad implications and give them
plenary time to explain their goals, work plans, and general
functional ideas.  Done well and timed correctly, that allows
very early and very broad review by the community independent of
what is committed to writing in particular documents and alerts
to issues that had best be considered and resolved earlier
rather than later.  Perhaps we should review our priorities for
plenary time and try that again.

best,
   john







From marka@isc.org  Sun May  5 15:13:56 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CDCB21F9788 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 15:13:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.276
X-Spam-Level: 
X-Spam-Status: No, score=-2.276 tagged_above=-999 required=5 tests=[AWL=0.323,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c2q2S3BKkk84 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 15:13:55 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 7E63C21F9787 for <ietf@ietf.org>; Sun,  5 May 2013 15:13:55 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 724F95F985D; Sun,  5 May 2013 22:13:44 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367792034; bh=+ozgKN9DBiZIDtEzug5JUjy4EjcPz3J5+MP80QA+J0w=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=p7iGitjG5FtwL7JR+iqm5CjGNX5kdrvPzq4yRTRmX4b49tbkf15V6p50fI1W1/0RR MSuJgxhlht1W16nEFWOpUAZmQ/zGIEhoohvxlfxBjKSt9IbdETJWREYe+dhgVYFRd8 8CPHSShwrVRNzvZ7413ExUMEcX+YZFlWr7Nq3jR8=
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 79143216C40; Sun,  5 May 2013 22:13:42 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 3A43733EA4D6; Mon,  6 May 2013 08:13:38 +1000 (EST)
To: S Moonesamy <sm+ietf@elandsys.com>
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org> <20130504225748.68DE733E7216@drugs.dv.isc.org> <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Sun, 05 May 2013 08:58:21 -0700." <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>
Date: Mon, 06 May 2013 08:13:38 +1000
Message-Id: <20130505221338.3A43733EA4D6@drugs.dv.isc.org>
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, 05 May 2013 22:13:56 -0000

In message <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>, S Moonesamy write
s:
> Hi Mark,
> At 15:57 04-05-2013, Mark Andrews wrote:
> >The publisher can choose to interoperate with everyone by publishing
> >both.
> >
> >The client side can choose to interoperate with everyone by looking
> >for both.
> >
> >Both side can choose their level of interoperability.  There is no
> >bug.
> 
> Thanks for the feedback.
> 
> Based on the quoted text I would write the text as:
> 
>    (i)  you must have X and Y where X and Y are identical.
> 
>    (ii) I ask you for both X and Y (see [1] for example).
> 
> Item (i) is a combination of the previous items (a) and (c).  Item 
> (ii) is the last part of previous item (d).

That was not the intent.  Having choice here is very important here.
In fact it is essential to reach the end goal of Y only when starting
with X only.

There is nothing wrong with failing to catch every possible forgery
possible if both sides are using SPF.  Unfortunately the SPF WG
seem to think that unless the RFC does catch every possible forgery
that it is broken.  The SPF WG appears to not want to allow operators
to have the choice.  This is the case "pefect" being the enemy of
"good enough".  We need "good enough" here not "perfect".

Mark

> At 16:26 04-05-2013, Mark Andrews wrote:
> >Additionally it supports all implementions from pre RFC 4088 through
> >to the desired end state of type SPF only.
> >
> >B.T.W. the next point releases of named (at rc2 now) warns if SHOULD
> >have both is not being done.
> 
> Noted.
> 
> Regards,
> S. Moonesamy
> 
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg79114.html 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From scott@kitterman.com  Sun May  5 15:54:39 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E5F21F9789 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 15:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.351
X-Spam-Level: 
X-Spam-Status: No, score=-2.351 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wLISCGdPSAJ6 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 15:54:35 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id D174121F9779 for <ietf@ietf.org>; Sun,  5 May 2013 15:54:34 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 72315956001; Sun,  5 May 2013 17:54:30 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367794470; bh=l/6O1YF54wbC9q9AIOLq/gTMV0LvR0n5MZQrQVIYJrM=; h=In-Reply-To:References:Subject:From:Date:To:From; b=AspQd3IW51i7cCvoPn6Rvt2YNsSnKJmW5AWlVmdZ1NL3upj6bkn4pxdsz9uoFjipk A1YlL3wsscMJl4dGrJWJoREzpQeYaPbAR3OkrjyBXSYyXCEUR6NxEerKay1iwEppPE XSY12XwERBNWu+fO67aEI8ZkQ2XrpwFxIAtP0xTs=
Received: from [192.168.111.101] (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id E02E8D04060;  Sun,  5 May 2013 17:54:29 -0500 (CDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <20130505221338.3A43733EA4D6@drugs.dv.isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org> <20130504225748.68DE733E7216@drugs.dv.isc.org> <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com> <20130505221338.3A43733EA4D6@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: A note about draft-ietf-spfbis-4408bis
From: Scott Kitterman <scott@kitterman.com>
Date: Sun, 05 May 2013 18:54:26 -0400
To: ietf@ietf.org
Message-ID: <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 May 2013 22:54:39 -0000

Mark Andrews <marka@isc.org> wrote:

>
>In message <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>, S
>Moonesamy write
>s:
>> Hi Mark,
>> At 15:57 04-05-2013, Mark Andrews wrote:
>> >The publisher can choose to interoperate with everyone by publishing
>> >both.
>> >
>> >The client side can choose to interoperate with everyone by looking
>> >for both.
>> >
>> >Both side can choose their level of interoperability.  There is no
>> >bug.
>> 
>> Thanks for the feedback.
>> 
>> Based on the quoted text I would write the text as:
>> 
>>    (i)  you must have X and Y where X and Y are identical.
>> 
>>    (ii) I ask you for both X and Y (see [1] for example).
>> 
>> Item (i) is a combination of the previous items (a) and (c).  Item 
>> (ii) is the last part of previous item (d).
>
>That was not the intent.  Having choice here is very important here.
>In fact it is essential to reach the end goal of Y only when starting
>with X only.
>
>There is nothing wrong with failing to catch every possible forgery
>possible if both sides are using SPF.  Unfortunately the SPF WG
>seem to think that unless the RFC does catch every possible forgery
>that it is broken.  The SPF WG appears to not want to allow operators
>to have the choice.  This is the case "pefect" being the enemy of
>"good enough".  We need "good enough" here not "perfect".
>
>Mark

If we publish a 4408bis that suggests the normal way to publish an SPF record is in type SPF, then it'll get about 98% less effective based on the data we've collected. What you are suggesting is more like 'ignore the deployed base and start over'.  That's not wgat the WG was chartered to do.  

Additionally, I'm personally against publishing documents that require special external knowledge (if 4408bis prefers SPF over TXT deployers will have know to ignore that part of the RFC if they actually want the protocol to be useful. To promote interoperability there has to be a MUST publish and a MUST check format in common.  Given the lack of type SPF deployment, it's crazy to suggest that it should be the required type.

Scott K

>> At 16:26 04-05-2013, Mark Andrews wrote:
>> >Additionally it supports all implementions from pre RFC 4088 through
>> >to the desired end state of type SPF only.
>> >
>> >B.T.W. the next point releases of named (at rc2 now) warns if SHOULD
>> >have both is not being done.
>> 
>> Noted.
>> 
>> Regards,
>> S. Moonesamy
>> 
>> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg79114.html 
>> 


From marka@isc.org  Sun May  5 17:10:56 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD87521F973B for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 17:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level: 
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.215,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kaHUOyTW-b44 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 17:10:56 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 0864F21F9738 for <ietf@ietf.org>; Sun,  5 May 2013 17:10:54 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 85892C941E; Mon,  6 May 2013 00:10:45 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367799053; bh=gS1kH43exkC7ZAI5tYUPgqvJryuWLOoIFxm+iktL7ao=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=krkkdZw1e/9gPCDAxJSiXOXs8l/x372AJuNUITaSPqBJByFqJTUpGYZvWupsTUcht QLEUGk/XOd2sgMxo443j/xa3/lMemwAHhOroDbs2ZnWIup34z6LCI9w88fcj+j4/Ny dWOF9u78+5/LrEMUCCSERa8FEHQ90qksfDA16qD8=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Mon,  6 May 2013 00:10:45 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id D1096216C40; Mon,  6 May 2013 00:10:44 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 60BD233EAD7D; Mon,  6 May 2013 10:10:40 +1000 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <8D23D4052ABE7A4490E77B1A012B630775166B76@mbx-01.win.nominum.com> <517EE00D.8050401@dcrocker.net> <517EE2E3.3010003@isdg.net> <20130429230742.3D2833339511@drugs.dv.isc.org> <517FF144.5040600@tana.it> <20130501010455.DE040336241D@drugs.dv.isc.org> <51822FD6.1080805@tana.it> <6.2.5.6.2.20130502060904.0b38f518@resistor.net> <5182BCDB.5080100@dougbarton.us> <20130502195015.GA323@crankycanuck.ca> <5184460B.2050907@dougbarton.us> <6.2.5.6.2.20130504095840.0d4a98d8@resistor.net> <20130504221332.5E8DE33E70FE@drugs.dv.isc.org> <20130504225748.68DE733E7216@drugs.dv.isc.org> <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com> <20130505221338.3A43733EA4D6@drugs.dv.isc.org> <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Sun, 05 May 2013 18:54:26 -0400." <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com>
Date: Mon, 06 May 2013 10:10:40 +1000
Message-Id: <20130506001040.60BD233EAD7D@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
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, 06 May 2013 00:10:57 -0000

In message <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com>, Scott Kitt
erman writes:
> 
> 
> Mark Andrews <marka@isc.org> wrote:
> 
> >
> >In message <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>, S
> >Moonesamy write
> >s:
> >> Hi Mark,
> >> At 15:57 04-05-2013, Mark Andrews wrote:
> >> >The publisher can choose to interoperate with everyone by publishing
> >> >both.
> >> >
> >> >The client side can choose to interoperate with everyone by looking
> >> >for both.
> >> >
> >> >Both side can choose their level of interoperability.  There is no
> >> >bug.
> >> 
> >> Thanks for the feedback.
> >> 
> >> Based on the quoted text I would write the text as:
> >> 
> >>    (i)  you must have X and Y where X and Y are identical.
> >> 
> >>    (ii) I ask you for both X and Y (see [1] for example).
> >> 
> >> Item (i) is a combination of the previous items (a) and (c).  Item 
> >> (ii) is the last part of previous item (d).
> >
> >That was not the intent.  Having choice here is very important here.
> >In fact it is essential to reach the end goal of Y only when starting
> >with X only.
> >
> >There is nothing wrong with failing to catch every possible forgery
> >possible if both sides are using SPF.  Unfortunately the SPF WG
> >seem to think that unless the RFC does catch every possible forgery
> >that it is broken.  The SPF WG appears to not want to allow operators
> >to have the choice.  This is the case "pefect" being the enemy of
> >"good enough".  We need "good enough" here not "perfect".
> >
> >Mark
> 
> If we publish a 4408bis that suggests the normal way to publish an SPF
> record is in type SPF, then it'll get about 98% less effective based on
> the data we've collected. What you are suggesting is more like 'ignore
> the deployed base and start over'.  That's not wgat the WG was chartered
> to do.

No one said "ignore deployed base".  Firstly normal != only.

Secondly one could quite easly add "fixup SPF" functionality to
nameservers/zone signers by having the master server/signers add
type SPF records if they are not present when there are v=spf1 TXT
records.  This would also require fixing some DNSSEC records but
it is doable.

Name servers/signers fixup DNSSEC records all the time.  Adding
another type of record to fixup is a relatively trivial change.

For unsigned zones one could do this on slave servers as well.

You have already mentions you have a script that does it.  A script
needs someone to install it and run it so it is not comparable,
other than a proof of concept that it can be done, to getting
nameservers to do the fixup.  This get done installed and run
automatically.  Installation happens as part of OS upgrades / new
server installs.  It gets run as it is part of the default behaviour.

> Additionally, I'm personally against publishing documents that require
> special external knowledge (if 4408bis prefers SPF over TXT deployers
> will have know to ignore that part of the RFC if they actually want the
> protocol to be useful. To promote interoperability there has to be a MUST
> publish and a MUST check format in common.  Given the lack of type SPF
> deployment, it's crazy to suggest that it should be the required type.

What external knowledge.  4408 already effectly says that you need
to publish SPF records.  TXT records are described as "for backwards
i compatibilty".  It says you SHOULD publish both.

You are worrying about it not been "perfect" when it was in fact
what was in 4088 was "good enough".

Mark

> Scott K
> 
> >> At 16:26 04-05-2013, Mark Andrews wrote:
> >> >Additionally it supports all implementions from pre RFC 4088 through
> >> >to the desired end state of type SPF only.
> >> >
> >> >B.T.W. the next point releases of named (at rc2 now) warns if SHOULD
> >> >have both is not being done.
> >> 
> >> Noted.
> >> 
> >> Regards,
> >> S. Moonesamy
> >> 
> >> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg79114.html 
> >> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From scott@kitterman.com  Sun May  5 20:01:13 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF10E21F8A0B for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 20:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.413
X-Spam-Level: 
X-Spam-Status: No, score=-2.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MmZfqe4lVnqt for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 20:01:07 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 642EF21F8A09 for <ietf@ietf.org>; Sun,  5 May 2013 20:01:07 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 614A620E4128; Sun,  5 May 2013 23:01:06 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1367809266; bh=KBc5RdSYZRayeS3+af5l7gO547FwEsPNYyiyQs+saEI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=BMxoAV5QdW/krnxeSTfH6M5IRZ78wnKd1JnD9SKn3DVL6ZR9RaNbAwiFRa7VXFHb9 yQeXpmUIslPu/wTYVm77r3u92kNn+a1FCEcu1/I8o8aWFYTtOI6nyZeqNiwV6ui3MY FL6bRntvJanuCpcNxwEC/n8F0lyk79av+rKWEq1k=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 3CB2120E411E;  Sun,  5 May 2013 23:01:05 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: A note about draft-ietf-spfbis-4408bis
Date: Sun, 05 May 2013 23:01:02 -0400
Message-ID: <1962766.G247B9R6HU@scott-latitude-e6320>
User-Agent: KMail/4.10.2 (Linux/3.8.0-19-generic; KDE/4.10.2; i686; ; )
In-Reply-To: <20130506001040.60BD233EAD7D@drugs.dv.isc.org>
References: <517E90A6.6090108@gathman.org> <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com> <20130506001040.60BD233EAD7D@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 03:01:13 -0000

On Monday, May 06, 2013 10:10:40 AM Mark Andrews wrote:
> In message <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com>, Scott
> Kitterman writes:
> > Mark Andrews <marka@isc.org> wrote:
> > >In message <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>, S
> > >Moonesamy write
> > >
> > >s:
> > >> Hi Mark,
> > >> 
> > >> At 15:57 04-05-2013, Mark Andrews wrote:
> > >> >The publisher can choose to interoperate with everyone by publishing
> > >> >both.
> > >> >
> > >> >The client side can choose to interoperate with everyone by looking
> > >> >for both.
> > >> >
> > >> >Both side can choose their level of interoperability.  There is no
> > >> >bug.
> > >> 
> > >> Thanks for the feedback.
> > >> 
> > >> Based on the quoted text I would write the text as:
> > >>    (i)  you must have X and Y where X and Y are identical.
> > >>    
> > >>    (ii) I ask you for both X and Y (see [1] for example).
> > >> 
> > >> Item (i) is a combination of the previous items (a) and (c).  Item
> > >> (ii) is the last part of previous item (d).
> > >
> > >That was not the intent.  Having choice here is very important here.
> > >In fact it is essential to reach the end goal of Y only when starting
> > >with X only.
> > >
> > >There is nothing wrong with failing to catch every possible forgery
> > >possible if both sides are using SPF.  Unfortunately the SPF WG
> > >seem to think that unless the RFC does catch every possible forgery
> > >that it is broken.  The SPF WG appears to not want to allow operators
> > >to have the choice.  This is the case "pefect" being the enemy of
> > >"good enough".  We need "good enough" here not "perfect".
> > >
> > >Mark
> > 
> > If we publish a 4408bis that suggests the normal way to publish an SPF
> > record is in type SPF, then it'll get about 98% less effective based on
> > the data we've collected. What you are suggesting is more like 'ignore
> > the deployed base and start over'.  That's not wgat the WG was chartered
> > to do.
> 
> No one said "ignore deployed base".  Firstly normal != only.
> 
> Secondly one could quite easly add "fixup SPF" functionality to
> nameservers/zone signers by having the master server/signers add
> type SPF records if they are not present when there are v=spf1 TXT
> records.  This would also require fixing some DNSSEC records but
> it is doable.
> 
> Name servers/signers fixup DNSSEC records all the time.  Adding
> another type of record to fixup is a relatively trivial change.
> 
> For unsigned zones one could do this on slave servers as well.
> 
> You have already mentions you have a script that does it.  A script
> needs someone to install it and run it so it is not comparable,
> other than a proof of concept that it can be done, to getting
> nameservers to do the fixup.  This get done installed and run
> automatically.  Installation happens as part of OS upgrades / new
> server installs.  It gets run as it is part of the default behaviour.

None of this happened in 8 years.  There's no basis for the next 8 years being 
any different.

> > Additionally, I'm personally against publishing documents that require
> > special external knowledge (if 4408bis prefers SPF over TXT deployers
> > will have know to ignore that part of the RFC if they actually want the
> > protocol to be useful. To promote interoperability there has to be a MUST
> > publish and a MUST check format in common.  Given the lack of type SPF
> > deployment, it's crazy to suggest that it should be the required type.
> 
> What external knowledge.  4408 already effectly says that you need
> to publish SPF records.  TXT records are described as "for backwards
> i compatibilty".  It says you SHOULD publish both.
> 
> You are worrying about it not been "perfect" when it was in fact
> what was in 4088 was "good enough".

What was in 4408 turned out to be pointless and complicating.  There are also 
a few pour souls out there who published type SPF records only and are 
probably wondering why it's not working very well.

Personally, I'm quite surprised that doubling the DNS queries associated with 
SPF for the foreseeable future is a "meh" issue to DNS people.  

If you're going to query for type SPF, then you have to do an asynchronous 
query of some kind due to broken DNS servers that return either nothing 
(meaning you end up waiting for a timeout) or SERVFAIL for unknown types.  You 
still have to do type TXT queries and performance will suffer badly if you do 
them serially.  Additionally, we'd need to special case SERVFAIL for type SPF 
so that in appropriate temperrors weren't returned.  It adds a significant 
amount of complexity if you want to implement both types without poor 
performance (Mail::SPF does the queries sequentially and will fail on a bad 
DNS server, it's not really the model one would want).

I get the theory of type SPF, but dual types adds a lot of complexity for 
minuscule benefit.  A single type is much simpler and more reliable.  
Unfortunately, if it's only going to be one, TXT is the only one that makes 
any sense operationally.

Scott K 

From marka@isc.org  Sun May  5 20:51:51 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7D521F85BB for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 20:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.184
X-Spam-Level: 
X-Spam-Status: No, score=-1.184 tagged_above=-999 required=5 tests=[AWL=-0.985, BAYES_00=-2.599, J_CHICKENPOX_34=0.6, J_CHICKENPOX_62=0.6, J_CHICKENPOX_63=0.6, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6vdnrJV6etL for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 20:51:50 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 451D821F8529 for <ietf@ietf.org>; Sun,  5 May 2013 20:51:50 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 284B5C9450; Mon,  6 May 2013 03:51:42 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367812310; bh=Z6BYlovG6X1dyvyfPNvvVbEC1ULpwXI4hhDR+NVqNRk=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=q+4w+yANjlWoy1Fym/xK0y6/1XuY/m14oO+zUznyboVwllz5PsV1X7Ypf0rjMdq7j pEwayUgMonDkeM8VoKywS9eGVEOhGjqAtdeh27wNV3Tp60cQ9XFa8s71xFRLzscHVz 7HwvAosJ9J3KLwrMnVE/sZXms7lijLZrNEST2rcQ=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Mon,  6 May 2013 03:51:42 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:f44b:4f6c:37a:5c79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 19DE5216C40; Mon,  6 May 2013 03:51:41 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B55D833EC5C8; Mon,  6 May 2013 13:51:37 +1000 (EST)
To: Scott Kitterman <scott@kitterman.com>
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com> <20130506001040.60BD233EAD7D@drugs.dv.isc.org> <1962766.G247B9R6HU@scott-latitude-e6320>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Sun, 05 May 2013 23:01:02 -0400." <1962766.G247B9R6HU@scott-latitude-e6320>
Date: Mon, 06 May 2013 13:51:37 +1000
Message-Id: <20130506035137.B55D833EC5C8@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
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, 06 May 2013 03:51:51 -0000

In message <1962766.G247B9R6HU@scott-latitude-e6320>, Scott Kitterman writes:
> On Monday, May 06, 2013 10:10:40 AM Mark Andrews wrote:
> > In message <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com>, Scott
> > Kitterman writes:
> > > Mark Andrews <marka@isc.org> wrote:
> > > >In message <6.2.5.6.2.20130505082013.0adbbe40@elandnews.com>, S
> > > >Moonesamy write
> > > >
> > > >s:
> > > >> Hi Mark,
> > > >> 
> > > >> At 15:57 04-05-2013, Mark Andrews wrote:
> > > >> >The publisher can choose to interoperate with everyone by publishing
> > > >> >both.
> > > >> >
> > > >> >The client side can choose to interoperate with everyone by looking
> > > >> >for both.
> > > >> >
> > > >> >Both side can choose their level of interoperability.  There is no
> > > >> >bug.
> > > >> 
> > > >> Thanks for the feedback.
> > > >> 
> > > >> Based on the quoted text I would write the text as:
> > > >>    (i)  you must have X and Y where X and Y are identical.
> > > >>    
> > > >>    (ii) I ask you for both X and Y (see [1] for example).
> > > >> 
> > > >> Item (i) is a combination of the previous items (a) and (c).  Item
> > > >> (ii) is the last part of previous item (d).
> > > >
> > > >That was not the intent.  Having choice here is very important here.
> > > >In fact it is essential to reach the end goal of Y only when starting
> > > >with X only.
> > > >
> > > >There is nothing wrong with failing to catch every possible forgery
> > > >possible if both sides are using SPF.  Unfortunately the SPF WG
> > > >seem to think that unless the RFC does catch every possible forgery
> > > >that it is broken.  The SPF WG appears to not want to allow operators
> > > >to have the choice.  This is the case "pefect" being the enemy of
> > > >"good enough".  We need "good enough" here not "perfect".
> > > >
> > > >Mark
> > > 
> > > If we publish a 4408bis that suggests the normal way to publish an SPF
> > > record is in type SPF, then it'll get about 98% less effective based on
> > > the data we've collected. What you are suggesting is more like 'ignore
> > > the deployed base and start over'.  That's not wgat the WG was chartered
> > > to do.
> > 
> > No one said "ignore deployed base".  Firstly normal != only.
> > 
> > Secondly one could quite easly add "fixup SPF" functionality to
> > nameservers/zone signers by having the master server/signers add
> > type SPF records if they are not present when there are v=spf1 TXT
> > records.  This would also require fixing some DNSSEC records but
> > it is doable.
> > 
> > Name servers/signers fixup DNSSEC records all the time.  Adding
> > another type of record to fixup is a relatively trivial change.
> > 
> > For unsigned zones one could do this on slave servers as well.
> > 
> > You have already mentions you have a script that does it.  A script
> > needs someone to install it and run it so it is not comparable,
> > other than a proof of concept that it can be done, to getting
> > nameservers to do the fixup.  This get done installed and run
> > automatically.  Installation happens as part of OS upgrades / new
> > server installs.  It gets run as it is part of the default behaviour.
> 
> None of this happened in 8 years.  There's no basis for the next 8 years being 
> any different.

Sorry that mantra doesn't cut it.

Add words to say "Namesservers SHOULD add SPF records if they
discover v=spf1 TXT records without SPF records." and it gets dead
easy to add code like this below which does it for dnssec-signzone.

The nameserver is a little more complicated but not much more.  Add
some code to UPDATE processing.  Add some code when a master zone
gets loaded.

diff --git a/bin/dnssec/dnssec-signzone.c b/bin/dnssec/dnssec-signzone.c
index 5be654d..cfb3f8c 100644
--- a/bin/dnssec/dnssec-signzone.c
+++ b/bin/dnssec/dnssec-signzone.c
@@ -1677,6 +1677,67 @@ remove_sigs(dns_dbnode_t *node, dns_rdatatype_t which) {
 	dns_rdatasetiter_destroy(&rdsiter);
 }
 
+static isc_result_t
+spfify(dns_db_t *db, dns_db_t *version, dns_dbnode_t *node) {
+	dns_rdata_t rdata = DNS_RDATA_INIT;
+	dns_rdataset_t rdataset;
+	isc_boolean_t have_txt = ISC_FALSE;
+	isc_result_t result;
+
+	dns_rdataset_init(&rdataset);
+
+	result = dns_db_findrdataset(db, node, NULL, dns_rdatatype_spf,
+				     0, 0, &rdataset, NULL);
+	if (result == ISC_R_SUCCESS) {
+		dns_rdataset_disassociate(&rdataset);
+		return (ISC_R_SUCCESS);
+	}
+
+	result = dns_db_findrdataset(db, node, NULL, dns_rdatatype_txt,
+				     0, 0, &rdataset, NULL);
+	if (result != ISC_R_SUCCESS)
+		return (ISC_R_SUCCESS);
+
+	result = dns_rdataset_first(&rdataset);
+	while (result == ISC_R_SUCCESS) {
+		dns_rdataset_current(&rdataset, &rdata);
+		have_txt = dns_rdata_isspf(&rdata);
+		if (have_txt)
+			break;
+		dns_rdata_reset(&rdata);
+		result = dns_rdataset_next(&rdataset);
+	}
+
+	if (have_txt) {
+		dns_rdata_t spf = DNS_RDATA_INIT;
+		dns_rdatalist_t rdatalist;
+		dns_rdataset_t spfset;
+
+		dns_rdataset_init(&spfset);
+
+		dns_rdata_clone(&rdata, &spf);
+		spf.type = dns_rdatatype_spf;
+	
+		rdatalist.rdclass = spf.rdclass;
+		rdatalist.type = spf.type;
+		rdatalist.covers = 0;
+		rdatalist.ttl = rdataset.ttl;
+		ISC_LIST_INIT(rdatalist.rdata);
+		ISC_LIST_APPEND(rdatalist.rdata, &spf, link);
+		result = dns_rdatalist_tordataset(&rdatalist, &spfset);
+		if (result == ISC_R_SUCCESS) {
+			result = dns_db_addrdataset(db, node, version, 0,
+						    &spfset, 0, NULL);
+			dns_rdataset_disassociate(&spfset);
+		}
+	} else
+		result = ISC_R_SUCCESS;
+
+	dns_rdataset_disassociate(&rdataset);
+
+	return (result);
+}
+
 /*%
  * Generate NSEC records for the zone and remove NSEC3/NSEC3PARAM records.
  */
@@ -1798,6 +1859,10 @@ nsecify(void) {
 			fatal("iterating through the database failed: %s",
 			      isc_result_totext(result));
 		dns_dbiterator_pause(dbiter);
+
+		result = spfify(gdb, gversion, node);
+		check_result(result, "spfify()");
+
 		result = dns_nsec_build(gdb, gversion, node, nextname,
 					zone_soa_min_ttl);
 		check_result(result, "dns_nsec_build()");
@@ -2353,6 +2418,10 @@ nsec3ify(unsigned int hashalg, unsigned int iterations,
 		 * We need to pause here to release the lock on the database.
 		 */
 		dns_dbiterator_pause(dbiter);
+
+		result = spfify(gdb, gversion, node);
+		check_result(result, "spfify()");
+
 		addnsec3(name, node, salt, salt_length, iterations,
 			 hashlist, zone_soa_min_ttl);
 		dns_db_detachnode(gdb, &node);
diff --git a/lib/dns/include/dns/rdata.h b/lib/dns/include/dns/rdata.h
index 89ecaf8..d15b589 100644
--- a/lib/dns/include/dns/rdata.h
+++ b/lib/dns/include/dns/rdata.h
@@ -769,6 +769,9 @@ dns_rdata_makedelete(dns_rdata_t *rdata);
 const char *
 dns_rdata_updateop(dns_rdata_t *rdata, dns_section_t section);
 
+isc_boolean_t
+dns_rdata_isspf(const dns_rdata_t *rdata);
+
 ISC_LANG_ENDDECLS
 
 #endif /* DNS_RDATA_H */
diff --git a/lib/dns/rdata.c b/lib/dns/rdata.c
index 2bed961..bbc2a4a 100644
--- a/lib/dns/rdata.c
+++ b/lib/dns/rdata.c
@@ -2174,3 +2174,31 @@ dns_rdata_updateop(dns_rdata_t *rdata, dns_section_t section) {
 	}
 	return ("invalid");
 }
+
+isc_boolean_t
+dns_rdata_isspf(const dns_rdata_t *rdata) {
+        char buf[1024];
+        const unsigned char *data = rdata->data;
+        unsigned int rdl = rdata->length, i = 0, tl, len;
+
+        while (rdl > 0U) {
+                len = tl = *data;
+                ++data;
+                --rdl;
+                INSIST(tl <= rdl);
+                if (len > sizeof(buf) - i - 1)
+                        len = sizeof(buf) - i - 1;
+                memcpy(buf + i, data, len);
+                i += len;
+                data += tl;
+                rdl -= tl;
+        }
+
+        if (i < 6U)
+                return(ISC_FALSE);
+
+        buf[i] = 0;
+        if (strncmp(buf, "v=spf1", 6) == 0 && (buf[6] == 0 || buf[6] == ' '))
+                return (ISC_TRUE);
+        return (ISC_FALSE);
+}

> > > Additionally, I'm personally against publishing documents that require
> > > special external knowledge (if 4408bis prefers SPF over TXT deployers
> > > will have know to ignore that part of the RFC if they actually want the
> > > protocol to be useful. To promote interoperability there has to be a MUST
> > > publish and a MUST check format in common.  Given the lack of type SPF
> > > deployment, it's crazy to suggest that it should be the required type.
> > 
> > What external knowledge.  4408 already effectly says that you need
> > to publish SPF records.  TXT records are described as "for backwards
> > i compatibilty".  It says you SHOULD publish both.
> > 
> > You are worrying about it not been "perfect" when it was in fact
> > what was in 4088 was "good enough".
> 
> What was in 4408 turned out to be pointless and complicating.  There are also 
> a few pour souls out there who published type SPF records only and are 
> probably wondering why it's not working very well.

 
> Personally, I'm quite surprised that doubling the DNS queries associated with 
> SPF for the foreseeable future is a "meh" issue to DNS people.  

You just don't get it.  If you ask nameserver developers to HELP
you they will.

Getting code to modify zone content without a RFC saying to do it
is a uphill battle.  With a RFC it becomes a trivial exercise, "We
need to make our nameserver compliant with RFC XXXX".

> If you're going to query for type SPF, then you have to do an asynchronous 
> query of some kind due to broken DNS servers that return either nothing 
> (meaning you end up waiting for a timeout) or SERVFAIL for unknown types.

And TXT is almost as equally bad as SPF.

> You 
> still have to do type TXT queries and performance will suffer badly if you do 
> them serially.  Additionally, we'd need to special case SERVFAIL for type SPF 
> so that in appropriate temperrors weren't returned.  It adds a significant 
> amount of complexity if you want to implement both types without poor 
> performance (Mail::SPF does the queries sequentially and will fail on a bad 
> DNS server, it's not really the model one would want).

You need to add failure code for TXT as well.

> I get the theory of type SPF, but dual types adds a lot of complexity for 
> minuscule benefit.  A single type is much simpler and more reliable.  
> Unfortunately, if it's only going to be one, TXT is the only one that makes 
> any sense operationally.
> 
> Scott K 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Sun May  5 22:32:14 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0124521F8D2C for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 22:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.492
X-Spam-Level: 
X-Spam-Status: No, score=-1.492 tagged_above=-999 required=5 tests=[AWL=-0.184, BAYES_00=-2.599, MISSING_HEADERS=1.292, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F6PkNd+RuSne for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 22:32:13 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD5E21F8BE4 for <ietf@ietf.org>; Sun,  5 May 2013 22:32:13 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 98CA65F98B1; Mon,  6 May 2013 05:32:03 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367818332; bh=1YETk3i0dolFOVYbqkjG51AEdpPfzsnYeY2HaWHiPpc=; h=Cc:From:References:Subject:In-reply-to:Date; b=c+/kpU4AeNGbM4W2lHDAjuH5BD9KHaz/ayu948oQn1QnlWMt3c1ss0d5cxQp90eFX VIH7E+26wmcU/P+sZLp72b1OhGfLHx75qiey1X01N2EFh310B1+0q0q6bmlC/IP2Cc l/D80l3JAwd1gOufnLjiz89/m7875k8bS19fDxQE=
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:f44b:4f6c:37a:5c79]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 149B2216C40; Mon,  6 May 2013 05:32:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id DCD9A33ED9AC; Mon,  6 May 2013 15:31:59 +1000 (EST)
From: Mark Andrews <marka@isc.org>
References: <517E90A6.6090108@gathman.org> <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com> <20130506001040.60BD233EAD7D@drugs.dv.isc.org> <1962766.G247B9R6HU@scott-latitude-e6320> <20130506035137.B55D833EC5C8@drugs.dv.isc.org>
Subject: Re: A note about draft-ietf-spfbis-4408bis
In-reply-to: Your message of "Mon, 06 May 2013 13:51:37 +1000." <20130506035137.B55D833EC5C8@drugs.dv.isc.org>
Date: Mon, 06 May 2013 15:31:59 +1000
Message-Id: <20130506053159.DCD9A33ED9AC@drugs.dv.isc.org>
Cc: Scott Kitterman <scott@kitterman.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, 06 May 2013 05:32:14 -0000

And if one is worried about keeping automatically generated records
in sync add "auto=yes" as the first modifier to the automatically
generated record.  The two records will remain semantically identical.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mansaxel@besserwisser.org  Sun May  5 23:06:34 2013
Return-Path: <mansaxel@besserwisser.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 4F8D021F8E04 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 23:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9eisyaKTfikM for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 23:06:33 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 744AC21F8DCF for <ietf@ietf.org>; Sun,  5 May 2013 23:06:32 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id A6E559EF0; Mon,  6 May 2013 08:06:30 +0200 (CEST)
Date: Mon, 6 May 2013 08:06:30 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: A note about draft-ietf-spfbis-4408bis
Message-ID: <20130506060630.GD24847@besserwisser.org>
References: <517E90A6.6090108@gathman.org> <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com> <20130506001040.60BD233EAD7D@drugs.dv.isc.org> <1962766.G247B9R6HU@scott-latitude-e6320>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="veXX9dWIonWZEC6h"
Content-Disposition: inline
In-Reply-To: <1962766.G247B9R6HU@scott-latitude-e6320>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
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, 06 May 2013 06:06:34 -0000

--veXX9dWIonWZEC6h
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: A note about draft-ietf-spfbis-4408bis Date: Sun, May 05, 2013=
 at 11:01:02PM -0400 Quoting Scott Kitterman (scott@kitterman.com):
=20
> Personally, I'm quite surprised that doubling the DNS queries associated =
with=20
> SPF for the foreseeable future is a "meh" issue to DNS people. =20

Infrastructure is generally better at scaling to meet increased load
than it is at compensating for protocol ignorance.
=20
--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Yow!  Am I in Milwaukee?

--veXX9dWIonWZEC6h
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlGHSGYACgkQ02/pMZDM1cXabQCcDneBFQWXmXbMpC4nZEc2MDs6
EOYAn081WlADw/EzhrHPg9PmlswKNBEf
=Zxbw
-----END PGP SIGNATURE-----

--veXX9dWIonWZEC6h--

From dougb@dougbarton.us  Sun May  5 23:41:37 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36E5121F85FC for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 23:41:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzkXN6WWGJKW for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 23:41:33 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id EFC2621F85F7 for <ietf@ietf.org>; Sun,  5 May 2013 23:41:32 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:bd97:326e:ce:1bc7] (unknown [IPv6:2001:470:d:5e7:bd97:326e:ce:1bc7]) by dougbarton.us (Postfix) with ESMTPSA id 89F7E22B3F for <ietf@ietf.org>; Mon,  6 May 2013 06:41:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1367822492; bh=DLd/lo/OADhYftgMqS1HY604l32kmtQdu3U57VCzBV4=; h=Date:From:To:Subject:References:In-Reply-To; b=VmJSkB5rDMADVkiMSCgTekT0KWdjh7nyC/hP4iLJ4T330DrtgChUZrsVfOUveizAQ Wk5cACgp9Iqbl2HzWm1XliM+nz7cukvaE6a4iOmq/sMy52WowplpGoryY9C2l2fsZj QYHINXxBX3rUK78lE1dO+iMakeqSz3DRs7fjB+hA=
Message-ID: <5187509C.5080808@dougbarton.us>
Date: Sun, 05 May 2013 23:41:32 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: A note about draft-ietf-spfbis-4408bis
References: <517E90A6.6090108@gathman.org> <42523d2d-85c6-4e6d-b2a7-6791a0e5d4a8@email.android.com> <20130506001040.60BD233EAD7D@drugs.dv.isc.org> <1962766.G247B9R6HU@scott-latitude-e6320> <20130506060630.GD24847@besserwisser.org>
In-Reply-To: <20130506060630.GD24847@besserwisser.org>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
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: Mon, 06 May 2013 06:41:37 -0000

On 05/05/2013 11:06 PM, Måns Nilsson wrote:
> Subject: Re: A note about draft-ietf-spfbis-4408bis Date: Sun, May 05, 2013 at 11:01:02PM -0400 Quoting Scott Kitterman (scott@kitterman.com):
>
>> Personally, I'm quite surprised that doubling the DNS queries associated with
>> SPF for the foreseeable future is a "meh" issue to DNS people.
>
> Infrastructure is generally better at scaling to meet increased load
> than it is at compensating for protocol ignorance.

Not to mention that as I pointed out previously doubling the queries for
SPF (during the transition period) is in the noise when compared to all
the other DNS queries for each message received.


From jari.arkko@piuha.net  Sun May  5 23:46:14 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB7421F8D27 for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 23:46:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tbrcxu4AJlXe for <ietf@ietfa.amsl.com>; Sun,  5 May 2013 23:46:13 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id B967C21F85F7 for <ietf@ietf.org>; Sun,  5 May 2013 23:46:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BEB502CC53; Mon,  6 May 2013 09:45:34 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JsaZwYp4u3Zg; Mon,  6 May 2013 09:45:34 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D91502CC56; Mon,  6 May 2013 09:45:33 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: referencing RFCs (Was: Re: call for ideas: tail-heavy IETF process)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51864888.8080802@gmx.net>
Date: Mon, 6 May 2013 01:50:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D0CB2EA-A31E-41A5-ADE2-3AD7D8B46F21@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im> <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com> <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org> <51863677.7010807@cisco.com> <51864888.8080802@gmx.net>
To: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1503)
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: Mon, 06 May 2013 06:46:14 -0000

Hannes,

> The aim of this group is to find out how to reference IETF RFC (and =
standards from other organizations, like the W3C) since the European =
Commission seems to be unable to just reference standards beyond a small =
set of organizations (such as ETSI).
>=20
> As you can imagine, the different types of RFCs are not that easy to =
understand for those who do not participate actively in the IETF. =
Getting others to understand the different streams, the various document =
types and different standards is already difficult and maybe there is =
room for simplification here.
>=20


This may be going to a side-track from the purposes of the original =
discussion, but thank you Hannes and Olaf working the EC to better =
accept our standards. It is very important work. And I understand it has =
not been easy at all. If I have understood correctly, there is a process =
to accept standards (or groups of standards) one at a time, and that =
we've wanted to push IPv6 as one such specification but despite two =
years and your heroic efforts, we still do not have acceptance.

#rant on

But I'd separate two different reasons for difficulties of this nature. =
First, there is some actual confusion. For instance the distinction =
between different types of RFCs is usually lost on most people outside =
the IETF. But I'd say it is often mixed (and might be so in this case) =
with other issues, such as desire to push other types of standards. I =
really don't know how out of touch you'd have to be to not understand =
that there are some agreed standards in the Internet. Things that are =
glaringly obvious to any user who stares at a screen. Like "http". Or =
IP, if you took even one course in the university about networking =
technology. Actively ignoring reality?

#rant off

Jari


From McQuilWP@pobox.com  Mon May  6 00:26:27 2013
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 C8DB021F8EBE for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 00:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H5E4nyrY1LA7 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 00:26:23 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5AB2221F8EB9 for <ietf@ietf.org>; Mon,  6 May 2013 00:26:20 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 73DA8178A4; Mon,  6 May 2013 07:26:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=B9WAg8JT+00f Kc433Id9sJ+3aFY=; b=B+gM3+cqL86363JpBUWNoNtlvJq0DcIeCG6or1Lad98D SBF/nUMak4HFVZpUA2J8+Y5/3fro2C8uOU8ynZBeD4QwitLrywzmtdoesaglAYYZ JuQDKoyZMmyArEr59PMz12ZXNKUr8iPizYnNf7IGuG1N22Ternfdhn4pzFS7S2Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=sYyMTw B6DVwrBuj0gaefF61HT2lw8mezasvLx/nPLp82rBEKYV4uaJcVxSNlsfkL2XCxt9 se+8OR9PHa1VMur3ytB66TN9Lhy6kApdzrXdlpXcRVHnj63E8c48btrsVhryo2Dq JhNpJdFjQyl/FLMjMuNGHHZ9u3T9flgp6wsrg=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 6BD08178A3; Mon,  6 May 2013 07:26:19 +0000 (UTC)
Received: from BQ07NB (unknown [68.107.15.47]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id DA1EE1789C; Mon,  6 May 2013 07:26:18 +0000 (UTC)
Date: Mon, 6 May 2013 00:26:17 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <262233160.20130506002617@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <635576BE738E49593C8E6A6D@[192\.168\.1\.128]>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org> <5183CB90.7030900@dcrocker.net> <201305031729.r43HTMPk021875@cichlid.raleigh.ibm.com> <635576BE738E49593C8E6A6D@[192.168.1.128]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 3EAC1A4C-B61E-11E2-ABFD-E56BAAC0D69C-02871704!b-pb-sasl-quonix.pobox.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, 06 May 2013 07:26:27 -0000

On Sun, 2013-05-05, John C Klensin wrote:

> Finally, there are a few things that we used to do, that were
> helpful, and that were abandoned due to industry evolution and
> changes in priorities.  The original idea of a Proposed Standard
> as a fairly rough specification that would be used for study and
> evaluation on the basis of implementation experience, not a spec
> from which products were built, is one that has been mentioned
> (although not quite in that way).   

FWIW, this leads me to the thought that the IETF may have a 
terminology problem. The word "standard" is used too soon in the 
maturity levels of RFCs.

I think that our skills are primarily in producing "protocols"
rather than "standards". Perhaps it would have been better if the
names of the maturity levels were something like:

  Proposed Protocol
  Test Version 1 Protocol
  Test Version 2 protocol
   .
   .
   .
  Standard Protocol

Only using the word "standard" when it was determined to be 
stable and recommended for wide usage.

Anyway, my 2 cents.

-- 
Bill McQuillan <McQuilWP@pobox.com>


From olaf@NLnetLabs.nl  Mon May  6 01:35:20 2013
Return-Path: <olaf@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F234821F8F43 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 01:35:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LhNu-Djumz4B for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 01:35:18 -0700 (PDT)
Received: from open.nlnetlabs.nl (open.nlnetlabs.nl [IPv6:2001:7b8:206:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB2F21F8F53 for <ietf@ietf.org>; Mon,  6 May 2013 01:35:14 -0700 (PDT)
Received: from [192.168.178.179] (peer.kolkman.org [82.95.132.144]) (authenticated bits=0) by open.nlnetlabs.nl (8.14.7/8.14.4) with ESMTP id r468Z4YM094634 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 May 2013 10:35:05 +0200 (CEST) (envelope-from olaf@NLnetLabs.nl)
Authentication-Results: open.nlnetlabs.nl; dmarc=none header.from=NLnetLabs.nl
DKIM-Filter: OpenDKIM Filter v2.8.2 open.nlnetlabs.nl r468Z4YM094634
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1367829309; bh=XSDIhLQ46GMem2EyF+0OEz8+WtAxG9zwhSh+i2V55b8=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=iYUNStrrCVs7hLfsas3oxzRgDmek23+eROr76L+1eYkxIM2WeRT14azwV5K8ZVxsT zk9GI5Y7Hg1el6ls5CmAOWG3KEQogXq+VxCLLJh1WPbZot3hhar4syxzBTBex2gwuu ml4yuM2C5CyXGDH194T4MHy1bI6JxAeIUuo9q1qo=
Content-Type: multipart/alternative; boundary="Apple-Mail=_40CF782C-EDCE-4688-9CEC-CB52144A3A79"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Olaf Kolkman <olaf@NLnetLabs.nl>
In-Reply-To: <51864888.8080802@gmx.net>
Date: Mon, 6 May 2013 04:35:04 -0400
Message-Id: <CF914474-0AEF-4196-9A24-10E042434D55@NLnetLabs.nl>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im> <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com> <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org> <51863677.7010807@cisco.com> <51864888.8080802@gmx.net>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (open.nlnetlabs.nl [213.154.224.1]); Mon, 06 May 2013 10:35:07 +0200 (CEST)
Cc: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 08:35:20 -0000

--Apple-Mail=_40CF782C-EDCE-4688-9CEC-CB52144A3A79
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On May 5, 2013, at 7:54 AM, Hannes Tschofenig =
<hannes.tschofenig@gmx.net> wrote:

> On 05/05/2013 01:37 PM, Benoit Claise wrote:
>> On 2/05/2013 18:17, Carsten Bormann wrote:
>>> On May 2, 2013, at 07:21, "Eggert, Lars" <lars@netapp.com> wrote:
>>>=20
>>>> Yeah, all kinds of issues, but if we created a new thing here in
>>>> between WGLC and PS, the broader industry would never understand.
>>> That is a matter of naming and marketing ("candidate RFC"?).
>> There is already some misconception between I-RFC and Standards =
Tracks RFC.
>> I don't believe that adding a new name/category would help: instead =
it
>> would add to the confusion.
>>=20
>> Regards, Benoit
>=20
> Interesting that you mention this.
>=20
> A note from a recent experience: Together with Olaf we are =
participating in a European Multistakeholder Platform for ICT =
standardization, see =
http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=3DOJ:C:2011:349:0004=
:0006:EN:PDF
>=20
> The aim of this group is to find out how to reference IETF RFC (and =
standards from other organizations, like the W3C) since the European =
Commission seems to be unable to just reference standards beyond a small =
set of organizations (such as ETSI).
>=20
> As you can imagine, the different types of RFCs are not that easy to =
understand for those who do not participate actively in the IETF. =
Getting others to understand the different streams, the various document =
types and different standards is already difficult and maybe there is =
room for simplification here.

FWIW.

I think the difference between Informational and Standards track is =
fairly easily explained (in that context), having all the information in =
the headers and boilerplates helps. Where things become difficult is at =
the point where the maintenance of our standards need to be explained =
and questions about progression on the standards ladder get asked.=20

Personally I hope that RFC 6410 has the effect that we, as a community, =
get serious about promoting our proposed standards, or obsolete them.=20

I wonder how many standards got promoted after 6410 was published.

--Olaf








--Apple-Mail=_40CF782C-EDCE-4688-9CEC-CB52144A3A79
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 May 5, 2013, at 7:54 AM, Hannes Tschofenig &lt;<a =
href=3D"mailto:hannes.tschofenig@gmx.net">hannes.tschofenig@gmx.net</a>&gt=
; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><span style=3D"font-family: Monaco; 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; display: inline !important; float: none; =
">On 05/05/2013 01:37 PM, Benoit Claise wrote:</span><br =
style=3D"font-family: Monaco; 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; =
"><blockquote type=3D"cite" style=3D"font-family: Monaco; 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; ">On 2/05/2013 18:17, Carsten Bormann =
wrote:<br><blockquote type=3D"cite">On May 2, 2013, at 07:21, "Eggert, =
Lars" &lt;<a href=3D"mailto:lars@netapp.com">lars@netapp.com</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">Yeah, all kinds of issues, but =
if we created a new thing here in<br>between WGLC and PS, the broader =
industry would never understand.<br></blockquote>That is a matter of =
naming and marketing ("candidate RFC"?).<br></blockquote>There is =
already some misconception between I-RFC and Standards Tracks RFC.<br>I =
don't believe that adding a new name/category would help: instead =
it<br>would add to the confusion.<br><br>Regards, =
Benoit<br></blockquote><br style=3D"font-family: Monaco; 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; "><span style=3D"font-family: Monaco; =
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; display: =
inline !important; float: none; ">Interesting that you mention =
this.</span><br style=3D"font-family: Monaco; 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 style=3D"font-family: Monaco; =
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; "><span =
style=3D"font-family: Monaco; 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; =
display: inline !important; float: none; ">A note from a recent =
experience: Together with Olaf we are participating in a European =
Multistakeholder Platform for ICT standardization, see<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=3DOJ:C:2011:=
349:0004:0006:EN:PDF" style=3D"font-family: Monaco; 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; =
">http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=3DOJ:C:2011:349:00=
04:0006:EN:PDF</a><br style=3D"font-family: Monaco; 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 style=3D"font-family: Monaco; =
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; "><span =
style=3D"font-family: Monaco; 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; =
display: inline !important; float: none; ">The aim of this group is to =
find out how to reference IETF RFC (and standards from other =
organizations, like the W3C) since the European Commission seems to be =
unable to just reference standards beyond a small set of organizations =
(such as ETSI).</span><br style=3D"font-family: Monaco; 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 style=3D"font-family: Monaco; =
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; "><span =
style=3D"font-family: Monaco; 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; =
display: inline !important; float: none; ">As you can imagine, the =
different types of RFCs are not that easy to understand for those who do =
not participate actively in the IETF. Getting others to understand the =
different streams, the various document types and different standards is =
already difficult and maybe there is room for simplification =
here.</span></blockquote><br></div><div>FWIW.</div><div><br></div><div>I =
think the difference between Informational and Standards track is fairly =
easily explained (in that context), having all the information in the =
headers and boilerplates helps. Where things become difficult is at the =
point where the maintenance of our standards need to be explained and =
questions about progression on the standards ladder get =
asked.&nbsp;</div><div><br></div><div>Personally I hope that RFC 6410 =
has the effect that we, as a community, get serious about promoting our =
proposed standards, or obsolete them.&nbsp;</div><div><br></div><div>I =
wonder how many standards got promoted after 6410 was =
published.</div><div><br></div><div>--Olaf</div><div><br></div><div><br></=
div><div><br></div><div><br></div><div><br></div><div><br></div><br></body=
></html>=

--Apple-Mail=_40CF782C-EDCE-4688-9CEC-CB52144A3A79--

From andy@yumaworks.com  Fri May  3 11:34:08 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0A621F8E34 for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level: 
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[AWL=1.899,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kyIEA3rwDNZM for <ietf@ietfa.amsl.com>; Fri,  3 May 2013 11:34:07 -0700 (PDT)
Received: from mail-ia0-x231.google.com (mail-ia0-x231.google.com [IPv6:2607:f8b0:4001:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0777821F8518 for <ietf@ietf.org>; Fri,  3 May 2013 11:34:06 -0700 (PDT)
Received: by mail-ia0-f177.google.com with SMTP id m10so1543561iam.8 for <ietf@ietf.org>; Fri, 03 May 2013 11:34:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=E7jTaPp0lXqq3T7r+L+7SqoZR3HTG8QPLYVRrmQccCU=; b=kBYc0+tla9eZatGy5GJR3HxFQ52aS83fX0A0vPm2zzROxXyJ0Pa3ouSJfjhwjiSJja dhrkyVt+JepGvKdgq9BZJtOBs7eEe6JEnM0NDPaU8eMXS8yVCXMbqVOmfMLKmvTzIeVw QigxunpmisyhmekSkTZbdWGnt0v8uSeLsHcJE9lAmLuXf4bZxaQu8Q1/dacwWuRRNu1f sJzfYW65JYIHw58uRh5cxvQtIV6N1Wq6rn/7hPTmfskqWfX3AYZakIUV1r3NyLHevqkU UPbGkXUBCr4vbB/NSHYu04GQ+8oV3GDXDB1481K01EqQXNEi/ru+lv6YC+Ac7bXNOZe+ WkTQ==
MIME-Version: 1.0
X-Received: by 10.50.29.82 with SMTP id i18mr5511105igh.86.1367606046320; Fri, 03 May 2013 11:34:06 -0700 (PDT)
Received: by 10.231.125.202 with HTTP; Fri, 3 May 2013 11:34:06 -0700 (PDT)
In-Reply-To: <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
Date: Fri, 3 May 2013 11:34:06 -0700
Message-ID: <CABCOCHTcq_CBO9FGtB6BB3zVYXjQuunVLKFwdup273w2R96fmA@mail.gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
From: Andy Bierman <andy@yumaworks.com>
To: adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary=047d7bd6c628957aef04dbd49809
X-Gm-Message-State: ALoCoQnXHlbbwCAP0TEBVUVOMAQgPEwCZ3e4wm2KLkd4AneetLSmuy8TETrwX1iupmQNEj2S+BQV
X-Mailman-Approved-At: Mon, 06 May 2013 07:05:44 -0700
Cc: Thomas Narten <narten@us.ibm.com>, 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: Fri, 03 May 2013 18:34:08 -0000

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

..

> WG chairs might like to comment, but I suspect that one lunchtime training
> session every four months does not constitute proactive management.
>
>
+1 !!!

It works on down the line too.
WG Chairs meeting with I-D editors once every 4 months isn't so great
either.

If the total time has gone up 100 days, and the IESG time has gone down
100 days, then clearly the WG process is the main problem.

I'd like to see some stats on average delta between revisions of an I-D,
with some metric for the number of changes per revision.  I suspect
it would show way too many drafts that have a few edits once every
4 months. (One of mine right now even ;-)

The WG Chairs need more training on how to avoid the "slow tweak mode"
problem. The ADs need to manage their WG chairs so this doesn't happen.


Adrian
>
>
Andy

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

..<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
WG chairs might like to comment, but I suspect that one lunchtime training<=
br>
session every four months does not constitute proactive management.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>+1 !!!</div><div><br></div><div>It works on down the=
 line too.</div><div>WG Chairs meeting with I-D editors once every 4 months=
 isn&#39;t so great either.</div>
<div><br></div><div>If the total time has gone up 100 days, and the IESG ti=
me has gone down</div><div>100 days, then clearly the WG process is the mai=
n problem.</div><div><br></div><div>I&#39;d like to see some stats on avera=
ge delta between revisions of an I-D,</div>
<div>with some metric for the number of changes per revision. =A0I suspect<=
/div><div>it would show way too many drafts that have a few edits once ever=
y</div><div>4 months. (One of mine right now even ;-)</div><div><br></div>
<div>The WG Chairs need more training on how to avoid the &quot;slow tweak =
mode&quot;</div><div>problem. The ADs need to manage their WG chairs so thi=
s doesn&#39;t happen.</div><div><br></div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888">
Adrian<br>
<br>
</font></span></blockquote></div><br><div>Andy</div><div><br></div>

--047d7bd6c628957aef04dbd49809--

From mohamed.boucadair@orange.com  Mon May  6 01:03:08 2013
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E09821F8EEC; Mon,  6 May 2013 01:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.248
X-Spam-Level: 
X-Spam-Status: No, score=-2.248 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vbPB6HRThSQk; Mon,  6 May 2013 01:02:57 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by ietfa.amsl.com (Postfix) with ESMTP id A216921F8952; Mon,  6 May 2013 01:02:56 -0700 (PDT)
Received: from omfedm08.si.francetelecom.fr (unknown [xx.xx.xx.4]) by omfedm11.si.francetelecom.fr (ESMTP service) with ESMTP id 37FD93B424A; Mon,  6 May 2013 10:02:55 +0200 (CEST)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfedm08.si.francetelecom.fr (ESMTP service) with ESMTP id 14F5F23804B; Mon,  6 May 2013 10:02:55 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Mon, 6 May 2013 10:02:55 +0200
From: <mohamed.boucadair@orange.com>
To: Robert Sparks <rjsparks@nostrum.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, General Area Review Team <gen-art@ietf.org>,  "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@tools.ietf.org>
Date: Mon, 6 May 2013 10:02:53 +0200
Subject: RE: [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Topic: [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
Thread-Index: Ac5ClKF6HmqJ6RojQf+w5CK04H/aHwHmyPIg
Message-ID: <94C682931C08B048B7A8645303FDC9F36ECC240570@PUEXCB1B.nanterre.francetelecom.fr>
References: <517AA051.8080506@nostrum.com>
In-Reply-To: <517AA051.8080506@nostrum.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36ECC240570PUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2013.5.6.65415
X-Mailman-Approved-At: Mon, 06 May 2013 07:05:44 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 08:03:08 -0000

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

Dear Robert,

I updated the document to cover the comments you raised. You can check the =
diff available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-trigge=
red-reconfigure-06

Cheers,
Med

De : dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] De la part de R=
obert Sparks
Envoy=E9 : vendredi 26 avril 2013 17:42
=C0 : dhcwg@ietf.org; ietf@ietf.org; General Area Review Team; draft-ietf-d=
hc-triggered-reconfigure@tools.ietf.org
Objet : [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05

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><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-triggered-reconfigure-05
Reviewer:  Robert Sparks
Review Date: April 26, 2013
IETF LC End Date: May 6, 2013
IESG Telechat date: May 16, 2013

Summary: This draft is on the right track but has open issues, described in
      the review.

Major issues:

Overall, this document is solid, but I think there is a bug in section 6.3.
I could be wrong, but If I'm right, this paragraph:
When retransmission is required, the relay may decide to correct the conten=
t of RECONFIGURE-REQUEST message it issues (e.g., update the Client Identif=
ier list).  This decision is local to the relay (e.g., it may be based on o=
bserved events such as one or more clients were reconfigured on their own).

introduces a race-condition that could lead to an erroneous state. If a rel=
ay's first message included client A, then the retransmission included clie=
nts A and B, but that retransmission crosses with a success RECONFIGURE-REP=
LY to the request that only included client A, the relay will think it succ=
eeded in asking A and B to be reconfigured.

Minor issues:

This sentence:
Furthermore, means to recover state in failure events must be supported, bu=
t are not discussed in this document.
places a requirement on a relay (even though it's not using a 2119 MUST). I=
s there some other document that defines this requirement that you can refe=
rence? If not, the requirement should be discussed in this document. Altern=
atively, you could change the sentence to talk about the consequences of no=
t having a proprietary means for recovering state.

Nits/editorial comments:

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 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 bgcolor=3Dwhite lang=3DFR li=
nk=3Dblue vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><sp=
an style=3D'font-size:10.0pt;font-family:"Courier New";color:#1F497D'>Dear =
Robert,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Courier New";color:#1F497D'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt;font-fam=
ily:"Courier New";color:#1F497D'>I updated the document to cover the commen=
ts you raised. You can check the diff available at: </span><a href=3D"http:=
//www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-triggered-reconfigure-06"><spa=
n lang=3DEN-US>http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dhc-triggered-=
reconfigure-06</span></a><span lang=3DEN-US><o:p></o:p></span></p><p class=
=3DMsoNormal><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Cour=
ier New";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><s=
pan lang=3DEN-US style=3D'font-size:10.0pt;font-family:"Courier New";color:=
#1F497D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-=
US style=3D'font-size:10.0pt;font-family:"Courier New";color:#1F497D'>Med<o=
:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'font-s=
ize:10.0pt;font-family:"Courier New";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;p=
adding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>De=
&nbsp;:</span></b><span lang=3DEN-US style=3D'font-size:10.0pt;font-family:=
"Tahoma","sans-serif";color:windowtext'> dhcwg-bounces@ietf.org [mailto:dhc=
wg-bounces@ietf.org] <b>De la part de</b> Robert Sparks<br><b>Envoy=E9&nbsp=
;:</b> vendredi 26 avril 2013 17:42<br><b>=C0&nbsp;:</b> dhcwg@ietf.org; ie=
tf@ietf.org; General Area Review Team; draft-ietf-dhc-triggered-reconfigure=
@tools.ietf.org<br><b>Objet&nbsp;:</b> [dhcwg] Gen-art review: draft-ietf-d=
hc-triggered-reconfigure-05<o:p></o:p></span></p></div></div><p class=3DMso=
Normal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>I am the assigned Gen-ART reviewer for this =
draft. For background on <br>Gen-ART, please see the FAQ at <br><br><a href=
=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wik=
i.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>. <br><br>Please resol=
ve these comments along with any other Last Call comments <br>you may recei=
ve. <br><br>Document: draft-ietf-dhc-triggered-reconfigure-05<br>Reviewer:&=
nbsp; Robert Sparks<br>Review Date: April 26, 2013<br>IETF LC End Date: May=
 6, 2013<br>IESG Telechat date: May 16, 2013<br><br>Summary: This draft is =
on the right track but has open issues, described in<br>&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp; the review.<br><br>Major issues: <br><br>Overall, this document=
 is solid, but I think there is a bug in section 6.3. <br>I could be wrong,=
 but If I'm right, this paragraph:<o:p></o:p></p><p class=3DMsoNormal>When =
retransmission is required, the relay may decide to correct the content of =
RECONFIGURE-REQUEST message it issues (e.g., update the Client Identifier l=
ist).&nbsp; This decision is local to the relay (e.g., it may be based on o=
bserved events such as one or more clients were reconfigured on their own).=
<o:p></o:p></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>intr=
oduces a race-condition that could lead to an erroneous state. If a relay's=
 first message included client A, then the retransmission included clients =
A and B, but that retransmission crosses with a success RECONFIGURE-REPLY t=
o the request that only included client A, the relay will think it succeede=
d in asking A and B to be reconfigured.<br><br>Minor issues: <br><br>This s=
entence:<o:p></o:p></p><p class=3DMsoNormal>Furthermore, means to recover s=
tate in failure events must be supported, but are not discussed in this doc=
ument.<o:p></o:p></p><p class=3DMsoNormal>places a requirement on a relay (=
even though it's not using a 2119 MUST). Is there some other document that =
defines this requirement that you can reference? If not, the requirement sh=
ould be discussed in this document. Alternatively, you could change the sen=
tence to talk about the consequences of not having a proprietary means for =
recovering state.<br><br>Nits/editorial comments: <o:p></o:p></p></div></di=
v></body></html>=

--_000_94C682931C08B048B7A8645303FDC9F36ECC240570PUEXCB1Bnante_--

From l.wood@surrey.ac.uk  Mon May  6 07:13:46 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A7421F900C for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 07:13:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wro6UXqMhn8R for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 07:13:32 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7F57521F9223 for <ietf@ietf.org>; Mon,  6 May 2013 07:13:31 -0700 (PDT)
Received: from [195.245.230.131:6154] by server-15.bemta-3.messagelabs.com id CF/EF-32363-08AB7815; Mon, 06 May 2013 14:13:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-78.messagelabs.com!1367849599!30521567!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.8.6.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14808 invoked from network); 6 May 2013 14:13:20 -0000
Received: from unknown (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-15.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 6 May 2013 14:13:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Mon, 6 May 2013 15:13:19 +0100
From: <l.wood@surrey.ac.uk>
To: <john-ietf@jck.com>, <brian.e.carpenter@gmail.com>, <yaronf.ietf@gmail.com>
Date: Mon, 6 May 2013 15:10:40 +0100
Subject: RE: Language editing
Thread-Topic: Language editing
Thread-Index: Ac5JvvcVmbW2CJhxR+Ws0F+Bqs2XiAApIZKM
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com>	<5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu>	<51842A94.6060505@gmail.com> <51843485.90802@gmail.com>,<D80C0D989A6138451CD9F852@[192.168.1.128]>
In-Reply-To: <D80C0D989A6138451CD9F852@[192.168.1.128]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 14:13:46 -0000

http://labs.apnic.net/blabs/?p=3D309

an excellent detective story on badly-written, poorly edited, standards tra=
ck RFCs leading to interop problems. Enjoy.

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

Technical writer and editor, native English speaker, IELTS score of 9.0, va=
guely appalled by this discussion.


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of John C Kle=
nsin [john-ietf@jck.com]
Sent: 05 May 2013 19:32
To: Brian E Carpenter; Yaron Sheffer
Cc: ietf@ietf.org
Subject: Re: Language editing

--On Saturday, May 04, 2013 10:04 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 04/05/2013 09:22, Yaron Sheffer wrote:
>> GEN-ART is a good example, but actual document editing is
>> much more work and arguably, less rewarding than a review. So
>> I think this can only succeed with professional (=3Dpaid)
>> editors.
>
> I think I disagree, if we can find the knack of effective
> crowd-sourcing. We do after all have several hundred native
> English speakers active in the IETF, which would mean each one
> would have to volunteer for less than one draft per year and
> we'd be done.

And what we have found more times than I care to think about --
and I've found even more times than that when trying to read
undergraduate papers -- is that "native English speaker" does
not imply "ability to write good, clear, coherent technical
English".  In addition, the IETF includes a reasonable number of
people whose first language is not English but whose ability to
write high-quality technical documents in English generally
exceeds that of our typical native speaker.   So my first
concern is that we not start making plans based on the
population of native speakers -- if we are going to find
volunteers to pretend to be technical editors, or assess the
population of such people, we had better base our assumptions on
the right set of skills.

> I don't know how much experience you have with professional
> editors. Apart from the RFC Editor crew, my experience has
> been "mixed". Somebody a year or three ago (the last time we
> had this exact same discussion) pointed out the differences
> between copy-editors and technical editors. One difference is
> that the latter are much more expensive. Copy-editors tend to
> be rule-driven; technical editors are supposed to understand
> the material.

To be a little more precise, technical editors are supposed to
understand the nature of technical documents, to have good
intuitions about what is clear and precise and what isn't, and
so on.  Specific subject-matter expertise is yet another layer
of requirement and something we would be unlikely to find far
outside the relevant WG or Area.  I think the distinction
between copy editors and technical editors is very significant
(and I might have been the one who made the comment to which you
refer).  But one should not confuse that distinction with the
observation that there are probably as large a proportion of
poor editors who can't deal with material that requires some
skill (in either subcategory) in the world as there are poor
engineers who can't competently handle actual systems design
issues.

Having shepherded (and kicked, clawed, and dragged) a number of
documents through the system in the last few years that were
written by people whose engineering and protocol design skills
far exceeded their [English] technical writing skills, I'm less
optimistic about volunteer editing than several others seem to
be.  If a WG has surplus people with good technical editing
skills to pair with authors who may be better about the
technical details or tracking the WG discussions and getting
them into to document, then that is great.  But I have certainly
worked in or chaired WGs when there are no such people to spare
or who will volunteer.  In addition, it is really hard for
someone who cares enough about the subject matter of the WG to
be able to edit or translate a draft into good, clear, technical
English without injecting their own opinions about areas where
the original I-D may be unclear -- perhaps it is even harder
than writing the document with careful attention to WG consensus.

My guess is that we are going to need a mixed strategy that
involves volunteer (and adequately skilled) editors where we can
find them, professional technical editors where necessary (and a
good model for how they get paid), and oversight of the whole
process by the RFC Editor as well as relevant WG Chairs, ADs,
and the IESG.  We are also going to need to be much more clear
about what level of quality we, as a community (not just the
IESG), want and will insist on before a document goes into Last
Call.

I've always hoped that the standard could be "absolutely clear
about what is being specified, but everything else can be fixed
by the RFC Editor after approval".  But that requirement is more
easily stated that interpreted and used: I've seen text in
documents that I thought were that good nit-picked by the IESG
and edited by large committees and, with other documents, not
fixed (or even made worse) by the RFC Editor.

There are probably no easy and comprehensive solutions or magic
bullets.

   john
>
>     Brian




From rjsparks@nostrum.com  Mon May  6 09:09:47 2013
Return-Path: <rjsparks@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 2D2CC21F8FF5; Mon,  6 May 2013 09:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NceC5ZgUTWW0; Mon,  6 May 2013 09:09:46 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id D402121F8F12; Mon,  6 May 2013 09:09:45 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-079-070.mycingular.net [166.147.79.70]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r46G9fvr027267 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Mon, 6 May 2013 11:09:45 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <5187D5C8.5000902@nostrum.com>
Date: Mon, 06 May 2013 11:09:44 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: mohamed.boucadair@orange.com
Subject: Re: [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
References: <517AA051.8080506@nostrum.com> <94C682931C08B048B7A8645303FDC9F36ECC240570@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36ECC240570@PUEXCB1B.nanterre.francetelecom.fr>
Content-Type: multipart/alternative; boundary="------------010407040103010500050401"
Received-SPF: pass (shaman.nostrum.com: 166.147.79.70 is authenticated by a trusted mechanism)
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, General Area Review Team <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-triggered-reconfigure@tools.ietf.org" <draft-ietf-dhc-triggered-reconfigure@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, 06 May 2013 16:09:47 -0000

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

Looks good to me. Thanks!
RjS

On 5/6/13 3:02 AM, mohamed.boucadair@orange.com wrote:
>
> Dear Robert,
>
> I updated the document to cover the comments you raised. You can check 
> the diff available at: 
> http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-triggered-reconfigure-06
>
> Cheers,
>
> Med
>
> *De :*dhcwg-bounces@ietf.org [mailto:dhcwg-bounces@ietf.org] *De la 
> part de* Robert Sparks
> *Envoyé :* vendredi 26 avril 2013 17:42
> *À :* dhcwg@ietf.org; ietf@ietf.org; General Area Review Team; 
> draft-ietf-dhc-triggered-reconfigure@tools.ietf.org
> *Objet :* [dhcwg] Gen-art review: draft-ietf-dhc-triggered-reconfigure-05
>
> 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> 
> <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-triggered-reconfigure-05
> Reviewer:  Robert Sparks
> Review Date: April 26, 2013
> IETF LC End Date: May 6, 2013
> IESG Telechat date: May 16, 2013
>
> Summary: This draft is on the right track but has open issues, 
> described in
>       the review.
>
> Major issues:
>
> Overall, this document is solid, but I think there is a bug in section 
> 6.3.
> I could be wrong, but If I'm right, this paragraph:
>
> When retransmission is required, the relay may decide to correct the 
> content of RECONFIGURE-REQUEST message it issues (e.g., update the 
> Client Identifier list).  This decision is local to the relay (e.g., 
> it may be based on observed events such as one or more clients were 
> reconfigured on their own).
>
>
> introduces a race-condition that could lead to an erroneous state. If 
> a relay's first message included client A, then the retransmission 
> included clients A and B, but that retransmission crosses with a 
> success RECONFIGURE-REPLY to the request that only included client A, 
> the relay will think it succeeded in asking A and B to be reconfigured.
>
> Minor issues:
>
> This sentence:
>
> Furthermore, means to recover state in failure events must be 
> supported, but are not discussed in this document.
>
> places a requirement on a relay (even though it's not using a 2119 
> MUST). Is there some other document that defines this requirement that 
> you can reference? If not, the requirement should be discussed in this 
> document. Alternatively, you could change the sentence to talk about 
> the consequences of not having a proprietary means for recovering state.
>
> Nits/editorial comments:
>


--------------010407040103010500050401
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">Looks good to me. Thanks!<br>
      RjS<br>
      <br>
      On 5/6/13 3:02 AM, <a class="moz-txt-link-abbreviated" href="mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a> wrote:<br>
    </div>
    <blockquote
cite="mid:94C682931C08B048B7A8645303FDC9F36ECC240570@PUEXCB1B.nanterre.francetelecom.fr"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
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:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:"Courier New";
	mso-fareast-language:EN-US;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D">Dear Robert,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D" lang="EN-US">I updated the document
            to cover the comments you raised. You can check the diff
            available at: </span><a moz-do-not-send="true"
href="http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-triggered-reconfigure-06"><span
              lang="EN-US">http://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-triggered-reconfigure-06</span></a><span
            lang="EN-US"><o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D" lang="EN-US">Cheers,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D" lang="EN-US">Med<o:p></o:p></span></p>
        <p class="MsoNormal"><span
            style="font-size:10.0pt;font-family:&quot;Courier
            New&quot;;color:#1F497D" lang="EN-US"><o:p>&nbsp;</o:p></span></p>
        <div style="border:none;border-left:solid blue 1.5pt;padding:0cm
          0cm 0cm 4.0pt">
          <div>
            <div style="border:none;border-top:solid #B5C4DF
              1.0pt;padding:3.0pt 0cm 0cm 0cm">
              <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext"
                    lang="EN-US">De&nbsp;:</span></b><span
style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:windowtext"
                  lang="EN-US"> <a class="moz-txt-link-abbreviated" href="mailto:dhcwg-bounces@ietf.org">dhcwg-bounces@ietf.org</a>
                  [<a class="moz-txt-link-freetext" href="mailto:dhcwg-bounces@ietf.org">mailto:dhcwg-bounces@ietf.org</a>] <b>De la part de</b>
                  Robert Sparks<br>
                  <b>Envoy&eacute;&nbsp;:</b> vendredi 26 avril 2013 17:42<br>
                  <b>&Agrave;&nbsp;:</b> <a class="moz-txt-link-abbreviated" href="mailto:dhcwg@ietf.org">dhcwg@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; General Area
                  Review Team;
                  <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-dhc-triggered-reconfigure@tools.ietf.org">draft-ietf-dhc-triggered-reconfigure@tools.ietf.org</a><br>
                  <b>Objet&nbsp;:</b> [dhcwg] Gen-art review:
                  draft-ietf-dhc-triggered-reconfigure-05<o:p></o:p></span></p>
            </div>
          </div>
          <p class="MsoNormal"><span lang="EN-US"><o:p>&nbsp;</o:p></span></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt">I am the
            assigned Gen-ART reviewer for this draft. For background on
            <br>
            Gen-ART, please see the FAQ at <br>
            <br>
            <a moz-do-not-send="true"
              href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.
            <br>
            <br>
            Please resolve these comments along with any other Last Call
            comments <br>
            you may receive. <br>
            <br>
            Document: draft-ietf-dhc-triggered-reconfigure-05<br>
            Reviewer:&nbsp; Robert Sparks<br>
            Review Date: April 26, 2013<br>
            IETF LC End Date: May 6, 2013<br>
            IESG Telechat date: May 16, 2013<br>
            <br>
            Summary: This draft is on the right track but has open
            issues, described in<br>
            &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the review.<br>
            <br>
            Major issues: <br>
            <br>
            Overall, this document is solid, but I think there is a bug
            in section 6.3. <br>
            I could be wrong, but If I'm right, this paragraph:<o:p></o:p></p>
          <p class="MsoNormal">When retransmission is required, the
            relay may decide to correct the content of
            RECONFIGURE-REQUEST message it issues (e.g., update the
            Client Identifier list).&nbsp; This decision is local to the
            relay (e.g., it may be based on observed events such as one
            or more clients were reconfigured on their own).<o:p></o:p></p>
          <p class="MsoNormal" style="margin-bottom:12.0pt"><br>
            introduces a race-condition that could lead to an erroneous
            state. If a relay's first message included client A, then
            the retransmission included clients A and B, but that
            retransmission crosses with a success RECONFIGURE-REPLY to
            the request that only included client A, the relay will
            think it succeeded in asking A and B to be reconfigured.<br>
            <br>
            Minor issues: <br>
            <br>
            This sentence:<o:p></o:p></p>
          <p class="MsoNormal">Furthermore, means to recover state in
            failure events must be supported, but are not discussed in
            this document.<o:p></o:p></p>
          <p class="MsoNormal">places a requirement on a relay (even
            though it's not using a 2119 MUST). Is there some other
            document that defines this requirement that you can
            reference? If not, the requirement should be discussed in
            this document. Alternatively, you could change the sentence
            to talk about the consequences of not having a proprietary
            means for recovering state.<br>
            <br>
            Nits/editorial comments: <o:p></o:p></p>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------010407040103010500050401--

From tjc@ecs.soton.ac.uk  Mon May  6 09:26:51 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 059BD21F860B; Mon,  6 May 2013 09:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MM2Kv4sCixzj; Mon,  6 May 2013 09:26:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 7328A21F859B; Mon,  6 May 2013 09:26:49 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r46GQXx2031601;  Mon, 6 May 2013 17:26:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r46GQXx2031601
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1367857594; bh=a4l+aSSARNwGz2AqrW5G4eZdHFM=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=L82Xa2K/Kwfl4zOPNpitfsUTWpEkGMuBe5kK7NKyVoWWPWRwqcB1T/6mizDZyWsKB mXLdjfWP5Qi8+e6PaZH763lxFVvGf7/i7cVK4OZKVyDE/SVQqvc8aqkcu3fcSNYh+H /Br4D/UEvQ85KDwBdpY3AjzBzu3TChsOxf9N8LEY=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p45HQX0430647178yw ret-id none; Mon, 06 May 2013 17:26:33 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r46GPCHe011521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 6 May 2013 17:25:13 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [renum] Gen-art review: draft-ietf-6renum-gap-analysis-05.txt
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <517FE691.2070707@bogus.com>
Date: Mon, 6 May 2013 17:25:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|8d29bcd8f9cb5293eee024b76facd925p45HQX03tjc|ecs.soton.ac.uk|1F756E4B-5011-4B49-AB77-F4D51BC20E94@ecs.soton.ac.uk>
References: <5159F239.1060001@nostrum.com>	<8AE0F17B87264D4CAC7DE0AA6C406F453D6ED6C3@nkgeml506-mbx.china.huawei.com>	<515AABB5.5050202@gmail.com> <517FE44C.7000609@nostrum.com> <517FE691.2070707@bogus.com> <1F756E4B-5011-4B49-AB77-F4D51BC20E94@ecs.soton.ac.uk>
To: joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p45HQX043064717800; tid=p45HQX0430647178yw; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=8:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r46GQXx2031601
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@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, 06 May 2013 16:26:52 -0000

On 30 Apr 2013, at 16:43, joel jaeggli <joelja@bogus.com> wrote:

> On 4/30/13 8:33 AM, Robert Sparks wrote:
>> On 4/2/13 4:58 AM, Brian E Carpenter wrote:
>>> Just picking a couple of points for further comment:
>>>=20
>>> On 02/04/2013 08:46, Liubing (Leo) wrote:
>>>>=20
>>>> [Bing] draft-chown-v6ops-renumber-thinkabout is an important input =
for the gap analysis. Although the draft is expired, most of the content =
are still valid.
>>>> draft-chown is a more comprehensive analysis, while the gap draft =
is focusing on gaps in enterprise renumbering. So it might not easy to =
abstract several points as important from draft-chown to this draft. We =
actually encourage people to read it.
>>> Robert is right, though, sending people to a long-expired draft is a =
bad idea.
> I'm not sure I see that as worse than referring to Wikipedia, an =
expired draft has the property that it's not going to change. I have no =
problem with the idea that it would be an informative reference.   but =
yes it's a bit much to say go read this.
>>> Of course we have to acknowledge it, but maybe we should pull some =
of its text
>>> into an Appendix.
>>>=20
>>> Tim Chown, any opinion?
>> The most recent version (and the one slated for the next telechat) =
still has this long-expired draft referenced.


Hi,

The old renumbering "thinkabout" draft came out of experiments on IPv6 =
renumbering we did in 6NET some 10 (yikes!) years ago, for both =
enterprise and ISP networks. I think most of what was written is still =
applicable.  Brian borrowed a fair deal of it for RFC 5887.  I stopped =
work on it as there was little/no interest in the problem in v6ops at =
the time (or whatever v6ops was called back then). We produced technical =
6NET reports separately, and did some follow-up work with Cisco =
separately.

Personally I don't mind if the principles are mentioned without the =
explicit reference - an ack in the Acknowledgements is adequate.=20

It would be interesting to review the "thinkabout" draft to see how much =
still holds true.  Glancing at it, sections like "Application and =
Service-Oriented Issues" are still very much relevant. I guess Stig and =
I could consider advancing it along the Independent Submission path, or =
look for publication to an appropriate journal.  Life is short :)

Tim


From worley@shell01.TheWorld.com  Mon May  6 11:01:11 2013
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 8371F21F92F4 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 11:01:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.432
X-Spam-Level: 
X-Spam-Status: No, score=-1.432 tagged_above=-999 required=5 tests=[AWL=1.548,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfyJSMkwBVdr for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 11:01:05 -0700 (PDT)
Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id 9935D21F92EC for <ietf@ietf.org>; Mon,  6 May 2013 11:01:05 -0700 (PDT)
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 r46I10kj021338; Mon, 6 May 2013 14:01:02 -0400
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 r46I10f44234010; Mon, 6 May 2013 14:01:00 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r46I10Xc4258883; Mon, 6 May 2013 14:01:00 -0400 (EDT)
Date: Mon, 6 May 2013 14:01:00 -0400 (EDT)
Message-Id: <201305061801.r46I10Xc4258883@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-reply-to: <51843485.90802@gmail.com> (brian.e.carpenter@gmail.com)
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org>	<5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org>	<51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.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: Mon, 06 May 2013 18:01:11 -0000

> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> 
> On 04/05/2013 09:22, Yaron Sheffer wrote:
> > GEN-ART is a good example, but actual document editing is much more work
> > and arguably, less rewarding than a review. So I think this can only
> > succeed with professional (=paid) editors.
> 
> I think I disagree, if we can find the knack of effective crowd-sourcing.
> We do after all have several hundred native English speakers active
> in the IETF, which would mean each one would have to volunteer for
> less than one draft per year and we'd be done.
> 
> I don't know how much experience you have with professional editors.
> Apart from the RFC Editor crew, my experience has been "mixed". Somebody
> a year or three ago (the last time we had this exact same discussion)
> pointed out the differences between copy-editors and technical editors.
> One difference is that the latter are much more expensive. Copy-editors
> tend to be rule-driven; technical editors are supposed to understand
> the material.

In a sense you're right; if we could find sufficient members who are
good at editing technical English and motivate them to do so, then the
problem would be solved.  However, I don't see any of those conditions
becoming true.  As an organization, we don't place much value on
making the *words* of a document clear and correct, and neither do our
employers.  And relatively few engineers can write high-quality
English specifications.

More subtly, our process works against us, because we use technical
contributors as the document editors.  Improving writing is a matter
of zillions of relatively small changes, which is inefficient to do if
the person weilding the pen isn't the person who is working out the
corrections to the majority of the sentences in the document.

Dale

From brian.e.carpenter@gmail.com  Mon May  6 13:23:31 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4D9721F910D for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 13:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dRUlcEfhqMkS for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 13:23:30 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D004421F905C for <ietf@ietf.org>; Mon,  6 May 2013 13:23:30 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id uo1so2174174pbc.20 for <ietf@ietf.org>; Mon, 06 May 2013 13:23:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=X0mEqAk5ZPbPYZUQK5JRriKFZu6mjjEcKTdR7sZz7g8=; b=Sqw02SnfyaFdHcgs3guqZyIhJoEJQ2AWJw7HkWbma/vbou5DbudiEzDGP6xHtkg2Ca 8K1D+4UdgZy+hNabhII5JgNg7FuIKen6VXO2h2QLaXzehckWLrl/FGwc+OXAHlvtuDou HWSMgmusgzRELcq9m8emt6HJIfR+bcJ0FoD1yP4XG49iyFkAWdIytW92k1vXt47/+aPU x+jtJLt/VNq0w+2xdvwAh0D1/0dKrvpMs4L0IhIfyokl13n0xaJRZvlqh5XUmFiaUHw8 Iv0nfGxAZ330xkLPRO3G6efYf9f97nsxxxxNrKOoUO/hyq+kB+NHk81xfF9n3JpojhBG 9apA==
X-Received: by 10.66.149.5 with SMTP id tw5mr28486192pab.87.1367871810604; Mon, 06 May 2013 13:23:30 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id 10sm25082300pbr.45.2013.05.06.13.23.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 May 2013 13:23:29 -0700 (PDT)
Message-ID: <51881140.5070904@gmail.com>
Date: Tue, 07 May 2013 08:23:28 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org>	<5182DD64.7040205@gmail.com>	<5182E2A8.50800@acm.org>	<51839ABA.4010406@internet2.edu>	<51842A94.6060505@gmail.com>	<51843485.90802@gmail.com>, <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: john-ietf@jck.com, yaronf.ietf@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, 06 May 2013 20:23:31 -0000

On 07/05/2013 02:10, l.wood@surrey.ac.uk wrote:
> http://labs.apnic.net/blabs/?p=309
> 
> an excellent detective story on badly-written, poorly edited, standards track RFCs leading to interop problems. Enjoy.

I don't that is quite right. The problem in this case is not to do
with linguistic quality. It's due to a lack of formal verification
among a set of interacting and cross-area RFCs. (And the problem
is wider, because there are two distinct places in IETF standards
where ABNF for the text representation of IPv6 addresses can be
found.) This is a case where no amount of language editing would
have helped. Actually I used it a couple of months ago in a
discussion with some experts on formal verification, and they rather
liked it as a poster child for the need for formal methods in SDOs.

    Brian

From sm@resistor.net  Mon May  6 13:32:09 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66DD021F8F5C for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 13:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQSE3LDW3P4H for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 13:32:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 95CEA21F87D2 for <ietf@ietf.org>; Mon,  6 May 2013 13:32:08 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r46KW3MW023860; Mon, 6 May 2013 13:32:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367872327; bh=9tH2cB5JfzYv0jDkYZfjADjleSSUvWHjaAnZ1LhPxhc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SvMXXC1m17RUdEW5z4CRauzbkVi7z9eyKBE4aZ5ijSdqfa24r9I68L5UrOaS1+pFx fGyABxqrK1ClqifLv3eym6GUDCGnKOe8ZZB743h17Pk+zi86ba5w6rJql7Bsz82umq 0vZsp0so2qt3PHBNPvX0tWF8G0n/my9GMIz5jAfU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367872327; i=@resistor.net; bh=9tH2cB5JfzYv0jDkYZfjADjleSSUvWHjaAnZ1LhPxhc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SIZs21vRL3A0jVbr4pcWvEaq8L+bfgn2qJJrmE4mrj7pS27Bwut+eHTxeIS3h64dA CljAtiJe5lhAZKdYuzAFf3XpdCc2TiHHA2pa5TmN7Uy+yoinyDaxhUQRnUwWxXHU2r fNzFxhbp7AdmabaA09DliAdwcjHwydHUXc4SDKmU=
Message-Id: <6.2.5.6.2.20130506092257.0b91e3a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 06 May 2013 13:28:50 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: RE: call for ideas: tail-heavy IETF process
In-Reply-To: <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Andy Bierman <andy@yumaworks.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, 06 May 2013 20:32:09 -0000

At 07:20 03-05-2013, Adrian Farrel wrote:
>WG chairs might like to comment, but I suspect that one lunchtime training
>session every four months does not constitute proactive management.

One lunch every four months does not look like proactive management. :-)

At 11:34 03-05-2013, Andy Bierman wrote:
>WG Chairs meeting with I-D editors once every 4 months isn't so great either.

Yes.

>If the total time has gone up 100 days, and the IESG time has gone down
>100 days, then clearly the WG process is the main problem.

Yes.

I posted a message over a year ago ( 
http://www.ietf.org/mail-archive/web/urn/current/msg01653.html ).  I 
looked at the WG status page a few minutes ago.  The WG did not 
publish any document.  I looked at the mailing list archive.  There's 
hasn't been a lot of activity.

>The WG Chairs need more training on how to avoid the "slow tweak mode"
>problem. The ADs need to manage their WG chairs so this doesn't happen.

The choice is whether to shut down the working group or not.  It was 
suggested (other thread) that WG Chairs have to find at least X 
reviewers [1].  I doubt that anyone is going to pay these reviewers 
[2].  This raises the question of whether the people who showed 
interest in starting the work were a bunch of cheerleaders. :-)

The current mode of operation is:

   (i)   The IESG will fix that

   (ii)  The RFC Editor will fix that

   (iii) More tools will fix that

There isn't any hurdle to try reviews by Senior IETF Reviewers 
(SIRS).  As an experiment the SIRS could commit to post public 
reviews of every draft going through a Working Group Last Call (WGLC) 
until the end of the year.  I assume that a report of the experiment 
will be provided after that so that the IETF community can assess for 
itself whether the experiment was a success.

Regards,
-sm

1. http://www.asterix.com/galerie/smailix/images/i11c.gif
2. http://www.asterix.com/galerie/smailix/images/i8c.gif 


From john-ietf@jck.com  Mon May  6 15:14:11 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9777B21F9154 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:14:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2WuWeJc1BB-P for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:14:07 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 48D7C21F8825 for <ietf@ietf.org>; Mon,  6 May 2013 15:14:06 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZTfY-0006Hk-14; Mon, 06 May 2013 18:14:04 -0400
X-Vipre-Scanned: 00AA3F21002C3100AA406E-TDI
Date: Mon, 06 May 2013 18:14:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, l.wood@surrey.ac.uk
Subject: Re: Language editing
Message-ID: <1F9DA0977DABC51DA2EF9963@[192.168.1.128]>
In-Reply-To: <51881140.5070904@gmail.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com>	<5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu>	<51842A94.6060505@gmail.com> <51843485.90802@gmail.com> ,<D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@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: yaronf.ietf@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, 06 May 2013 22:14:11 -0000

--On Tuesday, May 07, 2013 08:23 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 07/05/2013 02:10, l.wood@surrey.ac.uk wrote:
>> http://labs.apnic.net/blabs/?p=309
>> 
>> an excellent detective story on badly-written, poorly edited,
>> standards track RFCs leading to interop problems. Enjoy.
> 
> I don't that is quite right. The problem in this case is not
> to do with linguistic quality. It's due to a lack of formal
> verification among a set of interacting and cross-area RFCs.
> (And the problem is wider, because there are two distinct
> places in IETF standards where ABNF for the text
> representation of IPv6 addresses can be found.) This is a case
> where no amount of language editing would have helped.
> Actually I used it a couple of months ago in a discussion with
> some experts on formal verification, and they rather liked it
> as a poster child for the need for formal methods in SDOs.

And that is another oddity and perhaps another lesson.  The
robustness principle was formulated, not just as a general good
idea, but because of the understanding that there was little or
no aspiration in pre-IETF specifications to get every T crossed
and I dotted.   That level of precision is required for formal
verification (about which there are other problems) or formal
testing and certification (about which there are a different set
of other problems).  Not only was Jon aware that we often didn't
go into that level of detail, but there was a case to be made
that we didn't want to because it took too much time to get
after the documents right after the design and specification
were done (please reread that a few times).

Maybe things have changed, but, if one actually believes the
robustness principle, then, in the case Geoff cites, Exchange is
simply non-conforming -- not because the spec prohibits
rejecting on the basis of a fine distinction about IPv6 formats,
but because doing so is unnecessary, inconsistent with the
robustness principle, and, arguably, plain silly.

And that is the other thing we lost when "Proposed Standard"
went from "spec that might contain some problems, lack of
clarity, and less than wonderful writing as long as there were
no known technical defects" to "better get it right because it
is probably the last chance and people are going to build and
ship products on the basis of what it says".

We now have expectations consistent with specs that can be
formally verified and/or tested and that people will interpret
narrowly and a procedural model designed for specs that are much
less formal and complete.

    john


   john


From sm@resistor.net  Mon May  6 15:15:43 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6444B21F87CD for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IBCsGNgMgcH3 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:15:42 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AB32921F871C for <ietf@ietf.org>; Mon,  6 May 2013 15:15:42 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r46MFWeR023146; Mon, 6 May 2013 15:15:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1367878537; bh=MGmvs3FsV0qJchG2T6VNLaEpMSAMMIcM7b5v0n7Fb/M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0PoevVg1KCtKv3xhkpEgvvJb1jNmSnC/tiXvxMSaLsUifrnbeStOyhR9Za+DuIok2 Qtz+JHas1Ou+qJawk+EuzIgarNl3h8tR+1wRAZl2mwdOaeSLePeWKnGJCiAeQX32xI mjpdr9sBPmv672w7W2lkZCPXKkHETzx6R7ls+5rU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1367878537; i=@resistor.net; bh=MGmvs3FsV0qJchG2T6VNLaEpMSAMMIcM7b5v0n7Fb/M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=nit129oHQBips48R8/DBRn4NTZc0uETLVX2LGl3WzfNHCfKTJxbLNpXAyK49UYHJj TcW/se/EelZg7Q1N0bUdR/5MTZkWFwK99VPk1qnNp+buhQt7aZ7Y4pnbpsJxtXFkc5 7tVbtz+13STn8zKXQVdy0mu/04h64QxV52it3haE=
Message-Id: <6.2.5.6.2.20130506133253.0b979b68@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 06 May 2013 15:08:24 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Detective story (was: Language editing)
In-Reply-To: <51881140.5070904@gmail.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Mon, 06 May 2013 22:15:43 -0000

At 13:23 06-05-2013, Brian E Carpenter wrote:
>I don't that is quite right. The problem in this case is not to do
>with linguistic quality. It's due to a lack of formal verification

Quoting from the detective story:

   "At [censored] we have changed our mail server configuration in the past few
    months, and are now using a mail server from [censored] namely the
    [censored] Server."

There isn't any mention of whether the mail server was tested.

   "Seemingly at random my efforts to send mail just fail."

There would likely be an error code with text providing an 
explanation.  I would probably follow a different debugging 
path.  Anyway, the session showed:

   "EHLO [IPv6:2001:df9::4015:1430:8367:2073:5d0]
    501 5.5.4 Invalid domain name"

This is where I go and read RFC 6409 and I find that:

   "The MSA SHOULD log message errors, especially apparent
    misconfigurations of client software."

And then follow up with RFC 5321 where I find a mention of address 
literals.  I go and read RFC 4291 which is a Draft Standard.  I see 
an update in RFC 5952 which is a Proposed Standard.  As I was told 
that the Internet runs on Proposed Standards that update must be 
right.  I see the following:

   "The recommendation in this section SHOULD be followed by systems
    when generating an address to be represented as text, but all
    implementations MUST accept and be able to handle any legitimate
    [RFC4291] format."

Back to the detective story:

   "The writing if RFC5952 is incredibly sloppy for a Proposed Standard"

I look at the write-up:

  "The 6MAN working group reviewed and discussed this document several
   times. There is a strong consensus to move this forward."

  "This document has been reviewed by key members of the 6MAN working
   group and the chairs."

I look at the IESG evaluation and I see:

  "Language & grammar are rough."

Between you and me, these Area Directors are trouble-makers.  :-)

I verify compliance (2010), RFC 2821, RFC 4409; there isn't any 
mention of the IPv6 specifications mentioned in the detective story.

There are people out there who have to fix problems like this.  There 
are people out there who have to read those specifications and figure 
out where is the head and where is the tail.

Regards,
-sm 


From john-ietf@jck.com  Mon May  6 15:55:48 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60DF421F85BF for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.669
X-Spam-Level: 
X-Spam-Status: No, score=-101.669 tagged_above=-999 required=5 tests=[AWL=-0.930, BAYES_20=-0.74, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRupwYKMf2HS for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:55:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3714321F85C9 for <ietf@ietf.org>; Mon,  6 May 2013 15:55:43 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZUJo-0006MK-Ru; Mon, 06 May 2013 18:55:40 -0400
X-Vipre-Scanned: 00D0586D002C3100D059BA-TDI
Date: Mon, 06 May 2013 18:55:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: Olaf Kolkman <olaf@NLnetLabs.nl>, IETF list <ietf@ietf.org>
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <3211D44685883C48FF0C41BD@[192.168.1.128]>
In-Reply-To: <CF914474-0AEF-4196-9A24-10E042434D55@NLnetLabs.nl>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <7CA49E28-044E-47F3-AEC1-746C40A0E5DB@tzi.org> <51814CAF.1040307@stpeter.im> <74B6F7DE-A851-46B0-844E-9DCD88F791F2@vpnc.org> <51815260.6000002@stpeter.im> <DBD29CB8-8D4A-406C-AA2A-5A9CC808358C@netapp.com> <40035C8A-D68A-43CA-BA77-F701505944C9@tzi.org> <51863677.7010807@cisco.com> <51864888.8080802@gmx.net> <CF914474-0AEF-4196-9A24-10E042434D55@NLnetLabs.nl>
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: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 22:55:48 -0000

--On Monday, May 06, 2013 04:35 -0400 Olaf Kolkman
<olaf@NLnetLabs.nl> wrote:

> Personally I hope that RFC 6410 has the effect that we, as a
> community, get serious about promoting our proposed standards,
> or obsolete them. 
> 
> I wonder how many standards got promoted after 6410 was
> published.

According to my rough count (well, not that rough), the number
of RFCs numbered above 6410 that represent full Standards is
zero.  I note that DKIM is now in Last Call for promotion
without revision; if it succeeds, it would be the first.  

RFC 6410 was published in October 2011.  Between, e.g., October
2009 and May 2011, seven documents were published as Internet
Standards (RFCs 5652, 5730 - 5734, and 6152).  Because of the
five documents in the EPP series, that is not quite as large a
count as one would expect but even if one counts that as only
three, three is larger than zero.    

That is definitely not a comparison on which I'd want to make
any statistical assertions, but it suggests that 6410 has not
been an overwhelming success is promoting documents.

    john


From john-ietf@jck.com  Mon May  6 15:57:29 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 665A821F85C9 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:57:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.134
X-Spam-Level: 
X-Spam-Status: No, score=-102.134 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vQf+vLu6Lmm0 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 15:57:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4817E21F85BF for <ietf@ietf.org>; Mon,  6 May 2013 15:57:24 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZULS-0006MX-Mu; Mon, 06 May 2013 18:57:22 -0400
X-Vipre-Scanned: 00D1E640002C3100D1E78D-TDI
Date: Mon, 06 May 2013 18:57:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bill McQuillan <McQuilWP@pobox.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <D9A720FAD8052DF1493A929D@[192.168.1.128]>
In-Reply-To: <262233160.20130506002617@pobox.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <76519C05-F59F-4ABC-8BD9-B5713EA1F2C6@isoc.org> <5183CB90.7030900@dcrocker.net> <201305031729.r43HTMPk021875@cichlid.raleigh.ibm.com> <635576BE738E49593C8E6A6D@[192.168.1.128]> <262233160.20130506002617@pobox.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: Mon, 06 May 2013 22:57:29 -0000

--On Monday, May 06, 2013 00:26 -0700 Bill McQuillan
<McQuilWP@pobox.com> wrote:

> 
> On Sun, 2013-05-05, John C Klensin wrote:
> 
>> Finally, there are a few things that we used to do, that were
>> helpful, and that were abandoned due to industry evolution and
>> changes in priorities.  The original idea of a Proposed
>> Standard as a fairly rough specification that would be used
>> for study and evaluation on the basis of implementation
>> experience, not a spec from which products were built, is one
>> that has been mentioned (although not quite in that way).   
> 
> FWIW, this leads me to the thought that the IETF may have a 
> terminology problem. The word "standard" is used too soon in
> the  maturity levels of RFCs.
> 
> I think that our skills are primarily in producing "protocols"
> rather than "standards". Perhaps it would have been better if
> the names of the maturity levels were something like:
> 
>   Proposed Protocol
>   Test Version 1 Protocol
>   Test Version 2 protocol
>    .
>    .
>    .
>   Standard Protocol
> 
> Only using the word "standard" when it was determined to be 
> stable and recommended for wide usage.

Not the first time this has been proposed.  Or even only the
fourth or fifth.  That doesn't necessarily make it a bad idea,
just one the community has not been willing to adopt.

   john



From marka@isc.org  Mon May  6 17:59:37 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B49721F8FF0 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 17:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8pSMROEf2Pva for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 17:59:36 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 18EF221F89FD for <ietf@ietf.org>; Mon,  6 May 2013 17:59:35 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 679635F98E7; Tue,  7 May 2013 00:59:19 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367888375; bh=ox+3pWnzdY+HGTNVabbJaI3Z/soT47JtZ9df0JDREuQ=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=KKsFnKfRx2CjXhgxI0nKdM3iwG14kuwR+sU43r9xH2CMmH+yDSsmhELhMSUS6TLTX wZUBI4RxxqTIkQK4XPtD8wHBF5rjKKrQCdawmBGZgUe6qmw9Nna9y+PTJOGKxYGQd1 jHk6rfvfgakvcnH25yDzXXx+fTTBmitYUvXfjytE=
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9958:41b7:ce5:b4da]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id B76E4216C40; Tue,  7 May 2013 00:59:17 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 17D7C33F1807; Tue,  7 May 2013 10:59:11 +1000 (EST)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com>, <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com>
Subject: Re: Language editing
In-reply-to: Your message of "Tue, 07 May 2013 08:23:28 +1200." <51881140.5070904@gmail.com>
Date: Tue, 07 May 2013 10:59:10 +1000
Message-Id: <20130507005911.17D7C33F1807@drugs.dv.isc.org>
Cc: john-ietf@jck.com, yaronf.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 00:59:37 -0000

In message <51881140.5070904@gmail.com>, Brian E Carpenter writes:
> On 07/05/2013 02:10, l.wood@surrey.ac.uk wrote:
> > http://labs.apnic.net/blabs/?p=309
> > 
> > an excellent detective story on badly-written, poorly edited, standards track RFCs leading to interop pro
> blems. Enjoy.
> 
> I don't that is quite right. The problem in this case is not to do
> with linguistic quality. It's due to a lack of formal verification
> among a set of interacting and cross-area RFCs. (And the problem
> is wider, because there are two distinct places in IETF standards
> where ABNF for the text representation of IPv6 addresses can be
> found.) This is a case where no amount of language editing would
> have helped. Actually I used it a couple of months ago in a
> discussion with some experts on formal verification, and they rather
> liked it as a poster child for the need for formal methods in SDOs.
> 
>     Brian


Apples mail client is broken [IPv6:2001:df9::4015:1430:8367:2073:5d0]
is not legal according to both RFC 5321 and RFC 2821 which is all
that applies here.  RFC 2821 was consistent with RFC 2373 and the
SMTP literal spec has remained frozen since then which you want
when you are trying to promote long term interoperability.

Now one could update RFC 5321 to accept the above :: instead of a
single :0: but you could never legally send it.

Note for IPv4 [070.0.0.0] is 70.0.0.0 not 56.0.0.0 despite the fact
that many system will take 070.0.0.0 and send to 56.0.0.0. 

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From john@jlc.net  Mon May  6 18:29:33 2013
Return-Path: <john@jlc.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 522ED21F93A9 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 18:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.186
X-Spam-Level: 
X-Spam-Status: No, score=-105.186 tagged_above=-999 required=5 tests=[AWL=1.413, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dSnSJ-Ri+acv for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 18:29:28 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id E5E4121F9378 for <ietf@ietf.org>; Mon,  6 May 2013 18:29:23 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 3623B33C26; Mon,  6 May 2013 21:29:24 -0400 (EDT)
Date: Mon, 6 May 2013 21:29:24 -0400
From: John Leslie <john@jlc.net>
To: Mark Andrews <marka@isc.org>
Subject: Re: Language editing
Message-ID: <20130507012924.GX23227@verdi>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <20130507005911.17D7C33F1807@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130507005911.17D7C33F1807@drugs.dv.isc.org>
User-Agent: Mutt/1.4.1i
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, 07 May 2013 01:29:33 -0000

Mark Andrews <marka@isc.org> wrote:
> 
> Apples mail client is broken [IPv6:2001:df9::4015:1430:8367:2073:5d0]
> is not legal according to both RFC 5321 and RFC 2821 which is all
> that applies here.

   I was until today unaware how strong the feelings are on this
"one-or-more" vs. "two-or-more" issue. I do not expect to change
anybody's mind. :^(

   But I do object to calling that EHLO string "not legal".

   The 5321 reference names RFC 4291 as the source of address syntax
(even if it gives BNF which says "two or more" if you delve deeply
enough).

   RFC 4921 is clear about saying "one or more". The Errata posted
against it claiming it should say "two or more" have been rejected.
It is silly to argue under these conditions that Apple's EHLO string
is "not legal".

   BTW, RFC 5321 still contains the language about
" if the verification fails, the server MUST NOT refuse to accept a
" message on that basis.

so IMHO enforcing any particular interpretation of what an IPv6
address literal should look like is double-plus-ungood.

====

   To the casual observer, it looks as if RFC 4291 relaxed a previous
"two or more" requirement, but there are folks who don't want to
accept that relaxing.

   One can accept the idea that this relaxing has failed, yet still
observe "liberal in what you accept" as trumping it. I truly wish the
folks in the "two or more" camp would do so!

--
John Leslie <john@jlc.net>

From packetgrrl@gmail.com  Mon May  6 19:12:59 2013
Return-Path: <packetgrrl@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 853A521F9377 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 19:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.437
X-Spam-Level: 
X-Spam-Status: No, score=0.437 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VcrwWscNAtQK for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 19:12:58 -0700 (PDT)
Received: from mail-ia0-x22c.google.com (mail-ia0-x22c.google.com [IPv6:2607:f8b0:4001:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id B7EB021F8FF0 for <ietf@ietf.org>; Mon,  6 May 2013 19:12:58 -0700 (PDT)
Received: by mail-ia0-f172.google.com with SMTP id i20so67146ian.17 for <ietf@ietf.org>; Mon, 06 May 2013 19:12:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=9Yy+LsytS3LxdVoElwP6n0NfY495saxq5EwGxDLK/10=; b=hC0SEw78bKOXdr+IgHbe1QINIkORiLJ1O/F3E/ouf1NHtJi+6N6tNjCdXaiJ6ApTSK I0ZkdMf0br/p9n2pHqkJ/E5fG+2bun3Q+8VrJt/2bqomTUClxSIPoDCY5mTGPx4TUXY8 odX09DPeKqrIEwD2tr2ucD1RR+pkMokU+2jxtlkIFbWdh7riLKgQtvRydZfbGBjNYqDx NP0to8dgryWAMI2JbZFHhlS10KQbBrYvIp7l8/BIAtoF6auNbGELobeXCA+zUXyuE1aO v8frYMcaxW6Vze0wI12tJnT4n0ON4NC2UiTIA5xyz4Ny/+AQadO6Y7QvmqP9wSOEAO6g QuOQ==
MIME-Version: 1.0
X-Received: by 10.50.126.36 with SMTP id mv4mr16602igb.28.1367892778362; Mon, 06 May 2013 19:12:58 -0700 (PDT)
Sender: packetgrrl@gmail.com
Received: by 10.42.110.211 with HTTP; Mon, 6 May 2013 19:12:57 -0700 (PDT)
In-Reply-To: <m2fvy7sqcw.wl%randy@psg.com>
References: <51687C0D.8090804@labn.net> <51694B16.4090504@labn.net> <51695398.3000708@cs.tcd.ie> <7FABCCC7-D0B1-4B9A-B546-4F2FDE8B8DAE@isoc.org> <38b3500963cc19ad6b4a731541bead97.squirrel@www.trepanning.net> <516EB736.6060801@cisco.com> <8684e2fdd4acda5cab143e70e0e45821.squirrel@www.trepanning.net> <516EFC7E.90801@cisco.com> <bb357f249e7cf8ed60177d2bab7d0679.squirrel@www.trepanning.net> <20130419014446.GC1113@mx1.yitter.info> <1b273698cf7211ea2907e332bd19e4c4.squirrel@www.trepanning.net> <005501ce3ce5$24eb49a0$4001a8c0@gateway.2wire.net> <5EAC602D-8F88-4A09-9ED2-13A42BED93AC@lilacglade.org> <20130429040539.5657221F93BA@ietfa.amsl.com> <517E3932.9060006@cisco.com> <517EA52F.9040900@gmail.com> <20130429192848.5FB4F21F9B35@ietfa.amsl.com> <tslli816s9l.fsf@mit.edu> <517ED235.9070202@cisco.com> <tsl61z56p12.fsf@mit.edu> <517F1823.4070502@gmail.com> <tslzjwg4ujm.fsf@mit.edu> <3FD89A1B-F1D4-450F-BF38-61250F9A1D83@piuha.net> <m2fvy7sqcw.wl%randy@psg.com>
Date: Mon, 6 May 2013 20:12:57 -0600
X-Google-Sender-Auth: LY67jgqOoSwQqobLejeHLSxKMI8
Message-ID: <CAMvf=7ZXxptRcvYT28mFx9fEAfjEJy=+RG2QEed_0eMXqKbpwQ@mail.gmail.com>
Subject: Re: IETF Diversity Question on Berlin Registration?
From: CJ Aronson <cja@daydream.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=047d7b3a968425307f04dc175bf5
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: Tue, 07 May 2013 02:12:59 -0000

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

I was getting ready to send a note that basically said I give up when I saw
this post from Randy. Thanks Randy.

Then a friend posted this TED talk and it landed in my facebook feed.   It
gives me hope that there are a few men out there who might get the issue.
 I personally would love to see the IETF consult someone like this speaker.


http://www.upworthy.com/a-ted-talk-that-might-turn-every-man-who-watches-it-into-a-feminist-its-pretty-fantastic-7?g=2

I have found this whole thread discouraging and I felt the need to say
something.  This TED talk pretty much sums it up.

Thanks!

---Cathy


On Tue, Apr 30, 2013 at 2:41 PM, Randy Bush <randy@psg.com> wrote:

> you don't need a weatherman to know which way the wind blows.
> -- bob dylan
>
> we do not need measurements to know the ietf is embarrassingly
> non-diverse.  it is derived from and embedded in an embarrassingly
> non-diverse culture.
>
> we need to do what we can to remedy this.  progress not perfection is
> our goal.
>
> measurement may be useful to see if we are having effect and/or what
> things have effect (meeting locales, size of cookies, ...).
>
> we should be asking the minorities and those struggling to particiate
> what we can do to help.
>
> randy
>

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

<div dir=3D"ltr">I was getting ready to send a note that basically said I g=
ive up when I saw this post from Randy. Thanks Randy.=A0<div><br></div><div=
>Then a friend posted this TED talk and it landed in my facebook feed. =A0 =
It gives me hope that there are a few men out there who might get the issue=
. =A0I personally would love to see the IETF consult someone like this spea=
ker. =A0<div>

<br></div><div><a href=3D"http://www.upworthy.com/a-ted-talk-that-might-tur=
n-every-man-who-watches-it-into-a-feminist-its-pretty-fantastic-7?g=3D2" st=
yle=3D"font-family:arial,sans-serif;font-size:13px" target=3D"_blank">http:=
//www.upworthy.com/a-ted-talk-that-might-turn-every-man-who-watches-it-into=
-a-feminist-its-pretty-fantastic-7?g=3D2</a><br>

</div></div><div><br></div><div style>I have found this whole thread discou=
raging and I felt the need to say something. =A0This TED talk pretty much s=
ums it up. =A0</div><div style><br></div><div style>Thanks!</div><div style=
>
<br></div><div>---Cathy</div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Tue, Apr 30, 2013 at 2:41 PM, Randy Bush <span dir=3D"l=
tr">&lt;<a href=3D"mailto:randy@psg.com" target=3D"_blank">randy@psg.com</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">you don&#39;t need a weatherman to know whic=
h way the wind blows.<br>
-- bob dylan<br>
<br>
we do not need measurements to know the ietf is embarrassingly<br>
non-diverse. =A0it is derived from and embedded in an embarrassingly<br>
non-diverse culture.<br>
<br>
we need to do what we can to remedy this. =A0progress not perfection is<br>
our goal.<br>
<br>
measurement may be useful to see if we are having effect and/or what<br>
things have effect (meeting locales, size of cookies, ...).<br>
<br>
we should be asking the minorities and those struggling to particiate<br>
what we can do to help.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br>
</font></span></blockquote></div><br></div></div>

--047d7b3a968425307f04dc175bf5--

From marka@isc.org  Mon May  6 19:18:50 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D64621F9381 for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 19:18:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSstRS4VSHZH for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 19:18:49 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id B6F4821F937E for <ietf@ietf.org>; Mon,  6 May 2013 19:18:49 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 718ECC941E; Tue,  7 May 2013 02:18:41 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1367893128; bh=5Qv/gP5ziasCOST51DjgStRyom0gFmqf+PRxTX6QfGw=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=LokcDLESf4twdMeJm4i7pfglrGjzhFyEntgD+jDVDUlt35MUAWxW+IE8UyvbaL9ll 4/ybqG0CAYZBbpVOD8CkT5Ahk/x4ORQftuEt0HMNJtZKXq9enKYFZstmo3ZacjVXgU rLC1an3c7lN4DBdl9pFQXmLpijn8rhfJYtbX8Bks=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue,  7 May 2013 02:18:41 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 18C74216C4B; Tue,  7 May 2013 02:18:41 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 89D8933F1DA0; Tue,  7 May 2013 12:18:33 +1000 (EST)
To: John Leslie <john@jlc.net>
From: Mark Andrews <marka@isc.org>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <20130507005911.17D7C33F1807@drugs.dv.isc.org> <20130507012924.GX23227@verdi>
Subject: Re: Language editing
In-reply-to: Your message of "Mon, 06 May 2013 21:29:24 -0400." <20130507012924.GX23227@verdi>
Date: Tue, 07 May 2013 12:18:33 +1000
Message-Id: <20130507021833.89D8933F1DA0@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
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, 07 May 2013 02:18:50 -0000

	You missed the point RFC 5321 SMTP clients have to operate
	with RFC 2821 SMTP servers when sending address literal in
	the HELO/EHLO.  Code doesn't magically get updated when the
	spec is updated.  It takes years for changes to trickle
	through.  The code has to be written, then it has to be
	deployed.

	[The who SPF issue is about a WG that is too impatient to
	 wait for the updated code, that has been written, to be
	 deployed.  That will happen as OS's get update / replaced.]

	While RFC 4291 relaxed the address syntax, RFC 5321 didn't
	because to do so would break interoperability.

	RFC 5321's address literals are a subset of RFC 4291's
	permittable address formats.  So there is nothing wrong
	with referencing RFC 4291.

	Mark

In message <20130507012924.GX23227@verdi>, John Leslie writes:
> Mark Andrews <marka@isc.org> wrote:
> > 
> > Apples mail client is broken [IPv6:2001:df9::4015:1430:8367:2073:5d0]
> > is not legal according to both RFC 5321 and RFC 2821 which is all
> > that applies here.
> 
>    I was until today unaware how strong the feelings are on this
> "one-or-more" vs. "two-or-more" issue. I do not expect to change
> anybody's mind. :^(
> 
>    But I do object to calling that EHLO string "not legal".
> 
>    The 5321 reference names RFC 4291 as the source of address syntax
> (even if it gives BNF which says "two or more" if you delve deeply
> enough).
> 
>    RFC 4921 is clear about saying "one or more". The Errata posted
> against it claiming it should say "two or more" have been rejected.
> It is silly to argue under these conditions that Apple's EHLO string
> is "not legal".
> 
>    BTW, RFC 5321 still contains the language about
> " if the verification fails, the server MUST NOT refuse to accept a
> " message on that basis.
> 
> so IMHO enforcing any particular interpretation of what an IPv6
> address literal should look like is double-plus-ungood.
> 
> ====
> 
>    To the casual observer, it looks as if RFC 4291 relaxed a previous
> "two or more" requirement, but there are folks who don't want to
> accept that relaxing.
> 
>    One can accept the idea that this relaxing has failed, yet still
> observe "liberal in what you accept" as trumping it. I truly wish the
> folks in the "two or more" camp would do so!
> 
> --
> John Leslie <john@jlc.net>
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From ned+ietf@mauve.mrochek.com  Mon May  6 19:51:25 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8095321F884F for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 19:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8FZTfdDTZYNi for <ietf@ietfa.amsl.com>; Mon,  6 May 2013 19:51:20 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C5E8921F8AF8 for <ietf@ietf.org>; Mon,  6 May 2013 19:51:19 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OTC6P4RDC0005AXQ@mauve.mrochek.com> for ietf@ietf.org; Mon, 6 May 2013 19:46:15 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OT3BOFFH80000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 6 May 2013 19:46:12 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OTC6P35TA4000054@mauve.mrochek.com>
Date: Mon, 06 May 2013 19:37:23 -0700 (PDT)
Subject: Re: Language editing
In-reply-to: "Your message dated Mon, 06 May 2013 21:29:24 -0400" <20130507012924.GX23227@verdi>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <20130507005911.17D7C33F1807@drugs.dv.isc.org> <20130507012924.GX23227@verdi>
To: John Leslie <john@jlc.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: Tue, 07 May 2013 02:51:25 -0000

> Mark Andrews <marka@isc.org> wrote:
> >
> > Apples mail client is broken [IPv6:2001:df9::4015:1430:8367:2073:5d0]
> > is not legal according to both RFC 5321 and RFC 2821 which is all
> > that applies here.

>    I was until today unaware how strong the feelings are on this
> "one-or-more" vs. "two-or-more" issue. I do not expect to change
> anybody's mind. :^(

>    But I do object to calling that EHLO string "not legal".

It's syntactically illegal according to the ABNF in RFC 5321 itself, which
specifically states:

 IPv6-comp      = [IPv6-hex *5(":" IPv6-hex)] "::"
                  [IPv6-hex *5(":" IPv6-hex)]
                    ; The "::" represents at least 2 16-bit groups of
                  ; zeros.  No more than 6 groups in addition to the
                  ; "::" may be present.

>    The 5321 reference names RFC 4291 as the source of address syntax
> (even if it gives BNF which says "two or more" if you delve deeply
> enough).

It may be the source, but the formal syntax specified in the document at hand
has to be the definitive one.

>    RFC 4921 is clear about saying "one or more". The Errata posted
> against it claiming it should say "two or more" have been rejected.
> It is silly to argue under these conditions that Apple's EHLO string
> is "not legal".

No, what's silly is your argument that the ABNF in the actual specification of
how mail clients and servers are supposed to behave isn't the definitive
definition.

>    BTW, RFC 5321 still contains the language about
> " if the verification fails, the server MUST NOT refuse to accept a
> " message on that basis.

And that language appears in the context of checking that the IP literal
in the HELO/EHLO actually corresponds to the IP address of the client. It
has nothing to do with syntactic validity.

> so IMHO enforcing any particular interpretation of what an IPv6
> address literal should look like is double-plus-ungood.

Then you should be arguing for a change in RFC 5321, because it is *very*
clear that this usage is not allowed.

				Ned

From ynir@checkpoint.com  Tue May  7 01:04:00 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC42F21F87B1 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 01:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.854
X-Spam-Level: 
X-Spam-Status: No, score=-9.854 tagged_above=-999 required=5 tests=[AWL=0.745,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RRBbN-W4X9e5 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 01:03:55 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD8421F89FD for <ietf@ietf.org>; Tue,  7 May 2013 01:03:54 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4783ixN017529; Tue, 7 May 2013 11:03:52 +0300
X-CheckPoint: {5188B3D8-2-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Tue, 7 May 2013 11:03:43 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: SM <sm@resistor.net>
Subject: Re: Detective story (was: Language editing)
Thread-Topic: Detective story (was: Language editing)
Thread-Index: AQHOSqdLpfBJHhE+QUONZPNy+st+o5j5Ky4A
Date: Tue, 7 May 2013 08:03:43 +0000
Message-ID: <ADE8CFDC-A612-4418-89CC-349F18E612A1@checkpoint.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <6.2.5.6.2.20130506133253.0b979b68@resistor.net>
In-Reply-To: <6.2.5.6.2.20130506133253.0b979b68@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.134]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11e2649d0786e147019903e228a1639d99861257c9
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <1D0E4F4F5FA1DE47A095626B6803AD94@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<john-ietf@jck.com>" <john-ietf@jck.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 08:04:01 -0000

On May 7, 2013, at 1:08 AM, SM <sm@resistor.net> wrote:

> At 13:23 06-05-2013, Brian E Carpenter wrote:
>> I don't that is quite right. The problem in this case is not to do
>> with linguistic quality. It's due to a lack of formal verification
>=20
> Quoting from the detective story:
>=20
>  "At [censored] we have changed our mail server configuration in the past=
 few
>   months, and are now using a mail server from [censored] namely the
>   [censored] Server."
>=20
> There isn't any mention of whether the mail server was tested.

I don't know why you censored this, but that particular implementation is u=
sed by a vast majority of corporations. The one good thing about running wi=
th the crowd is that stuff pretty much just works.  And it does, unless you=
 do <heresy> something weird like enabling IPv6 </heresy>.

>  "Seemingly at random my efforts to send mail just fail."
>=20
> There would likely be an error code with text providing an explanation.  =
I would probably follow a different debugging path.  Anyway, the session sh=
owed:
>=20
>  "EHLO [IPv6:2001:df9::4015:1430:8367:2073:5d0]
>   501 5.5.4 Invalid domain name"

Yeah, I would also start with the tcpdump. But that part of the story sound=
ed bogus. 2nd paragraph has this:

                                        To collect my mail I use IMAP, and =
to send my mail I use=20
   STMP, both standard protocols. These days security can=92t be ignored so=
 we use TLS for channel=20
   encryption. All pretty standard stuff.

So how did he get to see the server response, or test with telnet?

>=20
> This is where I go and read RFC 6409 and I find that:
>=20
>  "The MSA SHOULD log message errors, especially apparent
>   misconfigurations of client software."
>=20
> And then follow up with RFC 5321 where I find a mention of address litera=
ls.  I go and read RFC 4291 which is a Draft Standard.  I see an update in =
RFC 5952 which is a Proposed Standard.  As I was told that the Internet run=
s on Proposed Standards that update must be right.  I see the following:
>=20
>  "The recommendation in this section SHOULD be followed by systems
>   when generating an address to be represented as text, but all
>   implementations MUST accept and be able to handle any legitimate
>   [RFC4291] format."

Gee, you read a lot of RFCs when debugging network problems :-). I only do =
so if I'm going to file a bug report / support ticket

> Back to the detective story:
>=20
>  "The writing if RFC5952 is incredibly sloppy for a Proposed Standard"
>=20
> I look at the write-up:
>=20
> "The 6MAN working group reviewed and discussed this document several
>  times. There is a strong consensus to move this forward."
>=20
> "This document has been reviewed by key members of the 6MAN working
>  group and the chairs."
>=20
> I look at the IESG evaluation and I see:
>=20
> "Language & grammar are rough."
>=20
> Between you and me, these Area Directors are trouble-makers.  :-)

So they are. But the hard-to-read parts of this spec are mainly the motivat=
ional sections (everything but 4). It might have been clearer to state agai=
n that the whole point of this spec is "conservative in what you send". Lib=
eral in what you accept is mentioned in the first paragraph of section 4. =
=20

> I verify compliance (2010), RFC 2821, RFC 4409; there isn't any mention o=
f the IPv6 specifications mentioned in the detective story.
>=20
> There are people out there who have to fix problems like this.  There are=
 people out there who have to read those specifications and figure out wher=
e is the head and where is the tail.

Yup. That's why those people get the big bucks.=20

>=20
> Regards,
> -sm=20


From gonzalo.camarillo@ericsson.com  Tue May  7 04:02:44 2013
Return-Path: <gonzalo.camarillo@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 23D2321F8E9A; Tue,  7 May 2013 04:02:44 -0700 (PDT)
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_SE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFscTgM7X3RX; Tue,  7 May 2013 04:02:39 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCDA21F8733; Tue,  7 May 2013 04:02:38 -0700 (PDT)
X-AuditID: c1b4fb25-b7f396d000007d06-94-5188df4da9ac
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 36.67.32006.D4FD8815; Tue,  7 May 2013 13:02:37 +0200 (CEST)
Received: from [131.160.126.23] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Tue, 7 May 2013 13:02:36 +0200
Message-ID: <5188DF4B.1030402@ericsson.com>
Date: Tue, 7 May 2013 14:02:35 +0300
From: Gonzalo Camarillo <Gonzalo.Camarillo@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Samuel Weiler <weiler@watson.org>
Subject: Re: secdir review of draft-ietf-mmusic-sdp-cs-17
References: <alpine.BSF.2.00.1302011241020.47827@fledge.watson.org>
In-Reply-To: <alpine.BSF.2.00.1302011241020.47827@fledge.watson.org>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUyM+Jvra7v/Y5Ag53nBCw2rv3MZDHjz0Rm i2cb57NYfFj4kMWi/etzNgdWjyVLfjJ5fLn8mc1jacNu9gDmKC6blNSczLLUIn27BK6MU68e MRZMEat4PWMjewPjA8EuRk4OCQETif4JLxkhbDGJC/fWs3UxcnEICZxilPh4tZ8JwlnNKLH/ 5SMWkCpeAW2JZQ9mAdkcHCwCKhJP2t1BwmwCFhJbbt0HKxEViJL493Y3I0S5oMTJmU/A4iIC qhIX/n9nBbGZBWIldkz/zwRiCwtYSjyYeA5spJCAs8SV+wkgJqeAi0TPMn2I0yQlFk3rZIHo 1JOYcrWFEcKWl9j+dg4ziC0EdNjyZy0sExiFZiFZPAtJyywkLQsYmVcxsucmZuaklxttYgSG 88Etv1V3MN45J3KIUZqDRUmcN5mrMVBIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDo1d8r4+r 09PI9Rf0pR43bLUpjW8otpj+O1be5sQW7Y3brabu5IxM6v9uq1DJaB2ls9cy422fji2PyLTm HxuYVnq5v745Sbdbp7pMb/bv2M+JBlON/swXcwjVkv7p+t/ud2iuNneYs9mZEM5SHuE7W9Iz Zt7LL2prmWfz/+68Kbpb/9lFykUpsRRnJBpqMRcVJwIAahmkXTUCAAA=
Cc: ietf@ietf.org, iesg@ietf.org, draft-ietf-mmusic-sdp-cs@tools.ietf.org, secdir@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 11:02:44 -0000

Hi Samuel,

the authors of this draft have reviewed it in order to address your
comments:

http://tools.ietf.org/html/draft-ietf-mmusic-sdp-cs-18

Could you please have a look at this revision and let them know whether
you are happy with it?

Thanks,

Gonzalo


On 04/02/2013 9:08 PM, Samuel Weiler wrote:
> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
> 
> This document allows SIP endpoints to negotiate the use of a
> circuit-switched (e.g. PSTN) channel.  It presents a mechanism for
> correlating an incoming circuit-switched connection with a given SDP/SIP
> session by sending a nonce or a static string.
> 
> Summary: I would like to see a stronger authentication mechanism
> defined to replace the static string or "plaintext password" nonce.
> 
> I am content with the analysis of security weaknesses: an attacker
> could trick someone into initiating a potentially expensive PSTN call,
> and the correlation mechanism is weak.
> 
> I am not content with the use of a mere nonce or static string for
> correlation.  That is the equivalent of sending plaintext passwords, and
> I suspect we have better mechanisms available that could allow for
> mutual endpoint authentication, making it statistically unlikely for a
> man-in-the-middle to participate successfully in the correlation
> exchange.  The document makes a case for using short strings/nonces
> (e.g. a caller-ID string or 10 DTFM digits).  I suspect both that those
> lengths could be extended without great pain and that some stronger
> authentication mechanisms could work with such short strings, especially
> given the ability to send longer keying material in the packet-switched
> SDP session.
> 
> Non-security observation: I'm worried that the architecture of the
> current correlation mechanism will have some unintended consequences.
>> From section 5.2.3:
> 
>    The endpoints should be able to correlate the circuit-switched bearer
>    with the session negotiated with SDP in order to avoid ringing for an
>    incoming circuit-switched bearer that is related to the session
>    controlled with SDP (and SIP).
> 
> As I understand it, some of the defined variants of the correlation
> scheme require answering the call (e.g. the DTMF scheme) before
> knowing whether or not the channel corresponds to a SIP session.  If
> it does not, then what?  The call is already answered, which gives a
> surprising user experience.  Feel free to tell me I'm off base with
> this one.
> 
> -- Sam
> 
> 


From joelja@bogus.com  Tue May  7 07:22:05 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F91E21F8F12 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 07:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9BvI2x3nD0Q for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 07:22:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id B466B21F8AA6 for <ietf@ietf.org>; Tue,  7 May 2013 07:22:04 -0700 (PDT)
Received: from joels-MacBook-Air.local ([193.1.64.8]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r47ELuUD094829 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 7 May 2013 14:21:59 GMT (envelope-from joelja@bogus.com)
Message-ID: <51890DFF.9000805@bogus.com>
Date: Tue, 07 May 2013 15:21:51 +0100
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-eastlake-rfc5342bis-02.txt> (IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters) to Best Current Practice
References: <20130507110739.12847.4273.idtracker@ietfa.amsl.com>
In-Reply-To: <20130507110739.12847.4273.idtracker@ietfa.amsl.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]); Tue, 07 May 2013 14:22:00 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 14:22:05 -0000

On 5/7/13 12:07 PM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IANA Considerations and IETF Protocol and Documentation Usage for IEEE
>     802 Parameters'
>    <draft-eastlake-rfc5342bis-02.txt> as Best Current Practice
Sponsoring AD here,

Getting feedback on the 5342bis document is important since this is the 
primary consensus call.

Thanks
Joel

> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-04. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     Some IETF protocols make use of Ethernet frame formats and IEEE 802
>     parameters.  This document discusses some use of such parameters in
>     IETF protocols, specifies IANA considerations for assignment of
>     points under the IANA OUI (Organizationally Unique Identifier),
>     provides some values for use in documentation, and obsoletes RFC
>     5342.
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-eastlake-rfc5342bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-eastlake-rfc5342bis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


From ned+ietf@mauve.mrochek.com  Tue May  7 08:24:26 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A05F121F8F0D for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 08:24:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gXOLLHmkwMl6 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 08:24:21 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8507121F8C69 for <ietf@ietf.org>; Tue,  7 May 2013 08:24:21 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OTCWZSCVKW005HSU@mauve.mrochek.com> for ietf@ietf.org; Tue, 7 May 2013 08:19:18 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OT3BOFFH80000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 7 May 2013 08:19:13 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OTCWZOSHC0000054@mauve.mrochek.com>
Date: Tue, 07 May 2013 08:08:14 -0700 (PDT)
Subject: Re: Language editing
In-reply-to: "Your message dated Mon, 06 May 2013 18:14:03 -0400" <1F9DA0977DABC51DA2EF9963@[192.168.1.128]>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <1F9DA0977DABC51DA2EF9963@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
Cc: yaronf.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 15:24:26 -0000

> Maybe things have changed, but, if one actually believes the
> robustness principle, then, in the case Geoff cites, Exchange is
> simply non-conforming -- not because the spec prohibits
> rejecting on the basis of a fine distinction about IPv6 formats,
> but because doing so is unnecessary, inconsistent with the
> robustness principle, and, arguably, plain silly.

I'm afraid I'm going to have to disagree here. If you look at RFC 5321 and
are unaware of the history of how the text came about, it gives the definite
appearance of going out of its way to ban the use of :: to replace a single
0. A reasonable interpretation is therefore that such forms are disallowed
for a reason.

It's fine to be tolerant of stuff the relevant standard doesn't
allow but doesn't call out explicitly. But that's not the case here.

In any case, if you want to "fix" this, we could change RFC 5321 to accept this
form. But as Mark Andrews points out, you can't make it legal to send such
forms without breaking interoperability. I suppose we could make the change and
recycle at proposed, but that seems rather extreme to fix what is in fact a
nonissue.

I'll also point out that this has diddley-squat to do with formal verification
processes. Again as Mark Anrdrews points out, we deployed something with a
restriction that subsequently turned out to be unnecessary, and now we're stuck
with it. Indeed, had formal verification processes been properly used, they
would have flagged any attempt to change this as breaking interoperability.

				Ned

From john-ietf@jck.com  Tue May  7 08:28:57 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7465D21F8F0E for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 08:28:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=0.310, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNwp0maNdDaQ for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 08:28:48 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8415221F8EDA for <ietf@ietf.org>; Tue,  7 May 2013 08:28:48 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UZjoq-0008qs-G9; Tue, 07 May 2013 11:28:44 -0400
X-Vipre-Scanned: 045D865D002C31045D87AA-TDI
Date: Tue, 07 May 2013 11:28:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Language editing
Message-ID: <5AB71E192C2AE7DACE70630B@[192.168.1.128]>
In-Reply-To: <01OTCWZOSHC0000054@mauve.mrochek.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <1F9DA0977DABC51DA2EF9963@[192.168.1.128]> <01OTCWZOSHC0000054@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: yaronf.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 15:28:57 -0000

--On Tuesday, May 07, 2013 08:08 -0700 Ned Freed
<ned.freed@mrochek.com> wrote:

>> Maybe things have changed, but, if one actually believes the
>> robustness principle, then, in the case Geoff cites, Exchange
>> is simply non-conforming -- not because the spec prohibits
>> rejecting on the basis of a fine distinction about IPv6
>> formats, but because doing so is unnecessary, inconsistent
>> with the robustness principle, and, arguably, plain silly.
 
> I'm afraid I'm going to have to disagree here. If you look at
> RFC 5321 and are unaware of the history of how the text came
> about, it gives the definite appearance of going out of its
> way to ban the use of :: to replace a single 0. A reasonable
> interpretation is therefore that such forms are disallowed for
> a reason.

I hadn't looked at the syntax (as you know, the other part of
that history of how the text came about is that I didn't write
it or even make an effort to check it carefully).  But, having
now done so, you are completely correct.

> It's fine to be tolerant of stuff the relevant standard doesn't
> allow but doesn't call out explicitly. But that's not the case
> here.

Of course, we have lots of implementations that allow things on
input that the standard explicitly prohibits and we rarely spend
much time complaining about them.  I suppose that tolerance for
bare LF is among the most common examples.
 
> In any case, if you want to "fix" this, we could change RFC
> 5321 to accept this form. But as Mark Andrews points out, you
> can't make it legal to send such forms without breaking
> interoperability. I suppose we could make the change and
> recycle at proposed, but that seems rather extreme to fix what
> is in fact a nonissue.

Agreed
 
> I'll also point out that this has diddley-squat to do with
> formal verification processes. Again as Mark Anrdrews points
> out, we deployed something with a restriction that
> subsequently turned out to be unnecessary, and now we're stuck
> with it. Indeed, had formal verification processes been
> properly used, they would have flagged any attempt to change
> this as breaking interoperability.

Also agreed.

best,
   john



From brian.e.carpenter@gmail.com  Tue May  7 13:05:53 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5D321F8895 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 13:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Chi1ydf5fKc3 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 13:05:47 -0700 (PDT)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by ietfa.amsl.com (Postfix) with ESMTP id CD25721F899E for <ietf@ietf.org>; Tue,  7 May 2013 13:05:45 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so677926pde.37 for <ietf@ietf.org>; Tue, 07 May 2013 13:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3SGQ4x/f+fLd2Hy7YfEej/XkfChA1qlStM1D6GyTUqA=; b=guw2AKtFtH1qMPLcJO0CPWZLyC/rv3Vpwg0r5B9+lcrNXoBj3MVl3bmXBW4DtS5Hss M+xzUfkQNMul3QKedB/9Wf2TXhzkIGdFGMI0yIaTyDmJDTGVN3Gbg4cQ9eMZO+1HpJtN y3SNSRpuK+IR8hWIPWlU6QBydcFBsolB4YdRlmNDmo0GD+A2xZwjzs3+Mg6AoglAH4eb 2pJ8CFH+RB7Uy2JmzU4goCuyn4SEvgsvtRq9PPp6pVVQgpfFmWYxP76bZ8/joO52IVwt XSBUn1oEnBKxTWfJLPxcTT51CAy5+R6aBSIUdL933fXOxDVjv70LqLqWfTiiw0LOmbKv wc0w==
X-Received: by 10.68.196.65 with SMTP id ik1mr3894967pbc.194.1367957144396; Tue, 07 May 2013 13:05:44 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id ri8sm18352390pbc.3.2013.05.07.13.05.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 13:05:42 -0700 (PDT)
Message-ID: <51895E92.1020303@gmail.com>
Date: Wed, 08 May 2013 08:05:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <1F9DA0977DABC51DA2EF9963@[192.168.1.128]> <01OTCWZOSHC0000054@mauve.mrochek.com> <5AB71E192C2AE7DACE70630B@[192.168.1.128]>
In-Reply-To: <5AB71E192C2AE7DACE70630B@[192.168.1.128]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: yaronf.ietf@gmail.com, Ned Freed <ned.freed@mrochek.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, 07 May 2013 20:05:53 -0000

On 08/05/2013 03:28, John C Klensin wrote:
...
>> I'll also point out that this has diddley-squat to do with
>> formal verification processes. Again as Mark Anrdrews points
>> out, we deployed something with a restriction that
>> subsequently turned out to be unnecessary, and now we're stuck
>> with it. Indeed, had formal verification processes been
>> properly used, they would have flagged any attempt to change
>> this as breaking interoperability.
> 
> Also agreed.

To be clear, I'm no fan of formal verification either, but this
*is* a case where the IETF's lapse in formality has come back to
bite, and the Postel principle would have helped. Also, given the
original subject of the thread, I don't see how language editing
could have made any difference.

    Brian

From ned+ietf@mauve.mrochek.com  Tue May  7 13:41:01 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 098B221F8B5F for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 13:41:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLkNoAq8VxT4 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 13:40:55 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C624821F8D6A for <ietf@ietf.org>; Tue,  7 May 2013 13:40:55 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OTD828AG7K0033MX@mauve.mrochek.com> for ietf@ietf.org; Tue, 7 May 2013 13:35:52 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OT3BOFFH80000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 7 May 2013 13:35:45 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OTD824BDK6000054@mauve.mrochek.com>
Date: Tue, 07 May 2013 13:33:12 -0700 (PDT)
Subject: Re: Language editing
In-reply-to: "Your message dated Wed, 08 May 2013 08:05:38 +1200" <51895E92.1020303@gmail.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <1F9DA0977DABC51DA2EF9963@[192.168.1.128]> <01OTCWZOSHC0000054@mauve.mrochek.com> <5AB71E192C2AE7DACE70630B@[192.168.1.128]> <51895E92.1020303@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: John C Klensin <john-ietf@jck.com>, yaronf.ietf@gmail.com, Ned Freed <ned.freed@mrochek.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, 07 May 2013 20:41:01 -0000

> On 08/05/2013 03:28, John C Klensin wrote:
> ...
> >> I'll also point out that this has diddley-squat to do with
> >> formal verification processes. Again as Mark Anrdrews points
> >> out, we deployed something with a restriction that
> >> subsequently turned out to be unnecessary, and now we're stuck
> >> with it. Indeed, had formal verification processes been
> >> properly used, they would have flagged any attempt to change
> >> this as breaking interoperability.
> >
> > Also agreed.

> To be clear, I'm no fan of formal verification either, but this
> *is* a case where the IETF's lapse in formality has come back to
> bite, and the Postel principle would have helped. Also, given the
> original subject of the thread, I don't see how language editing
> could have made any difference.

Reread the notes about the history behind this in this thread. You haven't even
come close to making a case that formal verification of the standards would
have prevented this from happening. (Formal verification of implementation
compliance to the standards would of course have prevented Apple's client bug,
but that's a very different thing.)

You are, however, correct that this has nothing to do with specification
editing.

				Ned

From stpeter@stpeter.im  Tue May  7 13:48:28 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1B621F8E96 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 13:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.014
X-Spam-Level: 
X-Spam-Status: No, score=-102.014 tagged_above=-999 required=5 tests=[AWL=0.585, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsmPoOoVrOmJ for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 13:48:22 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BD37321F8F0C for <ietf@ietf.org>; Tue,  7 May 2013 13:48:22 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8F741E8275; Tue,  7 May 2013 14:59:59 -0600 (MDT)
Message-ID: <51896896.80706@stpeter.im>
Date: Tue, 07 May 2013 14:48:22 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net>
In-Reply-To: <5182EFA3.30400@dcrocker.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Tue, 07 May 2013 20:48:28 -0000

On 5/2/13 4:58 PM, Dave Crocker wrote:
> On 5/2/2013 3:25 PM, Jari Arkko wrote:
>> But the delay was really not my main concern. Primarily because I
>> think other issues such as transparency to the working group or late
>> surprises are more fundamental issues than mere timing. But also
>> because I actually*do*  have some statistics that seem to indicate
>> that, overall, the last phase still goes through pretty quickly. Look
>> athttp://www.arkko.com/tools/lifecycle/wgdocs.html  and compare the
>> WG, IESG, and RFC editor times in the first graph. The WG time
>> dominates. (I said "seem to indicate" because the results are pretty
>> dated and I'm not really sure how valid they are, but they match at
>> least my intuitive experience.) Not saying delay reduction wouldn't be
>> useful, the overall times are still very long, and the IETF last call
>> - IESG time is still a significant component. Just that delay would
>> not be my primary
> 
> 
> Jari,
> 
> Very interesting set of graphs.  Thanks!
> 
> 
> Doing very rough eyeballing of the "left side" averages against the
> "right side" averages -- that is, considering how things have changed
> over the last 10 years -- it looks like:
> 
>      Working groups were taking around 500 days and now take around 600.
> 
>      The IESG was taking around 200 days and now takes around 110.
> 
>      The RFC then and now takes around 100 days (with lots of variation
> between the then and the now, of course.)

I'm curious what exactly falls under the RFC Editor phase. My impression
from recent plenaries is that the purely RFC Editor responsibilities
(not including states like MISSREF and AUTH48) has been running around
6-7 weeks. That's a far cry from 100 days.

Peter


From brian.e.carpenter@gmail.com  Tue May  7 14:19:40 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D93C721F90B3 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 14:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5mSIjbePUZFq for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 14:19:35 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0F25121F905F for <ietf@ietf.org>; Tue,  7 May 2013 14:19:35 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id 10so716654pdi.15 for <ietf@ietf.org>; Tue, 07 May 2013 14:19:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5d7V5NA6lpykQEussAo9n23vVB66eyxPm/NJUX+Vx6M=; b=sa6T4644OpIBrVS+2bAXYAMDdVUTW7g1isXGS5UyUvHzXFIjkvIPUNBIL3RCOpDu27 Pvd26BJzz2tB6y1jN/RyJ9hdQDOyUyZSPm4yzLBSu5035uUYyknRxnGP71rEMeD68dy+ wSaSBjsJE28sTph24JG45emwQsShsx6VgAItET+oXcgpo1Aud99iVERE4V5td6rc+o5m d/heWRKW4xCvxAbl6iEbAAAwYIqmrjJ8/OseprFKKREVJOm0dp8mqm5W34yTlx4fAs6Y vJznyAIGX+LyoZwjvlwJV9YYXGFsC/cODrpnG6bxYVrKt5fdmfqG3hj3RAo4goMv45ck EspA==
X-Received: by 10.68.232.42 with SMTP id tl10mr4299478pbc.72.1367961574817; Tue, 07 May 2013 14:19:34 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id fa5sm29580615pbb.35.2013.05.07.14.19.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 May 2013 14:19:33 -0700 (PDT)
Message-ID: <51896FE6.9080303@gmail.com>
Date: Wed, 08 May 2013 09:19:34 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Language editing
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <1F9DA0977DABC51DA2EF9963@[192.168.1.128]> <01OTCWZOSHC0000054@mauve.mrochek.com> <5AB71E192C2AE7DACE70630B@[192.168.1.128]> <51895E92.1020303@gmail.com> <01OTD824BDK6000054@mauve.mrochek.com>
In-Reply-To: <01OTD824BDK6000054@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, yaronf.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 21:19:41 -0000

On 08/05/2013 08:33, Ned Freed wrote:
>> On 08/05/2013 03:28, John C Klensin wrote:
>> ...
>>>> I'll also point out that this has diddley-squat to do with
>>>> formal verification processes. Again as Mark Anrdrews points
>>>> out, we deployed something with a restriction that
>>>> subsequently turned out to be unnecessary, and now we're stuck
>>>> with it. Indeed, had formal verification processes been
>>>> properly used, they would have flagged any attempt to change
>>>> this as breaking interoperability.
>>> Also agreed.
> 
>> To be clear, I'm no fan of formal verification either, but this
>> *is* a case where the IETF's lapse in formality has come back to
>> bite, and the Postel principle would have helped. Also, given the
>> original subject of the thread, I don't see how language editing
>> could have made any difference.
> 
> Reread the notes about the history behind this in this thread. You haven't even
> come close to making a case that formal verification of the standards would
> have prevented this from happening. 

You are correct if only considering the mail standards. I suspect
that a serious attempt at formal verification would have thrown
up an inconsistency between the set of mail-related standards and
the URI standard. However, I think the underlying problem here is
that we ended up defining the text representation of IPv6 addresses
in three different places, rather than having a single normative
source. (ABNF in the mail standards, ABNF in the URI standard,
and English in ipv6/6man standards.)

> (Formal verification of implementation
> compliance to the standards would of course have prevented Apple's client bug,
> but that's a very different thing.)
> 
> You are, however, correct that this has nothing to do with specification
> editing.
> 
> 				Ned
> 

From randy_presuhn@mindspring.com  Tue May  7 14:37:56 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7858921F90DF for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 14:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rhJ2QevFZLS for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 14:37:43 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 46A4E21F8F53 for <ietf@ietf.org>; Tue,  7 May 2013 14:37:43 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=d8K2fHgQLmQp3TMsHNZhVME9L1utbm6JwoV7EPMami/J255STYvB+1lWyAfErupg; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [76.254.50.245] (helo=oemcomputer) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UZpZu-0005Aw-CL for ietf@ietf.org; Tue, 07 May 2013 17:37:42 -0400
Message-ID: <005e01ce4b6b$856389c0$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "IETF Discussion" <ietf@ietf.org>
References: <mailman.21.1367521206.21891.ietf@ietf.org><5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org><51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com><51843485.90802@gmail.com><D80C0D989A6138451CD9F852@[192.168.1.128]><290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk><51881140.5070904@gmail.com><1F9DA0977DABC51DA2EF9963@[192.168.1.128]><01OTCWZOSHC0000054@mauve.mrochek.com><5AB71E192C2AE7DACE70630B@[192.168.1.128]><51895E92.1020303@gmail.com> <01OTD824BDK6000054@mauve.mrochek.com> <51896FE6.9080303@gmail.com>
Subject: Re: Language editing
Date: Tue, 7 May 2013 14:40:40 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88880ff2f3e23ebe946602c7a0a9d902fe25320999ab7f4f3f5350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 76.254.50.245
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 May 2013 21:37:56 -0000

Hi -

> From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> To: "Ned Freed" <ned.freed@mrochek.com>
> Cc: "John C Klensin" <john-ietf@jck.com>; <yaronf.ietf@gmail.com>; <ietf@ietf.org>
> Sent: Tuesday, May 07, 2013 2:19 PM
> Subject: Re: Language editing
...
> You are correct if only considering the mail standards. I suspect
> that a serious attempt at formal verification would have thrown
> up an inconsistency between the set of mail-related standards and
> the URI standard. However, I think the underlying problem here is
> that we ended up defining the text representation of IPv6 addresses
> in three different places, rather than having a single normative
> source. (ABNF in the mail standards, ABNF in the URI standard,
> and English in ipv6/6man standards.)
> 
> > (Formal verification of implementation
> > compliance to the standards would of course have prevented Apple's client bug,
> > but that's a very different thing.)
> > 
> > You are, however, correct that this has nothing to do with specification
> > editing.
> > 
> > Ned

I'm not so sure about that.  To me this seems to be a case of
inappropriate use of MUST.  First a reminder from RFC 2119:

   In particular, they MUST only be used where it is
   actually required for interoperation or to limit behavior which has
   potential for causing harm (e.g., limiting retransmisssions)

The prohibition against using :: more than once is amply motivated.
Multiple occurrances would introduce ambiguities, so that prohibition
clearly warrants a MUST.

The prohibition against using :: for a single 0 seems to lack
such an obvious syntactic / semantic motivation.  Does anyone
remember why this syntactic limitation was added?

Randy


From ned+ietf@mauve.mrochek.com  Tue May  7 16:34:14 2013
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD2911E80A4 for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 16:34:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e5ITFyoVxJAz for <ietf@ietfa.amsl.com>; Tue,  7 May 2013 16:34:09 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0578C21F8F87 for <ietf@ietf.org>; Tue,  7 May 2013 16:34:08 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OTDE40H9BK005H27@mauve.mrochek.com> for ietf@ietf.org; Tue, 7 May 2013 16:29:05 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OT3BOFFH80000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 7 May 2013 16:28:59 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OTDE3VYJQC000054@mauve.mrochek.com>
Date: Tue, 07 May 2013 16:17:40 -0700 (PDT)
Subject: Re: Language editing
In-reply-to: "Your message dated Wed, 08 May 2013 09:19:34 +1200" <51896FE6.9080303@gmail.com>
References: <mailman.21.1367521206.21891.ietf@ietf.org> <5182DD64.7040205@gmail.com> <5182E2A8.50800@acm.org> <51839ABA.4010406@internet2.edu> <51842A94.6060505@gmail.com> <51843485.90802@gmail.com> <D80C0D989A6138451CD9F852@[192.168.1.128]> <290E20B455C66743BE178C5C84F12408223F494E86@EXMB01CMS.surrey.ac.uk> <51881140.5070904@gmail.com> <1F9DA0977DABC51DA2EF9963@[192.168.1.128]> <01OTCWZOSHC0000054@mauve.mrochek.com> <5AB71E192C2AE7DACE70630B@[192.168.1.128]> <51895E92.1020303@gmail.com> <01OTD824BDK6000054@mauve.mrochek.com> <51896FE6.9080303@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: John C Klensin <john-ietf@jck.com>, yaronf.ietf@gmail.com, Ned Freed <ned.freed@mrochek.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, 07 May 2013 23:34:14 -0000

> On 08/05/2013 08:33, Ned Freed wrote:
> >> On 08/05/2013 03:28, John C Klensin wrote:
> >> ...
> >>>> I'll also point out that this has diddley-squat to do with
> >>>> formal verification processes. Again as Mark Anrdrews points
> >>>> out, we deployed something with a restriction that
> >>>> subsequently turned out to be unnecessary, and now we're stuck
> >>>> with it. Indeed, had formal verification processes been
> >>>> properly used, they would have flagged any attempt to change
> >>>> this as breaking interoperability.
> >>> Also agreed.
> >
> >> To be clear, I'm no fan of formal verification either, but this
> >> *is* a case where the IETF's lapse in formality has come back to
> >> bite, and the Postel principle would have helped. Also, given the
> >> original subject of the thread, I don't see how language editing
> >> could have made any difference.
> >
> > Reread the notes about the history behind this in this thread. You haven't even
> > come close to making a case that formal verification of the standards would
> > have prevented this from happening.

> You are correct if only considering the mail standards. I suspect
> that a serious attempt at formal verification would have thrown
> up an inconsistency between the set of mail-related standards and
> the URI standard.

Which is relevant to the present situation... how exactly? And in any case, the
relevant URI standard incorporates the ABNF from RFC 2373, but doesn't
state whether or not it also inherits restrictions specified in prose
in that specification, which is where the restriction in RFC 2821
originated.

> However, I think the underlying problem here is
> that we ended up defining the text representation of IPv6 addresses
> in three different places, rather than having a single normative
> source. (ABNF in the mail standards, ABNF in the URI standard,
> and English in ipv6/6man standards.)

Except that wasn't the problem. The ABNF in the email standards is
consistent with what the other standards said when RFC 2821 was published. And
once that happened the die was cast as far as email usage was concerned. The
fact that the other standards later decided to loosen the rules in this
regard is what caused the inconsistency.

If you want to blame something, it has to be either the initial decision to
limit use of :: or the subsequent decision to remove that limit. And for
increased formalism to have helped it would have to have prevented one of those
from happening. I supose that's possible, but I certainly don't see it as
inevitable.

				Ned

From rse@rfc-editor.org  Wed May  8 02:07:58 2013
Return-Path: <rse@rfc-editor.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 6CED221F8F2E for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 02:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SMNh5G2GTI-G for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 02:07:53 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 0C76E21F8FDB for <ietf@ietf.org>; Wed,  8 May 2013 02:07:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0963D128BB4 for <ietf@ietf.org>; Wed,  8 May 2013 02:07:46 -0700 (PDT)
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 tdX1tDUSygvz for <ietf@ietf.org>; Wed,  8 May 2013 02:07:45 -0700 (PDT)
Received: from Heathers-MacBook-Pro.local (unknown [193.1.64.8]) by c8a.amsl.com (Postfix) with ESMTPSA id 920FC128BAE for <ietf@ietf.org>; Wed,  8 May 2013 02:07:45 -0700 (PDT)
Message-ID: <518A15E3.7040707@rfc-editor.org>
Date: Wed, 08 May 2013 10:07:47 +0100
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net> <51896896.80706@stpeter.im>
In-Reply-To: <51896896.80706@stpeter.im>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 08 May 2013 08:03:40 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2013 09:07:58 -0000

On 5/7/13 9:48 PM, Peter Saint-Andre wrote:
> On 5/2/13 4:58 PM, Dave Crocker wrote:
>> On 5/2/2013 3:25 PM, Jari Arkko wrote:
>>> But the delay was really not my main concern. Primarily because I
>>> think other issues such as transparency to the working group or late
>>> surprises are more fundamental issues than mere timing. But also
>>> because I actually*do*  have some statistics that seem to indicate
>>> that, overall, the last phase still goes through pretty quickly. Look
>>> athttp://www.arkko.com/tools/lifecycle/wgdocs.html  and compare the
>>> WG, IESG, and RFC editor times in the first graph. The WG time
>>> dominates. (I said "seem to indicate" because the results are pretty
>>> dated and I'm not really sure how valid they are, but they match at
>>> least my intuitive experience.) Not saying delay reduction wouldn't be
>>> useful, the overall times are still very long, and the IETF last call
>>> - IESG time is still a significant component. Just that delay would
>>> not be my primary
>>
>>
>> Jari,
>>
>> Very interesting set of graphs.  Thanks!
>>
>>
>> Doing very rough eyeballing of the "left side" averages against the
>> "right side" averages -- that is, considering how things have changed
>> over the last 10 years -- it looks like:
>>
>>      Working groups were taking around 500 days and now take around 600.
>>
>>      The IESG was taking around 200 days and now takes around 110.
>>
>>      The RFC then and now takes around 100 days (with lots of variation
>> between the then and the now, of course.)
> 
> I'm curious what exactly falls under the RFC Editor phase. My impression
> from recent plenaries is that the purely RFC Editor responsibilities
> (not including states like MISSREF and AUTH48) has been running around
> 6-7 weeks. That's a far cry from 100 days.
> 

You are correct, Peter.  MISSREF and AUTH48 are not part of the RFC
Editor timed states, and the RFC Editor timed states have been largely
under 7 weeks for the last year.

If anyone is curious about current stats, which includes average times
in AUTH48 and MISSREF, see http://www.rfc-editor.org/CurrQstats.txt

Heather Flanagan, RSE


From jari.arkko@piuha.net  Wed May  8 08:50:37 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6541221F87D0 for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 08:50:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aFvhKQY+0hU7 for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 08:50:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CDD1C21F93F4 for <ietf@ietf.org>; Wed,  8 May 2013 08:50:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7D8C72CC5D; Wed,  8 May 2013 18:50:30 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RjwB96ge253q; Wed,  8 May 2013 18:50:29 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id BF8F62CC48; Wed,  8 May 2013 18:50:29 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <518A15E3.7040707@rfc-editor.org>
Date: Wed, 8 May 2013 16:50:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net> <51896896.80706@stpeter.im> <518A15E3.7040707@rfc-editor.org>
To: Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org>
X-Mailer: Apple Mail (2.1503)
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, 08 May 2013 15:50:37 -0000

Heather, all,

> You are correct, Peter.  MISSREF and AUTH48 are not part of the RFC
> Editor timed states, and the RFC Editor timed states have been largely
> under 7 weeks for the last year.

Indeed. The actual time for what RFC Editor does for documents is quite =
short (and thank you and others at the RFC Editor side for that!).

My stats counted both MISSREF and AUTH48, I think.

Jari


From mrex@sap.com  Wed May  8 09:54:52 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10BD621F9610 for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 09:54:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEpczB551Qvx for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 09:54:43 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0466B21F94A4 for <ietf@ietf.org>; Wed,  8 May 2013 09:54:42 -0700 (PDT)
Received: from mail06.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r48GseZc007743 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 8 May 2013 18:54:40 +0200 (MEST)
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <CF914474-0AEF-4196-9A24-10E042434D55@NLnetLabs.nl>
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Date: Wed, 8 May 2013 18:54:40 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130508165440.C6DE21A6F4@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Carsten Bormann <cabo@tzi.org>, IETF list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2013 16:54:52 -0000

Olaf Kolkman wrote:
> 
> Where things become difficult is at the point where the maintenance
> of our standards need to be explained and questions about progression
> on the standards ladder get asked. 
> 
> Personally I hope that RFC 6410 has the effect that we, as a community,
> get serious about promoting our proposed standards, or obsolete them. 
> 
> I wonder how many standards got promoted after 6410 was published.

One significant problem is that in the few working groups (in the security
area) that I'm tracking, there appears to be a constituency behind every
(formally provable) breakage and every non-trivial omission that makes
it impossible to ever progress the documents beyong proposed.

And the IESG seems OK with waiving the breakage when documents are
recycled on proposed, rather than requiring WGs to fix it when
problems are identified during LC of a bis document.

-Martin


From sm@elandsys.com  Wed May  8 10:07:05 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1A3021F90C3; Wed,  8 May 2013 10:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sgd6ZJUJtWLx; Wed,  8 May 2013 10:07:04 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D071321F9121; Wed,  8 May 2013 10:07:04 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.145.230]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r48H6gFR011969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 May 2013 10:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368032821; bh=VqGmhoCTZLT7tdGw9bsAEdoIzPCdQAiNjBel/0JE+kI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Fp5hRMoV9DOwuuo0iYb9JlgBYcd9yvmLdS17YW/QX2kklzyh4sdI6OvCEwjfgv9Ou yjrCon8iSHGbK8g/FA2W4A6xUWvV7ORJtfPflQ9TlbTtwJkbGlQgD2EmMlcD6qWr6c gKtzQq1HFWibkf2hGo+cgp4/2Z9Ym8AhcxOvZTtg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1368032821; i=@elandsys.com; bh=VqGmhoCTZLT7tdGw9bsAEdoIzPCdQAiNjBel/0JE+kI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QaFqeDnopAPyM3olNhdi8PYzI6VixU2ZUY7u0Tw5JS4AQsshtI16WHGUbIGCYgZyf Dmhgqd6Racrhv4UJlRk2AQyAtwvyYygIMFLf0fRM6jHfJr3QNh6ohqSUcsr/CEiPCc M2IqXlNjJ5b6YLa+vh/WeP7npUBDh0xi+VxHMNKs=
Message-Id: <6.2.5.6.2.20130508092054.0c02f378@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 08 May 2013 10:03:43 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
In-Reply-To: <20130430083206.GD46852@elstar.local>
References: <6.2.5.6.2.20130428233426.0b62fed0@elandnews.com> <20130430083206.GD46852@elstar.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2013 17:07:05 -0000

At 01:32 30-04-2013, Juergen Schoenwaelder wrote:
>I am not sure what you think is unclear. Note that the definition of
>the typedef domain-name is unchanged from the one in RFC 6021. Perhaps
>you can make a concrete text change proposal so I better understand
>what your concern is.

I read draft-ietf-netmod-rfc6021-bis-02.  In Section 4:

   "The domain-name type represents a DNS domain name.  The
    name SHOULD be fully qualified whenever possible."

That sounds like a MAY.

The text in RFC 6021 and the draft is clear.  I don't think that the 
fact that DNS-related text is already in RFC 6021 means that it is correct.

   "Internationalized domain names MUST be encoded in punycode as described
    in RFC 3492";

RFC 5891 discusses about IDNA-aware implementations.  It also 
discusses about A-labels and U-labels.  The above text jumps directly 
to punycode.

Regards,
S. Moonesamy



From daedulus@btconnect.com  Wed May  8 10:48:28 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02C9421F91AB for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 10:48:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.045
X-Spam-Level: 
X-Spam-Status: No, score=0.045 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DATE_IN_PAST_03_06=0.044]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Ql2l68bMnam for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 10:48:23 -0700 (PDT)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0184.outbound.messaging.microsoft.com [213.199.154.184]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF3521F8F38 for <ietf@ietf.org>; Wed,  8 May 2013 10:48:22 -0700 (PDT)
Received: from mail76-db8-R.bigfish.com (10.174.8.226) by DB8EHSOBE008.bigfish.com (10.174.4.71) with Microsoft SMTP Server id 14.1.225.23; Wed, 8 May 2013 17:48:21 +0000
Received: from mail76-db8 (localhost [127.0.0.1])	by mail76-db8-R.bigfish.com (Postfix) with ESMTP id 3E030C40092	for <ietf@ietf.org>; Wed,  8 May 2013 17:48:21 +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: -11
X-BigFish: PS-11(zzzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m35h1155h)
Received: from mail76-db8 (localhost.localdomain [127.0.0.1]) by mail76-db8 (MessageSwitch) id 1368035299878121_7327; Wed,  8 May 2013 17:48:19 +0000 (UTC)
Received: from DB8EHSMHS002.bigfish.com (unknown [10.174.8.247])	by mail76-db8.bigfish.com (Postfix) with ESMTP id D3D242C0066	for <ietf@ietf.org>; Wed,  8 May 2013 17:48:19 +0000 (UTC)
Received: from DBXPRD0710HT003.eurprd07.prod.outlook.com (157.56.253.197) by DB8EHSMHS002.bigfish.com (10.174.4.12) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 8 May 2013 17:48:16 +0000
Received: from DBXPRD0611HT003.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.79.166) with Microsoft SMTP Server (TLS) id 14.16.305.3; Wed, 8 May 2013 17:48:15 +0000
Message-ID: <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: t.p. <daedulus@btconnect.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org><50992BEF.9000803@gmail.com><C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net>
Subject: Accessing tools from IETF pages
Date: Wed, 8 May 2013 15:05:11 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-FOPE-CRA-SourceIpAddress: 157.56.253.197
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-OriginatorOrg: btconnect.com
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, 08 May 2013 17:48:28 -0000

I wanted to submit an I-D so I wanted to access the tools, as I have
done before, so I clicked on 'IETF Tools' from
http://datatracker.ietf.org/wg/
and when that failed tried again with 'Tools Team Pages' from
http://www.ietf.org/iesg/
with the same result.  Can anyone else get to tools from that link?

It resolves to
http://tools.ietf.org/
which Internet Explorer (what else?) assures me cannot be displayed,
either from the link or from typing it into the Open drop down.

The trouble ticket drew a response of

"It sounds like the tools pages were experiencing some issues that have
now been resolved."

Well, for a few milliseconds, perhaps, but I get the same response
24x7x365x...

Not that easily put off, I found a way around it (thank you, Google),
but in the spirit of wanting others to be able to do what I can (with
some difficulty) do, I would like those links to work (or to disappear).

Tom Petch



From elwynd@dial.pipex.com  Wed May  8 12:15:37 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3A7321F91B7; Wed,  8 May 2013 12:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.465
X-Spam-Level: 
X-Spam-Status: No, score=-102.465 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTTP_ESCAPED_HOST=0.134, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7E9aSO-I8YVT; Wed,  8 May 2013 12:15:36 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8C621F9130; Wed,  8 May 2013 12:15:36 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1Ua9pq-0005nR-Sv; Wed, 08 May 2013 20:15:34 +0100
Subject: Re: Accessing tools from IETF pages
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "t.p." <daedulus@btconnect.com>
In-Reply-To: <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.net>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net> <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain
Date: Wed, 08 May 2013 20:08:07 +0100
Message-Id: <1368040087.5273.14409.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
X-Spam-Score-a.painless.aa.net.uk: -2.9
Cc: IETF discussion <ietf@ietf.org>, IETF tools discussion <tools-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, 08 May 2013 19:15:37 -0000

Both links work just fine from a selection of browsers/os/machines other
than Msoft. (Firefox, Evolution, Chrome)  It also works on an old
version of IE8 but reports errors.

Presumably turning off some strict error checking in IE allows it to
display.

Running the page through the W3C HTML validator reports 14 Errors and 3
Warnings:
http://validator.w3.org/check?uri=http%3A%2F%2Ftools.ietf.org%
2F&charset=%28detect+automatically%
29&doctype=Inline&group=0&user-agent=W3C_Validator%2F1.3+http%3A%2F%
2Fvalidator.w3.org%2Fservices

/Elwyn

On Wed, 2013-05-08 at 15:05 +0100, t.p. wrote:
> I wanted to submit an I-D so I wanted to access the tools, as I have
> done before, so I clicked on 'IETF Tools' from
> http://datatracker.ietf.org/wg/
> and when that failed tried again with 'Tools Team Pages' from
> http://www.ietf.org/iesg/
> with the same result.  Can anyone else get to tools from that link?
> 
> It resolves to
> http://tools.ietf.org/
> which Internet Explorer (what else?) assures me cannot be displayed,
> either from the link or from typing it into the Open drop down.
> 
> The trouble ticket drew a response of
> 
> "It sounds like the tools pages were experiencing some issues that have
> now been resolved."
> 
> Well, for a few milliseconds, perhaps, but I get the same response
> 24x7x365x...
> 
> Not that easily put off, I found a way around it (thank you, Google),
> but in the spirit of wanting others to be able to do what I can (with
> some difficulty) do, I would like those links to work (or to disappear).
> 
> Tom Petch
> 
> 


From worley@shell01.TheWorld.com  Wed May  8 12:38:07 2013
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 3171221F8EE1 for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 12:38:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[AWL=0.540,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cj1xrfmbIJ1k for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 12:38:02 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 695B021F8EF7 for <ietf@ietf.org>; Wed,  8 May 2013 12:38:02 -0700 (PDT)
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 r48Jbmi3000831; Wed, 8 May 2013 15:37:50 -0400
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 r48Jbl7m4364613; Wed, 8 May 2013 15:37:47 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r48JbjTQ4388434; Wed, 8 May 2013 15:37:45 -0400 (EDT)
Date: Wed, 8 May 2013 15:37:45 -0400 (EDT)
Message-Id: <201305081937.r48JbjTQ4388434@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: "t.p." <daedulus@btconnect.com>
In-reply-to: <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.net> (daedulus@btconnect.com)
Subject: Re: Accessing tools from IETF pages
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org><50992BEF.9000803@gmail.com><C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net> <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.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: Wed, 08 May 2013 19:38:07 -0000

> From: "t.p." <daedulus@btconnect.com>
> 
> I wanted to submit an I-D so I wanted to access the tools, as I have
> done before, so I clicked on 'IETF Tools' from
> http://datatracker.ietf.org/wg/
> and when that failed tried again with 'Tools Team Pages' from
> http://www.ietf.org/iesg/
> with the same result.  Can anyone else get to tools from that link?
> 
> It resolves to
> http://tools.ietf.org/
> which Internet Explorer (what else?) assures me cannot be displayed,
> either from the link or from typing it into the Open drop down.

Well, all three of those links work for me at "May 8 19:33:01 UTC
2013" using Firefox 18.0.2 on Linux.  (For whatever that is worth.)

I'd sniff the HTTP transaction to get some information on the specific
failure mode.

Dale

From randy@psg.com  Wed May  8 12:53:08 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F205B21F8ADF; Wed,  8 May 2013 12:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmAkAVyRm-Sx; Wed,  8 May 2013 12:53:07 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 85AD521F89FF; Wed,  8 May 2013 12:53:07 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UaAQB-000GQy-3V; Wed, 08 May 2013 19:53:03 +0000
Date: Wed, 08 May 2013 21:53:01 +0200
Message-ID: <m2a9o5ckpu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
In-Reply-To: <6.2.5.6.2.20130508092054.0c02f378@resistor.net>
References: <6.2.5.6.2.20130428233426.0b62fed0@elandnews.com> <20130430083206.GD46852@elstar.local> <6.2.5.6.2.20130508092054.0c02f378@resistor.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2013 19:53:08 -0000

>    "The domain-name type represents a DNS domain name.  The
>     name SHOULD be fully qualified whenever possible."
> 
> That sounds like a MAY.

MAY != SHOULD

From sm@elandsys.com  Wed May  8 14:30:29 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F019D21F8ED8; Wed,  8 May 2013 14:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.195
X-Spam-Level: 
X-Spam-Status: No, score=-102.195 tagged_above=-999 required=5 tests=[AWL=0.404, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-NO0SqDSG3Y; Wed,  8 May 2013 14:30:29 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3402221F884F; Wed,  8 May 2013 14:30:28 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.145.230]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r48LUEZH005813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 May 2013 14:30:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368048627; bh=OA9vcS4BW/kx8g9pAuYDkazTHpkIu9UlOHgrVccQ/1o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LIGwws4am02FKeDoFRUVk4AWvSfoVGOw0O8Do0NDOhlmdEd/Hz4VrC6wpMotFybLf PTBhQ01vMya6Paf1vmKhDeMPQQKWh626xwpIkgF5puooi3+iu39WuohZk4teur3GbO uHPJIX2+Z9ClmbyRXd67+F+klFSJSqkxLniNjsJ4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1368048627; i=@elandsys.com; bh=OA9vcS4BW/kx8g9pAuYDkazTHpkIu9UlOHgrVccQ/1o=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=IQ9RbsVw+S5T8kz1AAimow5cQ5moKT2ybR0w5rl+dd4Hk8xJhKlg0njCzHOMvqyv+ zWOLHTA5f92U0lx+xbJJc1EkrhllXGSIIrsQcWDp2xhy+9v8Yxajw8W0h2ekloYOAL MHMwWvMZTPAD225c+IqdmEAPQKD5jVrZ0x/uRA+Q=
Message-Id: <6.2.5.6.2.20130508130025.0c082b18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 08 May 2013 13:44:44 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
In-Reply-To: <m2a9o5ckpu.wl%randy@psg.com>
References: <6.2.5.6.2.20130428233426.0b62fed0@elandnews.com> <20130430083206.GD46852@elstar.local> <6.2.5.6.2.20130508092054.0c02f378@resistor.net> <m2a9o5ckpu.wl%randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2013 21:30:30 -0000

At 12:53 08-05-2013, Randy Bush wrote:
>MAY != SHOULD

The text is as follows: "The name SHOULD be fully qualified whenever 
possible".  If the working group would like a RFC 2119 SHOULD it 
would help if there is an explanation in the sentence for the reader 
weigh the implications of not following that.

For what it is worth Eric Burger posted an analysis of "SHOULD" usage 
in a different draft ( 
http://www.ietf.org/mail-archive/web/mile/current/msg01021.html ).

Regards,
S. Moonesamy 


From jabley@hopcount.ca  Wed May  8 14:55:50 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B10421F8721 for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 14:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o04ETFTkcvPU for <ietf@ietfa.amsl.com>; Wed,  8 May 2013 14:55:49 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A55D721F86F0 for <ietf@ietf.org>; Wed,  8 May 2013 14:55:49 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s11so1342279qcw.15 for <ietf@ietf.org>; Wed, 08 May 2013 14:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=x-received:references:from:mime-version:in-reply-to:date:message-id :subject:to:cc:content-type; bh=wBcZ/bmQOh0G1PYVdxCD2be+H62RdbgXN7M9Y0ch+oA=; b=mYjFy2M/rDPQJaTT+S71C6K4ibnslLETm5KC/Xri0e2qIigwl4JNFgjj+Ssp5Y4Vo+ JMznLzpbvH3ly38IztWwU7hPviK2mGnk/YH4ilAbl9Ul3zPgDJsFhZ1CW3/70dU/Phwj /Ntacix7FKu/jjyCjxNpMNDevdRFgRIJDEFL4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:from:mime-version:in-reply-to:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=wBcZ/bmQOh0G1PYVdxCD2be+H62RdbgXN7M9Y0ch+oA=; b=F8b24wgD8NUheUYpfDrlyBM/vuMYdu/quO4ApkVxENhmiIk+8krDYWgcL92woBDX1g jJNiepYTd2s5nyfYh4o7DWMJnG/mIMamlmmwejgevBOfrWF1tSogn4a7P1m5lf30xB9c BCrC43WBqGJcjFIpFYCozs7KU+c2Dpzskn8qHWJXoEFBiu1qm41VqsQuXvZYbLOdTyEK W9hA83hE/E+iNFM0XzK/0JwGSZIunBqBG7+xj2BEGnfOSAztb2ONRZaexkykGFqKgc1q wV+QRRcXP61vgonyqZ2ICJ1ajlEixpPyBEiaIGyejDWWcTWA+SONUopT2kWO0BsIE87u tLVw==
X-Received: by 10.49.104.37 with SMTP id gb5mr7314169qeb.41.1368050149092; Wed, 08 May 2013 14:55:49 -0700 (PDT)
References: <6.2.5.6.2.20130428233426.0b62fed0@elandnews.com> <20130430083206.GD46852@elstar.local> <6.2.5.6.2.20130508092054.0c02f378@resistor.net> <m2a9o5ckpu.wl%randy@psg.com> <6.2.5.6.2.20130508130025.0c082b18@elandnews.com>
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
In-Reply-To: <6.2.5.6.2.20130508130025.0c082b18@elandnews.com>
Date: Wed, 8 May 2013 17:55:49 -0400
Message-ID: <2604527301889679776@unknownmsgid>
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQkT5jfAXFtJxnwNoDLXnMpD/5tvLQsfyqTr4Vop/DV5dzkzIO4u3Ewh7AdC976E7+AUUN+s
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, "ietf@ietf.org" <ietf@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 May 2013 21:55:50 -0000

On 2013-05-08, at 17:30, S Moonesamy <sm+ietf@elandsys.com> wrote:

> At 12:53 08-05-2013, Randy Bush wrote:
>> MAY != SHOULD
>
> The text is as follows: "The name SHOULD be fully qualified whenever possible".  If the working group would like a RFC 2119 SHOULD it would help if there is an explanation in the sentence for the reader weigh the implications of not following that.

My knee-jerk reaction is to use MUST. Partially-qualified domain names
are ambiguous at best.

Similarly, "wherever possible" is unhelpful; if it's not possible to
fully-qualify a domain name then ambiguity is guaranteed.


Joe

From mrex@sap.com  Wed May  8 23:31:25 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC4821F859D; Wed,  8 May 2013 23:31:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-QEQhpQyWMQ; Wed,  8 May 2013 23:31:20 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 3D99521F85C3; Wed,  8 May 2013 23:31:19 -0700 (PDT)
Received: from mail06.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r496V12V004323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 9 May 2013 08:31:01 +0200 (MEST)
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
In-Reply-To: <6.2.5.6.2.20130508092054.0c02f378@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
Date: Thu, 9 May 2013 08:31:01 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130509063101.3141D1A700@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 May 2013 06:31:25 -0000

S Moonesamy wrote:
> At 01:32 30-04-2013, Juergen Schoenwaelder wrote:
> >I am not sure what you think is unclear. Note that the definition of
> >the typedef domain-name is unchanged from the one in RFC 6021. Perhaps
> >you can make a concrete text change proposal so I better understand
> >what your concern is.
> 
> I read draft-ietf-netmod-rfc6021-bis-02.  In Section 4:
> 
>    "The domain-name type represents a DNS domain name.  The
>     name SHOULD be fully qualified whenever possible."
> 
> That sounds like a MAY.

That is a MAY.  That probably needs to be a may.

How do you recognize a "fully qualified" name anyway?


Today a huge number of machines simply does not have a
"fully qualified domain name" (and uses private address space).

My DSL router (a brand that is pretty common in Germany)
does _not_ provide a domain name via DHCP and will resolve
plain hostnames for all addresses that it hands out via DHCP.
And a lot of stuff that you attach to home networks comes
with a Web-UI (my DVB-S Set-Top Box, my HomeNAS, my DSL-router
(although the latter recognizes "fritz.box" as a name for itself).

-Martin

From randy@psg.com  Thu May  9 00:28:28 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2156121F8E2C for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 00:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rJ2PByp+YPNO for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 00:28:27 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 9A85E21F8F03 for <ietf@ietf.org>; Thu,  9 May 2013 00:28:27 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UaLH6-000Jcd-4V; Thu, 09 May 2013 07:28:24 +0000
Date: Thu, 09 May 2013 09:28:22 +0200
Message-ID: <m2vc6sboix.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
In-Reply-To: <2604527301889679776@unknownmsgid>
References: <6.2.5.6.2.20130428233426.0b62fed0@elandnews.com> <20130430083206.GD46852@elstar.local> <6.2.5.6.2.20130508092054.0c02f378@resistor.net> <m2a9o5ckpu.wl%randy@psg.com> <6.2.5.6.2.20130508130025.0c082b18@elandnews.com> <2604527301889679776@unknownmsgid>
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: Thu, 09 May 2013 07:28:28 -0000

>>> MAY != SHOULD
>> The text is as follows: "The name SHOULD be fully qualified whenever
>> possible".  If the working group would like a RFC 2119 SHOULD it
>> would help if there is an explanation in the sentence for the reader
>> weigh the implications of not following that.
> My knee-jerk reaction is to use MUST. Partially-qualified domain names
> are ambiguous at best.

that is a separate issue

> Similarly, "wherever possible" is unhelpful; if it's not possible to
> fully-qualify a domain name then ambiguity is guaranteed.

no, that is what SHOLD means.  e.g. when i write docco that has an ops
clause where there is likely a knob or other op choice, i do not think
i have the prerogative to tell the op how they MUST run their network.
but i can say that they SHOULD do x.

randy

From spencer@wonderhamster.org  Thu May  9 01:32:26 2013
Return-Path: <spencer@wonderhamster.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 4964F21F8F0A for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 01:32:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HTXlgVRK2at for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 01:32:20 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1B621F8F07 for <ietf@ietf.org>; Thu,  9 May 2013 01:32:20 -0700 (PDT)
Received: from [192.168.182.129] (csopen.scss.tcd.ie [134.226.52.39]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0LoWaA-1U2v8D1DlC-00goiR; Thu, 09 May 2013 04:32:15 -0400
Message-ID: <518B5F0D.4070802@wonderhamster.org>
Date: Thu, 09 May 2013 03:32:13 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net> <51896896.80706@stpeter.im> <518A15E3.7040707@rfc-editor.org> <DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net>
In-Reply-To: <DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:Un/dixkOe+ZCnm3Pd/Y53VlQqjtVo1SxbzLbC+Nt8qU NGnRil+GYR2LLQngSbtDFo7oy4ZhLQVGeu5KxOT1GZyYGclwld fEQxF97iN1nN5cAZ7khqu3xQlrazX5lp3fw7pJWhu7P82NTxGY h7ai9cWdWNrd+Kl1XvmVzxBcpG+S7ZifG75C+yRu/ubtyEU1Y6 28BNJLGYZCxo2NhO/CK3A0AxH0VhSK6hBurvWv/v3J9HzGpcGL DBwHIjBWE8pnje1ytpLNy5AtgCFZtdU+rT3Qp+BqxEmqxO5mzw NMeEaojm0Sl3c2mpc1+5U+WCUN9MZjOWuxEBBFXQg9Xco8tbXs 9tlafphaIf/D2kp/yBY2ixNFyIojJEMlQQq9sxhM9
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.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, 09 May 2013 08:32:26 -0000

On 5/8/2013 10:50 AM, Jari Arkko wrote:
> Heather, all,
>
>> You are correct, Peter.  MISSREF and AUTH48 are not part of the RFC
>> Editor timed states, and the RFC Editor timed states have been largely
>> under 7 weeks for the last year.
>
> Indeed. The actual time for what RFC Editor does for documents is quite short (and thank you and others at the RFC Editor side for that!).
>
> My stats counted both MISSREF and AUTH48, I think.

I remember that when this was previously discussed (mid-2000s), we noted 
that the states didn't map 1:1 with who had to actually do something. 
Sounds like this is still true.

So in this case, we're looking at "RFC Editor state" = "Heather, please 
do something" + "some working group, please do something" + "author(s), 
please do something", and we can't tell how much time to attribute to 
each of these ...

Spencer


From john-ietf@jck.com  Thu May  9 06:07:02 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4FB21F8FFC for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 06:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KSe1jkmYQ61 for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 06:06:50 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9E521F8E4C for <ietf@ietf.org>; Thu,  9 May 2013 06:06:50 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UaQYT-000Cuc-Er; Thu, 09 May 2013 09:06:41 -0400
Date: Thu, 09 May 2013 09:06:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Joe Abley <jabley@hopcount.ca>
Subject: Re: APPSDIR review of draft-ietf-netmod-rfc6021-bis-01
Message-ID: <DDF6E544CB7F1A705F95F8DE@JcK-HP8200.jck.com>
In-Reply-To: <m2vc6sboix.wl%randy@psg.com>
References: <6.2.5.6.2.20130428233426.0b62fed0@elandnews.com> <20130430083206.GD46852@elstar.local> <6.2.5.6.2.20130508092054.0c02f378@resistor.net> <m2a9o5ckpu.wl%randy@psg.com> <6.2.5.6.2.20130508130025.0c082b18@elandnews.com> <2604527301889679776@unknownmsgid> <m2vc6sboix.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: Thu, 09 May 2013 13:07:02 -0000

--On Thursday, May 09, 2013 09:28 +0200 Randy Bush
<randy@psg.com> wrote:

>> Similarly, "wherever possible" is unhelpful; if it's not
>> possible to fully-qualify a domain name then ambiguity is
>> guaranteed.
> 
> no, that is what SHOLD means.  e.g. when i write docco that
> has an ops clause where there is likely a knob or other op
> choice, i do not think i have the prerogative to tell the op
> how they MUST run their network. but i can say that they
> SHOULD do x.

If you are writing a protocol spec and you believe various bad
things can happen to you if partially-qualified names are used,
sure you do.  Whether your belief about possible damage and its
likelihood is reasonable is another question and that, IMO, is
the discussion we should be having.

Now that op has prerogatives too.   Because conformance to IETF
Standards is voluntary, it can ignore the MUST, leaving you the
option of calling the protocol police and/or deciding not to
deal with that op.  Or it could decide to not deal with you
because you make such unreasonable demands.  But neither of
those options deprive you, or the IETF, from saying "MUST" if
you are convinced it is necessary.  IMO, "necessary" should
include interoperability, security, or stable and predictable
operational reasons, despite 2119's apparent restriction to the
first of those.

best,
   john




From john-ietf@jck.com  Thu May  9 06:13:27 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC8721F91BF for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 06:13:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1hy2o0Kl-+co for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 06:13:21 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6850E21F900C for <ietf@ietf.org>; Thu,  9 May 2013 06:13:19 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UaQeo-000CvQ-1l; Thu, 09 May 2013 09:13:14 -0400
Date: Thu, 09 May 2013 09:13:06 -0400
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins <spencer@wonderhamster.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <AE98FA932FF026CB380D1262@JcK-HP8200.jck.com>
In-Reply-To: <518B5F0D.4070802@wonderhamster.org>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net> <51896896.80706@stpeter.im>	<518A15E3.7040707@rfc-editor.org> <DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net> <518B5F0D.4070802@wonderhamster.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.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, 09 May 2013 13:13:27 -0000

--On Thursday, May 09, 2013 03:32 -0500 Spencer Dawkins
<spencer@wonderhamster.org> wrote:

> So in this case, we're looking at "RFC Editor state" =
> "Heather, please do something" + "some working group, please
> do something" + "author(s), please do something", and we can't
> tell how much time to attribute to each of these ...

You could further add to that list "RFC Production Center,
please do something" (different from an RSE wait, which is, or
at least ought to be, more significant) and "IESG or appropriate
AD, please do something", which does happen.

But the RFC Editor's numbers try (almost always successfully) to
separate the two "waiting on the RFC Editor Function to do
something" (Heather plus Production Center plus, in principle,
Publisher) from the other states.  Those other states could,
from their point of view, be aggregated into "stuck, someone
else's problem".   If we are looking for issues with IETF
end-game process, we need to parse those, but that is a
different sort of question in terms of data-gathering and
reporting.

best,
   john




From brian.e.carpenter@gmail.com  Thu May  9 13:09:41 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6917021F8D2E for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 13:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T4PyykjzosJo for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 13:09:39 -0700 (PDT)
Received: from mail-ia0-x232.google.com (mail-ia0-x232.google.com [IPv6:2607:f8b0:4001:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3E07C21F8EBC for <ietf@ietf.org>; Thu,  9 May 2013 13:09:39 -0700 (PDT)
Received: by mail-ia0-f178.google.com with SMTP id t29so3572600iag.23 for <ietf@ietf.org>; Thu, 09 May 2013 13:09:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aZKr8G11IbnLFX7A76l5y8lKRrzWXvMOTNbylFDwMyg=; b=wEBa2Javem1rtlYY53Wk6C+qD62FsGWwa1mtl5mi0gyVo+xCZnaw1/wIymqZbLRNqm 3yPxuzjaobwyoCEId9V41q4i1Zutt9nTpx131x+Uk8/TMsSXXpTuAR0RLveUI7OFVvHO S/xNRD8xuw9WqmDHrKXyRySZ4gUS/0YQO7Pid3mek4hWD1WPMx/3PjuoVUxyEojZbT2U 26n2TLn/1dIb28NpQtc0M3SIu6Y/3s7e7R4nM9BPA7JxreA1zMWWHlcTQtkL2ZIVlPV+ lkONeGhsEnXBHvo6KbL6He7k2I0ETrph/EXJa8wZRIyoJI2vpWovJveAIMJ9Ew5zideN 74fw==
X-Received: by 10.50.12.3 with SMTP id u3mr6553954igb.1.1368130178847; Thu, 09 May 2013 13:09:38 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id c11sm6499620igv.1.2013.05.09.13.09.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 May 2013 13:09:37 -0700 (PDT)
Message-ID: <518C0282.1080101@gmail.com>
Date: Fri, 10 May 2013 08:09:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<5182AD0F.4010204@gmx.net>	<9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net>	<5182EFA3.30400@dcrocker.net>	<51896896.80706@stpeter.im>	<518A15E3.7040707@rfc-editor.org>	<DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net>	<518B5F0D.4070802@wonderhamster.org> <AE98FA932FF026CB380D1262@JcK-HP8200.jck.com>
In-Reply-To: <AE98FA932FF026CB380D1262@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.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, 09 May 2013 20:09:41 -0000

On 10/05/2013 01:13, John C Klensin wrote:
> 
> --On Thursday, May 09, 2013 03:32 -0500 Spencer Dawkins
> <spencer@wonderhamster.org> wrote:
> 
>> So in this case, we're looking at "RFC Editor state" =
>> "Heather, please do something" + "some working group, please
>> do something" + "author(s), please do something", and we can't
>> tell how much time to attribute to each of these ...
> 
> You could further add to that list "RFC Production Center,
> please do something" (different from an RSE wait, which is, or
> at least ought to be, more significant) and "IESG or appropriate
> AD, please do something", which does happen.
> 
> But the RFC Editor's numbers try (almost always successfully) to
> separate the two "waiting on the RFC Editor Function to do
> something" (Heather plus Production Center plus, in principle,
> Publisher) from the other states.  Those other states could,
> from their point of view, be aggregated into "stuck, someone
> else's problem".   If we are looking for issues with IETF
> end-game process, we need to parse those, but that is a
> different sort of question in terms of data-gathering and
> reporting.

All of which suggests that, ideally, the tracker would include
a variable "onTheHook" for each draft, containing at all times
the person or role responsible for the next step. That isn't
necessarily implied by the state machine. For example,
AUTH48 doesn't always imply that the author is on the hook -
it may be that the author has asked the WG Chair to ask the
WG for a quick review of a proposed last-minute change. At
that point, the WG as a whole is on the hook.

    Brian

From doug.mtview@gmail.com  Thu May  9 18:52:35 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3836521F90DF for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 18:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmWeayCSUiDR for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 18:52:30 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 7534F21F85EF for <ietf@ietf.org>; Thu,  9 May 2013 18:52:30 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id g10so2380359pdj.8 for <ietf@ietf.org>; Thu, 09 May 2013 18:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:date:message-id:cc:to :mime-version:x-mailer; bh=Q7z2XduqakO+I2dzBfyHB8tgZ61Ild8fsZ5tCkYVY5w=; b=wx7uFmv16Brmq3Rw7W86Q5eEInhuu3LWi/vtt9+iUwLXbfmO9e2NxKA3W5FQx+QvYz ikYd8z3upJnviU4M4PXntIzsC47mdeEk5mZPWnWPMhUj/vRdvPGDeaFvYXVV/15R++fB cVoYT6ABnnYaVheIz6iiUCGN8WZQYF4kKRUEJM3vQj4JjC/3+fyQny+EpbpalrgTGYyC an0aLCK2DBUy/ROONI0PWkzE/lpwZWQb2cBRV2OUsd1xu4oPbsEzC1wVIcj/tk3q+lzt w3tjkNLtNKY5tY6Gh8LXEUqpanz779jUHyYz67LWqWyVHdGUtSGFy9oNVSp4aK6/Pow4 I90Q==
X-Received: by 10.66.188.137 with SMTP id ga9mr15764653pac.9.1368150750206; Thu, 09 May 2013 18:52:30 -0700 (PDT)
Received: from [192.168.1.194] (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPSA id hp1sm671221pac.3.2013.05.09.18.52.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 May 2013 18:52:29 -0700 (PDT)
From: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_248E649C-766F-409D-B718-A485A511BC3D"
Subject: Update of draft-otis-ipv6-email-authent
Date: Thu, 9 May 2013 18:52:25 -0700
Message-Id: <E9784937-8A46-4769-89B4-DCEA7B28F049@gmail.com>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Cc: "presnick@qti.qualcomm.com" <presnick@qti.qualcomm.com>, "sm+ietf@elandsys.com Moonesamy" <sm+ietf@elandsys.com>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, "barryleiba@computer.org Leiba" <barryleiba@computer.org>, "clewis+ietf@mustelids.ca" <clewis+ietf@mustelids.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 01:52:35 -0000

--Apple-Mail=_248E649C-766F-409D-B718-A485A511BC3D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear ietf, spfbis, and repute,

Until an identifier is linked with the source of an exchange by way of =
authentication, it must not be trusted as offering valid reputation =
input. For example, a valid DKIM signature lacks important context.  A =
valid DKIM signature does not depend upon actual sources or intended =
recipients, both of which are essential elements in determining =
unsolicited messages or even whether the message is valid.  SPF only =
offers authorization of Non-Delivery Notifications, and can not be =
considered to represent actual sources.

Three different authors attempted to repair DKIM's header field issue =
within the WG process but repairs were rejected.  As with the DKIM WG, =
being right about likely outcomes will not always prevail in offering =
safe and dependable protocols offering a well understood services.

The initial intent for DKIM was to help prevent spoofing, but that =
effort ran astray with desires to extend DKIM beyond its capabilities.  =
Flexibility allowing DKIM to be relayed removes typical rate limitations =
protecting a domain's reputation from occasional lapses or from messages =
easily taken out of context.

Since a valid DKIM signature may not preclude prepended header fields, =
this raises important questions.  When such spoofing does occur, which =
domain's reputation should be affected?  A domain too big to block that =
does not add the non-existent header field hack? A domain being spoofed =
to improve statistical filtering?  It is clear those actually =
responsible for abusive exchange may be ignored by these strategies.

Better solutions at enforcing security and offering fair reputations are =
readily available.

http://tools.ietf.org/html/draft-otis-ipv6-email-authent-01

DKIM can not be used to establish reputation without a link with those =
responsible for its transmission.  Neither DKIM nor SPF established =
those actually responsible for the exchange.  Today, unfortunately, the =
only thing that can be "trusted" in email is the ip address of the host =
connecting to the mail server - and even that can be subverted with BGP =
injection.

Regards,
Douglas Otis=

--Apple-Mail=_248E649C-766F-409D-B718-A485A511BC3D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Dear ietf, spfbis, and repute,</div><div><br></div><div>Until an =
identifier is linked with the source of an exchange by way of =
authentication, it must not be trusted as offering valid reputation =
input.&nbsp;For example, a valid DKIM signature lacks important context. =
&nbsp;A valid DKIM signature does not depend upon actual sources or =
intended recipients, both of which are essential elements in determining =
unsolicited messages or even whether the message is valid. &nbsp;SPF =
only offers authorization of Non-Delivery Notifications, and can not be =
considered to represent actual sources.</div><div><br></div><div>Three =
different authors attempted to repair DKIM's header field issue within =
the WG process but repairs were rejected. &nbsp;As with the DKIM WG, =
being right about likely outcomes will not always prevail in offering =
safe and dependable protocols offering a well understood =
services.</div><div><br></div><div>The initial intent for DKIM was to =
help prevent spoofing, but that effort ran astray with desires to extend =
DKIM beyond its capabilities. &nbsp;Flexibility allowing DKIM to be =
relayed removes typical rate limitations protecting a domain's =
reputation from occasional lapses or from messages easily taken out of =
context.</div><div><br></div><div>Since a valid DKIM signature may not =
preclude prepended header fields, this raises important questions. =
&nbsp;When such spoofing does occur, which domain's reputation should be =
affected? &nbsp;A domain too big to block that does not add the =
non-existent header field hack? A domain being spoofed to improve =
statistical filtering? &nbsp;It is clear those actually responsible for =
abusive exchange may be ignored by these =
strategies.</div><div><br></div><div>Better solutions at enforcing =
security and offering fair reputations are readily =
available.</div><div><br></div><a =
href=3D"http://tools.ietf.org/html/draft-otis-ipv6-email-authent-01">http:=
//tools.ietf.org/html/draft-otis-ipv6-email-authent-01</a><div><br></div><=
div>DKIM can not be used to establish reputation without a link with =
those responsible for its transmission. &nbsp;Neither DKIM nor SPF =
established those actually responsible for the exchange. &nbsp;Today, =
unfortunately, the only thing that can be "trusted" in email is the ip =
address of the host connecting to the mail server - and even that =
can&nbsp;be subverted with BGP =
injection.<br><div><br></div><div>Regards,</div><div>Douglas =
Otis</div></div></body></html>=

--Apple-Mail=_248E649C-766F-409D-B718-A485A511BC3D--

From narten@us.ibm.com  Thu May  9 21:53:23 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0819121F8F25 for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 21:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QuMDbp+YrPJJ for <ietf@ietfa.amsl.com>; Thu,  9 May 2013 21:53:10 -0700 (PDT)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 15C8421F8F43 for <ietf@ietf.org>; Thu,  9 May 2013 21:53:09 -0700 (PDT)
Received: from /spool/local by e8.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 10 May 2013 00:53:08 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 10 May 2013 00:53:05 -0400
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id EEB0438C8042 for <ietf@ietf.org>; Fri, 10 May 2013 00:53:04 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4A4r5Ej320476 for <ietf@ietf.org>; Fri, 10 May 2013 00:53:05 -0400
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4A4r4mn020072 for <ietf@ietf.org>; Fri, 10 May 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4A4r4Zb020063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 10 May 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.6/8.12.5) with ESMTP id r4A4r3x2021241 for <ietf@ietf.org>; Fri, 10 May 2013 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.6/8.14.6/Submit) id r4A4r3e0021206 for ietf@ietf.org; Fri, 10 May 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201305100453.r4A4r3e0021206@rotala.raleigh.ibm.com>
Date: Fri, 10 May 2013 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13051004-9360-0000-0000-0000121CC1FB
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 04:53:23 -0000

Total of 138 messages in the last 7 days.
 
script run at: Fri May 10 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.25% |   10 |  8.90% |    93387 | marka@isc.org
  6.52% |    9 |  7.85% |    82311 | narten@us.ibm.com
  7.25% |   10 |  6.58% |    69033 | john-ietf@jck.com
  4.35% |    6 |  4.92% |    51589 | scott@kitterman.com
  4.35% |    6 |  3.90% |    40851 | hannes.tschofenig@gmx.net
  4.35% |    6 |  3.70% |    38841 | sm+ietf@elandsys.com
  3.62% |    5 |  3.33% |    34916 | brian.e.carpenter@gmail.com
  2.90% |    4 |  3.30% |    34585 | doug.mtview@gmail.com
  2.90% |    4 |  3.27% |    34333 | alh-ietf@tndh.net
  2.90% |    4 |  3.06% |    32061 | bclaise@cisco.com
  2.90% |    4 |  3.05% |    31953 | daedulus@btconnect.com
  2.90% |    4 |  2.61% |    27392 | ned+ietf@mauve.mrochek.com
  2.17% |    3 |  2.15% |    22521 | dougb@dougbarton.us
  2.17% |    3 |  1.80% |    18858 | joelja@bogus.com
  2.17% |    3 |  1.63% |    17072 | worley@ariadne.com
  2.17% |    3 |  1.43% |    14970 | randy@psg.com
  1.45% |    2 |  1.97% |    20627 | rdroms.ietf@gmail.com
  1.45% |    2 |  1.48% |    15501 | presnick@qti.qualcomm.com
  1.45% |    2 |  1.46% |    15269 | hsantos@isdg.net
  1.45% |    2 |  1.43% |    15015 | sm@resistor.net
  1.45% |    2 |  1.30% |    13638 | swb@internet2.edu
  1.45% |    2 |  1.28% |    13407 | ted.lemon@nominum.com
  1.45% |    2 |  1.25% |    13073 | elwynd@dial.pipex.com
  1.45% |    2 |  1.19% |    12444 | jari.arkko@piuha.net
  1.45% |    2 |  1.16% |    12116 | derhoermi@gmx.net
  1.45% |    2 |  1.15% |    12093 | john@jlc.net
  1.45% |    2 |  1.06% |    11096 | adrian@olddog.co.uk
  1.45% |    2 |  1.05% |    11035 | mrex@sap.com
  1.45% |    2 |  1.04% |    10900 | peter@akayla.com
  0.72% |    1 |  1.61% |    16854 | olaf@nlnetlabs.nl
  0.72% |    1 |  1.58% |    16521 | rjsparks@nostrum.com
  0.72% |    1 |  1.41% |    14746 | mohamed.boucadair@orange.com
  0.72% |    1 |  1.02% |    10730 | l.wood@surrey.ac.uk
  0.72% |    1 |  0.94% |     9817 | warren@kumari.net
  0.72% |    1 |  0.92% |     9697 | cja@daydream.com
  0.72% |    1 |  0.87% |     9082 | ynir@checkpoint.com
  0.72% |    1 |  0.82% |     8628 | tjc@ecs.soton.ac.uk
  0.72% |    1 |  0.79% |     8334 | gonzalo.camarillo@ericsson.com
  0.72% |    1 |  0.78% |     8214 | andy@yumaworks.com
  0.72% |    1 |  0.73% |     7621 | jouni.nospam@gmail.com
  0.72% |    1 |  0.69% |     7232 | randy_presuhn@mindspring.com
  0.72% |    1 |  0.68% |     7184 | rse@rfc-editor.org
  0.72% |    1 |  0.68% |     7109 | superuser@gmail.com
  0.72% |    1 |  0.67% |     6977 | mcquilwp@pobox.com
  0.72% |    1 |  0.63% |     6643 | yaronf.ietf@gmail.com
  0.72% |    1 |  0.62% |     6543 | mcr+ietf@sandelman.ca
  0.72% |    1 |  0.62% |     6505 | barryleiba@computer.org
  0.72% |    1 |  0.62% |     6475 | jabley@hopcount.ca
  0.72% |    1 |  0.60% |     6336 | stpeter@stpeter.im
  0.72% |    1 |  0.58% |     6130 | dhc@dcrocker.net
  0.72% |    1 |  0.58% |     6070 | spencer@wonderhamster.org
  0.72% |    1 |  0.57% |     5934 | rpelletier@isoc.org
  0.72% |    1 |  0.55% |     5817 | cabo@tzi.org
  0.72% |    1 |  0.55% |     5765 | johnl@taugh.com
  0.72% |    1 |  0.55% |     5731 | mansaxel@besserwisser.org
  0.72% |    1 |  0.53% |     5607 | stephen.farrell@cs.tcd.ie
  0.72% |    1 |  0.53% |     5583 | envite@rolamasao.org
--------+------+--------+----------+------------------------
100.00% |  138 |100.00% |  1048772 | Total


From daedulus@btconnect.com  Fri May 10 01:19:37 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38F0C21F8E5B for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 01:19:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.777
X-Spam-Level: 
X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[AWL=1.822,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UHlORzG0XOz7 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 01:19:32 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe005.messaging.microsoft.com [216.32.181.185]) by ietfa.amsl.com (Postfix) with ESMTP id EF89D21F8B18 for <ietf@ietf.org>; Fri, 10 May 2013 01:19:31 -0700 (PDT)
Received: from mail29-ch1-R.bigfish.com (10.43.68.252) by CH1EHSOBE006.bigfish.com (10.43.70.56) with Microsoft SMTP Server id 14.1.225.23; Fri, 10 May 2013 08:19:30 +0000
Received: from mail29-ch1 (localhost [127.0.0.1])	by mail29-ch1-R.bigfish.com (Postfix) with ESMTP id EBED560163; Fri, 10 May 2013 08:19:30 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zz9371I542I1432I1a09Jd799hzz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail29-ch1 (localhost.localdomain [127.0.0.1]) by mail29-ch1 (MessageSwitch) id 1368173968280144_28313; Fri, 10 May 2013 08:19:28 +0000 (UTC)
Received: from CH1EHSMHS042.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.246])	by mail29-ch1.bigfish.com (Postfix) with ESMTP id 0D6ED1C013B;	Fri, 10 May 2013 08:19:28 +0000 (UTC)
Received: from AMSPRD0711HT002.eurprd07.prod.outlook.com (157.56.250.181) by CH1EHSMHS042.bigfish.com (10.43.69.251) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 10 May 2013 08:19:21 +0000
Received: from AMXPRD0111HT003.eurprd01.prod.exchangelabs.com (157.56.250.117) by pod51017.outlook.com (10.242.14.163) with Microsoft SMTP Server (TLS) id 14.16.305.3; Fri, 10 May 2013 08:19:14 +0000
Message-ID: <001801ce4d56$53084460$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: "Dale R. Worley" <worley@ariadne.com>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org><50992BEF.9000803@gmail.com><C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com><00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net> <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.net> <201305081937.r48JbjTQ4388434@shell01.TheWorld.com>
Subject: Re: Accessing tools from IETF pages
Date: Fri, 10 May 2013 09:13:36 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-FOPE-CRA-SourceIpAddress: 157.56.250.181
X-FOPE-CRA-DRYRUN: 1207119;1
X-FOPE-BFA-SENDER: daedulus@btconnect.com
X-FOPE-BFA-RECEIVER: ietf@ietf.org
X-FOPE-BFA-RECEIVER: worley@ariadne.com
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, 10 May 2013 08:19:37 -0000

Tom Petch

----- Original Message -----
From: "Dale R. Worley" <worley@ariadne.com>
To: "t.p." <daedulus@btconnect.com>
Cc: <ietf@ietf.org>
Sent: Wednesday, May 08, 2013 8:37 PM
Subject: Re: Accessing tools from IETF pages


> > From: "t.p." <daedulus@btconnect.com>
> >
> > I wanted to submit an I-D so I wanted to access the tools, as I have
> > done before, so I clicked on 'IETF Tools' from
> > http://datatracker.ietf.org/wg/
> > and when that failed tried again with 'Tools Team Pages' from
> > http://www.ietf.org/iesg/
> > with the same result.  Can anyone else get to tools from that link?
> >
> > It resolves to
> > http://tools.ietf.org/
> > which Internet Explorer (what else?) assures me cannot be displayed,
> > either from the link or from typing it into the Open drop down.
>
> Well, all three of those links work for me at "May 8 19:33:01 UTC
> 2013" using Firefox 18.0.2 on Linux.  (For whatever that is worth.)
>
> I'd sniff the HTTP transaction to get some information on the specific
> failure mode.

Dale

Many thanks for that; if others can get to it, then that resolves my
issue, I can always  go via other means, until I get myself a trace and
see what is really going on.

Tom Petch

> Dale
>



From elwynd@dial.pipex.com  Fri May 10 02:36:19 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0340F21F86CE for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 02:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7inRQV0tOQju for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 02:36:18 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 7B38E21F84D8 for <ietf@ietf.org>; Fri, 10 May 2013 02:36:15 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1UajkJ-00074l-Pk; Fri, 10 May 2013 10:36:11 +0100
Subject: Re: call for ideas: tail-heavy IETF process
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <518C0282.1080101@gmail.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net>	<9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net>	<51896896.80706@stpeter.im> <518A15E3.7040707@rfc-editor.org> <DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net> <518B5F0D.4070802@wonderhamster.org> <AE98FA932FF026CB380D1262@JcK-HP8200.jck.com> <518C0282.1080101@gmail.com>
Content-Type: text/plain
Date: Fri, 10 May 2013 10:28:38 +0100
Message-Id: <1368178118.5273.14469.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.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, 10 May 2013 09:36:19 -0000

Similarly, AFAICS the 'IESG time' includes IETF last call and the
inevitable delay caused by the quantized nature of IESG teleconferenes.

On the average, this will be somewhere around 28-30 days (2 or 4 weeks
in Last call according to document type plus an average of 1 week until
the earliest possible teleconference and a fudge factor for weekends)
which is an irreducible minimum imposed by our processes.   There is not
much the IESG can do to help on that.

/Elwyn

On Fri, 2013-05-10 at 08:09 +1200, Brian E Carpenter wrote:
> On 10/05/2013 01:13, John C Klensin wrote:
> > 
> > --On Thursday, May 09, 2013 03:32 -0500 Spencer Dawkins
> > <spencer@wonderhamster.org> wrote:
> > 
> >> So in this case, we're looking at "RFC Editor state" =
> >> "Heather, please do something" + "some working group, please
> >> do something" + "author(s), please do something", and we can't
> >> tell how much time to attribute to each of these ...
> > 
> > You could further add to that list "RFC Production Center,
> > please do something" (different from an RSE wait, which is, or
> > at least ought to be, more significant) and "IESG or appropriate
> > AD, please do something", which does happen.
> > 
> > But the RFC Editor's numbers try (almost always successfully) to
> > separate the two "waiting on the RFC Editor Function to do
> > something" (Heather plus Production Center plus, in principle,
> > Publisher) from the other states.  Those other states could,
> > from their point of view, be aggregated into "stuck, someone
> > else's problem".   If we are looking for issues with IETF
> > end-game process, we need to parse those, but that is a
> > different sort of question in terms of data-gathering and
> > reporting.
> 
> All of which suggests that, ideally, the tracker would include
> a variable "onTheHook" for each draft, containing at all times
> the person or role responsible for the next step. That isn't
> necessarily implied by the state machine. For example,
> AUTH48 doesn't always imply that the author is on the hook -
> it may be that the author has asked the WG Chair to ask the
> WG for a quick review of a proposed last-minute change. At
> that point, the WG as a whole is on the hook.
> 
>     Brian


From jari.arkko@piuha.net  Fri May 10 05:07:55 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86EA521F8BDE for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 05:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.742
X-Spam-Level: 
X-Spam-Status: No, score=-102.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fauFG2mUqG6u for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 05:07:50 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB1321F8B5F for <ietf@ietf.org>; Fri, 10 May 2013 05:07:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 86CDF2CC48 for <ietf@ietf.org>; Fri, 10 May 2013 15:07:40 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xz0DZh13FZUo for <ietf@ietf.org>; Fri, 10 May 2013 15:07:40 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id E70C32CC3C for <ietf@ietf.org>; Fri, 10 May 2013 15:07:39 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: ways forward with the tail-heavy aspects of the IETF process
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <518B5F0D.4070802@wonderhamster.org>
Date: Fri, 10 May 2013 13:07:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A49DE340-4ACB-4E8D-BC47-CD3284E078E3@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <5182AD0F.4010204@gmx.net> <9AB65B31-4C42-4A33-AE74-E24AFA284A66@piuha.net> <5182EFA3.30400@dcrocker.net> <51896896.80706@stpeter.im> <518A15E3.7040707@rfc-editor.org> <DA1D94B8-ABCF-4F68-81D6-C3B512A9091A@piuha.net> <518B5F0D.4070802@wonderhamster.org>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 12:07:55 -0000

I wanted to send an update, after having discussed this topic in the =
IESG retreat that we just had here in Dublin. The overall plan is to =
start with three specific changes listed below. Note that these are =
approaches that we have discussed, and more detailed plans will be =
developed in the coming weeks.

1. Send more documents back to the WG to complete the necessary changes. =
While the responsibility for changes has always been at the WG, the =
documents were still in the IESG process. The IESG felt that =
particularly in situations where changes are large or multiple, it would =
be useful to make the situation about WG ownership even clearer. We will =
do this by handing the document back to the WG and getting the IESG out =
of the loop, with the instruction that the chairs should manage the =
process and address the issues raised in the IETF last call and by the =
ADs.

2. Moving some directorate reviews earlier, to WG last call time as =
opposed to IETF last call or IESG review. With the intent of not =
increasing the number of reviews.

3. Start inviting the document shepherds (i..e., usually WG chairs) to =
some of the telechats where the IESG discusses their documents.

While these changes do not by themselves decrease the amount of work =
done in the final stages, we believe they make the role of the working =
group more central, and as such, contribute to improving the tail-heavy =
situation in the long run. We will work further in the IESG and affected =
parties on the details. One obvious question is how various directorates =
feel about the changes, and how we avoid increasing workload for them.

Jari


From jmh@joelhalpern.com  Fri May 10 07:38:20 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D859021F8B9C; Fri, 10 May 2013 07:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tMvmqa4yvwdU; Fri, 10 May 2013 07:38:16 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 3A57321F8B54; Fri, 10 May 2013 07:38:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 206191D22BC; Fri, 10 May 2013 07:38:15 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.72.211.58] (unknown [193.1.64.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5EF8B1C07EB; Fri, 10 May 2013 07:38:11 -0700 (PDT)
Message-ID: <518D0635.7040301@joelhalpern.com>
Date: Fri, 10 May 2013 10:37:41 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Subject: Re: [Gen-art]  Review: draft-ietf-netmod-rfc6021-bis-01
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com>
In-Reply-To: <5171C416.5070105@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 14:38:21 -0000

I am guessing that the authors intended the addition of the text 
emphasizing that the no-zone typedefs are derived general typedef 
addresses the difference in the patterns.

Is there a YANG rule that says tat if typedef X is derived from typedef 
Y then the string for X must match the pattern for X and the pattern for 
Y?  If so, then my concern below is misplaced.  (The fact that I find 
the vague pattern for the child misleading is not a fault with the 
document, but rather in my head, under that requirement.)

Yours,
Joel

On 4/19/2013 6:24 PM, Joel M. Halpern 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-netmod-rfc6021-bis-01
>      Common YANG Data Types
> Reviewer: Joel M. Halpern
> Review Date: 19-April-2013
> IETF LC End Date: 1-May-2013
> IESG Telechat date: N/A
>
> Summary: This document is nearly ready for publication as a Standards
> Track RFC
>
> Major issues:
>      (The following may well be a non-issue.)
>      In the revision of the ietf-inet-types, the patterns for the new
> ip4-address-no-zone and ipv6-address-no-zone are drastically simplified
> from the ipv4-address and ipv6-address patterns.  The new
> ipv4-address-no-zone allows any sequence of decimal digits an periods,
> while the original was carefully defined as dotted quads of 0..255.
> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex
> digits and colons.  The original patterns were very careful to match
> rules for validity.  Is there a reason for the change.
>
> Minor issues:
>
> Nits/editorial comments:
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art
>

From rjsparks@nostrum.com  Fri May 10 08:12:48 2013
Return-Path: <rjsparks@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 8FA4B21F8CB4; Fri, 10 May 2013 08:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lym-4T45rWIR; Fri, 10 May 2013 08:12:47 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8131A21F8C40; Fri, 10 May 2013 08:12:46 -0700 (PDT)
Received: from unnumerable.local (mobile-166-147-077-105.mycingular.net [166.147.77.105]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4AFCcj3079542 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK); Fri, 10 May 2013 10:12:39 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <518D0E64.6020504@nostrum.com>
Date: Fri, 10 May 2013 10:12:36 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Liubing (Leo)" <leo.liubing@huawei.com>
Subject: Re: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 166.147.77.105 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 15:12:48 -0000

Thanks Bing -

The updates make the document better, and I appreciate the resolution of 
referencing Tim's expired draft.
I think you've addressed all my comments except for the one on section 
5.1, but that's ok.

For completeness and ease on the ADs, here's an updated summary:

Document: draft-ietf-6renum-gap-analysis-05.txt
Reviewer: Robert Sparks
Review Date: May 10, 2013
IETF LC End Date: April 10, 2013
IESG Telechat date: May 16, 2013

Summary: Ready



On 5/2/13 6:02 AM, Liubing (Leo) wrote:
> Hi, Robert
>
> Thanks a lot for your continuous careful review.
> Please see replies inline.
>
>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> Sent: Wednesday, May 01, 2013 12:33 AM
>> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
>> Cc: gen-art@ietf.org; ietf@ietf.org
>> Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt
>>
>> 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-6renum-gap-analysis-05.txt
>> Reviewer: Robert Sparks
>> Review Date: April 1, 2013
>> IETF LC End Date: April 10, 2013
>> IESG Telechat date: May 16, 2013
>>
>> Summary: Ready with nits (that border on minor issues)
>>
>> This update improved the readability significantly, and addressed my
>> major concern about being able to build a list of the gaps. Thank you.
>>
>> There are a few issues from my last call review that are still not
>> addressed.
>> I have left the classification of minor issue vs nits the same as the
>> original review to make referring to the earlier review easier,
>> but please consider all of these Nits. The IESG will need to decide
>> whether to escalate them.
>>
>> I've trimmed away the points that were addressed.
>>
>> On 4/1/13 3:46 PM, Robert Sparks wrote:
>>> ----------------------
>>> Minor issues:
>>>
>>> The document currently references
>>> draft-chown-v6ops-renumber-thinkabout several times.
>>> That document is long expired (2006). It would be better to simply
>>> restate what is
>>> important from that document here and reference it only once in the
>>> acknowlegements
>>> rather than send the reader off to read it.
>> This version still references that long expired draft. There was also
>> conversation on apps-discuss
>> about making that reference normative. IMHO, this is not the right way
>> to treat the RFC series, and
>> strongly encourage moving the text that you want to reference into
>> something that will
>> become an RFC.
> [Bing] Maybe Brian's suggestion of putting some texts into an appendix is a good way. We'll discuss this problem when make the next time update.
>
>>> Should section 8 belong to some other document? It looks like
>>> operational renumbering
>>> advice/considerations, but doesn't seem to be exploring renumbering
>>> gaps, except for
>>> the very short section 8.2 which says "we need a better mechanism"
>>> without much explanation.
>> Afaict, this wasn't addressed at all. In particular, "we need a better
>> mechanism" is still all that
>> section 8.2 says.
> [Bing] Sorry for leaving it out. Will do in next update.
>
>>> Section 5.1, first bullet. The list below "the impact of ambiguous M/O
>>> flags" says things like
>>> "there is no standard" and "it is unspecified". I think you are trying
>>> to say that there is
>>> ambiguity in what's written, not that nothing's written. This entire
>>> list would benefit from
>>> being recast in terms of what needs to be done (what are the gaps?).
>> This text remains unmodified.
> [Bing] We made revision focusing on explaining "what are the gaps", but the texts change was omitted, will do in next update.
>
>>> ----------------------
>>> Nits/editorial comments:
>>>
>>> There are a few sentences ending with "etc." in the document. Please
>>> consider deleting the
>>> word from the list - it doesn't help each sentence make its point.
>> There were some changes, but mostly these still exist. I'll leave
>> pressing this point further to the RFC Editor.
> [Bing] A professional language/editorial check would be helpful.
>
>>> Seciton 7.1: The first bullet does not parse. If I guess its meaning
>>> correctly
>>> (that it would be benificial to tell hosts that local DNS has been
>>> updated and
>>> they may want to make fresh queries), please be careful with the
>>> wording. The
>>> hosts don't know which names are likely to resolve locally.
>> This text remained unchanged, and when coming back to the document for a
>> re-review
>> (which is somewhat like coming back to an RFC you've read before just
>> for reference),
>> it's even harder to understand what it's trying to say than it was when
>> reading the document
>> linearly.
>>
>> I think you are trying to say
>> "A notification mechanism may be needed to indicate _to_ hosts that a
>> renumbering event has _changed how local recursive DNS servers will
>> respond_. That mechanism may also need to indicate that such a change
>> will happen at a specific time in the future."
> [Bing] I think it's a better description. Will update, thanks much.
>
>>> Section 7.1, third bullet - This isn't obviously about notification.
>>> Why is it
>>> in this section? What's the gap this is trying to identify?
>> This text was unchanged.
> [Bing] For example, if border routers enabled egress filtering based on the SIP, then the router need to know the renumbering events on some internal nodes. We'll make it clear in the next version.
>
>>> Section 9.4 - what is it about these that make them gaps, much less
>>> unsolvable gaps.
>>> Is this discussion in the wrong section of the document?
>> This is now section 10.3 and is mostly unchanged. It's still not clear
>> why this discussion is in the "unsolvable gaps" section.
> [Bing] We considered the two points (ID/Locator overloading in transport layer & address caching in app layer ) are too fundamental that might not be proper to modify them just in terms of renumbering.
>
> Best regards,
> Bing


From sm@resistor.net  Fri May 10 11:51:32 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080CE21F89B2 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 11:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yzyy3WbOfEt5 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 11:51:30 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 05BC021F8972 for <ietf@ietf.org>; Fri, 10 May 2013 11:51:29 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4AIpPZn012379 for <ietf@ietf.org>; Fri, 10 May 2013 11:51:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368211888; bh=PHwIglXmPxdkmtdmo4Uzy3xbxUeK0b+erxDNSlnOpJg=; h=Date:To:From:Subject:In-Reply-To:References; b=VaESbnk3pHGHkJMnasvSPeUOs03Y88F8rlops2uwal/I9FZw1qY1DhekMjrVTMEnR IdPxqw65sF87W7CnOVG/v+55zJaFAE5SxtghbxGrPU0mlQBXnMJMI+oPZrqXAW/NA9 trok3XzuHYopr2+lBYhZ3eVOgIsVRr7f3IqMvKjI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1368211888; i=@resistor.net; bh=PHwIglXmPxdkmtdmo4Uzy3xbxUeK0b+erxDNSlnOpJg=; h=Date:To:From:Subject:In-Reply-To:References; b=PzuicF+1qQKRBptGNoTS3P5Tc6hsqWbVkp9QoA1+iHADh2ikfgEF8C7ZTfxmmU2lh pfRUDAIy9ErqKOXlAX5IF+eZ6TdowQ/hZ7eV+FFT7Cxtq9//KtP05JjzCOfbpY1snB REaZLAGVRKg4I4UxF7R91bvdHU16UUmdcmhYGIdQ=
Message-Id: <6.2.5.6.2.20130510103049.0ca25050@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 10 May 2013 11:40:45 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
In-Reply-To: <20130416230618.31243.43068.idtracker@ietfa.amsl.com>
References: <20130416230618.31243.43068.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: Fri, 10 May 2013 18:51:32 -0000

At 16:06 16-04-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'The Internet Numbers Registry System'
>   <draft-housley-rfc2050bis-01.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-05-14. Exceptionally, comments may be

This draft is well-written and it is a significant improvement 
compared to the previous version.

In Section 2:

   "As such, allocations must be made in accordance with the operational
    needs of those running the networks that make use of these number
    resources and by taking into consideration pool limitations at the
    time of allocation."

The global IPv4 address pool is currently depleted.  Two RIR regions 
are in IPv4 exhaustion phase.  There is a proposal in the RIPE region 
to remove "need" [1].  I gather that this new version of the Internet 
Numbers Registry System looks towards a future where hosts are IPv6 
accessible.  Given that the free IPv6 address pool is very large and 
that IP addresses are not free, what is the rationale for keeping 
allocations in accordance with operational needs?

   "Registration Accuracy: A core requirement of the Internet
    Numbers Registry System is to maintain a registry of
    allocations to ensure uniqueness and to provide accurate
    registration information of those allocations in order to
    meet a variety of operational requirements."

There isn't any mention of privacy [2] considerations in the 
draft.  Is it up to the IETF to set up a one-stop shop for personal 
data requests?

Regards,
-sm

1. https://www.ripe.net/ripe/policies/proposals/2013-03
2. http://lists.arin.net/pipermail/arin-ppml/2012-April/024596.html 


From brian.e.carpenter@gmail.com  Fri May 10 12:35:06 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17B6921F871C; Fri, 10 May 2013 12:35:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35uAp+djjH17; Fri, 10 May 2013 12:35:05 -0700 (PDT)
Received: from mail-ia0-x235.google.com (mail-ia0-x235.google.com [IPv6:2607:f8b0:4001:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 76D3621F86BB; Fri, 10 May 2013 12:35:05 -0700 (PDT)
Received: by mail-ia0-f181.google.com with SMTP id f27so4895301iae.26 for <multiple recipients>; Fri, 10 May 2013 12:35:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EJ2AfnDAPi4SEvRs54lKASllD7RywbFqg465zkTjASo=; b=VI3nPqMjqwbnYAAUU0RPAB9kOPhnO6v9bC4J9hkq3KITLuPLPilCFi2mWokb5sfNqU I1EuwvSvtycS1VL+K8S39P8WAn7ev5O93vNSRRdPA/HrUw8EX/bjZ9VsMUsH75bXhQGL oRohPgagq7ScqSykc84c8vx1bcG2A0XseE+MY22PCWFzay6ZY8J5oQaDJoRjV+Q5M4XU hMeXZl9tcz+9zeT9g2X43RAdSYOxYcYkuHqmmewRwDHfu6Xvuyq75EoCQAVoY/lMjoFy scEdO3zlhZjtYIhQKs1tKUN6G6RWysD79RR5a/CgKPxPLQ2QOdzHOs/8lfVYiAias6+F rvhQ==
X-Received: by 10.42.168.198 with SMTP id x6mr8274651icy.45.1368214505068; Fri, 10 May 2013 12:35:05 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id lr1sm6051138igb.6.2013.05.10.12.35.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 May 2013 12:35:04 -0700 (PDT)
Message-ID: <518D4BF0.8030307@gmail.com>
Date: Sat, 11 May 2013 07:35:12 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Stig Venaas <stig@cisco.com>
Subject: Re: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com> <518D2728.9000606@cisco.com>
In-Reply-To: <518D2728.9000606@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@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, 10 May 2013 19:35:06 -0000

On 11/05/2013 04:58, Stig Venaas wrote:
> On 5/10/2013 8:12 AM, Robert Sparks wrote:
>> Thanks Bing -
>>
>> The updates make the document better, and I appreciate the resolution of
>> referencing Tim's expired draft.
> 
> So the solution is to not reference it? I see the name of the draft is
> mentioned in the acknowledgments as:
>  [draft-chown-v6ops-renumber-thinkabout].
> 
> Shouldn't it then be an informational reference? It doesn't make sense
> to me to mention a draft in the text and not have a reference.

YMMV, but I expect the RFC Editor will resolve this.

   Brian


From cb.list6@gmail.com  Fri May 10 17:44:32 2013
Return-Path: <cb.list6@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D1E921F8F20 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 17:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id li7IhQzJ47mV for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 17:44:31 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2819621F8ECA for <ietf@ietf.org>; Fri, 10 May 2013 17:44:30 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id f11so4471496wgh.3 for <ietf@ietf.org>; Fri, 10 May 2013 17:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=MRHQEvG8jL/5PwdDMHLcPiCcy8pWaR8mzmATN9xbX18=; b=h+GEc12yBsDxnNSiikQasrXe8RC4OWUlULHvckycuGcnZOAnpz/K8XpnrEKgja2RKa 62JSULrQM27SS6qqSka+qNYWZ0ma5MKSphXzc+Q2h/Q/juWb/pgexjm1614ODhSRU8iW Xof95NkoPTkxrPcsNrHovJh5bYalriBTXJYNpqMMF23maRbUPtcSSBRI2jrRWDm0WyMM shdknpq31bt3mDQ8aV1a/7v1sPdwzAr52Rzx/rxdK+datO46l6FCpkSKrBjd7QZ5EmlX 9gwdNQNDwldQHHy3id3KjzbUF9maVD0YRLKF7mOn7n3XMr4Da8ytOwdXzES8Nd3JFJR7 Awig==
MIME-Version: 1.0
X-Received: by 10.180.210.225 with SMTP id mx1mr6963259wic.15.1368233070029; Fri, 10 May 2013 17:44:30 -0700 (PDT)
Received: by 10.194.77.14 with HTTP; Fri, 10 May 2013 17:44:29 -0700 (PDT)
Received: by 10.194.77.14 with HTTP; Fri, 10 May 2013 17:44:29 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130510103049.0ca25050@resistor.net>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net>
Date: Fri, 10 May 2013 17:44:29 -0700
Message-ID: <CAD6AjGRE_ah2JAQG3hZQA8+qv+ECxZo34A6C3pRjkewgYv5KEA@mail.gmail.com>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
From: "cb.list6" <cb.list6@gmail.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=001a11c26ac61befc204dc6696b0
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, 11 May 2013 00:44:32 -0000

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

On May 10, 2013 11:51 AM, "SM" <sm@resistor.net> wrote:
>
> At 16:06 16-04-2013, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'The Internet Numbers Registry System'
>>   <draft-housley-rfc2050bis-01.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-05-14. Exceptionally, comments may be
>
>
> This draft is well-written and it is a significant improvement compared
to the previous version.
>
> In Section 2:
>
>   "As such, allocations must be made in accordance with the operational
>    needs of those running the networks that make use of these number
>    resources and by taking into consideration pool limitations at the
>    time of allocation."
>
> The global IPv4 address pool is currently depleted.  Two RIR regions are
in IPv4 exhaustion phase.  There is a proposal in the RIPE region to remove
"need" [1].  I gather that this new version of the Internet Numbers
Registry System looks towards a future where hosts are IPv6 accessible.
 Given that the free IPv6 address pool is very large and that IP addresses
are not free, what is the rationale for keeping allocations in accordance
with operational needs?
>

I disagree with need based assignment and believe this draft should remove
all such language

The need based policy is not equitable and is nothing but a drag in the
post ipv4 exhaust world.

I have made a case for moving away from need basis here,
http://lists.arin.net/pipermail/arin-ppml/2013-April/026592.html

The ietf should really take the time to review what the rirs have done and
if their mandate needs to be updated.

Ipv4 belongs to the market and ipv6 does not have scarcity issues.

CB


>   "Registration Accuracy: A core requirement of the Internet
>    Numbers Registry System is to maintain a registry of
>    allocations to ensure uniqueness and to provide accurate
>    registration information of those allocations in order to
>    meet a variety of operational requirements."
>
> There isn't any mention of privacy [2] considerations in the draft.  Is
it up to the IETF to set up a one-stop shop for personal data requests?
>
> Regards,
> -sm
>
> 1. https://www.ripe.net/ripe/policies/proposals/2013-03
> 2. http://lists.arin.net/pipermail/arin-ppml/2012-April/024596.html

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

<p dir=3D"ltr"><br>
On May 10, 2013 11:51 AM, &quot;SM&quot; &lt;<a href=3D"mailto:sm@resistor.=
net">sm@resistor.net</a>&gt; wrote:<br>
&gt;<br>
&gt; At 16:06 16-04-2013, The IESG wrote:<br>
&gt;&gt;<br>
&gt;&gt; The IESG has received a request from an individual submitter to co=
nsider<br>
&gt;&gt; the following document:<br>
&gt;&gt; - &#39;The Internet Numbers Registry System&#39;<br>
&gt;&gt; =A0 &lt;draft-housley-rfc2050bis-01.txt&gt; as Informational RFC<b=
r>
&gt;&gt;<br>
&gt;&gt; The IESG plans to make a decision in the next few weeks, and solic=
its<br>
&gt;&gt; final comments on this action. Please send substantive comments to=
 the<br>
&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists b=
y 2013-05-14. Exceptionally, comments may be<br>
&gt;<br>
&gt;<br>
&gt; This draft is well-written and it is a significant improvement compare=
d to the previous version.<br>
&gt;<br>
&gt; In Section 2:<br>
&gt;<br>
&gt; =A0 &quot;As such, allocations must be made in accordance with the ope=
rational<br>
&gt; =A0 =A0needs of those running the networks that make use of these numb=
er<br>
&gt; =A0 =A0resources and by taking into consideration pool limitations at =
the<br>
&gt; =A0 =A0time of allocation.&quot;<br>
&gt;<br>
&gt; The global IPv4 address pool is currently depleted. =A0Two RIR regions=
 are in IPv4 exhaustion phase. =A0There is a proposal in the RIPE region to=
 remove &quot;need&quot; [1]. =A0I gather that this new version of the Inte=
rnet Numbers Registry System looks towards a future where hosts are IPv6 ac=
cessible. =A0Given that the free IPv6 address pool is very large and that I=
P addresses are not free, what is the rationale for keeping allocations in =
accordance with operational needs?<br>

&gt;</p>
<p dir=3D"ltr">I disagree with need based assignment and believe this draft=
 should remove all such language </p>
<p dir=3D"ltr">The need based policy is not equitable and is nothing but a =
drag in the post ipv4 exhaust world. </p>
<p dir=3D"ltr">I have made a case for moving away from need basis here, <a =
href=3D"http://lists.arin.net/pipermail/arin-ppml/2013-April/026592.html">h=
ttp://lists.arin.net/pipermail/arin-ppml/2013-April/026592.html</a><br></p>

<p dir=3D"ltr">The ietf should really take the time to review what the rirs=
 have done and if their mandate needs to be updated. </p>
<p dir=3D"ltr">Ipv4 belongs to the market and ipv6 does not have scarcity i=
ssues. </p>
<p dir=3D"ltr">CB<br><br><br></p>
<p dir=3D"ltr">&gt; =A0 &quot;Registration Accuracy: A core requirement of =
the Internet<br>
&gt; =A0 =A0Numbers Registry System is to maintain a registry of<br>
&gt; =A0 =A0allocations to ensure uniqueness and to provide accurate<br>
&gt; =A0 =A0registration information of those allocations in order to<br>
&gt; =A0 =A0meet a variety of operational requirements.&quot;<br>
&gt;<br>
&gt; There isn&#39;t any mention of privacy [2] considerations in the draft=
. =A0Is it up to the IETF to set up a one-stop shop for personal data reque=
sts?<br>
&gt;<br>
&gt; Regards,<br>
&gt; -sm<br>
&gt;<br>
&gt; 1. <a href=3D"https://www.ripe.net/ripe/policies/proposals/2013-03">ht=
tps://www.ripe.net/ripe/policies/proposals/2013-03</a><br>
&gt; 2. <a href=3D"http://lists.arin.net/pipermail/arin-ppml/2012-April/024=
596.html">http://lists.arin.net/pipermail/arin-ppml/2012-April/024596.html<=
/a> <br>
</p>

--001a11c26ac61befc204dc6696b0--

From drc@virtualized.org  Fri May 10 18:36:24 2013
Return-Path: <drc@virtualized.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 4FDDD21F8B38 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 18:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H0BhQObrkrnm for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 18:36:18 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 7F50A21F8B33 for <ietf@ietf.org>; Fri, 10 May 2013 18:36:17 -0700 (PDT)
Received: from [10.0.1.4] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id DCD60170B7; Sat, 11 May 2013 01:36:16 +0000 (UTC)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <6.2.5.6.2.20130510103049.0ca25050@resistor.net>
Date: Fri, 10 May 2013 18:36:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1503)
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, 11 May 2013 01:36:24 -0000

SM,

On May 10, 2013, at 11:40 AM, SM <sm@resistor.net> wrote:
> In Section 2:
>=20
>  "As such, allocations must be made in accordance with the operational
>   needs of those running the networks that make use of these number
>   resources and by taking into consideration pool limitations at the
>   time of allocation."
>=20
> The global IPv4 address pool is currently depleted. =20

The IANA IPv4 free pool is exhausted (well, modulo blocks of addresses =
returned to IANA), yes.

> Two RIR regions are in IPv4 exhaustion phase.  There is a proposal in =
the RIPE region to remove "need" [1]. =20

Yes.

> I gather that this new version of the Internet Numbers Registry System =
looks towards a future where hosts are IPv6 accessible. =20

Sure, but it is also looking towards the remaining few IPv4 allocations =
that will be made over the next few years.

> Given that the free IPv6 address pool is very large and that IP =
addresses are not free, what is the rationale for keeping allocations in =
accordance with operational needs?

The fact that the IPv6 address pool is very large does not remove the =
fact that it is a not an infinite resource and thus, constraints must be =
applied to allocation policy. Lacking those constraints, I'm sure you or =
I could come up with an allocation policy that would blow through the =
IPv6 free pool quite quickly. To date, the communities interested in IP =
addressing have established policies that dictate "operational needs" =
should be the primary constraint (as opposed to say constraining on =
geo-political boundaries, by ability to pay, etc). However, the second =
part of that sentence is saying that pool limitations at the time of =
allocation should also be taken into consideration.  Since _at this =
time_ the IPv6 free pool is quite large, it would follow that allocation =
policy constraints would be minimal (as I believe they are).

>  "Registration Accuracy: A core requirement of the Internet
>   Numbers Registry System is to maintain a registry of
>   allocations to ensure uniqueness and to provide accurate
>   registration information of those allocations in order to
>   meet a variety of operational requirements."
>=20
> There isn't any mention of privacy [2] considerations in the draft. =20=


True. The document is documenting current practices and policies. At =
this point in time, I'm unaware of a global privacy practice or policy =
that is applicable to all levels of the Internet Numbers Registry =
System.

> Is it up to the IETF to set up a one-stop shop for personal data =
requests?

I suspect not, but I suspect it isn't up to the IETF to dictate global =
privacy policy either.

Regards,
-drc


From lear@cisco.com  Sat May 11 06:15:02 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C9721F8A4E for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 06:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YxOR4gkG3-U for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 06:14:57 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 36DF721F89A5 for <ietf@ietf.org>; Sat, 11 May 2013 06:14:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=526; q=dns/txt; s=iport; t=1368278097; x=1369487697; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ftDFLSCbG1SIETDpTbvvqEJBhDz6zuskKyinG+sycX4=; b=R/EwZ818Lglhv/hM4mYB3iBOJytFV0TV8r/3JqwO8TlorhhquumCsfeU AcQvcgTW0c4kRcnbsww9/BPhzguCSVoIuWcwBkdg+4sQDDs+2gz6pjECL PE1oZSB++W7k3mSmI5CwLNVIDbo+1ar6/ob74YxsV7POliYN1UnebpV/Y E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAEBDjlGQ/khM/2dsb2JhbABagweDc7xnfxZ0gh8BAQEDASNVARALDgwCBRYEBwICCQMCAQIBRQYNAQcBAYgCBqs5kHCBJo4CB4JCgRMDlyyRNYFXgTk7
X-IronPort-AV: E=Sophos;i="4.87,653,1363132800"; d="scan'208";a="13406134"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 11 May 2013 13:14:56 +0000
Received: from ams3-vpn-dhcp7074.cisco.com (ams3-vpn-dhcp7074.cisco.com [10.61.91.161]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4BDErUG019165 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 May 2013 13:14:54 GMT
Message-ID: <518E4451.4000002@cisco.com>
Date: Sat, 11 May 2013 14:14:57 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org>
In-Reply-To: <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Sat, 11 May 2013 13:15:02 -0000

Dave,

Just on this point:

On 5/11/13 2:36 AM, David Conrad wrote:

> > There isn't any mention of privacy [2] considerations in the draft.  
> True. The document is documenting current practices and policies. At this point in time, I'm unaware of a global privacy practice or policy that is applicable to all levels of the Internet Numbers Registry System.

It's probably worth saying that the various PDPs SHOULD address policy
considerations.  How they address them is a matter for them, individually.

Eliot


From lear@cisco.com  Sat May 11 06:24:34 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84AB921F8ECB for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 06:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MwLVzcLMI+ik for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 06:24:29 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 2677A21F8B90 for <ietf@ietf.org>; Sat, 11 May 2013 06:24:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=303; q=dns/txt; s=iport; t=1368278669; x=1369488269; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6BdY8VcrzZIXlVfmN0VocKcfnAOAs55cE5sc6z+mS1E=; b=cPt4mdDF+/X/VwDpzH0h2DdmdjZmquqpFs6k0gk0PsbFdtAlwr3NuQFs VL8QwNKuUeQjfnpAiBMsXXaTn4m8Tjn2cFcalGSsiB5TARbx1OKU8Tq3T wv7F+9Sel8MJOiVfNGAqEDED2ucjEqNfw2AaPAsZ1AJObvyPVj6U13ncR s=;
X-IronPort-AV: E=Sophos;i="4.87,653,1363132800"; d="scan'208";a="13874679"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 11 May 2013 13:24:28 +0000
Received: from ams3-vpn-dhcp7074.cisco.com (ams3-vpn-dhcp7074.cisco.com [10.61.91.161]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4BDOPEV017391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 May 2013 13:24:26 GMT
Message-ID: <518E468D.6060106@cisco.com>
Date: Sat, 11 May 2013 14:24:29 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <518E4451.4000002@cisco.com>
In-Reply-To: <518E4451.4000002@cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Sat, 11 May 2013 13:24:34 -0000

Uch...  you can see where my head is:

On 5/11/13 2:14 PM, Eliot Lear wrote:
> It's probably worth saying that the various PDPs SHOULD address policy
> considerations. How they address them is a matter for them, individually.


s/policy considerations/privacy considerations/

Grr...

Eliot

From sm@resistor.net  Sat May 11 08:38:48 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7332B21F9397 for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 08:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rs0hDpqoECvu for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 08:38:47 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AA81D21F93AA for <ietf@ietf.org>; Sat, 11 May 2013 08:38:45 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4BFcbtE021297; Sat, 11 May 2013 08:38:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368286722; bh=X8RhZtF0ESpfE1gHlmW3eC+dqpV5PNxrtpbFc2BjUkQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Uh45OFAgfRA8rdJNjhiF1qC22QGI3NyB97mB5sAOSeFSqR9wlLdm1Srqbrus9Hxei 3qvul+oSRZXy4baQQ9+lMD7269s8TJ4WQvKhlKy7uL+g2Sn0ukXu1zI+G2nbpXorVN uUqL4S9HK/1S43LepaFK+XzD5SNk7csNUYRG9EUM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1368286722; i=@resistor.net; bh=X8RhZtF0ESpfE1gHlmW3eC+dqpV5PNxrtpbFc2BjUkQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=b7SUJuZAxp8ORjF3CuYl+ToL17JCqgvXL0S9p0GdEf99UCEr/Zo2suM6LoHV+OmVb PHX4LTNwXjMbVt3ltm+Wk/zWmf5cAPlT7v3KcFdY54YY17wycDvPsSLG/aCfWIkq/2 U//9CDzEQjj1heaGRq3fQ+2Eb0ybfufhJpGqJGhs=
Message-Id: <6.2.5.6.2.20130510231552.0df99d90@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 May 2013 08:17:12 -0700
To: David Conrad <drc@virtualized.org>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
In-Reply-To: <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 May 2013 15:38:48 -0000

Hi David,
At 18:36 10-05-2013, David Conrad wrote:
>Sure, but it is also looking towards the remaining few IPv4 
>allocations that will be made over the next few years.

I am looking at the draft from an IETF perspective.  There is IPv4 
address space for protocol assignments.  It could be said that the 
IETF's role is limited to providing guidance on IP architectural and 
operational considerations (e.g. RFC 6177).  Several years ago some 
RIRs adopted policies which were inconsistent with IAB/IESG 
recommendations.  I suggest leaving IPv4 allocations unrelated to 
protocol assignments up to other communities to avoid further inconsistencies.

>The fact that the IPv6 address pool is very large does not remove 
>the fact that it is a not an infinite resource and thus, constraints 
>must be applied to allocation policy.

The constraints are not set by the IETF.  It's up to other 
communities to see what constraints, if any, should be applied.

>  Lacking those constraints, I'm sure you or I could come up with an 
> allocation policy that would blow through the IPv6 free pool quite 
> quickly. To date, the communities

Yes.  I doubt that you or I would get away with it. :-)

>interested in IP addressing have established policies that dictate 
>"operational needs" should be the primary constraint (as opposed to 
>say constraining on geo-political boundaries, by ability to pay, 
>etc). However, the second part of that sentence is saying that pool 
>limitations at the time of allocation should also be taken into 
>consideration.  Since _at this time_ the IPv6 free pool is quite 
>large, it would follow that allocation policy constraints would be 
>minimal (as I believe they are).

InternetNZ wrote a very good message, in my opinion, a few months to 
argue for the position it took on a proposal.  It applied its 
principles to explain its position.  I would like to look at this in 
terms of principles instead of politics.  From the above I see that 
communities interested in IP addressing set the policy constraints, 
e.g. "operational needs".  If it's a policy it cannot be a principle.

I'll suggest alternative text:

   1) Allocation Pool: IP addresses and AS numbers are fixed length numbers.
      The allocation pools for these number resources are considered as
      resources which are finite.

The principle for the above is to avoid set any constraint unless it 
is necessary for IETF protocols to work.

>True. The document is documenting current practices and policies. At 
>this point in time, I'm unaware of a global privacy practice or 
>policy that is applicable to all levels of the Internet Numbers 
>Registry System.
>
> > Is it up to the IETF to set up a one-stop shop for personal data requests?
>
>I suspect not, but I suspect it isn't up to the IETF to dictate 
>global privacy policy either.

Section 2 is about the goals for distributing number resources (re. 
first sentence).  I suggest removing the third goal as it might be a 
matter of global (or other) policy.  It also makes privacy a 
non-issue as there isn't any relationship between it and the goals.

In Section 5:

   "The discussions regarding Internet Numbers Registry evolution must
    also continue to consider the overall Internet address architecture
    and technical goals referenced in this document."

I'll wordsmith this:

   It is expected that discussions regarding Internet Numbers 
Registry evolution
   will continue to consider the overall Internet address architecture and
   goals mentioned in this document.

I removed the "must".

I noticed the following in Section 5:

   "In addition, in the cases where the IETF sets technical recommendations
    for protocols, practices, or services which are directly related to
    IP address space or AS numbers, such recommendations must be taken
    into consideration in Internet Numbers Registry System policy
    discussions regardless of venue."

The text does not add any value as "must be taken into consideration" 
does mean anything.  The IETF publishes recommendations which people 
can elect to follow or ignore.  If one believes that it is important 
to consider technical recommendations the person or organization can 
try and convince the appropriate venue to state that.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Sat May 11 13:14:30 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C595621F8BC0 for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 13:14:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.339
X-Spam-Level: 
X-Spam-Status: No, score=-102.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RB+vB39C+5RO for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 13:14:30 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7D821F8B18 for <ietf@ietf.org>; Sat, 11 May 2013 13:14:30 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id aq17so10273900iec.1 for <ietf@ietf.org>; Sat, 11 May 2013 13:14:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bhe8ta4TcAaHqryeNdvNJewlyJy793JpjELas6wvd6w=; b=ZCCwiktQ+k9kW2Q9OFn7Zvt03sEtQijhFCrgJwIT/qDv3IYXtp7HcKwKNaPJpSwV8c 4ZL/SKJYHfjsToQxghIeBwUXTcoyd4ZM4vnZeFFD678DFavzT8Q4/BmGzNhjJgUlaFih o0ncri7+OJJ57yQKhUPCn4lKq4oC3/GMRXdmJqIeUBmwORCe9f9X34sLPyjQ+9P1DK6C lPTryNqyOqjALBucUXhS1LrQs4jryeLcCHZGSlsC7xw8kYKeH1iwMXfCCU+yQKE59Ahf f0+Pb+dK/JWzV7EHjia9Bv7HU+o3TSvjt5XyWyRFzkZ/xSguAVDm921BievYFLh3ohSR 4FJg==
X-Received: by 10.50.128.227 with SMTP id nr3mr6000313igb.24.1368303269801; Sat, 11 May 2013 13:14:29 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id ve9sm6952725igb.3.2013.05.11.13.14.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 May 2013 13:14:28 -0700 (PDT)
Message-ID: <518EA69F.9010403@gmail.com>
Date: Sun, 12 May 2013 08:14:23 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet	Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20130510103049.0ca25050@resistor.net>	<D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net>
In-Reply-To: <6.2.5.6.2.20130510231552.0df99d90@resistor.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: Sat, 11 May 2013 20:14:30 -0000

On 12/05/2013 03:17, SM wrote:
...
>> The fact that the IPv6 address pool is very large does not remove the
>> fact that it is a not an infinite resource and thus, constraints must
>> be applied to allocation policy.
> 
> The constraints are not set by the IETF.  It's up to other communities
> to see what constraints, if any, should be applied.

It's up to the IETF to set boundary conditions for the address space
that it created (in the case of IPv6) or inherited (in the case of
IPv4), in order to protect the long-term viability of the Internet.

...

> I'll suggest alternative text:
> 
>   1) Allocation Pool: IP addresses and AS numbers are fixed length numbers.
>      The allocation pools for these number resources are considered as
>      resources which are finite.

That doesn't set any boundary conditions beyond those imposed by
mathematics, and is therefore a no-op. The mention of "operational
needs" is a real boundary condition that makes it clear that
address space is not to be wasted. As has been pointed out from
time to time, it would be quite easy to design an allocation model,
fully respecting the hierarchical constraint in the following
guideline, that blows away galactic quantities of address space,
even for IPv6.

It is entirely appropriate for the IETF and IAB to write a goal
that avoids this.

> The principle for the above is to avoid set any constraint unless it is
> necessary for IETF protocols to work.

No IETF protocol will work if the address space is exhausted of
if BGP4 runs out of steam or otherwise fails. The goals listed in
Section 2 address that.

...
> Section 2 is about the goals for distributing number resources (re.
> first sentence).  I suggest removing the third goal as it might be a
> matter of global (or other) policy.  

No, it's a necessity in order for the two preceding goals to be
verifiably achieved, and to avoid accidental duplication of
addresses.

...

> In Section 5:
> 
>   "The discussions regarding Internet Numbers Registry evolution must
>    also continue to consider the overall Internet address architecture
>    and technical goals referenced in this document."
> 
> I'll wordsmith this:
> 
>   It is expected that discussions regarding Internet Numbers Registry
> evolution
>   will continue to consider the overall Internet address architecture and
>   goals mentioned in this document.
> 
> I removed the "must".

The "must" is necessary.

> 
> I noticed the following in Section 5:
> 
>   "In addition, in the cases where the IETF sets technical recommendations
>    for protocols, practices, or services which are directly related to
>    IP address space or AS numbers, such recommendations must be taken
>    into consideration in Internet Numbers Registry System policy
>    discussions regardless of venue."
> 
> The text does not add any value as "must be taken into consideration"
> does mean anything.  

Er, it means what it says. It is exactly as powerful as any other
"must" or even "MUST" written by the IETF. If you ignore it, your
network might break.

I think that the current wording of the draft is correct.

   Brian

From sm@resistor.net  Sat May 11 16:35:00 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACEE821F8A74 for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 16:35:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOrvQGMZ3vxQ for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 16:34:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C079521F89B0 for <ietf@ietf.org>; Sat, 11 May 2013 16:34:59 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4BNYgTY007453; Sat, 11 May 2013 16:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368315289; bh=WyiDTNhS6/fv7Gjn21xMUqqMDPARqwyQLFABZIrnpQ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GKqUMLG1f78Bfw9m1k1GCVveKGzEiyvlrXsd4Z38XsSqbA1IKtZa6Swex2WR38109 c9Lu17jAAa9i45EmXDBZFyRgE+DnQSkyPKTtn7AIf21dJ7738i4Zq/8APAwtk/C1Qc z7WE+ui/DgWE126DY6sINypEnRFDqJ9+ZVs1vcOA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1368315289; i=@resistor.net; bh=WyiDTNhS6/fv7Gjn21xMUqqMDPARqwyQLFABZIrnpQ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gH5r6CEV81lHT7HvxM5JEDDZmaHOYAzoPuPahQksRoGinLK/OeSYmSdudMwXLWwVX 0tciaS9JSlVvFzSunNy1tVf+a3tgEnUJkfzULcMsHdUdVdAgApCElH1oJ4h4ZOGbah Xnq9lt64TmGy4cqnkTUEEKOBAbAynNk8P8W55JLE=
Message-Id: <6.2.5.6.2.20130511133231.07f7a940@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 May 2013 16:34:24 -0700
To: Tom Vest <tvest@eyeconomics.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
In-Reply-To: <4529DB87-C5E6-4EC0-AA0B-00D261743A2E@eyeconomics.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <4529DB87-C5E6-4EC0-AA0B-00D261743A2E@eyeconomics.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: Sat, 11 May 2013 23:35:00 -0000

At 13:08 11-05-2013, Tom Vest wrote:
>Sorry, but unless you can point to some relevant real-world examples 
>of self-executing, self-sustaining principles, or you're a nihilist 
>and don't really believe that such things as principles exist at 
>all, this is a patently false, bordering on nonsense statement.

I am not suggesting any self-executing or self-sustaining principles.

>One is tempted to ask "work for who?" but that would entail giving 
>this statement more credence that it merits. Since TCP/IP is only 
>useful to the end of communication between two or more nodes, the 
>proposed "principle" of finitude would perfectly consistent with 
>this, and almost every other IETF addressing/attachment protocol 
>*not* working at all.
>
>Or did you mean to say that "The principle for the above is to avoid 
>set any constraint unless it is necessary for IETF protocols to 
>'work' between two virtual machines, under lab conditions"?

What I meant was to leave policy (PDP, etc.) to the communities 
interested in IP addressing.  I'll quote part of a message posted on 
the thread:

   'To date, the communities interested in IP addressing have 
established policies
    that dictate "operational needs" should be the primary constraint 
(as opposed
    to say constraining on geo-political boundaries, by ability to pay, etc).'

The message is at 
http://www.ietf.org/mail-archive/web/ietf/current/msg79200.html in 
case what I was quoted is misrepresented.

At 13:14 11-05-2013, Brian E Carpenter wrote:
>It's up to the IETF to set boundary conditions for the address space
>that it created (in the case of IPv6) or inherited (in the case of
>IPv4), in order to protect the long-term viability of the Internet.

There is some text about Internet address architecture.  It would 
cover that if the relevant communities are agreeable to it.

Regards,
-sm 


From doug.mtview@gmail.com  Sun May 12 11:00:10 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97EC921F859D for <ietf@ietfa.amsl.com>; Sun, 12 May 2013 11:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9KWQU0vIojtw for <ietf@ietfa.amsl.com>; Sun, 12 May 2013 11:00:06 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 2461D21F853D for <ietf@ietf.org>; Sun, 12 May 2013 11:00:05 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id 3so3865710pdj.41 for <ietf@ietf.org>; Sun, 12 May 2013 11:00:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:subject:message-id:date:to :mime-version:x-mailer; bh=pTCbBHiyXlT3iqbsJdC3tCv6WuUSkOhxSS8EnIG7wsI=; b=B3GfVdTBKn+1Ti1gBtxTfPGm2qUv8UFo20Lw/s38InFTVsko0Vs5/C6E1CugF7N0fD KO+cnZJj55kVTmm+dhiI0Ai2GT8OU6u0ecF0JB6MCJMDWhnuDFhqQC9satNVRbJFO+hv n/TkXlJ/QruCnNWcGz5Fp6Vz7TA+Ce6adwTj9rc2wRspgKNOmjt/Wn9kv+4p/3D6+GpO tuln0HDEmN+Thhtkb0ORA6PNbJKXRemtd7Y1f2VCh+/clsRj7/nTtEnKaBBAAkqtVl3s QyLS5TmeMbpW4y9zjC+ejWw/xRWxQFgwwuOqruiQNnas07csEW6mFl4K2E3dpuKtX4kV SJ6w==
X-Received: by 10.66.172.233 with SMTP id bf9mr26076595pac.139.1368381604916;  Sun, 12 May 2013 11:00:04 -0700 (PDT)
Received: from [192.168.2.54] (c-24-6-101-92.hsd1.ca.comcast.net. [24.6.101.92]) by mx.google.com with ESMTPSA id zo4sm10848819pbc.21.2013.05.12.11.00.02 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 May 2013 11:00:03 -0700 (PDT)
From: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B0D2127B-840F-4ED0-A08D-B96EDADE0585"
Subject: DKIM is Harmful as Specified
Message-Id: <3D0FC6FC-43FF-4C1C-9513-839CE98F59BB@gmail.com>
Date: Sun, 12 May 2013 11:00:01 -0700
To: "ietf@ietf.org IETF" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 May 2013 18:00:10 -0000

--Apple-Mail=_B0D2127B-840F-4ED0-A08D-B96EDADE0585
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear ietf,

To better clarify elements within otis-ipv6-email-authent draft, a =
separate I-D is focused primarily on DKIM.

http://tools.ietf.org/html/draft-otis-dkim-harmful-00

Regards,
Douglas Otis=

--Apple-Mail=_B0D2127B-840F-4ED0-A08D-B96EDADE0585
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Dear ietf,</div><div><br></div><div>To better clarify elements within otis-ipv6-email-authent draft, a separate I-D is focused primarily on DKIM.</div><div><br></div><div><a href="http://tools.ietf.org/html/draft-otis-dkim-harmful-00">http://tools.ietf.org/html/draft-otis-dkim-harmful-00</a></div><div><br></div><div>Regards,</div><div>Douglas Otis</div></body></html>
--Apple-Mail=_B0D2127B-840F-4ED0-A08D-B96EDADE0585--

From doug.mtview@gmail.com  Sun May 12 12:48:00 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31F1221F882A; Sun, 12 May 2013 12:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKwakqABPsCu; Sun, 12 May 2013 12:47:56 -0700 (PDT)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0903421F8766; Sun, 12 May 2013 12:47:55 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id ld10so4070495pab.24 for <multiple recipients>; Sun, 12 May 2013 12:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:message-id:references:to:x-mailer; bh=Fa5mJNIcX/lbOSlRN0G92KYD/mWE50a9PQDgYAqJ7wo=; b=wpLJvgbqllXyKyb8ViOHS5KWPE761lf3pLtglV3jArY6R+c5cS1/cp9wR36VrxHbw6 QBHJ7ZpbjvWBMy8AEEV5Wzlj10XYylnIO0QXepKJEZnwC5xwLvm1lFKr9R1N76b/CNpm 3ZsKDag0DtuL0+CYPNUhV6atuY3VbAt+VkEyQefCP3cuWqn7AQ+n8aoP8GOHWC5qFQgh i0KdjlqYfFKnMnLi/Bm5nLF5DfpE8diGZshvQQm2x7MDyJVmFQ5s/ZDYngxm6itvLR62 KnpwhK0iX/IMWM4PbFDufVX1RhmREqS+HhuRYcvdKRwb7OLTu0Qg0goHEu5J5l9JZVjl Bfqw==
X-Received: by 10.66.88.38 with SMTP id bd6mr27476788pab.184.1368388075794; Sun, 12 May 2013 12:47:55 -0700 (PDT)
Received: from ?IPv6:2601:9:4d80:89:dd8a:fced:21fe:910c? ([2601:9:4d80:89:dd8a:fced:21fe:910c]) by mx.google.com with ESMTPSA id wi6sm11075746pbc.22.2013.05.12.12.47.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 May 2013 12:47:54 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_725C512B-CB82-4BFA-B7A7-B1DC8D16860B"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [ietf-dkim] Last Call: Change the status of DKIM (RFC 6376) to Internet Standard
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <20130503162119.31310.96671.idtracker@ietfa.amsl.com>
Date: Sun, 12 May 2013 12:47:52 -0700
Message-Id: <B7A2BAA6-E254-461E-85D2-777A633D4166@gmail.com>
References: <20130503162119.31310.96671.idtracker@ietfa.amsl.com>
To: "ietf@ietf.org IETF" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
Cc: The IESG <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: Sun, 12 May 2013 19:48:00 -0000

--Apple-Mail=_725C512B-CB82-4BFA-B7A7-B1DC8D16860B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear IETF,

Sorry for repeating this message, but the proper subject line had not =
been used.

http://tools.ietf.org/html/draft-otis-dkim-harmful-00
explains why this document should not be supported to proceed as =
currently defined.

Feedback on this I-D is welcome.

Regards,
Douglas Otis




--Apple-Mail=_725C512B-CB82-4BFA-B7A7-B1DC8D16860B
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>Dear IETF,</div></div><div><br></div><div>Sorry for repeating this message, but the proper subject line had not been used.</div><div><br></div><div><a href="http://tools.ietf.org/html/draft-otis-dkim-harmful-00">http://tools.ietf.org/html/draft-otis-dkim-harmful-00</a></div><div>explains why this document should not be supported to proceed as currently defined.</div><div><br></div><div>Feedback on this I-D is welcome.</div><div><br></div><div>Regards,</div><div>Douglas Otis</div><div><br></div><div><br></div><div><br></div></body></html>
--Apple-Mail=_725C512B-CB82-4BFA-B7A7-B1DC8D16860B--

From dhc@dcrocker.net  Sun May 12 21:59:46 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A957021F8F09; Sun, 12 May 2013 21:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.4
X-Spam-Level: 
X-Spam-Status: No, score=-3.4 tagged_above=-999 required=5 tests=[J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y5DwHezBcR+8; Sun, 12 May 2013 21:59:42 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 958FE21F8F0A; Sun, 12 May 2013 21:59:40 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4D4xQLJ024414 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 12 May 2013 21:59:29 -0700
Message-ID: <51907325.7050600@dcrocker.net>
Date: Sun, 12 May 2013 21:59:17 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Douglas Otis <doug_otis@trendmicro.com>, Dave Rand <dave_rand@trendmicro.com>, iesg <iesg@ietf.org>, "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>
Subject: Review of: draft-otis-dkim-harmful
X-Priority: 2 (High)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 12 May 2013 21:59:30 -0700 (PDT)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 04:59:46 -0000

Review of:     DKIM is Harmful as Specified
I-D:           draft-otis-dkim-harmful-00
Reviewed by:   D. Crocker
Review Date:   12 May 2013



Summary:

    DKIM is in wide use for email operations today; it is currently at 
Draft Standard and has been submitted for elevation to full Internet 
Standard.  The nature and purpose of DKIM is described in the opening 
lines of the Abstract for its core specification (RFC 6376):

    DomainKeys Identified Mail (DKIM) permits a person, role, or
    organization that owns the signing domain to claim some
    responsibility for a message by associating the domain with the
    message.  This can be an author's organization, an operational relay,
    or one of their agents.  DKIM separates the question of the identity
    of the Signer of the message from the purported author of the
    message.  Assertion of responsibility is validated through a
    cryptographic signature and by querying the Signer's domain directly
    to retrieve the appropriate public key.

    The current document expresses concerns about DKIM's limitations and
its use, and it re-raises issues that were extensively discussed and
rejected in the original DKIM working group. The document essentially
criticizes DKIM's performance for message validation, rather than for
its stated purpose of affixing a domain name to the message. The
document also cites some exploits that are not prevented/detected by
DKIM, in spite of their being entirely of the scope of the DKIM
specification. The document seems to be basing its justification for
this criticism on the fact there there are some unspecified people or
organizations that misunderstand DKIM functions.

    Much of the text in this document is factually incorrect, confused
and/or confusing, including architectural layer confusion; some of it
is simply irrelevant to the stated purpose of the document.

    Given DKIM's 6+ years of extensive production experience, flaws as
deep as this document claims exist should be more widely perceived by
now.



Detailed Comments:


> Abstract
>
>    Currently, email lacks conventions ensuring SMTP clients can be
>    identified by an authenticated domain.  Unfortunately many hope to
>    use DKIM as an alternative, but it is independent of intended

DKIM is associated with the message object; in technical terms, it is
independent of the message channel, such as SMTP client. (As a handling
agent, an SMTP client might affix a DKIM signature, but the associated
identifier does not carry any explicit or implicit statement of the
handling role.) Hence, the opening sentence is misguided or, at least, 
misleading.

Also, who are the 'many' and what is the evidence of the claimed 
confusion?  DKIM has been in production deployment since 2006.  If the 
dangers and damages threatened in this document were as real and serious 
as claimed, surely we'd have heard of them from others in the community.


>    recipients and domains accountable for sending the message.  This

DKIM is explicitly defined to be affixed by domains declaring 'some' 
responsibility for the message; this may include domains that send the 
message.  Hence, the assertion here is wrong.


>    means DKIM is poorly suited for establishing abuse assessments for
>    unsolicited messaging of commercial email otherwise known as SPAM,

Actually, DKIM is for making trust assessments, not abuse assessments, 
as acknowledged a bit farther down in the text...


>    nor was this initially DKIM's intent.  DKIM lacks message context
>    essential to ensure fair assessment and to ensure this assessment is
>    not poisoned.

I don't know what "message context" means here.

Taken on its own, this sentence sounds portentous but it has no obvious 
meaning or substantiation.


>    DKIM was instead intended to establish increased levels of trust

Exactly.


>    based upon valid DKIM signatures controlling acceptance and what a
>    user sees within the FROM header field.  But DKIM failed to guard

The identifier used by DKIM is independent of the rfc5322.From field and 
the specification is explicit that it carries no relationship to it. 
Hence this sentence is wrong.


>    against pre-pended header fields where any acceptance based on valid
>    DKIM signatures is sure to exclude header field spoofing, especially

It's true that DKIM does not protect against all possible attacks...


>    that of the FROM.  This weakness allows malefactors to exploit DKIM
>    signature acceptance established by high-volume DKIM domains to spoof
>    ANY other domain, even when prohibited within the Signer's network.

It's true that attacks through vectors not covered by DKIM will not be 
prevented or detected by DKIM use...

It's also true that none of these limitations have been noted as 
problems by the DKIM operations community.


> 1.  Introduction
>
>    Currently, IPv4 address reputation provides the primary basis for
>    defending SMTP open services.  Use of IP addresses in this role

I do not understand what "SMTP open services" means here.


>    completely breaks down when dealing with IPv6 [RFC2460].  There are

That's a prediction, not yet an observable fact.

Although the prediction is reasonable, it's not appropriate to assert it 
as fact.  For example there have been some analyses which suggest that 
adaptation of IPv4-based mechanisms might still prove useful.


>    currently 18,209,237,415,985,168 /64 equivalent IPv6 prefixes routed.
>    [v6-BGP-Rpts].  In comparison, for IPv4 there are 2,614,711,792 IP
>    addresses routed.  While IPv4 is reaching its maximum, IPv6 has about
>    0.1% of the available /64 prefix routed and this continues to grow
>    rapidly.  Unlike IPv4, there is no practical means to scan reverse
>    DNS namespace within IPv6 since each /64 prefix may contain any
>    number of PTR records ranging up to 184,000,000,000,000,000,000.
>
>    A technique commonly employed to automate IPv4 address categorization
>    of suitable hosts is to check whether reverse PTR records appear to
>    represent valid hostnames.  Those that represent 4 decimal numbers
>    are often considered unacceptable, for example.  Our processing of
>    reverse DNS namespace in cooperation with network providers now
>    excludes about 38%, or about 1,000,000,000 IPv4 addresses.  Comparing
>    IPv6 /64 prefixes with the remainder of routable IPv4 addresses shows
>    there are 11.3 million times more IPv6 /64 prefixes needing
>    categorization.  In addition, there is no practical means to
>    facilitate this effort.
>
>    Some also suggest there will not be a significant increase in the
>    number of servers running over IPv6 and since their overall number
>    should be comparable, email should still be dealing with a similar
>    number of IP addresses.  Unlike IPv4, IPv6 does not constrain the
>    number of IP addresses assigned to a network interface.  This feature
>    allows each connection from a server to originate from a different IP
>    address over the entire life of its operation while also having an
>    ability to effortlessly change /64 prefixes.  The potential increase
>    allowed by IPv6 may prove explosive.

All three of the above paragraphs are essentially irrelevant to a 
critique of DKIM...


>
>    Many now hope DKIM will be able to offer a domain identity to provide
>    a basis for acceptance to replace that of the IP address used by SMTP

awkward sentence construction...


>    clients.  With a lack of uptake by commercial reputation services,
>    there are proposals within the IETF aimed at establishing DKIM as a

Both claims in this sentence are false.


>    basis for reputation schemes in the Repute WG.  When such an ill-
>    considered effort is combined with DKIM's inability to detect invalid
>    prefixed header fields, the results can prove highly harmful.

The 'ill-considered' apparently refers to the Repute working group, but 
there's no explanation of its flaws.  Since this is offered as the basis 
for harm, it undermines the entire document.

It's also not clear how reference to the Repute WG is relevant to a 
criticism of DKIM.


>
> 2.  Maintaining Trust
>
>    Not every subsystem or protocol layer should be expected to repeat
>    previous security checks, however critical checks should not be
>    assumed, especially those that involve a trivial amount of effort.
>
>
>
> Otis & Rand             Expires November 13, 2013               [Page 4]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>    With high levels of abuse resulting from email's open nature,
>    delegating checks in a structured manner better conserves essential
>    resources.  However, email's highly distributed store and forward
>    protocol could not function if rigid message structures were enforced
>    by the transport.  New authentication or presentation requirements
>    may involve small structural adjustments.  For example,
>    internationalization introduced a format negotiation not assured to
>    survive beyond the next hop.

I do not understand the applicability of the text in this section to to 
the premise of the document, and especially not to the title of the section.


>
> 3.  Responding to Defects and Exploitation
>
>    With the advent of aviation, the world marveled at the skill and
>    intellect taking us to ever greater heights.  With aviation, faults
>    threatening security, that when found, demanded our attention and
>    diligence to effect repair.  As with aviation, the success of email
>    has risen to great heights.  Email has become an integral component

Email does not travel via airplanes, except for those few passengers 
using their laptops, connected during flight.  But perhaps I'm confused 
about the meaning and relevance of this section...


>    in general commerce and the maintenance of security such as reporting
>    system failures, break-in attempts, and facilitating account access
>    recovery.
>
>    Reporting or predicting failure should not be viewed as exhibiting a
>    lack of respect for achieved accomplishments.  Noting and repairing
>    faults only signify the importance of email's prominent role.  As
>    with most security related protocols, responding to noted defects is
>    fairly common.  Not responding to discovered defects in a security
>    related protocol would be shocking.

I do not understand the applicability of the text in this section to to 
the premise of the document.


>
> 4.  SMTP Can't
>
>    SMTP [RFC5321] recommends against rejecting messages based upon
>    perceived defects in the message structure.  This liberal acceptance
>    permits evolutionary changes in message specifications starting at
>    [RFC0822] that was based on [RFC0733] replaced by [RFC2822] and again
>    by [RFC5322], [RFC6152], [RFC6532], and [RFC6854]; the second to last
>    paragraph in section 3 of [RFC5321] provides a definitive statement

Section 3.3, not Section 3.


>    messages should not be rejected due to perceived defects in the
>    [RFC0822] message structure.  The initial reference to [RFC0822] in
>    this paragraph offers two foot notes with the second referencing the
>    latest version of [RFC0822] which is [RFC5322] which itself has
>    recently been updated.  The impact of initially removing text
>    specifically indicating which header fields are not to repeat is

I do not understand what 'removing' is meant here.


>    unknown.  This information was implied within the then-new ABNF

ABNF was new in 1977, not 1982...


>    notation.  Clarifying text for this requirement did not return until
>    the [RFC0822] revision 19 years later which also indicates this
>    specification's success at providing a foundation that allowed email
>    to flourish.

I do not understand the point of the text here.  It seems to be irrelevant.


>
>
>
> Otis & Rand             Expires November 13, 2013               [Page 5]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>    There are many SMTP servers that have been in operation for decades
>    with years passing between security patches.  Such an accomplishment
>    is most remarkable considering the volume of traffic being handled,
>    often from highly malicious sources.  This amazing stability and
>    scalability with high levels of security would not have been possible
>    if SMTP had been expected to validate message formats.
>
>    Expecting SMTP to validate message formats to protect against
>    vulnerabilities pertaining to protocols such as DKIM does not scale.

DKIM has essentially nothing to do with SMTP.  As such, all of the above 
text is irrelevant to a critique of DKIM.


>    The general use of DKIM permits signature checks subsequent to
>    acceptance where only the status of signatures determines internal
>    placement.  As such, it becomes critical to ensure a valid signature
>    is never declared having malformed header field stacks.  To

I can't parse this "As such" sentence.


>    accomplish this, the DKIM specification must change.
>
>
> 5.  DKIM Vulnerability
>
>    DKIM permits a vulnerability by not checking the message header field
>    stack for invalid repeats when signing or verifying a signature.  The

DKIM does not "validate" a message. It associates a domain name with the
message. The difference is fundamental and essential. Again, there are
many attacks DKIM does not protect against, since it isn't trying to
protect against them...


>    DKIM signature process must walk both down and then up the header

No, it is not required to; alternative approaches are viable and permitted.


>    field stack while selecting the header fields to be included in the
>    hash process of the signature.  The DKIM process will even ignore
>    prefixed FROM header fields which is the only header field always
>    included.
>
>    The WG concluded that "listing non-existent header fields as signed"
>    hack added in non-normative language together with opinions that

FWIW, this also had AD support...


>    checking for invalid repeated header fields is not to be considered
>    DKIM's problem.  See section 8.15 of [RFC6376] where this issue was
>    expressed as not an attack against the trust DKIM intends to convey,
>    and thus not a concern for DKIM.  Nevertheless, improperly formed
>    messages may display only the first of multiple header fields that,
>    as a result of erroneous assumptions of there being no invalid
>    repeated header fields, the prefixed header fields are likely to be
>    displayed in lieu of those signed while not impacting DKIM's
>    signature validity.

This text appears to be irrelevant to DKIM's functions, if only because 
DKIM does not cover displays to users.


>
>    DKIM incorrectly assumed the header field stack's starting condition,
>    which DKIM itself is best able to determine, and is an option in the

I don't understand what this sentence is trying to say.


>    OpenDKIM implementation.  This is likely to astonish most recipients
>    that DKIM failed to make a robust effort to maintain the trust it is
>    attempting to convey.  Three members of the WG authored proposed

Small nit:  IETF working group have participants, not 'members'...


>    changes aimed specifically at addressing this issue [DKIM-MH-Attack].
>    At the time, some expressed concerns about whether this might set

This appears to be an attempt to re-raise an issue that was considered 
and rejected by the working group.  How is that productive?


>    back DKIM's standardization process.  As such, DKIM Signers may sign
>    malformed messages (e.g., violate [RFC5322]) and be in compliance

DKIM's RFC 6376, Section 3.8:

    Accordingly, DKIM's design is predicated on valid input.

So the assertion being made here appears to be incorrect.


>    with DKIM specifications.  In addition, receivers may verify these
>
>
>
> Otis & Rand             Expires November 13, 2013               [Page 6]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>    messages as having valid signatures despite multiple instances of a
>    header field only permitted to occur once and also be in compliance
>    with DKIM specifications.  See addendum for examples.
>
>    Use of DKIM on such messages exposes a vulnerability in the
>    evaluation process.  Rather than ensuring essential checks are made
>    prior to producing a result, a wasteful hack was later suggested
>    where extra non-existent header fields could be included in the list
>    of signed header fields.  Any pre-pended header field added after
>    signing would thereby change resulting hashes and invalidate the
>    signature.  Not all domains are attempting to achieve the same level
>    of trust and may be more sensitive to incurring incremental storage
>    requirements.  Some domains may even inadvertently sign invalid
>    repeated header fields because this check had not been required in
>    the DKIM process.  These same DKIM domains are also likely to
>    establish themselves as being Too Big To Block.  These TBTB domains
>    can then be used to spoof other domains that may have otherwise
>    established a high level of trust by implementing the hack where, due
>    to this defect in DKIM, can still do nothing in their defense from
>    the perspective of now deceived recipients.
>
>    This vulnerability in DKIM represents an exploit allowing serious
>    attacks caused by erroneous assumptions made in DKIM's signature
>    process.  There is also a header field, which because of its label,
>    may potentially mislead recipients into believing it contains valid
>    "Authentication-Results" [RFC5451].  Common phrases such as
>    "Authentication-Results", "pass", and "fail", rather than use of
>    result codes belies introductory claims this header is not intended
>    for direct human consumption.
>
>
> 6.  Barriers to an Authenticated Domain
>
>    Some advocate use of DKIM as a means to obtain domain references

I do not understand what "a means to obtain domain references" means here?


>    based on the increased prevalence of this protocol.  DKIM is
>    independent of the domain actually sending the message and the

exactly.


>    recipient by design.  Unfortunately, DKIM also does not attempt to
>    protect against likely abuses that are also beyond the control of the
>    signing domain in which DKIM signature validity conveys no assurance
>    pre-fixed header fields have not changed what recipients see.  As

It's true that there are many abuses that DKIM does not protect against 
and does not attempt to protect against.


>    such, DKIM signing domains can not be held accountable for incidents
>    of abuse appearing to violate subscription policies or that spoof
>    other domains.
>
>    Because of DKIM's vulnerability to header field spoofing, it would
>    never be safe to express positive reputations either.  Any such
>    assurance could be exploited by malefactors to deceive those trusting
>    DKIM results.  In short, a DKIM signed domain as currently defined,
>
>
>
> Otis & Rand             Expires November 13, 2013               [Page 7]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>    can never be safely used in any context, other than the most rigid
>    exclusion of any unsigned content which is well beyond any existing
>    implementation.  It can never be used for email reputation as
>    currently defined.
>
>
> 7.  Domains as a Basis for Managing Traffic
>
>    A manageable basis for assessments can leverage a smaller number of
>    related domains, compared to IPv6 or even IPv4 addresses.  Although

I do not understand what "a smaller number of related domains" means 
here, nor especially how being 'related' is relevant.


>    technically the domain name space can be larger than the massively
>    large IPv6 address space, in practice it is not.  One hundred
>    thousand domains control 90% of Internet traffic out of approximately
>    100 million domains active each month.  The top 150 domains control
>    50% of the traffic, and the top 2,500 domains control 75%.  This
>    level of domain consolidation permits effective fast-path white-
>    listing.  Improvements achieved using domains to consolidate the
>    threat landscape can easily justify added cryptographic
>    authentication burdens.  Even APL resource records [RFC3123] can
>    authenticate EHLO using a single DNS transaction, but this would not
>    allow IPv6 email to be more easily managed, which cryptographic
>    technology can offer.
>
>
> 8.  XMPP Shows the Way Forward
>
>    In addition to SMTP [RFC5321] using StartTLS [RFC3207] XMPP [RFC6122]
>    uses StartTLS [RFC6120] over a different port with many of the
>    features used by web servers such as [RFC2560] as one means to
>    increase scalability.  It seems plausible that by defining SMTP
>    access over a different port is where a new authentication and
>    international requirements can be resolved together.  Of course, port
>    25 can be used, where it might require StartTLS in the case of IPv6
>    connections.

This appears to be proposing a channel-based, one-hop authentication 
mechanism.  One problem is that TLS is rarely used for authentication of 
the client...

In any event, this section is irrelevant to the stated topic of the 
document, namely DKIM 'harm'.



>    Many administrators overlook a serious problem made much worse by
>    chatty protocols that impose processing delays.  Examining server
>    logs will not reveal any problem either, because the limited resource
>    being consumed is the number of outstanding connections TCP is able
>    to support.  Reaching this limit will prevent new connections from
>    being instantiated but this is not logged as an event.  Over time
>    administrators may hear complaints email is not being delivered or
>    just see an ever growing percentage of spam.
>
>
> 9.  IANA Considerations
>
>    This document requires no IANA consideration.
>
>
>
> Otis & Rand             Expires November 13, 2013               [Page 8]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
> 10.  Security Considerations
>
>    This draft intends to describe serious security concerns raised with
>    use of DKIM exacerbated with IPv6 email.  The contained
>    recommendations are expected to reduce the security concerns.  To
>    ensure security, the DKIM specification must change.
>
>
> 11.  References - Informative
>
>    [DKIM-MH-Attack]
>               http://trac.tools.ietf.org/wg/dkim/trac/ticket/24,
>               "Multiple-header-attack alternative proposal", April 2011.
>
>    [RFC0733]  Crocker, D., Vittal, J., Pogran, K., and D. Henderson,
>               "Standard for the format of ARPA network text messages",
>               RFC 733, November 1977.
>
>    [RFC0822]  Crocker, D., "Standard for the format of ARPA Internet
>               text messages", STD 11, RFC 822, August 1982.
>
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997.
>
>    [RFC2460]  Deering, S. and R. Hinden, "Internet Protocol, Version 6
>               (IPv6) Specification", RFC 2460, December 1998.
>
>    [RFC2560]  Myers, M., Ankney, R., Malpani, A., Galperin, S., and C.
>               Adams, "X.509 Internet Public Key Infrastructure Online
>               Certificate Status Protocol - OCSP", RFC 2560, June 1999.
>
>    [RFC2822]  Resnick, P., "Internet Message Format", RFC 2822,
>               April 2001.
>
>    [RFC3123]  Koch, P., "A DNS RR Type for Lists of Address Prefixes
>               (APL RR)", RFC 3123, June 2001.
>
>    [RFC3207]  Hoffman, P., "SMTP Service Extension for Secure SMTP over
>               Transport Layer Security", RFC 3207, February 2002.
>
>    [RFC4291]  Hinden, R. and S. Deering, "IP Version 6 Addressing
>               Architecture", RFC 4291, February 2006.
>
>    [RFC4408]  Wong, M. and W. Schlitt, "Sender Policy Framework (SPF)
>               for Authorizing Use of Domains in E-Mail, Version 1",
>               RFC 4408, April 2006.
>
>    [RFC4941]  Narten, T., Draves, R., and S. Krishnan, "Privacy
>
>
>
> Otis & Rand             Expires November 13, 2013               [Page 9]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>               Extensions for Stateless Address Autoconfiguration in
>               IPv6", RFC 4941, September 2007.
>
>    [RFC4954]  Siemborski, R. and A. Melnikov, "SMTP Service Extension
>               for Authentication", RFC 4954, July 2007.
>
>    [RFC5321]  Klensin, J., "Simple Mail Transfer Protocol", RFC 5321,
>               October 2008.
>
>    [RFC5322]  Resnick, P., Ed., "Internet Message Format", RFC 5322,
>               October 2008.
>
>    [RFC5451]  Kucherawy, M., "Message Header Field for Indicating
>               Message Authentication Status", RFC 5451, April 2009.
>
>    [RFC6120]  Saint-Andre, P., "Extensible Messaging and Presence
>               Protocol (XMPP): Core", RFC 6120, March 2011.
>
>    [RFC6122]  Saint-Andre, P., "Extensible Messaging and Presence
>               Protocol (XMPP): Address Format", RFC 6122, March 2011.
>
>    [RFC6152]  Klensin, J., Freed, N., Rose, M., and D. Crocker, "SMTP
>               Service Extension for 8-bit MIME Transport", STD 71,
>               RFC 6152, March 2011.
>
>    [RFC6376]  Crocker, D., Hansen, T., and M. Kucherawy, "DomainKeys
>               Identified Mail (DKIM) Signatures", RFC 6376,
>               September 2011.
>
>    [RFC6532]  Yang, A., Steele, S., and N. Freed, "Internationalized
>               Email Headers", RFC 6532, February 2012.
>
>    [RFC6854]  Leiba, B., "Update to Internet Message Format to Allow
>               Group Syntax in the "From:" and "Sender:" Header Fields",
>               RFC 6854, March 2013.
>
>    [v6-BGP-Rpts]
>               http://bgp.potaroo.net/v6/as6447/, "BGP Routing Table
>               Analysis Reports/IPv6/AS6447 views", May 2013.
>
>
> Appendix A.  DKIM Examples
>
> From Random User Tue Mar 12 12:07:37 2013
> X-Apparently-To: just4spamdlr@yahoo.com via 72.30.237.8; Tue, 12 Mar 2013 12:08:37 -0700
> Return-Path: <Fake.user@gmail.com>
> Received-SPF: neutral (192.83.249.65 is neither permitted nor denied by domain of gmail.com)
>  A3RleHQvcGxhaW4DAzACA3RleHQvaHRtbAMDMQ--
>
>
>
> Otis & Rand             Expires November 13, 2013              [Page 10]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
> X-YMailISG: Po8J_9cWLDuz5QIo_tChc7OagZYPBIscsK7APx8FMj835hEX
>  clyJxoQr6Ojy40ccEugqmkym_ayJu65fKm.KJY73k6aprxb9s7Bj6P32lpml
>  6yGzxWFYdNXCwcxHtFGdhKe3v7Tjh8x051jkxjIqfuS0vo8J5rZOr.Z__6vD
>  4wiGFDUwFHNUWAwuz_pwp7pZ5HCivuuuyszYVvH0eIFsrQ9crR.rrk_3EQU2
>  Xkv_fInlGDFR8fafFPMOgQ7QOrHhy0zQUbptDEFGdh1QVOyLwIpjwEC7264k
>  4MqxUH7zz_M5JOQzj6dJslH0.iz5y9Sgp6y6kTUHAVP2f_t1hMeRvf3F7WJ6
>  1yY2rZJALIME1CtiNKQJoDctzgGFRnh_5mo415MvUcEIH7qqS5RFgWtXEQpd
>  JIpyYlECDXVUcuASoLmzbuGSiCEVLq7f4EiBTAsaMwXJ07OgXBR.QYDw3VfA
>  Z0AcfnFrUVHNLZtLaFukQKzdk9c6SpHFHSuCAsvLPuZeRy4Ij5ndXd7viyCS
>  IkAHsnhG_u3.nZr3zUDFOrqw8sEKphobj6ZJ8KEXtuhr_tx.94abE1JRJYi5
>  fukj2h8y9s.K10ZxoTClaw41_DD8fxESbyfyTRPytiEXUdK1WEjgS3rAZ0TA
>  WPJPDr063xLYk20UY0V.N5J15lBCtqZcde_9pdXwxVySyXo1KEQOaH3TNRBZ
>  AKMFuCC7NF56aklkiUgk2EWm8iYoHsFez5_HtOz1zmc1dv4mNFOPTaNrXF2X
>  qjFiwfdUipupIlAEc6pIdv0_le.xvz1jnaewEOyxo4dKd2XLVvybLfsLY16U
>  FzLS9MJJ1wC0Cmf3G2SbOmT4ZiAvPjyv8QnHzbSDDDy3hqg8F0uEE03sJ5dm
>  on5FxOHZZ1wCH7DL1QAXpZYxYWKV.h3q69dKQMl6HbnmfT_WZQY4X8uKXqkZ
>  o34v.YmvJxHSRCSmhFpug1EstpJ4gHVitl_eJzT_n6xYQwhNAuMZ9uRjN2xE
>  1Lf7NpgzRf9bFvOpJAlyLoK5Xvxbx711cMgEUfGIha_JtL1P7hyfncRszHDv
>  txgUYzcsVvRyAyVvwDAM.TEBsFhAtqqwOibqo2l5xCBj2yXRbKJ0EOC1JDMs
> HA--
> X-Originating-IP: [192.83.249.65]
> Authentication-Results: mta1225.mail.bf1.yahoo.com from=gmail.com; domainkeys=neutral (no sig);
> from=gmail.com; dkim=pass (ok)
> Received: from 127.0.0.1 (EHLO rdaver.bungi.com) (192.83.249.65)
> by mta1225.mail.bf1.yahoo.com with SMTP; Tue, 12 Mar 2013 12:08:36 -0700
> Received: by rdaver.bungi.com
>         via smail with stdio
>         id <m1UFUYr-00KeXPC@rdaver.bungi.com>
>         for Just4spamdlr@yahoo.com; Tue, 12 Mar 2013 12:08:33 -0700 (PDT)
>         (Smail-3.2.0.94 1997-Apr-22 #591 built 2011-Feb-5)
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>         d=gmail.com; s=20120113;
>         h=mime-version:x-received:date:message-id:subject:from:to
>         :content-type;
>         bh=PS9xMxYwwTGwWXbCd8bjBBm2rwb79wVOSDLhmp+k4b4=;
>         b=qnYVUccLSAi2DGJdUgDDIP9A3uPk3PaxgqhYLBn6xU382MsCi/ICFgKAoFPuwM7BvL
>         AuSuqL6P54cIJ3Pn36h2xmXy+ucNr5r5OqIY63rtvj6Apjr4uW1PzG47J7BGEiP9iwDZ
>         PLTzl9ZLpZXvZZpTCJOXUQP2HF8q6aivCblYZIQcCdVRCftG+A4z0+dEyTHbxoAMx9U3
>         GFISRRHcZ7k7GAyYmLrSr3fUTjvpa1YWoNK+IcSALC2tKVSW5FP1IQAT07f1e8+bOgHh
>         JleaQIw8b1Vjlzhs4hFKLdedmjQqjDJXVP/K3J+t/ggfYn4H547fu6Pb5syKZIiuPf1e
>         yJqA==
>
> MIME-Version: 1.0
> X-Received: by 10.220.221.143 with SMTP id ic15mr6773333vcb.32.1363115257152;
>  Tue, 12 Mar 2013 12:07:37 -0700 (PDT)
> Received: by 10.52.70.169 with HTTP; Tue, 12 Mar 2013 12:07:37 -0700 (PDT)
> Date: Tue, 12 Mar 2013 09:07:37 -1000
> Message-ID: <CA+VnpPKv0s-p2nKkAkNHS4V2SxZehw_6S9QF5p1p2ji+FMof=Q@mail.gmail.com>
>
>
>
> Otis & Rand             Expires November 13, 2013              [Page 11]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
> Subject: An example signed message
> From: Random User <random.j.user.994@gmail.com>
> To: just4spamdlr@yahoo.com
> Content-Type: multipart/alternative; boundary=14dae9cdc33bb0ff5204d7bf00ff
> Content-Length: 280
>
>                          reporting valid signature
>
>
> From Fake User Tue Mar 12 12:07:37 2013
> X-Apparently-To: just4spamdlr@yahoo.com via 72.30.237.8; Tue, 12 Mar 2013 12:09:01 -0700
> Return-Path: <Fake.user@gmail.com>
> Received-SPF: neutral (192.83.249.65 is neither permitted nor denied by domain of gmail.com)
>  A3RleHQvcGxhaW4DAzACA3RleHQvaHRtbAMDMQ--
> X-YMailISG: gFqc.ysWLDtqkdjDpSCH39uGWhgFfnsGdWobzNb5os6sP0We
> _L38eAdX.VKZWQ2F75gFwoipcPyj4g0uKMm_vSayLjrnps9lBxMGLvtTE8kT
> XYxIw6vZb4aFZ_jEcpoRntvJDkZQl4XSGWGakfmJ5G2blTWZ_i1BVkBvj0Sv
> jEymvhoIXZTb_l8C0Jh69ot3MgrNBvjhrBmhCK3sziUtDPpKQPJb_lxCnYKN
> O0SiArQ_TUXrCRFRNsyEiJxzVfSgJWIdsCV5BN3cp..NZ17X8fguB.YxNQjt
> qjVcGMd4IjQioY.a4f1luQxuiCN1yWvYqiLpP6eOCQhMrHt9XOdk32HAXNuJ
> GBraVtjrySTl9Db7PpRC46wlMs3iIUHl3z0d4o6293sMA5qFmnbczGoLRGFs
> RUVlBJuRoJCSYZh5LOwbj0RPQNX2Nmw.LHwF7SY3XcZWFUjvUQQ2sdx63m_J
> Mgy7JHAwBTVH6ytULsbXvu38a5GIYHccfNnDKVjtsrIg9qBDpVASHrRkncL0
> MFLy5FHLb_XBW1TPztCFtlRViKr_HFxMob6aZIte6T57AMqlV2YAHwVNObwx
> WE8ZWTkKNWbXqJYytd3vyuyAHfuseBFP_Jfmj0zVtg52EXpIlDiTANEOTamP
> zeu23QbeRWJd_Gpz9bbGw_OorPdcV.WJOQ29DHpiYAQRgWjJNLjkd8dI.vuM
> vs1Fr7LOiE3wRpSU5AW_hrR4anvGrnwSPOQaFmpNE0pl8n.Vomrp.5NU8cgU
> QYI1UCSPoE_HK5Som2HMPYZFQv0pJSu1NeitXlRM3DHkIMvW4aVYqrHSNVjl
> gGCFFx77c25QW.XAGtySBYWcTzcUlHP4fMa7Wli4u06C4N3pDPiQoXKOC10U
> koXUMKFYmedaZYvEeQRPO3_8xHwKyZ.QInDsnQRwPFWYKvcWCJu4c5zxDMG4
> h1AsyT3CM80nZXk8.ZGhzfTgo810Xjn_OJVgUfkG1z3..ReN990deaWJY8F5
> _j6lRWLZZRzCMwOGpJ6I.jgaN5mNk38Kj6.NYLFCpMTEIt28jIRHD85cfpa3
> iOL3drg1TIKQWrEhS9u3H29niQ_hjHbk7ys6uSJvowilRwO8eB2s.Wz0
> X-Originating-IP: [192.83.249.65]
> Authentication-Results: mta1266.mail.bf1.yahoo.com
> from=gmail.com; domainkeys=neutral (no sig);
> from=gmail.com; dkim=pass (ok)
> Received: from 127.0.0.1 (EHLO rdaver.bungi.com) (192.83.249.65)
>  by mta1266.mail.bf1.yahoo.com with SMTP; Tue, 12 Mar 2013 12:09:00 -0700
>  Received: by rdaver.bungi.com
>         via smail with stdio
>         id <m1UFUZI-00KeXRC@rdaver.bungi.com>
>         for Just4spamdlr@yahoo.com; Tue, 12 Mar 2013 12:09:00 -0700 (PDT)
>         (Smail-3.2.0.94 1997-Apr-22 #591 built 2011-Feb-5)
> From: Fake User <fake.user@gmail.com>
> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>      d=gmail.com; s=20120113;
>      h=mime-version:x-received:date:message-id:subject:from:to
>
>
>
> Otis & Rand             Expires November 13, 2013              [Page 12]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>      :content-type;
>      bh=PS9xMxYwwTGwWXbCd8bjBBm2rwb79wVOSDLhmp+k4b4=;
>      b=qnYVUccLSAi2DGJdUgDDIP9A3uPk3PaxgqhYLBn6xU382MsCi/ICFgKAoFPuwM7BvL
>       AuSuqL6P54cIJ3Pn36h2xmXy+ucNr5r5OqIY63rtvj6Apjr4uW1PzG47J7BGEiP9iwDZ
>       PLTzl9ZLpZXvZZpTCJOXUQP2HF8q6aivCblYZIQcCdVRCftG+A4z0+dEyTHbxoAMx9U3
>       GFISRRHcZ7k7GAyYmLrSr3fUTjvpa1YWoNK+IcSALC2tKVSW5FP1IQAT07f1e8+bOgHh
>       JleaQIw8b1Vjlzhs4hFKLdedmjQqjDJXVP/K3J+t/ggfYn4H547fu6Pb5syKZIiuPf1e
>       yJqA==
> MIME-Version: 1.0
> X-Received: by 10.220.221.143 with SMTP id ic15mr6773333vcb.32.1363115257152;
>  Tue, 12 Mar 2013 12:07:37 -0700 (PDT)
> Received: by 10.52.70.169 with HTTP; Tue, 12 Mar 2013 12:07:37 -0700 (PDT)
> Date: Tue, 12 Mar 2013 09:07:37 -1000
> Message-ID: <CA+VnpPKv0s-p2nKkAkNHS4V2SxZehw_6S9QF5p1p2ji+FMof=Q@mail.gmail.com>
> Subject: An example signed message
> From: Random User <random.j.user.994@gmail.com>
> To: just4spamdlr@yahoo.com
> Content-Type: multipart/alternative; boundary=14dae9cdc33bb0ff5204d7bf00ff
> Content-Length: 280
>
>                      spoofed DKIM with valid signature
>
>
> Appendix B.  Stats
>
>      Total spams:               9438
>      DKIM pass:                  688 (about 25% relayed from large ESPs)
>      DKIM fail:                  189
>      DKIM pass w/multiple from:   28 (about 2% on average)
>      Unsigned:                  8561
>
>                      Looking at a few minutes of spam.
>
>
> Authors' Addresses
>
>    Douglas Otis
>    Trend Micro
>    10101 N. De Anza Blvd
>    Cupertino, CA  95014
>    USA
>
>    Phone: +1.408.257-1500
>    Email: doug_otis@trendmicro.com
>
>
>
>
>
>
>
> Otis & Rand             Expires November 13, 2013              [Page 13]
> 
> Internet-Draft                DKIM-HARMFUL                      May 2013
>
>
>    Dave Rand
>    Trend Micro
>    10101 N. De Anza Blvd
>    Cupertino, CA  95014
>    USA
>
>    Phone: +1.408.257-1500
>    Email: dave_rand@trendmicro.com
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Otis & Rand             Expires November 13, 2013              [Page 14]
> 

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From superuser@gmail.com  Sun May 12 22:46:31 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C83D21F8FEC; Sun, 12 May 2013 22:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lP0w8uuikGUg; Sun, 12 May 2013 22:46:31 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 970C521F8F6D; Sun, 12 May 2013 22:46:30 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id e11so6028356wgh.14 for <multiple recipients>; Sun, 12 May 2013 22:46:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=2Uj1aN8bxa1UMEt7faJo24qoF0wgkXQyLK4ggpHLCBw=; b=SbT0P0KD4Cl4wTTIcCfKrffApRG3ecsevWPAjvZHegE/ZQ8e6q1ICwGXOFVJkyRSsX MfwHybiNvIAtcDaqrdKnQJ5ouTsvwhiIII8SvpN6/9O5wo/I8o+Lcq15AKjJhVH4NxbF AP2CRySkipRN5qisdy7OguKtJbWW5iOETxHmBAQIaPSZ2+qnEQLwtJD1oNFvgS3GRrQc vom/82LWMWykWSEPCxmHzNjJzmZFdiMYD8o5HYkvtcAXv6CCfxVAq85vg05JkIe20jw0 h15R1sY95rI30OxvqLvLO7oC3BAVpFjcVETUg5tfMgnVuvXO7Y49nGbYZB4PA0SIcR7G +J0Q==
MIME-Version: 1.0
X-Received: by 10.180.37.109 with SMTP id x13mr15866681wij.20.1368423989785; Sun, 12 May 2013 22:46:29 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Sun, 12 May 2013 22:46:29 -0700 (PDT)
In-Reply-To: <3D0FC6FC-43FF-4C1C-9513-839CE98F59BB@gmail.com>
References: <3D0FC6FC-43FF-4C1C-9513-839CE98F59BB@gmail.com>
Date: Sun, 12 May 2013 22:46:29 -0700
Message-ID: <CAL0qLwaOR84x73W-nvSZsToJgExyLES5aK65ja+iyeQahsaNbw@mail.gmail.com>
Subject: Re: DKIM is Harmful as Specified
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f6473f5d038cc04dc930974
Cc: "ietf@ietf.org IETF" <ietf@ietf.org>, The IESG <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: Mon, 13 May 2013 05:46:31 -0000

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

Dave has already commented on the confusing and rambling nature of this
document, so I'll focus only on the core claim.

In this document, Doug is re-raising an objection that was discussed long
and hard in the DKIM working group during the development of RFC6376.  The
archives are still available for public review.  The result of that
discussion was the addition of Section 8.15 to that RFC, wherein the
problem is described clearly to bring it to the attention of implementers,
including mitigation steps an application might take if the application
considers this scenario a real threat.  I can speak for one implementation
that included those steps even before the RFC was published; Doug even
references it in his draft.

The few dissenters to the text that became Section 8.15 were given ample
time to propose alternatives that could sway the consensus of the working
group, but failed to do so.

As this draft presents no information that is new since working group
consensus was reached, I don't believe there's any need to reopen the
debate.  It is still not a flaw in DKIM.




On Sun, May 12, 2013 at 11:00 AM, Douglas Otis <doug.mtview@gmail.com>wrote:

> Dear ietf,
>
> To better clarify elements within otis-ipv6-email-authent draft, a
> separate I-D is focused primarily on DKIM.
>
> http://tools.ietf.org/html/draft-otis-dkim-harmful-00
>
> Regards,
> Douglas Otis
>

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

<div dir=3D"ltr"><div>Dave has already commented on the confusing and rambl=
ing nature of this document, so I&#39;ll focus only on the core claim.<br><=
br>In this document, Doug is re-raising an objection that was discussed lon=
g and hard in the DKIM working group during the development of RFC6376.=A0 =
The archives are still available for public review.=A0 The result of that d=
iscussion was the addition of Section 8.15 to that RFC, wherein the problem=
 is described clearly to bring it to the attention of implementers, includi=
ng mitigation steps an application might take if the application considers =
this scenario a real threat.=A0 I can speak for one implementation that inc=
luded those steps even before the RFC was published; Doug even references i=
t in his draft.<br>
<br>The few dissenters to the text that became Section 8.15 were given ampl=
e time to propose alternatives that could sway the consensus of the working=
 group, but failed to do so.<br><br>As this draft presents no information t=
hat is new since working group consensus was reached, I don&#39;t believe t=
here&#39;s any need to reopen the debate.=A0 It is still not a flaw in DKIM=
.<br>
<br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div clas=
s=3D"gmail_quote">On Sun, May 12, 2013 at 11:00 AM, Douglas Otis <span dir=
=3D"ltr">&lt;<a href=3D"mailto:doug.mtview@gmail.com" target=3D"_blank">dou=
g.mtview@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 style=3D"word-wrap:break-word"><div>Dea=
r ietf,</div><div><br></div><div>To better clarify elements within otis-ipv=
6-email-authent draft, a separate I-D is focused primarily on DKIM.</div>
<div><br></div><div><a href=3D"http://tools.ietf.org/html/draft-otis-dkim-h=
armful-00" target=3D"_blank">http://tools.ietf.org/html/draft-otis-dkim-har=
mful-00</a></div><div><br></div><div>Regards,</div><div>Douglas Otis</div><=
/div>
</blockquote></div><br></div>

--e89a8f6473f5d038cc04dc930974--

From bclaise@cisco.com  Mon May 13 03:34:00 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 447F321F9446; Mon, 13 May 2013 03:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.987
X-Spam-Level: 
X-Spam-Status: No, score=-8.987 tagged_above=-999 required=5 tests=[AWL=1.612,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ymdUidkzQ7ny; Mon, 13 May 2013 03:33:56 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id E722A21F942B; Mon, 13 May 2013 03:33:55 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r4DAXsew029514; Mon, 13 May 2013 12:33:54 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r4DAWwOT003732; Mon, 13 May 2013 12:33:14 +0200 (CEST)
Message-ID: <5190C159.2050509@cisco.com>
Date: Mon, 13 May 2013 12:32:57 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com>
In-Reply-To: <5171C416.5070105@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org, gen-art@ietf.org, "A. Jean Mahoney" <mahoney@nostrum.com>, NETMOD Working Group <netmod@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 10:34:00 -0000

Forwarding to the authors and WG

Regards, Benoit
> 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-netmod-rfc6021-bis-01
>     Common YANG Data Types
> Reviewer: Joel M. Halpern
> Review Date: 19-April-2013
> IETF LC End Date: 1-May-2013
> IESG Telechat date: N/A
>
> Summary: This document is nearly ready for publication as a Standards 
> Track RFC
>
> Major issues:
>     (The following may well be a non-issue.)
>     In the revision of the ietf-inet-types, the patterns for the new 
> ip4-address-no-zone and ipv6-address-no-zone are drastically 
> simplified from the ipv4-address and ipv6-address patterns.  The new 
> ipv4-address-no-zone allows any sequence of decimal digits an periods, 
> while the original was carefully defined as dotted quads of 0..255. 
> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of 
> hex digits and colons.  The original patterns were very careful to 
> match rules for validity.  Is there a reason for the change.
>
> Minor issues:
>
> Nits/editorial comments:
>
>


From bclaise@cisco.com  Mon May 13 03:34:51 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64BC421F89E2; Mon, 13 May 2013 03:34:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.309
X-Spam-Level: 
X-Spam-Status: No, score=-9.309 tagged_above=-999 required=5 tests=[AWL=1.290,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t+1UqbXohvht; Mon, 13 May 2013 03:34:47 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 2044921F84B1; Mon, 13 May 2013 03:34:24 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r4DAYNBu029679; Mon, 13 May 2013 12:34:24 +0200 (CEST)
Received: from [10.60.67.87] (ams-bclaise-8916.cisco.com [10.60.67.87]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r4DAXbo4004285; Mon, 13 May 2013 12:33:52 +0200 (CEST)
Message-ID: <5190C181.8020500@cisco.com>
Date: Mon, 13 May 2013 12:33:37 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [Gen-art]  Review: draft-ietf-netmod-rfc6021-bis-01
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com> <518D0635.7040301@joelhalpern.com>
In-Reply-To: <518D0635.7040301@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org, gen-art@ietf.org, "A. Jean Mahoney" <mahoney@nostrum.com>, NETMOD Working Group <netmod@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 10:34:51 -0000

Forwarding to the authors and WG

Regards, Benoit
> I am guessing that the authors intended the addition of the text 
> emphasizing that the no-zone typedefs are derived general typedef 
> addresses the difference in the patterns.
>
> Is there a YANG rule that says tat if typedef X is derived from 
> typedef Y then the string for X must match the pattern for X and the 
> pattern for Y?  If so, then my concern below is misplaced. (The fact 
> that I find the vague pattern for the child misleading is not a fault 
> with the document, but rather in my head, under that requirement.)
>
> Yours,
> Joel
>
> On 4/19/2013 6:24 PM, Joel M. Halpern 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-netmod-rfc6021-bis-01
>>      Common YANG Data Types
>> Reviewer: Joel M. Halpern
>> Review Date: 19-April-2013
>> IETF LC End Date: 1-May-2013
>> IESG Telechat date: N/A
>>
>> Summary: This document is nearly ready for publication as a Standards
>> Track RFC
>>
>> Major issues:
>>      (The following may well be a non-issue.)
>>      In the revision of the ietf-inet-types, the patterns for the new
>> ip4-address-no-zone and ipv6-address-no-zone are drastically simplified
>> from the ipv4-address and ipv6-address patterns.  The new
>> ipv4-address-no-zone allows any sequence of decimal digits an periods,
>> while the original was carefully defined as dotted quads of 0..255.
>> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex
>> digits and colons.  The original patterns were very careful to match
>> rules for validity.  Is there a reason for the change.
>>
>> Minor issues:
>>
>> Nits/editorial comments:
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>>
>
>


From j.schoenwaelder@jacobs-university.de  Mon May 13 03:37:56 2013
Return-Path: <j.schoenwaelder@jacobs-university.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 342CF21F8E9E; Mon, 13 May 2013 03:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.249
X-Spam-Level: 
X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qjlUsqc6NlkM; Mon, 13 May 2013 03:37:51 -0700 (PDT)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD2521F9446; Mon, 13 May 2013 03:37:51 -0700 (PDT)
Received: from localhost (demetrius1.jacobs-university.de [212.201.44.46]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7644320C2C; Mon, 13 May 2013 12:37:50 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius1.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id V-IHdEMKNm7p; Mon, 13 May 2013 12:37:50 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id B745420C23; Mon, 13 May 2013 12:37:49 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 13D48263524C; Mon, 13 May 2013 12:37:47 +0200 (CEST)
Date: Mon, 13 May 2013 12:37:47 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: [Gen-art]  Review: draft-ietf-netmod-rfc6021-bis-01
Message-ID: <20130513103745.GB8186@elstar.local>
Mail-Followup-To: Benoit Claise <bclaise@cisco.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org, IETF discussion list <ietf@ietf.org>, NETMOD Working Group <netmod@ietf.org>, draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com> <518D0635.7040301@joelhalpern.com> <5190C181.8020500@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5190C181.8020500@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF discussion list <ietf@ietf.org>, NETMOD Working Group <netmod@ietf.org>, gen-art@ietf.org, draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org, "A. Jean Mahoney" <mahoney@nostrum.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 10:37:56 -0000

Joel,

this is specified in the third paragraph of section 9.4.6 of RFC 6020:

9.4.6.  The pattern Statement

   The "pattern" statement, which is an optional substatement to the
   "type" statement, takes as an argument a regular expression string,
   as defined in [XSD-TYPES].  It is used to restrict the built-in type
   "string", or types derived from "string", to values that match the
   pattern.

   If the type has multiple "pattern" statements, the expressions are
   ANDed together, i.e., all such expressions have to match.

   If a pattern restriction is applied to an already pattern-restricted
   type, values must match all patterns in the base type, in addition to
   the new patterns.

/js

On Mon, May 13, 2013 at 12:33:37PM +0200, Benoit Claise wrote:
> Forwarding to the authors and WG
> 
> Regards, Benoit
> >I am guessing that the authors intended the addition of the text
> >emphasizing that the no-zone typedefs are derived general typedef
> >addresses the difference in the patterns.
> >
> >Is there a YANG rule that says tat if typedef X is derived from
> >typedef Y then the string for X must match the pattern for X and
> >the pattern for Y?  If so, then my concern below is misplaced.
> >(The fact that I find the vague pattern for the child misleading
> >is not a fault with the document, but rather in my head, under
> >that requirement.)
> >
> >Yours,
> >Joel
> >
> >On 4/19/2013 6:24 PM, Joel M. Halpern 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-netmod-rfc6021-bis-01
> >>     Common YANG Data Types
> >>Reviewer: Joel M. Halpern
> >>Review Date: 19-April-2013
> >>IETF LC End Date: 1-May-2013
> >>IESG Telechat date: N/A
> >>
> >>Summary: This document is nearly ready for publication as a Standards
> >>Track RFC
> >>
> >>Major issues:
> >>     (The following may well be a non-issue.)
> >>     In the revision of the ietf-inet-types, the patterns for the new
> >>ip4-address-no-zone and ipv6-address-no-zone are drastically simplified
> >>from the ipv4-address and ipv6-address patterns.  The new
> >>ipv4-address-no-zone allows any sequence of decimal digits an periods,
> >>while the original was carefully defined as dotted quads of 0..255.
> >>Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex
> >>digits and colons.  The original patterns were very careful to match
> >>rules for validity.  Is there a reason for the change.
> >>
> >>Minor issues:
> >>
> >>Nits/editorial comments:
> >>_______________________________________________
> >>Gen-art mailing list
> >>Gen-art@ietf.org
> >>https://www.ietf.org/mailman/listinfo/gen-art
> >>
> >
> >
> 

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From jmh@joelhalpern.com  Mon May 13 05:18:02 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5460921F9579; Mon, 13 May 2013 05:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puEmthCnPPPS; Mon, 13 May 2013 05:17:57 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id A2F4521F9408; Mon, 13 May 2013 05:17:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 8B0AB1C08E0; Mon, 13 May 2013 05:17:57 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-119.clppva.east.verizon.net [70.106.134.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 1AC461C07C6; Mon, 13 May 2013 05:17:55 -0700 (PDT)
Message-ID: <5190D9E8.7040004@joelhalpern.com>
Date: Mon, 13 May 2013 08:17:44 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>,  "Joel M. Halpern" <jmh@joelhalpern.com>, "A. Jean Mahoney" <mahoney@nostrum.com>, gen-art@ietf.org,  IETF discussion list <ietf@ietf.org>, NETMOD Working Group <netmod@ietf.org>,  draft-ietf-netmod-rfc6021-bis.all@tools.ietf.org
Subject: Re: [Gen-art]  Review: draft-ietf-netmod-rfc6021-bis-01
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com> <518D0635.7040301@joelhalpern.com> <5190C181.8020500@cisco.com> <20130513103745.GB8186@elstar.local>
In-Reply-To: <20130513103745.GB8186@elstar.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 12:18:02 -0000

Thank you Juergen.  I see that the pattern statement is therefore correct.
And presumably it is a judgment call as to hw to write te new pattern to 
restrict the old one.  Personally, I find a pattern statement that 
covers a whole lot of other things, but that happens when combined with 
the parent patter to give the right result, to be a confusing way to 
document what is needed.  But I can not claim it is technically 
incorrect.  (And I suppose that some would claim that repeating the more 
detailed parent pattern is redundant.)

Yours,
Joel

On 5/13/2013 6:37 AM, Juergen Schoenwaelder wrote:
> Joel,
>
> this is specified in the third paragraph of section 9.4.6 of RFC 6020:
>
> 9.4.6.  The pattern Statement
>
>     The "pattern" statement, which is an optional substatement to the
>     "type" statement, takes as an argument a regular expression string,
>     as defined in [XSD-TYPES].  It is used to restrict the built-in type
>     "string", or types derived from "string", to values that match the
>     pattern.
>
>     If the type has multiple "pattern" statements, the expressions are
>     ANDed together, i.e., all such expressions have to match.
>
>     If a pattern restriction is applied to an already pattern-restricted
>     type, values must match all patterns in the base type, in addition to
>     the new patterns.
>
> /js
>
> On Mon, May 13, 2013 at 12:33:37PM +0200, Benoit Claise wrote:
>> Forwarding to the authors and WG
>>
>> Regards, Benoit
>>> I am guessing that the authors intended the addition of the text
>>> emphasizing that the no-zone typedefs are derived general typedef
>>> addresses the difference in the patterns.
>>>
>>> Is there a YANG rule that says tat if typedef X is derived from
>>> typedef Y then the string for X must match the pattern for X and
>>> the pattern for Y?  If so, then my concern below is misplaced.
>>> (The fact that I find the vague pattern for the child misleading
>>> is not a fault with the document, but rather in my head, under
>>> that requirement.)
>>>
>>> Yours,
>>> Joel
>>>
>>> On 4/19/2013 6:24 PM, Joel M. Halpern 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-netmod-rfc6021-bis-01
>>>>      Common YANG Data Types
>>>> Reviewer: Joel M. Halpern
>>>> Review Date: 19-April-2013
>>>> IETF LC End Date: 1-May-2013
>>>> IESG Telechat date: N/A
>>>>
>>>> Summary: This document is nearly ready for publication as a Standards
>>>> Track RFC
>>>>
>>>> Major issues:
>>>>      (The following may well be a non-issue.)
>>>>      In the revision of the ietf-inet-types, the patterns for the new
>>>> ip4-address-no-zone and ipv6-address-no-zone are drastically simplified
>>> >from the ipv4-address and ipv6-address patterns.  The new
>>>> ipv4-address-no-zone allows any sequence of decimal digits an periods,
>>>> while the original was carefully defined as dotted quads of 0..255.
>>>> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex
>>>> digits and colons.  The original patterns were very careful to match
>>>> rules for validity.  Is there a reason for the change.
>>>>
>>>> Minor issues:
>>>>
>>>> Nits/editorial comments:
>>>> _______________________________________________
>>>> Gen-art mailing list
>>>> Gen-art@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/gen-art
>>>>
>>>
>>>
>>
>

From andy@yumaworks.com  Fri May 10 09:33:45 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81CD121F8F62 for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 09:33:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.264
X-Spam-Level: 
X-Spam-Status: No, score=0.264 tagged_above=-999 required=5 tests=[AWL=0.575,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6P7y+40pkjU for <ietf@ietfa.amsl.com>; Fri, 10 May 2013 09:33:44 -0700 (PDT)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 91E7421F856D for <ietf@ietf.org>; Fri, 10 May 2013 09:33:43 -0700 (PDT)
Received: by mail-ie0-f169.google.com with SMTP id u16so8576206iet.28 for <ietf@ietf.org>; Fri, 10 May 2013 09:33:31 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=pZKSWoo6ZlL907/aB8fuu8COapNRykruAgrygBuWtvQ=; b=GKXH2BhpfVh0OxKKJMCWtnTZnr2bwVQ2o9aHYA/ugvrhLeS9Y3rXANpgCI5d8EXHgc +TnoXuLU4x8w6hntUYa5fMlBbquZ8cwfAxkjZ9mbf0Srs4MMyBpxGspK9qm57xqXoy1N lbY59nVMbXyUjQCzUfb0xojAxFH2CvwrvLtvjC8mNIUWqu6mgHQBdQ+Ut3+M2DDsvAsi yBB0o4+OJnEgIHnIS4UDXfCPqukEfpp3EiPpteuzq2ndCCe5Da7UaxwpPzioNJzMljM9 ZrSDSA2XQPLv/LMElMOm30NMKoXJCjl5XJuQMyNbM4B38Df7jJyX7nmgKnGOFInAQX7G uFRQ==
MIME-Version: 1.0
X-Received: by 10.50.120.4 with SMTP id ky4mr2430121igb.86.1368203611391; Fri, 10 May 2013 09:33:31 -0700 (PDT)
Received: by 10.231.125.202 with HTTP; Fri, 10 May 2013 09:33:31 -0700 (PDT)
In-Reply-To: <518D0635.7040301@joelhalpern.com>
References: <5170722E.2070401@nostrum.com> <5171C416.5070105@joelhalpern.com> <518D0635.7040301@joelhalpern.com>
Date: Fri, 10 May 2013 09:33:31 -0700
Message-ID: <CABCOCHT_YLzcNeo36yZA==JA+J0LzD1F0zfqnaTGgvixF47+MQ@mail.gmail.com>
Subject: Re: [Gen-art] Review: draft-ietf-netmod-rfc6021-bis-01
From: Andy Bierman <andy@yumaworks.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=047d7b8746d43ce00a04dc5fba57
X-Gm-Message-State: ALoCoQn79PFzlBRvfJEb1wBzBH+rGXTZ97fIC+ltRuwVv3oCAx807vVJNo8zlrraNbxNmVOH3TCE
X-Mailman-Approved-At: Mon, 13 May 2013 07:02:22 -0700
Cc: gen-art@ietf.org, "A. Jean Mahoney" <mahoney@nostrum.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: Fri, 10 May 2013 16:33:45 -0000

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

On Fri, May 10, 2013 at 7:37 AM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> I am guessing that the authors intended the addition of the text
> emphasizing that the no-zone typedefs are derived general typedef addresses
> the difference in the patterns.
>
> Is there a YANG rule that says tat if typedef X is derived from typedef Y
> then the string for X must match the pattern for X and the pattern for Y?
>  If so, then my concern below is misplaced.  (The fact that I find the
> vague pattern for the child misleading is not a fault with the document,
> but rather in my head, under that requirement.)
>

Yes. RFC 6020, sec. 9.4.6.
All the patterns are ANDed together.


>
> Yours,
> Joel
>
>

Andy


> On 4/19/2013 6:24 PM, Joel M. Halpern 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<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-netmod-rfc6021-bis-**01
>>      Common YANG Data Types
>> Reviewer: Joel M. Halpern
>> Review Date: 19-April-2013
>> IETF LC End Date: 1-May-2013
>> IESG Telechat date: N/A
>>
>> Summary: This document is nearly ready for publication as a Standards
>> Track RFC
>>
>> Major issues:
>>      (The following may well be a non-issue.)
>>      In the revision of the ietf-inet-types, the patterns for the new
>> ip4-address-no-zone and ipv6-address-no-zone are drastically simplified
>> from the ipv4-address and ipv6-address patterns.  The new
>> ipv4-address-no-zone allows any sequence of decimal digits an periods,
>> while the original was carefully defined as dotted quads of 0..255.
>> Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex
>> digits and colons.  The original patterns were very careful to match
>> rules for validity.  Is there a reason for the change.
>>
>> Minor issues:
>>
>> Nits/editorial comments:
>> ______________________________**_________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/**listinfo/gen-art<https://www.ietf.org/mailman/listinfo/gen-art>
>>
>>

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

<br><br><div class=3D"gmail_quote">On Fri, May 10, 2013 at 7:37 AM, Joel M.=
 Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com" targe=
t=3D"_blank">jmh@joelhalpern.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">
I am guessing that the authors intended the addition of the text emphasizin=
g that the no-zone typedefs are derived general typedef addresses the diffe=
rence in the patterns.<br>
<br>
Is there a YANG rule that says tat if typedef X is derived from typedef Y t=
hen the string for X must match the pattern for X and the pattern for Y? =
=A0If so, then my concern below is misplaced. =A0(The fact that I find the =
vague pattern for the child misleading is not a fault with the document, bu=
t rather in my head, under that requirement.)<br>
</blockquote><div><br></div><div>Yes. RFC 6020, sec. 9.4.6.</div><div>All t=
he patterns are ANDed together.</div><div>=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">

<br>
Yours,<br>
Joel<br>
<br></blockquote><div><br></div><div><br></div><div>Andy</div><div>=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
On 4/19/2013 6:24 PM, Joel M. Halpern wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I am the assigned Gen-ART reviewer for this draft. For background on<br>
Gen-ART, please see the FAQ at<br>
<br>
&lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" tar=
get=3D"_blank">http://wiki.tools.ietf.org/<u></u>area/gen/trac/wiki/GenArtf=
aq</a>&gt;.<br>
<br>
Please resolve these comments along with any other Last Call comments<br>
you may receive.<br>
<br>
Document: draft-ietf-netmod-rfc6021-bis-<u></u>01<br>
=A0 =A0 =A0Common YANG Data Types<br>
Reviewer: Joel M. Halpern<br>
Review Date: 19-April-2013<br>
IETF LC End Date: 1-May-2013<br>
IESG Telechat date: N/A<br>
<br>
Summary: This document is nearly ready for publication as a Standards<br>
Track RFC<br>
<br>
Major issues:<br>
=A0 =A0 =A0(The following may well be a non-issue.)<br>
=A0 =A0 =A0In the revision of the ietf-inet-types, the patterns for the new=
<br>
ip4-address-no-zone and ipv6-address-no-zone are drastically simplified<br>
from the ipv4-address and ipv6-address patterns. =A0The new<br>
ipv4-address-no-zone allows any sequence of decimal digits an periods,<br>
while the original was carefully defined as dotted quads of 0..255.<br>
Similarly, te ipv6-address-no-zone allows any arbitrary sequence of hex<br>
digits and colons. =A0The original patterns were very careful to match<br>
rules for validity. =A0Is there a reason for the change.<br>
<br>
Minor issues:<br>
<br>
Nits/editorial comments:<br>
______________________________<u></u>_________________<br>
Gen-art mailing list<br>
<a href=3D"mailto:Gen-art@ietf.org" target=3D"_blank">Gen-art@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/gen-art" target=3D"_blank"=
>https://www.ietf.org/mailman/<u></u>listinfo/gen-art</a><br>
<br>
</blockquote>
</blockquote></div><br>

--047d7b8746d43ce00a04dc5fba57--

From stig@cisco.com  Fri May 10 09:58:24 2013
Return-Path: <stig@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 2A5AC21F89D5; Fri, 10 May 2013 09:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6np02ebi3SSB; Fri, 10 May 2013 09:58:19 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 2A19621F8F12; Fri, 10 May 2013 09:58:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=478; q=dns/txt; s=iport; t=1368205098; x=1369414698; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=cCAwPwFspHJgIkwZuzYsQObc7I8lI1aJxsONWU4/1Jk=; b=dRz2bbBu+1EMoho0QG1FMr+BOTFtzhzTky3tbqWKMyPsOkQHg+nVlAag mgM5L+0CZIvbUPi2ELcHWuitsI+DkDR7ZfmqEMgydB2UCjqibWiN8PK+y yceZ3ima1IbLHYKVddfZjH3Qb4Nech+ZRWhRFUGa6TMf8Cgd6TYKN4BVK M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFANckjVGrRDoG/2dsb2JhbABSgwe9YoJwfBZ0gh8BAQEEOEABEAsOCgkWDwkDAgECAUUGDQEHAQEXh3C9W48oB4NVA4kajhKGFosfgVeBWBw
X-IronPort-AV: E=Sophos;i="4.87,648,1363132800"; d="scan'208";a="78224302"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 10 May 2013 16:58:17 +0000
Received: from [10.33.12.93] ([10.33.12.93]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4AGwGdm020541; Fri, 10 May 2013 16:58:16 GMT
Message-ID: <518D2728.9000606@cisco.com>
Date: Fri, 10 May 2013 09:58:16 -0700
From: Stig Venaas <stig@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Robert Sparks <rjsparks@nostrum.com>
Subject: Re: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com>
In-Reply-To: <518D0E64.6020504@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Mon, 13 May 2013 07:02:22 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "Liubing \(Leo\)" <leo.liubing@huawei.com>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@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, 10 May 2013 16:58:24 -0000

On 5/10/2013 8:12 AM, Robert Sparks wrote:
> Thanks Bing -
>
> The updates make the document better, and I appreciate the resolution of
> referencing Tim's expired draft.

So the solution is to not reference it? I see the name of the draft is
mentioned in the acknowledgments as:
  [draft-chown-v6ops-renumber-thinkabout].

Shouldn't it then be an informational reference? It doesn't make sense
to me to mention a draft in the text and not have a reference.

Stig


From tvest@eyeconomics.com  Sat May 11 13:08:50 2013
Return-Path: <tvest@eyeconomics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8526A21F87B1 for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 13:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpL5cB8TyqEz for <ietf@ietfa.amsl.com>; Sat, 11 May 2013 13:08:45 -0700 (PDT)
Received: from smtp102.ord1c.emailsrvr.com (smtp102.ord1c.emailsrvr.com [108.166.43.102]) by ietfa.amsl.com (Postfix) with ESMTP id 5F05421F884F for <ietf@ietf.org>; Sat, 11 May 2013 13:08:45 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7748F1B0098; Sat, 11 May 2013 16:08:40 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: tvest-AT-eyeconomics.com) with ESMTPA id 0B8CB1B0091;  Sat, 11 May 2013 16:08:39 -0400 (EDT)
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Tom Vest <tvest@eyeconomics.com>
In-Reply-To: <6.2.5.6.2.20130510231552.0df99d90@resistor.net>
Date: Sat, 11 May 2013 16:08:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4529DB87-C5E6-4EC0-AA0B-00D261743A2E@eyeconomics.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Mon, 13 May 2013 07:02:22 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 May 2013 20:08:50 -0000

On May 11, 2013, at 11:17 AM, SM wrote:

> If it's a policy it cannot be a principle.

Sorry, but unless you can point to some relevant real-world examples of =
self-executing, self-sustaining principles, or you're a nihilist and =
don't really believe that such things as principles exist at all, this =
is a patently false, bordering on nonsense statement.

> I'll suggest alternative text:
>=20
>  1) Allocation Pool: IP addresses and AS numbers are fixed length =
numbers.
>     The allocation pools for these number resources are considered as
>     resources which are finite.
>=20
> The principle for the above is to avoid set any constraint unless it =
is necessary for IETF protocols to work.

One is tempted to ask "work for who?" but that would entail giving this =
statement more credence that it merits. Since TCP/IP is only useful to =
the end of communication between two or more nodes, the proposed =
"principle" of finitude would perfectly consistent with this, and almost =
every other IETF addressing/attachment protocol *not* working at all.=20

Or did you mean to say that "The principle for the above is to avoid set =
any constraint unless it is necessary for IETF protocols to 'work' =
between two virtual machines, under lab conditions"?=20

I suggest that the proposed alternative text should be rejected.

>> True. The document is documenting current practices and policies. At =
this point in time, I'm unaware of a global privacy practice or policy =
that is applicable to all levels of the Internet Numbers Registry =
System.
>>=20
>> > Is it up to the IETF to set up a one-stop shop for personal data =
requests?
>>=20
>> I suspect not, but I suspect it isn't up to the IETF to dictate =
global privacy policy either.
>=20
> Section 2 is about the goals for distributing number resources (re. =
first sentence).  I suggest removing the third goal as it might be a =
matter of global (or other) policy. =20

Since uniqueness is a basic constraint for most if not all current =
addressing/attachment-related IETF protocols -- even between two virtual =
machines, under lab conditions -- and would still be a basic constraint =
even if current address protocols were not quantity constrained in any =
way, you seem to be suggesting that the IETF forego not only policy =
statements, but also your own "only work" principle, at least under =
certain circumstances.=20

Bottom line: this word "principle," I do not think it means what you =
think it means.=20

I suggest leaving section three in place.

TV=20






> Regards,
> -sm=20


From tvest@eyeconomics.com  Sun May 12 13:45:57 2013
Return-Path: <tvest@eyeconomics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF8C21F8529 for <ietf@ietfa.amsl.com>; Sun, 12 May 2013 13:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSKElkY-TSJc for <ietf@ietfa.amsl.com>; Sun, 12 May 2013 13:45:52 -0700 (PDT)
Received: from smtp94.ord1c.emailsrvr.com (smtp94.ord1c.emailsrvr.com [108.166.43.94]) by ietfa.amsl.com (Postfix) with ESMTP id CBB9121F84B6 for <ietf@ietf.org>; Sun, 12 May 2013 13:45:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 4450114007E; Sun, 12 May 2013 16:45:52 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.ord1c.emailsrvr.com (Authenticated sender: tvest-AT-eyeconomics.com) with ESMTPA id B8375140083;  Sun, 12 May 2013 16:45:51 -0400 (EDT)
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Tom Vest <tvest@eyeconomics.com>
In-Reply-To: <6.2.5.6.2.20130511133231.07f7a940@resistor.net>
Date: Sun, 12 May 2013 16:45:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC59E3A6-00A6-4940-A2E4-32D9E553DFE7@eyeconomics.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <4529DB87-C5E6-4EC0-AA0B-00D261743A2E@eyeconomics.com> <6.2.5.6.2.20130511133231.07f7a940@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Mon, 13 May 2013 07:02:22 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 May 2013 20:45:57 -0000

On May 11, 2013, at 7:34 PM, SM wrote:

> At 13:08 11-05-2013, Tom Vest wrote:
>> Sorry, but unless you can point to some relevant real-world examples =
of self-executing, self-sustaining principles, or you're a nihilist and =
don't really believe that such things as principles exist at all, this =
is a patently false, bordering on nonsense statement.
>=20
> I am not suggesting any self-executing or self-sustaining principles.

Fair enough; I will assume that we agree that "policies" and =
"principles" are not mutually exclusive and incompatible phenomena, and =
that the class of durable, self-executing, and self-sustaining =
principles is an empty set.

>> One is tempted to ask "work for who?" but that would entail giving =
this statement more credence that it merits. Since TCP/IP is only useful =
to the end of communication between two or more nodes, the proposed =
"principle" of finitude would perfectly consistent with this, and almost =
every other IETF addressing/attachment protocol *not* working at all.
>>=20
>> Or did you mean to say that "The principle for the above is to avoid =
set any constraint unless it is necessary for IETF protocols to 'work' =
between two virtual machines, under lab conditions"?
>=20
> What I meant was to leave policy (PDP, etc.) to the communities =
interested in IP addressing.  I'll quote part of a message posted on the =
thread:
>=20
>  'To date, the communities interested in IP addressing have =
established policies
>   that dictate "operational needs" should be the primary constraint =
(as opposed
>   to say constraining on geo-political boundaries, by ability to pay, =
etc).'
>=20
> The message is at =
http://www.ietf.org/mail-archive/web/ietf/current/msg79200.html in case =
what I was quoted is misrepresented.

I certainly did not intend to misrepresent your position. But given the =
fact that the "part of a message" that you reproduced was offered in =
response to doubts that you yourself raised about the points covered =
therein (esp. "operational need"), what is your position, exactly? As =
David said, "to date" the communities have established policies that are =
broadly informed by the practical implications of the finitude and =
uniqueness constraints on address resource management. However, to =
conclude based on past observations that such will always be true would =
be tantamount to claiming that management of those constraints is =
assured by the operation of (unspecified self-executing, =
self-sustaining) principles. Based on your views as expressed in/around =
draft-moonesamy-rfc2050-historic-00, it's pretty clear that you don't =
see any durable, much less "timeless" principles embodied therein -- but =
that only makes your position on these matters all the more ambiguous.=20=


Perhaps it would help if you would answer the following clarifying =
questions:

1. Is it your position that some other force or principle(s) outside of =
the general mechanisms/practices documented in RFC2050 (and potentially, =
RFC2050-bis) guarantees that IETF-defined addressing protocols will =
"just work" as designed, in perpetuity, and thus the informational =
codification of matters related to the management of finitude and =
uniqueness constraints is at best unnecessary, at worst =
counterproductive? If so, what are those unnamed forces/principles, =
exactly?

2. Is it your position that, if the traditional "communities interested =
in IP addressing" one day elect to adopt policies that make it =
impossible for IETF addressing protocols to fulfill even the basic "just =
work" test, then from the "IETF view"  that should be regarded as a =
perfectly appropriate and acceptable outcome?

> At 13:14 11-05-2013, Brian E Carpenter wrote:
>> It's up to the IETF to set boundary conditions for the address space
>> that it created (in the case of IPv6) or inherited (in the case of
>> IPv4), in order to protect the long-term viability of the Internet.
>=20
> There is some text about Internet address architecture.  It would =
cover that if the relevant communities are agreeable to it.

Could you please clarify which passages about Internet address =
architecture you are suggesting are sufficient to make the sections =
about distribution and uniqueness constraints unnecessary?

Thanks,=20

TV


> Regards,
> -sm=20


From leo.liubing@huawei.com  Sun May 12 18:59:10 2013
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC19521F8D41; Sun, 12 May 2013 18:59:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODqeG74CbjmY; Sun, 12 May 2013 18:59:05 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id A94E921F8464; Sun, 12 May 2013 18:59:04 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARH79014; Mon, 13 May 2013 01:59:03 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 13 May 2013 02:58:45 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Mon, 13 May 2013 02:59:02 +0100
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.102]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Mon, 13 May 2013 09:58:59 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>
Subject: RE: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
Thread-Topic: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
Thread-Index: AQHOTZDVCx2KD3Z6N0mmZwguV2SXypkCXtWQ
Date: Mon, 13 May 2013 01:58:59 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com>
In-Reply-To: <518D0E64.6020504@nostrum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.161]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 13 May 2013 07:02:22 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 01:59:10 -0000

Hi, Robert

Your careful review and comments really helped improving the document a lot=
.
Many thanks to you.

All the best,
Bing

> -----Original Message-----
> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> Sent: Friday, May 10, 2013 11:13 PM
> To: Liubing (Leo)
> Cc: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org;
> gen-art@ietf.org; ietf@ietf.org
> Subject: Re: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.t=
xt
> (updated for -07)
>=20
> Thanks Bing -
>=20
> The updates make the document better, and I appreciate the resolution of
> referencing Tim's expired draft.
> I think you've addressed all my comments except for the one on section
> 5.1, but that's ok.
>=20
> For completeness and ease on the ADs, here's an updated summary:
>=20
> Document: draft-ietf-6renum-gap-analysis-05.txt
> Reviewer: Robert Sparks
> Review Date: May 10, 2013
> IETF LC End Date: April 10, 2013
> IESG Telechat date: May 16, 2013
>=20
> Summary: Ready
>=20
>=20
>=20
> On 5/2/13 6:02 AM, Liubing (Leo) wrote:
> > Hi, Robert
> >
> > Thanks a lot for your continuous careful review.
> > Please see replies inline.
> >
> >> -----Original Message-----
> >> From: Robert Sparks [mailto:rjsparks@nostrum.com]
> >> Sent: Wednesday, May 01, 2013 12:33 AM
> >> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
> >> Cc: gen-art@ietf.org; ietf@ietf.org
> >> Subject: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.tx=
t
> >>
> >> 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-6renum-gap-analysis-05.txt
> >> Reviewer: Robert Sparks
> >> Review Date: April 1, 2013
> >> IETF LC End Date: April 10, 2013
> >> IESG Telechat date: May 16, 2013
> >>
> >> Summary: Ready with nits (that border on minor issues)
> >>
> >> This update improved the readability significantly, and addressed my
> >> major concern about being able to build a list of the gaps. Thank you.
> >>
> >> There are a few issues from my last call review that are still not
> >> addressed.
> >> I have left the classification of minor issue vs nits the same as the
> >> original review to make referring to the earlier review easier,
> >> but please consider all of these Nits. The IESG will need to decide
> >> whether to escalate them.
> >>
> >> I've trimmed away the points that were addressed.
> >>
> >> On 4/1/13 3:46 PM, Robert Sparks wrote:
> >>> ----------------------
> >>> Minor issues:
> >>>
> >>> The document currently references
> >>> draft-chown-v6ops-renumber-thinkabout several times.
> >>> That document is long expired (2006). It would be better to simply
> >>> restate what is
> >>> important from that document here and reference it only once in the
> >>> acknowlegements
> >>> rather than send the reader off to read it.
> >> This version still references that long expired draft. There was also
> >> conversation on apps-discuss
> >> about making that reference normative. IMHO, this is not the right way
> >> to treat the RFC series, and
> >> strongly encourage moving the text that you want to reference into
> >> something that will
> >> become an RFC.
> > [Bing] Maybe Brian's suggestion of putting some texts into an appendix =
is a
> good way. We'll discuss this problem when make the next time update.
> >
> >>> Should section 8 belong to some other document? It looks like
> >>> operational renumbering
> >>> advice/considerations, but doesn't seem to be exploring renumbering
> >>> gaps, except for
> >>> the very short section 8.2 which says "we need a better mechanism"
> >>> without much explanation.
> >> Afaict, this wasn't addressed at all. In particular, "we need a better
> >> mechanism" is still all that
> >> section 8.2 says.
> > [Bing] Sorry for leaving it out. Will do in next update.
> >
> >>> Section 5.1, first bullet. The list below "the impact of ambiguous M/=
O
> >>> flags" says things like
> >>> "there is no standard" and "it is unspecified". I think you are tryin=
g
> >>> to say that there is
> >>> ambiguity in what's written, not that nothing's written. This entire
> >>> list would benefit from
> >>> being recast in terms of what needs to be done (what are the gaps?).
> >> This text remains unmodified.
> > [Bing] We made revision focusing on explaining "what are the gaps", but
> the texts change was omitted, will do in next update.
> >
> >>> ----------------------
> >>> Nits/editorial comments:
> >>>
> >>> There are a few sentences ending with "etc." in the document. Please
> >>> consider deleting the
> >>> word from the list - it doesn't help each sentence make its point.
> >> There were some changes, but mostly these still exist. I'll leave
> >> pressing this point further to the RFC Editor.
> > [Bing] A professional language/editorial check would be helpful.
> >
> >>> Seciton 7.1: The first bullet does not parse. If I guess its meaning
> >>> correctly
> >>> (that it would be benificial to tell hosts that local DNS has been
> >>> updated and
> >>> they may want to make fresh queries), please be careful with the
> >>> wording. The
> >>> hosts don't know which names are likely to resolve locally.
> >> This text remained unchanged, and when coming back to the document
> for a
> >> re-review
> >> (which is somewhat like coming back to an RFC you've read before just
> >> for reference),
> >> it's even harder to understand what it's trying to say than it was whe=
n
> >> reading the document
> >> linearly.
> >>
> >> I think you are trying to say
> >> "A notification mechanism may be needed to indicate _to_ hosts that a
> >> renumbering event has _changed how local recursive DNS servers will
> >> respond_. That mechanism may also need to indicate that such a change
> >> will happen at a specific time in the future."
> > [Bing] I think it's a better description. Will update, thanks much.
> >
> >>> Section 7.1, third bullet - This isn't obviously about notification.
> >>> Why is it
> >>> in this section? What's the gap this is trying to identify?
> >> This text was unchanged.
> > [Bing] For example, if border routers enabled egress filtering based on=
 the
> SIP, then the router need to know the renumbering events on some internal
> nodes. We'll make it clear in the next version.
> >
> >>> Section 9.4 - what is it about these that make them gaps, much less
> >>> unsolvable gaps.
> >>> Is this discussion in the wrong section of the document?
> >> This is now section 10.3 and is mostly unchanged. It's still not clear
> >> why this discussion is in the "unsolvable gaps" section.
> > [Bing] We considered the two points (ID/Locator overloading in transpor=
t
> layer & address caching in app layer ) are too fundamental that might not=
 be
> proper to modify them just in terms of renumbering.
> >
> > Best regards,
> > Bing


From tjc@ecs.soton.ac.uk  Mon May 13 10:36:52 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70C8B21F9360; Mon, 13 May 2013 10:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yqWy7cKTAL7e; Mon, 13 May 2013 10:36:51 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id AF72221F92EC; Mon, 13 May 2013 10:36:50 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4DHaeb7002327;  Mon, 13 May 2013 18:36:40 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4DHaeb7002327
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1368466601; bh=2V0DYH5kp9U5ILMW21bt8kk2W2I=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=l9vEDQOez3IKjkJVvVEJcc75j6MNN0PxoUceAzPSypWWNGuG9SG21fh0mVrQrr9Tx 45hGi5VDDMWGDoB1F1wE29FIdtNrn194D5OOKyCdslLUzuwRk+896BeVot5GnqYuCb PT1MY9H+EPpNHH/Iiujaw3yL+sn11Tjxsli6UuT0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4CIae0430602276Nl ret-id none; Mon, 13 May 2013 18:36:41 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4DHaVuD017767 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 May 2013 18:36:32 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Gen-art telechat review: draft-ietf-6renum-gap-analysis-06.txt (updated for -07)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com>
Date: Mon, 13 May 2013 18:36:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fe2727486afbb9ad7009bcf9319d50dbp4CIae03tjc|ecs.soton.ac.uk|3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk>
References: <5159F239.1060001@nostrum.com> <517FF231.3080700@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D700926@nkgeml506-mbx.china.huawei.com> <518D0E64.6020504@nostrum.com> <8AE0F17B87264D4CAC7DE0AA6C406F453D70E78D@nkgeml506-mbx.china.huawei.com> <3D439D9C-E9FE-427C-9E35-8EC8468202F0@ecs.soton.ac.uk>
To: Liubing (Leo) <leo.liubing@huawei.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4CIae043060227600; tid=p4CIae0430602276Nl; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=6:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4DHaeb7002327
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "draft-ietf-6renum-gap-analysis@tools.ietf.org" <draft-ietf-6renum-gap-analysis@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, 13 May 2013 17:36:52 -0000

Yes, thanks all - I think we're nearly there=85

Tim

On 13 May 2013, at 02:58, Liubing (Leo) <leo.liubing@huawei.com> wrote:

> Hi, Robert
>=20
> Your careful review and comments really helped improving the document =
a lot.
> Many thanks to you.
>=20
> All the best,
> Bing
>=20
>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> Sent: Friday, May 10, 2013 11:13 PM
>> To: Liubing (Leo)
>> Cc: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org;
>> gen-art@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-art telechat review: =
draft-ietf-6renum-gap-analysis-06.txt
>> (updated for -07)
>>=20
>> Thanks Bing -
>>=20
>> The updates make the document better, and I appreciate the resolution =
of
>> referencing Tim's expired draft.
>> I think you've addressed all my comments except for the one on =
section
>> 5.1, but that's ok.
>>=20
>> For completeness and ease on the ADs, here's an updated summary:
>>=20
>> Document: draft-ietf-6renum-gap-analysis-05.txt
>> Reviewer: Robert Sparks
>> Review Date: May 10, 2013
>> IETF LC End Date: April 10, 2013
>> IESG Telechat date: May 16, 2013
>>=20
>> Summary: Ready
>>=20
>>=20
>>=20
>> On 5/2/13 6:02 AM, Liubing (Leo) wrote:
>>> Hi, Robert
>>>=20
>>> Thanks a lot for your continuous careful review.
>>> Please see replies inline.
>>>=20
>>>> -----Original Message-----
>>>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>>>> Sent: Wednesday, May 01, 2013 12:33 AM
>>>> To: renum@ietf.org; draft-ietf-6renum-gap-analysis@tools.ietf.org
>>>> Cc: gen-art@ietf.org; ietf@ietf.org
>>>> Subject: Gen-art telechat review: =
draft-ietf-6renum-gap-analysis-06.txt
>>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background =
on
>>>> Gen-ART, please see the FAQ at
>>>> < http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>>=20
>>>> Please wait for direction from your document shepherd
>>>> or AD before posting a new version of the draft.
>>>>=20
>>>> Document: draft-ietf-6renum-gap-analysis-05.txt
>>>> Reviewer: Robert Sparks
>>>> Review Date: April 1, 2013
>>>> IETF LC End Date: April 10, 2013
>>>> IESG Telechat date: May 16, 2013
>>>>=20
>>>> Summary: Ready with nits (that border on minor issues)
>>>>=20
>>>> This update improved the readability significantly, and addressed =
my
>>>> major concern about being able to build a list of the gaps. Thank =
you.
>>>>=20
>>>> There are a few issues from my last call review that are still not
>>>> addressed.
>>>> I have left the classification of minor issue vs nits the same as =
the
>>>> original review to make referring to the earlier review easier,
>>>> but please consider all of these Nits. The IESG will need to decide
>>>> whether to escalate them.
>>>>=20
>>>> I've trimmed away the points that were addressed.
>>>>=20
>>>> On 4/1/13 3:46 PM, Robert Sparks wrote:
>>>>> ----------------------
>>>>> Minor issues:
>>>>>=20
>>>>> The document currently references
>>>>> draft-chown-v6ops-renumber-thinkabout several times.
>>>>> That document is long expired (2006). It would be better to simply
>>>>> restate what is
>>>>> important from that document here and reference it only once in =
the
>>>>> acknowlegements
>>>>> rather than send the reader off to read it.
>>>> This version still references that long expired draft. There was =
also
>>>> conversation on apps-discuss
>>>> about making that reference normative. IMHO, this is not the right =
way
>>>> to treat the RFC series, and
>>>> strongly encourage moving the text that you want to reference into
>>>> something that will
>>>> become an RFC.
>>> [Bing] Maybe Brian's suggestion of putting some texts into an =
appendix is a
>> good way. We'll discuss this problem when make the next time update.
>>>=20
>>>>> Should section 8 belong to some other document? It looks like
>>>>> operational renumbering
>>>>> advice/considerations, but doesn't seem to be exploring =
renumbering
>>>>> gaps, except for
>>>>> the very short section 8.2 which says "we need a better mechanism"
>>>>> without much explanation.
>>>> Afaict, this wasn't addressed at all. In particular, "we need a =
better
>>>> mechanism" is still all that
>>>> section 8.2 says.
>>> [Bing] Sorry for leaving it out. Will do in next update.
>>>=20
>>>>> Section 5.1, first bullet. The list below "the impact of ambiguous =
M/O
>>>>> flags" says things like
>>>>> "there is no standard" and "it is unspecified". I think you are =
trying
>>>>> to say that there is
>>>>> ambiguity in what's written, not that nothing's written. This =
entire
>>>>> list would benefit from
>>>>> being recast in terms of what needs to be done (what are the =
gaps?).
>>>> This text remains unmodified.
>>> [Bing] We made revision focusing on explaining "what are the gaps", =
but
>> the texts change was omitted, will do in next update.
>>>=20
>>>>> ----------------------
>>>>> Nits/editorial comments:
>>>>>=20
>>>>> There are a few sentences ending with "etc." in the document. =
Please
>>>>> consider deleting the
>>>>> word from the list - it doesn't help each sentence make its point.
>>>> There were some changes, but mostly these still exist. I'll leave
>>>> pressing this point further to the RFC Editor.
>>> [Bing] A professional language/editorial check would be helpful.
>>>=20
>>>>> Seciton 7.1: The first bullet does not parse. If I guess its =
meaning
>>>>> correctly
>>>>> (that it would be benificial to tell hosts that local DNS has been
>>>>> updated and
>>>>> they may want to make fresh queries), please be careful with the
>>>>> wording. The
>>>>> hosts don't know which names are likely to resolve locally.
>>>> This text remained unchanged, and when coming back to the document
>> for a
>>>> re-review
>>>> (which is somewhat like coming back to an RFC you've read before =
just
>>>> for reference),
>>>> it's even harder to understand what it's trying to say than it was =
when
>>>> reading the document
>>>> linearly.
>>>>=20
>>>> I think you are trying to say
>>>> "A notification mechanism may be needed to indicate _to_ hosts that =
a
>>>> renumbering event has _changed how local recursive DNS servers will
>>>> respond_. That mechanism may also need to indicate that such a =
change
>>>> will happen at a specific time in the future."
>>> [Bing] I think it's a better description. Will update, thanks much.
>>>=20
>>>>> Section 7.1, third bullet - This isn't obviously about =
notification.
>>>>> Why is it
>>>>> in this section? What's the gap this is trying to identify?
>>>> This text was unchanged.
>>> [Bing] For example, if border routers enabled egress filtering based =
on the
>> SIP, then the router need to know the renumbering events on some =
internal
>> nodes. We'll make it clear in the next version.
>>>=20
>>>>> Section 9.4 - what is it about these that make them gaps, much =
less
>>>>> unsolvable gaps.
>>>>> Is this discussion in the wrong section of the document?
>>>> This is now section 10.3 and is mostly unchanged. It's still not =
clear
>>>> why this discussion is in the "unsolvable gaps" section.
>>> [Bing] We considered the two points (ID/Locator overloading in =
transport
>> layer & address caching in app layer ) are too fundamental that might =
not be
>> proper to modify them just in terms of renumbering.
>>>=20
>>> Best regards,
>>> Bing
>=20


From ben@nostrum.com  Mon May 13 12:28:14 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C18F821F94CC; Mon, 13 May 2013 12:28:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t-I-nj0wLyez; Mon, 13 May 2013 12:28:14 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id EE63921F949D; Mon, 13 May 2013 12:28:12 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-071-184.mycingular.net [166.147.71.184]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4DJS9Qw095728 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 May 2013 14:28:10 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-ietf-forces-interop-07
Date: Mon, 13 May 2013 14:28:04 -0500
Message-Id: <8EC701FD-4258-4382-9711-B76EFBB3E1BA@nostrum.com>
To: draft-ietf-forces-interop.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 166.147.71.184 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 19:28:14 -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-forces-interop-07
Reviewer: Ben Campbell
Review Date: 2013-05-13
IETF LC End Date: 2013-05-13
IESG Telechat date:=20

Summary: This draft is almost ready for publication as an informational =
RFC. I have a few minor questions and editorial comments that may be =
worth considering prior to publication.

*** Major issues:

None.

*** Minor issues:

-- The draft mentions a couple of instances of tests that failed because =
of an incorrect implementation or differing encapsulation formats. Does =
this suggest that the specifications should be clarified? In particular, =
in the case of encapsulation format mismatch, should the specs include =
stronger requirements to be able to receive all encapsulation formats? =
Or should the number of options be reduced?

-- I have a mild concern that the use of origin country names for each =
implementation could confuse readers into thinking that the countries =
themselves officially participated, rather than organizations from each =
country.


-- section 4.4, last paragraph:

The text says that since the mentioned failures were likely the result =
of bugs, it doesn't indicate an interoperability problem in the specs. I =
have to point out that, it also doesn't prove interoperability in both =
directions for the particular test. It would also be worth commenting on =
whether the probably bugs were programming errors rather than =
misunderstandings of the specification.


*** Nits/editorial comments:

-- The draft uses inconsistent verb tense throughout. I found this a bit =
confusing, as I assume the draft talks entirely about tests that have =
already occurred.

-- IDNits points out that you have several references without explicit =
citations. I see that you called the references out by name in the text, =
but it would be better to include the citations.

-- Section 1, paragraph 6:

Please expand abbreviations on first mention.

-- Section 1.1:

Please expand FE on first mention.

-- section 2.2.2, paragraph 1: "... from China and Japan =
implementations..."

Missing "the".

Is it possible to add a reference for details on the Smartbits testing =
machine?

-- Figure 2:

Do you really want to publish the IP addresses used in an RFC? RFCs live =
forever...

-- Section 2.2.2, paragraph after figure 2:=20

First sentence does not parse.


-- Figure 3:

The figure has some formatting issues, at least in the PDF version. =
Also, is it possible to avoid splitting the figure across the page =
break?

-- section 3.2, paragraph 3: "Because of system deficiency to deploy =
IPSec over TML in Greece,..."

Phrase doesn't parse.

-- section 3.2, paragraph 4: "... over IPSec channel."

Missing "the".

"...to have established..."

to establish.

-- section 4 and subsections:

It seems like some of the test descriptions in 4.X may be redundant to =
the previous scenario descriptions.

-- section 4.1, notes on 28 and 29:

Sentence does not parse.

... notes on 30 and 31:

Missing articles.

-- section 5.1, last paragraph in list item "2.": "The interoperability =
test witnessed that..."

The test _showed_...   [or the _testers_ witnessed...]

-- section 9:

It would be worth mentioning that you explicitly tested for IPSec =
support.


=20






From Malcolm.BETTS@zte.com.cn  Mon May 13 13:01:41 2013
Return-Path: <Malcolm.BETTS@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 17D0921F8696 for <ietf@ietfa.amsl.com>; Mon, 13 May 2013 13:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fCPFtKKYfflv for <ietf@ietfa.amsl.com>; Mon, 13 May 2013 13:01:36 -0700 (PDT)
Received: from zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id E917D21F92C2 for <ietf@ietf.org>; Mon, 13 May 2013 13:01:35 -0700 (PDT)
Received: from zte.com.cn (unknown [192.168.168.119]) by Websense Email Security Gateway with ESMTP id BD2E15C8BF for <ietf@ietf.org>; Tue, 14 May 2013 04:01:09 +0800 (CST)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id DC140177ACE1 for <ietf@ietf.org>; Tue, 14 May 2013 04:01:07 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id r4DK10YY024761 for <ietf@ietf.org>; Tue, 14 May 2013 04:01:00 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
Subject: MalcolmBETTS90013533 is out of the office.
Auto-Submitted: auto-generated
From: Malcolm.BETTS@zte.com.cn
To: ietf@ietf.org
Message-ID: <OF40B6DF4F.F4A3F217-ON48257B6A.006DF4BB-48257B6A.006DF4BB@zte.com.cn>
Date: Tue, 14 May 2013 04:01:00 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2013-05-14 04:00:48
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-MAIL: mse01.zte.com.cn r4DK10YY024761
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 May 2013 20:01:41 -0000

I will be out of the office starting  10/05/2013 and will not return until
20/05/2013.

I will not have access to email, I will respond to your message when I
return on May 20th.


From sm@resistor.net  Mon May 13 21:34:34 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7A911E80F9 for <ietf@ietfa.amsl.com>; Mon, 13 May 2013 21:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.607
X-Spam-Level: 
X-Spam-Status: No, score=-101.607 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zjQ-j5VmPG9A for <ietf@ietfa.amsl.com>; Mon, 13 May 2013 21:34:33 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B93A11E80EF for <ietf@ietf.org>; Mon, 13 May 2013 21:34:33 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4E4YGFc018624; Mon, 13 May 2013 21:34:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368506064; bh=4z12kl5u2oyc1/Gi9RptAOKf3rJYw2iMmuTh6Z5I6DU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=40AOVC0Rywuf2AC1VFNKOGfAAjWDwLOKIMkev7tC4DoovmkepOITm6Y14pPFzdND6 V8JhKYB7FiEq8avy1uiPcYLHu5/guNgiqEvXEi9Hkc93VuQqWO6Mv6NAQX054HjoOF o9N++OfgYzjASlpD52d0nmUKlkbZMyTrxkWq6lk0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1368506064; i=@resistor.net; bh=4z12kl5u2oyc1/Gi9RptAOKf3rJYw2iMmuTh6Z5I6DU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=z1Ka/IYSTTJZ6wLqoybg4BNwmxxFRg26Aj/FumaCfLXychGDuQZX4y6JwHs/Y+3a3 y4GB/cXIXeYFSKC9i0mEnWc4zeniPT4YMOKU8TIyZFehfCZzcgZgYtH+44NANwr8WH +EQvI2Z8auScWkiwt960cqIIbLd9AUX7lQoB22kM=
Message-Id: <6.2.5.6.2.20130512144959.0d2b6c00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 13 May 2013 01:49:16 -0700
To: Tom Vest <tvest@eyeconomics.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
In-Reply-To: <DC59E3A6-00A6-4940-A2E4-32D9E553DFE7@eyeconomics.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <4529DB87-C5E6-4EC0-AA0B-00D261743A2E@eyeconomics.com> <6.2.5.6.2.20130511133231.07f7a940@resistor.net> <DC59E3A6-00A6-4940-A2E4-32D9E553DFE7@eyeconomics.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: Tue, 14 May 2013 04:34:34 -0000

At 13:45 12-05-2013, Tom Vest wrote:
>I certainly did not intend to misrepresent your position. But given 
>the fact that the
>  "part of a message" that you reproduced was offered in response to 
> doubts that you yourself raised about the points covered therein 
> (esp. "operational need"), what is your position, exactly? As David 
> said, "to date" the communities have established policies that are 
> broadly informed by the practical implications of the finitude and 
> uniqueness constraints on address resource management. However, to 
> conclude based on past observations that such will always be true 
> would be tantamount to claiming that management of those 
> constraints is assured by the operation of (unspecified 
> self-executing, self-sustaining) principles. Based on your views as 
> expressed in/around draft-moonesamy-rfc2050-historic-00, it's 
> pretty clear that you don't see any durable, much less "timeless" 
> principles embodied therein -- but that only makes your position on 
> these matters all the more ambiguous.

I prefer to keep draft-housley-rfc2050bis-01 separate from other 
drafts to keep matters simple.  My position is that it is better to 
work towards consensus.

>Perhaps it would help if you would answer the following clarifying questions:
>
>1. Is it your position that some other force or principle(s) outside 
>of the general mechanisms/practices documented in RFC2050 (and 
>potentially, RFC2050-bis) guarantees that IETF-defined addressing 
>protocols will "just work" as designed, in perpetuity, and thus the 
>informational codification of matters related to the management of 
>finitude and uniqueness constraints is at best unnecessary, at worst 
>counterproductive? If so, what are those unnamed forces/principles, exactly?
>
>2. Is it your position that, if the traditional "communities 
>interested in IP addressing" one day elect to adopt policies that 
>make it impossible for IETF addressing protocols to fulfill even the 
>basic "just work" test, then from the "IETF view"  that should be 
>regarded as a perfectly appropriate and acceptable outcome?

I don't have an opinion about questions (1) or (2).

>Could you please clarify which passages about Internet address 
>architecture you are suggesting are sufficient to make the sections 
>about distribution and uniqueness constraints unnecessary?

The comment was in a reply to a comment from another person.  There 
wasn't any mention of "distribution and uniqueness constraints" in 
the quoted text.

Regards,
-sm  


From jari.arkko@piuha.net  Tue May 14 02:11:20 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6523521F90FC for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 02:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level: 
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvy5VHZQIVn1 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 02:11:16 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2523121F90B9 for <ietf@ietf.org>; Tue, 14 May 2013 02:11:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 700C42CC56 for <ietf@ietf.org>; Tue, 14 May 2013 12:11:14 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SOrYk2teyLmD for <ietf@ietf.org>; Tue, 14 May 2013 12:11:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id EFF222CC53 for <ietf@ietf.org>; Tue, 14 May 2013 12:11:12 +0300 (EEST)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: article on innovation and open standards
Message-Id: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net>
Date: Tue, 14 May 2013 11:11:13 +0200
To: "ietf@ietf.org list" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 09:11:20 -0000

Just FYI that I wrote another article, this time on "permissionless =
innovation" and the role of open standards. We've talked about these =
topics earlier, but this has been on my mind recently - I've been =
traveling in recent weeks and talking about the roles of various =
organisations and styles of standards-making with many people. =
(Currently at the WTPF in Geneva=85)

Here's the article:

http://www.ietf.org/blog/2013/05/permissionless-innovation/

Comments and thoughts appreciated, as always.

Jari


From fluffy@cisco.com  Tue May 14 06:58:45 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C246221F905D for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 06:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXIqRyVxbupX for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 06:58:41 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id EA72721F8F03 for <ietf@ietf.org>; Tue, 14 May 2013 06:58:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3207; q=dns/txt; s=iport; t=1368539921; x=1369749521; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=EXRUxEZw6TB/OqERdlv2emU8EkBTJHecUa1OfwN3vtY=; b=LG+X9C4IblmVv41gwBnb95/WYkDaMTel18Fpo0Of8+oL88ssbIuObUsP +dkLmjy9P4eoXGA2Uvf78R1vJE6iqWb5nO683XpwKlceKvnWJM3IoNoPU a8wEvtpBZsiMGKVSivh8omnKxopJJrG2QU3f5HdVlgU0TftiNiJYlHcml 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFABRCklGtJV2c/2dsb2JhbABagwc3wCx+FnSCHwEBAQMBHR06BQULAgEIIhQQMiUCBA4FCAELh3IGDK5Djy2OawIxB4J0YQOocYMPgic
X-IronPort-AV: E=Sophos;i="4.87,670,1363132800"; d="scan'208";a="207309556"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 14 May 2013 13:58:40 +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 r4EDwec4023576 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 May 2013 13:58:40 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.192]) by xhc-aln-x09.cisco.com ([173.36.12.83]) with mapi id 14.02.0318.004; Tue, 14 May 2013 08:58:40 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHOUKsiXOVpLl4nP0WcdEFu4Zh95g==
Date: Tue, 14 May 2013 13:58:39 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F8513710F86AC24DA258C985B0EFA424@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 14 May 2013 13:58:45 -0000

Few thoughts.=20

1) don't get wrapped around the axel of STD, PS, Foo bar label, it has noth=
ing to do with the problem that that IESG believes many drafts need changes=
 to fix significant problems. Lots of people imply that the IESG is setting=
 the bar too high but when you look at the changes that are made to drafts =
from point they go in, to point they come out of IESG it seems to be a rare=
 example where people don't agree that major changes were an improvement an=
d needed. =20

2) On the point of what the IESG should be doing, I would like to see the w=
hole IESG say they agree with the Discuss Criteria document and will stay w=
ithin that (or change it if they disagree). The cross area review teams mig=
ht want to also provide comments within this context.=20

3) Require each pub request  from a WG to come with names of 3 nom com elig=
ible people that are willing to say "I have carefully reviewed this draft a=
nd I believe it is ready to be published as an RFC". If a WG can't find 3 p=
eople to do this, it should probably be closed. You might consider somethin=
g similar for AD sponsored drafts but I am more interested in the WG ones.=
=20

4) Get the ADs involved earlier. My experience is that many ADs won't say m=
uch because they are worried that they would be over influencing the WG. AD=
s got the job because we think they are the right people to provide influen=
ce and obviously it would be better to get that early rather than late.=20

5) Given how long a WG takes, I have no problem with time IESG / RFCEd take=
s. I would suggest mitigating this concern by clearly telling the community=
 that if there were a spec that truly needed to be fast tracked for some re=
al reason, you would make it priority. And on the rare occasion that is nee=
ded, do it and track the stats for fast track separately. I would guess tha=
t less than 1 in 100 needs this and you could do theses with delays in the =
small numbers of weeks instead of months. How fast you can move when really=
 needed is more important to me than the average and I know that the IESG/I=
ANA/RFCEd team works well in parallel and can move fast when needed.=20

6) Over the long term, set up the tools to separately track IESG / RFCEd ti=
me where the ball is in the authors court.=20

7) Remember that in the end, the goal is not a standard. The goal is an fea=
ture rich interopeable internet that is a fertile ground for inovation. Hig=
h quality and relevant standards that think about the future are the way to=
 get there. The goal is not to publish lots of specification that aren't us=
ed and don't work.=20

Cullen


On May 1, 2013, at 9:33 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> I wrote a blog article about how we do a fairly significant amount of rev=
iews and changes in the late stages of the IETF process. Next week the IESG=
 will be having a retreat in Dublin, Ireland. As we brought this topic to o=
ur agenda, Pete and I wanted to raise the issue here and call for feedback =
& ideas for improving the situation with all of you.
>=20
> http://www.ietf.org/blog/2013/05/balancing-the-process/
>=20
> Jari
>=20


From Ted.Lemon@nominum.com  Tue May 14 09:34:21 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 289D221F90BB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 09:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.531
X-Spam-Level: 
X-Spam-Status: No, score=-106.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8AASZKYI5Oy for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 09:34:14 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id DAF1E21F8B90 for <ietf@ietf.org>; Tue, 14 May 2013 09:34:13 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUZJnhfgEPL+Qh3OKtaYkxgOK7ozDbYo7@postini.com; Tue, 14 May 2013 09:34:13 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 748D21B816C for <ietf@ietf.org>; Tue, 14 May 2013 09:34:13 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 6DA0919005D; Tue, 14 May 2013 09:34:13 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-02.WIN.NOMINUM.COM ([64.89.228.134]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 14 May 2013 09:34:13 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgA=
Date: Tue, 14 May 2013 16:34:12 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.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: <6F13E509914CAF4D9E3F562C05A701C1@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 14 May 2013 16:34:21 -0000

On May 14, 2013, at 9:58 AM, "Cullen Jennings (fluffy)" <fluffy@cisco.com> =
wrote:
> 2) On the point of what the IESG should be doing, I would like to see the=
 whole IESG say they agree with the Discuss Criteria document and will stay=
 within that (or change it if they disagree). The cross area review teams m=
ight want to also provide comments within this context.=20

I am not entirely convinced that the DISCUSS criteria are complete.   There=
 are some rules in the criteria that are intended to curb abuse, and that I=
 think do have that effect, but that also would make some very appropriate =
DISCUSSes fail to meet the criteria.   I don't really know how to address t=
hat problem.   E.g. the rule about not coming up with new DISCUSSes: if a D=
ISCUSS winds opening up a can of worms, it ought to be possible to enlarge =
the DISCUSS, but I think that the rule about not adding new DISCUSSes after=
 the first DISCUSS tends to forbid that, and the reason given is a good one=
.   Having said that, I don't think the right answer is to ignore that requ=
irement.  I don't actually have a good answer.

It's worth noting that ADs are not omniscient, and hence the DISCUSS criter=
ia apply to what the AD entering the DISCUSS _knows_, not to the full state=
 of all knowledge in the world.   If someone other than the AD has knowledg=
e that they think means that the DISCUSS doesn't meet the criteria, that do=
esn't mean the DISCUSS doesn't mean the criteria.   In this case, the criti=
c needs to communicate it to the AD, who may or may not agree with the crit=
ic's point of view.   This is not to say that it's never correct to say "th=
is doesn't meet the DISCUSS criteria."   But the reason given should be tha=
t it would be obvious to anyone reading the DISCUSS that it didn't meet the=
 criteria.   The critic's expert knowledge can't be given as a reason.

I have also noticed that some authors have the impression that a DISCUSS me=
ans the AD doesn't like the document, or doesn't want the document to advan=
ce, or is a non-negotiable pronouncement from on high that the authors shou=
ld not question.   This is certainly not my motivation when I enter a DISCU=
SS.   I'm just some guy who got nominated by the nomcom.   Hopefully I'm qu=
alified, but I don't claim to be right.   I have seen DISCUSSes I've raised=
 improve documents, and I've seen DISCUSSes I've raised turn out not to req=
uire any change, but just some discussion to clear up a misunderstanding on=
 my part.  I very much hope that in the latter case, the author will argue =
back, and not just make a change to shut me up!

The reason I raise a DISCUSS rather than a comment is that at the time I'm =
writing the DISCUSS, it appears _to me_ to be the case that there is a prob=
lem that ought to be addressed before the document is published.   I may th=
ink it's generally a great document, but I want the concern I've raised to =
be addressed before it moves forward.   That is _all_ a DISCUSS from me mea=
ns.   If I think the document is an irretrievably bad idea, I will abstain,=
 and say why I think so.


From carlosm3011@gmail.com  Tue May 14 09:45:28 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCAC21F90C1 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 09:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+8qQ6DzPRcE for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 09:45:26 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4B69A21F8D84 for <ietf@ietf.org>; Tue, 14 May 2013 09:45:26 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ii15so417157qab.11 for <ietf@ietf.org>; Tue, 14 May 2013 09:45:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ig3Zy0+pUOSCgpGTwrI7E2fVwmgKbFnQXyLhiq+FmVs=; b=kLbPDgcc1ixYVtDC1FcFcqWhkuVZlaHZ1EEe92wcPy89u5lWaNDs8HB55y1JkT9aKA 5NvDRVt7CyeyHEb2Hfo8ybk0VKd54oWP0uj+Mx75OS1C7e+3vxiuJKGM0i1ogpptOVlM nCxRdsdc6zonNaYrnN1Ghm8lU+6x9PrKL1LlYPmPPVojlmLGcoZYjQJaJ9nIsnDb3U/C JT08PLYg9X3ug+ALPPccd4yrw7tEStUZsQZM7Cx4zYRJ3lgeSOzfGXWG3WFDyS5gcloS souNoYAPyFp5LeiIx/ZJ5F/OKjq6VDGtL5fkzQXxLEz6EJQiGd5jRmUfD8af3dX7p320 r5oA==
X-Received: by 10.229.155.201 with SMTP id t9mr5274115qcw.155.1368549925784; Tue, 14 May 2013 09:45:25 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:286f:9cea:21f6:8f2d]) by mx.google.com with ESMTPSA id j9sm15445505qas.3.2013.05.14.09.45.22 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 May 2013 09:45:24 -0700 (PDT)
Message-ID: <51926A21.5090307@gmail.com>
Date: Tue, 14 May 2013 13:45:21 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>
In-Reply-To: <A5D17763-847B-4A29-8343-844588440BF2@piuha.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
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 16:45:28 -0000

Just to echo in some form what others have said, I believe that an
intermediate stage between I-D and RFC is needed.

I don't have a name for it, but conceptually would be something like
'feature freeze', e.g. no more tweakings to the protocol, or base spec
are to be introduced (unless a major showstopper is discovered), and
just nits and maybe IANA considerations are left to add / discuss.

This would help by sending a clear signal to developers when it's
reasonable to start implementing a given I-D.

A couple of days ago I was part of an email exchange in WEIRDS where
something along this lines happened, when someone proposed an addition
to a base spec that, at least myself, considered already 'frozen'.

The confusion is understandable. Someone entering a WG at a later stage
during the development of an I-D has no way of knowing if the base spec
/ protocol has been agreed and considered stable by the rest of the
participants.

Yes, sure, he/she could comb the ML archives, but I don't think that's
either productive nor even viable in every case, since this 'freezing'
is (in my experience) more like a 'shared feeling' in the ML and not
(usually) explicitly signaled.

IMO, this could also help reducing the length of the overall process and
I would think such a signal would lead to more 'running code' earlier in
the process.

cheers!

~Carlos

On 5/1/13 12:33 PM, Jari Arkko wrote:
> I wrote a blog article about how we do a fairly significant amount of reviews and changes in the late stages of the IETF process. Next week the IESG will be having a retreat in Dublin, Ireland. As we brought this topic to our agenda, Pete and I wanted to raise the issue here and call for feedback & ideas for improving the situation with all of you.
> 
> http://www.ietf.org/blog/2013/05/balancing-the-process/
> 
> Jari
> 

From fluffy@cisco.com  Tue May 14 09:55:43 2013
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0FAB21F91D4 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 09:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BkZq+S+oomoI for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 09:55:27 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id BF92121F852A for <ietf@ietf.org>; Tue, 14 May 2013 09:55:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4987; q=dns/txt; s=iport; t=1368550510; x=1369760110; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=aD7Unwk+maaL+IV+L+hT5/wETDVwzUaPFGm/GWXPM28=; b=KdvDGwTYIz2DAE/TOYQu6H+XpkaiTBHB3PBJZy5Xp/VWsloW9Kt/5mZp ZMhLCGAEgmQClWI2VZIUpGQxkLZdN6KSkvXDvmrfh39jcihUUs/yWxLhi +Mz+ud0JwavoUl3TZk5pmQldszhnGfE1MN6HF0Qn+fh3x4m+jnUJwAym+ Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhEFAGNrklGtJXHB/2dsb2JhbABagwfAYoEAFnSCHwEBAQMBHR0xDgULAgEIGAoUEDIlAgQOBQiHfgaucI8qjVyBDwIxB4J0YQOocYMPgXI1
X-IronPort-AV: E=Sophos;i="4.87,671,1363132800"; d="scan'208";a="210378056"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 14 May 2013 16:55:07 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4EGt70M020041 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 May 2013 16:55:07 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.192]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Tue, 14 May 2013 11:55:06 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFU1ZTEkO7rgUObu6/YBqERNZkFPpuAgAArdgD//+RPAA==
Date: Tue, 14 May 2013 16:55:06 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <977708E0A9BBD948B46EA7FF1B31584F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Tue, 14 May 2013 16:55:43 -0000

inline

On May 14, 2013, at 10:34 AM, Ted Lemon <Ted.Lemon@nominum.com>
 wrote:

> On May 14, 2013, at 9:58 AM, "Cullen Jennings (fluffy)" <fluffy@cisco.com=
> wrote:
>> 2) On the point of what the IESG should be doing, I would like to see th=
e whole IESG say they agree with the Discuss Criteria document and will sta=
y within that (or change it if they disagree). The cross area review teams =
might want to also provide comments within this context.=20
>=20
> I am not entirely convinced that the DISCUSS criteria are complete. =20

agree but I like and think they help even thought they are not complete=20

>  There are some rules in the criteria that are intended to curb abuse, an=
d that I think do have that effect, but that also would make some very appr=
opriate DISCUSSes fail to meet the criteria. =20

If you could give some examples of DISCUSSes that you think are reasonable =
but fail to meet the criteria, it would be really great if you could provid=
e some examples of that as I think it would help refine DISCUSS criteria. I=
 think everyone agrees there could be things in that category but - that wa=
s part of the reason DISCUSS criteria did not end up as a BCP.=20

>  I don't really know how to address that problem.  =20

The IESG needs to keep using common sense and keep doing the right thing. I=
'm happy that the IESG deal with the unexpected.

> E.g. the rule about not coming up with new DISCUSSes: if a DISCUSS winds =
opening up a can of worms, it ought to be possible to enlarge the DISCUSS, =
but I think that the rule about not adding new DISCUSSes after the first DI=
SCUSS tends to forbid that, and the reason given is a good one.   Having sa=
id that, I don't think the right answer is to ignore that requirement.  I d=
on't actually have a good answer.

I think the IESG has generally followed a good path of not adding new thing=
s, and at the same time if some huge problem was found later, still dealing=
 with it. A long time ago it was hard to know when the IESG might actually =
finish review, that is not longer a problem but I don't want to go back to =
it being a problem.=20

>=20
> It's worth noting that ADs are not omniscient, and hence the DISCUSS crit=
eria apply to what the AD entering the DISCUSS _knows_, not to the full sta=
te of all knowledge in the world. =20

Of course and that is part of why the name DISCUSS. The AD wants to DISCUSS=
 it with people and improve their knowledge of state of work and what happe=
ned in WG and why it is the way it is and resolve it. I'm perfectly happy w=
ith DISCUSSes being resolved with "once it got explained to me, I see it is=
 not a problem and cleared".=20

>  If someone other than the AD has knowledge that they think means that th=
e DISCUSS doesn't meet the criteria, that doesn't mean the DISCUSS doesn't =
mean the criteria.   In this case, the critic needs to communicate it to th=
e AD, who may or may not agree with the critic's point of view.   This is n=
ot to say that it's never correct to say "this doesn't meet the DISCUSS cri=
teria."   But the reason given should be that it would be obvious to anyone=
 reading the DISCUSS that it didn't meet the criteria.  =20

Sure but as everyone knowledge increases, I'd expect that AD would update t=
he DISCUSS or remove it if it becomes clear it is not longer relevant. My e=
xperience has been IESG does do this. =20

> The critic's expert knowledge can't be given as a reason.
>=20
> I have also noticed that some authors have the impression that a DISCUSS =
means the AD doesn't like the document, or doesn't want the document to adv=
ance, or is a non-negotiable pronouncement from on high that the authors sh=
ould not question.   This is certainly not my motivation when I enter a DIS=
CUSS.   I'm just some guy who got nominated by the nomcom.   Hopefully I'm =
qualified, but I don't claim to be right.   I have seen DISCUSSes I've rais=
ed improve documents, and I've seen DISCUSSes I've raised turn out not to r=
equire any change, but just some discussion to clear up a misunderstanding =
on my part.  I very much hope that in the latter case, the author will argu=
e back, and not just make a change to shut me up!

+1 to that.=20

>=20
> The reason I raise a DISCUSS rather than a comment is that at the time I'=
m writing the DISCUSS, it appears _to me_ to be the case that there is a pr=
oblem that ought to be addressed before the document is published.   I may =
think it's generally a great document, but I want the concern I've raised t=
o be addressed before it moves forward.   That is _all_ a DISCUSS from me m=
eans.   If I think the document is an irretrievably bad idea, I will abstai=
n, and say why I think so.
>=20

Again, +1 to that and my experience is most the IESG feels the same way.=20

Thanks for sending your email. I think it help people understand how ADs th=
ink about DISCUSSes.





From dhc@dcrocker.net  Tue May 14 10:19:14 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6498C21F8AA6 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 10:19:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5
X-Spam-Level: 
X-Spam-Status: No, score=-5 tagged_above=-999 required=5 tests=[AWL=1.600, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B4tqT6yxRVHR for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 10:19:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A472E21F89FF for <ietf@ietf.org>; Tue, 14 May 2013 10:19:04 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4EHIxKB032697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 10:19:02 -0700
Message-ID: <519271F5.4020202@dcrocker.net>
Date: Tue, 14 May 2013 10:18:45 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 14 May 2013 10:19:02 -0700 (PDT)
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 17:19:14 -0000

On 5/14/2013 6:58 AM, Cullen Jennings (fluffy) wrote:
>    when you look at the
> changes that are made to drafts from point they go in, to point they
> come out of IESG it seems to be a rare example where people don't
> agree that major changes were an improvement and needed.

This is an important assertion; probably fundamental.  Hence it needs 
some sort of objective substantiation.


> 2) On the point of what the IESG should be doing, I would like to see
> the whole IESG say they agree with the Discuss Criteria document and
> will stay within that (or change it if they disagree).

+1

And a Discuss should be required to assert which criteria apply and how.

FWIW, I assume the formal list will need to change; this means that 
there will be times when it is incomplete.  Hence any specific AD 
concern might not fit into the existing list. So I think it's important 
for that to be ok, as long as the AD justifies the exception carefully 
and thoroughly.


>  The cross area
> review teams might want to also provide comments within this
> context.

Interesting idea.  Reviews don't carry the force of law, as a Discuss 
does, but the discipline of distinguishing specific discuss criteria 
from other comments in a review could be helpful.



d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stephen.farrell@cs.tcd.ie  Tue May 14 10:43:13 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B9F21F8E4E for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 10:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kx-cUZ6qmdEs for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 10:42:59 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2E721F847B for <ietf@ietf.org>; Tue, 14 May 2013 10:42:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C2AEABEA0; Tue, 14 May 2013 18:41:38 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FKItt4310B4j; Tue, 14 May 2013 18:41:34 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.44.76.96]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0BE26BE88; Tue, 14 May 2013 18:41:34 +0100 (IST)
Message-ID: <51927748.3000702@cs.tcd.ie>
Date: Tue, 14 May 2013 18:41:28 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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: Tue, 14 May 2013 17:43:21 -0000

Hi Cullen,

On 05/14/2013 02:58 PM, Cullen Jennings (fluffy) wrote:
> I would like to see the whole IESG say they agree with the Discuss Criteria document and will stay within that (or change it if they disagree). 

That I'm pretty sure is the case. When I started as a new AD
one of the first things I did was put on stupid discuss that
didn't meet the discuss criteria, at which I was very quickly,
but nicely, pointed, (thanks Robert:-), so I learned that
lesson early.

I've seen it happen a fair few times since, with new and not
so new ADs - the IESG as a whole do beat one another up with
the discuss criteria, and not that infrequently. (There was
mail making exactly this point today for example.)

If it helps, I personally think the discuss-criteria are very
good, and work well and I do my best to follow 'em. (Though
since most of my discusses are security related that's maybe
easier for me than for ADs in other areas.)

> The cross area review teams might want to also provide comments within this context.

No harm. But all cross-area reviews are explicitly adopted by
an AD before becoming discuss points. And the IESG also beat
one another up if an AD posts a discuss that only says "see review
foo" without saying more, so all discusses are the AD's and need
to be argued by that AD. Again, it doesn't happen every week
that we beat up an AD for that, but maybe a few times a year.

On 05/14/2013 05:34 PM, Ted Lemon wrote:
> the rule about not coming up with new DISCUSSes:

I've not found that a real problem. When its happened that we
did turn up something bigger than we thought after the telechat
(and updating your discuss points before or during the telechat
is considered fair game) then I think the authors/chairs have
always also agreed that stuff needed to be done.

Cheers,
S.



From farmer@umn.edu  Tue May 14 11:04:55 2013
Return-Path: <farmer@umn.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 9879621F87B1 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 11:04:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GorArzeeNaSE for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 11:04:28 -0700 (PDT)
Received: from vs-m.tc.umn.edu (vs-m.tc.umn.edu [134.84.135.97]) by ietfa.amsl.com (Postfix) with ESMTP id 87C2121F8470 for <ietf@ietf.org>; Tue, 14 May 2013 11:03:43 -0700 (PDT)
Received: from mail-ie0-f171.google.com (mail-ie0-f171.google.com [209.85.223.171]) by vs-m.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Tue, 14 May 2013 13:02:52 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f171.google.com [209.85.223.171] #+LO+TR
X-Umn-Classification: local
Received: by mail-ie0-f171.google.com with SMTP id e11so1723917iej.2 for <ietf@ietf.org>; Tue, 14 May 2013 11:02:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding:x-gm-message-state; bh=XkZJleHdekiifgTGgGPHbPj9oaUlKyjcQprqtjCOsU0=; b=A8MNM0csMR/WGSTzl4+aER1ga6jzSQlDBUY0JHzh2nLWrrs3OTe33BJghS7O61kuNc U3HSVPqcLRN6mUpTcF9Dz4Fk0bEuaUWCFs+HtbVHtamJ2CvUkPt3/LvPXbUKAm2EJbPv 3ySzPuHsESQeXfyTHmT/sBDlC36Pq4AmACdah8n/B13otJ4a8JsPrIztr8O8f8lhI7ip MpnqTf0a+VFxuOD9oKOLjeXgfIGv7D1iV8GDnpkaaeNheZvnKjNAGaFOhKSufz0uRNWe qDWhjlzxLWgZkFFgSYCWDIN/oxoNoYExh/nwb1Kx8FAZkD8skzj9heVzHTiN4V5j3jLS Zg3w==
X-Received: by 10.50.134.196 with SMTP id pm4mr2862664igb.93.1368554571857; Tue, 14 May 2013 11:02:51 -0700 (PDT)
X-Received: by 10.50.134.196 with SMTP id pm4mr2862653igb.93.1368554571771; Tue, 14 May 2013 11:02:51 -0700 (PDT)
Received: from x-128-101-233-101.uofm-secure.wireless.umn.edu ([2607:ea00:104:2000:b51d:883:23c3:34d7]) by mx.google.com with ESMTPSA id o10sm26708910igh.2.2013.05.14.11.02.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 May 2013 11:02:50 -0700 (PDT)
Message-ID: <51927C4B.6090400@umn.edu>
Date: Tue, 14 May 2013 13:02:51 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net>
In-Reply-To: <6.2.5.6.2.20130510231552.0df99d90@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQkE+7TJK8xwuI+667OmvVq+HOjLDBTrl/Q0A1RWZWjnmoYZmtA73mEfOTiTqxPFpdAwGZX8FYQJ0ADx/zmr1l6C5LtVo8wi0bFzPHGYjWebcbOGOLv4PYQgIyeKc8dbkGxr3o1E
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 18:05:01 -0000

On 5/11/13 10:17 , SM wrote:
> At 18:36 10-05-2013, David Conrad wrote:
...
>> > Is it up to the IETF to set up a one-stop shop for personal data
>> requests?
>>
>> I suspect not, but I suspect it isn't up to the IETF to dictate global
>> privacy policy either.
>
> Section 2 is about the goals for distributing number resources (re.
> first sentence).  I suggest removing the third goal as it might be a
> matter of global (or other) policy.  It also makes privacy a non-issue
> as there isn't any relationship between it and the goals.
...

The third goal you refer to focuses on the need for "accurate 
registration information ... in order to meet a variety of operational 
requirements."  I believe this to be a valid technical concerns of the 
IETF, it is difficult to imagine how a global Internet can technically 
function without this.  So, I think it is important for it to remain in 
the draft.

However, issues of privacy, law enforcement access, and a myriad of 
other extremely important issues related to the Internet Numbers 
Registry System are outside the technical and operational scope of the 
IETF.  The whole point of the draft is to document the issues that are 
properly the concern of the IETF towards the Internet Numbers Registry 
System and to pass the rest of it to the multi-stakeholder environment 
of ICANN and the RIRs to hash it out.



-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

From drc@virtualized.org  Tue May 14 11:32:45 2013
Return-Path: <drc@virtualized.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 B0C6B11E80F8 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 11:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-wXinHNVvms for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 11:32:39 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id 177E521F8F69 for <ietf@ietf.org>; Tue, 14 May 2013 11:32:38 -0700 (PDT)
Received: from [10.0.1.4] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 076FA170B7; Tue, 14 May 2013 18:32:36 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <51927C4B.6090400@umn.edu>
Date: Tue, 14 May 2013 11:32:35 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1503)
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: Tue, 14 May 2013 18:32:45 -0000

Hi,

On May 14, 2013, at 11:02 AM, David Farmer <farmer@umn.edu> wrote:
> The third goal you refer to focuses on the need for "accurate =
registration information ... in order to meet a variety of operational =
requirements."  I believe this to be a valid technical concerns of the =
IETF, it is difficult to imagine how a global Internet can technically =
function without this.  So, I think it is important for it to remain in =
the draft.

I would also point out that the third goal makes no statement on whether =
the registration data is publicly available or not.

> However, issues of privacy, law enforcement access, and a myriad of =
other extremely important issues related to the Internet Numbers =
Registry System are outside the technical and operational scope of the =
IETF.  The whole point of the draft is to document the issues that are =
properly the concern of the IETF towards the Internet Numbers Registry =
System and to pass the rest of it to the multi-stakeholder environment =
of ICANN and the RIRs to hash it out.

Exactly. Section 4 notes that provision of "public WHOIS" has been a =
technical consideration and that "it may be necessary for the Internet =
community to examine these and related technical and operational =
considerations and how best to meet them."

Regards,
-drc


From brian.e.carpenter@gmail.com  Tue May 14 13:10:16 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F0B21F8630 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:10:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uzcULzNINDrB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:10:13 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0698321F8532 for <ietf@ietf.org>; Tue, 14 May 2013 13:10:10 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id s9so2014013iec.34 for <ietf@ietf.org>; Tue, 14 May 2013 13:10:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FLXzYpOwmPi302a5UbPDIfJ3YwM7dtLGMGruh2WvBSA=; b=UZLpoIjlT8EKtGyWsfWPxKWuqwup2T8SOIAZt9a5EmQR3Ham/3dHW5rRaweZ5+iOZp AUYtx+sH41/0sTm1j92dq16ElyOF9w9NgECpdqUAc9WOcNU7w0xVknIfi43+KNMKKS8i 4Fai1PjmdjlX3+yQrN6PFLepsjUdMqWr7NQfaLvzMrAyBcRu5124rs+HGQeu6ZgRsQ9L XfbJluv3N1d1yWTJjfqBn7PGvp2X+nhm9J/KowlBK+pHAyA/1aF7QWZ8XBQMYS+gjYQi izyBJib2WVqJH7AbMc8x5IofXG1l1YiHsAf8ONcArlJ69zaAtV/FHa5++qRuBuiPuRx/ 2mZg==
X-Received: by 10.50.127.242 with SMTP id nj18mr3337890igb.47.1368562210115; Tue, 14 May 2013 13:10:10 -0700 (PDT)
Received: from [192.168.1.64] (122-60-170-151.jetstream.xtra.co.nz. [122.60.170.151]) by mx.google.com with ESMTPSA id o10sm27357152igh.2.2013.05.14.13.10.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 May 2013 13:10:08 -0700 (PDT)
Message-ID: <51929A21.8030105@gmail.com>
Date: Wed, 15 May 2013 08:10:09 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com>
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: Tue, 14 May 2013 20:10:16 -0000

I think this exchange between Cullen and Ted says it all, except
for one tweak: the IESG is allowed, even encouraged, to apply common
sense when considering the DISCUSS criteria. They are guidance,
not rules.

Also, everybody needs to take the word "discuss" literally. An
entirely possible outcome is that after discussion, the AD says
"Oh. You're correct. Pretend I never spoke!". Or the author says
"Oh. You're correct. We'll change it." Either outcome is good.

Regards
   Brian

On 15/05/2013 04:55, Cullen Jennings (fluffy) wrote:
> inline
> 
> On May 14, 2013, at 10:34 AM, Ted Lemon <Ted.Lemon@nominum.com>
>  wrote:
> 
>> On May 14, 2013, at 9:58 AM, "Cullen Jennings (fluffy)" <fluffy@cisco.com> wrote:
>>> 2) On the point of what the IESG should be doing, I would like to see the whole IESG say they agree with the Discuss Criteria document and will stay within that (or change it if they disagree). The cross area review teams might want to also provide comments within this context. 
>> I am not entirely convinced that the DISCUSS criteria are complete.  
> 
> agree but I like and think they help even thought they are not complete 
> 
>>  There are some rules in the criteria that are intended to curb abuse, and that I think do have that effect, but that also would make some very appropriate DISCUSSes fail to meet the criteria.  
> 
> If you could give some examples of DISCUSSes that you think are reasonable but fail to meet the criteria, it would be really great if you could provide some examples of that as I think it would help refine DISCUSS criteria. I think everyone agrees there could be things in that category but - that was part of the reason DISCUSS criteria did not end up as a BCP. 
> 
>>  I don't really know how to address that problem.   
> 
> The IESG needs to keep using common sense and keep doing the right thing. I'm happy that the IESG deal with the unexpected.
> 
>> E.g. the rule about not coming up with new DISCUSSes: if a DISCUSS winds opening up a can of worms, it ought to be possible to enlarge the DISCUSS, but I think that the rule about not adding new DISCUSSes after the first DISCUSS tends to forbid that, and the reason given is a good one.   Having said that, I don't think the right answer is to ignore that requirement.  I don't actually have a good answer.
> 
> I think the IESG has generally followed a good path of not adding new things, and at the same time if some huge problem was found later, still dealing with it. A long time ago it was hard to know when the IESG might actually finish review, that is not longer a problem but I don't want to go back to it being a problem. 
> 
>> It's worth noting that ADs are not omniscient, and hence the DISCUSS criteria apply to what the AD entering the DISCUSS _knows_, not to the full state of all knowledge in the world.  
> 
> Of course and that is part of why the name DISCUSS. The AD wants to DISCUSS it with people and improve their knowledge of state of work and what happened in WG and why it is the way it is and resolve it. I'm perfectly happy with DISCUSSes being resolved with "once it got explained to me, I see it is not a problem and cleared". 
> 
>>  If someone other than the AD has knowledge that they think means that the DISCUSS doesn't meet the criteria, that doesn't mean the DISCUSS doesn't mean the criteria.   In this case, the critic needs to communicate it to the AD, who may or may not agree with the critic's point of view.   This is not to say that it's never correct to say "this doesn't meet the DISCUSS criteria."   But the reason given should be that it would be obvious to anyone reading the DISCUSS that it didn't meet the criteria.   
> 
> Sure but as everyone knowledge increases, I'd expect that AD would update the DISCUSS or remove it if it becomes clear it is not longer relevant. My experience has been IESG does do this.  
> 
>> The critic's expert knowledge can't be given as a reason.
>>
>> I have also noticed that some authors have the impression that a DISCUSS means the AD doesn't like the document, or doesn't want the document to advance, or is a non-negotiable pronouncement from on high that the authors should not question.   This is certainly not my motivation when I enter a DISCUSS.   I'm just some guy who got nominated by the nomcom.   Hopefully I'm qualified, but I don't claim to be right.   I have seen DISCUSSes I've raised improve documents, and I've seen DISCUSSes I've raised turn out not to require any change, but just some discussion to clear up a misunderstanding on my part.  I very much hope that in the latter case, the author will argue back, and not just make a change to shut me up!
> 
> +1 to that. 
> 
>> The reason I raise a DISCUSS rather than a comment is that at the time I'm writing the DISCUSS, it appears _to me_ to be the case that there is a problem that ought to be addressed before the document is published.   I may think it's generally a great document, but I want the concern I've raised to be addressed before it moves forward.   That is _all_ a DISCUSS from me means.   If I think the document is an irretrievably bad idea, I will abstain, and say why I think so.
>>
> 
> Again, +1 to that and my experience is most the IESG feels the same way. 
> 
> Thanks for sending your email. I think it help people understand how ADs think about DISCUSSes.
> 
> 
> 
> 
> 

From worley@shell01.TheWorld.com  Tue May 14 13:38:05 2013
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 7A0E321F9049 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYs3g2gLfOg9 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:37:59 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD9021F90B3 for <ietf@ietf.org>; Tue, 14 May 2013 13:37:59 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r4EKbCwU013176; Tue, 14 May 2013 16:37:14 -0400
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 r4EKbBE54763726; Tue, 14 May 2013 16:37:11 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r4EKbBUU4764257; Tue, 14 May 2013 16:37:11 -0400 (EDT)
Date: Tue, 14 May 2013 16:37:11 -0400 (EDT)
Message-Id: <201305142037.r4EKbBUU4764257@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Jari Arkko <jari.arkko@piuha.net>
In-reply-to: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> (jari.arkko@piuha.net)
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.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: Tue, 14 May 2013 20:38:05 -0000

> From: Jari Arkko <jari.arkko@piuha.net>
> 
> Just FYI that I wrote another article, this time on "permissionless
> innovation" and the role of open standards.

A nice summary!

    No permit had to be applied [for], no new network had to be built,
    and no commercial negotiation with other parties was needed when
    Facebook started, for instance.

And one consequence is, "No incumbent could value-price its services
so as to extract the added value created by Facebook."  But I don't
think that would be very popular at the ITU!

The critical difference is that the IETF is an organization of
*buyers* rather than an organization of *sellers*.

Dale

From touch@isi.edu  Tue May 14 13:47:00 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5CC221F90EB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.216
X-Spam-Level: 
X-Spam-Status: No, score=-105.216 tagged_above=-999 required=5 tests=[AWL=1.383, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HPDm3orSfTNL for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:46:55 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id ED1DA21F8F6E for <ietf@ietf.org>; Tue, 14 May 2013 13:46:54 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4EKkLGc008627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 13:46:21 -0700 (PDT)
Message-ID: <5192A282.7060409@isi.edu>
Date: Tue, 14 May 2013 13:45:54 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com>
In-Reply-To: <51929A21.8030105@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 20:47:00 -0000

Brian, et al.,

On 5/14/2013 1:10 PM, Brian E Carpenter wrote:
> I think this exchange between Cullen and Ted says it all, except
> for one tweak: the IESG is allowed, even encouraged, to apply common
> sense when considering the DISCUSS criteria. They are guidance,
> not rules.
>
> Also, everybody needs to take the word "discuss" literally. An
> entirely possible outcome is that after discussion, the AD says
> "Oh. You're correct. Pretend I never spoke!". Or the author says
> "Oh. You're correct. We'll change it." Either outcome is good.

The trouble with this assumption is the IESG review process.

COMMENTS are appropriate for feedback, but the IESG review process is 
too often considered an *opportunity* for the IESG to "make the document 
better", or (in some case) have an opportunity for their input.

As important as the DISCUSS criteria are, there are NON-DISCUSS criteria 
that ought to be more carefully followed - including the point that 
disagreements with the WG or clarifications are not justification for 
DISCUSS.

Ted pointed out that DISCUSS doesn't mean the IESG doesn't like a 
document - agreed, but it *does* hold up a document until the IESG 
member clears it.

That can - has - and is - being used as leverage to force changes to 
documents that are sometimes clearly out of scope (e.g., listed as 
NON-DISCUSS).

DISCUSS is a heavyweight mechanism that holds up document resolution; it 
should be used only where absolutely appropriate. If the IESG wants to 
have a "discussion" with the authors, they are welcome to participate in 
the WGs or IETF LC, or to contact them out of band.

Joe

From touch@isi.edu  Tue May 14 13:47:36 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B00F21F918C for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.413
X-Spam-Level: 
X-Spam-Status: No, score=-105.413 tagged_above=-999 required=5 tests=[AWL=1.186, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FUAfgWDFFY9H for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 13:47:30 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6C10E21F910D for <ietf@ietf.org>; Tue, 14 May 2013 13:47:30 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4EKklIf008697 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 13:46:47 -0700 (PDT)
Message-ID: <5192A29D.9070205@isi.edu>
Date: Tue, 14 May 2013 13:46:21 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <519271F5.4020202@dcrocker.net>
In-Reply-To: <519271F5.4020202@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 20:47:36 -0000

On 5/14/2013 10:18 AM, Dave Crocker wrote:
> And a Discuss should be required to assert which criteria apply and how.

+1

Joe

From stephen.farrell@cs.tcd.ie  Tue May 14 14:00:09 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5472521F8FEB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLhngf0Hip4t for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:00:04 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7C5DE21F8FED for <ietf@ietf.org>; Tue, 14 May 2013 14:00:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 400D6BE76; Tue, 14 May 2013 21:59:41 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HuVSF9rZWRM9; Tue, 14 May 2013 21:59:40 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.44.76.96]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D558BBE74; Tue, 14 May 2013 21:59:39 +0100 (IST)
Message-ID: <5192A5B6.3000205@cs.tcd.ie>
Date: Tue, 14 May 2013 21:59:34 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu>
In-Reply-To: <5192A282.7060409@isi.edu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 21:00:09 -0000

Joe,

On 05/14/2013 09:45 PM, Joe Touch wrote:
> As important as the DISCUSS criteria are, there are NON-DISCUSS criteria
> that ought to be more carefully followed - including the point that
> disagreements with the WG or clarifications are not justification for
> DISCUSS.

I had assumed that the term discuss-criteria meant [1] which includes
both. Not sure if that's also what you meant but worth adding the URL
here just in case some folks aren't familiar with it.

   [1] https://www.ietf.org/iesg/statement/discuss-criteria.html

> DISCUSS is a heavyweight mechanism that holds up document resolution; 

Agreed. But its a keystone in the current process. So getting
rid of it would be fairly revolutionary. (Not that I'm against
a bit of revolving now and then:-)

> it
> should be used only where absolutely appropriate. 

s/absolutely appropriate/appropriate/ would be better.

> If the IESG wants to
> have a "discussion" with the authors, they are welcome to participate in
> the WGs or IETF LC, or to contact them out of band.

With our current tail-heavy process, and ~100 WGs that's impossible
in almost all cases.

On 05/14/2013 09:46 PM, Joe Touch wrote:>
> On 5/14/2013 10:18 AM, Dave Crocker wrote:
>> And a Discuss should be required to assert which criteria apply and how.
>
> +1

That'd be -1 from me fwiw. There aren't enough disputes about that
to make it worthwhile and as I said the IESG is, believe it or not,
pretty good at policing itself in this respect.

S.


From touch@isi.edu  Tue May 14 14:14:26 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68FCD21F9180 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.562
X-Spam-Level: 
X-Spam-Status: No, score=-103.562 tagged_above=-999 required=5 tests=[AWL=-0.962, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJ-MNlYk+71k for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:14:21 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id ABC1221F92A5 for <ietf@ietf.org>; Tue, 14 May 2013 14:14:20 -0700 (PDT)
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 r4ELDPZf008421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 14:13:26 -0700 (PDT)
Message-ID: <5192A8DB.7030207@isi.edu>
Date: Tue, 14 May 2013 14:12:59 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie>
In-Reply-To: <5192A5B6.3000205@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 21:14:26 -0000

On 5/14/2013 1:59 PM, Stephen Farrell wrote:
>
> Joe,
>
> On 05/14/2013 09:45 PM, Joe Touch wrote:
>> As important as the DISCUSS criteria are, there are NON-DISCUSS criteria
>> that ought to be more carefully followed - including the point that
>> disagreements with the WG or clarifications are not justification for
>> DISCUSS.
>
> I had assumed that the term discuss-criteria meant [1] which includes
> both. Not sure if that's also what you meant but worth adding the URL
> here just in case some folks aren't familiar with it.
>
>     [1] https://www.ietf.org/iesg/statement/discuss-criteria.html
>
>> DISCUSS is a heavyweight mechanism that holds up document resolution;
>
> Agreed. But its a keystone in the current process. So getting
> rid of it would be fairly revolutionary. (Not that I'm against
> a bit of revolving now and then:-)

I am *not* suggesting getting rid of it.

I *am* suggesting that it needs to be used only where necessary, and 
that 'necessary' ought to be clearly proved by:

	- citing the specific DISCUSS criteria involved

	- providing explicit information on what would
	be required to clear the DISCUSS

>> it
>> should be used only where absolutely appropriate.
>
> s/absolutely appropriate/appropriate/ would be better.
>
>> If the IESG wants to
>> have a "discussion" with the authors, they are welcome to participate in
>> the WGs or IETF LC, or to contact them out of band.
>
> With our current tail-heavy process, and ~100 WGs that's impossible
> in almost all cases.

The NON-DISCUSS criteria imply that DISCUSS is not an opportunity for 
late input. I appreciate that early input isn't practical, but that does 
NOT provide a rationale for violating the NON-DISCUSS criteria 
(technical disagreement with the WG, etc. - see the list).

The IESG can offer its advice in COMMENTS in other positions. It can 
make suggestions, and let the authors and ADs decide what to do.

But it should NEVER hold a document hostage with a DISCUSS without 
specific merit.

Since some of you asked, here's a *current* example:

------

Ted Lemon issued a DISCUSS on a doc I have pending - here's the link:

http://datatracker.ietf.org/doc/draft-ietf-tcpm-experimental-options/ballot/

Note that his DISCUSS raises the point that 32-bit ExIDs "don't add 
value" and are "pointless" (despite having several paragraphs of 
justification in the doc). That's second-guessing the WG, which is 
listed among the explicit NON-DISCUSS criteria.

There's no clear no collateral damage to the Internet, just damage to 
those who might use a longer TCP option, and there are implementations 
that already use this (as well as other TCP options that are much less 
frugal in their use of option space). It affects only shared use of 
experimental option codepoints, a situation that's intended to be 
transient if an option becomes widely used. The choice of 32-bit ExIDs 
has pros and cons listed in the doc, and both 16-bit and 32-bit ExIDs 
are allowed.

Right now, he's waiting for the doc to be changed to recommend 16-bit 
ExIDs. I don't disagree with that suggestion, but is it really 
appropriate to hold a document hostage using a DISCUSS this way?

I don't think so.

I questioned this process, and he suggested that debating the validity 
of a DISCUSS was out of scope during IESG review. That's not acceptable 
to me, and I hope to others.

Joe

From ajs@anvilwalrusden.com  Tue May 14 14:32:34 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9D8021F912C for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:32:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kENPMVnkSeQa for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:32:29 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA9321F90EA for <ietf@ietf.org>; Tue, 14 May 2013 14:32:28 -0700 (PDT)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 33F6A8A031 for <ietf@ietf.org>; Tue, 14 May 2013 21:32:27 +0000 (UTC)
Date: Tue, 14 May 2013 17:32:25 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: article on innovation and open standards
Message-ID: <20130514213225.GD17491@mx1.yitter.info>
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201305142037.r4EKbBUU4764257@shell01.TheWorld.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 21:32:34 -0000

On Tue, May 14, 2013 at 04:37:11PM -0400, Dale R. Worley wrote:

> The critical difference is that the IETF is an organization of
> *buyers* rather than an organization of *sellers*.

Without wishing to be nasty, I will point out that we have way more
vendors than operators participating in our standards development.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Ted.Lemon@nominum.com  Tue May 14 14:39:41 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C70BD21F91B7 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.537
X-Spam-Level: 
X-Spam-Status: No, score=-106.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aW4p8CHSF0yb for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 14:39:35 -0700 (PDT)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7CB21F90FC for <ietf@ietf.org>; Tue, 14 May 2013 14:39:34 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUZKvFQRv8ivOWJ5us5eboGIDw55dKsc4@postini.com; Tue, 14 May 2013 14:39:34 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B2F551B8163 for <ietf@ietf.org>; Tue, 14 May 2013 14:39:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id AA76F19005D; Tue, 14 May 2013 14:39:33 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 14 May 2013 14:39:27 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAA+QQCAAEJ9AA==
Date: Tue, 14 May 2013 21:39:26 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519A4A8@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <51927748.3000702@cs.tcd.ie>
In-Reply-To: <51927748.3000702@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E93908289DC0E64E8913C94937F45F91@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 21:39:42 -0000

On May 14, 2013, at 1:41 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wr=
ote:
> I've not found that a real problem. When its happened that we
> did turn up something bigger than we thought after the telechat
> (and updating your discuss points before or during the telechat
> is considered fair game) then I think the authors/chairs have
> always also agreed that stuff needed to be done.

Yup, I'm not convinced that it's a problem in practice.   I just happened t=
o notice that it could have become an issue the other day when discussing a=
 DISCUSS.


From jmh@joelhalpern.com  Tue May 14 15:01:16 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECBF721F8FEB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mtsp-zUlBQMH for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:01:08 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5D121F84DC for <ietf@ietf.org>; Tue, 14 May 2013 15:01:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 1CC131C080B; Tue, 14 May 2013 15:01:08 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-209.clppva.east.verizon.net [70.106.134.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E9A9B1C07F7; Tue, 14 May 2013 15:01:06 -0700 (PDT)
Message-ID: <5192B415.50006@joelhalpern.com>
Date: Tue, 14 May 2013 18:00:53 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu>
In-Reply-To: <5192A8DB.7030207@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 22:01:16 -0000

It seems to me that if it is really a discussion, then there may be many 
possible things which could resolve it, and the AD raising the question 
may not know exactly what is feasible to clear it.  Otherwise it is a 
demand, not a discussions.  And in my experience while ADs can be pushy 
(like the rest of us), they are generally prepared to have discussion.

Thus, I find your second item below to be inappropriate.

At the same time, discussions do have to be resolvable.  If there is no 
way to address it, then it is not a discuss.  But "required to clar" is 
the wrong picture as far as I can tell.

Yours,
Joel

On 5/14/2013 5:12 PM, Joe Touch wrote:
> I am *not* suggesting getting rid of it.
>
> I *am* suggesting that it needs to be used only where necessary, and
> that 'necessary' ought to be clearly proved by:
>
>      - citing the specific DISCUSS criteria involved
>
>      - providing explicit information on what would
>      be required to clear the DISCUSS

From touch@isi.edu  Tue May 14 15:05:17 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97BB321F854E for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:05:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.455
X-Spam-Level: 
X-Spam-Status: No, score=-103.455 tagged_above=-999 required=5 tests=[AWL=-0.856, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJSeuQkWZ4eZ for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:05:11 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id BEC9D21F850B for <ietf@ietf.org>; Tue, 14 May 2013 15:05:11 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4EM4Vsk007893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 15:04:31 -0700 (PDT)
Message-ID: <5192B4D5.90904@isi.edu>
Date: Tue, 14 May 2013 15:04:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com>
In-Reply-To: <5192B415.50006@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 22:05:17 -0000

On 5/14/2013 3:00 PM, Joel M. Halpern wrote:
> It seems to me that if it is really a discussion, then there may be many
> possible things which could resolve it, and the AD raising the question
> may not know exactly what is feasible to clear it.  Otherwise it is a
> demand, not a discussions.  And in my experience while ADs can be pushy
> (like the rest of us), they are generally prepared to have discussion.
>
> Thus, I find your second item below to be inappropriate.
>
> At the same time, discussions do have to be resolvable.  If there is no
> way to address it, then it is not a discuss.  But "required to clar" is
> the wrong picture as far as I can tell.

Point taken - at least some indication on what is expected to be changed 
toward a path of resolution.

As you note, otherwise it's not a DISCUSS.

Joe

>
> Yours,
> Joel
>
> On 5/14/2013 5:12 PM, Joe Touch wrote:
>> I am *not* suggesting getting rid of it.
>>
>> I *am* suggesting that it needs to be used only where necessary, and
>> that 'necessary' ought to be clearly proved by:
>>
>>      - citing the specific DISCUSS criteria involved
>>
>>      - providing explicit information on what would
>>      be required to clear the DISCUSS

From jmh@joelhalpern.com  Tue May 14 15:11:39 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B02B521F915B for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4kPcXjGE-eI for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:11:33 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id D4A5C21F8630 for <ietf@ietf.org>; Tue, 14 May 2013 15:11:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id BD03E1D25EF; Tue, 14 May 2013 15:11:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-209.clppva.east.verizon.net [70.106.134.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 8F4C61D24BC; Tue, 14 May 2013 15:11:29 -0700 (PDT)
Message-ID: <5192B681.7020501@joelhalpern.com>
Date: Tue, 14 May 2013 18:11:13 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <5192B4D5.90904@isi.edu>
In-Reply-To: <5192B4D5.90904@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 22:11:39 -0000

Below:

On 5/14/2013 6:04 PM, Joe Touch wrote:
>
>
> On 5/14/2013 3:00 PM, Joel M. Halpern wrote:
>> It seems to me that if it is really a discussion, then there may be many
>> possible things which could resolve it, and the AD raising the question
>> may not know exactly what is feasible to clear it.  Otherwise it is a
>> demand, not a discussions.  And in my experience while ADs can be pushy
>> (like the rest of us), they are generally prepared to have discussion.
>>
>> Thus, I find your second item below to be inappropriate.
>>
>> At the same time, discussions do have to be resolvable.  If there is no
>> way to address it, then it is not a discuss.  But "required to clar" is
>> the wrong picture as far as I can tell.
>
> Point taken - at least some indication on what is expected to be changed
> toward a path of resolution.
>
> As you note, otherwise it's not a DISCUSS.
>
> Joe
Thanks Joe.  I am glad we are on the same apage about the kind of 
clarity of description needed in discusses.  We may have different 
experiences, but the vast majority of the discusses I have dealt with 
have been sufficiently clear on the question of how to approach 
resolving them.  Sometimes an actual conversation with the AD has been 
necessary to understand the issue and reach a practical point for 
resolving it, but that is a communication style issue, not a discuss 
substance issue.

Yours,
Joel

>
>>
>> Yours,
>> Joel
>>
>> On 5/14/2013 5:12 PM, Joe Touch wrote:
>>> I am *not* suggesting getting rid of it.
>>>
>>> I *am* suggesting that it needs to be used only where necessary, and
>>> that 'necessary' ought to be clearly proved by:
>>>
>>>      - citing the specific DISCUSS criteria involved
>>>
>>>      - providing explicit information on what would
>>>      be required to clear the DISCUSS
>

From Ted.Lemon@nominum.com  Tue May 14 15:12:47 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D3121F924D for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.54
X-Spam-Level: 
X-Spam-Status: No, score=-107.54 tagged_above=-999 required=5 tests=[AWL=1.059, BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5-2DNFVX5LES for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:12:40 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3348B21F915B for <ietf@ietf.org>; Tue, 14 May 2013 15:12:40 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKUZK214xjFIYf1hs9ni/S5M0P7MTa1883@postini.com; Tue, 14 May 2013 15:12:40 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 8DA0A1B8163 for <ietf@ietf.org>; Tue, 14 May 2013 15:12:39 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8562519005D; Tue, 14 May 2013 15:12:39 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 14 May 2013 15:12:39 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgA==
Date: Tue, 14 May 2013 22:12:37 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com>
In-Reply-To: <5192B415.50006@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4F1FA4CB65A89C4FA7673A3F9BBE5F5E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 22:12:47 -0000

On May 14, 2013, at 6:00 PM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:
> At the same time, discussions do have to be resolvable.  If there is no w=
ay to address it, then it is not a discuss.  But "required to clar" is the =
wrong picture as far as I can tell.

Exactly right.   It would actually be pretty presumptuous for an AD to say =
what is required to clear the DISCUSS.   That would tend to imply that the =
DISCUSS is a directive, not an invitation to, well, discuss.   Of course we=
 have to _try_ to say what we think would clear the discuss, but I don't th=
ink we can go beyond that; it's virtually impossible for us to have complet=
e information.


From dhc@dcrocker.net  Tue May 14 15:31:14 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B84C821F9017 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:31:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.799
X-Spam-Level: 
X-Spam-Status: No, score=-6.799 tagged_above=-999 required=5 tests=[AWL=1.800,  BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Of6koAmzRzNl for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:31:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D2D7821F85C3 for <ietf@ietf.org>; Tue, 14 May 2013 15:31:09 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4EMV4Vj005968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 15:31:07 -0700
Message-ID: <5192BB1C.3000902@dcrocker.net>
Date: Tue, 14 May 2013 15:30:52 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 14 May 2013 15:31:07 -0700 (PDT)
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 22:31:14 -0000

On 5/14/2013 3:12 PM, Ted Lemon wrote:
> On May 14, 2013, at 6:00 PM, "Joel M. Halpern" <jmh@joelhalpern.com>
> wrote:
>> At the same time, discussions do have to be resolvable.  If there
>> is no way to address it, then it is not a discuss.  But "required
>> to clar" is the wrong picture as far as I can tell.
>
> Exactly right.   It would actually be pretty presumptuous for an AD
> to say what is required to clear the DISCUSS.   That would tend to
> imply that the DISCUSS is a directive, not an invitation to, well,
> discuss.

It isn't an 'invitation'.  It's an exercise in political authority by
blocking progress of the document.

We came up with the term "Discuss" when I was an AD because, at the
time, the IESG had little authority and wanted to encourage a
constructive tone; we didn't want to sound like we were saying 'no'.

And of course, that's still everyone's preference.  But the reality is
that the imposition of the Discuss is an assertion that changes are
being required.

For reference, that milder uses of Discuss, which is something akin to
"I'd like something clarified" does not require a Discuss.  It requires
a query to the working group and some dialogue.


   Of course we have to _try_ to say what we think would
> clear the discuss, but I don't think we can go beyond that; it's
> virtually impossible for us to have complete information.

That makes no sense.  The AD is the one choosing to block progress.  It
will be the AD who decides to clear the discuss.

How can it be reasonable for the AD to provide no basis for knowing what
it will take to get the AD to do this?

I suspect you are confusing 'what' with 'how'.  The issue is not one of
imposing the details of the engineering or documentation changes that
are being demanded by the AD, but of the criteria that will be applied
in evaluated the adequacy of the changes.  Othrwise, the authors have to
play a guessing game, trying to figure out what will please the AD well
enough to clear the Discuss.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From ajs@anvilwalrusden.com  Tue May 14 15:46:21 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3B921F90EE for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[AWL=-0.000,  BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lCzGTmvXDn5v for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 15:46:16 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id C758821F90C1 for <ietf@ietf.org>; Tue, 14 May 2013 15:46:12 -0700 (PDT)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E5FBE8A031 for <ietf@ietf.org>; Tue, 14 May 2013 22:46:06 +0000 (UTC)
Date: Tue, 14 May 2013 18:46:05 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <20130514224605.GI17491@mx1.yitter.info>
References: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5192BB1C.3000902@dcrocker.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 22:46:22 -0000

On Tue, May 14, 2013 at 03:30:52PM -0700, Dave Crocker wrote:
> 
> And of course, that's still everyone's preference.  But the reality is
> that the imposition of the Discuss is an assertion that changes are
> being required.
> 
> For reference, that milder uses of Discuss, which is something akin to
> "I'd like something clarified" does not require a Discuss.  It requires
> a query to the working group and some dialogue.

To be fair, for what it's worth as a WG chair I've had the latter
experience at least as often as the former in the use of DISCUSS, and
I've observed some DISCUSSes cleared without any change at all to the
document in question.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Ted.Lemon@nominum.com  Tue May 14 16:04:04 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD54A21F8E97 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 16:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.586
X-Spam-Level: 
X-Spam-Status: No, score=-106.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D85UTrDSxcsN for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 16:03:58 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id 1A04121F84DC for <ietf@ietf.org>; Tue, 14 May 2013 16:03:58 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUZLC3TwtHjRVZbDRBi1ctbebc5cHlEGY@postini.com; Tue, 14 May 2013 16:03:58 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 899321B816C for <ietf@ietf.org>; Tue, 14 May 2013 16:03:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 78F8519005D; Tue, 14 May 2013 16:03:57 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 14 May 2013 16:03:57 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, Dave Crocker <dhc@dcrocker.net>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgIAABRkAgAAJPQA=
Date: Tue, 14 May 2013 23:03:56 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net>
In-Reply-To: <5192BB1C.3000902@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C56DC816D432B74FBCD0F5AEF686A38E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, 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: Tue, 14 May 2013 23:04:04 -0000

On May 14, 2013, at 6:30 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> And of course, that's still everyone's preference.  But the reality is
> that the imposition of the Discuss is an assertion that changes are
> being required.

No, it absolutely is not.   That may have been the theory when you were AD,=
 but I can tell you from personal experience dealing with DISCUSSes on draf=
ts for which I am the responsible AD that that is not the theory now.

> For reference, that milder uses of Discuss, which is something akin to
> "I'd like something clarified" does not require a Discuss.  It requires
> a query to the working group and some dialogue.

One of the DISCUSS criteria requires that you not keep heaping on DISCUSSes=
, so it seems to me that escalating a No Objection to a DISCUSS would be wo=
rse, but perhaps you disagree?

> That makes no sense.  The AD is the one choosing to block progress.  It
> will be the AD who decides to clear the discuss.

I don't agree with your characterization here, but certainly it's true that=
 the AD has to clear the DISCUSS.

> How can it be reasonable for the AD to provide no basis for knowing what
> it will take to get the AD to do this?

It's not.   But that's not what Joe said.   What Joe said was that the AD s=
hould say _precisely_ what will clear the DISCUSS, and that is a very diffi=
cult thing to do with incomplete information.

> I suspect you are confusing 'what' with 'how'.  The issue is not one of
> imposing the details of the engineering or documentation changes that
> are being demanded by the AD, but of the criteria that will be applied
> in evaluated the adequacy of the changes.  Othrwise, the authors have to
> play a guessing game, trying to figure out what will please the AD well
> enough to clear the Discuss.

If the authors think that the goal is to "please the AD," something's wrong=
.  This would suggest that they will just do what the AD says without debat=
e, which is exactly the wrong thing.  The whole point of a DISCUSS is to ha=
ve a discussion.   Frankly, it's pretty disrespectful both to the AD and to=
 the working group if the authors make changes to "please the AD."


From doug.mtview@gmail.com  Tue May 14 16:04:44 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A26E21F901B; Tue, 14 May 2013 16:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJONNqoFCloU; Tue, 14 May 2013 16:04:43 -0700 (PDT)
Received: from mail-bk0-x234.google.com (mail-bk0-x234.google.com [IPv6:2a00:1450:4008:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4E621F8F0E; Tue, 14 May 2013 16:04:43 -0700 (PDT)
Received: by mail-bk0-f52.google.com with SMTP id mz1so656248bkb.39 for <multiple recipients>; Tue, 14 May 2013 16:04:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:x-priority :in-reply-to:date:cc:message-id:references:to:x-mailer; bh=RPfYpHKiS7gs/qEce1kLSCCpkXAbTfQ0/VWhAGw+VtU=; b=epAYStyM3zAwwKNjzPu8fm8CjkUpZkMYjF3BZVBS1+jkQw3t508ehPD3ChN7dVozZw kt9BpKNU1BNYk1k5sRXIr7NxjvObQPLr5Zgse/jHppdqtb+f1D1kQhNV6qpsRNrHONSF xbLcTCZ3XeXW6gbLO2cqQrbAbPmGba3D3WLj4mnuuth8wdy50+6yVeDenI8BCGl5lzmU pnPB6y2BoaiPkW/dPWfJt91zPv7qSHlxI05yu4Sh2S42kI/Pqp5dR2T4yMTo0bg1HRmd 0JJeWQVpL3qxGbDF6CHtZH4mFeV90wGkEd5A84pDpYsMk64n3aP4SzW9qaACLWaCeBEN 4+0A==
X-Received: by 10.205.105.8 with SMTP id do8mr9715499bkc.3.1368572682262; Tue, 14 May 2013 16:04:42 -0700 (PDT)
Received: from [192.168.1.194] (c-24-4-157-244.hsd1.ca.comcast.net. [24.4.157.244]) by mx.google.com with ESMTPSA id jm15sm67550bkb.13.2013.05.14.16.04.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 May 2013 16:04:41 -0700 (PDT)
Subject: Re: Review of: draft-otis-dkim-harmful
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: multipart/alternative; boundary="Apple-Mail=_F196C688-2EC6-4BC5-8F0A-16A01CEAC9A9"
From: Douglas Otis <doug.mtview@gmail.com>
X-Priority: 2 (High)
In-Reply-To: <51907325.7050600@dcrocker.net>
Date: Tue, 14 May 2013 16:04:37 -0700
Message-Id: <0D5E55AA-D05F-4E4F-838E-00D0EF6FB27F@gmail.com>
References: <51907325.7050600@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
Cc: "Murray S. Kucherawy" <msk@blackops.org>, Tony Hansen <tony@att.com>, IETF Discussion <ietf@ietf.org>, Douglas Otis <doug_otis@trendmicro.com>, iesg <iesg@ietf.org>, Dave Rand <dave_rand@trendmicro.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, 14 May 2013 23:04:44 -0000

--Apple-Mail=_F196C688-2EC6-4BC5-8F0A-16A01CEAC9A9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On May 12, 2013, at 9:59 PM, Dave Crocker <dhc@dcrocker.net> wrote:

Dear Dave,

Thank you for your thoughtful review, it was most helpful.  I have =
updated the draft in hopes of adding greater clarity and to address your =
concerns.=20
The new information not available to the WG at the time is how the DKIM =
specification would likely be implemented despite the precautions given, =
and the level of growing abuse being received.

http://tools.ietf.org/html/draft-otis-dkim-harmful-01

Best Regards,
Douglas Otis=

--Apple-Mail=_F196C688-2EC6-4BC5-8F0A-16A01CEAC9A9
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 12, 2013, at 9:59 PM, Dave Crocker &lt;<a href="mailto:dhc@dcrocker.net">dhc@dcrocker.net</a>&gt; wrote:</div><div><br></div><div>Dear Dave,</div><div><br></div><div>Thank you for your thoughtful review, it was most helpful. &nbsp;I have updated the draft in hopes of adding greater clarity and to address your concerns.&nbsp;</div><div>The new information not available to the WG at the time is how the DKIM specification would likely be implemented despite the precautions given, and the level of growing abuse being received.</div><div><br></div><div><a href="http://tools.ietf.org/html/draft-otis-dkim-harmful-01">http://tools.ietf.org/html/draft-otis-dkim-harmful-01</a></div><div><br></div><div>Best Regards,</div><div>Douglas Otis</div></div></body></html>
--Apple-Mail=_F196C688-2EC6-4BC5-8F0A-16A01CEAC9A9--

From dhc@dcrocker.net  Tue May 14 16:15:48 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BAAE21F8E4C for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 16:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.399
X-Spam-Level: 
X-Spam-Status: No, score=-6.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f0+K37rffT5J for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 16:15:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8327621F8532 for <ietf@ietf.org>; Tue, 14 May 2013 16:15:43 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4ENFdm8006813 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 14 May 2013 16:15:43 -0700
Message-ID: <5192C58F.5070304@dcrocker.net>
Date: Tue, 14 May 2013 16:15:27 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: call for ideas: tail-heavy IETF process
References: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <20130514224605.GI17491@mx1.yitter.info>
In-Reply-To: <20130514224605.GI17491@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 14 May 2013 16:15:43 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 23:15:48 -0000

On 5/14/2013 3:46 PM, Andrew Sullivan wrote:

> To be fair, for what it's worth as a WG chair I've had the latter
> experience at least as often as the former in the use of DISCUSS, and
> I've observed some DISCUSSes cleared without any change at all to the
> document in question.

We suffer a continuing logic error in the IETF.  We use "sometimes it
happens the other way" as if that negates the existence and problem
cause by what is being criticized.

So, yeah, of course a Discuss /sometimes/ causes a small delay with no
changes.  /Sometimes/ ADs use the sledgehammer of the Discuss to ask for
a bit of conversation.  That's all irrelevant.

What's relevant is the nature of the mechanisms, its capability, and the
cost it can and does impose on authors and the working group.

When a serious defect is identified, it's entirely worth the cost.

When it isn't, it isn't.

In all cases, the person imposing the cost has an obligation to
facilitate closing it, including making clear the criteria for closing
it.  It is unreasonable to have those who must do the work to clear it
play a guessing game.



> On 5/14/2013 4:03 PM, Ted Lemon wrote:> On May 14, 2013, at 6:30 PM,
> Dave Crocker <dhc@dcrocker.net> wrote:
>>> And of course, that's still everyone's preference.  But the
>>> reality is that the imposition of the Discuss is an assertion
>>> that changes are being required.
>>
>> No, it absolutely is not.   That may have been the theory when you
>> were AD, but I can tell you from personal experience dealing with
>> DISCUSSes on drafts for which I am the responsible AD that that is
>> not the theory now.

It's the practice now.  It's also often/typically the intent now.

      "'DISCUSS' is a blocking position; the document cannot proceed
until any issues are resolved to the satisfaction of the Area Director
who issued the DISCUSS."

This, of course, sounds very conversational (except for the blocking
part.)  And sometimes that's how it is used.  Sledgehammer to demand
polite conversation.  Talk with me, or else.

But look over the Discuss Criteria (Section 3.1) and at least half of
the bullets pertain to core technical or procedural failings.  These are
not matters of misunderstanding, resolved with some polite
conversations.  They require change.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jmh@joelhalpern.com  Tue May 14 16:58:12 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3765021F8F15 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 16:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id INO5fFxagNAh for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 16:58:04 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD6A21F8E99 for <ietf@ietf.org>; Tue, 14 May 2013 16:58:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id B775D1C07F7; Tue, 14 May 2013 16:58:02 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-209.clppva.east.verizon.net [70.106.134.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 79A711D25CE; Tue, 14 May 2013 16:58:01 -0700 (PDT)
Message-ID: <5192CF7C.6080108@joelhalpern.com>
Date: Tue, 14 May 2013 19:57:48 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: call for ideas: tail-heavy IETF process
References: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <20130514224605.GI17491@mx1.yitter.info> <5192C58F.5070304@dcrocker.net>
In-Reply-To: <5192C58F.5070304@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2013 23:58:13 -0000

And your bottom line is exactly what te rules say, what I said, what Ted 
said, and what Joe agreed is reasonable.  It also matchesthe practice I 
have seen.  Even the discuss that I had a lot of arguments with did 
include proposals for paths forward.  Sometimes they were ard to 
understand.  That's probably inevitable with all these opinionated 
humans doing this.

Yours,
Joel

On 5/14/2013 7:15 PM, Dave Crocker wrote:
> On 5/14/2013 3:46 PM, Andrew Sullivan wrote:
>
>> To be fair, for what it's worth as a WG chair I've had the latter
>> experience at least as often as the former in the use of DISCUSS, and
>> I've observed some DISCUSSes cleared without any change at all to the
>> document in question.
>
> We suffer a continuing logic error in the IETF.  We use "sometimes it
> happens the other way" as if that negates the existence and problem
> cause by what is being criticized.
>
> So, yeah, of course a Discuss /sometimes/ causes a small delay with no
> changes.  /Sometimes/ ADs use the sledgehammer of the Discuss to ask for
> a bit of conversation.  That's all irrelevant.
>
> What's relevant is the nature of the mechanisms, its capability, and the
> cost it can and does impose on authors and the working group.
>
> When a serious defect is identified, it's entirely worth the cost.
>
> When it isn't, it isn't.
>
> In all cases, the person imposing the cost has an obligation to
> facilitate closing it, including making clear the criteria for closing
> it.  It is unreasonable to have those who must do the work to clear it
> play a guessing game.
>

From touch@isi.edu  Tue May 14 17:29:16 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6693821F8E96 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 17:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.369
X-Spam-Level: 
X-Spam-Status: No, score=-105.369 tagged_above=-999 required=5 tests=[AWL=1.230, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kylau32RITs2 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 17:29:10 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3C021F8E99 for <ietf@ietf.org>; Tue, 14 May 2013 17:29:10 -0700 (PDT)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4F0RlVr020602 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 14 May 2013 17:27:47 -0700 (PDT)
Message-ID: <5192D684.2000104@isi.edu>
Date: Tue, 14 May 2013 17:27:48 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, 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, 15 May 2013 00:29:16 -0000

On 5/14/2013 4:03 PM, Ted Lemon wrote:
> If the authors think that the goal is to "please the AD," something's
> wrong.  This would suggest that they will just do what the AD says
> without debate, which is exactly the wrong thing.  The whole point of
> a DISCUSS is to have a discussion.   Frankly, it's pretty
> disrespectful both to the AD and to the working group if the authors
> make changes to "please the AD."

That is what happens exactly because the DISCUSS holds up the document, 
and most ADs don't want to burn time stalling their documents if there's 
a way around that delay.

If the suggestion is a suggestion, then change your DISCUSS to some 
other position, and issue the suggestion as a COMMENT. Yes, that's both 
general advice and specific to the case we have pending, Ted.

Joe

From Ted.Lemon@nominum.com  Tue May 14 17:53:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCF921F8E2C for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 17:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.587
X-Spam-Level: 
X-Spam-Status: No, score=-106.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N5gsHxMhpQaB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 17:53:18 -0700 (PDT)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id E039C21F8E04 for <ietf@ietf.org>; Tue, 14 May 2013 17:53:17 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUZLcfe5w7TIilEjehDQi83qrKq1vqk2n@postini.com; Tue, 14 May 2013 17:53:17 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 07C7F1B80DC for <ietf@ietf.org>; Tue, 14 May 2013 17:53:17 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F2A5D19005D; Tue, 14 May 2013 17:53:16 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Tue, 14 May 2013 17:53:16 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgIAABRkAgAAJPQCAABdvAIAABx4A
Date: Wed, 15 May 2013 00:53:16 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519BB55@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com> <5192D684.2000104@isi.edu>
In-Reply-To: <5192D684.2000104@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <740DEED5CD6B8F438C45ABDB53BAEF0B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 15 May 2013 00:53:24 -0000

On May 14, 2013, at 8:27 PM, Joe Touch <touch@isi.edu> wrote:
> That is what happens exactly because the DISCUSS holds up the document, a=
nd most ADs don't want to burn time stalling their documents if there's a w=
ay around that delay.

It can only happen if an author values getting their document through the p=
rocess more than getting it right, in which case one has to wonder why they=
 tried to publish the document in the first place.   (I assume you meant "a=
uthors," not "ADs" above).   The IESG processes documents quite quickly; I =
don't think it's valid to say that there is some terrifying stall in the do=
cument process as a result of the IESG, such that an author needs to chew o=
ff their leg to finally get the thing through.=

From hartmans@mit.edu  Tue May 14 19:42:15 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96B821F8AE2 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 19:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odh7dXPLUoQf for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 19:42:09 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id C904321F8AA8 for <ietf@ietf.org>; Tue, 14 May 2013 19:42:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 2F1B020556; Tue, 14 May 2013 22:39:26 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T71HZZixoF37; Tue, 14 May 2013 22:39:24 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 14 May 2013 22:39:24 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E37E8440A; Tue, 14 May 2013 22:42:04 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com> <5192D684.2000104@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519BB55@mbx-01.win.nominum.com>
Date: Tue, 14 May 2013 22:42:04 -0400
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519BB55@mbx-01.win.nominum.com> (Ted Lemon's message of "Wed, 15 May 2013 00:53:16 +0000")
Message-ID: <tslr4h9m0ar.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: 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, 15 May 2013 02:42:15 -0000

I'll say that about a year and a half ago I found myself pushing back on discusses
that in my opinion clearly were not within the discuss criteria
significantly more than I ever had to do as an AD. My role was as WG
chair/editor.

Interestingly it's been less of an issue in my experience lately.

Definitely not statistically significant data set for any of this.

From moore@network-heretics.com  Tue May 14 21:54:40 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E71021F86CE for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 21:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.599
X-Spam-Level: 
X-Spam-Status: No, score=-5.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2ln6fdP865J for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 21:54:35 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id DC9C921F8E3C for <ietf@ietf.org>; Tue, 14 May 2013 21:54:34 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BB77620B46 for <ietf@ietf.org>; Wed, 15 May 2013 00:54:33 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Wed, 15 May 2013 00:54:33 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=nwQ+B0h45G7mSsqOJCJT92 j8CEw=; b=V6g80sQFNnxXHn0arh59MHp4FYpAmNHyVsiqugTbw5bU4ZhId8IF26 wO4aRyD0i11BQ3fBfNtNUziA+/c1wBayYowyovDlakOBX06JxuTlo9mlgLSv6LLE XORxfXh0uk/0n3ctfBloKa3CUC6RcAq0BnMPd0jAzh1FUaCZhlNVg=
X-Sasl-enc: JcuzJ4djN6sXwY2HzCQcBSVODvrGhp+wkoyre2YGLwQx 1368593673
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 00BD2C80008; Wed, 15 May 2013 00:54:32 -0400 (EDT)
Message-ID: <51931506.3010702@network-heretics.com>
Date: Wed, 15 May 2013 00:54:30 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net>
In-Reply-To: <5192BB1C.3000902@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: Wed, 15 May 2013 04:54:40 -0000

On 05/14/2013 06:30 PM, Dave Crocker wrote:
> On 5/14/2013 3:12 PM, Ted Lemon wrote:
>> On May 14, 2013, at 6:00 PM, "Joel M. Halpern" <jmh@joelhalpern.com>
>> wrote:
>>> At the same time, discussions do have to be resolvable.  If there
>>> is no way to address it, then it is not a discuss.  But "required
>>> to clar" is the wrong picture as far as I can tell.
>>
>> Exactly right.   It would actually be pretty presumptuous for an AD
>> to say what is required to clear the DISCUSS.   That would tend to
>> imply that the DISCUSS is a directive, not an invitation to, well,
>> discuss.
>
> It isn't an 'invitation'.  It's an exercise in political authority by
> blocking progress of the document.

It's a mistake to inherently define "progress" in terms of advancing the 
document.   Many documents should not be published in the form in which 
they first reach IESG; a few documents that reach IESG should probably 
never be published.

> We came up with the term "Discuss" when I was an AD because, at the
> time, the IESG had little authority and wanted to encourage a
> constructive tone; we didn't want to sound like we were saying 'no'.
>
> And of course, that's still everyone's preference.  But the reality is
> that the imposition of the Discuss is an assertion that changes are
> being required.

That's neither what Discuss means, or what it should mean.   Though I've 
seen many cases where WGs or authors demanded that ADs tell them what to 
fix.   It's understandable that they should want clarity from the AD, 
and yet fixing the document is not the AD's job.
>
> For reference, that milder uses of Discuss, which is something akin to
> "I'd like something clarified" does not require a Discuss.  It requires
> a query to the working group and some dialogue.
>
Disagree.   I've seen a number of cases where informal conversations 
caused more problems and delay than voting DISCUSS.   By the time a 
document has reached final IESG review, it's generally much better to 
have the level of formality and transparency that comes with voting 
DISCUSS.

> Of course we have to _try_ to say what we think would
>> clear the discuss, but I don't think we can go beyond that; it's
>> virtually impossible for us to have complete information.
>
> That makes no sense.  The AD is the one choosing to block progress.  It
> will be the AD who decides to clear the discuss.

I disagree in the strongest possible terms.

If an AD believes that there is something wrong with a document, even 
something that needs clarification, the proper thing for the AD is to 
vote DISCUSS.   This is NOT "choosing to block progress". Publishing 
broken or unclear documents is not progress.

Keith


From moore@network-heretics.com  Tue May 14 22:06:08 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A5721F89EB for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 22:06:08 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2jSkYv4ZYszC for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 22:06:03 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id DDF6821F846C for <ietf@ietf.org>; Tue, 14 May 2013 22:06:02 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B9A1320914 for <ietf@ietf.org>; Wed, 15 May 2013 01:06:01 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 15 May 2013 01:06:01 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=OuPh98usabGz+2pUkUYilJ T1VQg=; b=uSjPHVh3Z38yNuwyEuykFYx4qEUJi1TUXpTsPgRjWpiG4OwQh6sn1H WmpCk8FwbkLGaHWruxG6dGWc8rM3i21X91e349sdknECPcMipCmqNY/jhG79aztG 6cKZO7nznEYOnCjrJrg1t+K3wf+lAgZ4uXhwiAJhG3nOPck8gFChg=
X-Sasl-enc: VLHkkqHwAtD5nqDxo3jKH+wPrYVj8Dz2HIYx5IndjIWa 1368594361
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id DEA02C80005; Wed, 15 May 2013 01:06:00 -0400 (EDT)
Message-ID: <519317B6.8090107@network-heretics.com>
Date: Wed, 15 May 2013 01:05:58 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu>
In-Reply-To: <5192A282.7060409@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 05:06:08 -0000

On 05/14/2013 04:45 PM, Joe Touch wrote:
> Brian, et al.,
>
> On 5/14/2013 1:10 PM, Brian E Carpenter wrote:
>> I think this exchange between Cullen and Ted says it all, except
>> for one tweak: the IESG is allowed, even encouraged, to apply common
>> sense when considering the DISCUSS criteria. They are guidance,
>> not rules.
>>
>> Also, everybody needs to take the word "discuss" literally. An
>> entirely possible outcome is that after discussion, the AD says
>> "Oh. You're correct. Pretend I never spoke!". Or the author says
>> "Oh. You're correct. We'll change it." Either outcome is good.
>
> The trouble with this assumption is the IESG review process.
>
> COMMENTS are appropriate for feedback, but the IESG review process is 
> too often considered an *opportunity* for the IESG to "make the 
> document better", or (in some case) have an opportunity for their input.

For that matter, working groups are too often echo chambers where a set 
of people manage to isolate themselves from input from those whose work 
they might otherwise effect.    Some people seem to think that working 
group output should be sacrosanct.   There's absolutely no reason to 
believe that.  WGs often make technical mistakes that are uncovered by 
external review.   Even when no such mistakes are encountered, WG output 
rarely represents rough consensus of all interested parties, and WGs 
often fail to do due diligence in considering the interests of the broad 
spectrum of those potentially affected by their work.

Of course IESG isn't infallible either, and shouldn't behave as if it 
is.  But review by experts from outside of the WG generally seems to 
improve the IETF's output.

> As important as the DISCUSS criteria are, there are NON-DISCUSS 
> criteria that ought to be more carefully followed - including the 
> point that disagreements with the WG or clarifications are not 
> justification for DISCUSS.

Strongly disagree.  First, DISCUSS only means that there's something the 
AD wants to discuss.    In particular, disagreements with the WG about 
technical quality are always appropriate for IESG to raise. The same is 
true of requests for clarification.

> Ted pointed out that DISCUSS doesn't mean the IESG doesn't like a 
> document - agreed, but it *does* hold up a document until the IESG 
> member clears it.

But there are also procedures within IESG to ignore a single DISCUSS 
vote.   So ultimately it takes multiple DISCUSS votes to hold up a 
document indefinitely.

>
> DISCUSS is a heavyweight mechanism that holds up document resolution; 
> it should be used only where absolutely appropriate. If the IESG wants 
> to have a "discussion" with the authors, they are welcome to 
> participate in the WGs or IETF LC, or to contact them out of band.

DISCUSS is not supposed to be a heavyweight mechanism, and actually it's 
hard to imagine a lighter weight mechanism that gives IESG review any 
weight.   Informal communication doesn't generally work well in practice 
because it lacks transparency, and it can cause additional delay without 
resolving the problem.   Voting DISCUSS puts pressure on BOTH the AD and 
the WG to resolve the issue.

Keith


From swmike@swm.pp.se  Tue May 14 23:00:51 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E433021F8D69 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UG-YSE28TNnI for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:00:51 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 586A421F8D31 for <ietf@ietf.org>; Tue, 14 May 2013 23:00:50 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id F002A9F; Wed, 15 May 2013 08:00:43 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5D3459C for <ietf@ietf.org>; Wed, 15 May 2013 08:00:43 +0200 (CEST)
Date: Wed, 15 May 2013 08:00:43 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: article on innovation and open standards
In-Reply-To: <201305142037.r4EKbBUU4764257@shell01.TheWorld.com>
Message-ID: <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se>
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
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: Wed, 15 May 2013 06:00:52 -0000

On Tue, 14 May 2013, Dale R. Worley wrote:

> The critical difference is that the IETF is an organization of *buyers* 
> rather than an organization of *sellers*.

Not that I have been active in the IETF that long (only a few years), but 
IETF is pretty vendor-heavy.

Otoh hand the whole point with IETF is that *nobody* is *excluded*, it 
consists of all interested parties and the barrier of entry is really low.

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

From moore@network-heretics.com  Tue May 14 23:26:37 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53B4321F8D31 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3QkTJnFHeBEm for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:26:32 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC2F21F8574 for <ietf@ietf.org>; Tue, 14 May 2013 23:26:32 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 710B8207F9 for <ietf@ietf.org>; Wed, 15 May 2013 02:26:27 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Wed, 15 May 2013 02:26:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=NzEDfEgqZ0lp1lhTZJCAnw M4AMM=; b=Tf4bJfDoW16QMra3vDWrELlfvrNdlHdswzw2VUZp8kFlPT50vwjrOo 642AZpszbr3LB3emKBahkKIcSMU4EafpEXIYuEZzMvMrVaimUl0gE9T6VsCzwNE2 hdTdxG47SpjPP0Bv2w9nbt9Qb8LS6+/PS+qfjGNXoUyGxe7sYQtIo=
X-Sasl-enc: dhQLn52tImLyutpY2FtJEpi/p+pISbObMpqdnvhS2iqj 1368599186
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 20FA2C8000B; Wed, 15 May 2013 02:26:25 -0400 (EDT)
Message-ID: <51932A8D.3030206@network-heretics.com>
Date: Wed, 15 May 2013 02:26:21 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 06:26:37 -0000

On 05/15/2013 02:00 AM, Mikael Abrahamsson wrote:
> Otoh hand the whole point with IETF is that *nobody* is *excluded*, it 
> consists of all interested parties and the barrier of entry is really 
> low.
That's what many of us would like to believe.   But IETF certainly 
doesn't consist of all interested parties, and the barrier to effective 
participation (regularly showing up at meetings all over the world and 
spending significant time participating in mailing lists) can be 
prohibitively high.

Yes, I'm aware that some people (including myself) have effectively 
participated on occasion without doing either of the above.   But I 
think it's hard to effectively participate in IETF on a regular basis 
without a significant investment in both time and money.

Keith


From swmike@swm.pp.se  Tue May 14 23:42:02 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5985921F8CEC for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:42:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5IHRTtpYSNR for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:42:02 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id CE43621F8B45 for <ietf@ietf.org>; Tue, 14 May 2013 23:42:01 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C93D69F; Wed, 15 May 2013 08:42:00 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id BC5BE9C for <ietf@ietf.org>; Wed, 15 May 2013 08:42:00 +0200 (CEST)
Date: Wed, 15 May 2013 08:42:00 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: article on innovation and open standards
In-Reply-To: <51932A8D.3030206@network-heretics.com>
Message-ID: <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se>
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se> <51932A8D.3030206@network-heretics.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
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: Wed, 15 May 2013 06:42:02 -0000

On Wed, 15 May 2013, Keith Moore wrote:

> Yes, I'm aware that some people (including myself) have effectively 
> participated on occasion without doing either of the above.  But I think 
> it's hard to effectively participate in IETF on a regular basis without 
> a significant investment in both time and money.

Personally I've only been on a single physical IETF meeting. I participate 
mainly via mailing lists.

And yes, it's hard to participate without spending (significant) time. I 
don't know how else this could be done though. It's at least my opinion 
that if time is made available, the barrier of entry is probably the 
lowest of any similar organisation I can think of.

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

From moore@network-heretics.com  Tue May 14 23:55:43 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA5F21F86F0 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:55:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DTn6i43PrVa7 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 23:55:38 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 6729B21F8B33 for <ietf@ietf.org>; Tue, 14 May 2013 23:55:38 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B5FDE20B3B for <ietf@ietf.org>; Wed, 15 May 2013 02:55:37 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 15 May 2013 02:55:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=7No7HxmRkFysYnGsVlwfL5 M20kg=; b=nB+wLCebIKJsrFrCy0I7810LqsxyYe4wr5zIjDlaxFXBNbNqW5mG05 0M5LHgUQdmKpu1vi4SYCnZlvtAGi0lskcQqJl90MCNaNno2BcOBRlVCrspy74Oio jg/8/CVXDtVtfpHlw9U9HJ9yKJXE1vzSP8Rce10NIOzMRGXt8I+i0=
X-Sasl-enc: ZzXrAvLmQIYQRndbTPyMlDKmtVYFnoTt2kcT7qqr+iSm 1368600937
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 07021C80007; Wed, 15 May 2013 02:55:36 -0400 (EDT)
Message-ID: <51933166.3030708@network-heretics.com>
Date: Wed, 15 May 2013 02:55:34 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se> <51932A8D.3030206@network-heretics.com> <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 06:55:43 -0000

On 05/15/2013 02:42 AM, Mikael Abrahamsson wrote:
> On Wed, 15 May 2013, Keith Moore wrote:
>
>> Yes, I'm aware that some people (including myself) have effectively 
>> participated on occasion without doing either of the above.  But I 
>> think it's hard to effectively participate in IETF on a regular basis 
>> without a significant investment in both time and money.
>
> Personally I've only been on a single physical IETF meeting. I 
> participate mainly via mailing lists.
>
> And yes, it's hard to participate without spending (significant) time. 
> I don't know how else this could be done though. It's at least my 
> opinion that if time is made available, the barrier of entry is 
> probably the lowest of any similar organisation I can think of.

I'd like to see WGs be more pro-active about periodically summarizing 
the salient points of their proposals, determining which parties outside 
of the WG are likely to be affected, explicitly soliciting input from 
those parties, and explicitly considering that input in their 
deliberations.   Some WGs do this, but for most WGs I don't think it 
happens often enough or formally/transparently enough.

Last Call shouldn't be the first time that we explicitly solicit 
feedback on proposals from interested parties outside the WG.

As far as I can tell, the primary reason that WGs are so resistant to 
IESG feedback is that too often the WGs have labored long and hard with 
little or no feedback from external sources, and they've reached 
consensus mostly by exhaustion.   By the time a document gets to IESG 
review and community-wide Last Call, the WG is usually too exhausted 
and/or too committed to that particular solution to fix any major 
flaws.   At this point there are often no good solutions - simple text 
changes and IESG notes are usually inadequate, and publishing the 
document in its current form may do more harm than good.   But if WGs 
got feedback from outside parties much earlier in the process, there's a 
much better chance that such problems could be fixed before the WG were 
exhausted and committed.

Of course anyone can send input to a WG's mailing list at any time. But 
someone who doesn't regularly follow the mailing list can have a 
difficult time understanding the state of things and knowing how and 
when to provide useful input.

Keith


From abdussalambaryun@gmail.com  Wed May 15 01:45:07 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DEB921F8F28 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 01:45:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level: 
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yQBxKUhbdBK6 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 01:45:02 -0700 (PDT)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by ietfa.amsl.com (Postfix) with ESMTP id 086B221F8EB9 for <ietf@ietf.org>; Wed, 15 May 2013 01:45:02 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so1166802pde.9 for <ietf@ietf.org>; Wed, 15 May 2013 01:45:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=NZWUrm7ftRYIfELG4X4M1D6/JfRNgLjvaS9MoKDrUFg=; b=gtj1weyRMXs4oQDn8PvfmRNpLf9TnP33ryOJIGu6ZHuWjTWSyr28tmc8BBN/5DPUNj O4zHGf5XMF/VXPJODPipLllMeC7dPhIodeYldEwPXgj/YXuStLAjlfL3fSNJOtQgBdPc 3I58kZWNB5Gl8ndrkfCMLmQZHy6uRvMxqqxUZgHdT+WlSo2yosc4RErz5Z96YWXWAG2G Rcwv8KLDtktr1JZRHg3893rRzLehx50Q7TEbyYZBcPPt7tzkAbtodiOBRp27xiTdp1OP cKElEP/qdXEgcwz1NSISRtk4zRix4PMBGuj5oUL/oO8a9lz8Jk14icoSQm6GzJRYFXcw 72Dw==
MIME-Version: 1.0
X-Received: by 10.68.14.6 with SMTP id l6mr38186142pbc.202.1368607501689; Wed, 15 May 2013 01:45:01 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Wed, 15 May 2013 01:45:01 -0700 (PDT)
In-Reply-To: <FCC2C49A-88BF-4351-B5AB-DB9B8AB5EBE6@verisign.com>
References: <FCC2C49A-88BF-4351-B5AB-DB9B8AB5EBE6@verisign.com>
Date: Wed, 15 May 2013 10:45:01 +0200
Message-ID: <CADnDZ8-g0cysRbYb8M4X6-EunRobFMNPzxqcwBXOtaw14vse4Q@mail.gmail.com>
Subject: Re: NomCom 2013-2014 Call for Volunteers - CORRECTED dates in first sentence
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 08:45:07 -0000

For diversity purposes in NomCom-participants we may need both
face-to-face participants and remote participant opportunities
considered (may be 5% NomCom to be remote). RFC3777 does make
conditions, but changing it in IETF may not be wanted by active
participants because they are face-to-face ones.  I know that if I
write a I-D for update I may have about 1200 participants that will go
against my proposals so I will need to find 1000 remote participants.

IMHO, it is hard to make 1200 face-to-face participants to change
their mind, but not hard to find 1000 remote ones that agree.

AB
just comments from a remote participant, for future efforts.

On 5/13/13, Mankin, Allison <amankin@verisign.com> wrote:
> The IETF nominating committee (nomcom) process for 2013-14 has begun. The
> IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
> and the IESG. Ten voting members for the nomcom are selected in a
> verifiably
> random way from a pool of volunteers. The more volunteers, the better
> chance
> we have of choosing a random yet representative cross section of the IETF
> population.  This year, a challenge:  let's get beyond the 100-mark for
> number of volunteers.  Let's get to 200 volunteers!
>
> The details of the operation of the nomcom can be found in RFC 3777.
>
> Volunteers must have attended 3 of the past 5 IETF meetings.  As specified
> in
> RFC 3777, that means three out of the five past meetings up to the time
> this
> email announcement goes out to start the solicitation of volunteers. The
> five
> meetings out of which you must have attended three are IETF 82, 83, 84, 85,
> 86.
>
> If you qualify, please volunteer.  However, much as we want this, before you
>
> decide to volunteer, please be sure you are willing to forgo appointment
> to any of the positions for which this nomcom is responsible.
>
> The list of people and posts whose terms end with the March 2014 IETF
> meeting, and thus the positions for which this nomcom is responsible, are
>
> IAOC:
> Chris Griffiths
>
> IAB:
>
> Bernard Aboba
> Marc Blanchet
> Ross Callon
> Eliot Lear
> Hannes Tschofenig
>
> IESG:
>
> Barry Leiba (Applications)
> Brian Haberman (Internet)
> Benoit Claise (Operations and Management)
> Gonzalo Camarillo (RAI)
> Stewart Bryant (Routing)
> Sean Turner (Security)
> Martin Stiemerling (Transport)
>
> The primary activity for this nomcom will begin in July 2013 and should be
> completed in January 2014.  The nomcom will have regularly scheduled
> conference calls to ensure progress.  There will be activities to collect
> requirements from the community, review candidate questionnaires, review
> feedback from community members about candidates, and talk to
> candidates.  Thus, being a nomcom member does require some time commitment.
>
> Please volunteer by sending me an email before 11:59 pm EDT (UTC -4 hours)
> June 16, 2013, as follows:
>
> To: amankin@verisign.com
> Subject: Nomcom 2013-14 Volunteer
>
> Please include the following information in the email body:
>
>  <Your Full Name>
>   // First/Given Name followed by Last/Family Name
>   // matching how you enter it in the IETF Registration Form)
>  <Current Primary Affiliation>
>   // Typically what goes in the Company field
>   // in the IETF Registration Form
> [<All email addresses used to register for the past 5 IETF meetings>]
>  <Preferred email address>
>  <Telephone number>
>   // For confirmation if selected
>
> You should expect an email response from me within 3 business days stating
> whether or not you are qualified.  If you don't receive this response,
> please re-send your email with the tag "RESEND"" added to the subject line.
>
> If you are not yet sure if you would like to volunteer, please consider
> that nomcom members play a very important role in shaping the leadership
> of the IETF. Volunteering for the nomcom is a great way to contribute
> to the IETF!
>
> I will be publishing a more detailed target timetable, as well as details
> of the randomness seeds to be used for the RFC 3797 selection process,
> within the next couple weeks.
>
> Thank you!
> Allison Mankin
> amankin@verisign.com
>
> P.S. Because the 2012-2013 nomcom is still at work, we cannot use the ietf
> addresses for the nomcom chair or the nomcom committee yet, so please send
> all the volunteer mail (and any questions/comments you may have) to the
> address given.
>
>
>
>
>
>
>
>

From jari.arkko@piuha.net  Wed May 15 02:57:18 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04B1D21F8E9E for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 02:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.376
X-Spam-Level: 
X-Spam-Status: No, score=-102.376 tagged_above=-999 required=5 tests=[AWL=0.223, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQEYJDOnOgvS for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 02:57:13 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CA7AA21F8B33 for <ietf@ietf.org>; Wed, 15 May 2013 02:57:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 140CF2CC56; Wed, 15 May 2013 12:57:10 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTQPsJyBDzxo; Wed, 15 May 2013 12:57:08 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 48EA62CC48; Wed, 15 May 2013 12:57:08 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: article on innovation and open standards
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se>
Date: Wed, 15 May 2013 12:57:05 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <1970A8DF-6BC4-4871-B9BC-9C7A2A0A3CF2@piuha.net>
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se> <51932A8D.3030206@network-heretics.com> <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1503)
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, 15 May 2013 09:57:18 -0000

> And yes, it's hard to participate without spending (significant) time. =
I don't know how else this could be done though. It's at least my =
opinion that if time is made available, the barrier of entry is probably =
the lowest of any similar organisation I can think of.

That is my experience as well, at least when talking about organisations =
that I think of as standards bodies. There are other forms of =
co-operation (just a set of interested people on a mailing list, for =
instance) where costs might be even lower. But it is hard for me to =
think there would not be at least some time spent, if you are making a =
comment on anything in any setting. You have to get somewhat familiar =
with the topic, you may have spent time finding out that there is a =
discussion that you want to participate in to begin with, you may have =
invested your own time in building something which made you an expert on =
the topic, etc. Anyway, I think relevance, timeliness, openness are =
probably higher up in my set of priorities for standards making than =
cost minimisation, except where costs are a barrier to the priorities =
higher up in priority.

But in any case, the point that Keith made about explicitly searching =
and soliciting for outsider's input is important. Well run standards =
efforts do this, and try to reach out to people who might care. Even if =
they have no time or possibility to attend IETFs or join mailing lists. =
We should probably try to do it even more than we are now. Sounds like a =
task for working group chairs.

Jari


From jari.arkko@piuha.net  Wed May 15 03:52:29 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6211321F86C1 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 03:52:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.396
X-Spam-Level: 
X-Spam-Status: No, score=-102.396 tagged_above=-999 required=5 tests=[AWL=0.203, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edqGNxWBwdSX for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 03:52:24 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 79C4221F8F69 for <ietf@ietf.org>; Wed, 15 May 2013 03:52:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D560B2CC56 for <ietf@ietf.org>; Wed, 15 May 2013 13:52:18 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2eJmP2XaBsI for <ietf@ietf.org>; Wed, 15 May 2013 13:52:18 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3D99A2CC48 for <ietf@ietf.org>; Wed, 15 May 2013 13:52:18 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <519317B6.8090107@network-heretics.com>
Date: Wed, 15 May 2013 13:52:18 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <077F09F9-6F9F-42B1-B745-541D1D6EDA65@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <519317B6.8090107@network-heretics.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 10:52:29 -0000

I feel that the discussion is stuck on the different perceptions on =
whether an AD's actions are either blocking reasonable progress, or an =
essential correction to a mistake that went undetected.

I'd like to make a couple of observations. First of all, we at the IESG =
process 10-25 documents every second week, and several points (comment =
or discuss) are raised for each one. Given that both working groups and =
the IESG consist of humans, I'm guessing that none of us are making =
perfect decisions all the time. While the Discuss Criteria document is =
very useful, I'd warn against trying to codify the proper behaviour too =
much. It would be very difficult, and ultimately it comes down to making =
a call on whether an issue is really crucial for the Internet or not.

I feel that the discussion and pressure from other ADs and authors and =
the rest of the working group is a more useful avenue to ensure that we =
really are fixing the necessary bugs and only those. And I know you are =
doing that - lets make sure we keep doing it. "If you see something, say =
something". It is everyone's responsibility to try to do the right =
thing, and if you feel it is not happening, say so. I think the current =
IESG has a very good mood for receiving feedback and acting on it. =
(Speaking as the longest serving member in the current IESG, who =
frequently gets shown to be wrong by other ADs or WG folk.)=20

In addition, as discussed separately, moving more of the issue =
resolution to the open and to the WG is a good thing.

Jari


From abdussalambaryun@gmail.com  Wed May 15 05:30:07 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 158DF21F89FD for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 05:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level: 
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2E20sEhtlTgU for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 05:30:02 -0700 (PDT)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by ietfa.amsl.com (Postfix) with ESMTP id F152421F8F4F for <ietf@ietf.org>; Wed, 15 May 2013 05:30:01 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y10so582253pdj.28 for <ietf@ietf.org>; Wed, 15 May 2013 05:30:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=xBv3ibfFzemWZgAoZOb+EGGj2lEWoA65AWMwcGThxPY=; b=EfFoZrEcwFjPlV5xVGZU5W4eEzbW548Yq66L3yiypyUL2gdSXESn0JZ66XPy4+CSgt e06VUanNw+ZbaWoTrop0S7zn1IfrX4OyzdJjA8x6+3aQ+155JsJGsQH1mdd9Hb5ym+rJ qD+WjzrOKaiXDmVOu5D3Dryos6Cws+UBD/Bo7dkPC4UMCjTfvebug+NhUUPH2LfpBGHe X5G/kLq493McAc0I+BELmNPPihMTS7qOEZG7cZCTmXT3hP9FWfd6mWKSg6TVo+O3W0tq Ah9cCNmDWSgzBvrVy5Ld0he6jD7Xk3w9Y/p2V8EnYkHKzD/O5m+TlhwXikf6KJDCAW6D XyGw==
MIME-Version: 1.0
X-Received: by 10.66.74.226 with SMTP id x2mr38877107pav.190.1368621001721; Wed, 15 May 2013 05:30:01 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Wed, 15 May 2013 05:30:01 -0700 (PDT)
Date: Wed, 15 May 2013 14:30:01 +0200
Message-ID: <CADnDZ8-4bjO+r6XXpqgDRR5mWnubZDc0TBE+vgFK_OrVbrrwAQ@mail.gmail.com>
Subject: Re: article on innovation and open standards
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 12:30:07 -0000

> And yes, it's hard to participate without spending (significant) time. I =
don't know how else this could be done though. It's at least my opinion tha=
t if time is made available, the barrier of entry is probably the lowest of=
 any similar organisation I can think of.

I like the article it is a great benefit for us (i.e. permissionless),
and regarding time spent by participants, I think what is important is
not what was *spent*, but what was *used*,  time is money for us and
IETF. The IETF is gaining time as long participants spend it for the
IETF, but the most important times are the ones used in IETF. The
beauty of IETF working time it is not fixed but dynamic per day
(including weekends), no organisation can get similar gain only
through *remote participations*. If IETF reduces remote participation
services, then it will not gain much working times. I agree that IETF
may not be using well the working times spent in WGs. I hope all WGs
encourage permissionless for remote-participants.

I spend 30 minutes for this, including reading thread, but my aim is
used or benefits by someone.

AB

From thierry.moreau@connotech.com  Wed May 15 06:01:33 2013
Return-Path: <thierry.moreau@connotech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACF621F85DC for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 06:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8mvDzPW2Cd4x for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 06:01:28 -0700 (PDT)
Received: from mail.connotech.com (connotech.com [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 5180B21F86F7 for <ietf@ietf.org>; Wed, 15 May 2013 06:01:28 -0700 (PDT)
Received: from [192.168.1.200] (PORTABLE-THIERRY.CONNOTECH-INTERNAL.COM [192.168.1.200]) by mail.connotech.com (Postfix) with ESMTPA id BCF5B317CE; Wed, 15 May 2013 09:00:46 -0400 (EDT)
Message-ID: <51938724.2050704@connotech.com>
Date: Wed, 15 May 2013 09:01:24 -0400
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20090608)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net>	<201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 13:01:33 -0000

Mikael Abrahamsson wrote:
> On Tue, 14 May 2013, Dale R. Worley wrote:
> 
>> The critical difference is that the IETF is an organization of 
>> *buyers* rather than an organization of *sellers*.
> 
> Not that I have been active in the IETF that long (only a few years), 
> but IETF is pretty vendor-heavy.
> 

Some sections of the IETF would be more vendor-heavy, e.g. the routing 
area. In those sections, only a serious economic study might tell to 
which extent the "patent pool" (wikipedia is your friend) excludes the 
permissionless inventor in those IETF sections.

The DNS aspects pertaining to very high throughput nameservers appears 
vendor-heavy. I noticed some patents that are under the IETF IPR policy 
in this niche IT sector, and I am not aware of patent pools in this 
specific case.

> Otoh hand the whole point with IETF is that *nobody* is *excluded*, it 
> consists of all interested parties and the barrier of entry is really low.
> 

Still in the DNS field, the lack of support of authoritative nameservers 
for "generic resource record type" would be a barrier to entry for 
permisionless innovation, maybe with a root cause linked to 
vendor-weight in a portion of the DNS field. Thus, permissionless 
invention occurs with the DNS TXT resource record type.

Let me insist that these two observations are hypotheses.


-- 
- Thierry Moreau

CONNOTECH Experts-conseils inc.
9130 Place de Montgolfier
Montreal, QC, Canada H2M 2A1

Tel. +1-514-385-5691

From swmike@swm.pp.se  Wed May 15 07:00:49 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7824421F8D31 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y2sJ+vZ3gfJv for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:00:49 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id E135121F8539 for <ietf@ietf.org>; Wed, 15 May 2013 07:00:48 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E68429F; Wed, 15 May 2013 16:00:41 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5176A9C; Wed, 15 May 2013 16:00:41 +0200 (CEST)
Date: Wed, 15 May 2013 16:00:41 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: article on innovation and open standards
In-Reply-To: <51933166.3030708@network-heretics.com>
Message-ID: <alpine.DEB.2.00.1305151557020.24367@uplift.swm.pp.se>
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se> <51932A8D.3030206@network-heretics.com> <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se> <51933166.3030708@network-heretics.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 14:00:49 -0000

On Wed, 15 May 2013, Keith Moore wrote:

> I'd like to see WGs be more pro-active about periodically summarizing 
> the salient points of their proposals, determining which parties outside 
> of the WG are likely to be affected, explicitly soliciting input from 
> those parties, and explicitly considering that input in their 
> deliberations.  Some WGs do this, but for most WGs I don't think it 
> happens often enough or formally/transparently enough.

I agree. I'm also participating on nanog-l and other operator lists, and 
it's very rarely that a WG solicits feedback in those kinds of forums.

Question is, if larger feedback is requested, a lot of the time a larger 
feedback will be generated, and more work needed to go through this 
feedback and answer it.

End result might be better, but overall workload would be up, both in 
preparation phase and when feedback is coming in. I'm sure end result 
would probably be better, but more work would be needed, probably 
resulting in less technical work being done.

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

From moore@network-heretics.com  Wed May 15 07:14:52 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 160C121F8633 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vvpkRtZ6dzl9 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:14:47 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id C0CE121F870F for <ietf@ietf.org>; Wed, 15 May 2013 07:14:46 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CD6F320A20; Wed, 15 May 2013 10:14:45 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Wed, 15 May 2013 10:14:45 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=66KI5RIm+VqFrOz9v4Tb6n sRi6w=; b=Qp7iv1R1mZ915EP6V4IyQw1tmkq0XLt4ejkmLdxIMu9ZL8b+stBV/8 Ng+8ulbBltbdn2uTWXw7X+9aHm9sSg4oXdw2qUaQlbd0DkPsd5/s0emnqMeoBChr GZ7IvmnL7KBsSv+v2ycBc7hUI1Cbh5yCcJsFlQ8FB3WGREEeXgZiE=
X-Sasl-enc: 32ngIGv2ofvcDzuk5bzGAUxYLOMUKulsB4ku9i0SzCfs 1368627285
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 2469D2001AE; Wed, 15 May 2013 10:14:45 -0400 (EDT)
Message-ID: <51939851.9090506@network-heretics.com>
Date: Wed, 15 May 2013 10:14:41 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se> <51932A8D.3030206@network-heretics.com> <alpine.DEB.2.00.1305150837220.24367@uplift.swm.pp.se> <51933166.3030708@network-heretics.com> <alpine.DEB.2.00.1305151557020.24367@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1305151557020.24367@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 14:14:52 -0000

On 05/15/2013 10:00 AM, Mikael Abrahamsson wrote:
> On Wed, 15 May 2013, Keith Moore wrote:
>
>> I'd like to see WGs be more pro-active about periodically summarizing 
>> the salient points of their proposals, determining which parties 
>> outside of the WG are likely to be affected, explicitly soliciting 
>> input from those parties, and explicitly considering that input in 
>> their deliberations.  Some WGs do this, but for most WGs I don't 
>> think it happens often enough or formally/transparently enough.
>
> I agree. I'm also participating on nanog-l and other operator lists, 
> and it's very rarely that a WG solicits feedback in those kinds of 
> forums.
>
> Question is, if larger feedback is requested, a lot of the time a 
> larger feedback will be generated, and more work needed to go through 
> this feedback and answer it.
>
> End result might be better, but overall workload would be up, both in 
> preparation phase and when feedback is coming in. I'm sure end result 
> would probably be better, but more work would be needed, probably 
> resulting in less technical work being done.
>

We need to be careful about the tendency to measure IETF's output in 
terms of the number of RFCs produced.   I'd like to see IETF produce 
fewer (and sometimes shorter) RFCs of more relevance and higher 
technical quality, than we do now.

Keith


From touch@isi.edu  Wed May 15 07:26:25 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC82121F8F4D for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:26:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.481
X-Spam-Level: 
X-Spam-Status: No, score=-105.481 tagged_above=-999 required=5 tests=[AWL=1.118, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dWwHzxakhpj for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:26:20 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E4FA521F8EC1 for <ietf@ietf.org>; Wed, 15 May 2013 07:26:19 -0700 (PDT)
Received: from [128.9.176.36] (c1-vpn6.isi.edu [128.9.176.36]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4FEPJ9P004637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 07:25:19 -0700 (PDT)
Message-ID: <51939AD1.6010605@isi.edu>
Date: Wed, 15 May 2013 07:25:21 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com> <5192D684.2000104@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519BB55@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519BB55@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 15 May 2013 14:26:25 -0000

On 5/14/2013 5:53 PM, Ted Lemon wrote:
> On May 14, 2013, at 8:27 PM, Joe Touch <touch@isi.edu> wrote:
>> That is what happens exactly because the DISCUSS holds up the
>> document, and most ADs don't want to burn time stalling their documents
>> if there's a way around that delay.
>
> It can only happen if an author values getting their document
> through  the process more than getting it right, in which case one has to wonder
> why they tried to publish the document in the first place. (I assume you
> meant "authors," not "ADs" above).

No; there are times when the document authors are pressured by ADs to do 
anything to resolve pending DISCUSSes, rather than stand up to the fact 
that the issue is either incorrect or the DISCUSS is invalid.

> The IESG processes documents quite
> quickly; I don't think it's valid to say that there is some terrifying
> stall in the document process as a result of the IESG, such that an
> author needs to chew off their leg to finally get the thing through.

Well, there are IESG members who stand their ground even when it's 
incorrect, such as:

	- claiming that determining WG consensus is up to the AD,
	then repeatedly demanding evidence of that consensus

	- failing to drop a DISCUSS even when it meets their own
	criteria

Those hold up a document too, as you should know (these are examples 
from your review of my doc). As does demanding a document revision while 
there remain open ballot positions, as was done today - on this 
document, to address your pending DISCUSS.

Joe


From touch@isi.edu  Wed May 15 07:30:25 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F0F21F869F for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.653
X-Spam-Level: 
X-Spam-Status: No, score=-105.653 tagged_above=-999 required=5 tests=[AWL=0.946, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OHG1WqGm87GU for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:30:19 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3E40B21F8503 for <ietf@ietf.org>; Wed, 15 May 2013 07:30:19 -0700 (PDT)
Received: from [128.9.176.36] (c1-vpn6.isi.edu [128.9.176.36]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4FEU0gL005558 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 07:30:00 -0700 (PDT)
Message-ID: <51939BEA.7040600@isi.edu>
Date: Wed, 15 May 2013 07:30:02 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <20130514224605.GI17491@mx1.yitter.info> <5192C58F.5070304@dcrocker.net> <5192CF7C.6080108@joelhalpern.com>
In-Reply-To: <5192CF7C.6080108@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 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, 15 May 2013 14:30:25 -0000

On 5/14/2013 4:57 PM, Joel M. Halpern wrote:
> And your bottom line is exactly what te rules say, what I said, what Ted
> said, and what Joe agreed is reasonable.

Unfortunately, it's not what happens/is happening right now.

Joe

From touch@isi.edu  Wed May 15 07:35:29 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F4621F853A for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.72
X-Spam-Level: 
X-Spam-Status: No, score=-105.72 tagged_above=-999 required=5 tests=[AWL=0.879, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVbuvhdffUNX for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:35:24 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 0DA8021F8599 for <ietf@ietf.org>; Wed, 15 May 2013 07:35:24 -0700 (PDT)
Received: from [128.9.176.36] (c1-vpn6.isi.edu [128.9.176.36]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4FEZ4SS006333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 07:35:04 -0700 (PDT)
Message-ID: <51939D19.2050907@isi.edu>
Date: Wed, 15 May 2013 07:35:05 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519B873@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, 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, 15 May 2013 14:35:29 -0000

On 5/14/2013 4:03 PM, Ted Lemon wrote:
> The whole point of a DISCUSS is to have a discussion.

The *whole* point of a DISCUSS is to hold a document in IETF review 
until a discussion is *resolved*.

There are thus three parts:
	- having a discussion
	- pausing the document
	- waiting for resolution

Nothing limits the IESG to having a "discussion" by issuing a DISCUSS; 
they can issue COMMENTs in any position and simply ask for a dialogue.

Because DISCUSS includes these other properties, it influences authors 
to make changes simply to make a DISCUSS go away, due to pressure by the 
IESG or their own ADs.

That's why they need to be used only where that pressure is appropriate 
and not inappropriate; that's the reason there are both DISCUSS and 
NON-DISCUSS criteria, and why it's very important for those in IESG 
review to hold the IESG to that distinction.

Joe

From touch@isi.edu  Wed May 15 07:39:58 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41B7C21F9133 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.779
X-Spam-Level: 
X-Spam-Status: No, score=-105.779 tagged_above=-999 required=5 tests=[AWL=0.820, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c4xsELIcNs-L for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:39:52 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2A521F90BB for <ietf@ietf.org>; Wed, 15 May 2013 07:39:52 -0700 (PDT)
Received: from [128.9.176.36] (c1-vpn6.isi.edu [128.9.176.36]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4FEdZ87007249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 07:39:35 -0700 (PDT)
Message-ID: <51939E29.7080309@isi.edu>
Date: Wed, 15 May 2013 07:39:37 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com>
In-Reply-To: <51931506.3010702@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 15 May 2013 14:39:58 -0000

On 5/14/2013 9:54 PM, Keith Moore wrote:
> Publishing broken or unclear documents is not progress.
>
> Keith

Broken, agreed.

Unclear, nope - please review the NON-DISCUSS criteria, notably:

The motivation for a particular feature of a protocol is not clear 
enough. At the IESG review stage, protocols should not be blocked 
because they provide capabilities beyond what seems necessary to acquit 
their responsibilities.

The DISCUSS isn't there to make documents "better" - that's for 
COMMENTs. A DISCUSS there to catch a set of problems and to *block* the 
document's progress until that problem is resolved.

Joe

From moore@network-heretics.com  Wed May 15 07:41:48 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEA2C21F8F83 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:41:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LRL7tQ+zLsgi for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:41:43 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id A9A3A21F8FE9 for <ietf@ietf.org>; Wed, 15 May 2013 07:41:43 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 629D5206FF; Wed, 15 May 2013 10:41:43 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Wed, 15 May 2013 10:41:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=muNN5uy62Xb8yDTBv6ecau ocNvQ=; b=JKF3E5DbqBQoIbSl8hldlRiy53LmNd7k75faYasY2zUrNvI2U98J0+ NPpF/DY8k5b/2X1jr6X4cDQjq981THKo6jqe2xNOgdi7aHhlX+XUrAVfdRC6KbH7 /BaKeTURQ/7pb9GHOVOvjS++FRiVVfrpry1nbK25dqscI9tye1R+k=
X-Sasl-enc: WVbcfbR3eadYqhX8LyfYq3SkBvBEjDSRzDmTJVe9s6m1 1368628902
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id A2614C80007; Wed, 15 May 2013 10:41:42 -0400 (EDT)
Message-ID: <51939EA0.9070704@network-heretics.com>
Date: Wed, 15 May 2013 10:41:36 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu>
In-Reply-To: <51939E29.7080309@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 14:41:48 -0000

On 05/15/2013 10:39 AM, Joe Touch wrote:
>
>
> On 5/14/2013 9:54 PM, Keith Moore wrote:
>> Publishing broken or unclear documents is not progress.
>>
>> Keith
>
> Broken, agreed.
>
> Unclear, nope - please review the NON-DISCUSS criteria, notably:
>
> The motivation for a particular feature of a protocol is not clear 
> enough. At the IESG review stage, protocols should not be blocked 
> because they provide capabilities beyond what seems necessary to 
> acquit their responsibilities.
>
> The DISCUSS isn't there to make documents "better" - that's for 
> COMMENTs. A DISCUSS there to catch a set of problems and to *block* 
> the document's progress until that problem is resolved.

I strongly disagree with what the NON-DISCUSS criteria say. DISCUSS 
isn't just for blocking documents.   And document quality is as 
important (in the sense that poor document quality can lead to as many 
interoperability or other problems) as technical correctness.

Why are people trying to sabotage IESG?

Keith


From touch@isi.edu  Wed May 15 07:49:13 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20BD21F8F83 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.83
X-Spam-Level: 
X-Spam-Status: No, score=-105.83 tagged_above=-999 required=5 tests=[AWL=0.769, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CYBMcHmxGu0L for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:49:08 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2637421F8F69 for <ietf@ietf.org>; Wed, 15 May 2013 07:49:08 -0700 (PDT)
Received: from [128.9.176.36] (c1-vpn6.isi.edu [128.9.176.36]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4FElwGb008847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 07:47:58 -0700 (PDT)
Message-ID: <5193A01F.1030507@isi.edu>
Date: Wed, 15 May 2013 07:47:59 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <519317B6.8090107@network-heretics.com>
In-Reply-To: <519317B6.8090107@network-heretics.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 14:49:14 -0000

On 5/14/2013 10:05 PM, Keith Moore wrote:
...
> For that matter, working groups are too often echo chambers where a set
> of people manage to isolate themselves from input from those whose work
> they might otherwise effect.    Some people seem to think that working
> group output should be sacrosanct.   There's absolutely no reason to
> believe that.  WGs often make technical mistakes that are uncovered by
> external review.   Even when no such mistakes are encountered, WG output
> rarely represents rough consensus of all interested parties, and WGs
> often fail to do due diligence in considering the interests of the broad
> spectrum of those potentially affected by their work.
>
> Of course IESG isn't infallible either, and shouldn't behave as if it
> is.  But review by experts from outside of the WG generally seems to
> improve the IETF's output.

Sure, but note that there is a specific NON-DISCUSS criteria on this point:

Disagreement with informed WG decisions that do not exhibit problems 
outlined in Section 3.1 (DISCUSS Criteria). In other words, disagreement 
in preferences among technically sound approaches.

Finding technical mistakes is good, but imposing the IESG's preferred 
technical solution over the WG's preference is inappropriate, but happens.

>> As important as the DISCUSS criteria are, there are NON-DISCUSS
>> criteria that ought to be more carefully followed - including the
>> point that disagreements with the WG or clarifications are not
>> justification for DISCUSS.
>
> Strongly disagree.  First, DISCUSS only means that there's something the
> AD wants to discuss.

As noted in another post, it means "hold this doc until the DISCUSS is 
resolved". Discussions can happen as a result of COMMENTs in any IESG 
position.

>  In particular, disagreements with the WG about
> technical quality are always appropriate for IESG to raise.

Yes.

> same is
> true of requests for clarification.

Sometimes - there's a specific NON-CRITERIA about clarification, however:

The motivation for a particular feature of a protocol is not clear 
enough. At the IESG review stage, protocols should not be blocked 
because they provide capabilities beyond what seems necessary to acquit 
their responsibilities.

>> Ted pointed out that DISCUSS doesn't mean the IESG doesn't like a
>> document - agreed, but it *does* hold up a document until the IESG
>> member clears it.
>
> But there are also procedures within IESG to ignore a single DISCUSS
> vote.   So ultimately it takes multiple DISCUSS votes to hold up a
> document indefinitely.

Those procedures take time, so even a single DISCUSS holds things up.

>> DISCUSS is a heavyweight mechanism that holds up document resolution;
>> it should be used only where absolutely appropriate. If the IESG wants
>> to have a "discussion" with the authors, they are welcome to
>> participate in the WGs or IETF LC, or to contact them out of band.
>
> DISCUSS is not supposed to be a heavyweight mechanism, and actually it's
> hard to imagine a lighter weight mechanism that gives IESG review any
> weight.

Oh, I'm not suggesting removing the DISCUSS mechanism.

First, it ought to have a new name - one that makes clear that this is 
heavyweight. Perhaps "HOLD FOR REVISION", which is the net effect it 
already has.

The key bug is that the IESG can't easily issue a question without 
casting a ballot position, but that may also be a feature. It might be 
useful to be able to issue a QUESTION withouth changing a ballot 
position, though.

 > Informal communication doesn't generally work well in practice
> because it lacks transparency, and it can cause additional delay without
> resolving the problem.   Voting DISCUSS puts pressure on BOTH the AD and
> the WG to resolve the issue.

Which is appropriate only when the IESG should have the right to force 
that resolution, and when the path to that resolution is sufficiently 
clear. If there is no path, then vote NO. If forcing resolution and 
putting pressure isn't warranted, issue a COMMENT on any other ballot 
position.

Joe

From rdroms.ietf@gmail.com  Wed May 15 07:49:55 2013
Return-Path: <rdroms.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 2B0FB21F91F1 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4YpgPKRRlmw7 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:49:50 -0700 (PDT)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id EEBF821F91A5 for <ietf@ietf.org>; Wed, 15 May 2013 07:49:49 -0700 (PDT)
Received: by mail-vc0-f181.google.com with SMTP id lf11so1834077vcb.26 for <ietf@ietf.org>; Wed, 15 May 2013 07:49:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=9y4tomliLlOUfnHFOII+Ln9nRlcxnu3tNiYTbv/g/BM=; b=omoGzYuo+TDj7t7Dc0rG4MvcrfCRb3RdEfrGjNn/0VKFj/IwpcYWmHSRcv9Bv149aO XePB3dOhzL9DRKpaMOHbvAW/Xho332+/H8D24MxukfwHaRClO/G3Jh6v+A4acTtWlvkk vD9Ps3kNy3Gf9HNFXU/GaJaptxuokE2pB3AWRPQJDetMeOECAMvYNz0onT0MNjebQxsB zRNCo9VxkoquDNOsafqri2/1+FnISn0/Og1bDFNHn0i+sgvN7iere6fvSB2HineujiOa ezh8iF9uvWj3k87GMlR/hahvGKt99lSWdA/Y9ifQMnB7gGuOtoieaInvOGDcJslVO8UB Qw6w==
X-Received: by 10.58.90.66 with SMTP id bu2mr25098003veb.29.1368629389252; Wed, 15 May 2013 07:49:49 -0700 (PDT)
Received: from ?IPv6:2001:420:2c51:1311:d1e2:66e2:b4c9:df84? ([2001:420:2c51:1311:d1e2:66e2:b4c9:df84]) by mx.google.com with ESMTPSA id s9sm3024435vdh.4.2013.05.15.07.49.46 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 May 2013 07:49:46 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <51939E29.7080309@isi.edu>
Date: Wed, 15 May 2013 10:49:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A584852E-C7B0-4533-B4FC-C173A9BD06D3@gmail.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 14:49:55 -0000

On May 15, 2013, at 10:39 AM 5/15/13, Joe Touch <touch@ISI.EDU> wrote:

>=20
>=20
> On 5/14/2013 9:54 PM, Keith Moore wrote:
>> Publishing broken or unclear documents is not progress.
>>=20
>> Keith
>=20
> Broken, agreed.
>=20
> Unclear, nope - please review the NON-DISCUSS criteria, notably:
>=20
> The motivation for a particular feature of a protocol is not clear =
enough. At the IESG review stage, protocols should not be blocked =
because they provide capabilities beyond what seems necessary to acquit =
their responsibilities.
>=20
> The DISCUSS isn't there to make documents "better" - that's for =
COMMENTs. A DISCUSS there to catch a set of problems and to *block* the =
document's progress until that problem is resolved.

I'll agree with you *if* you consider an unclear description of a =
feature of a protocol, severe enough that reader of the specification =
are not able to build interoperable implementations, as a problem for =
which a DISCUSS can be posted.

In my opinion, there are many ways in which document can be unclear =
beyond the "motivation for a particular feature of a protocol is not =
clear enough." =20

- Ralph

>=20
> Joe


From Ted.Lemon@nominum.com  Wed May 15 07:55:56 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA2E11E80A6 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.58
X-Spam-Level: 
X-Spam-Status: No, score=-106.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wd-w0mHfWGVa for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 07:55:49 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 8605121F86C1 for <ietf@ietf.org>; Wed, 15 May 2013 07:55:45 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUZOh8SbmOrZ57FrcmhX4Q+6hFc+MO2N7@postini.com; Wed, 15 May 2013 07:55:45 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E2F371B80B1 for <ietf@ietf.org>; Wed, 15 May 2013 07:55:44 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id DA69C19005D; Wed, 15 May 2013 07:55:44 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 15 May 2013 07:55:44 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgIAABRkAgABrMACAAKN7gIAAAI4AgAAD8YA=
Date: Wed, 15 May 2013 14:55:43 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com>
In-Reply-To: <51939EA0.9070704@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <477504C1093D404C9E16A96AAA84257D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 14:55:56 -0000

On May 15, 2013, at 10:41 AM, Keith Moore <moore@network-heretics.com> wrot=
e:
>> The motivation for a particular feature of a protocol is not clear enoug=
h. At the IESG review stage, protocols should not be blocked because they p=
rovide capabilities beyond what seems necessary to acquit their responsibil=
ities.
>=20
> I strongly disagree with what the NON-DISCUSS criteria say. DISCUSS isn't=
 just for blocking documents.   And document quality is as important (in th=
e sense that poor document quality can lead to as many interoperability or =
other problems) as technical correctness.

The interpretation of this particular NON-DISCUSS criterion that Joe has gi=
ven is simply wrong.   The key word to pay attention to to see the error is=
 "motivation."   The point of this criterion is to eliminate a very specifi=
c sort of stall that has been known to happen in the past: the stall where =
the AD doesn't understand why the document is being put forward at all, and=
 therefore blocks the document until the authors explain the motivation beh=
ind the document to the satisfaction of the AD who is holding the DISCUSS.

This is a real issue that has created real problems in the past, and that i=
s why it is in the NON-DISCUSS criteria.   But this criterion _does not_ me=
an that a criticism that the document itself is unclear is not a valid reas=
on to hold a DISCUSS on it.   In fact, it's an excellent reason to hold a D=
ISCUSS on it.   A lack of clarity in a document can result in it being impl=
emented incorrectly, or in the case of a BCP, interpreted incorrectly.   Or=
 in extreme cases, not read at all.   This is a bad outcome, worth spending=
 time on, even if the authors would rather be quit of it.


From moore@network-heretics.com  Wed May 15 08:06:41 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA9FE21F8F12 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:06:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ASRY-mNeJOVY for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:06:36 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id B26D721F8F0A for <ietf@ietf.org>; Wed, 15 May 2013 08:06:36 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id A704A20F08; Wed, 15 May 2013 11:06:31 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 15 May 2013 11:06:32 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:from :subject:date:to; s=smtpout; bh=UIpfAKpE0P/2AmGZoudUd6koxNA=; b= dpaFjE3i+NZWY42H46noxmss2zi7iBfJ81jwnZ+I3NrSb1wWpJVa4TEK8skaGcuQ fK0eAEtMCz30c4a3VOtDghUp+7atLESi030DpVyQ7UZ3fOJkJLt0Kg+tUZI2/a4e i6UAIPp8mV2lFm+3YqspHqsL9YoB6qK0biKX0m3Jzhs=
X-Sasl-enc: mYvk1a/nOZKRmmI9WeFIq7DajjBBB2sA7hdCo/N74PHI 1368630384
Received: from [21.148.133.29] (unknown [66.87.153.29]) by mail.messagingengine.com (Postfix) with ESMTPA id 7938AC80010; Wed, 15 May 2013 11:06:24 -0400 (EDT)
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <1F717CBE-ADD9-4BD5-B0A7-4E5B5D26CD13@network-heretics.com>
X-Mailer: iPhone Mail (10B329)
From: Keith Moore <moore@network-heretics.com>
Subject: Re: call for ideas: tail-heavy IETF process
Date: Wed, 15 May 2013 11:06:22 -0400
To: Ted Lemon <Ted.Lemon@nominum.com>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 15:06:41 -0000

IMO, IESG should have grounds to reject any document that isn't specifically=
 authorized in a WG's charter.

- Keith

On May 15, 2013, at 10:55 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On May 15, 2013, at 10:41 AM, Keith Moore <moore@network-heretics.com> wro=
te:
>>> The motivation for a particular feature of a protocol is not clear enoug=
h. At the IESG review stage, protocols should not be blocked because they pr=
ovide capabilities beyond what seems necessary to acquit their responsibilit=
ies.
>>=20
>> I strongly disagree with what the NON-DISCUSS criteria say. DISCUSS isn't=
 just for blocking documents.   And document quality is as important (in the=
 sense that poor document quality can lead to as many interoperability or ot=
her problems) as technical correctness.
>=20
> The interpretation of this particular NON-DISCUSS criterion that Joe has g=
iven is simply wrong.   The key word to pay attention to to see the error is=
 "motivation."   The point of this criterion is to eliminate a very specific=
 sort of stall that has been known to happen in the past: the stall where th=
e AD doesn't understand why the document is being put forward at all, and th=
erefore blocks the document until the authors explain the motivation behind t=
he document to the satisfaction of the AD who is holding the DISCUSS.
>=20
> This is a real issue that has created real problems in the past, and that i=
s why it is in the NON-DISCUSS criteria.   But this criterion _does not_ mea=
n that a criticism that the document itself is unclear is not a valid reason=
 to hold a DISCUSS on it.   In fact, it's an excellent reason to hold a DISC=
USS on it.   A lack of clarity in a document can result in it being implemen=
ted incorrectly, or in the case of a BCP, interpreted incorrectly.   Or in e=
xtreme cases, not read at all.   This is a bad outcome, worth spending time o=
n, even if the authors would rather be quit of it.
>=20

From jari.arkko@piuha.net  Wed May 15 08:15:37 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFFC21F8709 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:15:37 -0700 (PDT)
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.186, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BZQoDdp6CZeu for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:15:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DFA7121F859D for <ietf@ietf.org>; Wed, 15 May 2013 08:15:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 68C1A2CC48; Wed, 15 May 2013 18:15:30 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FR_gkx8LUOZT; Wed, 15 May 2013 18:15:29 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id DA4472CC56; Wed, 15 May 2013 18:15:29 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: call for ideas: tail-heavy IETF process
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51939E29.7080309@isi.edu>
Date: Wed, 15 May 2013 18:15:29 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4826D20-F8CB-4121-A505-DED8DD9BE1E0@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 15:15:37 -0000

Joe,

> Broken, agreed.

Yep.

> Unclear, nope - please review the NON-DISCUSS criteria, notably:
>=20
> The motivation for a particular feature of a protocol is not clear =
enough. At the IESG review stage, protocols should not be blocked =
because they provide capabilities beyond what seems necessary to acquit =
their responsibilities.
>=20
> The DISCUSS isn't there to make documents "better" - that's for =
COMMENTs. A DISCUSS there to catch a set of problems and to *block* the =
document's progress until that problem is resolved.


Yes, but note that there are multiple aspects of "unclear". You cite =
above the motivation aspect. There's also a DISCUSS criteria for other =
forms of unclear, e.g., if I can't figure out what I should do in the =
implementation, it would be an issue. The criteria document confirms:

"The specification is impossible to implement due to technical or =
clarity issues."


> Sure, but note that there is a specific NON-DISCUSS criteria on this =
point:
>=20
> Disagreement with informed WG decisions that do not exhibit problems =
outlined in Section 3.1 (DISCUSS Criteria). In other words, disagreement =
in preferences among technically sound approaches.
>=20
> Finding technical mistakes is good, but imposing the IESG's preferred =
technical solution over the WG's preference is inappropriate, but =
happens.

If you are hit with a Discusss that is about preferring another =
technical solution, you should push back.

Jari


From andy@yumaworks.com  Tue May 14 17:56:12 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2088921F8539 for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 17:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.494
X-Spam-Level: 
X-Spam-Status: No, score=-1.494 tagged_above=-999 required=5 tests=[AWL=0.483,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4n1o1n-QTJLS for <ietf@ietfa.amsl.com>; Tue, 14 May 2013 17:56:11 -0700 (PDT)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6369721F8E3C for <ietf@ietf.org>; Tue, 14 May 2013 17:56:10 -0700 (PDT)
Received: by mail-ie0-f182.google.com with SMTP id a14so2525718iee.27 for <ietf@ietf.org>; Tue, 14 May 2013 17:56:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=dGBs89f1H+EOaquY14ewPjN60XmOGJhDfMrZI7A8GI0=; b=MsA0Q/kX6jjkeMdUY8SXwLshoVc9z3Xxk1jRZiYvhtHwXj+yhb/AdyO+W6cyummWBD FbBL0ZmjcRYGv0P833/HC9izockxTe7XK/c5fQtzUzjdTfanhotslAwwd9gs1kNZ6qfk Sixsrr+zUpX9imK4we0FN9yqubH+w5qiM27RmTSdFy5//7dT+jZc4W4pztdsyhiwbT8I UexdUL04v1ocFa92g7MMEvSV2Wckkp6LeHUwwuEGBeoTUko5JBsaaa9Orxf1i9Yqcirf H2GtIJ26xIHPNd+QkNNYM+hj590LsvJWrO5mtoHzet0iVLvLJPHOlgtjYuFoaPTDjnH+ 25KA==
MIME-Version: 1.0
X-Received: by 10.50.140.73 with SMTP id re9mr3891443igb.59.1368579370232; Tue, 14 May 2013 17:56:10 -0700 (PDT)
Received: by 10.231.206.71 with HTTP; Tue, 14 May 2013 17:56:10 -0700 (PDT)
In-Reply-To: <5192CF7C.6080108@joelhalpern.com>
References: <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <20130514224605.GI17491@mx1.yitter.info> <5192C58F.5070304@dcrocker.net> <5192CF7C.6080108@joelhalpern.com>
Date: Tue, 14 May 2013 17:56:10 -0700
Message-ID: <CABCOCHTC=9UxYhOTh7cvcMhOEDbepUfAwW9zGFjqPcyR41QreQ@mail.gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
From: Andy Bierman <andy@yumaworks.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=e89a8f50344435be4104dcb7372a
X-Gm-Message-State: ALoCoQk8+rGpBAsK0+FrSkBy6hVvZZYU2oeMWYAz99vcqwLKLq/l4LmjUS2onqAABJg3gthi7DF/
X-Mailman-Approved-At: Wed, 15 May 2013 08:18:10 -0700
Cc: 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, 15 May 2013 00:56:12 -0000

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

Hi,

The evidence seems to show that the IESG is getting faster
at their job and WGs are getting slower at theirs.  I don't
see any need for "DISCUSS Rules".  All the AD reviews I've
experienced have improved the document, sometimes a lot.
All DISCUSS issues got cleared with reasonable (even good)
solutions.

IMO, there is no question that applying the right expertise at the
appropriate time in the WG draft process would improve the
entire system and avoid surprises during I* Last Call.
The question is the best way to do that.

Andy


On Tue, May 14, 2013 at 4:57 PM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> And your bottom line is exactly what te rules say, what I said, what Ted
> said, and what Joe agreed is reasonable.  It also matchesthe practice I
> have seen.  Even the discuss that I had a lot of arguments with did include
> proposals for paths forward.  Sometimes they were ard to understand.
>  That's probably inevitable with all these opinionated humans doing this.
>
> Yours,
> Joel
>
> On 5/14/2013 7:15 PM, Dave Crocker wrote:
>
>> On 5/14/2013 3:46 PM, Andrew Sullivan wrote:
>>
>>  To be fair, for what it's worth as a WG chair I've had the latter
>>> experience at least as often as the former in the use of DISCUSS, and
>>> I've observed some DISCUSSes cleared without any change at all to the
>>> document in question.
>>>
>>
>> We suffer a continuing logic error in the IETF.  We use "sometimes it
>> happens the other way" as if that negates the existence and problem
>> cause by what is being criticized.
>>
>> So, yeah, of course a Discuss /sometimes/ causes a small delay with no
>> changes.  /Sometimes/ ADs use the sledgehammer of the Discuss to ask for
>> a bit of conversation.  That's all irrelevant.
>>
>> What's relevant is the nature of the mechanisms, its capability, and the
>> cost it can and does impose on authors and the working group.
>>
>> When a serious defect is identified, it's entirely worth the cost.
>>
>> When it isn't, it isn't.
>>
>> In all cases, the person imposing the cost has an obligation to
>> facilitate closing it, including making clear the criteria for closing
>> it.  It is unreasonable to have those who must do the work to clear it
>> play a guessing game.
>>
>>

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

Hi,<div><br></div><div>The evidence seems to show that the IESG is getting =
faster</div><div>at their job and WGs are getting slower at theirs. =A0I do=
n&#39;t</div><div>see any need for &quot;DISCUSS Rules&quot;. =A0All the AD=
 reviews I&#39;ve</div>
<div>experienced have improved the document, sometimes a lot.</div><div>All=
 DISCUSS issues got cleared with reasonable (even good)</div><div>solutions=
.</div><div><br></div><div>IMO, there is no question that applying the righ=
t expertise at the</div>
<div>appropriate time in the WG draft process would improve the</div><div>e=
ntire system and avoid surprises during I* Last Call.</div><div>The questio=
n is the best way to do that.</div><div><br></div><div>Andy</div><div><br>
</div><div><br><div class=3D"gmail_quote">On Tue, May 14, 2013 at 4:57 PM, =
Joel M. Halpern <span dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com=
" target=3D"_blank">jmh@joelhalpern.com</a>&gt;</span> wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
And your bottom line is exactly what te rules say, what I said, what Ted sa=
id, and what Joe agreed is reasonable. =A0It also matchesthe practice I hav=
e seen. =A0Even the discuss that I had a lot of arguments with did include =
proposals for paths forward. =A0Sometimes they were ard to understand. =A0T=
hat&#39;s probably inevitable with all these opinionated humans doing this.=
<br>

<br>
Yours,<br>
Joel<br>
<br>
On 5/14/2013 7:15 PM, Dave Crocker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 5/14/2013 3:46 PM, Andrew Sullivan wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
To be fair, for what it&#39;s worth as a WG chair I&#39;ve had the latter<b=
r>
experience at least as often as the former in the use of DISCUSS, and<br>
I&#39;ve observed some DISCUSSes cleared without any change at all to the<b=
r>
document in question.<br>
</blockquote>
<br>
We suffer a continuing logic error in the IETF. =A0We use &quot;sometimes i=
t<br>
happens the other way&quot; as if that negates the existence and problem<br=
>
cause by what is being criticized.<br>
<br>
So, yeah, of course a Discuss /sometimes/ causes a small delay with no<br>
changes. =A0/Sometimes/ ADs use the sledgehammer of the Discuss to ask for<=
br>
a bit of conversation. =A0That&#39;s all irrelevant.<br>
<br>
What&#39;s relevant is the nature of the mechanisms, its capability, and th=
e<br>
cost it can and does impose on authors and the working group.<br>
<br>
When a serious defect is identified, it&#39;s entirely worth the cost.<br>
<br>
When it isn&#39;t, it isn&#39;t.<br>
<br>
In all cases, the person imposing the cost has an obligation to<br>
facilitate closing it, including making clear the criteria for closing<br>
it. =A0It is unreasonable to have those who must do the work to clear it<br=
>
play a guessing game.<br>
<br>
</blockquote>
</blockquote></div><br></div>

--e89a8f50344435be4104dcb7372a--

From ynir@checkpoint.com  Wed May 15 08:33:47 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F23B021F9133 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:33:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.227
X-Spam-Level: 
X-Spam-Status: No, score=-10.227 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8GMgPbOkXhrm for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:33:41 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id B64CD21F9130 for <ietf@ietf.org>; Wed, 15 May 2013 08:33:40 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4FFXTJs016931; Wed, 15 May 2013 18:33:33 +0300
X-CheckPoint: {5193A8D5-D-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Wed, 15 May 2013 18:33:29 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFXXIl2sAtusE6dtOC39kdvwZkElveAgAArdgCAAAXXAIAANn+AgAAJ/QCAAAPSAIAAA7+AgAANYoCAAANIgIAABRkAgABrMACAAKN6gIAAAI4AgAAD8oCAAAL6AIAAB5GA
Date: Wed, 15 May 2013 15:33:28 +0000
Message-ID: <F49C3B7A-355A-42D1-BAE9-F0FAD5641EBE@checkpoint.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <1F717CBE-ADD9-4BD5-B0A7-4E5B5D26CD13@network-heretics.com>
In-Reply-To: <1F717CBE-ADD9-4BD5-B0A7-4E5B5D26CD13@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.104]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 111d011399e67af7939e118fda53739bfc4ee1acee
Content-Type: text/plain; charset="us-ascii"
Content-ID: <9B316CF566A87C4781A977CE6CE38AF4@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 15:33:47 -0000

On May 15, 2013, at 6:06 PM, Keith Moore <moore@network-heretics.com>
 wrote:

> IMO, IESG should have grounds to reject any document that isn't specifica=
lly authorized in a WG's charter.
>=20
> - Keith
>=20

Why? There's definitely a process failure there, and it should be blamed on=
 the WG chairs and/or the AD, who should have either moved the work out of =
the working group or worked on updating the charter.

But the IESG handles documents from both working groups and from individual=
s, and individuals don't have charters.  Why should an otherwise good docum=
ent be rejected after it has gone through IETF last call and has been broug=
ht to the IESG by one of their own?

Yoav



From narten@us.ibm.com  Wed May 15 08:55:56 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E6A21F87FB for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-rRYTRc0mJc for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 08:55:50 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA5821F8ED8 for <ietf@ietf.org>; Wed, 15 May 2013 08:55:49 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 15 May 2013 11:55:42 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 15 May 2013 11:55:40 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 5A832C9003E for <ietf@ietf.org>; Wed, 15 May 2013 11:55:39 -0400 (EDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4FFtbYE265700 for <ietf@ietf.org>; Wed, 15 May 2013 11:55:38 -0400
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 r4FFtYdG021565 for <ietf@ietf.org>; Wed, 15 May 2013 09:55:34 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-104-101.mts.ibm.com [9.65.104.101]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4FFtXBi021278; Wed, 15 May 2013 09:55:33 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r4FFtSPM007981; Wed, 15 May 2013 17:55:28 +0200
Message-Id: <201305151555.r4FFtSPM007981@cichlid.raleigh.ibm.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: call for ideas: tail-heavy IETF process
In-reply-to: <077F09F9-6F9F-42B1-B745-541D1D6EDA65@piuha.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <519317B6.8090107@network-heretics.com> <077F09F9-6F9F-42B1-B745-541D1D6EDA65@piuha.net>
Comments: In-reply-to Jari Arkko <jari.arkko@piuha.net> message dated "Wed, 15 May 2013 13:52:18 +0300."
Date: Wed, 15 May 2013 17:55:27 +0200
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13051515-7182-0000-0000-000006B82052
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 15:55:56 -0000

+1 to what Jari says below.

>From my perspective, the important things to keep in mind:

1) Discuss criteria should be principles, not rigid rules. The details
of the issue at hand always matter, and it will sometimes come down to
judgement calls where reasonable individuals just might disagree. And
if we try to replace judgement with rigid, overly specified rules, we
surely won't like the results. i.e, the process requires we do X, when
X is really a bad outcome overall.

2) There will always be judgement calls, where an AD and an author (or
WG) don't necessarily agree. Fine tuning the rules won't fix that. By
default, when there is disagreement, the presumption needs to be the
AD could be right and needs to be convinced. That is the essence of
what a DISCUSS is intended to be. If the dialog between author/WG/AD
is not progressing, bring in someone else. I.e., the way to overrule a
"stubborn" AD is to convince other ADs (and/or WG members) to weigh in
based on the merits. If an author/WG can't do that, that says
something...

Thomas

Jari Arkko <jari.arkko@piuha.net> writes:

> I feel that the discussion is stuck on the different perceptions on
> whether an AD's actions are either blocking reasonable progress, or
> an essential correction to a mistake that went undetected.

> I'd like to make a couple of observations. First of all, we at the
> IESG process 10-25 documents every second week, and several points
> (comment or discuss) are raised for each one. Given that both
> working groups and the IESG consist of humans, I'm guessing that
> none of us are making perfect decisions all the time. While the
> Discuss Criteria document is very useful, I'd warn against trying to
> codify the proper behaviour too much. It would be very difficult,
> and ultimately it comes down to making a call on whether an issue is
> really crucial for the Internet or not.

> I feel that the discussion and pressure from other ADs and authors
> and the rest of the working group is a more useful avenue to ensure
> that we really are fixing the necessary bugs and only those. And I
> know you are doing that - lets make sure we keep doing it. "If you
> see something, say something". It is everyone's responsibility to
> try to do the right thing, and if you feel it is not happening, say
> so. I think the current IESG has a very good mood for receiving
> feedback and acting on it. (Speaking as the longest serving member
> in the current IESG, who frequently gets shown to be wrong by other
> ADs or WG folk.)

> In addition, as discussed separately, moving more of the issue
> resolution to the open and to the WG is a good thing.

> Jari


From narten@us.ibm.com  Wed May 15 09:27:16 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C4B21F90BB for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 09:27:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hk8WPQv7aRPM for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 09:27:09 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id A6AFC21F8FEC for <ietf@ietf.org>; Wed, 15 May 2013 09:26:55 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 15 May 2013 12:26:46 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 15 May 2013 12:26:43 -0400
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 3BA22C90049 for <ietf@ietf.org>; Wed, 15 May 2013 12:26:42 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4FGQgQ1289866 for <ietf@ietf.org>; Wed, 15 May 2013 12:26:42 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4FGQg0R021809 for <ietf@ietf.org>; Wed, 15 May 2013 13:26:42 -0300
Received: from cichlid.raleigh.ibm.com (sig-9-65-104-101.mts.ibm.com [9.65.104.101]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4FGQb7J021281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2013 13:26:38 -0300
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r4FGPhvZ012163; Wed, 15 May 2013 18:25:45 +0200
Message-Id: <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
In-reply-to: <518435D5.5040601@isdg.net>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net>
Comments: In-reply-to Hector Santos <hsantos@isdg.net> message dated "Fri, 03 May 2013 18:10:29 -0400."
Date: Wed, 15 May 2013 18:25:43 +0200
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13051516-5806-0000-0000-0000212B18BC
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, 15 May 2013 16:27:16 -0000

I don't think the IETF needs to be in the profile/resume
business. There are plenty of other places that do a fine job already.

What I do think the IETF should do is *require* that participants
identify themselves. That means knowing who they are (a name and email
contact) and an affiliation. For 80% of the participants, this info is
not very hard to figure out (see below). But we also have participants
that use obscure email handles that don't correlate to anything
obvious, whether a real person or to a name in the list of registered
attendees, etc. I suspect these folk are *not* intenending to be
anonymous participants, but in practice they are.

And yes, knowing who someone is, their background and who they work
for is important to me in figuring out how to guage their input. E.g.,
I would likely pay more attention to an operator's comments on a
proposed use case than from someone else.

How to figure out who someone is:

1) look at the list of registered attendees. (but that doesn't include
email addresses, so no clean way to map attendee name into email
addresses being used).

Also, for some reason, some people who register don't bother giving an
affiliation. In some cases this is intentional, but there are others
where it doesn't make sense (e.g., someone who has worked for the same
employer for 10+ years and is still working for that employer).

E.g., if you look at the registration list for Orland0, fully 180 names
don't list affiliations -- and there are a number pretty obvious
surprises in that list...

2) look at email addresses. But nowadays they are often generic (e.g.,
gmail) and don't correlate back to an obvious sponsor.

3) Google names, look at authorship info in RFCs, linked in,
etc. Works in a lot of cases, but is sometimes more work than seems
appropriate. And for those with less history in the IETF, knowing
where to look for this stuff is trickier.

But even doing the above, there are people participating (e.g.,
posting on the IETF list) who I don't know who they are, even after
spending some time trying to figure who who they are and what their
background is. For an open standards organization, that somehow
doesn't seem quite right.

Thomas




From touch@isi.edu  Wed May 15 09:37:38 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 625B921F9017 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 09:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.805
X-Spam-Level: 
X-Spam-Status: No, score=-103.805 tagged_above=-999 required=5 tests=[AWL=-1.206, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZF1yRXbI3Hlk for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 09:37:25 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id AB4A121F9003 for <ietf@ietf.org>; Wed, 15 May 2013 09:37:25 -0700 (PDT)
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 r4FGb13m016042 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 09:37:01 -0700 (PDT)
Message-ID: <5193B9A6.6000008@isi.edu>
Date: Wed, 15 May 2013 09:36:54 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Keith Moore <moore@network-heretics.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 16:37:38 -0000

On 5/15/2013 7:55 AM, Ted Lemon wrote:
> On May 15, 2013, at 10:41 AM, Keith Moore <moore@network-heretics.com> wrote:
>>> The motivation for a particular feature of a protocol is not
>>> clearenough. At the IESG review stage, protocols should not be blocked
>>> because they provide capabilities beyond what seems necessary to acquit
>>> their responsibilities.
>>
>> I strongly disagree with what the NON-DISCUSS criteria say.
>> DISCUSS isn't just for blocking documents. And document quality is
>> as important (in the sense that poor document quality can lead to
>> as many interoperability or other problems) as technical
>> correctness.
>
> The interpretation of this particular NON-DISCUSS criterion that Joe
> has given is simply wrong. The key word to pay attention to to see the
> error is "motivation." The point of this criterion is to eliminate a
> very specific sort of stall that has been known to happen in the past:
> the stall where the AD doesn't understand why the document is being put
> forward at all, and therefore blocks the document until the authors
> explain the motivation behind the document to the satisfaction of the AD
> who is holding the DISCUSS.

I'm impressed that you have such a specific interpretation that this
criteria refers to the entire document, even when it talks about the
"feature of a protocol".

So now we're supposed to accept your interpretation of this rather than 
the explicit text?

> This is a real issue that has created real problems in the past, and
> that is why it is in the NON-DISCUSS criteria.   But this criterion
> _does not_ mean that a criticism that the document itself is unclear
> is not a valid reason to hold a DISCUSS on it.

Agreed - this does not refer to the document. It refers to a specific 
feature of a protocol.

> In fact, it's an
> excellent reason to hold a DISCUSS on it.   A lack of clarity in a
> document can result in it being implemented incorrectly, or in the
> case of a BCP, interpreted incorrectly.

I agree that THESE are good reasons for a DISCUSS, but simply not being 
clear is NOT.

> Or in extreme cases, not
> read at all.

There's nothing you can do about that; RFCs are not read all the time.

Joe


From Ted.Lemon@nominum.com  Wed May 15 10:15:33 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F31321F8539 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 10:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.581
X-Spam-Level: 
X-Spam-Status: No, score=-106.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hp4LpSfIau6y for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 10:15:26 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 034EF21F84F2 for <ietf@ietf.org>; Wed, 15 May 2013 10:15:25 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUZPCrfR0goIVD25gCZgejuTjx7bXp6W5@postini.com; Wed, 15 May 2013 10:15:26 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 724F01B80B1 for <ietf@ietf.org>; Wed, 15 May 2013 10:15:25 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 67C6B19005D; Wed, 15 May 2013 10:15:25 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 15 May 2013 10:15:25 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgIAABRkAgABrMACAAKN7gIAAAI4AgAAD8YCAABxFAIAACsIA
Date: Wed, 15 May 2013 17:15:24 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519CD44@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <5193B9A6.6000008@isi.edu>
In-Reply-To: <5193B9A6.6000008@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <77DD88F56DFC8745945E14A53018EADC@nominum.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: Wed, 15 May 2013 17:15:33 -0000

On May 15, 2013, at 12:36 PM, Joe Touch <touch@isi.edu> wrote:
> I'm impressed that you have such a specific interpretation that this
> criteria refers to the entire document, even when it talks about the
> "feature of a protocol".

"The motivation for a feature of a protocol is not clear enough."   What's =
ambiguous or subject to interpretation about that?   The commentary exactly=
 echoes what I said.   This does not mean that all lacks of clarity are not=
 DISCUSS criteria: only that a lack of clarity with respect to motivation i=
s not.


From touch@isi.edu  Wed May 15 10:24:36 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD11E21F8F4A for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 10:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.741
X-Spam-Level: 
X-Spam-Status: No, score=-103.741 tagged_above=-999 required=5 tests=[AWL=-1.142, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMihwQpLMlUh for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 10:24:31 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 8931821F9092 for <ietf@ietf.org>; Wed, 15 May 2013 10:24:26 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4FHNjt9017670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 10:23:46 -0700 (PDT)
Message-ID: <5193C4A1.40505@isi.edu>
Date: Wed, 15 May 2013 10:23:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <5193B9A6.6000008@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519CD44@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519CD44@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Keith Moore <moore@network-heretics.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 17:24:36 -0000

On 5/15/2013 10:15 AM, Ted Lemon wrote:
> On May 15, 2013, at 12:36 PM, Joe Touch <touch@isi.edu> wrote:
>> I'm impressed that you have such a specific interpretation that this
>> criteria refers to the entire document, even when it talks about the
>> "feature of a protocol".
>
> "The motivation for a feature of a protocol is not clear enough."
> What's ambiguous or subject to interpretation about that? The commentary
> exactly echoes what I said. This does not mean that all lacks of clarity
> are not DISCUSS criteria: only that a lack of clarity with respect to
> motivation is not.

And yet that is the precise issue of your pending DISCUSS on my current 
document.

You don't agree that the motivation for the difference between using 
16-bit vs. 32-bit ExIDs is sufficient, even though that is already 
discussed in the document.

Joe

From sm@resistor.net  Wed May 15 10:37:19 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4B621F91BF for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 10:37:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.103
X-Spam-Level: 
X-Spam-Status: No, score=-102.103 tagged_above=-999 required=5 tests=[AWL=0.496, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CgCRhFmo21p0 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 10:37:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C19CB21F91BC for <ietf@ietf.org>; Wed, 15 May 2013 10:37:17 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4FHawvQ009251; Wed, 15 May 2013 10:37:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1368639425; bh=io13TsaLP11cqu7S3Xys8zKtFVqoNurRkLIX7F2PpKo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BvPGyV7DdTNpylaCmYAtcqOoulby1pbdZDc4VjAL5Plr3O40cXuyZtUTixrSNryoi XvauCHwD90gXRXiS0c0nxUQKBrdx7QgbvOwG/fnIQs9ct5r25klSGi0Q7zkq808HyT hG3JvRgFjw+SFKAP3SdZqULym1Rsp6UrfpE+oWvI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1368639425; i=@resistor.net; bh=io13TsaLP11cqu7S3Xys8zKtFVqoNurRkLIX7F2PpKo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=L8+PoKzbhtMne5Zo8k8I8UrB9KDJpaMnQyHV+BbFZtf5G504hPZ9ocFCOUrY3OmmH eSxyv3xsItcG3b/BH1tFuoc53debVcHyzpvpjufcbQ+m1sP91csudS3f3vZy+6a3T2 lNq8FuydukkFmcBH7w0aYW3GumkP034vUmHrSpyU=
Message-Id: <6.2.5.6.2.20130515090956.0c4009a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 15 May 2013 10:32:12 -0700
To: Keith Moore <moore@network-heretics.com>, Joe Touch <touch@isi.edu>, Yoav Nir <ynir@checkpoint.com>
From: SM <sm@resistor.net>
Subject: Re: call for ideas: tail-heavy IETF process
In-Reply-To: <1F717CBE-ADD9-4BD5-B0A7-4E5B5D26CD13@network-heretics.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <1F717CBE-ADD9-4BD5-B0A7-4E5B5D26CD13@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: Wed, 15 May 2013 17:37:19 -0000

At 08:06 15-05-2013, Keith Moore wrote:
>IMO, IESG should have grounds to reject any document that isn't 
>specifically authorized in a WG's charter.

I read a few charters:

core:
   Dec 2099 - HOLD (date TBD) Constrained security bootstrapping specification
               submitted to IESG
ancp:
   Sep 2010 - Access Node Control Protocol (ANCP) Last Call
   Dec 2010 - ANCP MIB Last Call
   Dec 2010 - ANCP Multicast Extensions last call
   Jan 2011 - ANCP applicability to PON last call
   Mar 2011 - Re-charter or conclude Working Group

6man:
  Jan 2008 - Submit PPP Compression Negotiation specification to IESG as a
             Proposed Standard
  Mar 2008 - Determine way forward for ULA-C specification

l2tpext:
   Mar 2008 - Submit Internet-Draft of PPP over L2TPv3 to IESG
   Done     - WG Last Call on TDM over L2TPv3
   Jun 2008 - WG Last Call on IP over L2TPv3

drinks:
   Apr 2012 - Request publication of SPPP over SOAP Document
   Apr 2012 - Request publication of Framework Document

straw:
   Nov 2011 - Specification for a SIP overload control mechanism based on
              implicit/explicit feedback to IESG for publication as 
Proposed Standard
   Feb 2012 - Specification for a SIP load filtering mechaism to IESG 
for publication
              as Proposed Standard
idr:
   Mar 2010 - Solicit work items for scalability improvements
   Aug 2010 - Submit AS-wide Unique BGP Identifier for BGP-4 to IESG 
as a Proposed Standard
   Aug 2010 - Submit Dynamic Capability for BGP-4 to IESG as a 
Proposed Standard
   Aug 2010 - Submit ASpath ORF draft to IESG as a Proposed Standard
   Aug 2010 - Submit MIB v2 for BGP-4 to IESG as a Proposed Standard
   Nov 2010 - Submit BGP Support for Four-octet AS Number Space 
(revised version) to
              IESG as a Proposed Standard
   Nov 2010 - Submit Revisions to the BGP 'Minimum Route 
Advertisement Interval' to
              IESG as a Proposed Standard
   Nov 2010 - Submit Advertisement of Multiple Paths in BGP to IESG 
as a Proposed Standard
   Nov 2010 - Submit BGP Link Bandwidth Extended Community to IESG as 
a Proposed Standard
   Nov 2010 - Submit Advertisement of the best external route in BGP to IESG as
               a Proposed Standard
   Dec 2010 - Submit Multisession BGP to IESG as a Proposed Standard
   Dec 2010 - Submit Error Handling for Optional Transitive BGP Attributes to
              IESG as a Proposed Standard
   Dec 2010 - Submit ASpath ORF to IESG as a Proposed Standard
   Dec 2010 - Revise WG charter

pim:
   Aug 2011 - First WG version of udated RFC 4601
   Aug 2011 - Submit a more reliable PIM solution (refresh reduction) 
to the IESG
   Nov 2011 - Submit a population count extension to PIM to the IESG
   Dec 2011 - Submit update of RFC 4601 to IESG for advancement to 
Draft Standard

pkix:
   Sep 2007 - Progression of CRMF, CMP, and CMP Transport to DRAFT Standard
   Sep 2007 - Progression of Qualified Certificates Profile RFC to 
DRAFT Standard
   Sep 2007 - Progression of Certificate & CRL Profile RFC to DRAFT Standard
   Sep 2007 - Progression of Time Stamp Protocols RFC to DRAFT Standard
   Sep 2007 - Progression of Logotype RFC to DRAFT Standard
   Nov 2007 - Progression of Proxy Certificate RFC to DRAFT Standard
   Nov 2007 - Progression of Attribute Certificate Profile RFC to 
DRAFT standard
   Feb 2008 - Update to CMC approved as PROPOSED Standard
   Mar 2008 - ECC Algorithms approved as PROPOSED Standard RFC
   Mar 2008 - Progression of CMC RFCs to DRAFT Standard
   Mar 2008 - SCVP approved as PROPOSED Standard RFC

ippm:
   Nov 2010 - Final version of process draft
   Nov 2010 - Implementation report based on process draft
   Mar 2011 - Revise charter

ppsp:
   Dec 2010 - Submit problem statement to IESG as Informational
   Apr 2011 - Submit architectural survey to IESG as Informational
   Apr 2011 - Submit requirements document to IESG as Informational
   Aug 2011 - Submit PPSP peer protocol to IESG as Proposed Standard
   Aug 2011 - Submit PPSP tracker protocol to IESG as Proposed Standard
   Dec 2011 - Submit usage guide to IESG to IESG as Informational

I did not verify whether the drafts mentioned about left the working 
group or not.  The IESG would be rejecting a lot of documents if it 
looked into what was authorized by the charter.

At 08:33 15-05-2013, Yoav Nir wrote:
>Why? There's definitely a process failure there, and it should be 
>blamed on the WG chairs and/or the AD, who should have either moved 
>the work out of the working group or worked on updating the charter.

There would be a lot of WG chairs and/or ADs to blame as there are 
dates up to five years in the past in the charter extracts mentioned above.

At 07:25 15-05-2013, Joe Touch wrote:
>Well, there are IESG members who stand their ground even when it's 
>incorrect, such as:
>
>         - claiming that determining WG consensus is up to the AD,
>         then repeatedly demanding evidence of that consensus

If there was WG consensus it shouldn't be much of a problem to 
provide evidence.  I read a write-up recently where "strong 
consensus" is mentioned.  I took a quick look at the mailing list 
archives and I saw the WGLC message; the next message about the draft 
was the AD review.

Regards,
-sm 


From Ted.Lemon@nominum.com  Wed May 15 11:08:39 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAB6521F8FB6 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 11:08:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.582
X-Spam-Level: 
X-Spam-Status: No, score=-106.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UBFmLRdVBynt for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 11:08:34 -0700 (PDT)
Received: from exprod7og127.obsmtp.com (exprod7og127.obsmtp.com [64.18.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 2006921F8FA5 for <ietf@ietf.org>; Wed, 15 May 2013 11:08:34 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob127.postini.com ([64.18.6.12]) with SMTP ID DSNKUZPPIeZ+W3KgLWdg17cyq13IDMg2LAHz@postini.com; Wed, 15 May 2013 11:08:34 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7A1331B80D2 for <ietf@ietf.org>; Wed, 15 May 2013 11:08:33 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 7133F19005D; Wed, 15 May 2013 11:08:33 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 15 May 2013 11:08:33 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgIAABRkAgABrMACAAKN7gIAAAI4AgAAD8YCAABxFAIAACsIAgAACVYCAAAyCgA==
Date: Wed, 15 May 2013 18:08:32 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519CEE0@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <5193B9A6.6000008@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519CD44@mbx-01.win.nominum.com> <5193C4A1.40505@isi.edu>
In-Reply-To: <5193C4A1.40505@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <4314D65DD7DC6A4799A358FE261DA858@nominum.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: Wed, 15 May 2013 18:08:40 -0000

On May 15, 2013, at 1:23 PM, Joe Touch <touch@isi.edu> wrote:
> You don't agree that the motivation for the difference between using 16-b=
it vs. 32-bit ExIDs is sufficient, even though that is already discussed in=
 the document.

I don't think this is a topic that the IETF as a whole is likely to find ve=
ry interesting.   However, if anyone is curious, they are welcome to read t=
he DISCUSS here and see if they agree with your characterization of my ques=
tion: http://datatracker.ietf.org/doc/draft-ietf-tcpm-experimental-options/=
ballot/

For those who may be interested, the last sentence of the first paragraph i=
s the motivation for this being a DISCUSS position (as opposed to a comment=
).


From john-ietf@jck.com  Wed May 15 11:38:36 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E8CD21F8AD5 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 11:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eV2Dh2FvcWcK for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 11:38:30 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5A621F88EA for <ietf@ietf.org>; Wed, 15 May 2013 11:38:30 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ucgap-000Ome-LF; Wed, 15 May 2013 14:38:27 -0400
Date: Wed, 15 May 2013 14:38:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF	process]
Message-ID: <DF2FFC421E5CBA9C13EB6C76@JcK-HP8200.jck.com>
In-Reply-To: <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net> <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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, 15 May 2013 18:38:36 -0000

--On Wednesday, May 15, 2013 18:25 +0200 Thomas Narten
<narten@us.ibm.com> wrote:

> I don't think the IETF needs to be in the profile/resume
> business. There are plenty of other places that do a fine job
> already.
> 
> What I do think the IETF should do is *require* that
> participants identify themselves. That means knowing who they
> are (a name and email contact) and an affiliation. For 80% of
> the participants, this info is not very hard to figure out
> (see below). But we also have participants that use obscure
> email handles that don't correlate to anything obvious,
> whether a real person or to a name in the list of registered
> attendees, etc. I suspect these folk are *not* intenending to
> be anonymous participants, but in practice they are.

Thomas, 

I completely agree, but..

> Also, for some reason, some people who register don't bother
> giving an affiliation. In some cases this is intentional, but
> there are others where it doesn't make sense (e.g., someone
> who has worked for the same employer for 10+ years and is
> still working for that employer).
> 
> E.g., if you look at the registration list for Orland0, fully
> 180 names don't list affiliations -- and there are a number
> pretty obvious surprises in that list...

Ok.  I'm probably one of the 180, although I would be surprised
if I were one of the "obvious surprises".  I had a corporate
affiliation until somewhat over a decade ago and showed that
affiliation when asked for it on registration, IAB and IESG
mini-biographies, etc.  Since then, I have been an independent
consultant.  I don't consider the way my business is organized,
whether it has other employees or not, etc., to be any of the
IETF's business.  In order to respond to an implied part of your
question, in that last decade or so, I have never been paid by a
client to attend IETF or to represent that client's interests.
That has been largely by choice and driven by a desire to stay
absolutely independent.   I have accepted travel money and
waivers of registration fees on a few (very few) occasions, but
never, in my post-corporate life, compensation for my time spent
of IETF.

So, what would you have me (and others like me) put on
registration forms so that I'm not part of that undifferentiated
"180 names"?  I objected several years ago to the Secretariat
listing me as "Independent" because I know of multiple
organizations/ enterprises with "Independent" in their names
(including, apparently, six separate ones with second-level
domain names in six popular gTLDs I checked).  You tell me how
to fill in that form a way that doesn't misrepresent my
situation or disclose information that is irrelevant to the IETF
and I will happily do it.  Up through the last IETF meeting, I
could most closely approximate that condition by leaving the
information box blank.

To pursue this a tad further, for the purposes for which you
want affiliations, someone who is legally a consultant or
independent contractor rather than an employee but who is being
paid by a firm to attend IETF may have no less obligation to
consider the interests of that firm in their IETF actions than
you have to IBM.  They might even have more of an obligation.
If you want affiliation information in the interest of openness
--and, again, I think that would be a really good idea-- than
such a person is not "independent" or representing only
themselves.   If we are trying to determinate affiliation to
evaluate positions, he or she is definitely affiliated with that
firm and should be listing it (ideally as "consultant to..." or
"contractor to...").

On of the other side of that coin, in prior professional lives,
I've been in situations in which an employer or research sponsor
has essentially said "you are welcome to attend IETF as long as
you can show (in a way that will satisfy auditors) that you did
so entirely on your own time, with no portion of your salary
during that time or your expenses attributable to the company.
In most cases, that person is as independent of company control
over positions taken as I am -- far more so than a consultant
who is being paid to represent a company at IETF or to come to
IETF in order to advise the company on IETF strategy.  She may
even be constrained to not mention the company's name in
conjunction with IETF efforts for fear that mention will be
taken as endorsement.   What would you like to see on the
registration form?

Finally, do any of the answers change if the consultant or
contractor either is employed directly by a consulting firm that
pays a salary or is an individual but more organized as a
business than I have chosen to be? Is the affiliation you want
the name of the nominal employer of the organizational identity
of whomever is really paying the bills and/or calling the tune?

Relative to overall IETF participation, all of the above may be
edge cases.  For reasons similar to those of the "diversity"
debates, I have no way to guess how many there actually are in
the registrant or participant communities.  But, if one were to
look only at present and past WG Chairs, document authors, and
IAB and IESG members, I wouldn't be surprised to find that
people in those ambiguous situations were somewhat
overrepresented.

I think it is all very well to ask for affiliations in principle
and, also in principle, I agree that it is a good idea.  But, in
practice, I think there are a lot of clarifications and other
changes that would be required and that might or might not be
practical.  

 best,
   john


From touch@isi.edu  Wed May 15 11:48:46 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3283821F8F4A for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 11:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.632
X-Spam-Level: 
X-Spam-Status: No, score=-103.632 tagged_above=-999 required=5 tests=[AWL=-1.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9UtGQxlgWPpM for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 11:48:41 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 8491D21F8F0E for <ietf@ietf.org>; Wed, 15 May 2013 11:48:41 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4FImMp5014332 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 11:48:22 -0700 (PDT)
Message-ID: <5193D875.9070908@isi.edu>
Date: Wed, 15 May 2013 11:48:21 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <5193B9A6.6000008@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519CD44@mbx-01.win.nominum.com> <5193C4A1.40505@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519CEE0@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B63077519CEE0@mbx-01.win.nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: Keith Moore <moore@network-heretics.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 18:48:46 -0000

On 5/15/2013 11:08 AM, Ted Lemon wrote:
> On May 15, 2013, at 1:23 PM, Joe Touch <touch@isi.edu> wrote:
>> You don't agree that the motivation for the difference between using 16-bit vs. 32-bit ExIDs is sufficient, even though that is already discussed in the document.
>
> I don't think this is a topic that the IETF as a whole is likely to
> find very interesting. However, if anyone is curious, they are welcome
> to read the DISCUSS here and see if they agree with your
> characterization of my question:
> http://datatracker.ietf.org/doc/draft-ietf-tcpm-experimental-options/ballot/
>
> For those who may be interested, the last sentence of the first
> paragraph is the motivation for this being a DISCUSS position (as
> opposed to a comment).

Which is "I think that using a 4-byte ExID runs a real risk of
overflowing the available space in the TCP header in real-world 
circumstances."

Except that the document already describes the ExID as either 16-bit or 
32-bit:

    >> All ExIDs MUST be either 16-bits or 32-bits long.

Motivation for the additional two bytes is already explained in the 
document in several places, notably:

    The second two bytes serve as a "magic number".
...
    Using the additional magic number bytes helps the option contents
    have the same byte alignment in the TCP header as they would have if
    (or when) a conventional (non-experiment) TCP option codepoint is
    assigned. Use of the same alignment reduces the potential for
    implementation errors, especially in using the same word-alignment
    padding, if the same software is later modified to use a
    conventional codepoint. Use of the longer, 32-bit ExID further
    decreases the probability of such a false positive compared to those
    using shorter, 16-bit ExIDs.
...
    Use of the longer, 32-bit ExID consumes more
    space, but provides more protection against false positives.

Which is why I feel this motivation isn't sufficient for a DISCUSS.

I'd be glad to hear others' view of this as well.

Joe




From moore@network-heretics.com  Wed May 15 12:36:03 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD72321F871C for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 12:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.766
X-Spam-Level: 
X-Spam-Status: No, score=-3.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fnyOgxr2tiZU for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 12:35:59 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 38C0A21F8717 for <ietf@ietf.org>; Wed, 15 May 2013 12:35:58 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 23C6A208E2; Wed, 15 May 2013 15:35:57 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 15 May 2013 15:35:57 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=MZSfRdG/fmqXPqRRzvP0zh Vwh28=; b=Ys0AzfzOAUbUorhVv8YycUnIvaFQpJZRwu01BebLe2YWzcvSqCfiFr 0rFabbx3X59fULe7//56/bIgWV0BzYlVpDExVW4LmijMY4hAdALN6zLtD66670Jp pOUevgezKZtkfIVzqAu1U5bTsTDYCsBFj988nBll5W1sXnv88xe74=
X-Sasl-enc: zGcSJFMvsI+dnGXwGGRVBM7R5DHgY/0g4XDxJU+iZXO7 1368646556
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 3A23D200193; Wed, 15 May 2013 15:35:56 -0400 (EDT)
Message-ID: <5193E398.9080905@network-heretics.com>
Date: Wed, 15 May 2013 15:35:52 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <5193B9A6.6000008@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519CD44@mbx-01.win.nominum.com> <5193C4A1.40505@isi.edu> <8D23D4052ABE7A4490E77B1A012B63077519CEE0@mbx-01.win.nominum.com> <5193D875.9070908@isi.edu>
In-Reply-To: <5193D875.9070908@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 19:36:03 -0000

On 05/15/2013 02:48 PM, Joe Touch wrote:
>
>
> On 5/15/2013 11:08 AM, Ted Lemon wrote:
>> I don't think this is a topic that the IETF as a whole is likely to
>> find very interesting. However, if anyone is curious, they are welcome
>> to read the DISCUSS here and see if they agree with your
>> characterization of my question:
>> http://datatracker.ietf.org/doc/draft-ietf-tcpm-experimental-options/ballot/ 
>>
>>
>> For those who may be interested, the last sentence of the first
>> paragraph is the motivation for this being a DISCUSS position (as
>> opposed to a comment).
>
> Which is "I think that using a 4-byte ExID runs a real risk of
> overflowing the available space in the TCP header in real-world 
> circumstances."
>
> Except that the document already describes the ExID as either 16-bit 
> or 32-bit:
>
>    >> All ExIDs MUST be either 16-bits or 32-bits long.
>
> Motivation for the additional two bytes is already explained in the 
> document in several places, notably:
>
>    The second two bytes serve as a "magic number".
> ...
>    Using the additional magic number bytes helps the option contents
>    have the same byte alignment in the TCP header as they would have if
>    (or when) a conventional (non-experiment) TCP option codepoint is
>    assigned. Use of the same alignment reduces the potential for
>    implementation errors, especially in using the same word-alignment
>    padding, if the same software is later modified to use a
>    conventional codepoint. Use of the longer, 32-bit ExID further
>    decreases the probability of such a false positive compared to those
>    using shorter, 16-bit ExIDs.
> ...
>    Use of the longer, 32-bit ExID consumes more
>    space, but provides more protection against false positives.
>
> Which is why I feel this motivation isn't sufficient for a DISCUSS.

It certainly seems like a valid topic for an AD to want to discuss with 
a WG.    And that's all that DISCUSS inherently means.

Keith



From moore@network-heretics.com  Wed May 15 13:24:29 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25FE621F86CE for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.742
X-Spam-Level: 
X-Spam-Status: No, score=-3.742 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpI+5e8Dj4WI for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:24:24 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 04DA021F84D9 for <ietf@ietf.org>; Wed, 15 May 2013 13:24:23 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 5FDDE20835; Wed, 15 May 2013 16:24:23 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Wed, 15 May 2013 16:24:23 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=JB4qeBZNh+Q9YX4ftshSwt QkWcU=; b=RkzlhOc4spcs3v7VjypcxvA4vnPeQc7qsMMPDHpvzv3TOMDoBQilSX eDiJqhFxyKqj4pm0Y4b5jUmEVkLbkjdww3XgHx0kixwfzFZcIpZIKevb+vO0q4tq BuEikS5Jep81ushS0nT7Q6LSOrNlp1Ir7skjDosVRtQtbRYOtqIE0=
X-Sasl-enc: J/kOKcL8fT+16aBQ7+FMnw3tF9+G5+eCzyaRhzHjQ+NO 1368649462
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 9B1BA20016D; Wed, 15 May 2013 16:24:22 -0400 (EDT)
Message-ID: <5193EEF2.4050601@network-heretics.com>
Date: Wed, 15 May 2013 16:24:18 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <8D23D4052ABE7A4490E77B1A012B63077519C8C6@mbx-01.win.nominum.com> <1F717CBE-ADD9-4BD5-B0A7-4E5B5D26CD13@network-heretics.com> <F49C3B7A-355A-42D1-BAE9-F0FAD5641EBE@checkpoint.com>
In-Reply-To: <F49C3B7A-355A-42D1-BAE9-F0FAD5641EBE@checkpoint.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: Wed, 15 May 2013 20:24:29 -0000

On 05/15/2013 11:33 AM, Yoav Nir wrote:
> On May 15, 2013, at 6:06 PM, Keith Moore <moore@network-heretics.com>
>   wrote:
>
>> IMO, IESG should have grounds to reject any document that isn't specifically authorized in a WG's charter.
>>
>> - Keith
>>
> Why? There's definitely a process failure there, and it should be blamed on the WG chairs and/or the AD, who should have either moved the work out of the working group or worked on updating the charter.

ADs shouldn't have to micro-manage the WGs and keep track of whether 
every single document that a WG is working on is authorized by its 
charter.  Fundamentally, it's the WG chair's job to stay within the charter.

What I was addressing with my above statement is that there seems to be 
a presumption on the part of some people that a WG can produce anything 
it wants, and that the IESG is under an obligation to approve such work 
unless it can object on some very specific grounds.    I can understand 
something resembling such a presumption for work that the WG is 
specifically chartered to do.   We don't want WGs investing their 
members' time and energy to produce something that will never see the 
light of day, and WG members need some assurance that their efforts are 
likely to bear fruit at least as far as publication is concerned.   But 
I see no reason that a WG should be able to presume that the IESG should 
ultimately accept something that they weren't specifically chartered to 
do in the first place.

Though probably a better remedy than to reject the document outright, 
would be for IESG to treat such documents as individual submissions.

Keith


From worley@shell01.TheWorld.com  Wed May 15 13:26:08 2013
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 715F921F86DD for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bpXU9XrmPLh for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:26:02 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 88B4A21F86CE for <ietf@ietf.org>; Wed, 15 May 2013 13:26:02 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r4FKPEv3029493 for <ietf@ietf.org>; Wed, 15 May 2013 16:25:16 -0400
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 r4FKPESY4816618 for <ietf@ietf.org>; Wed, 15 May 2013 16:25:14 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r4FKPDN64789169; Wed, 15 May 2013 16:25:13 -0400 (EDT)
Date: Wed, 15 May 2013 16:25:13 -0400 (EDT)
Message-Id: <201305152025.r4FKPDN64789169@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <51938724.2050704@connotech.com> (thierry.moreau@connotech.com)
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net>	<201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <alpine.DEB.2.00.1305150758460.24367@uplift.swm.pp.se> <51938724.2050704@connotech.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, 15 May 2013 20:26:08 -0000

> From: Thierry Moreau <thierry.moreau@connotech.com>
> 
> Some sections of the IETF would be more vendor-heavy, e.g. the routing 
> area. In those sections, only a serious economic study might tell to 
> which extent the "patent pool" (wikipedia is your friend) excludes the 
> permissionless inventor in those IETF sections.

My impression of the presentation is that it does not focus on
innovation that is part of, and extends, an existing technological
area, but rather innovation that uses existing technology as a
"platform" upon which to build new technology.  This sort of
innovation is less vulnerable to attack via patents, but it is
vulnerable to service providers that can differentially price the use
of the platform within the new application. 

Dale

From worley@shell01.TheWorld.com  Wed May 15 13:26:11 2013
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 5EB0211E80D9 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lxynZ9BAvXw for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:26:05 -0700 (PDT)
Received: from TheWorld.com (pcls4.std.com [192.74.137.144]) by ietfa.amsl.com (Postfix) with ESMTP id 772B221F86D8 for <ietf@ietf.org>; Wed, 15 May 2013 13:26:05 -0700 (PDT)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r4FKPXjS026541 for <ietf@ietf.org>; Wed, 15 May 2013 16:25:35 -0400
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 r4FKPWnx4812748 for <ietf@ietf.org>; Wed, 15 May 2013 16:25:33 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r4FKPWie4817365; Wed, 15 May 2013 16:25:32 -0400 (EDT)
Date: Wed, 15 May 2013 16:25:32 -0400 (EDT)
Message-Id: <201305152025.r4FKPWie4817365@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <20130514213225.GD17491@mx1.yitter.info> (ajs@anvilwalrusden.com)
Subject: Re: article on innovation and open standards
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <20130514213225.GD17491@mx1.yitter.info>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 20:26:11 -0000

> From: Andrew Sullivan <ajs@anvilwalrusden.com>
> 
> > The critical difference is that the IETF is an organization of
> > *buyers* rather than an organization of *sellers*.
> 
> Without wishing to be nasty, I will point out that we have way more
> vendors than operators participating in our standards development.

That is actually what I mean...  By "sellers" I mean "sellers of
telecommunications services".  The equipment vendors generally favor
the interests of the "buyers of telecommunications services", who are
their customers.

Dale

From adrian@olddog.co.uk  Wed May 15 13:30:44 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753EE21F86F4 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level: 
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxNHGmy0VBSZ for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:30:31 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id AADB921F86CE for <ietf@ietf.org>; Wed, 15 May 2013 13:30:30 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4FKUTFK002174 for <ietf@ietf.org>; Wed, 15 May 2013 21:30:29 +0100
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 r4FKUSoT002164 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 15 May 2013 21:30:28 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Date: Wed, 15 May 2013 21:30:26 +0100
Message-ID: <00c301ce51ab$090b8350$1b2289f0$@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: Ac5RqwcXD+o+sMzvQcOh0KzSI1C9fQ==
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: Wed, 15 May 2013 20:30:44 -0000

The claim (or one of the claims) is that some ADs may place Discusses that are
intended to raise a discussion with the authors/WG that could equally have been
raised with a Comment or through direct email. This, it is claimed, may
unnecessarily delay the document from completing the publication process.

Now the dangerous bit,

Suppose the AD raised her concern by writing a Comment or sending an email and
balloting "No Objection." That would mean that the I-D would be approved for
publication.

At this point either:
- the discussion goes on, but the document becomes an RFC anyway
or
- the responsible AD holds the document pending satisfactory completion of the
discussion.

I suggest that the former is a bad result. Not that the authors/WG will ignore
the discussion, but if they disagree on something the AD considers very
important, the authors/WG have no incentive to participate in the discussion. Of
course, all participants in this thread so far would never behave like that, but
there is a possibility that this will happen for some authors.

I also suggest that the latter introduces exactly the same amount of delay as
the Discuss.

Personally (but this may reflect my Discusses) I find that an active engagement
by the authors and the Discussing AD on the issue and the potential resolution,
always leads to speedy progression of the document either with the AD feeling
stupid, or the document improved. Both are adequate results.

Adrian



From Ted.Lemon@nominum.com  Wed May 15 13:39:17 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99AFE21F871C for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:39:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.584
X-Spam-Level: 
X-Spam-Status: No, score=-106.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0c7CQk5xIsf for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:39:11 -0700 (PDT)
Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by ietfa.amsl.com (Postfix) with ESMTP id DB53521F8709 for <ietf@ietf.org>; Wed, 15 May 2013 13:39:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUZPyatyHu9mhlcdFrXryO6QFUOlvhnVK@postini.com; Wed, 15 May 2013 13:39:10 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 02AB71B818A for <ietf@ietf.org>; Wed, 15 May 2013 13:39:06 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F0A1219005D; Wed, 15 May 2013 13:39:05 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 15 May 2013 13:39:05 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: Ac5RqwcXD+o+sMzvQcOh0KzSI1C9fQAO+LiA
Date: Wed, 15 May 2013 20:39:05 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519D506@mbx-01.win.nominum.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>
In-Reply-To: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <52457C873ED4CE4B93B61F22245C705A@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 20:39:17 -0000

On May 15, 2013, at 4:30 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> I suggest that the former is a bad result. Not that the authors/WG will i=
gnore
> the discussion, but if they disagree on something the AD considers very
> important, the authors/WG have no incentive to participate in the discuss=
ion. Of
> course, all participants in this thread so far would never behave like th=
at, but
> there is a possibility that this will happen for some authors.

This can also happen purely by accident=97it need not involve malice on any=
one's part.


From touch@isi.edu  Wed May 15 13:51:56 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5DB21F9023 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:51:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.585
X-Spam-Level: 
X-Spam-Status: No, score=-105.585 tagged_above=-999 required=5 tests=[AWL=1.014, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kw3MQT-5a22J for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 13:51:50 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8638221F869F for <ietf@ietf.org>; Wed, 15 May 2013 13:51:50 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4FKnh6H020458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 May 2013 13:49:43 -0700 (PDT)
Message-ID: <5193F4E6.4050407@isi.edu>
Date: Wed, 15 May 2013 13:49:42 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <A584852E-C7B0-4533-B4FC-C173A9BD06D3@gmail.com>
In-Reply-To: <A584852E-C7B0-4533-B4FC-C173A9BD06D3@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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, 15 May 2013 20:51:56 -0000

On 5/15/2013 7:49 AM, Ralph Droms wrote:
>> >The DISCUSS isn't there to make documents "better" - that's for COMMENTs. A DISCUSS there to catch a set of problems and to*block*  the document's progress until that problem is resolved.

> I'll agree with you *if*  you consider an unclear description of a
> feature of a protocol, severe enough that reader of the specification
> are not able to build interoperable implementations, as a problem for
> which a DISCUSS can be posted.
>
> In my opinion, there are many ways in which document can be unclear
> beyond the "motivation for a particular feature of a protocol is not
> clear enough."
>
> - Ralph

Absolutely. Note that issues interfering with interoperability or 
correctness are among the explicit DISCUSS criteria.

Joe



From agmalis@gmail.com  Wed May 15 14:24:53 2013
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 A0FF411E80D2 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 14:24:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OwiftjjOW5+h for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 14:24:52 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8F511E80AD for <ietf@ietf.org>; Wed, 15 May 2013 14:24:52 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id p57so679351wes.32 for <ietf@ietf.org>; Wed, 15 May 2013 14:24:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=0LGraryCXiDcDxIhQWLCPtiJCmKbvXu+2f0fATa4MUE=; b=J8aL7jnCGcsX6peqsvysYPywMb0z/o3v/tta7dW3DKYGwP1UCmhZPn0SacaU21KsFR Ke6nNt1LL1VqWYnWTXarzVNte0Hg34fWGd7ww744XFNZRsdejnyzfP9/ZAW5zkgmEoT1 E1vQtlsEQqtxMNpjF6gpbJv0OEr1CJHBeyQ77vYrLkMHJNJLIlDmy5Fw2VsPoACK2JAg P/vXIde4O6ZivSeFDAFdGTGf9wJzXyccvWYxEOQOf/SRLG9HtXPy+M6WsKtzj0S4FSwF 47R36/A0djHX2rTnceNJHZIifGda9pbq20ab1JhpJZh1XmApqkrPNK1aUF2CMlLHuMzX sC3g==
X-Received: by 10.180.185.179 with SMTP id fd19mr18222218wic.1.1368653091511;  Wed, 15 May 2013 14:24:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.217.79.138 with HTTP; Wed, 15 May 2013 14:24:31 -0700 (PDT)
In-Reply-To: <001801ce4d56$53084460$4001a8c0@gateway.2wire.net>
References: <55D046F8-5DD2-42E8-9B8C-36C612C4B3F8@ietf.org> <50992BEF.9000803@gmail.com> <C66E7DEF-EEE8-4678-91C1-1FD46854312C@vigilsec.com> <00b301cdbd2c$6ec30e20$4001a8c0@gateway.2wire.net> <014d01ce4c13$7d9c2dc0$4001a8c0@gateway.2wire.net> <201305081937.r48JbjTQ4388434@shell01.TheWorld.com> <001801ce4d56$53084460$4001a8c0@gateway.2wire.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 15 May 2013 17:24:31 -0400
Message-ID: <CAA=duU2B7rk9jabz84YoiixqK3wGsb-+4JwSwhgfigtru7ectA@mail.gmail.com>
Subject: Re: Accessing tools from IETF pages
To: "t.p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=001a11c25e4c5722ea04dcc8610d
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, 15 May 2013 21:24:53 -0000

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

Tom,

There's a "compatibility view" button in recent versions of IE that I've
found helps with some websites. See
http://windows.microsoft.com/en-us/internet-explorer/products/ie-9/features/compatibility-view.
You can also find it in the Tools menu.

Cheers,
Andy



On Fri, May 10, 2013 at 4:13 AM, t.p. <daedulus@btconnect.com> wrote:

>
> Tom Petch
>
> ----- Original Message -----
> From: "Dale R. Worley" <worley@ariadne.com>
> To: "t.p." <daedulus@btconnect.com>
> Cc: <ietf@ietf.org>
> Sent: Wednesday, May 08, 2013 8:37 PM
> Subject: Re: Accessing tools from IETF pages
>
>
> > > From: "t.p." <daedulus@btconnect.com>
> > >
> > > I wanted to submit an I-D so I wanted to access the tools, as I have
> > > done before, so I clicked on 'IETF Tools' from
> > > http://datatracker.ietf.org/wg/
> > > and when that failed tried again with 'Tools Team Pages' from
> > > http://www.ietf.org/iesg/
> > > with the same result.  Can anyone else get to tools from that link?
> > >
> > > It resolves to
> > > http://tools.ietf.org/
> > > which Internet Explorer (what else?) assures me cannot be displayed,
> > > either from the link or from typing it into the Open drop down.
> >
> > Well, all three of those links work for me at "May 8 19:33:01 UTC
> > 2013" using Firefox 18.0.2 on Linux.  (For whatever that is worth.)
> >
> > I'd sniff the HTTP transaction to get some information on the specific
> > failure mode.
>
> Dale
>
> Many thanks for that; if others can get to it, then that resolves my
> issue, I can always  go via other means, until I get myself a trace and
> see what is really going on.
>
> Tom Petch
>
> > Dale
> >
>
>
>

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

<div dir=3D"ltr"><div><div><div>Tom,<br></div><br></div>There&#39;s a &quot=
;compatibility view&quot; button in recent versions of IE that I&#39;ve fou=
nd helps with some websites. See <a href=3D"http://windows.microsoft.com/en=
-us/internet-explorer/products/ie-9/features/compatibility-view">http://win=
dows.microsoft.com/en-us/internet-explorer/products/ie-9/features/compatibi=
lity-view</a> . You can also find it in the Tools menu.<br>

<br>Cheers,<br></div>Andy<br><br></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Fri, May 10, 2013 at 4:13 AM, t.p. <span dir=
=3D"ltr">&lt;<a href=3D"mailto:daedulus@btconnect.com" target=3D"_blank">da=
edulus@btconnect.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
Tom Petch<br>
<div><div class=3D"h5"><br>
----- Original Message -----<br>
From: &quot;Dale R. Worley&quot; &lt;<a href=3D"mailto:worley@ariadne.com">=
worley@ariadne.com</a>&gt;<br>
To: &quot;t.p.&quot; &lt;<a href=3D"mailto:daedulus@btconnect.com">daedulus=
@btconnect.com</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
Sent: Wednesday, May 08, 2013 8:37 PM<br>
Subject: Re: Accessing tools from IETF pages<br>
<br>
<br>
&gt; &gt; From: &quot;t.p.&quot; &lt;<a href=3D"mailto:daedulus@btconnect.c=
om">daedulus@btconnect.com</a>&gt;<br>
&gt; &gt;<br>
&gt; &gt; I wanted to submit an I-D so I wanted to access the tools, as I h=
ave<br>
&gt; &gt; done before, so I clicked on &#39;IETF Tools&#39; from<br>
&gt; &gt; <a href=3D"http://datatracker.ietf.org/wg/" target=3D"_blank">htt=
p://datatracker.ietf.org/wg/</a><br>
&gt; &gt; and when that failed tried again with &#39;Tools Team Pages&#39; =
from<br>
&gt; &gt; <a href=3D"http://www.ietf.org/iesg/" target=3D"_blank">http://ww=
w.ietf.org/iesg/</a><br>
&gt; &gt; with the same result. =A0Can anyone else get to tools from that l=
ink?<br>
&gt; &gt;<br>
&gt; &gt; It resolves to<br>
&gt; &gt; <a href=3D"http://tools.ietf.org/" target=3D"_blank">http://tools=
.ietf.org/</a><br>
&gt; &gt; which Internet Explorer (what else?) assures me cannot be display=
ed,<br>
&gt; &gt; either from the link or from typing it into the Open drop down.<b=
r>
&gt;<br>
&gt; Well, all three of those links work for me at &quot;May 8 19:33:01 UTC=
<br>
&gt; 2013&quot; using Firefox 18.0.2 on Linux. =A0(For whatever that is wor=
th.)<br>
&gt;<br>
&gt; I&#39;d sniff the HTTP transaction to get some information on the spec=
ific<br>
&gt; failure mode.<br>
<br>
Dale<br>
<br>
</div></div>Many thanks for that; if others can get to it, then that resolv=
es my<br>
issue, I can always =A0go via other means, until I get myself a trace and<b=
r>
see what is really going on.<br>
<br>
Tom Petch<br>
<br>
&gt; Dale<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div>

--001a11c25e4c5722ea04dcc8610d--

From doug@ewellic.org  Wed May 15 14:28:40 2013
Return-Path: <doug@ewellic.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 1539911E80DE for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 14:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHQwfIDJjc3z for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 14:28:34 -0700 (PDT)
Received: from p3plwbeout03-05.prod.phx3.secureserver.net (p3plsmtp03-05-2.prod.phx3.secureserver.net [72.167.218.217]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1F111E80AD for <ietf@ietf.org>; Wed, 15 May 2013 14:28:31 -0700 (PDT)
Received: from localhost ([72.167.218.245]) by p3plwbeout03-05.prod.phx3.secureserver.net with bizsmtp id cMUW1l0015JG3DC01MUWKv; Wed, 15 May 2013 14:28:30 -0700
X-SID: cMUW1l0015JG3DC01
Received: (qmail 13910 invoked by uid 99); 15 May 2013 21:28:30 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.190
User-Agent: Workspace Webmail 5.6.38
Message-Id: <20130515142829.665a7a7059d7ee80bb4d670165c8327d.05d5be4788.wbe@email03.secureserver.net>
From: "Doug Ewell" <doug@ewellic.org>
To: ietf@ietf.org
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
Date: Wed, 15 May 2013 14:28:29 -0700
Mime-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 21:28:40 -0000

John C Klensin <john dash ietf at jck dot com> wrote:=0A=0A> I think it is =
all very well to ask for affiliations in principle=0A> and, also in princip=
le, I agree that it is a good idea. But, in=0A> practice, I think there are=
 a lot of clarifications and other=0A> changes that would be required and t=
hat might or might not be=0A> practical. =0A=0AI used the term "Consultant"=
 in RFCs 4645 and 5645, instead of revealing=0Athe name of my company (whic=
h was different each time, and neither of=0Awhich contributed any time or m=
oney to my WG effort). I did this because=0Athe WG at the time included a m=
alicious contributor who had already=0Acontacted the HR department of anoth=
er contributor's employer, asking=0Athem to professionally discipline the e=
mployee, because he had supported=0Aan RFC 3683 PR-action against the first=
 contributor. Full disclosure can=0Abe a dangerous thing.=0A=0A--=0ADoug Ew=
ell | Thornton, CO, USA=0Ahttp://ewellic.org | @DougEwell =C2=AD=0A

From peter@akayla.com  Wed May 15 14:35:33 2013
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0D111E80D9; Wed, 15 May 2013 14:35:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v1JVuPxcMBQs; Wed, 15 May 2013 14:35:28 -0700 (PDT)
Received: from m1plsmtpa01-03.prod.mesa1.secureserver.net (m1plsmtpa01-03.prod.mesa1.secureserver.net [64.202.165.4]) by ietfa.amsl.com (Postfix) with ESMTP id 88C5911E80D2; Wed, 15 May 2013 14:35:28 -0700 (PDT)
Received: from [172.16.6.97] ([12.104.232.101]) by m1plsmtpa01-03.prod.mesa1.secureserver.net with  id cMbD1l00G2BvQwk01MbFNJ; Wed, 15 May 2013 14:35:21 -0700
User-Agent: Microsoft-MacOutlook/14.3.2.130206
Date: Wed, 15 May 2013 14:36:50 -0700
Subject: Gen-ART Telechat review of draft-ietf-netmod-ip-cfg-09
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-netmod-ip-cfg.all@tools.ietf.org>
Message-ID: <CDB94C58.457F%peter@akayla.com>
Thread-Topic: Gen-ART Telechat review of draft-ietf-netmod-ip-cfg-09
In-Reply-To: <05fd01ce4890$45f5cbf0$d1e163d0$@akayla.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: gen-art@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 21:35:34 -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.


This draft has not been updated since my Last Call review, so the
information below remains unchanged.

Document: draft-ietf-netmod-ip-cfg-09
Reviewer: Peter Yee
Review Date: May-03-2013
IETF LC End Date: May-03-2013
IESG Telechat date: May-16-2013

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

The abstract says it pretty well: This document defines a YANG data model
for management of IP implementations.

Major issues:

Minor issues:

Nits:

Page 7, bottom: The code copyright date says 2012.  Update it to 2013.

Page 10, in leaf phys-address, the description has an incorrect spelling of
"neighbor".

General: where a description of phys-address is given, in both cases it
says
"The physical level address...".  It might be more correct to state "The
link layer address..." for most but not all cases.

That's it.  Everything appears consistent within the limits of my
understanding of YANG.

		-Peter Yee



From l.wood@surrey.ac.uk  Wed May 15 15:35:28 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BB0A21F89D5 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 15:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oi7fowv3UBCD for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 15:35:24 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.107]) by ietfa.amsl.com (Postfix) with ESMTP id 3BCA811E80D3 for <ietf@ietf.org>; Wed, 15 May 2013 15:35:21 -0700 (PDT)
Received: from [193.109.255.147:15544] by server-3.bemta-14.messagelabs.com id 30/C2-06484-8AD04915; Wed, 15 May 2013 22:35:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-72.messagelabs.com!1368657320!10910317!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27480 invoked from network); 15 May 2013 22:35:20 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-16.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 15 May 2013 22:35:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 15 May 2013 23:35:19 +0100
From: <l.wood@surrey.ac.uk>
To: <doug@ewellic.org>, <ietf@ietf.org>
Date: Wed, 15 May 2013 23:35:18 +0100
Subject: RE: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF	process]
Thread-Topic: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF	process]
Thread-Index: Ac5RszpvvHJglmUrSXqR8ZcC4+SGKwAB3WKb
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E88@EXMB01CMS.surrey.ac.uk>
References: <20130515142829.665a7a7059d7ee80bb4d670165c8327d.05d5be4788.wbe@email03.secureserver.net>
In-Reply-To: <20130515142829.665a7a7059d7ee80bb4d670165c8327d.05d5be4788.wbe@email03.secureserver.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 22:35:28 -0000

You want resumes? You've got linkedin for that.

The sort of thing Doug describes is actually quite common.

For example, I once had a group chair threaten to have me disciplined by th=
e company
I worked for, for pointing out the technical failings of his pet protocol.

The IETF isn't a lovey-dovey bunch of hippies working in harmony for humani=
ty.
The IETF is hardball.

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Doug Ewell=
 [doug@ewellic.org]
Sent: 15 May 2013 22:28
To: ietf@ietf.org
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IE=
TF   process]

John C Klensin <john dash ietf at jck dot com> wrote:

> I think it is all very well to ask for affiliations in principle
> and, also in principle, I agree that it is a good idea. But, in
> practice, I think there are a lot of clarifications and other
> changes that would be required and that might or might not be
> practical.

I used the term "Consultant" in RFCs 4645 and 5645, instead of revealing
the name of my company (which was different each time, and neither of
which contributed any time or money to my WG effort). I did this because
the WG at the time included a malicious contributor who had already
contacted the HR department of another contributor's employer, asking
them to professionally discipline the employee, because he had supported
an RFC 3683 PR-action against the first contributor. Full disclosure can
be a dangerous thing.

--
Doug Ewell | Thornton, CO, USA
http://ewellic.org | @DougEwell =AD


From narten@us.ibm.com  Wed May 15 15:40:07 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E41821F842B for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 15:40:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psPRqgBdjivR for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 15:40:02 -0700 (PDT)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 9895921F842E for <ietf@ietf.org>; Wed, 15 May 2013 15:40:01 -0700 (PDT)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Wed, 15 May 2013 18:40:00 -0400
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 15 May 2013 18:39:59 -0400
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 6B23BC90041 for <ietf@ietf.org>; Wed, 15 May 2013 18:39:58 -0400 (EDT)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4FMdwFQ45875342 for <ietf@ietf.org>; Wed, 15 May 2013 18:39:58 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4FMdwwD027449 for <ietf@ietf.org>; Wed, 15 May 2013 18:39:58 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-76-69-59.mts.ibm.com [9.76.69.59]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4FMdswf027205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 May 2013 18:39:57 -0400
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r4FMdp6b003172; Thu, 16 May 2013 00:39:53 +0200
Message-Id: <201305152239.r4FMdp6b003172@cichlid.raleigh.ibm.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
In-reply-to: <DF2FFC421E5CBA9C13EB6C76@JcK-HP8200.jck.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net> <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com> <DF2FFC421E5CBA9C13EB6C76@JcK-HP8200.jck.com>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Wed, 15 May 2013 14:38:13 -0400."
Date: Thu, 16 May 2013 00:39:50 +0200
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13051522-5806-0000-0000-0000212CB24E
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, 15 May 2013 22:40:07 -0000

Hi John.

I agree there are a number of specific cases where there is no
simple/obvious way to handle. I'd be OK with something fairly simple
as "unaffiliated" or "consultant" or something more nuanced. But I'd
like to think those are edge cases (but could of course be wrong in
how common they are). I was specifically thinking of much more obvious
cases where I'm pretty sure that their main employers is sending them.

One thing I've done at times is look at the attendance figures at
meetings to try to identify some of the entities that send the most
attendees to meetings (e.g.,, to track trends). As a result of that,
I've noticed that the number of "no affiliation given" seems high to
me, and I've seen obvious cases where I know the person and where they
were working in the past, and then when I check later, it turns out
they are still working at the same place (e.g. a Cisco, Google or
Huawei). Maybe its just the case that the registration form makes it
to easy to leave it blank.

Just loooking at the list
https://www.ietf.org/registration/ietf86/attendance.py?sortkey=3&login=
I easily counted 20 names of folk I know that don't list an
affiliation, where if any of them have changed employers, that number
would likely be very small.

Thomas


From stephen.farrell@cs.tcd.ie  Wed May 15 16:33:58 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A812311E80D9 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 16:33:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x9kusPfrYMpU for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 16:33:52 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id C4D7C11E80D3 for <ietf@ietf.org>; Wed, 15 May 2013 16:33:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F0631BE80; Thu, 16 May 2013 00:33:24 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0leqjA-GBj7R; Thu, 16 May 2013 00:33:24 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.45.60.184]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 174A5BE7D; Thu, 16 May 2013 00:33:24 +0100 (IST)
Message-ID: <51941B43.5000105@cs.tcd.ie>
Date: Thu, 16 May 2013 00:33:23 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net> <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com> <DF2FFC421E5CBA9C13EB6C76@JcK-HP8200.jck.com>
In-Reply-To: <DF2FFC421E5CBA9C13EB6C76@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 23:33:58 -0000

On 05/15/2013 07:38 PM, John C Klensin wrote:
> So, what would you have me (and others like me) put on
> registration forms so that I'm not part of that undifferentiated
> "180 names"? 

How about 7 densely worded paragraphs?

Sorry, couldn't resist:-)

S.


From farmer@umn.edu  Wed May 15 16:51:10 2013
Return-Path: <farmer@umn.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 5FBA321F871D for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 16:51:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mS8pty2-CbIi for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 16:51:03 -0700 (PDT)
Received: from vs-m.tc.umn.edu (vs-m.tc.umn.edu [134.84.135.97]) by ietfa.amsl.com (Postfix) with ESMTP id 0B98621F86F5 for <ietf@ietf.org>; Wed, 15 May 2013 16:51:02 -0700 (PDT)
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) by vs-m.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Wed, 15 May 2013 18:50:51 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f178.google.com [209.85.223.178] #+LO+TR
X-Umn-Classification: local
Received: by mail-ie0-f178.google.com with SMTP id b11so4943100iee.23 for <ietf@ietf.org>; Wed, 15 May 2013 16:50:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-received:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding:x-gm-message-state; bh=+55oFwdBUoFKiMMcYet2Ae9hHDSquW/aSi8JVyPTyY8=; b=LQnWxRc0qUSI0vCZz1NYquPURVfSW0GLAl6BRnj92IGRD/nPrN5CVnZjvi7aqJPj+d 0GAQ9acV3T9GmPWlZaQr9J8QeHyH/SKe2O6uwvkXCHvlzbasTH5b5bNdjxY1jSrgil+L 9TrPowLU1z/qfYC1bWn2poRRvryWhicUm36C7mpmpbiraNhJlmovC50PVUBiQQ30QSvG 6/Fj04/ZykIE6QoKEJEFwHXGRYiMs0fdmtWTufCAmqn9dZXMC13G8LgIpVfXA2V30fKG 3VY+HE+K4lG9mC+OcRvsOWeH00I4sU6YkHvhJYQ2zlF9TCp+kBHje8qrdvleqlj0nyGj biig==
X-Received: by 10.50.16.36 with SMTP id c4mr7241490igd.60.1368661851438; Wed, 15 May 2013 16:50:51 -0700 (PDT)
X-Received: by 10.50.16.36 with SMTP id c4mr7241486igd.60.1368661851376; Wed, 15 May 2013 16:50:51 -0700 (PDT)
Received: from x-128-101-233-13.uofm-secure.wireless.umn.edu (x-128-101-233-13.uofm-secure.wireless.umn.edu. [128.101.233.13]) by mx.google.com with ESMTPSA id b6sm283701igv.5.2013.05.15.16.50.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 15 May 2013 16:50:50 -0700 (PDT)
Message-ID: <51941F5F.7060201@umn.edu>
Date: Wed, 15 May 2013 18:50:55 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org>
In-Reply-To: <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQlPx6iE2HjKWf+UPrE2gxJBnNC5QCCplvb+k/i+riAoUEGsmw5tZlv6jERFpetV5jzQvfUvJnSAGBtYcIDlqktlU4+Ej3ze/Ci3YER76S732tngarh+nMsq9FHkHxhjjIjXpSbN
Cc: ietf@ietf.org, SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 May 2013 23:51:10 -0000

On 5/14/13 13:32 , David Conrad wrote:
> Hi,
>
> On May 14, 2013, at 11:02 AM, David Farmer <farmer@umn.edu> wrote:
>> The third goal you refer to focuses on the need for "accurate registration information ... in order to meet a variety of operational requirements."  I believe this to be a valid technical concerns of the IETF, it is difficult to imagine how a global Internet can technically function without this.  So, I think it is important for it to remain in the draft.
>
> I would also point out that the third goal makes no statement on whether the registration data is publicly available or not.
>
>> However, issues of privacy, law enforcement access, and a myriad of other extremely important issues related to the Internet Numbers Registry System are outside the technical and operational scope of the IETF.  The whole point of the draft is to document the issues that are properly the concern of the IETF towards the Internet Numbers Registry System and to pass the rest of it to the multi-stakeholder environment of ICANN and the RIRs to hash it out.
>
> Exactly. Section 4 notes that provision of "public WHOIS" has been a technical consideration and that "it may be necessary for the Internet community to examine these and related technical and operational considerations and how best to meet them."

I agree with everything you say above regarding public available of the 
registration data.  However, at the same time Section 7, quoted below, 
makes a very strong argument for it to remain public.

"It is generally recognized that accuracy and public availability of 
Internet registry data is often an essential component in researching 
and resolving security and operational issues on the Internet."

So lets play a little hypothetical here;  What if an RIR or ICANN 
through a global policy decided Whois Data no longer should be public 
for overriding privacy reasons.  My read of Section 5, is that would be 
proper path for such a change, and long as the technical guidance of the 
IETF is considered in the process.  But then through RFC 2860 and 
Section 5, if the IETF objected on technical or architectural grounds, 
and formally through the IESG, then the IAB would essentially adjudicate 
the issue.  And ICANN or the RIR are obligated to accept the decision of 
the IAB.  Do I have that right?

To be clear, I'm not advocating Whois should or shouldn't remain public, 
or that anything is wrong with the Section 5.  This just seemed like a 
plausible hypothetical to explore how the puzzle pieces work together to 
make the Internet Numbers Registry System.  Also, I just want to fully 
understand what Section 5 really means.

Thanks.

-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

From aeopare@gmail.com  Wed May 15 17:14:14 2013
Return-Path: <aeopare@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E394811E80E3 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 17:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u8vlTzbz88rw for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 17:14:09 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id C71CD11E80D3 for <ietf@ietf.org>; Wed, 15 May 2013 17:14:09 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id i4so2989740oah.35 for <ietf@ietf.org>; Wed, 15 May 2013 17:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CXkpqlWDIHtA2laIMP+otBOKQFlGJhso7qnP9G1dSXc=; b=Jl4li+rgAD0FhtK/Q63KC0ueBVOPzrXzQk88B0vqww797IlBlel6QINhBN4ijRWaLl YwyuNLWrfqy2tHlbPG2GmCyA+snBRkAPvyPA7vg8VlH3tjNxolwgG3vpAwR2gletjSSM BLEYHigmqWH4uWZcmmQqNvpZhhra1y3zDph5BKLlwy68NP6HwUZAlYrtPQv3Fyzc7Awf ufbgtyeqJICeK1ki12PQPBoAADBhVNNVUZP4YtsshJeuJn4Y5/MHWA9IkshZaDQbKJT9 SDQsi7XUudyw2ixoxZRAE4IFmAAwm4yhDK6d2GFnv5CIf5jHzFYw6sGz0LxaXU2IVYgE sjaA==
MIME-Version: 1.0
X-Received: by 10.182.33.40 with SMTP id o8mr18452244obi.39.1368663249333; Wed, 15 May 2013 17:14:09 -0700 (PDT)
Received: by 10.60.36.231 with HTTP; Wed, 15 May 2013 17:14:09 -0700 (PDT)
In-Reply-To: <51941B43.5000105@cs.tcd.ie>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net> <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com> <DF2FFC421E5CBA9C13EB6C76@JcK-HP8200.jck.com> <51941B43.5000105@cs.tcd.ie>
Date: Thu, 16 May 2013 00:14:09 +0000
Message-ID: <CANeGSFnF+rOJzvtrD65iaaSK8p9_rpKoQzQuD3zLJ+iYaJzn-Q@mail.gmail.com>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
From: "Edwin A. Opare" <aeopare@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=089e01161b5ccb827d04dccabef5
Cc: John C Klensin <john-ietf@jck.com>, Thomas Narten <narten@us.ibm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 00:14:15 -0000

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

In all earnestness I don't think a resume will be necessary at all :).

--
Regards,

Edwin A. Opare



On Wed, May 15, 2013 at 11:33 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie
> wrote:

>
>
> On 05/15/2013 07:38 PM, John C Klensin wrote:
> > So, what would you have me (and others like me) put on
> > registration forms so that I'm not part of that undifferentiated
> > "180 names"?
>
> How about 7 densely worded paragraphs?
>
> Sorry, couldn't resist:-)
>
> S.
>
>

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

<div dir=3D"ltr">In all earnestness I don&#39;t think a resume will be nece=
ssary at all :).<div><div class=3D"gmail_extra"><br clear=3D"all"><div>--<b=
r>Regards,<br><br>Edwin A. Opare<br></div><div><br></div>
<br><br><div class=3D"gmail_quote">On Wed, May 15, 2013 at 11:33 PM, Stephe=
n 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><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<div class=3D"im"><br>
<br>
On 05/15/2013 07:38 PM, John C Klensin wrote:<br>
&gt; So, what would you have me (and others like me) put on<br>
&gt; registration forms so that I&#39;m not part of that undifferentiated<b=
r>
&gt; &quot;180 names&quot;?<br>
<br>
</div>How about 7 densely worded paragraphs?<br>
<br>
Sorry, couldn&#39;t resist:-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
S.<br>
<br>
</font></span></blockquote></div><br></div></div></div>

--089e01161b5ccb827d04dccabef5--

From presnick@qti.qualcomm.com  Wed May 15 18:07:59 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B470911E80E6 for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 18:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.382
X-Spam-Level: 
X-Spam-Status: No, score=-102.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id idBu6WlQZXNe for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 18:07:55 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC3211E80D7 for <ietf@ietf.org>; Wed, 15 May 2013 18:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1368666475; x=1400202475; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=9QN6a18xOuI+PiEcFz/6K9DeNstpqqkKS5ItSrOWOsI=; b=dprF34UTfmNsB0bJy0u0vqjLMEAQI7sgi3J4d2pHFUxqLzplaMWMSNKP eimcpy1Ow1zJZGIyJJGJ1n7fiy42fBHje4BWcz7dFJ7KdokMPweFm56Kb c1GBEfj8RrZK6GnOxWjpSrBpnPKtFBpg9MVJMdUEWA2+ZzjGeMzyIA5vA g=;
X-IronPort-AV: E=Sophos;i="4.87,681,1363158000"; d="scan'208";a="40126933"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 15 May 2013 18:07:54 -0700
X-IronPort-AV: E=Sophos;i="4.87,681,1363158000"; d="scan'208";a="448751713"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 15 May 2013 18:07:54 -0700
Received: from elliots-iphone.wlan.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.4; Wed, 15 May 2013 18:07:54 -0700
Message-ID: <51943168.6050908@qti.qualcomm.com>
Date: Wed, 15 May 2013 18:07:52 -0700
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: Keith Moore <moore@network-heretics.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com>	<51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu>	<5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu>	<5192B415.50006@joelhalpern.com>	<8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com>	<5192BB1C.3000902@dcrocker.net>	<51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com>
In-Reply-To: <51939EA0.9070704@network-heretics.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 01:07:59 -0000

I initially replied to address Keith's comment. But a few things on Joe's:

On 5/15/13 7:41 AM, Keith Moore wrote:
> On 05/15/2013 10:39 AM, Joe Touch wrote:
>> On 5/14/2013 9:54 PM, Keith Moore wrote:
>>> Publishing broken or unclear documents is not progress.
>>
>> Broken, agreed.
>>
>> Unclear, nope - please review the NON-DISCUSS criteria, notably:
>>
>> The motivation for a particular feature of a protocol is not clear 
>> enough. At the IESG review stage, protocols should not be blocked 
>> because they provide capabilities beyond what seems necessary to 
>> acquit their responsibilities.
>>
>> The DISCUSS isn't there to make documents "better" - that's for COMMENTs.

Exactly right. Sometimes we forget; it's a good thing to remind us.

>> A DISCUSS there to catch a set of problems and to *block* the 
>> document's progress until that problem is resolved.

Mostly correct. However:

- If there is only one AD who wishes to DISCUSS and no other AD agrees 
with the DISCUSS holder, at the next telechat the document is unblocked. 
(See <http://www.ietf.org/iesg/voting-procedures.html>.)
- Even if others agree with the DISCUSS, the chair can be asked to use 
the alternate procedure, which requires 2/3 of non-recused ADs to agree 
to publication.

Which is to say, if there is only a single AD "blocking" a document, 
that block is essentially a 2 week affair if you are willing to push the 
point. No need for negotiating; if the WG decides that the AD is totally 
off base, tell your sponsoring AD that you're waiting the two weeks. 
People (unfortunately IMO) don't push the point nearly enough.

(For the record, the IESG has *never* used the latter of the two 
procedures.)

That said, I am also of the view that there is a third way, but I have 
never seen a WG attempt it:

DISCUSS should in fact require discussing. Assuming there was some good 
faith effort on the part of the WG to figure out what the AD was on 
about and they really assess that the AD has it wrong, a WG could say, 
"Sorry, we got this right. You are confused (or wrong). We are not 
changing the document. We are done discussing." At that point, I am of 
the opinion that the AD cannot hold the DISCUSS any longer. The AD must 
move to ABSTAIN. The discussion is, for all intents and purposes, over 
and to continue to DISCUSS is (IMO) an appealable offense. Then it is a 
matter of the IESG deciding whether there are enough ADs supporting the 
document (YES or NO OBJECTION) to count as consensus of the IESG. We 
ostensibly use 2/3 of non-recused ADs to mean "consensus", since (I 
think the theory goes) if you can't get 2/3 of ADs to agree that it's OK 
to publish a document, that is a sign of a lack of rough consensus in 
the IETF (and probably a serious problem in WG operation). Indeed, if 
the ADs are so off of their rockers that more than 1/3 of them are 
against a perfectly reasonable document, it's time for the appeals and 
recall procedures to be used.

(This is, BTW, where I disagree with Dave Crocker: Yes, a DISCUSS can be 
used as an exercise in authority, but only if it is allowed to be an 
"assertion that changes are being required". If the rest of the IETF 
started saying, "Sorry, no change is going to be made" instead of making 
changes simply to satisfy the AD, we'd actually be better off and the 
DISCUSS would stop being seen -- and used -- as authoritative.)

Finally, do keep in mind that, although there have been times where the 
numbers have been much different, currently there are 16 documents with 
outstanding DISCUSSes (and I think the total number has been pretty 
stable for a while), and 7 of those are on tomorrow's telechat and 
therefore should hopefully be cleared within a few days of when the 
document could most quickly have been approved anyway. So I'm not sure 
(and we should look at the statistics) how much of a problem this is for 
most documents we are producing.

Now, as to Keith's comments:

> I strongly disagree with what the NON-DISCUSS criteria say. DISCUSS 
> isn't just for blocking documents.   And document quality is as 
> important (in the sense that poor document quality can lead to as many 
> interoperability or other problems) as technical correctness.
>
> Why are people trying to sabotage IESG?

I'm sorry Keith, but your last line is rubbish. To claim that what 
people in this thread are talking about amounts to an attempt to 
sabotage the IESG is the height of hubris. In my opinion, the IESG has 2 
jobs as far as document review goes: (1) Check for serious technical 
problems that the WG might not have considered and make sure they get 
considered; and (2) Make sure that our processes have been followed to 
assure that the WG products are truly the product of (IETF-wide) 
consensus and fit within the policies of the IETF. I am *positive* that 
I have failed to limit my DISCUSSes on documents to one of those two 
reasons; I expect I will err and do so in the future. I should be 
corrected. We reject kings, and should.

As for the rest: The IESG should be looking for technical correctness 
problems and identify those that do not appear to have been properly 
considered by the WG, but trying to police document quality beyond that, 
including all of those listed in the NON-DISCUSS criteria, really are 
out of bounds for the IESG to be concerning themselves with. Sure, there 
are issues of clarity that can result in interoperability problems, but 
every one of those I have seen is because the words written can be read 
in a technically incorrect way. My take is you are solidly in the rough 
on the question of the DISCUSS/NON-DISCUSS criteria.

  Our documents are never going to be perfect and attempts to make them 
so actually lessen the quality of our output over the long term.

pr

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


From moore@network-heretics.com  Wed May 15 21:55:57 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD7521F8F2E for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 21:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.724
X-Spam-Level: 
X-Spam-Status: No, score=-3.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57TdsPCtNZHD for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 21:55:53 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1E98A21F8F15 for <ietf@ietf.org>; Wed, 15 May 2013 21:55:52 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C056020668; Thu, 16 May 2013 00:55:48 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Thu, 16 May 2013 00:55:48 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=jMpnAi/Ocsyx4/ieEyoIcw AraUQ=; b=dR3gyikB6IL2AAebh+j2R4ALPowyq1v5tcJwOC8guPXMJ0Vnj8R9ZI daKIAHHh5Zi9fQBgqidwMK6Rj1izTUzDl572oaGBStufB4qSUyQm+EbadL91f/TX hyrfdPk+W+QbSRDKeH6JfFw3SZC3DNLv8dO2SRFYd3d8t4BlDAGoA=
X-Sasl-enc: MeW7i+8saLyyyKR+fioz+sZoDj8Q9TPXwSIdkwmHInyx 1368680147
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 611F9C80007; Thu, 16 May 2013 00:55:47 -0400 (EDT)
Message-ID: <519466CD.9010508@network-heretics.com>
Date: Thu, 16 May 2013 00:55:41 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com>	<8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com>	<C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com>	<51929A21.8030105@gmail.com> <5192A282.7060409@isi.edu>	<5192A5B6.3000205@cs.tcd.ie> <5192A8DB.7030207@isi.edu>	<5192B415.50006@joelhalpern.com>	<8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com>	<5192BB1C.3000902@dcrocker.net>	<51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <51943168.6050908@qti.qualcomm.com>
In-Reply-To: <51943168.6050908@qti.qualcomm.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, 16 May 2013 04:55:57 -0000

On 05/15/2013 09:07 PM, Pete Resnick wrote:
> I initially replied to address Keith's comment. But a few things on 
> Joe's:
>
> On 5/15/13 7:41 AM, Keith Moore wrote:
>> On 05/15/2013 10:39 AM, Joe Touch wrote:
>>> On 5/14/2013 9:54 PM, Keith Moore wrote:
>>>> Publishing broken or unclear documents is not progress.
>>>
>>> Broken, agreed.
>>>
>>> Unclear, nope - please review the NON-DISCUSS criteria, notably:
>>>
>>> The motivation for a particular feature of a protocol is not clear 
>>> enough. At the IESG review stage, protocols should not be blocked 
>>> because they provide capabilities beyond what seems necessary to 
>>> acquit their responsibilities.
>>>
>>> The DISCUSS isn't there to make documents "better" - that's for 
>>> COMMENTs.
>
> Exactly right. Sometimes we forget; it's a good thing to remind us.
>
>>> A DISCUSS there to catch a set of problems and to *block* the 
>>> document's progress until that problem is resolved.
>
> Mostly correct. However:
>
> - If there is only one AD who wishes to DISCUSS and no other AD agrees 
> with the DISCUSS holder, at the next telechat the document is 
> unblocked. (See <http://www.ietf.org/iesg/voting-procedures.html>.)
> - Even if others agree with the DISCUSS, the chair can be asked to use 
> the alternate procedure, which requires 2/3 of non-recused ADs to 
> agree to publication.
>
> Which is to say, if there is only a single AD "blocking" a document, 
> that block is essentially a 2 week affair if you are willing to push 
> the point. No need for negotiating; if the WG decides that the AD is 
> totally off base, tell your sponsoring AD that you're waiting the two 
> weeks. People (unfortunately IMO) don't push the point nearly enough.

I think it's very unfortunate that IESG has adopted rules that work this 
way.   Part of IESG's job is to provide independent review of WG 
output.   It that review can be circumvented merely by waiting two 
weeks, that's a bug in the process.   And if an AD raises a DISCUSS 
about a matter of technical or document quality (or for that matter, 
about a process violation), and the WG isn't even willing to discuss the 
point, but instead relies on the two week timeout, I think that's 
grounds for appeal to the IAB.

> (For the record, the IESG has *never* used the latter of the two 
> procedures.)
>
> That said, I am also of the view that there is a third way, but I have 
> never seen a WG attempt it:
>
> DISCUSS should in fact require discussing. 

We agree on that much.
> Assuming there was some good faith effort on the part of the WG to 
> figure out what the AD was on about and they really assess that the AD 
> has it wrong, a WG could say, "Sorry, we got this right. You are 
> confused (or wrong). We are not changing the document. We are done 
> discussing." At that point, I am of the opinion that the AD cannot 
> hold the DISCUSS any longer. The AD must move to ABSTAIN. 

I disagree with this in the strongest possible terms.  I believe that 
for IESG to have rules that insist on or encourage voting ABSTAIN when 
the AD really means "this document is not acceptable", is both 
irresponsible and dishonest on the IESG's part.  I also believe that it 
tends to mean that ADs who didn't actually review the document get more 
say than ADs who did.   The proper thing to do in that case is for 
either side to appeal to the IAB.

> The discussion is, for all intents and purposes, over and to continue 
> to DISCUSS is (IMO) an appealable offense. Then it is a matter of the 
> IESG deciding whether there are enough ADs supporting the document 
> (YES or NO OBJECTION) to count as consensus of the IESG. We ostensibly 
> use 2/3 of non-recused ADs to mean "consensus", since (I think the 
> theory goes) if you can't get 2/3 of ADs to agree that it's OK to 
> publish a document, that is a sign of a lack of rough consensus in the 
> IETF (and probably a serious problem in WG operation). Indeed, if the 
> ADs are so off of their rockers that more than 1/3 of them are against 
> a perfectly reasonable document, it's time for the appeals and recall 
> procedures to be used.

I don't think IESG voting should be thought of as a consensus process, 
except perhaps in the deadlock breaking procedure.   The typical number 
of reviewers on the IESG is too small for a consensus process to be 
meaningful.   With so few thorough reviewers outside of the WG, you need 
a procedure that at least initially assumes that all review comments 
have to be taken seriously.

> Now, as to Keith's comments:
>
>> I strongly disagree with what the NON-DISCUSS criteria say. DISCUSS 
>> isn't just for blocking documents.   And document quality is as 
>> important (in the sense that poor document quality can lead to as 
>> many interoperability or other problems) as technical correctness.
>>
>> Why are people trying to sabotage IESG?
>
> I'm sorry Keith, but your last line is rubbish. To claim that what 
> people in this thread are talking about amounts to an attempt to 
> sabotage the IESG is the height of hubris. 

"sabotage" is probably not the best word I could have chosen.   But I do 
have the strong impression that people are clamoring for IESG reviews to 
be toothless, and that frustrates me.   Every time I attend an IETF 
meeting and look at what a broad spectrum of WGs are doing, I find that 
most of the ones I see are producing output of very dubious quality.   
While trying to fix this after WGLC almost never works well, the threat 
of IESG rejection of WG documents is one of the few incentives that WGs 
have to actually consider interests outside of their narrow areas.   
External review after a WG has completed its work is absolutely 
essential.   And in our current process, the only even marginally 
effective mechanism that we have for that is IESG review.

I understand that ADs can sometimes be capricious and sometimes simply 
be wrong, and I'm supportive of the idea that there should be some way 
to keep a single AD from holding things up.   But expecting ADs to 
change their reviews just because others don't agree with them is 
completely inappropriate.   So is letting people who didn't thoroughly 
reviewed a document have more sway in the review process than people who 
have reviewed it.

> In my opinion, the IESG has 2 jobs as far as document review goes: (1) 
> Check for serious technical problems that the WG might not have 
> considered and make sure they get considered; and (2) Make sure that 
> our processes have been followed to assure that the WG products are 
> truly the product of (IETF-wide) consensus and fit within the policies 
> of the IETF. I am *positive* that I have failed to limit my DISCUSSes 
> on documents to one of those two reasons; I expect I will err and do 
> so in the future. I should be corrected. We reject kings, and should.

I agree that we should reject kings.   But we should also reject 
stubborn working groups and stubborn authors.   We shouldn't presume 
that a WG knows better than the IESG.  The two have different 
points-of-view, but neither is inherently superior to the other.


>
> As for the rest: The IESG should be looking for technical correctness 
> problems and identify those that do not appear to have been properly 
> considered by the WG, but trying to police document quality beyond 
> that, including all of those listed in the NON-DISCUSS criteria, 
> really are out of bounds for the IESG to be concerning themselves 
> with. Sure, there are issues of clarity that can result in 
> interoperability problems, but every one of those I have seen is 
> because the words written can be read in a technically incorrect way. 

I disagree with this also.   Ambiguities in technical specifications 
that could affect interoperability need to be corrected no matter who 
finds them.   But I've rarely seen significant delays result from fixing 
minor ambiguities here and there.   The bigger delays come from the 
occasional documents that are so poorly written that small changes can't 
clarify them.    Those documents, frankly, need to be rewritten.   
(Perhaps the best thing that IESG could do in such cases is approve such 
documents as Experimental and commission a rewrite with a competent 
technical writer as co-author.)

>
>  Our documents are never going to be perfect and attempts to make them 
> so actually lessen the quality of our output over the long term.
>

I think I understand what you mean, and probably agree.   But the 
problem with stating things in that way is that it can be taken to mean 
that we should just write things as quickly and sloppily as possible.

Keith


From john-ietf@jck.com  Wed May 15 22:08:53 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169CE21F90CC for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 22:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NfrfaKQPtmJQ for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 22:08:47 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3D48A21F90C1 for <ietf@ietf.org>; Wed, 15 May 2013 22:08:47 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UcqQn-000PV2-Bq; Thu, 16 May 2013 01:08:45 -0400
Date: Thu, 16 May 2013 01:08:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: Doug Ewell <doug@ewellic.org>, ietf@ietf.org
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF	process]
Message-ID: <854984CADE6206C4F0C49CFE@JcK-HP8200.jck.com>
In-Reply-To: <20130515142829.665a7a7059d7ee80bb4d670165c8327d.05d5be4788.wbe@email03.secureserver.net>
References: <20130515142829.665a7a7059d7ee80bb4d670165c8327d.05d5be4788.wbe@email03.secureserver.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 05:08:53 -0000

--On Wednesday, May 15, 2013 14:28 -0700 Doug Ewell
<doug@ewellic.org> wrote:

>...
> I did this because
> the WG at the time included a malicious contributor who had
> already contacted the HR department of another contributor's
> employer, asking them to professionally discipline the
> employee, because he had supported an RFC 3683 PR-action
> against the first contributor. Full disclosure can be a
> dangerous thing.

I know that sort of "contact the employer and ask them to chew
out the employee" stuff goes on because I've had it tried on me
at least twice although both involved technical issues and
choices, not, e.g., a PR-action.  In the first instance, the
employer said something about academic freedom and essentially
told the person complaining to kiss off.  In the second, the
employer laughed.  

I may have been luckier in my choices of employers (and clients)
and I know bad stuff happens sometimes, but the sort of case you
outline doesn't seem to me to be a good argument against
disclosure of affiliations.  It seems to me that, very rare edge
cases aside, either:

	(i) Your employer knows what you are doing and saying in
	the IETF, at least to the extent that they care, and
	will back you should such complaints arrive.
	
	(ii) You and your employer have an agreement that you
	participate in the IETF as an independent activity that
	they don't try to control.  Should a complaint arise,
	they presumably tell the complaining party that unless
	your IETF behavior is an embarrassment to the company,
	in which case (iii) applies.
	
	(iii) Your IETF behavior is, as far as your employer is
	concerned, that of a loose cannon.  You regularly work
	against company positions or the company's best
	interests and haven't laid the internal foundation for
	that to be acceptable.  A complaint associated with
	something you have disclosed could get you into big
	trouble, but complaints are equally likely from people
	who know where you are working, disclosure or no, such
	as fellow employees of the same organization.

So I suggest that, if your behavior is proper and above board,
disclosure will rarely create a problem.  If your behavior
isn't, then disclosure may be the least of your difficulties.  

In addition, the IETF may be in need of a mechanism for
documenting and disclosing the identities of anyone who thinks
that complaining to someone's employer about his or her
reasonable behavior at the IETF.  I imagine the community could
figure out appropriate and completely informal ways to
discourage that particular style of trying to influence IETF
decision-making.

best,
    john


From john-ietf@jck.com  Wed May 15 22:45:03 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F046021F909A for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 22:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2a2+4eR0gB+Q for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 22:44:57 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC3F21F9092 for <ietf@ietf.org>; Wed, 15 May 2013 22:44:57 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ucqzk-000PXL-DC; Thu, 16 May 2013 01:44:52 -0400
Date: Thu, 16 May 2013 01:44:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: Keith Moore <moore@network-heretics.com>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: call for ideas: tail-heavy IETF process
Message-ID: <FCA58917A139C84A0F3A462D@JcK-HP8200.jck.com>
In-Reply-To: <519466CD.9010508@network-heretics.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com>	<5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie>	<5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <51943168.6050908@qti.qualcomm.com> <519466CD.9010508@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: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 05:45:03 -0000

--On Thursday, May 16, 2013 00:55 -0400 Keith Moore
<moore@network-heretics.com> wrote:

>> Which is to say, if there is only a single AD "blocking" a
>> document,  that block is essentially a 2 week affair if you
>> are willing to push  the point. No need for negotiating; if
>> the WG decides that the AD is  totally off base, tell your
>> sponsoring AD that you're waiting the two  weeks. People
>> (unfortunately IMO) don't push the point nearly enough.
> 
> I think it's very unfortunate that IESG has adopted rules that
> work this way.   Part of IESG's job is to provide independent
> review of WG output.   It that review can be circumvented
> merely by waiting two weeks, that's a bug in the process.
> And if an AD raises a DISCUSS about a matter of technical or
> document quality (or for that matter, about a process
> violation), and the WG isn't even willing to discuss the
> point, but instead relies on the two week timeout, I think
> that's grounds for appeal to the IAB.

Keith,

I generally agree with Pete although I share your low opinion of
a lot of current IETF work, but your comment above seems to call
for comment from someone, like myself, who has often been
critical of the IESG.  I don't think the current rules are
ideal, but the effect of the ones that you and Pete cite isn't
really that a WG can circumvent a review by waiting two weeks.
First, the dissenting AD has those same two weeks to convince
others on the IESG that his or her position is reasonable or at
least needs more extensive consideration.  If that is possible,
then there is no longer a single AD objecting and the two week
rule does not apply.  If it is not possible, then there is
either something wrong with the objection or the AD making it
and probably it is reasonable for the process to move forward.

Conversely, a WG that decides to avoid actually engaging on an
issue in the hope of letting the two-week clock run out is
putting itself at considerable risk.  The IESG still have the
ability to fire WG leadership and even to close WGs.  Under any
reasonable circumstances, I assume that the IESG would respond
very strongly if an AD pointed out the a WG had ignored an
effort to discuss a substantive issue even if the rest of the
IESG disagreed with that particular AD about that issue.  I
can't remember any instances of a WG Chair being fired, or a WG
being shut down entirely, while documents were post IETF Last
Call and under IESG discussion, but I presume that is because
the IESG has never been provoked quite enough rather than
because there is any rule that would prevent it.  Firing a Chair
or closing a WG on the grounds that they refused to engage on a
substantive issue would, I assume, be sustained on any appeal.

Similarly...
 
> I agree that we should reject kings.   But we should also
> reject stubborn working groups and stubborn authors.   We
> shouldn't presume that a WG knows better than the IESG.  The
> two have different points-of-view, but neither is inherently
> superior to the other.

I don't think we should presume that a WG knows better than the
IESG either.  I do think it is reasonable to assume that a WG
knows better than a single AD who cannot convince others on the
IESG of the merit of his or her position or even that the issue
is important enough that they should read the document carefully
and form their own informed opinions.

    best,
      john


From moore@network-heretics.com  Wed May 15 23:05:26 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9165721F914C for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 23:05:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.71
X-Spam-Level: 
X-Spam-Status: No, score=-3.71 tagged_above=-999 required=5 tests=[AWL=-0.111,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qz+UQ7vBeCRa for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 23:05:21 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 47E7921F9130 for <ietf@ietf.org>; Wed, 15 May 2013 23:05:21 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C46992095E; Thu, 16 May 2013 02:05:19 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Thu, 16 May 2013 02:05:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=JdCJYFQXKKIfgJk+dByB+d N+h70=; b=aASQ3WJh/3mnTdMr+f5w25G4b7w/2WxRbciRk28MVq1avhjvYn4iQE bdyC0GL4fpOIA3qYeDOyWxhD8+qn5c0rs/BDKPO58YM3lqguBzx3i4IPpIbJ8PYH If6Rceut0svu/2w638PnLBUDhI0O9aJVuZZZwzYwIcz4KOFgbXrR8=
X-Sasl-enc: v1w7gKXI8ejgHVvqYpVP9JKKLmKxHE3nmZ7/TaXX+Eus 1368684318
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 14BF6C80007; Thu, 16 May 2013 02:05:17 -0400 (EDT)
Message-ID: <51947718.6050502@network-heretics.com>
Date: Thu, 16 May 2013 02:05:12 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: call for ideas: tail-heavy IETF process
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com>	<5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie>	<5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <51943168.6050908@qti.qualcomm.com> <519466CD.9010508@network-heretics.com> <FCA58917A139C84A0F3A462D@JcK-HP8200.jck.com>
In-Reply-To: <FCA58917A139C84A0F3A462D@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 06:05:26 -0000

On 05/16/2013 01:44 AM, John C Klensin wrote:
>
> --On Thursday, May 16, 2013 00:55 -0400 Keith Moore
> <moore@network-heretics.com> wrote:
>
>>> Which is to say, if there is only a single AD "blocking" a
>>> document,  that block is essentially a 2 week affair if you
>>> are willing to push  the point. No need for negotiating; if
>>> the WG decides that the AD is  totally off base, tell your
>>> sponsoring AD that you're waiting the two  weeks. People
>>> (unfortunately IMO) don't push the point nearly enough.
>> I think it's very unfortunate that IESG has adopted rules that
>> work this way.   Part of IESG's job is to provide independent
>> review of WG output.   It that review can be circumvented
>> merely by waiting two weeks, that's a bug in the process.
>> And if an AD raises a DISCUSS about a matter of technical or
>> document quality (or for that matter, about a process
>> violation), and the WG isn't even willing to discuss the
>> point, but instead relies on the two week timeout, I think
>> that's grounds for appeal to the IAB.
> Keith,
>
> I generally agree with Pete although I share your low opinion of
> a lot of current IETF work, but your comment above seems to call
> for comment from someone, like myself, who has often been
> critical of the IESG.  I don't think the current rules are
> ideal, but the effect of the ones that you and Pete cite isn't
> really that a WG can circumvent a review by waiting two weeks.
> First, the dissenting AD has those same two weeks to convince
> others on the IESG that his or her position is reasonable or at
> least needs more extensive consideration.  If that is possible,
> then there is no longer a single AD objecting and the two week
> rule does not apply.  If it is not possible, then there is
> either something wrong with the objection or the AD making it
> and probably it is reasonable for the process to move forward.

I don't think I agree.   I do agree that a single AD shouldn't be able 
to indefinitely delay a WG's output, and that you want IESG to be able 
resolve such issues internally in the vast majority of cases (because 
appeals to IAB are very time- and resource-consuming). But I don't think 
two weeks is long enough in general to get other ADs to thoroughly 
review a document.  Two months would be much better.

Now it might be the case that IESG members will help each other out, and 
collaborate to log multiple DISCUSS votes to give everybody more time to 
review a document.   People of good will acting in good faith can 
usually find ways to work around buggy processes to make the right thing 
happen, at least in the most important cases.   But it's not ideal, and 
it relies on ADs "getting along" with each other - which creates 
incentives for ADs to not do an adequate job of reviewing some 
documents, so that they'll be able to call in favors from other ADs when 
they need them.   So overall I think the balloting process that IESG 
currently follows is seriously flawed.

> Conversely, a WG that decides to avoid actually engaging on an
> issue in the hope of letting the two-week clock run out is
> putting itself at considerable risk.  The IESG still have the
> ability to fire WG leadership and even to close WGs.

In theory, yes.   But that hardly seems like a good tool for resolving 
issues in a single document, especially when the WG has other ongoing 
work that might turn out to be useful.    Also, at least when I was on 
IESG all of us seemed to be aware that though we did have the authority 
and responsibility to push back on poor work, we also had to be mindful 
of the potential for the community to mutiny.


> Under any
> reasonable circumstances, I assume that the IESG would respond
> very strongly if an AD pointed out the a WG had ignored an
> effort to discuss a substantive issue even if the rest of the
> IESG disagreed with that particular AD about that issue.

I'd hope so.  But I also think that the process should work even for an 
objection raised by an AD who was unpopular with the rest of IESG.  Of 
course I hope that ADs get along well with one another and work together 
to make a better Internet.  But I also know from experience that some 
ADs tend to have more clout than others, and that the ones with the most 
clout aren't always the ones with the best technical judgment.

Keith


From moore@network-heretics.com  Wed May 15 23:20:11 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4A021F905F for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 23:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level: 
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 48eOueeYxobb for <ietf@ietfa.amsl.com>; Wed, 15 May 2013 23:20:06 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 3476621F905D for <ietf@ietf.org>; Wed, 15 May 2013 23:20:06 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2AE3520D52; Thu, 16 May 2013 02:20:04 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Thu, 16 May 2013 02:20:05 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=bku9nii7pVlgdSRUKWbUY4 0fdrg=; b=GcgfnV2TOzV9058kvXZhezmv3GLsMO74DGf8JLJGTOCTw+vNsqvPig d3j5IkA2PWVys/rijhWOeAHRXJnwtTDfNA3DPjZjXGKxIufDiXb9UlC1t8QPFgj7 Um1QNOM4GY+DwUaWeC/RUnkTFAMRl9uADNu7Xs9FqWLASbwGfL/to=
X-Sasl-enc: 1NgHp2vyJ28jZTCxq5h5/XreEmrqXTztvO90iXFe526G 1368685204
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1EE94C8000C; Thu, 16 May 2013 02:20:03 -0400 (EDT)
Message-ID: <51947A8E.9090106@network-heretics.com>
Date: Thu, 16 May 2013 02:19:58 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net> <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com>
In-Reply-To: <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.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, 16 May 2013 06:20:11 -0000

On 05/15/2013 12:25 PM, Thomas Narten wrote:
> I don't think the IETF needs to be in the profile/resume
> business. There are plenty of other places that do a fine job already.
>
> What I do think the IETF should do is *require* that participants
> identify themselves. That means knowing who they are (a name and email
> contact) and an affiliation.

I have mixed feelings about this.   On one hand I would like to know who 
(if anyone) is paying someone to do IETF work, because there's always 
some potential for inappropriate bias even among people with a high 
degree of integrity - and of course not everyone has such integrity.

On the other hand I don't think that a contributor's affiliation should 
mean anything at all when evaluating that contributor's input to IETF.   
If people treat contributors from major companies as having more weight 
than other contributors, it makes a joke out of the whole notion of 
consensus-based decision making.   (And we all know that people do this 
sometimes.)

I also don't think that anyone should automatically presume that a 
contributor's input is representing his employer's interests.

On balance, I do sometimes find it helpful when IETF contributors 
disclose their employers.   But I don't think it should be required.   
And if everybody stopped disclosing their employers in the context of 
IETF conversations, it might be a good thing.

Keith


From randy@psg.com  Thu May 16 00:52:33 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65E2A21F8E99 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 00:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.367
X-Spam-Level: 
X-Spam-Status: No, score=-2.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BnNyRQzVgqIO for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 00:52:20 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 24BC521F8EAF for <ietf@ietf.org>; Thu, 16 May 2013 00:52:20 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Ucsz3-0007fu-9L; Thu, 16 May 2013 07:52:17 +0000
Date: Thu, 16 May 2013 08:52:17 +0100
Message-ID: <m2li7fnyz2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: article on innovation and open standards
In-Reply-To: <20130514213225.GD17491@mx1.yitter.info>
References: <F385DA09-FC7E-41BC-8C23-F348E6E2E466@piuha.net> <201305142037.r4EKbBUU4764257@shell01.TheWorld.com> <20130514213225.GD17491@mx1.yitter.info>
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: Thu, 16 May 2013 07:52:33 -0000

> Without wishing to be nasty, I will point out that we have way more
> vendors than operators participating in our standards development.

          Into the Future with the Internet Vendor Task Force
                        A very Curmudgeonly View
                                 or
               Testing Spaghetti - a Wall's Point of View

       as published in ACM SIGCOMM Computer Communication Review
                   Volume 35, Number 5, October 2005

             http://archive.psg.com/051000.ccr-ivtf.html

From Ted.Lemon@nominum.com  Thu May 16 05:23:11 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4B1021F92EB for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 05:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.576
X-Spam-Level: 
X-Spam-Status: No, score=-106.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-LMUJ2DToPf for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 05:23:04 -0700 (PDT)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 172FB21F91B0 for <ietf@ietf.org>; Thu, 16 May 2013 05:23:03 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKUZTPp30ijoQByaVnIdJzi7RKz7BXS7WZ@postini.com; Thu, 16 May 2013 05:23:04 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 5E82A1B8199 for <ietf@ietf.org>; Thu, 16 May 2013 05:23:03 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4967D19005D; Thu, 16 May 2013 05:23:03 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Thu, 16 May 2013 05:22:56 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: call for ideas: tail-heavy IETF process
Thread-Topic: call for ideas: tail-heavy IETF process
Thread-Index: AQHORoFUUxpFLU6PE0+xWeVCH2or+pkFPpuAgAArdgCAAAXWAIAANn+AgAAJ/gCAAAPRAIAAA8CAgAANYoCAAANHgIAABRkAgABrMACAAKN7gIAAAI4AgACu+gCAAD+mgIAADayAgABvSYA=
Date: Thu, 16 May 2013 12:22:55 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077519F5FD@mbx-01.win.nominum.com>
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E7826@xmb-aln-x02.cisco.com> <8D23D4052ABE7A4490E77B1A012B6307751950AC@mbx-02.win.nominum.com> <C5E08FE080ACFD4DAE31E4BDBF944EB1134E870E@xmb-aln-x02.cisco.com> <51929A21.8030105@gmail.com>	<5192A282.7060409@isi.edu> <5192A5B6.3000205@cs.tcd.ie>	<5192A8DB.7030207@isi.edu> <5192B415.50006@joelhalpern.com> <8D23D4052ABE7A4490E77B1A012B63077519B6C3@mbx-01.win.nominum.com> <5192BB1C.3000902@dcrocker.net> <51931506.3010702@network-heretics.com> <51939E29.7080309@isi.edu> <51939EA0.9070704@network-heretics.com> <51943168.6050908@qti.qualcomm.com> <519466CD.9010508@network-heretics.com> <FCA58917A139C84A0F3A462D@JcK-HP8200.jck.com>
In-Reply-To: <FCA58917A139C84A0F3A462D@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B1C15962B769B3429D8BF01763B43288@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Keith Moore <moore@network-heretics.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 12:23:11 -0000

I must say that I have enjoyed reading the discussion between the three of =
you, and think it is immensely valuable in explaining what the IESG ought t=
o be doing.   You three should write it up.


From abdussalambaryun@gmail.com  Thu May 16 05:38:46 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41D8721F8F6D for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 05:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXh31PllMgs8 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 05:38:45 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 9186A21F8F27 for <ietf@ietf.org>; Thu, 16 May 2013 05:38:45 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id xa7so2263735pbc.25 for <ietf@ietf.org>; Thu, 16 May 2013 05:38:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=Z9A/R/MMpdG655KczQoFaAXHtsYo0+hzBLaVdIetfvo=; b=kjyqx1Vxs1B/DpJzjmHDBRlLYv1ru5mRTr/4xAFsj7HTon+zqgWUPm8Hr9Y8Kn8pVV /IBe3CFSs/SUeqb8w5MWcXhBX3MhynZI1zf8i6MoLn0fw8T57bDhJ6cT2BwOKl90ZgwK zcsvWIHrtzdLnXQUJbDZ9rNx+qyCIZvuMImw95hrFEoXd0yy2eOsBxyHExJiDg1SRtz9 I8jM5Dml8YMLg3730tZHmA+Km8GlCN0vhxDEo4PHNk2LAy+MSK0t/JbC2l4C1HiSpTqL lGhOqQodti4v6iKCYvzyH4fM4aA+Ezhr0OT3wCm70BHApkW3L6y1nh9xLc9w/02rMBT0 I8ZQ==
MIME-Version: 1.0
X-Received: by 10.66.224.73 with SMTP id ra9mr43477471pac.163.1368707925339; Thu, 16 May 2013 05:38:45 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Thu, 16 May 2013 05:38:45 -0700 (PDT)
Date: Thu, 16 May 2013 14:38:45 +0200
Message-ID: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 12:38:46 -0000

On May 15, 2013, at 4:30 PM, Adrian Farrel <adrian at olddog.co.uk> wrote:
> The claim (or one of the claims) is that some ADs may place Discusses that
> are
> intended to raise a discussion with the authors/WG that could equally have
> been
> raised with a Comment or through direct email. This, it is claimed, may
> unnecessarily delay the document from completing the publication process.

Discussions should have a time limit (can be one week), like we have
in meetings (2hours), if there is time we can know when things are
needed to respond to, I usually ignore when there is no milestones or
planing-time. Does IESG have milestones for documents
processing/discussions?

>
> Now the dangerous bit,
>
> Suppose the AD raised her concern by writing a Comment or sending an email
> and
> balloting "No Objection." That would mean that the I-D would be approved
> for
> publication.
>
> At this point either:
> - the discussion goes on, but the document becomes an RFC anyway
> or
> - the responsible AD holds the document pending satisfactory completion of
> the
> discussion.

That AD SHOULD not hold for unlimited time, also should discuss the
issue with the WG related in limited time.
>
> I suggest that the former is a bad result. Not that the authors/WG will
> ignore
> the discussion, but if they disagree on something the AD considers very
> important, the authors/WG have no incentive to participate in the
> discussion.

Only community rough concensus will decide the final result,
> Of
> course, all participants in this thread so far would never behave like that,
> but
> there is a possibility that this will happen for some authors.

Yes only if there is no time limits for work that should be done,

>
> I also suggest that the latter introduces exactly the same amount of delay
> as
> the Discuss.

There is always possibility of large delay in systems that have no
time limits for processing or responds. Our time/work used is
important for IETF, IMO, no one should hold work/time only if able to
decide/notify/plan when/how to leave it go for all reaction
possibilities.

AB

From loa@pi.nu  Thu May 16 06:55:55 2013
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 6540721F9354 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 06:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.898
X-Spam-Level: 
X-Spam-Status: No, score=-100.898 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lotx9dW6V9QE for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 06:55:49 -0700 (PDT)
Received: from pipi.pi.nu (unknown [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 82CB521F8F61 for <ietf@ietf.org>; Thu, 16 May 2013 06:55:49 -0700 (PDT)
Received: from [192.168.1.130] (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) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id A99721800272; Thu, 16 May 2013 15:55:47 +0200 (CEST)
Message-ID: <5194E565.3000200@pi.nu>
Date: Thu, 16 May 2013 15:55:49 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com>
In-Reply-To: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 13:55:55 -0000

On 2013-05-16 14:38, Abdussalam Baryun wrote:

> Discussions should have a time limit (can be one week),

I totally disagree, DISCUSSES are our friends, they need to be
discussed until we have rough consensus; it seems to be a
manifestly bad idea to draw a deadline after seven days, if
someone come up with a satisfactory solution on the eighth.

99,9% of the DISCUSSES improve our documents or the understanding
of them.

/Loa


like we have
> in meetings (2hours), if there is time we can know when things are
> needed to respond to, I usually ignore when there is no milestones or
> planing-time. Does IESG have milestones for documents
> processing/discussions?
>


-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From scott.brim@gmail.com  Thu May 16 07:08:01 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8D5521F9234 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.598
X-Spam-Level: 
X-Spam-Status: No, score=-103.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfHwZkqJrTW1 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:07:56 -0700 (PDT)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 353C021F90EE for <ietf@ietf.org>; Thu, 16 May 2013 07:07:56 -0700 (PDT)
Received: by mail-oa0-f48.google.com with SMTP id i4so3756649oah.21 for <ietf@ietf.org>; Thu, 16 May 2013 07:07:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=25rT7yl2p1+rjY+cLyEmk1hurfZDa73/aJIWeXeYEeI=; b=IUvUDgnR/e4htMIuGoXhbLueGU50d1MfZ00SEBQfNGSgl9y+iPn3EER87hEHYmOgfR UqfPGXZGH6OebmEM9dyTadRMc+BUmcZhA2h/xsh7PZOctJuEOIlDkEc2B2Dmu1I3/ah3 ekOul1NXu1MGCyuMzyI6g0DaoH8bymXnyf507+ayA35TAGSmzhhrr1mcmRfV0eYhxHH6 AcDa6QpzA7nKKvwMZna3BhDrGuNxyzWZQDtKsA+udD37K6tuZHyiOAE5POyYgqLoUbFj shpZ4YIpYgQp/mmE+XiLsB9X4ycB+PSkyo2SEvHgRVuNAnX0oCMOgS+yMh+35vtDQP7V UByQ==
X-Received: by 10.182.241.194 with SMTP id wk2mr14265721obc.77.1368713275750;  Thu, 16 May 2013 07:07:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.184.36 with HTTP; Thu, 16 May 2013 07:07:34 -0700 (PDT)
In-Reply-To: <5194E565.3000200@pi.nu>
References: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com> <5194E565.3000200@pi.nu>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 16 May 2013 10:07:34 -0400
Message-ID: <CAPv4CP-sh+ts3yYg_tao9Wx3v4pGNpJ1FHXLXUj9aKGRMZdhSA@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
To: Loa Andersson <loa@pi.nu>
Content-Type: multipart/alternative; boundary=089e01536b4e99c74e04dcd66402
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@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: Thu, 16 May 2013 14:08:02 -0000

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

Please distinguish between (1) making the system efficient and (2) making
individual documents go through it quickly.  If you put time limits on
parts of the process, you're not allowing them to function correctly.
 Putting arbitrary time limits on will hurry things up but it will not
produce higher quality results.

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

Please distinguish between (1) making the system efficient and (2) making i=
ndividual documents go through it quickly. =A0If you put time limits on par=
ts of the process, you&#39;re not allowing them to function correctly. =A0P=
utting arbitrary time limits on will hurry things up but it will not produc=
e higher quality results.

--089e01536b4e99c74e04dcd66402--

From abdussalambaryun@gmail.com  Thu May 16 07:08:50 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5869E21F8EFD for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:08:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.641
X-Spam-Level: 
X-Spam-Status: No, score=-2.641 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CZiF0GlwDuEg for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:08:45 -0700 (PDT)
Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by ietfa.amsl.com (Postfix) with ESMTP id 41EF121F8506 for <ietf@ietf.org>; Thu, 16 May 2013 07:08:29 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 10so1273747pdc.25 for <ietf@ietf.org>; Thu, 16 May 2013 07:08:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=UEA4uX11j2KOo6W1Q9KvMtSOx/XBKTayvSdQ9Wyn65Q=; b=OwvnJcunQ6/5WbvJYaqWXm3pBZFwfVq5nxeQh3OCJ1H5OQ+j6GG7ramPH9uzZifDlD SGPz9NPHKvoKmeOO7A+0Rb9/E7S2kBTruHzlkoU3dQZ1D3djQTBzSaM3akFn41Cpw2WH jT/xz2TtwPJ1+O160JW5HXrhlpL3giXzkVzbWIiXRmyCG3Wm5ni09WxHgiyqg6AGY8LP 8OxHzFd3a7ti5D+hhRinxc34frS7Nf/MwHV0nyPm5NwJV7UPYg9ymAbV2VQwoofRXI6p Twa/nyOILn8WwLjGR8WZg8FbQw/LLtSgGUdDmaljIYrmSIgaR463xzywPwNNc27XL7f9 /CTw==
MIME-Version: 1.0
X-Received: by 10.66.163.133 with SMTP id yi5mr37537578pab.93.1368713308904; Thu, 16 May 2013 07:08:28 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Thu, 16 May 2013 07:08:28 -0700 (PDT)
In-Reply-To: <5194E565.3000200@pi.nu>
References: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com> <5194E565.3000200@pi.nu>
Date: Thu, 16 May 2013 16:08:28 +0200
Message-ID: <CADnDZ89fu1QGZ6hAh2-hiLUEbQL74Wo-odazRpoYzA=7YOkxzg@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Loa Andersson <loa@pi.nu>
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: Thu, 16 May 2013 14:08:50 -0000

Hi Loa,

I agree with you discussions are our friend. I was focusing on
processing time, not document quality. No dought if you stay longer
time you will get better quality, but what about progress. So I mean
call for discussions is for a time limit, as if no discussion happends
then the call matures and the holding of the work stops as well. If
DISCUSS is continue I never like to close it as long as it is
continuous, but not delayed. In practice I never seen that DISCUSS of
ADs with the WGs are having much continuous communication, it is delay
with no time schedule.

> 99,9% of the DISCUSSES improve our documents or the understanding
> of them.

I know that DISCUSSES with WGs improves our documents (don't forget
that WGs are following milestones and WGLC periods), but DISCUSSES
that have no time limit makes more delays. I hope we see similar times
of WG into the IESG, so the communication can improve the processing
time.

AB

On 5/16/13, Loa Andersson <loa@pi.nu> wrote:
>
>
> On 2013-05-16 14:38, Abdussalam Baryun wrote:
>
>> Discussions should have a time limit (can be one week),
>
> I totally disagree, DISCUSSES are our friends, they need to be
> discussed until we have rough consensus; it seems to be a
> manifestly bad idea to draw a deadline after seven days, if
> someone come up with a satisfactory solution on the eighth.
>
> 99,9% of the DISCUSSES improve our documents or the understanding
> of them.
>
> /Loa
>
>
> like we have
>> in meetings (2hours), if there is time we can know when things are
>> needed to respond to, I usually ignore when there is no milestones or
>> planing-time. Does IESG have milestones for documents
>> processing/discussions?
>>
>
>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>

From abdussalambaryun@gmail.com  Thu May 16 07:11:17 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0E0021F8E46 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.635
X-Spam-Level: 
X-Spam-Status: No, score=-2.635 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5lrqYq3Nglc6 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:11:12 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id A4A6721F84AD for <ietf@ietf.org>; Thu, 16 May 2013 07:11:12 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id 6so2370896pdd.31 for <ietf@ietf.org>; Thu, 16 May 2013 07:11:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=b1i1ZweudnEYjtYQE4yeuJ6jNUgk2d8Hs82iy9kbSJw=; b=d8Aoh+EG4Cw1Q3v1ChR8bZvYjF1EYv9JUZwvyuHfDHNTO0ZbKhTjKZ1n/Pxuf3jZYR pBJNJ8+QiujQi9Nk1lTiW0hIWouHNVHiExnQNE0vQIUt6sONnqY5QgZBov2u/sy5hm7e BTrDNYGtjQo5vxzKSI+6JtJ/r0o3c8cLRLeA5mY8d5metA4O0AaZgS5/LXraiZbBLIg9 kRW4pKcGJikCoRg7QT8Oq37cu9A/u/6EhDYb51Zztgo0ioa1cPRmI1fwgvmSFJk3+9jp wzENyC+N8a614bTxStH0hQs06zjCwxZzslGzuwaG4EiAGPLae1VcE5CYgoWz0J6d3d7Z 4iRw==
MIME-Version: 1.0
X-Received: by 10.68.193.138 with SMTP id ho10mr43299370pbc.163.1368713472375;  Thu, 16 May 2013 07:11:12 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Thu, 16 May 2013 07:11:12 -0700 (PDT)
In-Reply-To: <CAPv4CP-sh+ts3yYg_tao9Wx3v4pGNpJ1FHXLXUj9aKGRMZdhSA@mail.gmail.com>
References: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com> <5194E565.3000200@pi.nu> <CAPv4CP-sh+ts3yYg_tao9Wx3v4pGNpJ1FHXLXUj9aKGRMZdhSA@mail.gmail.com>
Date: Thu, 16 May 2013 16:11:12 +0200
Message-ID: <CADnDZ891bdz2xgKmNXMrT9kQca+Ur1CVuWofM8hxdvXe5W=FPA@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 14:11:17 -0000

On 5/16/13, Scott Brim <scott.brim@gmail.com> wrote:
> Please distinguish between (1) making the system efficient and (2) making
> individual documents go through it quickly.  If you put time limits on
> parts of the process, you're not allowing them to function correctly.
>  Putting arbitrary time limits on will hurry things up but it will not
> produce higher quality results.
>

Ok, so do you agree, that if who holds the work, at least should tell
us HOW long he is holding or what is the time PLAN. Do you think
working without plan is efficient and gives good quality.

AB

From barryleiba.mailing.lists@gmail.com  Thu May 16 07:23:01 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 004A121F8F32 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:23:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.03
X-Spam-Level: 
X-Spam-Status: No, score=-102.03 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OZzCWgBkKIr5 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 07:23:00 -0700 (PDT)
Received: from mail-vb0-x22e.google.com (mail-vb0-x22e.google.com [IPv6:2607:f8b0:400c:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 7A71E21F8EDA for <ietf@ietf.org>; Thu, 16 May 2013 07:23:00 -0700 (PDT)
Received: by mail-vb0-f46.google.com with SMTP id 10so1411216vbe.19 for <ietf@ietf.org>; Thu, 16 May 2013 07:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=hAPLswhS8W7te2KVn7XKCCwwcASM9GnQQNi0V8nRHgE=; b=Z2QFubzYR20C4qycAE+oeAsREk63s5YT3um7IKLoM7OHpYwNlEuQ6uMhUuJGIgi41Z rnUV/q9zKTh5KLhmvsnMIy4RJC/Wzw51zcE3GNldPaW4FiWQQLUcGYs9GdItJblHxoSZ HGCQdOhjGtE2P94T+glJOlH5AjYO57uC/YsYkni51D5IHHiY2Mb9aXjzBi3F+S+4m/6S SLVpOAgAeLNZHv6vWF0Jo0CrnS3iHPCMgOqQk6k49Arz3XcAuA3tZDynhIvaqHMoBtH4 0vRkPtEH0/Z9SZzu0L4fC0TYihqhluUGCR+ixT252yfhyjyzzxRMpm/yX6ORHmSAD32r 8CIg==
MIME-Version: 1.0
X-Received: by 10.52.93.179 with SMTP id cv19mr24114199vdb.20.1368714179591; Thu, 16 May 2013 07:22:59 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.6.233 with HTTP; Thu, 16 May 2013 07:22:59 -0700 (PDT)
In-Reply-To: <CADnDZ891bdz2xgKmNXMrT9kQca+Ur1CVuWofM8hxdvXe5W=FPA@mail.gmail.com>
References: <CADnDZ88gzfwQSn84LjsksQESf_KrFk3FOtnLHKqkoD_=owPQWg@mail.gmail.com> <5194E565.3000200@pi.nu> <CAPv4CP-sh+ts3yYg_tao9Wx3v4pGNpJ1FHXLXUj9aKGRMZdhSA@mail.gmail.com> <CADnDZ891bdz2xgKmNXMrT9kQca+Ur1CVuWofM8hxdvXe5W=FPA@mail.gmail.com>
Date: Thu, 16 May 2013 10:22:59 -0400
X-Google-Sender-Auth: 7xKSg6vy2OHPkXIUMvJHNBVZ4gI
Message-ID: <CAC4RtVDqhn78tD4PsyAGoUC8+jxjj12EFV53royaxzbHS-3ogA@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 14:23:01 -0000

>> Putting arbitrary time limits on will hurry things up but it will not
>> produce higher quality results.
>
> Ok, so do you agree, that if who holds the work, at least should tell
> us HOW long he is holding or what is the time PLAN. Do you think
> working without plan is efficient and gives good quality.

We generally rely on judgment in this regard, not on time limits and
deadlines.  We do sometimes set deadlines (milestones in charters,
timeouts on last calls, fixed telechat dates, alerts when things take
too long), but we also give leeway (we know how solid charter
milestones aren't, and no one will ignore important, useful input just
because it came in after last call).

Someone is always responsible for determining when a discussion is no
longer productive (shepherds, chairs, responsible ADs), and someone is
responsible for moving things forward.  Reminders to those who are
responsible, telling them that things seem to be dragging, are fine.
Strict time limits are generally not how we prefer to work.

Barry

From worley@shell01.TheWorld.com  Thu May 16 08:47:10 2013
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 E45BA21F91F1 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 08:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSWU005v3u6D for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 08:47:05 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id F111621F8F6E for <ietf@ietf.org>; Thu, 16 May 2013 08:47:04 -0700 (PDT)
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 r4GFl1DK022890 for <ietf@ietf.org>; Thu, 16 May 2013 11:47:03 -0400
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 r4GFl16g4856810 for <ietf@ietf.org>; Thu, 16 May 2013 11:47:01 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r4GFl0D34873774; Thu, 16 May 2013 11:47:00 -0400 (EDT)
Date: Thu, 16 May 2013 11:47:00 -0400 (EDT)
Message-Id: <201305161547.r4GFl0D34873774@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com> (narten@us.ibm.com)
Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process]
References: <A5D17763-847B-4A29-8343-844588440BF2@piuha.net> <32577.1367426027@sandelman.ca> <201305031259.r43Cx5l9015836@cichlid.raleigh.ibm.com> <5183BB59.7090206@cs.tcd.ie> <201305031413.r43EDwkq027639@cichlid.raleigh.ibm.com> <04a601ce4809$5679a000$036ce000$@olddog.co.uk> <201305031432.r43EWov1030152@cichlid.raleigh.ibm.com> <518435D5.5040601@isdg.net> <201305151625.r4FGPhvZ012163@cichlid.raleigh.ibm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 15:47:11 -0000

> From: Thomas Narten <narten@us.ibm.com>
> 
> What I do think the IETF should do is *require* that participants
> identify themselves. That means knowing who they are (a name and email
> contact) and an affiliation. For 80% of the participants, this info is
> not very hard to figure out (see below). But we also have participants
> that use obscure email handles that don't correlate to anything
> obvious, whether a real person or to a name in the list of registered
> attendees, etc. I suspect these folk are *not* intenending to be
> anonymous participants, but in practice they are.
> 
> And yes, knowing who someone is, their background and who they work
> for is important to me in figuring out how to guage their input. E.g.,
> I would likely pay more attention to an operator's comments on a
> proposed use case than from someone else.

I believe that this is a less good idea than first appears.

One objection is that the concept of "affiliation" is less simple than
it appears.  People normally expect it to mean "Who is your employer?"

As John mentions, it can mean "What is the organization whose
interests you are promoting?"  But in regard to your observation about
use cases, it can also mean "What area of technology do you have
experience in?"

In many cases, "affiliation" is related to "Who is paying for your
attendance?"  But there are situations where your employer may be
willing to pay for your attendance but doesn't want you to be seen as
officially representing them.

And (at least in common-law countries) one can simply invent an
(unincorporated!) company name and claim it as your affiliation.

In practice, the way we deal with these problems is that we consider
everyone to be individuals, rather than as "the representative of
company XYZ", and it takes time to build a reputation.  One is thus
unwilling to sacrifice that expensive reputation to advocate a poor
solution because one's employer favors it.

    3) Google names, look at authorship info in RFCs, linked in,
    etc. Works in a lot of cases, but is sometimes more work than
    seems appropriate.

If you can't find any information about them, they have no reputation.

Dale

From dhc@dcrocker.net  Thu May 16 09:23:40 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFDD921F89AF for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 09:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GKLkz3CD-aqv for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 09:23:28 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4B47A21F85BF for <ietf@ietf.org>; Thu, 16 May 2013 09:23:28 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4GGNNfp027375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 May 2013 09:23:27 -0700
Message-ID: <519507ED.4090805@dcrocker.net>
Date: Thu, 16 May 2013 09:23:09 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>
In-Reply-To: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 16 May 2013 09:23:27 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 16:23:47 -0000

On 5/15/2013 1:30 PM, Adrian Farrel wrote:
> Suppose the AD raised her concern by writing a Comment or sending an email and
> balloting "No Objection." That would mean that the I-D would be approved for
> publication.
>
> At this point either:
> - the discussion goes on, but the document becomes an RFC anyway
> or
> - the responsible AD holds the document pending satisfactory completion of the
> discussion.
>
> I suggest that the former is a bad result.


> Personally (but this may reflect my Discusses) I find that an active engagement
> by the authors and the Discussing AD on the issue and the potential resolution,
> always leads to speedy progression of the document either with the AD feeling
> stupid, or the document improved. Both are adequate results.


Adrian,

I suggest we all take a look at the original text of the Subject field.

The problem here is that basic reviewing is being done by the ADs too 
late in the process.  We are making the mistake of having ADs be exempt 
from IETF Last Call, and allowing them to be unprepared for the IESG 
vote.  So we are combining "education" with "voting".  That's a paradigm 
error.

By the time the IESG schedules the vote, ADs need to already have 
educated themselves about the document.

Of course, the IESG discussion during the voting process well might 
uncover an actual, serious issue with the document; this should be 
exceptional and it should be an issue that the /IESG/ agrees needs to be 
resolved and it means that voting should not take place until it is. 
But that is quite different from the usual "let's talk about it" kind of 
Discuss imposed by individual ADs.

So here's a simple proposal that pays attention to AD workload and 
includes a simple efficiency hack:

      When the IETF Last Call is issued, wait a few days, to see whether 
any serious issues are raised by the community.  The really serious ones 
usually are raised quickly.  If there are none, it's pretty certain the 
document will advance to an IESG vote.  That leaves 7-10 days of IETF 
Last Call for ADs to get educated and ask questions, just like everyone 
else.

Jari has expressed the goal of having AD concerns be raised more 
publicly.  Moving AD review and comment to the IETF Last Call venue 
nicely accomplishes this, too.



On 5/15/2013 8:55 AM, Thomas Narten wrote:
 > 1) Discuss criteria should be principles, not rigid rules. The details
 > of the issue at hand always matter, and it will sometimes come down to
 > judgement calls where reasonable individuals just might disagree.

We've been doing protocol specification for 40 years.  If we can't 
codify the major concerns that warrant blocking advancement of a 
protocol, we're just being lazy.  Really.  That a given situation might 
cause the IESG to decide to enhance the list does not mean that the list 
shouldn't seek to be complete and precise and that ADs be held to it.

At every turn, the approach we've taken to the IESG review and approval 
process is to limit actual accountability to the community.  Everyone is 
well-intentioned, but really this makes the process a matter of 
personalities and not the rigor of serious professionalism.

The IESG's process is far, far better than it was 10-15 years ago, but 
it still lacks meaningful predictability and serious accountability; it 
is not reasonable for the process to require that authors and chairs 
take the initiative of complaining when an AD is being problematic.

In terms of quality assurance, the idea that we have a process that 
relies on the sudden insight of a single AD, at the end of a many-month 
process, is broken.  It's fine if that person sees something that 
everyone else has missed until then, but that is quite different from 
designing a process that is claimed to rely on it.

And of course, the reality is that we allow bad specs out the door all 
the time; we just allow fewer of them than many/most other standards 
bodies...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From adrian@olddog.co.uk  Thu May 16 09:40:32 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A420421F8FDD for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 09:40:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AtzEw+SnL00C for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 09:40:27 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 151C721F8FC4 for <ietf@ietf.org>; Thu, 16 May 2013 09:40:26 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4GGeIQw013646;  Thu, 16 May 2013 17:40:19 +0100
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 r4GGeHNb013632 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 16 May 2013 17:40:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dcrocker@bbiw.net>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net>
In-Reply-To: <519507ED.4090805@dcrocker.net>
Subject: RE: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Date: Thu, 16 May 2013 17:40:15 +0100
Message-ID: <027301ce5254$0b8689a0$22939ce0$@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: AQDRKFYqM70N+Q/8AK8pN4UgDAE3fAG9QZKgmvRqmyA=
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 16:40:32 -0000

That's a good question Dave.

The community might like to comment. 

On the whole, I am told that if an AD weighs in with her comments during working
group last call, her fearsome personality may overwhelm some of the WG
participants and she may dominate the WG consensus.

Is it possible that the same would happen in IETF last call? I know, of course,
that a number of you have a robust ability to defend your opinions, but how
would you (the community, not Dave) feel if ADs (speaking as ADs, not speaking
as individual contributors) made their review comments during IETF last call?

I agree that this would bring the tail forward a little (not a lot).
I don't believe it would reduce AD work-load (which is another issue entirely).
I have mixed feelings about whether it would change the processing time for a
draft. That might depend on how the review is handled in IETF last call.

Lastly, I think I disagree with you about "really serious" IETF last call
comments coming in the first few days. It seems to me that we also get an number
of late comments of substance resulting from people who are not familiar with
the document reviewing it (such as directorate reviews and people who didn't
notice the I-D sneaking through).

Still thinking,
Adrian

> -----Original Message-----
> From: Dave Crocker [mailto:dhc@dcrocker.net]
> Sent: 16 May 2013 17:23
> To: adrian@olddog.co.uk
> Cc: ietf@ietf.org
> Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF
process]
> 
> On 5/15/2013 1:30 PM, Adrian Farrel wrote:
> > Suppose the AD raised her concern by writing a Comment or sending an email
> and
> > balloting "No Objection." That would mean that the I-D would be approved for
> > publication.
> >
> > At this point either:
> > - the discussion goes on, but the document becomes an RFC anyway
> > or
> > - the responsible AD holds the document pending satisfactory completion of
> the
> > discussion.
> >
> > I suggest that the former is a bad result.
> 
> 
> > Personally (but this may reflect my Discusses) I find that an active
engagement
> > by the authors and the Discussing AD on the issue and the potential
resolution,
> > always leads to speedy progression of the document either with the AD
feeling
> > stupid, or the document improved. Both are adequate results.
> 
> 
> Adrian,
> 
> I suggest we all take a look at the original text of the Subject field.
> 
> The problem here is that basic reviewing is being done by the ADs too
> late in the process.  We are making the mistake of having ADs be exempt
> from IETF Last Call, and allowing them to be unprepared for the IESG
> vote.  So we are combining "education" with "voting".  That's a paradigm
> error.
> 
> By the time the IESG schedules the vote, ADs need to already have
> educated themselves about the document.
> 
> Of course, the IESG discussion during the voting process well might
> uncover an actual, serious issue with the document; this should be
> exceptional and it should be an issue that the /IESG/ agrees needs to be
> resolved and it means that voting should not take place until it is.
> But that is quite different from the usual "let's talk about it" kind of
> Discuss imposed by individual ADs.
> 
> So here's a simple proposal that pays attention to AD workload and
> includes a simple efficiency hack:
> 
>       When the IETF Last Call is issued, wait a few days, to see whether
> any serious issues are raised by the community.  The really serious ones
> usually are raised quickly.  If there are none, it's pretty certain the
> document will advance to an IESG vote.  That leaves 7-10 days of IETF
> Last Call for ADs to get educated and ask questions, just like everyone
> else.
> 
> Jari has expressed the goal of having AD concerns be raised more
> publicly.  Moving AD review and comment to the IETF Last Call venue
> nicely accomplishes this, too.
> 
> 
> 
> On 5/15/2013 8:55 AM, Thomas Narten wrote:
>  > 1) Discuss criteria should be principles, not rigid rules. The details
>  > of the issue at hand always matter, and it will sometimes come down to
>  > judgement calls where reasonable individuals just might disagree.
> 
> We've been doing protocol specification for 40 years.  If we can't
> codify the major concerns that warrant blocking advancement of a
> protocol, we're just being lazy.  Really.  That a given situation might
> cause the IESG to decide to enhance the list does not mean that the list
> shouldn't seek to be complete and precise and that ADs be held to it.
> 
> At every turn, the approach we've taken to the IESG review and approval
> process is to limit actual accountability to the community.  Everyone is
> well-intentioned, but really this makes the process a matter of
> personalities and not the rigor of serious professionalism.
> 
> The IESG's process is far, far better than it was 10-15 years ago, but
> it still lacks meaningful predictability and serious accountability; it
> is not reasonable for the process to require that authors and chairs
> take the initiative of complaining when an AD is being problematic.
> 
> In terms of quality assurance, the idea that we have a process that
> relies on the sudden insight of a single AD, at the end of a many-month
> process, is broken.  It's fine if that person sees something that
> everyone else has missed until then, but that is quite different from
> designing a process that is claimed to rely on it.
> 
> And of course, the reality is that we allow bad specs out the door all
> the time; we just allow fewer of them than many/most other standards
> bodies...
> 
> d/
> 
> 
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From dhc@dcrocker.net  Thu May 16 10:01:49 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24BA021F93E1 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 10:01:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.479
X-Spam-Level: 
X-Spam-Status: No, score=-6.479 tagged_above=-999 required=5 tests=[AWL=0.120,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBjhEkLAy0Ke for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 10:01:44 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 61B2D11E8102 for <ietf@ietf.org>; Thu, 16 May 2013 10:01:44 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4GH1egs028192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 16 May 2013 10:01:44 -0700
Message-ID: <519510E6.5010105@dcrocker.net>
Date: Thu, 16 May 2013 10:01:26 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <027301ce5254$0b8689a0$22939ce0$@olddog.co.uk>
In-Reply-To: <027301ce5254$0b8689a0$22939ce0$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 16 May 2013 10:01:44 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 17:01:49 -0000

On 5/16/2013 9:40 AM, Adrian Farrel wrote:
> That's a good question Dave.
>
> The community might like to comment.
>
> On the whole, I am told that if an AD weighs in with her comments during working
> group last call, her fearsome personality may overwhelm some of the WG
> participants and she may dominate the WG consensus.

Only women ADs? [1]

But seriously...


> Is it possible that the same would happen in IETF last call?

I think that the public sway of ADs on the IETF list is less of a risk 
than on wg mailing lists.  And note that my suggestion has ADs waiting 
to weigh in until community-generated active disagreement with the spec, 
or its passive agreement, has been established.

In any event, the current reality of having an AD weigh in with a a 
process-blocking Discuss is not exactly /under-/whelming...

Simply put:  We are starting with the reality that an AD is going to be 
expressing their opinions.  The question is when and how.  It's not 
going to be /less/ intimidating to have it done as a Discuss.

Contrary to some of the mythology that has been expressed about this, 
the frequent reality is that the typical wg goal is to clear the 
Discuss, not really to engage in debate with an AD who is blocking 
document progress.  (I've watched this reality many times over the 
years.)  That is far less healthy than having the AD's concern become 
part of the /public/ review process.


> I agree that this would bring the tail forward a little (not a lot).
> I don't believe it would reduce AD work-load (which is another issue entirely).

Yes, the timing change is small.  But the context change is enormous.


> Lastly, I think I disagree with you about "really serious" IETF last call
> comments coming in the first few days. It seems to me that we also get an number

Some, sure.  But I said it was an efficiency hack.  The goal isn't for 
it to be perfect, just helpful.

d/


[1] The question of proper referential language is a continuing surprise 
to me, given that the currently-popular conventions create more problems 
than they solve -- and it's even a question on a PSAT preparatory 
example that I saw yesterday.  There's a pretty straightforward 
alternative that works nearly all the time:

    http://dcrocker.net/#gender



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From Ted.Lemon@nominum.com  Thu May 16 10:14:51 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8220F11E812E for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 10:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.567
X-Spam-Level: 
X-Spam-Status: No, score=-106.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Wta8Su+DvWg for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 10:14:45 -0700 (PDT)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5FF11E8129 for <ietf@ietf.org>; Thu, 16 May 2013 10:14:45 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUZUUBUVHYDLaHhuiKidMdaDDxNtjRU86@postini.com; Thu, 16 May 2013 10:14:45 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 3A8F41B80AB for <ietf@ietf.org>; Thu, 16 May 2013 10:14:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 2F89019005D; Thu, 16 May 2013 10:14:45 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Thu, 16 May 2013 10:14:45 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, Dave Crocker <dhc@dcrocker.net>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUlHJjV59ms6lNUuynGFpNZ+3epkIeMqAgAAF6wCAAAO2gA==
Date: Thu, 16 May 2013 17:14:44 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751A11D9@mbx-01.win.nominum.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <027301ce5254$0b8689a0$22939ce0$@olddog.co.uk> <519510E6.5010105@dcrocker.net>
In-Reply-To: <519510E6.5010105@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B2F6BC75A83DAD4F826EEC1E3B750D68@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Adrian Farrel <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 17:14:51 -0000

On May 16, 2013, at 1:01 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>   http://dcrocker.net/#gender

That's what I do.  It gets a bit awkward with verb agreement and constructs=
 like "themself," which elicits the dreaded red snake underline of doom.   =
But I find it more comfortable than just subverting the sexist paradigm wit=
h a differently sexist paradigm.


From mrex@sap.com  Thu May 16 11:06:31 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A05D321F8F41 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 11:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.249
X-Spam-Level: 
X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGqKk5R6qsvs for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 11:06:27 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 326A821F8F38 for <ietf@ietf.org>; Thu, 16 May 2013 11:06:27 -0700 (PDT)
Received: from mail06.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r4GI6GbU019640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 16 May 2013 20:06:16 +0200 (MEST)
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
In-Reply-To: <519507ED.4090805@dcrocker.net>
To: dcrocker@bbiw.net
Date: Thu, 16 May 2013 20:06:15 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20130516180615.EDD651A73C@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 18:06:32 -0000

Dave Crocker wrote:
> 
> And of course, the reality is that we allow bad specs out the door all 
> the time; we just allow fewer of them than many/most other standards 
> bodies...

But different to (at least some) other standards bodies, we lack an
official means to publish defect reports (aka errata) to document defects
in a _timely_(!!) fashion.  (Timely = can be found where the RFC says
that it can be found, and within at most a few weeks after the
defect/omission has been found by an implementor).

In theory, we have the errata process, and recent RFC even include
a direct URL pointer to the RFC-Editors errata page on the title page:

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfcXXXX.

("XXXX" containing the real number of the RFC on which this appears).

However, the Errata process is currently working poorly, primarily
because a number of folks (including some IETF leadership) currently
thinks that posting something a trivial as a missing vital one-line
clarification to a published RFC as a "substantial change" that can
only be performed by publishing a whole new RFC.


-Martin

From scott.brim@gmail.com  Thu May 16 11:08:37 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669BF21F8EBC for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 11:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AektpasvXyZk for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 11:08:36 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id AEAFB21F9057 for <ietf@ietf.org>; Thu, 16 May 2013 11:08:35 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id vb8so3807910obc.14 for <ietf@ietf.org>; Thu, 16 May 2013 11:08:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=HXJRHVAOHGOkVqzt/nDPeij0/Xi/IzkYIzCJiewnMwQ=; b=emRvY9aaaml8/dKqbfFbwRdpe6HoI27b8DcSU2LT4P1YRQGmEh0SZ2weNagOEYhB70 FN7hutSZ8YD1SBhvSmzxh37WAyobCW6wV1Auf9xU9DsJbcI0p/nsMyIGQUQRZVW2+/E4 kELMeyy+Uu8NxOf9I3yLNlmmajsRXKescJzJneq22KQxAhSVeZ/f8WRUzit3eRs53tbM V322c/iKvHpWYNF30oeU5AieCAi1AYHhLq7xCZgbHOAfXoqlVrNcKrLE4Y1VPDeoXr8C JL+QCqm+qMaD4bYEGLwWYClL1uRgMju8vXRA18qMkamQPNLyTRPV3qCMQ4iVd2hlhkPK 5AtQ==
MIME-Version: 1.0
X-Received: by 10.60.141.193 with SMTP id rq1mr11441431oeb.58.1368727715157; Thu, 16 May 2013 11:08:35 -0700 (PDT)
Received: by 10.182.184.36 with HTTP; Thu, 16 May 2013 11:08:35 -0700 (PDT)
In-Reply-To: <519507ED.4090805@dcrocker.net>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net>
Date: Thu, 16 May 2013 14:08:35 -0400
Message-ID: <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Scott Brim <scott.brim@gmail.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b450be8419e9604dcd9c12e
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 18:08:38 -0000

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

On Thursday, May 16, 2013, Dave Crocker wrote:

> By the time the IESG schedules the vote, ADs need to already have educated
> themselves about the document.
>

Oh, so you're suggesting adding another phase to the process: IESG
education.  OK.


>
> So here's a simple proposal that pays attention to AD workload and
> includes a simple efficiency hack:
>
>      When the IETF Last Call is issued, wait a few days, to see whether
> any serious issues are raised by the community.  The really serious ones
> usually are raised quickly.  If there are none, it's pretty certain the
> document will advance to an IESG vote.  That leaves 7-10 days of IETF Last
> Call for ADs to get educated and ask questions, just like everyone else.
>

Placing a time limit on some phase of the process doesn't produce quality.
 The process should take as long as it must in order to produce a good
outcome.  The question shouldn't be how long the process takes (that's just
a cheap shortcut), it should be how to make it more efficient in doing
well.  I have an idea: let's place a time limit on working groups: they
need to finish drafts in six weeks or there will be penalties.  Why not?

Scott

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

On Thursday, May 16, 2013, Dave Crocker  wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">By the time the IESG schedules the vote, ADs need to already have ed=
ucated themselves about the document.<br>
</blockquote><div><br></div><div>Oh, so you&#39;re suggesting adding anothe=
r phase to the process: IESG education. =A0OK.</div><div>=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">

<br>So here&#39;s a simple proposal that pays attention to AD workload and =
includes a simple efficiency hack:<br>
<br>
=A0 =A0 =A0When the IETF Last Call is issued, wait a few days, to see wheth=
er any serious issues are raised by the community. =A0The really serious on=
es usually are raised quickly. =A0If there are none, it&#39;s pretty certai=
n the document will advance to an IESG vote. =A0That leaves 7-10 days of IE=
TF Last Call for ADs to get educated and ask questions, just like everyone =
else.<br>
</blockquote><div><br></div><div>Placing a time limit on some phase of the =
process doesn&#39;t produce quality. =A0The process should take as long as =
it must in order to produce a good outcome. =A0The question shouldn&#39;t b=
e how long the process takes (that&#39;s just a cheap shortcut), it should =
be how to make it more efficient in doing well. =A0I have an idea: let&#39;=
s place a time limit on working groups: they need to finish drafts in six w=
eeks or there will be penalties. =A0Why not?</div>
<div>=A0</div><div>Scott</div><div><br></div>

--047d7b450be8419e9604dcd9c12e--

From joelja@bogus.com  Thu May 16 13:49:37 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 775C511E815E for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level: 
X-Spam-Status: No, score=-102.676 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvRGEcFxQJru for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:49:36 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6266F11E815F for <ietf@ietf.org>; Thu, 16 May 2013 13:49:36 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4GKnVla029362 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 16 May 2013 20:49:31 GMT (envelope-from joelja@bogus.com)
Message-ID: <51954656.3010302@bogus.com>
Date: Thu, 16 May 2013 13:49:26 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>	<519507ED.4090805@dcrocker.net>	<027301ce5254$0b8689a0$22939ce0$@olddog.co.uk> <519510E6.5010105@dcrocker.net>
In-Reply-To: <519510E6.5010105@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.2.7 (nagasaki.bogus.com [147.28.0.81]); Thu, 16 May 2013 20:49:32 +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: Thu, 16 May 2013 20:49:37 -0000

On 5/16/13 10:01 AM, Dave Crocker wrote:
> On 5/16/2013 9:40 AM, Adrian Farrel wrote:
>> That's a good question Dave.
>>
>> The community might like to comment.
>>
>> On the whole, I am told that if an AD weighs in with her comments 
>> during working
>> group last call, her fearsome personality may overwhelm some of the WG
>> participants and she may dominate the WG consensus.
>
> Only women ADs? [1]
>
> But seriously...
>
If Tiresias prophet of Thebes is in your wg, I'd listen.
>> Is it possible that the same would happen in IETF last call?
>
> I think that the public sway of ADs on the IETF list is less of a risk 
> than on wg mailing lists.  And note that my suggestion has ADs waiting 
> to weigh in until community-generated active disagreement with the 
> spec, or its passive agreement, has been established.
>
Early participation AD's weighing in on draft's generally takes the form 
of just another participant unless you're asking for an opinion on a 
process point. wearing different hats on the course of the lifecycle is 
normal imho. opinion at the mic or on the list is not iesg review. The 
sponsoring AD (who is presumably the most involved) is not likely the 
one with the discuss later in the process since they had to do the 
initial review, put it through the ietf last call and then ballot it, so 
fundamentally they should have a document they can live with when it 
gets to that stage.
> In any event, the current reality of having an AD weigh in with a a 
> process-blocking Discuss is not exactly /under-/whelming...
>
> Simply put:  We are starting with the reality that an AD is going to 
> be expressing their opinions.  The question is when and how. It's not 
> going to be /less/ intimidating to have it done as a Discuss.
>
> Contrary to some of the mythology that has been expressed about this, 
> the frequent reality is that the typical wg goal is to clear the 
> Discuss, not really to engage in debate with an AD who is blocking 
> document progress.  (I've watched this reality many times over the 
> years.)  That is far less healthy than having the AD's concern become 
> part of the /public/ review process.
>
>
>> I agree that this would bring the tail forward a little (not a lot).
>> I don't believe it would reduce AD work-load (which is another issue 
>> entirely).
>
> Yes, the timing change is small.  But the context change is enormous.
>
>
>> Lastly, I think I disagree with you about "really serious" IETF last 
>> call
>> comments coming in the first few days. It seems to me that we also 
>> get an number
>
> Some, sure.  But I said it was an efficiency hack.  The goal isn't for 
> it to be perfect, just helpful.
>
> d/
>
>
> [1] The question of proper referential language is a continuing 
> surprise to me, given that the currently-popular conventions create 
> more problems than they solve -- and it's even a question on a PSAT 
> preparatory example that I saw yesterday.  There's a pretty 
> straightforward alternative that works nearly all the time:
>
>    http://dcrocker.net/#gender
>
>
>


From ynir@checkpoint.com  Thu May 16 13:50:00 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B745311E8153 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.31
X-Spam-Level: 
X-Spam-Status: No, score=-10.31 tagged_above=-999 required=5 tests=[AWL=0.288,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLeWuSBiZ5M0 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:49:54 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 340A011E8172 for <ietf@ietf.org>; Thu, 16 May 2013 13:49:51 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4GKle8L021002; Thu, 16 May 2013 23:49:41 +0300
X-CheckPoint: {519543E8-15-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Thu, 16 May 2013 23:46:12 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUlHUcz+WlRRzt0ejUkQyTd1vw5kH6dWAgAAsDAA=
Date: Thu, 16 May 2013 20:46:12 +0000
Message-ID: <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com>
In-Reply-To: <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@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.9]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_F46B3DFBDC3C4AD48D1A5694E89D6E9Fcheckpointcom_"
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 20:50:00 -0000

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


On May 16, 2013, at 9:08 PM, Scott Brim <scott.brim@gmail.com<mailto:scott.=
brim@gmail.com>> wrote:

On Thursday, May 16, 2013, Dave Crocker wrote:
By the time the IESG schedules the vote, ADs need to already have educated =
themselves about the document.

Oh, so you're suggesting adding another phase to the process: IESG educatio=
n.  OK.

I don't speak for Dave, but it makes sense that when a document reaches the=
 IESG telechat, the questions to be asked are (1) Did this get sufficient r=
eview by sufficiently capable people, and (2) Has the process been followed=
, including have all issues been addressed.

The time for asking whether the group has considered making this field fixe=
d length instead of variable, or whether RFC 2119 language is used in an ap=
propriate way, or whether the protocol is extensible enough is at IETF last=
 call. This is true of any participants, and ADs can do this too, regardles=
s of whether their presence might intimidate the crowd. It could even be th=
at if ADs voice their concerns at that time, others might join in, making t=
he LC time more useful and less about just waiting two or four weeks.

There is a problem, though, that this will increase the load on ADs. Other =
concerns raised during IETF LC may lead to revised I-Ds, which the ADs will=
 need to re-read (or at least look at the diff). I don't know how significa=
nt this extra work would be, but it would come at a time that we're thinkin=
g of ways to reduce AD workload. It might also require prolonging the LC ti=
me, because there would be actual discussion in it.

Yoav



--_000_F46B3DFBDC3C4AD48D1A5694E89D6E9Fcheckpointcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <A153C60D7F5CF44197304DDDC09EC687@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<br>
<div>
<div>On May 16, 2013, at 9:08 PM, Scott Brim &lt;<a href=3D"mailto:scott.br=
im@gmail.com">scott.brim@gmail.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">On Thursday, May 16, 2013, Dave Crocker wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
By the time the IESG schedules the vote, ADs need to already have educated =
themselves about the document.<br>
</blockquote>
<div><br>
</div>
<div>Oh, so you're suggesting adding another phase to the process: IESG edu=
cation. &nbsp;OK.</div>
</blockquote>
<br>
</div>
<div>I don't speak for Dave, but it makes sense that when a document reache=
s the IESG telechat, the questions to be asked are (1) Did this get suffici=
ent review by sufficiently capable people, and (2) Has the process been fol=
lowed, including have all issues
 been addressed.</div>
<div><br>
</div>
<div>The time for asking whether the group has considered making this field=
 fixed length instead of variable, or whether RFC 2119 language is used in =
an appropriate way, or whether the protocol is extensible enough is at IETF=
 last call. This is true of any
 participants, and ADs can do this too, regardless of whether their presenc=
e might intimidate the crowd. It could even be that if ADs voice their conc=
erns at that time, others might join in, making the LC time more useful and=
 less about just waiting two or
 four weeks.</div>
<div><br>
</div>
<div>There is a problem, though, that this will increase the load on ADs. O=
ther concerns raised during IETF LC may lead to revised I-Ds, which the ADs=
 will need to re-read (or at least look at the diff). I don't know how sign=
ificant this extra work would be,
 but it would come at a time that we're thinking of ways to reduce AD workl=
oad. It might also require prolonging the LC time, because there would be a=
ctual discussion in it.</div>
<div><br>
</div>
<div>Yoav</div>
<div><br>
</div>
<br>
</body>
</html>

--_000_F46B3DFBDC3C4AD48D1A5694E89D6E9Fcheckpointcom_--

From stephen.farrell@cs.tcd.ie  Thu May 16 13:56:31 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C42721F8E9D for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKEISCimwriM for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:56:07 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A3D9921F8E96 for <ietf@ietf.org>; Thu, 16 May 2013 13:56:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 9C872BE83; Thu, 16 May 2013 21:55:38 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SBhAqpxqGirB; Thu, 16 May 2013 21:55:34 +0100 (IST)
Received: from [10.87.48.3] (unknown [86.46.22.170]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id CA58ABE5C; Thu, 16 May 2013 21:55:33 +0100 (IST)
Message-ID: <519547BB.5010305@cs.tcd.ie>
Date: Thu, 16 May 2013 21:55:23 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
In-Reply-To: <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 20:56:31 -0000

I think Dave's idea is worth looking at, but have one comment:

On 05/16/2013 09:46 PM, Yoav Nir wrote:
> There is a problem, though, that this will increase the load on ADs.

There is that. But don't forget that ADs mostly read everything
in IESG review and often comment. Even leaving aside DISCUSSes,
if every IETF LC draft got a bunch of AD review comments, then
the IETF LC would be much busier than now. And its in the nature
of IETFers to chime in. So this would I suspect increase everyone's
load, if it works, and not just ADs.

Still worth a look though.

S.

From tobias.gondrom@gondrom.org  Thu May 16 13:56:40 2013
Return-Path: <tobias.gondrom@gondrom.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 4D83421F8EFD for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:56:40 -0700 (PDT)
X-Quarantine-ID: <Qsla8fJeqr8N>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char E2 hex): CC: ... draft-housley-rfc2050bis\342\200\213.all@tools.ie[...]
X-Spam-Flag: NO
X-Spam-Score: -95.361
X-Spam-Level: 
X-Spam-Status: No, score=-95.361 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qsla8fJeqr8N for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 13:56:40 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id D515A21F8EF7 for <ietf@ietf.org>; Thu, 16 May 2013 13:56:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=vBmZbwuugE5gI1e/2gAW0wD86teA31n/pNoq4Dr+BFbtXY/BH4xDhwzT+98xRFonZQKO70r/8fR9n6ik6Q1MwZKtomSr+rBUAynra0jARsu6XoAYBnxtEziUGxbDV8A0; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:X-Enigmail-Version:Content-Type;
Received: (qmail 32049 invoked from network); 16 May 2013 22:56:18 +0200
Received: from e181126254.adsl.alicedsl.de (HELO ?192.168.1.227?) (85.181.126.254) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 16 May 2013 22:56:18 +0200
Message-ID: <519547F2.20100@gondrom.org>
Date: Thu, 16 May 2013 21:56:18 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: apps-discuss@ietf.org
Subject: APPSDIR review of draft-housley-rfc2050bis-01
X-Enigmail-Version: 1.5.1
Content-Type: multipart/alternative; boundary="------------070308040604090302050109"
Cc: draft-housley-rfc2050bisâ€‹.all@tools.ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 20:56:40 -0000

This is a multi-part message in MIME format.
--------------070308040604090302050109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi,

I have been selected as the Applications Area Directorate reviewer for
this draft (for background on appsdir, please see â€‹
http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ).
Please resolve these comments along with any other Last Call comments
you may receive. Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-housley-rfc2050bis-01
Title: The Internet Numbers Registry System
Reviewer: Tobias Gondrom
Review Date: May-16

Status: Informational

Summary: I believe the draft is ready for publication.

Review:
0. The document is well written and I very much like that the document
is short and concise.

Comments:
1. One of two key sentences I took from the document is that its
self-described scope is "only documenting" the status quo. See Section
1: "does not propose any changes...., but it does provide information
about the current... system".
When reading this, one question the reader might consider is whether to
agree with this scope-self-limitation.
For my review, I followed this set scope, so the question is then only
does the ID reflect reality and provide sufficient information. My
answer to that is "yes".

2. And the second key sentence is from section 5:
...  "specified in the IETF/IAB/ICANN MOU [RFC2860], discussions
regarding the evolution of the Internet Numbers Registry System
structure, policy, and processes are to take place within the ICANN
framework and will respect ICANN's core values [ICANNBL]." So basically
fully delegating that responsibility to ICANN.

Personally IMHO, I would like to encourage the editors and the IETF to
actually take a more strategic and pro-active approach and consider also
whether any guided changes beyond status quo could improve the situation.
Are our assumptions for the current system still true? Can we reflect
about why certain aspects are as they are and whether we can learn from
the past about any improvements we should actively explore or consider?
A pro-active review of the overall situation including #1 and #2 might
be useful?

Best regards, Tobias





--------------070308040604090302050109
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Arial">Hi, <br>
    </font><br>
    I have been selected as the Applications Area Directorate reviewer
    for this draft (for background on appsdir, please see <a
      class="ext-link"
href="http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate"><span
        class="icon">â€‹</span>http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate</a>
    ).
    Please resolve these comments along with any other Last Call
    comments you may receive. Please wait for direction from your
    document shepherd or AD before posting a new version of the draft.<br>
    <br>
    <font face="Arial">Document: draft-housley-rfc2050bis-01<br>
      Title: The Internet Numbers Registry System<br>
      Reviewer: Tobias Gondrom<br>
      Review Date: May-16<br>
      <br>
      Status: Informational<br>
      <br>
      Summary: I believe the draft is ready for publication. <br>
      <br>
      Review: <br>
      0. The document is well written and I very much like that the
      document is short and concise.<br>
      <br>
      Comments: <br>
      1. One of two key sentences I took from the document is that its
      self-described scope is "only documenting" the status quo. See
      Section 1: "does not propose any changes...., but it does provide
      information about the current... system". <br>
      When reading this, one question the reader might consider is
      whether to agree with this scope-self-limitation. <br>
      For my review, I followed this set scope, so the question is then
      only does the ID reflect reality and provide sufficient
      information. My answer to that is "yes". <br>
      <br>
      2. And the second key sentence is from section 5:<br>
      ...Â  "specified in the IETF/IAB/ICANN MOU [RFC2860], discussions
      regarding the evolution of the Internet Numbers Registry System
      structure, policy, and processes are to take place within the
      ICANN framework and will respect ICANN's core values [ICANNBL]."
      So basically fully delegating that responsibility to ICANN.<br>
      <br>
      Personally IMHO, I would like to encourage the editors and the
      IETF to actually take a more strategic and pro-active approach and
      consider also whether any guided changes beyond status quo could
      improve the situation. <br>
      Are our assumptions for the current system still true? Can we
      reflect about why certain aspects are as they are and whether we
      can learn from the past about any improvements we should actively
      explore or consider? A pro-active review of the overall situation
      including #1 and #2 might be useful?<br>
      <br>
    </font><font face="Arial">Best regards, Tobias<br>
      <br>
      <br>
      <br>
      <br>
    </font>
  </body>
</html>

--------------070308040604090302050109--

From fred@cisco.com  Thu May 16 14:00:27 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FB3421F8E8E for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.191
X-Spam-Level: 
X-Spam-Status: No, score=-110.191 tagged_above=-999 required=5 tests=[AWL=0.408, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jk7qxV6jMlU8 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:00:21 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id CF8A821F8503 for <ietf@ietf.org>; Thu, 16 May 2013 14:00:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1106; q=dns/txt; s=iport; t=1368738021; x=1369947621; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=iu8I79llWHKe55Dte5yv6zDbL7khFT9IEKa8YblBGII=; b=BIyB5CBSNW3weKfqcV4qwETepJlwry/rOn7Q73L3Q9gfhfPhubopSVNc 5kHi8UXtHVC7f30D0x46FMZ6jUwLeUw1jNWu3NqLRmfh5yjTCVM/HJbHO jYB+049OwWYQA5j4PU/0K4O8eYjhPOjTht9FRW+V3hccqzu9n3cHLBgSj E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAJdHlVGtJV2c/2dsb2JhbABbgwfCBn4WdIIfAQEBAwEdHTEOBQsCAQgiFBAyJQIEDgUIh34GvD+ObAIxB4J0YQOoeIMQgiY
X-IronPort-AV: E=Sophos;i="4.87,686,1363132800"; d="scan'208";a="211276108"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 16 May 2013 21:00:21 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r4GL0JEp032546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 May 2013 21:00:21 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.02.0318.004; Thu, 16 May 2013 16:00:19 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUlHOqf8BfNX65UGsgZf7eymV45kIV0OAgABIpYA=
Date: Thu, 16 May 2013 21:00:19 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8EA92F@xmb-rcd-x09.cisco.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <027301ce5254$0b8689a0$22939ce0$@olddog.co.uk>
In-Reply-To: <027301ce5254$0b8689a0$22939ce0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A3B7A66AA3320E47ACB699C92DDE9813@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 21:00:27 -0000

On May 16, 2013, at 9:40 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> On the whole, I am told that if an AD weighs in with her comments during =
working
> group last call, her fearsome personality may overwhelm some of the WG
> participants and she may dominate the WG consensus.

There may be places where that happens, but I would be surprised if it happ=
ened in my working group. I think it is fair to say that the AD (or an IAB =
member, or someone who has recognized expertise on the topic) is likely to =
be listened to more carefully than some others might. Heck, I'm careful whe=
n I make a technical comment on a document in my working group, flagging it=
 with "</chair>" to ensure that it is seen as intended - a comment by a com=
petent practitioner of the art, not a process remark or an attempt to trump=
 some other view. Speaking personally, I would prefer to see those comments=
 in the WGLC, not IETF Last Call, if we can make that happen. For example, =
I'd like to get directorate reviews done (gen-art, security directorate, et=
c) in the timeframe of WGLC.=

From brian.e.carpenter@gmail.com  Thu May 16 14:04:39 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4436221F8956 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYOtl6XpuUG6 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:04:33 -0700 (PDT)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4774721F8C1A for <ietf@ietf.org>; Thu, 16 May 2013 14:04:33 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id ld10so2896237pab.10 for <ietf@ietf.org>; Thu, 16 May 2013 14:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=TyMPt1zYQd2UZ56neuAWQsSh8aBSvHTAEB7YFeIFdjg=; b=B9kTYGg+UmfC9NBXoMo7ORzSM5pYfzm0C6xm/eqFFOugw3sQ7BgAJ4/ZauzpvQRAp+ MEgXlgfnxyX6XZIzgDeIhBtUmdnXX+aqEXjH8iqrdn32+y+hIB3ieJHFOLnAW2TZejcL 3yg5PJSP09ecuh73AfJvFbL2I8eznEe2Y6fswIu7F+wov0UYjV3fJFieiVPWLDpx1nqm WYcjh4GEQZHcxoaEFGKtTptqM8MaK7U3w7/+L964vciBAkM08jRD5rOVhpxTqfTLKpXh R6ECsy/LsY87gbjePUTHIROrHrm0sI1isDhhO1ROFiMrbEYmyHZ7Ule64Jt/nF9iD2WV s7jA==
X-Received: by 10.66.118.79 with SMTP id kk15mr13973176pab.193.1368738272943;  Thu, 16 May 2013 14:04:32 -0700 (PDT)
Received: from [192.168.1.4] (29.131.252.27.dyn.cust.vf.net.nz. [27.252.131.29]) by mx.google.com with ESMTPSA id uv1sm8138827pbc.16.2013.05.16.14.04.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 14:04:31 -0700 (PDT)
Message-ID: <519549E6.5050405@gmail.com>
Date: Fri, 17 May 2013 09:04:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF	process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net>
In-Reply-To: <519507ED.4090805@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
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: Thu, 16 May 2013 21:04:39 -0000

Dave,

On 17/05/2013 04:23, Dave Crocker wrote:
...
> The problem here is that basic reviewing is being done by the ADs too
> late in the process.  

You are making a lot of assumptions in that sentence. At least these:

1. "Basic" reviewing means ....

2. At some stage before approval, ADs should perform basic reviewing.

3. Doing basic reviewing after the document has completed IETF LC
   is too late.

Now, if "basic" reviewing means (A) "looking for fundamental flaws"
that is one thing. If it means (B) "getting a general understanding
of the topic" it's another. I'm really not sure which you mean.

> We are making the mistake of having ADs be exempt
> from IETF Last Call, and allowing them to be unprepared for the IESG
> vote.  So we are combining "education" with "voting".  That's a paradigm
> error.
> 
> By the time the IESG schedules the vote, ADs need to already have
> educated themselves about the document.

Ah, maybe you mean basic (B). Well, I think this is a totally
unrealistic expectation. There are too many drafts on too diverse
a range of subjects for ADs to educate themselves at the time
of IETF LC, which may be weeks or months before a draft hits
the agenda. (I'm not talking about the sponsoring AD or her
co-AD, of course: they are presumed to be aware of what's going
on in their area.) Busy people are deadline driven, and the
IESG agenda is an imminent deadline for ADs in a way that an
IETF LC in another Area isn't.

> Of course, the IESG discussion during the voting process well might
> uncover an actual, serious issue with the document; 

And that's basic (B). I think we all agree that it's unfortunate
if a basic flaw shows up during the IESG ballot phase, but
please don't blame the IESG for that. Blame the WG and the
IETF as a whole for failing to pick it up during WG LC and
IETF LC. Thank the IESG for finding it.

> this should be
> exceptional and it should be an issue that the /IESG/ agrees needs to be
> resolved and it means that voting should not take place until it is. But
> that is quite different from the usual "let's talk about it" kind of
> Discuss imposed by individual ADs.

I'm not quite sure what you're saying here, but I think you're
saying that the majority of clarity and cross-area issues should
be picked up earlier. I couldn't agree more, but don't expect the
over-worked IESG to fix that. The rest of us need to fix that.

> 
> So here's a simple proposal that pays attention to AD workload and
> includes a simple efficiency hack:
> 
>      When the IETF Last Call is issued, wait a few days, to see whether
> any serious issues are raised by the community.  The really serious ones
> usually are raised quickly.  If there are none, it's pretty certain the
> document will advance to an IESG vote.  That leaves 7-10 days of IETF
> Last Call for ADs to get educated and ask questions, just like everyone
> else.

Which, as I said above, is a totally unrealistic expectation.

> Jari has expressed the goal of having AD concerns be raised more
> publicly.  Moving AD review and comment to the IETF Last Call venue
> nicely accomplishes this, too.

Thanks but no thanks. My mail is full enough with discussion of drafts
I will never read as it is. AD reviews should certainly go to the
WG list unless they are only nits, but isn't that what everybody does
anyway?

> 
> 
> 
> On 5/15/2013 8:55 AM, Thomas Narten wrote:
>> 1) Discuss criteria should be principles, not rigid rules. The details
>> of the issue at hand always matter, and it will sometimes come down to
>> judgement calls where reasonable individuals just might disagree.
> 
> We've been doing protocol specification for 40 years.  If we can't
> codify the major concerns that warrant blocking advancement of a
> protocol, we're just being lazy.  Really.  That a given situation might
> cause the IESG to decide to enhance the list does not mean that the list
> shouldn't seek to be complete and precise and that ADs be held to it.

I agree with Thomas. We need to be able to apply common sense. Rules
and targets are the enemy of common sense.

> At every turn, the approach we've taken to the IESG review and approval
> process is to limit actual accountability to the community.  Everyone is
> well-intentioned, but really this makes the process a matter of
> personalities and not the rigor of serious professionalism.
> 
> The IESG's process is far, far better than it was 10-15 years ago, but
> it still lacks meaningful predictability and serious accountability; it

I find that the tracker in its present state has substantially improved
both visibility and predictability.

> is not reasonable for the process to require that authors and chairs
> take the initiative of complaining when an AD is being problematic.

Huh? Who else will complain?

> In terms of quality assurance, the idea that we have a process that
> relies on the sudden insight of a single AD, at the end of a many-month
> process, is broken.  It's fine if that person sees something that
> everyone else has missed until then, but that is quite different from
> designing a process that is claimed to rely on it.

It's supposed to be a backstop, and I think we concur that too many
issues are being left for the backstop.

It's not the IESG that is falling down on the job. It's the rest
of us, who keep sending defective documents to the IESG.

> And of course, the reality is that we allow bad specs out the door all
> the time; we just allow fewer of them than many/most other standards
> bodies...

Hubris alert!

   Brian

From housley@vigilsec.com  Thu May 16 14:21:37 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F68621F8A4E; Thu, 16 May 2013 14:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4cvmqkSUmiW3; Thu, 16 May 2013 14:21:32 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 7E37F21F8F3E; Thu, 16 May 2013 14:21:31 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 1C9C6F24070; Thu, 16 May 2013 17:21:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 4yallx-XCW1w; Thu, 16 May 2013 17:21:27 -0400 (EDT)
Received: from [192.168.2.109] (pool-96-241-163-208.washdc.fios.verizon.net [96.241.163.208]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1F13AF2406E; Thu, 16 May 2013 17:21:33 -0400 (EDT)
Subject: Re: APPSDIR review of draft-housley-rfc2050bis-01
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-73--409934570
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <519547F2.20100@gondrom.org>
Date: Thu, 16 May 2013 17:21:29 -0400
Message-Id: <52506592-DBD1-485F-9EDD-39407B4887A4@vigilsec.com>
References: <519547F2.20100@gondrom.org>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org, iesg@ietf.org, apps-discuss@ietf.org, =?utf-8?Q?draft-housley-rfc2050bis=E2=80=8B=2Eall?=@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: Thu, 16 May 2013 21:21:37 -0000

--Apple-Mail-73--409934570
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Tobias:

Thanks for the review.  Really, the delegation id to the RIRs. which in =
turn use the ICANN ASO to establish global policy.

Thanks again,
  Russ


On May 16, 2013, at 4:56 PM, Tobias Gondrom wrote:

> Hi,=20
>=20
> I have been selected as the Applications Area Directorate reviewer for =
this draft (for background on appsdir, please see =
=E2=80=8Bhttp://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDir=
ectorate ). Please resolve these comments along with any other Last Call =
comments you may receive. Please wait for direction from your document =
shepherd or AD before posting a new version of the draft.
>=20
> Document: draft-housley-rfc2050bis-01
> Title: The Internet Numbers Registry System
> Reviewer: Tobias Gondrom
> Review Date: May-16
>=20
> Status: Informational
>=20
> Summary: I believe the draft is ready for publication.=20
>=20
> Review:=20
> 0. The document is well written and I very much like that the document =
is short and concise.
>=20
> Comments:=20
> 1. One of two key sentences I took from the document is that its =
self-described scope is "only documenting" the status quo. See Section =
1: "does not propose any changes...., but it does provide information =
about the current... system".=20
> When reading this, one question the reader might consider is whether =
to agree with this scope-self-limitation.=20
> For my review, I followed this set scope, so the question is then only =
does the ID reflect reality and provide sufficient information. My =
answer to that is "yes".=20
>=20
> 2. And the second key sentence is from section 5:
> ...  "specified in the IETF/IAB/ICANN MOU [RFC2860], discussions =
regarding the evolution of the Internet Numbers Registry System =
structure, policy, and processes are to take place within the ICANN =
framework and will respect ICANN's core values [ICANNBL]." So basically =
fully delegating that responsibility to ICANN.
>=20
> Personally IMHO, I would like to encourage the editors and the IETF to =
actually take a more strategic and pro-active approach and consider also =
whether any guided changes beyond status quo could improve the =
situation.=20
> Are our assumptions for the current system still true? Can we reflect =
about why certain aspects are as they are and whether we can learn from =
the past about any improvements we should actively explore or consider? =
A pro-active review of the overall situation including #1 and #2 might =
be useful?
>=20
> Best regards, Tobias
>=20
>=20
>=20
>=20


--Apple-Mail-73--409934570
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Tobias:<div><br></div><div>Thanks for the review. &nbsp;Really, the =
delegation id to the RIRs. which in turn use the ICANN ASO to establish =
global policy.</div><div><br></div><div>Thanks again,</div><div>&nbsp; =
Russ</div><div><br></div><div><br><div><div>On May 16, 2013, at 4:56 PM, =
Tobias Gondrom wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3DUTF-8" =
http-equiv=3D"Content-Type">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <font face=3D"Arial">Hi, <br>
    </font><br>
    I have been selected as the Applications Area Directorate reviewer
    for this draft (for background on appsdir, please see <a =
class=3D"ext-link" =
href=3D"http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDire=
ctorate"><span =
class=3D"icon">=E2=80=8B</span>http://trac.tools.ietf.org/area/app/trac/wi=
ki/ApplicationsAreaDirectorate</a>
    ).
    Please resolve these comments along with any other Last Call
    comments you may receive. Please wait for direction from your
    document shepherd or AD before posting a new version of the =
draft.<br>
    <br>
    <font face=3D"Arial">Document: draft-housley-rfc2050bis-01<br>
      Title: The Internet Numbers Registry System<br>
      Reviewer: Tobias Gondrom<br>
      Review Date: May-16<br>
      <br>
      Status: Informational<br>
      <br>
      Summary: I believe the draft is ready for publication. <br>
      <br>
      Review: <br>
      0. The document is well written and I very much like that the
      document is short and concise.<br>
      <br>
      Comments: <br>
      1. One of two key sentences I took from the document is that its
      self-described scope is "only documenting" the status quo. See
      Section 1: "does not propose any changes...., but it does provide
      information about the current... system". <br>
      When reading this, one question the reader might consider is
      whether to agree with this scope-self-limitation. <br>
      For my review, I followed this set scope, so the question is then
      only does the ID reflect reality and provide sufficient
      information. My answer to that is "yes". <br>
      <br>
      2. And the second key sentence is from section 5:<br>
      ...&nbsp; "specified in the IETF/IAB/ICANN MOU [RFC2860], =
discussions
      regarding the evolution of the Internet Numbers Registry System
      structure, policy, and processes are to take place within the
      ICANN framework and will respect ICANN's core values [ICANNBL]."
      So basically fully delegating that responsibility to ICANN.<br>
      <br>
      Personally IMHO, I would like to encourage the editors and the
      IETF to actually take a more strategic and pro-active approach and
      consider also whether any guided changes beyond status quo could
      improve the situation. <br>
      Are our assumptions for the current system still true? Can we
      reflect about why certain aspects are as they are and whether we
      can learn from the past about any improvements we should actively
      explore or consider? A pro-active review of the overall situation
      including #1 and #2 might be useful?<br>
      <br>
    </font><font face=3D"Arial">Best regards, Tobias<br>
      <br>
      <br>
      <br>
      <br>
    </font>
  </div>

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

--Apple-Mail-73--409934570--

From rdroms.ietf@gmail.com  Thu May 16 14:56:53 2013
Return-Path: <rdroms.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 A932C21F8797 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oMjUnvwPjwN3 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:56:48 -0700 (PDT)
Received: from mail-qe0-f44.google.com (mail-qe0-f44.google.com [209.85.128.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2C521F8733 for <ietf@ietf.org>; Thu, 16 May 2013 14:56:48 -0700 (PDT)
Received: by mail-qe0-f44.google.com with SMTP id s14so2314637qeb.3 for <ietf@ietf.org>; Thu, 16 May 2013 14:56:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=Fan8RawQ8OrgRaU8du5tEXBFLy4PuyipCjUvQebW74o=; b=ud78Ce/5Hjowdpu072ckTfCYwa2NMj3zUEGdvUE74A0/a1IcHPodU5TxWntjiMDXZI efGHf0igjv3poCzxTtOBrJWUEoK0iCKN8kdvHX+kr4BA5vbaiPbqzccBRARUTg2KEc+v Mj/VmpMN24DNnxq9XBphMOO9FSwfqEokURFAtYxHH9tZSnoXyJd0aZl7FnQDSQVHBmzD lV6oI+GkWYHQlLj9tIRFsbskOPWvy3wpNV9Mr+MvLvZsX3xrPbtXr8qiXOy856mYLgVd 6B9ApEsm9Nyf1C5RLQDDQap3cltBcJ9ooY329N19e6Ro2BYOtfsdKsRr6W5KD02rmAkb /oNg==
X-Received: by 10.224.191.9 with SMTP id dk9mr34560880qab.12.1368741403553; Thu, 16 May 2013 14:56:43 -0700 (PDT)
Received: from ?IPv6:2001:420:2481:20:4158:6507:a429:a451? ([2001:420:2481:20:4158:6507:a429:a451]) by mx.google.com with ESMTPSA id l13sm9390630qaj.9.2013.05.16.14.56.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 14:56:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8EA92F@xmb-rcd-x09.cisco.com>
Date: Thu, 16 May 2013 17:56:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <26F4E41A-6DAB-480F-9E14-C7A3F7D997CC@gmail.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <027301ce5254$0b8689a0$22939ce0$@olddog.co.uk> <8C48B86A895913448548E6D15DA7553B8EA92F@xmb-rcd-x09.cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1503)
Cc: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>, "<ietf@ietf.org>" <ietf@ietf.org>, "<dcrocker@bbiw.net>" <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: Thu, 16 May 2013 21:56:53 -0000

On May 16, 2013, at 5:00 PM 5/16/13, "Fred Baker (fred)" =
<fred@cisco.com> wrote:

>=20
> On May 16, 2013, at 9:40 AM, Adrian Farrel <adrian@olddog.co.uk> =
wrote:
>=20
>> On the whole, I am told that if an AD weighs in with her comments =
during working
>> group last call, her fearsome personality may overwhelm some of the =
WG
>> participants and she may dominate the WG consensus.
>=20
> There may be places where that happens, but I would be surprised if it =
happened in my working group. I think it is fair to say that the AD (or =
an IAB member, or someone who has recognized expertise on the topic) is =
likely to be listened to more carefully than some others might. Heck, =
I'm careful when I make a technical comment on a document in my working =
group, flagging it with "</chair>" to ensure that it is seen as intended =
- a comment by a competent practitioner of the art, not a process remark =
or an attempt to trump some other view. Speaking personally, I would =
prefer to see those comments in the WGLC, not IETF Last Call, if we can =
make that happen. For example, I'd like to get directorate reviews done =
(gen-art, security directorate, etc) in the timeframe of WGLC.

I think Fred is returning to an earlier theme here, when he asks for =
earlier review.

Perhaps, as has been already suggested in this thread, we should think =
about SIRSbis?=20

First, from draft-carpenter-icar-sirs-01:

     The procedure described in this document is intended to
     solve, or palliate, a number of related problems that
     have been observed in the IETF process [PROBLEM]:

          *    submission of documents to the IESG that
               still have significant problems (leading
               to delay)

          *    failure to detect fundamental problems
               and Internet- wide issues at an early
               stage

     Particularly because of the second point, it is
     impossible to resolve these problems simply by
     giving additional responsibility to working groups
     themselves. An additional procedure is needed.

In my opinion, it's important to assign responsibility (and =
accountability) to all WGs for producing publication-ready documents.  I =
agree that some additional work is needed before WGs send documents to =
the IESG.  Perhaps we can accomplish these goals through reorganizing =
the work we are=20

I suggest we might want to combine the need for more responsibility with =
the discussion of a new "really close to being ready" document state.  =
However, rather than a new document state, suppose we codify the =
expectation that a document that has passed WG last call is essentially =
ready-to-publish?  Correspondingly, any significant problems found in a =
document after WG last call would be considered a serious defect.

   Discussion:  I realize that, elsewhere in this thread, it has been
   asserted (or at least implied), that WGs already have this =
responsibility
   and DISCUSSes on document are usually unnecessary.  In practice, =
while
   there may still be unnecessary DISCUSSes, my experience as AD was =
that
   most DISCUSSes were appropriate and each one referred to a problem =
that
   the WG had missed.

Let's get all the expert review possible - directorate, AD, cross-area - =
in the WG last call review.  What pops out *should* be ready for =
publication.  Any issues raised by these reviews in WG last call will be =
exposed to and can be discussed by the WG at large, rather than being =
buried in the noise of IETF last call discussions or being fixed in more =
focused discussions among the IESG and the document authors.  This =
procedure diverges some from draft-carpenter-icar-sirs-01, in that it =
doesn't add a new form of review process.  Instead, it reschedules =
reviews that were going to take place anyway earlier in the process, so =
there is little or no new work added to the document publication =
process.

Perhaps the WG chairs would want to assign document shepherds earlier in =
the process, as well, investing the document shepherds with the =
responsibility of getting the right reviews and advising the WG chairs =
as to the readiness of the document for advancement.

Any WGs willing to volunteer as experimental subjects?  There is really =
no new process to invent ... it's mostly a matter of realigning =
expectations and responsibilities out to=20

- Ralph


From moore@network-heretics.com  Thu May 16 14:58:46 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC7921F85CE for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:58:46 -0700 (PDT)
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.091,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWi3RX0SHRI8 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 14:58:41 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 2C64B21F855A for <ietf@ietf.org>; Thu, 16 May 2013 14:58:41 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id EE95520CFD; Thu, 16 May 2013 17:58:38 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Thu, 16 May 2013 17:58:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=QW280F2tg9NO35g/GTk2Kt sFXDY=; b=tmRcenq5/Th/PcbH5b1KeLHLVd3bFMXDgBwFN0PQtjvrHBfQpDSswI zv5UK8Z2wiJ2HjjhVw7bAHs0FwFUNWvL/QsxuicUIh+6kuju86W7GcE5xvOBtYiR xxwBaKz5vdo06aymMoMCZHmyVbIGqU1s4+c1S7qudUWEci3uYSY60=
X-Sasl-enc: wd52xFCVcP/Ss/uDJmDHCgTJM8CjdyKj5GUDyNrBMWYX 1368741517
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 44E532001CF; Thu, 16 May 2013 17:58:37 -0400 (EDT)
Message-ID: <51955685.2060009@network-heretics.com>
Date: Thu, 16 May 2013 17:58:29 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
In-Reply-To: <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 21:58:46 -0000

On 05/16/2013 04:46 PM, Yoav Nir wrote:
> The time for asking whether the group has considered making this field 
> fixed length instead of variable, or whether RFC 2119 language is used 
> in an appropriate way, or whether the protocol is extensible enough is 
> at IETF last call. 

Actually the time for asking these questions is long before IETF-wide 
Last Call.  We need widespread review of proposals for standards-track 
documents long before a WG thinks it's finished with those documents.   
It's a gaping hole in our process.

Fix that problem, and most of the conflicts between IESG and WGs that 
surround DISCUSS votes will go away.

Keith


From rdroms.ietf@gmail.com  Thu May 16 15:06:43 2013
Return-Path: <rdroms.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 A523821F8F15 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oLJsJdJno2dg for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:06:42 -0700 (PDT)
Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4427E21F8F17 for <ietf@ietf.org>; Thu, 16 May 2013 15:06:42 -0700 (PDT)
Received: by mail-qa0-f41.google.com with SMTP id ia15so25470qab.14 for <ietf@ietf.org>; Thu, 16 May 2013 15:06:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=3dRrivonyZDQBkO6bvjNKJO5EOeCj+S15bV48WVhGGw=; b=ONsGVhFq9aaQcFYBz76G1U6/torGlJNGN6EOyjyQh0xWYHKK9X2EdpIq/jmJrYwCao 5Y0tZ9CXk9ZNW7yzQgraK3Cj/H7+nWd9t1a3XNVktCYbhfNrLVNq28yqmDtEVgjV6Agx om/5dIqnt033KTE50Jxic44SCnNK+DKlotnNxNAg4GF65qn4idl+KbU4CmpVcfA5K1w5 HymDC9ZUXbCqm/dRI01cdbtZZTSksX5FC1ZS5QbepcpMVI/i4rDxjGxldAhkLshx1Lnb cSJzmtOGlwk5ImgtB7PUioe8Tpxu6QpQd3rNni9x4HvxZ31l2SyTl0l01qQFylrLbSq3 k9Xg==
X-Received: by 10.229.167.131 with SMTP id q3mr13822491qcy.133.1368741997232;  Thu, 16 May 2013 15:06:37 -0700 (PDT)
Received: from rtp-rdroms-8913.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id u5sm8800317qeu.6.2013.05.16.15.06.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 15:06:36 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <519507ED.4090805@dcrocker.net>
Date: Thu, 16 May 2013 18:06:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <465FC35C-9594-47FC-8CCA-8460943E88D7@gmail.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
Cc: Farrel Adrian <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: Thu, 16 May 2013 22:06:43 -0000

Dave - I hope you'll indulge my selective quoting as I have a couple of =
specific points to address.  My apologies if I end up quoting you out of =
context...

On May 16, 2013, at 12:23 PM 5/16/13, Dave Crocker <dhc@dcrocker.net> =
wrote:

> [...]
>=20
> So here's a simple proposal that pays attention to AD workload and =
includes a simple efficiency hack:
>=20
>     When the IETF Last Call is issued, wait a few days, to see whether =
any serious issues are raised by the community.  The really serious ones =
usually are raised quickly.  If there are none, it's pretty certain the =
document will advance to an IESG vote.  That leaves 7-10 days of IETF =
Last Call for ADs to get educated and ask questions, just like everyone =
else.
>=20
> Jari has expressed the goal of having AD concerns be raised more =
publicly.  Moving AD review and comment to the IETF Last Call venue =
nicely accomplishes this, too.

I just posted elsewhere a suggestion to move this review even earlier, =
to WG last call.  Accomplishes most of the same ends, while putting the =
discussion in front of the IETF participants who are, presumably, most =
invested in the resulting document.

>=20
>=20
> [...]
> In terms of quality assurance, the idea that we have a process that =
relies on the sudden insight of a single AD, at the end of a many-month =
process, is broken.  It's fine if that person sees something that =
everyone else has missed until then, but that is quite different from =
designing a process that is claimed to rely on it.

As you and I have discussed in person, I am 100% in agreement with this =
comment.  As much as I liked to think of myself, when I was an AD, as a =
rock-god Network Expert with complete and in-depth insight into every =
document I reviewed, I know the reality was that any problems I might =
have found were related to the old observation that "even a blind =
squirrel finds an acorn occasionally".
>=20
> And of course, the reality is that we allow bad specs out the door all =
the time; we just allow fewer of them than many/most other standards =
bodies...

You're such an optimist.

- Ralph

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


From rdroms.ietf@gmail.com  Thu May 16 15:07:55 2013
Return-Path: <rdroms.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 1F4A411E80D1 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:07:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RYMc7gdzz7ig for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:07:54 -0700 (PDT)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id C38F811E80A3 for <ietf@ietf.org>; Thu, 16 May 2013 15:07:53 -0700 (PDT)
Received: by mail-qc0-f181.google.com with SMTP id s10so1355006qcv.40 for <ietf@ietf.org>; Thu, 16 May 2013 15:07:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=vwRq05rw2lhtsiJalmwnGZYOK0DuEoFnioOfxvw1NeU=; b=LReYcA+lY8IFBICxXDJIC3DTli8pXeKxxEH5SDZHV6+z2dj2q37JPiHAwD1Jirmcqz c9mQlEWH1QidNgDRTnn+qn0x18aZgcv+lcPOQnguWWdIQAKfOd1YrOCnG1BhE20iDd6/ jQwJVqY1kZrMu9151xdpJUUpk+EiBiC/vsFTPAUUKWBX+wm3+mKbTsdk2+fXbkKZf5ul bd2N3cVAA3kFUSrhKo0lH1/i7BSuyFEb1g916AxWhooJQgBCGXx6M4ajFwK5aq3aTCbN kOnMzcO/PukGWOPFJxNCMWoRSShG2oGfNd4P/JaDfNu/J9Fb2/hGCEDvHlaJfzLtNpAX VOdQ==
X-Received: by 10.224.30.76 with SMTP id t12mr33740362qac.24.1368742073258; Thu, 16 May 2013 15:07:53 -0700 (PDT)
Received: from rtp-rdroms-8913.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id 5sm9449383qap.11.2013.05.16.15.07.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 16 May 2013 15:07:52 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <51955685.2060009@network-heretics.com>
Date: Thu, 16 May 2013 18:07:50 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <ACB04092-1BCE-4E7E-9EB9-508472F9ACBB@gmail.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
Cc: Farrel Adrian <adrian@olddog.co.uk>, Crocker Dave <dcrocker@bbiw.net>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 22:07:55 -0000

On May 16, 2013, at 5:58 PM 5/16/13, Keith Moore =
<moore@network-heretics.com> wrote:

> On 05/16/2013 04:46 PM, Yoav Nir wrote:
>> The time for asking whether the group has considered making this =
field fixed length instead of variable, or whether RFC 2119 language is =
used in an appropriate way, or whether the protocol is extensible enough =
is at IETF last call.=20
>=20
> Actually the time for asking these questions is long before IETF-wide =
Last Call.  We need widespread review of proposals for standards-track =
documents long before a WG thinks it's finished with those documents.   =
It's a gaping hole in our process.

Hear, hear.

>=20
> Fix that problem, and most of the conflicts between IESG and WGs that =
surround DISCUSS votes will go away.

Well, you might be a little optimistic here, but I agree in theory.

>=20
> Keith
>=20

- Ralph


From joelja@bogus.com  Thu May 16 15:09:54 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5661D21F853A for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.664
X-Spam-Level: 
X-Spam-Status: No, score=-102.664 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kY4k+dWWXHoU for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:09:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2858F11E8110 for <ietf@ietf.org>; Thu, 16 May 2013 15:09:53 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4GM9bav030350 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 16 May 2013 22:09:37 GMT (envelope-from joelja@bogus.com)
Message-ID: <5195591C.2070901@bogus.com>
Date: Thu, 16 May 2013 15:09:32 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>, Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>	<519507ED.4090805@dcrocker.net>	<CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com>	<F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com>
In-Reply-To: <51955685.2060009@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]); Thu, 16 May 2013 22:09:37 +0000 (UTC)
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 22:09:54 -0000

On 5/16/13 2:58 PM, Keith Moore wrote:
> On 05/16/2013 04:46 PM, Yoav Nir wrote:
>> The time for asking whether the group has considered making this 
>> field fixed length instead of variable, or whether RFC 2119 language 
>> is used in an appropriate way, or whether the protocol is extensible 
>> enough is at IETF last call. 
>
> Actually the time for asking these questions is long before IETF-wide 
> Last Call.  We need widespread review of proposals for standards-track 
> documents long before a WG thinks it's finished with those 
> documents.   It's a gaping hole in our process.
>
As a Chair and as an AD I have asked for external and cross area reviews 
of some documents before they were considered for WG acceptance. this 
doesn't apply to all work we processed but it does apply to those where 
we were clear that such input was going to be useful.  One case you can 
see for that today is with capwap extensions that are potentially in 
opsawg.
> Fix that problem, and most of the conflicts between IESG and WGs that 
> surround DISCUSS votes will go away.
Maybe but I wouldn't take that as an article of faith. You're going to 
get pressure for more changes when fresh eyes review something.
> Keith
>


From stpeter@stpeter.im  Thu May 16 15:12:36 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EFB611E80CC for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:12:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOlYM1pao8M8 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:12:31 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 56BE111E80A3 for <ietf@ietf.org>; Thu, 16 May 2013 15:12:31 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id E3FC841116; Thu, 16 May 2013 16:24:36 -0600 (MDT)
Message-ID: <519559CC.9040907@stpeter.im>
Date: Thu, 16 May 2013 16:12:28 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <ACB04092-1BCE-4E7E-9EB9-508472F9ACBB@gmail.com>
In-Reply-To: <ACB04092-1BCE-4E7E-9EB9-508472F9ACBB@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Farrel Adrian <adrian@olddog.co.uk>, "ietf@ietf.org list" <ietf@ietf.org>, Keith Moore <moore@network-heretics.com>, Crocker Dave <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: Thu, 16 May 2013 22:12:36 -0000

On 5/16/13 4:07 PM, Ralph Droms wrote:
> 
> On May 16, 2013, at 5:58 PM 5/16/13, Keith Moore <moore@network-heretics.com> wrote:
> 
>> On 05/16/2013 04:46 PM, Yoav Nir wrote:
>>> The time for asking whether the group has considered making this field fixed length instead of variable, or whether RFC 2119 language is used in an appropriate way, or whether the protocol is extensible enough is at IETF last call. 
>>
>> Actually the time for asking these questions is long before IETF-wide Last Call.  We need widespread review of proposals for standards-track documents long before a WG thinks it's finished with those documents.   It's a gaping hole in our process.
> 
> Hear, hear.

One suggestion I've heard several times is a kind of cross-area buddy
system (e.g., ask or assign someone with clue in Area X to help WG Y in
Area Z early and often with regard to specific issues that are often
addressed in Area X). Unfortunately, this suffers from the same problem
that too many WGs suffer from on their own: participant burnout. But I
still think it's a good idea...

Peter

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



From fred@cisco.com  Thu May 16 15:38:43 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE3BF21F89C3 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.293
X-Spam-Level: 
X-Spam-Status: No, score=-110.293 tagged_above=-999 required=5 tests=[AWL=0.306, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VX+OOZLQ0A9V for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 15:38:38 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6919D21F8411 for <ietf@ietf.org>; Thu, 16 May 2013 15:38:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=851; q=dns/txt; s=iport; t=1368743918; x=1369953518; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ZTG3KC8sq4S/FI9L/gxif+2Dww3f7/cW8S+ns/B51aI=; b=cgESQRj0WUXX8Mr8X+5R6fF0novf19i8fmOeUmBos7f4aYrhQ13k25pZ HmJ68xFA1H/gK/rgxURMi6sM9ZuF2PxqDq3R7krLhZdMwP1KKb0ANv/hF 1QO2LyIJBQSW7lNCVYE04WuGLyuCM+YV2yhgoYGXUvphfe9SAJE/H12Jz g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4FAEpflVGtJXHB/2dsb2JhbABbgwiDLL5afxZ0gh8BAQEDAR1cBQsCAQgOFCQyJQIEDgUIh34GvEuObAIxB4J0YQOIZ6ARgxCCJg
X-IronPort-AV: E=Sophos;i="4.87,686,1363132800"; d="scan'208";a="208526281"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-9.cisco.com with ESMTP; 16 May 2013 22:38:37 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4GMcbkx010154 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 May 2013 22:38:37 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Thu, 16 May 2013 17:38:37 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUlHOqf8BfNX65UGsgZf7eymV45kIb/GAgAAsCgCAAB9nAA==
Date: Thu, 16 May 2013 22:38:36 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8EAC53@xmb-rcd-x09.cisco.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
In-Reply-To: <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8A5FE8DB16A60B4DA12D982AC632B904@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 May 2013 22:38:44 -0000

On May 16, 2013, at 1:46 PM, Yoav Nir <ynir@checkpoint.com> wrote:

> There is a problem, though, that this will increase the load on ADs. Othe=
r concerns raised during IETF LC may lead to revised I-Ds, which the ADs wi=
ll need to re-read (or at least look at the diff). I don't know how signifi=
cant this extra work would be, but it would come at a time that we're think=
ing of ways to reduce AD workload. It might also require prolonging the LC =
time, because there would be actual discussion in it.

If they raise the issue later in a "discuss", will they not have to do this=
 anyway? How does this relate to the timing of the comment or the vehicle b=
y which it is conveyed?

----------------------------------------------------
The ignorance of how to use new knowledge stockpiles exponentially.=20
   - Marshall McLuhan


From wmwang2001@hotmail.com  Thu May 16 20:19:23 2013
Return-Path: <wmwang2001@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F7511E80E4; Thu, 16 May 2013 20:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_25=0.6, J_CHICKENPOX_72=0.6, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s2WrE0dRru2g; Thu, 16 May 2013 20:19:10 -0700 (PDT)
Received: from blu0-omc2-s10.blu0.hotmail.com (blu0-omc2-s10.blu0.hotmail.com [65.55.111.85]) by ietfa.amsl.com (Postfix) with ESMTP id CE02311E80A3; Thu, 16 May 2013 20:19:09 -0700 (PDT)
Received: from BLU0-SMTP270 ([65.55.111.72]) by blu0-omc2-s10.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 May 2013 20:19:08 -0700
X-EIP: [SxqP2hsi4ak11Z+d4Hguy0oujz1dfECN]
X-Originating-Email: [wmwang2001@hotmail.com]
Message-ID: <BLU0-SMTP270A16556E20F95AC04C613C9AC0@phx.gbl>
Received: from WmwangHome ([125.120.80.123]) by BLU0-SMTP270.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 16 May 2013 20:19:06 -0700
From: "Wang,Weiming" <wmwang2001@hotmail.com>
To: "Ben Campbell" <ben@nostrum.com>, <draft-ietf-forces-interop.all@tools.ietf.org>, <jmh@joelhalpern.com>, <adrian@olddog.co.uk>, <forces-chairs@tools.ietf.org>, <wmwang@zjsu.edu.cn>
References: <8EC701FD-4258-4382-9711-B76EFBB3E1BA@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-forces-interop-07
Date: Fri, 17 May 2013 11:19:11 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-OriginalArrivalTime: 17 May 2013 03:19:06.0970 (UTC) FILETIME=[4A4CF3A0:01CE52AD]
Cc: gen-art@ietf.org, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 03:19:24 -0000

SGkgQmVuLCANCg0KVGhhbmsgeW91IHZlcnkgbXVjaCBmb3IgdGhlIHJldmlldyBjb21tZW50cy4g
UGxlYXNlIHNlZSBpbmxpbmUgcmVzcG9uc2VzIGZyb20gYXV0aG9ycyBvZiB0aGUgZG9jdW1lbnQg
b24gdGhlIGNvbW1lbnRzLg0KDQpIaSBTaGVycGhlcmQgYW5kIEFELCANCg0Kd2Ugd2lsbCB1cGRh
dGUgYSB2ZXJzaW9uIHZlcnkgc29vbi4gDQoNCnRoYW5rcyBhIGxvdC4NCldlaW1pbmcNCiANCi0t
LS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0gDQpGcm9tOiAiQmVuIENhbXBiZWxsIiA8YmVuQG5v
c3RydW0uY29tPg0KDQpJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlz
IGRyYWZ0LiBGb3IgYmFja2dyb3VuZCBvbg0KR2VuLUFSVCwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0
DQoNCjxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0
ZmFxPi4NCg0KUGxlYXNlIHJlc29sdmUgdGhlc2UgY29tbWVudHMgYWxvbmcgd2l0aCBhbnkgb3Ro
ZXIgTGFzdCBDYWxsIGNvbW1lbnRzDQp5b3UgbWF5IHJlY2VpdmUuDQoNCkRvY3VtZW50OiBkcmFm
dC1pZXRmLWZvcmNlcy1pbnRlcm9wLTA3DQpSZXZpZXdlcjogQmVuIENhbXBiZWxsDQpSZXZpZXcg
RGF0ZTogMjAxMy0wNS0xMw0KSUVURiBMQyBFbmQgRGF0ZTogMjAxMy0wNS0xMw0KSUVTRyBUZWxl
Y2hhdCBkYXRlOiANCg0KU3VtbWFyeTogVGhpcyBkcmFmdCBpcyBhbG1vc3QgcmVhZHkgZm9yIHB1
YmxpY2F0aW9uIGFzIGFuIGluZm9ybWF0aW9uYWwgUkZDLiBJIGhhdmUgYSBmZXcgbWlub3IgcXVl
c3Rpb25zIGFuZCBlZGl0b3JpYWwgY29tbWVudHMgdGhhdCBtYXkgYmUgd29ydGggY29uc2lkZXJp
bmcgcHJpb3IgdG8gcHVibGljYXRpb24uDQoNCioqKiBNYWpvciBpc3N1ZXM6DQoNCk5vbmUuDQoN
CioqKiBNaW5vciBpc3N1ZXM6DQoNCi0tIFRoZSBkcmFmdCBtZW50aW9ucyBhIGNvdXBsZSBvZiBp
bnN0YW5jZXMgb2YgdGVzdHMgdGhhdCBmYWlsZWQgYmVjYXVzZSBvZiBhbiBpbmNvcnJlY3QgaW1w
bGVtZW50YXRpb24gb3IgZGlmZmVyaW5nIGVuY2Fwc3VsYXRpb24gZm9ybWF0cy4gRG9lcyB0aGlz
IHN1Z2dlc3QgdGhhdCB0aGUgc3BlY2lmaWNhdGlvbnMgc2hvdWxkIGJlIGNsYXJpZmllZD8gSW4g
cGFydGljdWxhciwgaW4gdGhlIGNhc2Ugb2YgZW5jYXBzdWxhdGlvbiBmb3JtYXQgbWlzbWF0Y2gs
IHNob3VsZCB0aGUgc3BlY3MgaW5jbHVkZSBzdHJvbmdlciByZXF1aXJlbWVudHMgdG8gYmUgYWJs
ZSB0byByZWNlaXZlIGFsbCBlbmNhcHN1bGF0aW9uIGZvcm1hdHM/IE9yIHNob3VsZCB0aGUgbnVt
YmVyIG9mIG9wdGlvbnMgYmUgcmVkdWNlZD8NCltSZS4gYnkgzpXOl10gVGhlIHByb3RvY29sIHBy
b3ZpZGVzIGEgbnVtYmVyIG9mIGRpZmZlcmVudCBhcHByb2FjaGVzIA0KW1JlLiBieSBXZWltaW5n
XSBUaGUga2V5IGlzc3VlIGlzIHN0aWxsIGZyb20gdGhlIGRlZXAgdW5kZXJzdGFuZGluZyBvZiB0
aGUgcHJvdG9jb2wgZnJvbSBpbXBsZW1lbnRhdGlvbnMuIEkgc3RpbGwgaGF2ZSBub3Qgc2VlbiBu
ZWVkIGZvciBhbnkgdXJnZW50IGNoYW5nZSBmb3IgdGhlIHByb3RvY29sLiANCg0KLS0gSSBoYXZl
IGEgbWlsZCBjb25jZXJuIHRoYXQgdGhlIHVzZSBvZiBvcmlnaW4gY291bnRyeSBuYW1lcyBmb3Ig
ZWFjaCBpbXBsZW1lbnRhdGlvbiBjb3VsZCBjb25mdXNlIHJlYWRlcnMgaW50byB0aGlua2luZyB0
aGF0IHRoZSBjb3VudHJpZXMgdGhlbXNlbHZlcyBvZmZpY2lhbGx5IHBhcnRpY2lwYXRlZCwgcmF0
aGVyIHRoYW4gb3JnYW5pemF0aW9ucyBmcm9tIGVhY2ggY291bnRyeS4NCg0KDQpbUmUgYnkgRUhd
TWFrZXMgc2Vuc2UuIFdlIHNob3VsZCBwb3NzaWJseSBjaGFuZ2UgdGhpcy4gDQpJbiB0aGUgYmVn
aW5uaW5nIG9mIHNlY3Rpb24gMi4yLjEgd2hlcmUgaXQgc2F5czoNCiJUaGUgVW5pdmVyc2l0eSBv
ZiBQYXRyYXMgaW1wbGVtZW50YXRpb24gam9pbmVkIHJlbW90ZWx5IGZyb20gR3JlZWNlIg0KQ2hh
bmdlIHRvOg0KIlRoZSBVbml2ZXJzaXR5IG9mIFBhdHJhcyAoVW9QKSBpbXBsZW1lbnRhdGlvbiBq
b2luZWQgcmVtb3RlbHkgZnJvbSBHcmVlY2UiDQpBbmQgdGhlbiB1c2UgVW9QIGFmdGVyIHRoYXQg
Zm9yIHVzLg0KDQpbUmUuIGJ5IFdlaW1pbmddIEkgYWdyZWUgd2l0aCBFdmFuZ2Vsb3Mgb24gdGhp
cy4gSWYgcG9zc2libGUgKGtleSBpc3N1ZSBtaWdodCBiZSB0aGUgdGV4dCBzcGFjZSBmb3Igc29t
ZSBmaWd1cmVzKSB3ZSBtYXkgY2hhbmdlIHRoZSBHIHRvIFVvUCwgdGhlIEogdG8gTlRULCB0aGUg
QyB0byBaSlNVID8gDQpPdGhlciBhdXRob3JzLCBwbGVhc2Ugc2hvdyB5b3VyIHZpZXdzLiBUaGFu
a3MuIA0KDQotLSBzZWN0aW9uIDQuNCwgbGFzdCBwYXJhZ3JhcGg6DQoNClRoZSB0ZXh0IHNheXMg
dGhhdCBzaW5jZSB0aGUgbWVudGlvbmVkIGZhaWx1cmVzIHdlcmUgbGlrZWx5IHRoZSByZXN1bHQg
b2YgYnVncywgaXQgZG9lc24ndCBpbmRpY2F0ZSBhbiBpbnRlcm9wZXJhYmlsaXR5IHByb2JsZW0g
aW4gdGhlIHNwZWNzLiBJIGhhdmUgdG8gcG9pbnQgb3V0IHRoYXQsIGl0IGFsc28gZG9lc24ndCBw
cm92ZSBpbnRlcm9wZXJhYmlsaXR5IGluIGJvdGggZGlyZWN0aW9ucyBmb3IgdGhlIHBhcnRpY3Vs
YXIgdGVzdC4gSXQgd291bGQgYWxzbyBiZSB3b3J0aCBjb21tZW50aW5nIG9uIHdoZXRoZXIgdGhl
IHByb2JhYmx5IGJ1Z3Mgd2VyZSBwcm9ncmFtbWluZyBlcnJvcnMgcmF0aGVyIHRoYW4gbWlzdW5k
ZXJzdGFuZGluZ3Mgb2YgdGhlIHNwZWNpZmljYXRpb24uDQpbUmUuIGJ5IFdlaW1pbmddIHRvIGNo
YW5nZSB0aGUgd2hvbGUgcGFyYWdyYXBoIHRvOg0KICA8dD4gVGhlIHR3byB0ZXN0IGl0ZW1zIGZh
aWxlZC4gTm90ZSB0aGF0IFRlc3QgIzcgYW5kICM4IHdlcmUgaWRlbnRpY2FsIHRvIHRoZSB0ZXN0
cywgb25seSB3aXRoIENFIGFuZCBGRSBpbXBsZW1lbnRlcnMgd2VyZSBleGNoYW5nZWQuIE1vcmVv
dmVyLCB0ZXN0ICMxMiBhbmQgIzEzIHNob3dlZCB0aGF0IHRoZSByZWRpcmVjdCBjaGFubmVsIHdv
cmtlZCB3ZWxsLiBUaGVyZWZvcmUsIGl0IGNhbiBiZSByZWFzb25hYmx5IGluZmVycmVkIHRoYXQg
dGhlIHByb2JsZW0gY2F1c2VkIHRoZSBmYWlsdXJlIHdhcyBmcm9tIHRoZSBpbXBsZW1lbnRhdGlv
bnMsIHJhdGhlciB0aGFuIGZyb20gdGhlIEZvckNFUyBwcm90b2NvbCBpdHNlbGYgb3IgZnJvbSBt
aXN1bmRlcnN0YW5kaW5nIG9mIGltcGxlbWVudGF0aW9ucyBvbiB0aGUgcHJvdG9jb2wgc3BlY2lm
aWNhdGlvbi4gQWx0aG91Z2ggdGhlIGZhaWx1cmUgbWFkZSB0aGUgT1NQRiBpbnRlcm9wZXJhYmls
aXR5IHRlc3QgaW5jb21wbGV0ZSwgaXQgZGlkIG5vdCBzaG93IGludGVyb3BlcmFiaWxpdHkgcHJv
YmxlbS4gTW9yZSB0ZXN0IHdvcmsgaXMgbmVlZGVkIHRvIHZlcmlmeSB0aGUgT1NQRiBpbnRlcm9w
ZXJhYmlsaXR5LjwvdD4NCg0KKioqIE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KDQotLSBUaGUg
ZHJhZnQgdXNlcyBpbmNvbnNpc3RlbnQgdmVyYiB0ZW5zZSB0aHJvdWdob3V0LiBJIGZvdW5kIHRo
aXMgYSBiaXQgY29uZnVzaW5nLCBhcyBJIGFzc3VtZSB0aGUgZHJhZnQgdGFsa3MgZW50aXJlbHkg
YWJvdXQgdGVzdHMgdGhhdCBoYXZlIGFscmVhZHkgb2NjdXJyZWQuDQpbUmUuIGJ5IM6VzpddIFdl
IHdpbGwgc3RpY2sgd2l0aCB0aGUgcGFzdCB0ZW5zZS4NCg0KLS0gSUROaXRzIHBvaW50cyBvdXQg
dGhhdCB5b3UgaGF2ZSBzZXZlcmFsIHJlZmVyZW5jZXMgd2l0aG91dCBleHBsaWNpdCBjaXRhdGlv
bnMuIEkgc2VlIHRoYXQgeW91IGNhbGxlZCB0aGUgcmVmZXJlbmNlcyBvdXQgYnkgbmFtZSBpbiB0
aGUgdGV4dCwgYnV0IGl0IHdvdWxkIGJlIGJldHRlciB0byBpbmNsdWRlIHRoZSBjaXRhdGlvbnMu
DQpbUmUuIGJ5IFdlaW1pbmddV2Ugd2lsbCB0cnkgdG8gZml4IHRoaXMgYXMgbXVjaCBhcyBwb3Nz
aWJsZS4NCg0KLS0gU2VjdGlvbiAxLCBwYXJhZ3JhcGggNjoNCg0KUGxlYXNlIGV4cGFuZCBhYmJy
ZXZpYXRpb25zIG9uIGZpcnN0IG1lbnRpb24uDQpbUmUuIGJ5IFdlaW1pbmddIFllcy4NCg0KLS0g
U2VjdGlvbiAxLjE6DQoNClBsZWFzZSBleHBhbmQgRkUgb24gZmlyc3QgbWVudGlvbi4NCltSZS4g
YnkgV2VpbWluZ10gWWVzLg0KDQotLSBzZWN0aW9uIDIuMi4yLCBwYXJhZ3JhcGggMTogIi4uLiBm
cm9tIENoaW5hIGFuZCBKYXBhbiBpbXBsZW1lbnRhdGlvbnMuLi4iDQoNCk1pc3NpbmcgInRoZSIu
DQoNCklzIGl0IHBvc3NpYmxlIHRvIGFkZCBhIHJlZmVyZW5jZSBmb3IgZGV0YWlscyBvbiB0aGUg
U21hcnRiaXRzIHRlc3RpbmcgbWFjaGluZT8NCg0KLS0gRmlndXJlIDI6DQoNCkRvIHlvdSByZWFs
bHkgd2FudCB0byBwdWJsaXNoIHRoZSBJUCBhZGRyZXNzZXMgdXNlZCBpbiBhbiBSRkM/IFJGQ3Mg
bGl2ZSBmb3JldmVyLi4uDQoNCi0tIFNlY3Rpb24gMi4yLjIsIHBhcmFncmFwaCBhZnRlciBmaWd1
cmUgMjogDQoNCkZpcnN0IHNlbnRlbmNlIGRvZXMgbm90IHBhcnNlLg0KDQpbUmUuIGJ5IFdlaW1p
bmddIEluIEZpZ3VyZSAyLCBjaGFuZ2VkIHRoZSAnMTI0LjkwLjE0Ni4yMTggKEFEU0wpJyB0byAn
IChBRFNMKScuICBJbiBGaWd1cmUgMywgY2hhbmdlZCB0aGUgJzE1MC4xNDAuMjU0LjExMChWUE4p
JyB0byAnKFZQTiknIHRvIGF2b2lkIHBlcnNvbmFsIElQIGFkZHJlc3MgaW4gcHVibGljLg0KDQpT
ZWN0aW9uIDIuMi4yLCBwYXJhZ3JhcGggYWZ0ZXIgZmlndXJlIDIsIGZpcnN0IHNlbnRlbmNlIGlz
IGNoYW5nZWQgdG86IA0KPHQ+Q0UgYW5kIEZFIGZyb20gdGhlIEdyZWVjZSBpbXBsZW1lbnRhdGlv
biB3ZXJlIGxvY2F0ZWQgd2l0aGluIHRoZQ0KICAgVW5pdmVyc2l0eSBvZiBQYXRyYXMsIEdyZWVj
ZSwgYW5kIHdlcmUgY29ubmVjdGVkIHRvZ2V0aGVyIHVzaW5nIExBTiBhcyANCiAgIHNob3duIGlu
IDx4cmVmIHRhcmdldD0iRmlndXJlLTMiLz4uIENvbm5ldGlvbiB0byB0aGUgSW50ZXJuZXQgd2Fz
IHZpYSBhIFZQTiBjaGFubmVsLg0KPC90Pg0KWy9SZV0NCg0KLS0gRmlndXJlIDM6DQoNClRoZSBm
aWd1cmUgaGFzIHNvbWUgZm9ybWF0dGluZyBpc3N1ZXMsIGF0IGxlYXN0IGluIHRoZSBQREYgdmVy
c2lvbi4gQWxzbywgaXMgaXQgcG9zc2libGUgdG8gYXZvaWQgc3BsaXR0aW5nIHRoZSBmaWd1cmUg
YWNyb3NzIHRoZSBwYWdlIGJyZWFrPw0KDQpbUmUuIGJ5IFdlaW1pbmddIG9rLCB3ZSdsbCB0cnku
DQpbL1JlXQ0KDQotLSBzZWN0aW9uIDMuMiwgcGFyYWdyYXBoIDM6ICJCZWNhdXNlIG9mIHN5c3Rl
bSBkZWZpY2llbmN5IHRvIGRlcGxveSBJUFNlYyBvdmVyIFRNTCBpbiBHcmVlY2UsLi4uIg0KDQpQ
aHJhc2UgZG9lc24ndCBwYXJzZS4NCg0KLS0gc2VjdGlvbiAzLjIsIHBhcmFncmFwaCA0OiAiLi4u
IG92ZXIgSVBTZWMgY2hhbm5lbC4iDQoNCk1pc3NpbmcgInRoZSIuDQoNCiIuLi50byBoYXZlIGVz
dGFibGlzaGVkLi4uIg0KDQp0byBlc3RhYmxpc2guDQpbUmUuIGJ5IFdlaW1pbmddIFRoZSBzZWN0
aW9uIDMuMiBwYXJhLjMgaGFzIGJlZW4gY2hhbmdlZCB0bzogDQo8dD4uLi4gQmVjYXVzZSB0aGVy
ZSBjYW1lIHVuZm9ydHVuYXRlbHkgYSBwcm9ibGVtIHdpdGggdGhlIHRlc3Qgc3lzdGVtIGluIEdy
ZWVjZSB0byBkZXBsb3kgSVBTZWMgb3ZlciBUTUwgZHVyaW5nIHRoZSB0ZXN0IHByb2Nlc3MsIHRo
aXMgdGVzdCBvbmx5IHRvb2sgcGxhY2UgYmV0d2VlbiB0ZXN0IHN5c3RlbXMgaW4gQ2hpbmEgYW5k
IEphcGFuLjwvdD4NCk90aGVyIG5pdHMgYXJlIGFsc28gY29ycmVjdGVkLg0KdGhhbmtzLg0KWy9S
ZV0NCi0tIHNlY3Rpb24gNCBhbmQgc3Vic2VjdGlvbnM6DQoNCkl0IHNlZW1zIGxpa2Ugc29tZSBv
ZiB0aGUgdGVzdCBkZXNjcmlwdGlvbnMgaW4gNC5YIG1heSBiZSByZWR1bmRhbnQgdG8gdGhlIHBy
ZXZpb3VzIHNjZW5hcmlvIGRlc2NyaXB0aW9ucy4NCg0KW1JlLiBieSBXZWltaW5nXSBwcmV2aW91
cyBzZWN0aW9uIDMueCBpcyB0aGUgc2NlbmFyaW8gZGVzY3JpcHRpb24sIGFuZCB0aGUgNC54IHJl
bGF0ZWQgc2VjdGlvbiBpcyB0aGUgdGVzdCByZXN1bHRzLg0KDQotLSBzZWN0aW9uIDQuMSwgbm90
ZXMgb24gMjggYW5kIDI5Og0KDQpTZW50ZW5jZSBkb2VzIG5vdCBwYXJzZS4NCg0KLi4uIG5vdGVz
IG9uIDMwIGFuZCAzMToNCg0KTWlzc2luZyBhcnRpY2xlcy4NCltSZS4gYnkgV2VpbWluZ11UaGUg
dHdvIG5vdGVzIChOb3RlIG9uIHRlc3QgIzI4IGFuZCAjMjkgYW5kIG5vdGUgb24gdGVzdCAjMzAg
YW5kICMzMSBhcmUgdmFndWFlLiAgQWZ0ZXIgY29uc2lkZXJhdGlvbnMsIHdlIGRlY2lkZSB0byBy
ZW1vdmUgdGhlc3MgdHdvIG5vdGVzLiANClRoYW5rcy4NClsvUmUuXQ0KDQotLSBzZWN0aW9uIDUu
MSwgbGFzdCBwYXJhZ3JhcGggaW4gbGlzdCBpdGVtICIyLiI6ICJUaGUgaW50ZXJvcGVyYWJpbGl0
eSB0ZXN0IHdpdG5lc3NlZCB0aGF0Li4uIg0KDQpUaGUgdGVzdCBfc2hvd2VkXy4uLiAgIFtvciB0
aGUgX3Rlc3RlcnNfIHdpdG5lc3NlZC4uLl0NCg0KW1JlLiBieSBXZWltaW5nXSBtb2RpZmllZCB0
byAnVGhlIGludGVyb3BlcmFiaWxpdHkgdGVzdGVycyB3aXRuZXNzZWQgdGhhdC4uLiIuICBUaGFu
a3MuDQpbL1JlLl0NCg0KLS0gc2VjdGlvbiA5Og0KDQpJdCB3b3VsZCBiZSB3b3J0aCBtZW50aW9u
aW5nIHRoYXQgeW91IGV4cGxpY2l0bHkgdGVzdGVkIGZvciBJUFNlYyBzdXBwb3J0Lg0KDQpbUmUu
IGJ5IFdlaW1pbmddIEFzIGEgcmVzdWx0LCB0aGUgc2VjdGlvbiBoYXMgYmVlbiB1cGRhdGVkIGFz
Og0KDQogOS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zDQoNCiAgIERldmVsb3BlcnMgb2YgRm9y
Q0VTIEZFcyBhbmQgQ0VzIG11c3QgdGFrZSB0aGUgc2VjdXJpdHkNCiAgIGNvbnNpZGVyYXRpb25z
IG9mIHRoZSBGb3JDRVMgRnJhbWV3b3JrIFtSRkMzNzQ2XSAgYW5kIHRoZSBGb3JDRVMNCiAgIFBy
b3RvY29sIFtSRkM1ODEwXSAgaW50byBhY2NvdW50LiAgQWxzbywgYXMgc3BlY2lmaWVkIGluIHRo
ZSBzZWN1cml0eQ0KICAgY29uc2lkZXJhdGlvbnMgc2VjdGlvbiBvZiB0aGUgU0NUUC1CYXNlZCBU
TUwgZm9yIHRoZSBGb3JDRVMgUHJvdG9jb2wNCiAgIFtSRkM1ODExXSwgdGhlIHRyYW5zcG9ydC1s
ZXZlbCBzZWN1cml0eSBoYXMgdG8gYmUgZW5zdXJlZCBieSBJUHNlYy5UZXN0IA0KICAgcmVzdWx0
cyBvZiBUTUwgd2l0aCBJUHNlYyBzdXBwb3J0ZWQgaGF2ZSBiZWVuIHNob3duIGluIFNlY3Rpb24g
NC4yIG9mIHRoZSBkb2N1bWVudC4gDQpbL1JlLl0NCg0KDQoNCg0KDQoNCg0K


From moore@network-heretics.com  Thu May 16 21:11:58 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D66C21F8B2B for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 21:11:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.682
X-Spam-Level: 
X-Spam-Status: No, score=-3.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqrVHoBJ6mFz for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 21:11:53 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 471ED21F8B33 for <ietf@ietf.org>; Thu, 16 May 2013 21:11:52 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9ECDB20CB9; Fri, 17 May 2013 00:11:51 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute6.internal (MEProxy); Fri, 17 May 2013 00:11:51 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=h4ah/fW+bz49e817varVHc zMLWs=; b=lj2SPID7URFNQ4MSEUnGJ9va35JD7GjWiycI70LiNYxATnUdF+USf/ EDSl8I1P/TDGerLA0TdSLdzd5FHBcEU/7/4j5YVzNvBbS6XJJDx9zgU3A0VWyLPo s3EjIYloO+ryDZ8Pal0V87wwK+bG0tXQhIwfETK3btXWgchIX1srM=
X-Sasl-enc: PppAT18DByJw+nxYfMHP3mOW1VvQBL1uFdKy5u7IKIof 1368763911
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AD075200310; Fri, 17 May 2013 00:11:50 -0400 (EDT)
Message-ID: <5195ADFD.1090108@network-heretics.com>
Date: Fri, 17 May 2013 00:11:41 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130329 Thunderbird/17.0.5
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk>	<519507ED.4090805@dcrocker.net>	<CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com>	<F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <5195591C.2070901@bogus.com>
In-Reply-To: <5195591C.2070901@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 04:11:58 -0000

On 05/16/2013 06:09 PM, joel jaeggli wrote:
>
>> Fix that problem, and most of the conflicts between IESG and WGs that 
>> surround DISCUSS votes will go away.
> Maybe but I wouldn't take that as an article of faith. You're going to 
> get pressure for more changes when fresh eyes review something.

Yeah, every new set of eyes that looks at a document is going to have 
some new ideas for what the document should be.   The trick is to get 
those eyes to look at the document earlier in the process, when it's 
easier to fix problems.     Maybe if we did the early review well 
enough, the scope of Last Call comments could be limited in some way.

Keith


From narten@us.ibm.com  Thu May 16 21:53:19 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23AEC21F8F33 for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 21:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WLusAexdZe-c for <ietf@ietfa.amsl.com>; Thu, 16 May 2013 21:53:09 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 6885821F8F2C for <ietf@ietf.org>; Thu, 16 May 2013 21:53:09 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 17 May 2013 00:53:07 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 17 May 2013 00:53:05 -0400
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 595BB38C801A for <ietf@ietf.org>; Fri, 17 May 2013 00:53:04 -0400 (EDT)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4H4r4vr355392 for <ietf@ietf.org>; Fri, 17 May 2013 00:53:04 -0400
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4H4r4nm018963 for <ietf@ietf.org>; Thu, 16 May 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4H4r3ER018953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 May 2013 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r4H4r2s0007311 for <ietf@ietf.org>; Fri, 17 May 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r4H4r2Zs007280 for ietf@ietf.org; Fri, 17 May 2013 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201305170453.r4H4r2Zs007280@rotala.raleigh.ibm.com>
Date: Fri, 17 May 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13051704-7182-0000-0000-000006C20D22
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 04:53:19 -0000

Total of 151 messages in the last 7 days.
 
script run at: Fri May 17 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.27% |   14 |  9.58% |   113593 | moore@network-heretics.com
  9.27% |   14 |  7.82% |    92650 | touch@isi.edu
  7.28% |   11 |  6.76% |    80173 | ted.lemon@nominum.com
  3.97% |    6 |  6.47% |    76736 | dhc@dcrocker.net
  3.31% |    5 |  3.67% |    43481 | sm@resistor.net
  3.31% |    5 |  3.63% |    43035 | narten@us.ibm.com
  3.31% |    5 |  3.34% |    39531 | rdroms.ietf@gmail.com
  3.31% |    5 |  3.00% |    35548 | abdussalambaryun@gmail.com
  3.31% |    5 |  2.98% |    35297 | jmh@joelhalpern.com
  3.31% |    5 |  2.72% |    32293 | jari.arkko@piuha.net
  2.65% |    4 |  3.17% |    37539 | brian.e.carpenter@gmail.com
  2.65% |    4 |  2.09% |    24748 | stephen.farrell@cs.tcd.ie
  2.65% |    4 |  1.96% |    23226 | worley@ariadne.com
  1.99% |    3 |  2.20% |    26128 | john-ietf@jck.com
  1.99% |    3 |  1.73% |    20523 | doug.mtview@gmail.com
  1.32% |    2 |  2.05% |    24243 | wmwang2001@hotmail.com
  1.99% |    3 |  1.36% |    16166 | swmike@swm.pp.se
  1.32% |    2 |  1.92% |    22726 | andy@yumaworks.com
  1.32% |    2 |  1.68% |    19888 | fluffy@cisco.com
  1.32% |    2 |  1.48% |    17563 | farmer@umn.edu
  1.32% |    2 |  1.41% |    16770 | tvest@eyeconomics.com
  1.32% |    2 |  1.41% |    16659 | adrian@olddog.co.uk
  1.32% |    2 |  1.36% |    16115 | ynir@checkpoint.com
  1.32% |    2 |  1.22% |    14478 | scott.brim@gmail.com
  1.32% |    2 |  1.21% |    14343 | joelja@bogus.com
  1.32% |    2 |  1.21% |    14321 | fred@cisco.com
  1.32% |    2 |  1.15% |    13634 | drc@virtualized.org
  1.32% |    2 |  1.10% |    13000 | bclaise@cisco.com
  1.32% |    2 |  1.01% |    11932 | lear@cisco.com
  1.32% |    2 |  0.89% |    10500 | ajs@anvilwalrusden.com
  0.66% |    1 |  1.15% |    13606 | tjc@ecs.soton.ac.uk
  0.66% |    1 |  1.07% |    12720 | leo.liubing@huawei.com
  0.66% |    1 |  1.00% |    11897 | presnick@qti.qualcomm.com
  0.66% |    1 |  0.97% |    11460 | cb.list6@gmail.com
  0.66% |    1 |  0.95% |    11263 | rjsparks@nostrum.com
  0.66% |    1 |  0.95% |    11228 | housley@vigilsec.com
  0.66% |    1 |  0.90% |    10616 | tobias.gondrom@gondrom.org
  0.66% |    1 |  0.86% |    10205 | agmalis@gmail.com
  0.66% |    1 |  0.74% |     8787 | superuser@gmail.com
  0.66% |    1 |  0.74% |     8716 | j.schoenwaelder@jacobs-university.de
  0.66% |    1 |  0.68% |     8105 | ben@nostrum.com
  0.66% |    1 |  0.64% |     7568 | daedulus@btconnect.com
  0.66% |    1 |  0.62% |     7387 | aeopare@gmail.com
  0.66% |    1 |  0.62% |     7308 | carlosm3011@gmail.com
  0.66% |    1 |  0.60% |     7137 | elwynd@dial.pipex.com
  0.66% |    1 |  0.60% |     7108 | l.wood@surrey.ac.uk
  0.66% |    1 |  0.55% |     6518 | barryleiba@computer.org
  0.66% |    1 |  0.52% |     6160 | stig@cisco.com
  0.66% |    1 |  0.52% |     6119 | hartmans-ietf@mit.edu
  0.66% |    1 |  0.51% |     6090 | stpeter@stpeter.im
  0.66% |    1 |  0.51% |     6020 | thierry.moreau@connotech.com
  0.66% |    1 |  0.48% |     5682 | mrex@sap.com
  0.66% |    1 |  0.48% |     5650 | peter@akayla.com
  0.66% |    1 |  0.47% |     5562 | loa@pi.nu
  0.66% |    1 |  0.46% |     5476 | doug@ewellic.org
  0.66% |    1 |  0.43% |     5041 | randy@psg.com
  0.66% |    1 |  0.41% |     4902 | malcolm.betts@zte.com.cn
--------+------+--------+----------+------------------------
100.00% |  151 |100.00% |  1185170 | Total


From ynir@checkpoint.com  Fri May 17 02:19:15 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F5D21F9223 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.363
X-Spam-Level: 
X-Spam-Status: No, score=-10.363 tagged_above=-999 required=5 tests=[AWL=0.236, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRyLSRO7VLun for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:19:09 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 36FCD21F91BF for <ietf@ietf.org>; Fri, 17 May 2013 02:19:07 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4H9Is41011284; Fri, 17 May 2013 12:18:54 +0300
X-CheckPoint: {5195F3F3-10-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 17 May 2013 12:18:54 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUne/wKmUo3LHdUOuQSu+lci7BZkI5+aA
Date: Fri, 17 May 2013 09:18:53 +0000
Message-ID: <097E2B2F-B478-453A-861A-000DB0956D02@checkpoint.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <519547BB.5010305@cs.tcd.ie>
In-Reply-To: <519547BB.5010305@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.103]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11cdfc58fbad23e7dd697eaf1282177874f0f75e22
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E208DA4286CCBD4995D3A18ACB2CBB1E@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 09:19:15 -0000

On May 16, 2013, at 11:55 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> w=
rote:

>=20
> I think Dave's idea is worth looking at, but have one comment:
>=20
> On 05/16/2013 09:46 PM, Yoav Nir wrote:
>> There is a problem, though, that this will increase the load on ADs.
>=20
> There is that. But don't forget that ADs mostly read everything
> in IESG review and often comment. Even leaving aside DISCUSSes,
> if every IETF LC draft got a bunch of AD review comments, then
> the IETF LC would be much busier than now. And its in the nature
> of IETFers to chime in. So this would I suspect increase everyone's
> load, if it works, and not just ADs.

More community participation at IETF last call is a good thing.=20

The problem with AD's time is that they will need to review at IETF last ca=
ll, and then may need to review again after some changes have been made (in=
cluding changes not related to their own issue). That's where the increased=
 AD load comes from.

Yoav


From ynir@checkpoint.com  Fri May 17 02:31:30 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 879FD21F93A5 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.382
X-Spam-Level: 
X-Spam-Status: No, score=-10.382 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uaf5sGJbB4pY for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:31:19 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6EF21F914C for <ietf@ietf.org>; Fri, 17 May 2013 02:31:18 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4H9V952013419; Fri, 17 May 2013 12:31:10 +0300
X-CheckPoint: {5195F6D2-3-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 17 May 2013 12:31:09 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUoCPYrEDZp3mi0aiTEjx394grZkI60AA
Date: Fri, 17 May 2013 09:31:08 +0000
Message-ID: <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com>
In-Reply-To: <51955685.2060009@network-heretics.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.103]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11c21baab256deadab5821eae605b4f669ce3cf508
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <8D5385011510574E947B118FC0B213B8@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 09:31:30 -0000

On May 17, 2013, at 12:58 AM, Keith Moore <moore@network-heretics.com> wrot=
e:

> On 05/16/2013 04:46 PM, Yoav Nir wrote:
>> The time for asking whether the group has considered making this field f=
ixed length instead of variable, or whether RFC 2119 language is used in an=
 appropriate way, or whether the protocol is extensible enough is at IETF l=
ast call.=20
>=20
> Actually the time for asking these questions is long before IETF-wide Las=
t Call.  We need widespread review of proposals for standards-track documen=
ts long before a WG thinks it's finished with those documents.   It's a gap=
ing hole in our process.

Sure. But we have opinionated ADs who read every draft that comes to the IE=
SG. There is no way they have time to participate in all of the working gro=
ups. I, as a participant, can read drafts as they are discussed in working =
groups, because I'm free to ignore all the drafts that are not interesting =
to me. ADs don't have that luxury.

> Fix that problem, and most of the conflicts between IESG and WGs that sur=
round DISCUSS votes will go away.

Good reviewers are a scarce resource, and there are 500(*) working group dr=
afts competing for their attention. That's a hard problem to fix.

Yoav

(*) Went to datatracker, and searched for active drafts that start with  "d=
raft-ietf-". I probably hit some things that have already progressed, but O=
TOH the 500 number is too round, and may be a limitation of datatracker.



From ynir@checkpoint.com  Fri May 17 02:32:37 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1AE21F93B7 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:32:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.399
X-Spam-Level: 
X-Spam-Status: No, score=-10.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTip6bvtGNmp for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:32:31 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 2A41E21F871C for <ietf@ietf.org>; Fri, 17 May 2013 02:32:30 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4H9WAvZ013626; Fri, 17 May 2013 12:32:10 +0300
X-CheckPoint: {5195F70F-4-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 17 May 2013 12:32:10 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUlHUcz+WlRRzt0ejUkQyTd1vw5kH6dWAgAAsDACAAB9lAIAAtp6A
Date: Fri, 17 May 2013 09:32:10 +0000
Message-ID: <70FF494B-B9ED-4562-805F-D9CC8F2AF15F@checkpoint.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <8C48B86A895913448548E6D15DA7553B8EAC53@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8EAC53@xmb-rcd-x09.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.103]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11a93c4fcbff5eb757eb03ea5f0b067502f9e19c57
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F088CDEE3C867C429B1292C558F9045E@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 09:32:37 -0000

On May 17, 2013, at 1:38 AM, Fred Baker (fred) <fred@cisco.com> wrote:

>=20
> On May 16, 2013, at 1:46 PM, Yoav Nir <ynir@checkpoint.com> wrote:
>=20
>> There is a problem, though, that this will increase the load on ADs. Oth=
er concerns raised during IETF LC may lead to revised I-Ds, which the ADs w=
ill need to re-read (or at least look at the diff). I don't know how signif=
icant this extra work would be, but it would come at a time that we're thin=
king of ways to reduce AD workload. It might also require prolonging the LC=
 time, because there would be actual discussion in it.
>=20
> If they raise the issue later in a "discuss", will they not have to do th=
is anyway? How does this relate to the timing of the comment or the vehicle=
 by which it is conveyed?

If you review early, you later might feel like you need to review again, be=
cause the document has changed some. Hence - more work.

Yoav=

From stephen.farrell@cs.tcd.ie  Fri May 17 02:32:57 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10E0421F93DC for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWvjt+0VXOML for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 02:32:53 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1DB21F93EB for <ietf@ietf.org>; Fri, 17 May 2013 02:32:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B7205BEB5; Fri, 17 May 2013 10:32:28 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QvkV5GeucXTs; Fri, 17 May 2013 10:32:28 +0100 (IST)
Received: from [IPv6:2001:770:10:203:bd65:a93e:7637:a936] (unknown [IPv6:2001:770:10:203:bd65:a93e:7637:a936]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8CC2DBEB1; Fri, 17 May 2013 10:32:28 +0100 (IST)
Message-ID: <5195F92C.2040709@cs.tcd.ie>
Date: Fri, 17 May 2013 10:32:28 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <519547BB.5010305@cs.tcd.ie> <097E2B2F-B478-453A-861A-000DB0956D02@checkpoint.com>
In-Reply-To: <097E2B2F-B478-453A-861A-000DB0956D02@checkpoint.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 09:32:57 -0000

On 05/17/2013 10:18 AM, Yoav Nir wrote:
> 
> On May 16, 2013, at 11:55 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
>>
>> I think Dave's idea is worth looking at, but have one comment:
>>
>> On 05/16/2013 09:46 PM, Yoav Nir wrote:
>>> There is a problem, though, that this will increase the load on ADs.
>>
>> There is that. But don't forget that ADs mostly read everything
>> in IESG review and often comment. Even leaving aside DISCUSSes,
>> if every IETF LC draft got a bunch of AD review comments, then
>> the IETF LC would be much busier than now. And its in the nature
>> of IETFers to chime in. So this would I suspect increase everyone's
>> load, if it works, and not just ADs.
> 
> More community participation at IETF last call is a good thing. 
> 
> The problem with AD's time is that they will need to review at IETF last call, and then may need to review again after some changes have been made (including changes not related to their own issue). That's where the increased AD load comes from.

I'm not so sure that's a problem. The additional time I think
(for me) would be in reading the 100's of ietf-discuss mails
that'd get triggered by my or some other AD's comments. Not
all comments would trigger that of course, but if you look at
the minutes for any IESG telechat [1] and imagine that all
those comments had been sent to ietf-discuss during IETF LC
then you might worry about what'd happen on this list.

I'm not against considering this idea at all, but we should
bear in mind that any random thread on this list has a non-zero
probability of turning into major amounts of traffic. Most of
that traffic would doubtless be excellent IETF LC stuff, but
we maybe need to be careful in what we wish for too.

Cheers,
S.

[1] https://www.ietf.org/iesg/minutes/2013/index.html

> Yoav
> 
> 
> 

From jcurran@istaff.org  Fri May 17 05:12:58 2013
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD07221F93DC for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 05:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRtcnG5o22dI for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 05:12:53 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id DEEF821F93BC for <ietf@ietf.org>; Fri, 17 May 2013 05:12:52 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1UdJWm-0006fr-8b; Fri, 17 May 2013 12:12:52 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/IaTPklw5sb3YZkofN/ima
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
From: John Curran <jcurran@istaff.org>
In-Reply-To: <51941F5F.7060201@umn.edu>
Date: Fri, 17 May 2013 08:13:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1503)
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, 17 May 2013 12:12:59 -0000

On May 15, 2013, at 7:50 PM, David Farmer <farmer@umn.edu> wrote:

> So lets play a little hypothetical here;  What if an RIR or ICANN =
through a global policy decided Whois Data no longer should be public =
for overriding privacy reasons.  My read of Section 5, is that would be =
proper path for such a change, and long as the technical guidance of the =
IETF is considered in the process.  But then through RFC 2860 and =
Section 5, if the IETF objected on technical or architectural grounds, =
and formally through the IESG, then the IAB would essentially adjudicate =
the issue.  And ICANN or the RIR are obligated to accept the decision of =
the IAB.  Do I have that right?

To be abundantly clear, you are hypothesizing a difference of opinion =
between the=20
IETF/IESG and the ICANN/RIR communities, wherein the technical guidance =
of the IETF=20
was considered during the ICANN/RIR decision process, but in the end the =
outcome was=20
contrary to IETF expectations.

This would be an unfortunate (but not impossible) situation, as many =
folks in the=20
combined community would likely have been involved during the process =
trying to=20
figure out why there is such a significant difference in views and =
facilitating
sharing of the beliefs and thought processes that underlie the =
situation.  (btw,
these types of efforts happen in more contexts than just the =
hypothetical one you=20
suggest, and are a good reason to ask "Have you hugged your AD =
recently"? ;-)
=20
> To be clear, I'm not advocating Whois should or shouldn't remain =
public, or that anything is wrong with the Section 5.  This just seemed =
like a plausible hypothetical to explore how the puzzle pieces work =
together to make the Internet Numbers Registry System.  Also, I just =
want to fully understand what Section 5 really means.

Ultimately, your hypothetical situation could result in the breakdown of =
the present
relationship between IETF and ICANN/RIR organizations (ref: RFC 2860, =
section 2), with=20
otherwise indeterminate consequences...  i.e. "It would be bad."   When =
the various=20
Internet organizations are aligned in the coordination of Internet =
critical resources=20
(DNS, IP addresses, protocol & parameter #'s), then the result is well =
understood. =20
We lack experience with the alternative, and it is not clear whether =
chair remains=20
upright when missing one or more legs.

FYI,
/John

p.s. Disclaimer:  My views alone.


From jari.arkko@piuha.net  Fri May 17 06:34:44 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1306521F93FC for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 06:34:44 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jOn7TPMo-nso for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 06:34:39 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A5A8821F93EB for <ietf@ietf.org>; Fri, 17 May 2013 06:34:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6212F2CC53; Fri, 17 May 2013 16:34:28 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7oBbLyoayWwv; Fri, 17 May 2013 16:34:27 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 048202CC3C; Fri, 17 May 2013 16:34:26 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <465FC35C-9594-47FC-8CCA-8460943E88D7@gmail.com>
Date: Fri, 17 May 2013 16:34:18 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <077BD704-8609-449E-9367-A7BA1C64A3A3@piuha.net>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <465FC35C-9594-47FC-8CCA-8460943E88D7@gmail.com>
To: dcrocker@bbiw.net, Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 13:34:44 -0000

Dave, Ralph,

>> Jari has expressed the goal of having AD concerns be raised more =
publicly.  Moving AD review and comment to the IETF Last Call venue =
nicely accomplishes this, too.
>=20
> I just posted elsewhere a suggestion to move this review even earlier, =
to WG last call.  Accomplishes most of the same ends, while putting the =
discussion in front of the IETF participants who are, presumably, most =
invested in the resulting document.

We've also said that we'd like to move the directorate reviews earlier, =
to WGLC time. (Subject to us finding a way to do that without increasing =
directorate workload too much.) See the thread "ways forward with the =
tail-heavy aspects of the IETF process".

But overall, we have to be careful that we don't move the same processes =
to a process step that has a different name but in reality will not =
impact how things are done. Part of the idea for moving directorate =
reviews earlier is that more of the responsibility for dealing with =
these could reside with the WGs rather than ADs. And that is a change =
that affects substance and may improve scalability. Similar reasons are =
needed for other changes.

I'm not opposed to moving AD reviews to IETF LC time or even earlier, =
but we'd have to find a way to accommodate both technical comments as =
well as those relating to taking LC feedback into account. ("draft-foo =
LC feedback from Joe was was not appropriately addressed" and similar =
end-of-process checks.)

Jari


From moore@network-heretics.com  Fri May 17 07:02:05 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAF3F21F9375 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 07:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.676
X-Spam-Level: 
X-Spam-Status: No, score=-3.676 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBAOMre1+US3 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 07:02:00 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id AD0E421F9301 for <ietf@ietf.org>; Fri, 17 May 2013 07:02:00 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AF67C20B65 for <ietf@ietf.org>; Fri, 17 May 2013 10:01:59 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 17 May 2013 10:01:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=lml5fDxqVWES5H9DlzdNbY FDxPg=; b=AKvNRddBmtVG8LU0tfELVqhRcfUSx/nV0h8vE00hbzt2Hda6ehqArL f06dsR5YJxyB5S4PB3vX8bVB/Gbf5anlaV5K8F2+n26D86kiqzYBEAXqfQl6MnGF Da4g2XNeyb+AH/gtApXWWLUy6zJGOKoGI36lMQt/kEC3hy0mdZ1dI=
X-Sasl-enc: 40WF5ndn+Z8EXFgDPLhusx60/oZt0wvCpLshm/t9RuQt 1368799319
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E992E2001C7; Fri, 17 May 2013 10:01:58 -0400 (EDT)
Message-ID: <51963854.2050001@network-heretics.com>
Date: Fri, 17 May 2013 10:01:56 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com>
In-Reply-To: <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 14:02:06 -0000

On 05/17/2013 05:31 AM, Yoav Nir wrote:
> On May 17, 2013, at 12:58 AM, Keith Moore <moore@network-heretics.com> wrote:
>
>> On 05/16/2013 04:46 PM, Yoav Nir wrote:
>>> The time for asking whether the group has considered making this field fixed length instead of variable, or whether RFC 2119 language is used in an appropriate way, or whether the protocol is extensible enough is at IETF last call.
>> Actually the time for asking these questions is long before IETF-wide Last Call.  We need widespread review of proposals for standards-track documents long before a WG thinks it's finished with those documents.   It's a gaping hole in our process.
> Sure. But we have opinionated ADs who read every draft that comes to the IESG. There is no way they have time to participate in all of the working groups. I, as a participant, can read drafts as they are discussed in working groups, because I'm free to ignore all the drafts that are not interesting to me. ADs don't have that luxury.

Unless things have changed a great deal since I was on IESG, ADs do have 
the luxury of not reading drafts.   When I was an AD I tried to read 
every draft that was in my area (Applications), and every draft that 
seemed to have the ability to affect applications developers.    The 
lower in the protocol stack, the less likely that I'd feel like I'd have 
anything useful to say about a draft.   Even when I "read" a draft 
outside of my area, in many cases it was just skimming the draft looking 
for red flags.   I developed a pretty good sense of whether a group had 
done due diligence or whether there were serious technical omissions 
that they were trying to ignore.   Only in the latter (rare) cases did I 
feel like such drafts needed more of my attention.

I certainly agree that ADs don't have time to participate in all working 
groups, or even probably 10% of our working groups.   But WGs should be 
able to periodically summarize what they're doing - what problem they're 
trying to solve, what approach they're taking, what technologies they're 
using, what major decisions they've made, what the current sticking 
points seem to be, what problems are as yet unresolved, what potential 
for cross-group and cross-area effects have been identified, and what 
efforts have been made to get the affected parties in the loop.   For 
most groups that summary should be maybe 2-3 pages.   The ADs should be 
able to verify that those summaries are accurate and reasonably 
complete, or appoint a trusted WG observer other than the chair to 
review each summary. ADs and other members of the community should be 
able to view those summaries and comment on their accuracy.   And I 
think it would be reasonable for everyone on IESG to read through those 
summaries once in awhile - at least for groups that seemed likely to 
affect their areas of concern.   I think that such summaries could 
actually lessen IESG's workload.
>> Fix that problem, and most of the conflicts between IESG and WGs that surround DISCUSS votes will go away.
> Good reviewers are a scarce resource, and there are 500(*) working group drafts competing for their attention. That's a hard problem to fix.

That's a related but IMO somewhat different problem.   Working groups 
are producing far too many documents.   That's one reason (far from the 
only one) why WGs shouldn't undertake documents that aren't specifically 
authorized in their charters.

Keith


From moore@network-heretics.com  Fri May 17 07:22:23 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97AB21F925A for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 07:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.67
X-Spam-Level: 
X-Spam-Status: No, score=-3.67 tagged_above=-999 required=5 tests=[AWL=-0.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obBUa+gSBM1p for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 07:22:18 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id ABACA21F92F0 for <ietf@ietf.org>; Fri, 17 May 2013 07:22:17 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0DC63205DF for <ietf@ietf.org>; Fri, 17 May 2013 10:22:17 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Fri, 17 May 2013 10:22:17 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=+PdGore6ERr4WiM2ca8Uvg S//7c=; b=Hote6gI2yZsEJxcci34wqrD1Du5BUqBuGekit+VTWvOT5QiaNADLQi /IE/0nYElBfb4FP+iD70mRcefrxENmmxfGnUKHcgNTnliBIg2EUmvXNXqZmZ6qCF 7tdKROkWJ80t4KpTyld3Oo4Hk3Z5ZRW9rBcjZs5VV48Xqq8C+SzFw=
X-Sasl-enc: KWROuDQigV4cqeBuAS1GxoUe7q1oSk+f7RLanfKIU2TM 1368800536
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 52857C80004; Fri, 17 May 2013 10:22:16 -0400 (EDT)
Message-ID: <51963D16.5050600@network-heretics.com>
Date: Fri, 17 May 2013 10:22:14 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <8C48B86A895913448548E6D15DA7553B8EAC53@xmb-rcd-x09.cisco.com> <70FF494B-B9ED-4562-805F-D9CC8F2AF15F@checkpoint.com>
In-Reply-To: <70FF494B-B9ED-4562-805F-D9CC8F2AF15F@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 14:22:24 -0000

On 05/17/2013 05:32 AM, Yoav Nir wrote:
> On May 17, 2013, at 1:38 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>
>> On May 16, 2013, at 1:46 PM, Yoav Nir <ynir@checkpoint.com> wrote:
>>
>>> There is a problem, though, that this will increase the load on ADs. Other concerns raised during IETF LC may lead to revised I-Ds, which the ADs will need to re-read (or at least look at the diff). I don't know how significant this extra work would be, but it would come at a time that we're thinking of ways to reduce AD workload. It might also require prolonging the LC time, because there would be actual discussion in it.
>> If they raise the issue later in a "discuss", will they not have to do this anyway? How does this relate to the timing of the comment or the vehicle by which it is conveyed?
> If you review early, you later might feel like you need to review again, because the document has changed some. Hence - more work.
Yes, but you only need to review what has changed.     It _can_ be more 
work, particularly for documents that have changed a lot, or if it's 
been too long since the last review.    But I really wouldn't suggest 
that ADs should do several reviews of each document.    I suspect that 
the trick is to review a document at the time the WG thinks that it's 
maybe 70-80% done (which is to say the WG is probably closer to 40-50% 
done), but when some issues still seem unresolved.   That's when the 
ADs' input, and external input in general, can be the most valuable.    
That way, ADs should be able to say "yes, but you're totally ignoring 
this very important issue here, and you really have to deal with it" at 
a time when the WG isn't yet so exhausted or off in the weeds that it 
can't focus on it.   Then the ADs just need to track the changes from 
that point forward, to make sure that the issues identified were dealt 
with satisfactorily.

Of course new issues can still be identified, and WGs can address 
previously identified issues in unsatisfactory ways.   But at some point 
(well prior to WGLC) it might be appropriate to raise the bar for new 
issues.   At some point it should take a serious defect to significantly 
delay publication of a document, and at that point it might make more 
sense to consider other remedies for identified less-serious issues, 
especially if the existing protocol isn't seen to be actually harmful 
and it appears that the protocol can be extended to address the issues 
in a manner that is compatible with existing implementations.   In those 
cases, it might make sense to go ahead and publish, but charter the WG 
to extend the protocol to address those issues.

Keith


From dhc@dcrocker.net  Fri May 17 08:38:10 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A124921F969D for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 08:38:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.513
X-Spam-Level: 
X-Spam-Status: No, score=-6.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xSA4q5gpBzLL for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 08:38:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E69B521F9698 for <ietf@ietf.org>; Fri, 17 May 2013 08:38:00 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4HFbptI032020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 17 May 2013 08:37:54 -0700
Message-ID: <51964EBE.4070709@dcrocker.net>
Date: Fri, 17 May 2013 08:37:34 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com>
In-Reply-To: <51963854.2050001@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.66]); Fri, 17 May 2013 08:37:54 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 15:38:10 -0000

On 5/17/2013 7:01 AM, Keith Moore wrote:
> But WGs should be able to periodically summarize what they're doing -
> what problem they're trying to solve, what approach they're taking, what
> technologies they're using, what major decisions they've made, what the
> current sticking points seem to be, what problems are as yet unresolved,
> what potential for cross-group and cross-area effects have been
> identified, and what efforts have been made to get the affected parties
> in the loop.   For most groups that summary should be maybe 2-3 pages.
> The ADs should be able to verify that those summaries are accurate and
> reasonably complete, or appoint a trusted WG observer other than the
> chair to review each summary. ADs and other members of the community
> should be able to view those summaries and comment on their accuracy.


The idea that working groups should be required to issue periodic 
project progress reports seems strikingly reasonable and useful.

This makes the folks who are the most knowledgeable responsible for 
assessing their work, and should facilitate public review. Recording the 
sequence of reports into the wg datatracker could nicely allow 
evaluating progress over time.

It also, of course, nicely distributes the work.

  d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian@innovationslab.net  Fri May 17 08:44:37 2013
Return-Path: <brian@innovationslab.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE1F021F96C3 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 08:44:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTpGGotikYKu for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 08:44:32 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by ietfa.amsl.com (Postfix) with ESMTP id B5B0921F96CB for <ietf@ietf.org>; Fri, 17 May 2013 08:44:32 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 5574B8817B for <ietf@ietf.org>; Fri, 17 May 2013 08:44:32 -0700 (PDT)
Received: from 102522114.rudm1.ra.johnshopkins.edu (addr16212925014.ippl.jhmi.edu [162.129.250.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 0D3B414000C for <ietf@ietf.org>; Fri, 17 May 2013 08:44:31 -0700 (PDT)
Message-ID: <5196505D.5050009@innovationslab.net>
Date: Fri, 17 May 2013 11:44:29 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net>
In-Reply-To: <51964EBE.4070709@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: Fri, 17 May 2013 15:44:37 -0000

Dave,

On 5/17/13 11:37 AM, Dave Crocker wrote:
> On 5/17/2013 7:01 AM, Keith Moore wrote:
>> But WGs should be able to periodically summarize what they're doing -
>> what problem they're trying to solve, what approach they're taking, what
>> technologies they're using, what major decisions they've made, what the
>> current sticking points seem to be, what problems are as yet unresolved,
>> what potential for cross-group and cross-area effects have been
>> identified, and what efforts have been made to get the affected parties
>> in the loop.   For most groups that summary should be maybe 2-3 pages.
>> The ADs should be able to verify that those summaries are accurate and
>> reasonably complete, or appoint a trusted WG observer other than the
>> chair to review each summary. ADs and other members of the community
>> should be able to view those summaries and comment on their accuracy.
>
>
> The idea that working groups should be required to issue periodic
> project progress reports seems strikingly reasonable and useful.
>
> This makes the folks who are the most knowledgeable responsible for
> assessing their work, and should facilitate public review. Recording the
> sequence of reports into the wg datatracker could nicely allow
> evaluating progress over time.
>
> It also, of course, nicely distributes the work.
>
>   d/
>

We (the INT ADs) have been trying to do that for the past year.  See 
http://trac.tools.ietf.org/area/int/trac/wiki/IETF86 as an example.  The 
goal is to provide a place for INT area WGs to summarize what they have 
been doing so that others within INT can get an idea of what is going 
on.  It is not to the level of a "progress report", but it does provide 
a useful summation (at least based on the feedback that I have received 
to date).

Regards,
Brian


From randy@psg.com  Fri May 17 08:54:39 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E25C621F9500 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 08:54:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tT5+e6NoyPlN for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 08:54:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 60ABD21F8633 for <ietf@ietf.org>; Fri, 17 May 2013 08:54:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UdMzI-000FpZ-SY for ietf@ietf.org; Fri, 17 May 2013 15:54:33 +0000
Date: Fri, 17 May 2013 18:54:31 +0300
Message-ID: <m2mwrtlhzc.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet	Numbers Registry System) to Informational RFC
In-Reply-To: <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 15:54:40 -0000

> To be abundantly clear, you are hypothesizing a difference of opinion
> between the IETF/IESG and the ICANN/RIR communities, wherein the
> technical guidance of the IETF was considered during the ICANN/RIR
> decision process, but in the end the outcome was contrary to IETF
> expectations.

if you s/expectations/preference/ then there is a growing track record.
try the new greed top level domains (gtlds) for starters.

randy

From john-ietf@jck.com  Fri May 17 10:24:22 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8890E21F9732 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 10:24:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5+kzkdVZM-Ql for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 10:24:16 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 89FD921F9774 for <ietf@ietf.org>; Fri, 17 May 2013 10:24:16 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UdOO1-0002Uf-S8; Fri, 17 May 2013 13:24:09 -0400
Date: Fri, 17 May 2013 13:23:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, IETF Disgust <ietf@ietf.org>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC
Message-ID: <D1B3B222A9EFE9597A913F94@JcK-HP8200.jck.com>
In-Reply-To: <m2mwrtlhzc.wl%randy@psg.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <m2mwrtlhzc.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, 17 May 2013 17:24:22 -0000

--On Friday, May 17, 2013 18:54 +0300 Randy Bush <randy@psg.com>
wrote:

>> To be abundantly clear, you are hypothesizing a difference of
>> opinion between the IETF/IESG and the ICANN/RIR communities,
>> wherein the technical guidance of the IETF was considered
>> during the ICANN/RIR decision process, but in the end the
>> outcome was contrary to IETF expectations.
> 
> if you s/expectations/preference/ then there is a growing
> track record. try the new greed top level domains (gtlds) for
> starters.

I've been trying to stay out of this thread, but let me take
that a little further.  I believe that IETF "preferences" are
largely based on the overall welfare of the Internet as a
complete system.  I also believe that the understanding of that
system among IETF participants as a group is generally pretty
good.   Certainly we fail sometimes; IMO, much more often that
I'd like.   But there still seems to be rather general agreement
about success criteria and those criteria, to quote Harald's
comment of some years ago, involve making the Internet work
better.

In addition, actual capture of the IETF consensus process is
really hard.  WGs can sometimes be captured by specific
interests and the IESG decision processes are sometimes not
ideal, but capture is hard.  As several recent threads on the
IETF list illustrate, large portions of the community are
passionate about how decisions are made, express themselves
vigorously, and are usually listened to enough to affect actions
when that is appropriate.

As far as I can tell, large parts of the ICANN community and its
decision processes (I'm not going to comment on the RIRs because
I don't have nearly enough recent exposure) don't subscribe to
those same criteria.  Their most-cited criteria are
competitiveness.   "Security and stability" are chanted as a
mantra, but, empirically, that chant is about the avoidance of
major, scandalous, problems that can be directly attributed to
ICANN decisions rather than about making things better.  And the
price of entry and effective participation has gradually evolved
(or been captured) in a way that biases issue consideration and
decision making toward the wishes of a narrow range of
commercial interests with short-term profitability goals plus a
few symbolic "public" or "civil" "constituencies" whose ability
to be effective is constrained by the desire to continue to
participate and feed at the ICANN trough (the phrase "enjoy fine
lunches and dinners at the expense of others" may be applicable
here).   Those processes seem to be self-reinforcing and
self-reproducing enough, and driven in practice by a narrow
enough range of interests, to meet almost any criterion for a
"captured" label.

The level of harmony and conformance between ICANN's stated
principles and core values (as reflected in its bylaws,
reference [ICANNBL] in the draft) and ICANN's actual influences
and operational and decision-making practices would seem to lie
far outside the scope of this document.   I think the document
reflects a certain naivety about the range of differences
between theory and practice, but I'd not convinced that is
harmful beyond some risks of making the authors look silly in
some conceivable future scenarios.

If the "technical guidance of the IETF" were really based on the
best interests of a better Internet and then used as input to a
process that doesn't consider that a particularly useful
criterion, then an outcome that is contrary to that advice is
nearly inevitable unless the advice coincidentally matches the
criteria that are actually being used.  What should be done
about that is a different and, sadly complex matter  (especially
given the risks of significant collateral damage that could harm
the Internet).  

But it doesn't seem to me that is the present issue.  For the
present document, if it accurately describes the current
situation and how things have evolved since 2050, then it is
worth publishing.  If we don't like how things work, it seems to
me that changing that is part of a different effort and that a
good current description is a necessary starting point.

I, however, do have one significant objection to the current
draft of the document and do not believe it should be published
(at least as an RFC in the IETF Stream) until the problem is
remedied.  The Introduction (Section 1) contains the sentence
"Since the publication of RFC 2050, the Internet Numbers
Registry System has changed significantly."    That sentence is
expanded upon in Section 6, which bears the interesting title of
"Summary of Changes Since RFC 2050".  But Section 6 contains no
such summary, merely a statement that things have changed and
that some material -- unidentified except by the broadest of
categories -- has been omitted.   

I do not believe this document is complete enough to publish as
an RFC in the IETF Stream without a real summary of the changes
since 2050, preferably with either explanations of each
significant change or references to the documents or discussions
that instituted or explained those changes.

   best,
   john



From daedulus@btconnect.com  Fri May 17 10:34:00 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E3821F9623 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 10:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0WFS1ObXnkK for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 10:33:54 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id 7AADF21F966F for <ietf@ietf.org>; Fri, 17 May 2013 10:33:54 -0700 (PDT)
Received: from mail61-va3-R.bigfish.com (10.7.14.232) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 17 May 2013 17:33:53 +0000
Received: from mail61-va3 (localhost [127.0.0.1])	by mail61-va3-R.bigfish.com (Postfix) with ESMTP id 0E14E360336; Fri, 17 May 2013 17:33:53 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL8275dh8275chz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail61-va3 (localhost.localdomain [127.0.0.1]) by mail61-va3 (MessageSwitch) id 1368812031364280_4309; Fri, 17 May 2013 17:33:51 +0000 (UTC)
Received: from VA3EHSMHS036.bigfish.com (unknown [10.7.14.252])	by mail61-va3.bigfish.com (Postfix) with ESMTP id 4A9AF1600C2; Fri, 17 May 2013 17:33:51 +0000 (UTC)
Received: from DB3PRD0710HT003.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS036.bigfish.com (10.7.99.46) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 17 May 2013 17:33:51 +0000
Received: from DB3PRD0511HT001.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.255.75.38) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 17 May 2013 17:33:49 +0000
Message-ID: <007f01ce5323$eff08080$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <dcrocker@bbiw.net>, <ietf@ietf.org>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk><519507ED.4090805@dcrocker.net><CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com><F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com><51955685.2060009@network-heretics.com><4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com><51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETFprocess]
Date: Fri, 17 May 2013 18:28:16 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.213]
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, 17 May 2013 17:34:00 -0000

----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: <ietf@ietf.org>
Sent: Friday, May 17, 2013 4:37 PM
> On 5/17/2013 7:01 AM, Keith Moore wrote:
> > But WGs should be able to periodically summarize what they're
doing -
> > what problem they're trying to solve, what approach they're taking,
what
> > technologies they're using, what major decisions they've made, what
the
> > current sticking points seem to be, what problems are as yet
unresolved,
> > what potential for cross-group and cross-area effects have been
> > identified, and what efforts have been made to get the affected
parties
> > in the loop.   For most groups that summary should be maybe 2-3
pages.
> > The ADs should be able to verify that those summaries are accurate
and
> > reasonably complete, or appoint a trusted WG observer other than the
> > chair to review each summary. ADs and other members of the community
> > should be able to view those summaries and comment on their
accuracy.
>
>
> The idea that working groups should be required to issue periodic
> project progress reports seems strikingly reasonable and useful.

Some WG Chairs already do this and I find it most helpful.  Even at the
most basic level, of what documents have changed status in the past
month and what have not, this provides a valuable measure of progress,
or lack thereof.

And what is management but finding out what is going on and intervening
when intervention is needed?  And how can you know if you do not get
progress reports?  And, who knows, at a basic level, this could be
automated from the I-D Tracker, no extra work for AD or WG Chair (except
for intervening when intervention is needed).

Tom Petch

> This makes the folks who are the most knowledgeable responsible for
> assessing their work, and should facilitate public review. Recording
the
> sequence of reports into the wg datatracker could nicely allow
> evaluating progress over time.
>
> It also, of course, nicely distributes the work.
>
>   d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>



From dhc@dcrocker.net  Fri May 17 11:12:34 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CFB121F96EB for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 11:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bBN8y5ctGtNq for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 11:12:29 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6071121F96ED for <ietf@ietf.org>; Fri, 17 May 2013 11:12:29 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4HICMFC002614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 17 May 2013 11:12:27 -0700
Message-ID: <519672F4.9020208@dcrocker.net>
Date: Fri, 17 May 2013 11:12:04 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETFprocess]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk><519507ED.4090805@dcrocker.net><CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com><F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com><51955685.2060009@network-heretics.com><4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com><51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net> <007f01ce5323$eff08080$4001a8c0@gateway.2wire.net>
In-Reply-To: <007f01ce5323$eff08080$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 17 May 2013 11:12:27 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 18:12:34 -0000

On 5/17/2013 10:28 AM, t.p. wrote:
>> The idea that working groups should be required to issue periodic
>> project progress reports seems strikingly reasonable and useful.
>
> Some WG Chairs already do this and I find it most helpful.  Even at the
> most basic level, of what documents have changed status in the past
> month and what have not, this provides a valuable measure of progress,
> or lack thereof.


That's good, but it highlights a point I also noticed in the examples we 
were given for INT:  There's a basic difference between activity and 
progress.

Except for in-depth, detailed tracking situations, I think that 
reporting 'activity' is actually noise.

Progress is about decisions and output, not about movement and input.

Since the goal of the kind of reporting being discussed here is to 
inform the 'community' it needs to be very concise and semantic:  It 
needs to talk about the accomplishments that have /completed/ things.  A 
decision finishes a question.  Agreement on the text of a section 
finishes that part of a document.

Iterating on a document and holding meetings are activity that might or 
might not contain the kernel of progress.

For the current discussion, we need to hear about that kernel, IMO.  Not 
the rest.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian.e.carpenter@gmail.com  Fri May 17 13:14:45 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98A2621F94A6 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 13:14:45 -0700 (PDT)
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.239, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GlcpUQi5qSo4 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 13:14:39 -0700 (PDT)
Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) by ietfa.amsl.com (Postfix) with ESMTP id AD05E21F907E for <ietf@ietf.org>; Fri, 17 May 2013 13:14:39 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id rl6so3935582pac.28 for <ietf@ietf.org>; Fri, 17 May 2013 13:14:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Z32L8ke9LsReDZkEEP8XgRzGEjm3Kof+V3R+Ki1cKmE=; b=CNujIcyD8P2/EREvRRGwhstNPTsd8LTOsdT1m2XyEvWQJT/J2TUXUQeGacMleAv0WC yWiZQnWrCQERShPyhdz3Mh0vjdfK/VtshsODpyK++OsKqAQmA9X3CJ0ndMhvqfqR5ts1 6Hoc7wY4uCHt+NwouM6JXC19vRA1xUcdSt23K9N83nOauHTQIvgoTR9LLJzXeONgkxO7 XKekS6w25IzBqgdJ68z05shSkrgQc3nFTDjWCejkK+pHqRIx2p9R7MbGS0rvGz+pYWa7 /uqIFHwe77Lw/a9qEvDsc+2q5pu6StAg7U/qxIGsu+ajA/CpT6URDDZk3Pu/l3709Rah xQ7g==
X-Received: by 10.68.180.132 with SMTP id do4mr50128425pbc.96.1368821671127; Fri, 17 May 2013 13:14:31 -0700 (PDT)
Received: from [192.168.1.4] (29.131.252.27.dyn.cust.vf.net.nz. [27.252.131.29]) by mx.google.com with ESMTPSA id fn2sm12451293pbc.15.2013.05.17.13.14.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 17 May 2013 13:14:29 -0700 (PDT)
Message-ID: <51968FAE.1020509@gmail.com>
Date: Sat, 18 May 2013 08:14:38 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The	Internet Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20130510103049.0ca25050@resistor.net>	<D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org>	<6.2.5.6.2.20130510231552.0df99d90@resistor.net>	<51927C4B.6090400@umn.edu>	<5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org>	<51941F5F.7060201@umn.edu>	<805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org>	<m2mwrtlhzc.wl%randy@psg.com> <D1B3B222A9EFE9597A913F94@JcK-HP8200.jck.com>
In-Reply-To: <D1B3B222A9EFE9597A913F94@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 20:14:46 -0000

John,

On 18/05/2013 05:23, John C Klensin wrote:

...
> I, however, do have one significant objection to the current
> draft of the document and do not believe it should be published
> (at least as an RFC in the IETF Stream) until the problem is
> remedied.  The Introduction (Section 1) contains the sentence
> "Since the publication of RFC 2050, the Internet Numbers
> Registry System has changed significantly."   

If we want to avoid ratholes built into the document, it might be
prudent to rephrase that sentence as
"Since the publication of RFC 2050, the environment of the
Internet Numbers Registry System has changed."

> That sentence is
> expanded upon in Section 6, which bears the interesting title of
> "Summary of Changes Since RFC 2050".  But Section 6 contains no
> such summary, merely a statement that things have changed and
> that some material -- unidentified except by the broadest of
> categories -- has been omitted.

I took that section title to refer to changes *in the text* of
2050, not changes in the system. Maybe the authors could clarify
their intent, and if it is limited to text changes, clarify
the wording accordingly.

     Brian

From ynir@checkpoint.com  Fri May 17 13:36:14 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B0D621F9670 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 13:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.413
X-Spam-Level: 
X-Spam-Status: No, score=-10.413 tagged_above=-999 required=5 tests=[AWL=0.186, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sj-HGZFqpB4h for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 13:36:08 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id D49F821F966F for <ietf@ietf.org>; Fri, 17 May 2013 13:36:07 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4HKa3rr008162 for <ietf@ietf.org>; Fri, 17 May 2013 23:36:03 +0300
X-CheckPoint: {519692A2-18-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 17 May 2013 23:36:03 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: ietf Discussion <ietf@ietf.org>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: AQHOUwcn4MSMHuAbGEaRbqCaqz+mWJkJUI0AgABTZAA=
Date: Fri, 17 May 2013 20:36:01 +0000
Message-ID: <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net>
In-Reply-To: <51964EBE.4070709@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.230]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11d3d7daacc27a6338e7bce25e04f2454a56180cad
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F215426875BDCD4082887839FD0208A6@ad.checkpoint.com>
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: Fri, 17 May 2013 20:36:14 -0000

On May 17, 2013, at 6:37 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 5/17/2013 7:01 AM, Keith Moore wrote:
>> But WGs should be able to periodically summarize what they're doing -
>> what problem they're trying to solve, what approach they're taking, what
>> technologies they're using, what major decisions they've made, what the
>> current sticking points seem to be, what problems are as yet unresolved,
>> what potential for cross-group and cross-area effects have been
>> identified, and what efforts have been made to get the affected parties
>> in the loop.   For most groups that summary should be maybe 2-3 pages.
>> The ADs should be able to verify that those summaries are accurate and
>> reasonably complete, or appoint a trusted WG observer other than the
>> chair to review each summary. ADs and other members of the community
>> should be able to view those summaries and comment on their accuracy.
>=20
>=20
> The idea that working groups should be required to issue periodic project=
 progress reports seems strikingly reasonable and useful.
>=20
> This makes the folks who are the most knowledgeable responsible for asses=
sing their work, and should facilitate public review. Recording the sequenc=
e of reports into the wg datatracker could nicely allow evaluating progress=
 over time.
>=20
> It also, of course, nicely distributes the work.
>=20
> d/

"
From: WG Chair
To: ietf@ietf.org
Sunbject: Progress Report - Foo WG

There has been zero activity on the FOO list in the last three months (exce=
pt for that "Fake Conference" message everybody got last month). I've tried=
 emailing the WG document authors twice, but they're not answering my email=
s.

So, the WG has 2 documents: draft-ietf-foo-use-cases-03, and draft-ietf-foo=
-proto-01.

The use case document is just about done, but we haven't really started dis=
cussing the proto document. We haven't met in Orlando, and are unlikely to =
meet in Berlin

That's it for this report.

Cheers

WGC

"



From kotecha_kamal@yahoo.com  Fri May 17 14:31:18 2013
Return-Path: <kotecha_kamal@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 038CC21F96E5 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 14:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.461
X-Spam-Level: 
X-Spam-Status: No, score=0.461 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, J_CHICKENPOX_32=0.6, J_CHICKENPOX_63=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LStBukV1VmYO for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 14:31:11 -0700 (PDT)
Received: from nm5-vm4.bullet.mail.ne1.yahoo.com (nm5-vm4.bullet.mail.ne1.yahoo.com [98.138.91.165]) by ietfa.amsl.com (Postfix) with ESMTP id 68F8421F9682 for <ietf@ietf.org>; Fri, 17 May 2013 14:31:11 -0700 (PDT)
Received: from [98.138.90.48] by nm5.bullet.mail.ne1.yahoo.com with NNFMP; 17 May 2013 21:31:10 -0000
Received: from [98.138.226.163] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 17 May 2013 21:31:10 -0000
Received: from [127.0.0.1] by omp1064.mail.ne1.yahoo.com with NNFMP; 17 May 2013 21:31:10 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 814804.97861.bm@omp1064.mail.ne1.yahoo.com
Received: (qmail 5970 invoked by uid 60001); 17 May 2013 21:31:10 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1368826270; bh=LYsbWRPcqdDK2yahgldDxURMwlp69qNjhCBJyvQ17Lg=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=opXHdwbROn2uHhOgHGGebQ9C2eOtI4Fet79febb8STbpg8WEaV+vZ5WVEP17Z6IPluXIYSNcC1Zp2QpDQ7SDML731pIYP6y036POx4fIl4bWQ9HlVhgVC3GoBwTNJZy+kAZd+2AR2v2wjbB0WpNho5ECt6gn3sItduql96NaO5k=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=Og+06dW3luPeol/KLhT/8Hxj0uS8gHziQDRF7pZ9OAykjRarjQhFFxT19tYXWbWRP5hjqwsOYPdhRtNgsSqK8z65G9JnWPBSm7upjRB+g/zV0UPCO+pZaX764DSk/Wj22MwozUZoUEdjSt1W9mzWSEdbMFDKM2LGP8JzWyj3938=;
X-YMail-OSG: SxO_IXQVM1k0wiEcwDvgc0IbeJduvKKC6lwhgRgrJ6KgsMZ PdAzFvpUbZcAJFssPA5uNgmDeCdWc2.z2YKgvZT8s0gPlxkGEz0FL.1HiVHb 1MVnaQ5vi0r1yZuusSSRGr3q9g6uxHQM65M4ThKkeZ9pxLEhjn2wFMMQOaab 8NbEu7Y7l2tjuTuuf7EgQ9e6BMj1X4lvFahlmV5UvAdF3AsWHZKKUt2eKo6_ .Voee4oZRQscjYHtgSwvwF0QQEVFR4yCs8nFQ9J9J_WSmG9xPtUNM0oRWwxB nnMcm1OTsIoxQWB1k_yhE99FOFcNFTPk.El4WOAEKVaXrDeLSqP_1N565K17 oo8DIM4T2kkDORw86E3fWuQ5usYD8W_LCLugIG6_DYp4Ek7nRHUq_S7OPRT1 UoXZAnEyJmfqfh9trmIjw1oeOJXjK4yqDxaHeGN5EDuZpfYrrTaRPFMFErnY A.EWNaei8ERd.0xEUlskWDCYVan7UCiKHOmh1C.niVb_bwAmc1wXVkjhRuGn 0eSaayAKZLgpzjSVc.g--
Received: from [115.240.61.99] by web120104.mail.ne1.yahoo.com via HTTP; Fri, 17 May 2013 14:31:10 PDT
X-Rocket-MIMEInfo: 002.001, wqAKSGkgRm9sa3MsCsKgCldlIGFyZSBmYWNpbmcgYSBwcm9ibGVtIHdpdGggRGlhbWV0ZXIgQ3JlZGl0IENvbnRyb2wgQXBwbGljYXRpb246CsKgClByb2JsZW0gZGlzY3JpcHRpb246CsKgCkRpYW1ldGVyIGNsaWVudCBzZW5kcyBhIENDUi11cGRhdGUgbWVzc2FnZSB0byBzZXJ2ZXIsYnV0IHNlcnZlciBkb2VzIG5vdCByZXNwb25kIHRvIHRoZSByZXF1ZXN0LgrCoApOb3csYXMgY2xpZW50IGlzIGNvbmZpZ3VyZWQgd2l0aCBzZXNzaW9uIGZhaWxvdmVyLCBpdCB3aWxsIHNlbmQgQ0NSLXVwZGF0ZSB0byBiYWMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.142.542
Message-ID: <1368826270.98786.YahooMailNeo@web120104.mail.ne1.yahoo.com>
Date: Fri, 17 May 2013 14:31:10 -0700 (PDT)
From: Kamal Kotecha <kotecha_kamal@yahoo.com>
Subject: Diameter Credit Control Application--Issue during CCR-Update
To: "Ietf@ietf.org" <Ietf@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-1312421089-811922431-1368826270=:98786"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Kamal Kotecha <kotecha_kamal@yahoo.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 21:31:18 -0000

---1312421089-811922431-1368826270=:98786
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

=A0=0AHi Folks,=0A=A0=0AWe are facing a problem with Diameter Credit Contro=
l Application:=0A=A0=0AProblem discription:=0A=A0=0ADiameter client sends a=
 CCR-update message to server,but server does not respond to the request.=
=0A=A0=0ANow,as client is configured with session failover, it will send CC=
R-update to backup server.=0A=A0=0AIn this update message,=A0Destination Ho=
st AVP is not being included.=A0 (???)=0A=A0=0AHence, in same destination r=
ealm, this request is forwarded to random peer.=0A=A0=0AThis=A0 random peer=
 is responding with failure message as "Diamater Unable to Comply".=0A=0AWh=
ats wrong here..?? =0A=0A=0A(in rfc 4006, I'm not able to track this kind o=
f scenario!)=0A=0ARegards,=0AKamal Kotecha=0A
---1312421089-811922431-1368826270=:98786
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ve=
rdana, helvetica, sans-serif;font-size:10pt"><div><span></span>&nbsp;</div>=
<div><span>Hi Folks,</span></div><div><span></span>&nbsp;</div><div><span>W=
e are facing a problem with Diameter Credit Control Application:</span></di=
v><div><span></span>&nbsp;</div><div><span>Problem discription:</span></div=
><div><span></span>&nbsp;</div><div><span>Diameter client sends a CCR-updat=
e message to server,but server does not respond to the request.</span></div=
><div><span></span>&nbsp;</div><div><span>Now,as client is configured with =
session failover, it will send CCR-update to backup server.</span></div><di=
v><span></span>&nbsp;</div><div><span>In this update message,&nbsp;Destinat=
ion Host AVP is not being included.&nbsp; (???)</span></div><div><span></sp=
an>&nbsp;</div><div><span>Hence, in same destination realm, this request is=
 forwarded to random
 peer.</span></div><div><span></span>&nbsp;</div><div><span>This&nbsp; rand=
om peer is responding with failure message as "Diamater Unable to Comply".<=
/span></div><div>&nbsp;</div><div>Whats wrong here..?? </div><div>&nbsp;</d=
iv><div>&nbsp;</div><div>(in rfc 4006, I'm not able to track this kind of s=
cenario!)</div><div>&nbsp;</div><div>Regards,</div><div>Kamal Kotecha<br></=
div></div></body></html>
---1312421089-811922431-1368826270=:98786--

From john-ietf@jck.com  Fri May 17 16:59:41 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BD7621F95F6 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 16:59:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dmMFAI20rWcD for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 16:59:35 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8D521F9672 for <ietf@ietf.org>; Fri, 17 May 2013 16:59:35 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UdUYg-0002vg-UO; Fri, 17 May 2013 19:59:34 -0400
Date: Fri, 17 May 2013 19:59:16 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The	Internet Numbers Registry System) to Informational RFC
Message-ID: <818465C4E514C0957E0B6B89@JcK-HP8200.jck.com>
In-Reply-To: <51968FAE.1020509@gmail.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <m2mwrtlhzc.wl%randy@psg.com> <D1B3B222A9EFE9597A913F94@JcK-HP8200.jck.com> <51968FAE.1020509@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 May 2013 23:59:41 -0000

--On Saturday, May 18, 2013 08:14 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> John,
> 
> On 18/05/2013 05:23, John C Klensin wrote:
> 
> ...
>> I, however, do have one significant objection to the current
>> draft of the document and do not believe it should be
>> published (at least as an RFC in the IETF Stream) until the
>> problem is remedied.  The Introduction (Section 1) contains
>> the sentence "Since the publication of RFC 2050, the Internet
>> Numbers Registry System has changed significantly."   
> 
> If we want to avoid ratholes built into the document, it might
> be prudent to rephrase that sentence as
> "Since the publication of RFC 2050, the environment of the
> Internet Numbers Registry System has changed."

Both statements are true-- the environment has changed and the
system has changed.  At least in principle, the environment has
changed less with three three really notable events being the
advent of ICANN, the end-game of the IPv4 address space, and the
growing importance of the IPv6 one.  I think that can be said
and the other changes summarized.  From my point of view, if we
have to avoid describing the changes to avoid ratholes, it would
be legitimate for someone to ask what we are hiding.  

>> That sentence is
>> expanded upon in Section 6, which bears the interesting title
>> of "Summary of Changes Since RFC 2050".  But Section 6
>> contains no such summary, merely a statement that things have
>> changed and that some material -- unidentified except by the
>> broadest of categories -- has been omitted.
 
> I took that section title to refer to changes *in the text* of
> 2050, not changes in the system. Maybe the authors could
> clarify their intent, and if it is limited to text changes,
> clarify the wording accordingly.

I just checked your hypothesis by looking at a diff between 2050
and the present draft.  As far as I can tell from a quick
review, there is not a single unchanged paragraph.  So, if the
issue is text changes, this is not an update but an almost
complete replacement.

    john




From brian.e.carpenter@gmail.com  Fri May 17 18:08:27 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82E9F21F8517 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 18:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.856
X-Spam-Level: 
X-Spam-Status: No, score=-102.856 tagged_above=-999 required=5 tests=[AWL=-0.257, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VodtNTDU-nXa for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 18:08:27 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id EDC2C21F84E7 for <ietf@ietf.org>; Fri, 17 May 2013 18:08:26 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so3790180pbb.20 for <ietf@ietf.org>; Fri, 17 May 2013 18:08:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+li71udkqTyepbzTBX0osoObOnuej2Bnrf4mlCj2kHw=; b=EOiJFrt8PtIlUlpOeEAGBJyWqCq1tgWBGRNjqPbWhmm6VvMPXMqEgZUMWWaX77c0iM eN8FDHfjqXo5svu2bGpKxQEQb4VFWtsgf5m1eWeSNzbIkjxLnrebd7JooizcaHI5VMFk THOsO3zy4kkgixd7weZEC9KDz/maCLet7ssypCpbSLSl0O1Wk4xQoolA2Hn/AHtaVkCs o3UhlDHImB/ZMFClXzgR/DPUhKhjVVz7OHRJ77MjW7J9sQYBoRKZDW7IY/szZTSD0Bzi CXhFyQf4j/RnntY8Sf0ZHQSlyxLJ/itCHZ5Tyu9SS/QDlq8o9n0o/vpbd7340WCbxu4Y ElDQ==
X-Received: by 10.66.248.68 with SMTP id yk4mr52075335pac.137.1368839306729; Fri, 17 May 2013 18:08:26 -0700 (PDT)
Received: from [192.168.1.4] (103.201.252.27.dyn.cust.vf.net.nz. [27.252.201.103]) by mx.google.com with ESMTPSA id 10sm13283920pbm.0.2013.05.17.18.08.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 17 May 2013 18:08:25 -0700 (PDT)
Message-ID: <5196D493.6010407@gmail.com>
Date: Sat, 18 May 2013 13:08:35 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The	Internet Numbers Registry System) to Informational RFC
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <m2mwrtlhzc.wl%randy@psg.com> <D1B3B222A9EFE9597A913F94@JcK-HP8200.jck.com> <51968FAE.1020509@gmail.com> <818465C4E514C0957E0B6B89@JcK-HP8200.jck.com>
In-Reply-To: <818465C4E514C0957E0B6B89@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 May 2013 01:08:27 -0000

On 18/05/2013 11:59, John C Klensin wrote:
> 
> --On Saturday, May 18, 2013 08:14 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> John,
>>
>> On 18/05/2013 05:23, John C Klensin wrote:
>>
>> ...
>>> I, however, do have one significant objection to the current
>>> draft of the document and do not believe it should be
>>> published (at least as an RFC in the IETF Stream) until the
>>> problem is remedied.  The Introduction (Section 1) contains
>>> the sentence "Since the publication of RFC 2050, the Internet
>>> Numbers Registry System has changed significantly."   
>> If we want to avoid ratholes built into the document, it might
>> be prudent to rephrase that sentence as
>> "Since the publication of RFC 2050, the environment of the
>> Internet Numbers Registry System has changed."
> 
> Both statements are true-- the environment has changed and the
> system has changed.  At least in principle, the environment has
> changed less with three three really notable events being the
> advent of ICANN, the end-game of the IPv4 address space, and the
> growing importance of the IPv6 one.  I think that can be said
> and the other changes summarized.  From my point of view, if we
> have to avoid describing the changes to avoid ratholes, it would
> be legitimate for someone to ask what we are hiding.  
> 
>>> That sentence is
>>> expanded upon in Section 6, which bears the interesting title
>>> of "Summary of Changes Since RFC 2050".  But Section 6
>>> contains no such summary, merely a statement that things have
>>> changed and that some material -- unidentified except by the
>>> broadest of categories -- has been omitted.
>  
>> I took that section title to refer to changes *in the text* of
>> 2050, not changes in the system. Maybe the authors could
>> clarify their intent, and if it is limited to text changes,
>> clarify the wording accordingly.
> 
> I just checked your hypothesis by looking at a diff between 2050
> and the present draft.  As far as I can tell from a quick
> review, there is not a single unchanged paragraph.  So, if the
> issue is text changes, this is not an update but an almost
> complete replacement.

Yes, because apart from anything else, the draft leaves out
a number of topics that are explicitly out of IETF scope since
RFC 2860. I don't really see what we are hiding in this:

   This document
   describes the Internet Numbers Registry System as it presently exists
   and omits policy and operational procedures that have been superseded
   by ICANN and RIR policy since RFC 2050 publication.

(given that there is a reference to RFC 2860 a few lines earlier).

If I had the edit pen I would probably want to rephrase that
paragraph a bit, but it does say what has been deleted and why.

     Brian

From moore@network-heretics.com  Fri May 17 18:30:14 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 460FE21F961C for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 18:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.666
X-Spam-Level: 
X-Spam-Status: No, score=-3.666 tagged_above=-999 required=5 tests=[AWL=-0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ro1zGvWi4TZB for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 18:30:09 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id EFC6721F9616 for <ietf@ietf.org>; Fri, 17 May 2013 18:30:05 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id F073420935; Fri, 17 May 2013 21:30:03 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 17 May 2013 21:30:03 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=Bud3NalPmiPD4P3WvmfqB1 IvrIM=; b=J3xZB5zzZxuWAJFzHPpmiO6rk0+W146oFGxws+7imkF7rw4rdN7362 EueaWkOLyHtd5YdNXlMBRylL3IrNd4ONrrIa+vM3DTWw4YH2D42FtPEKs40chxMq zgZMOXPgm/EHA8VBdU2ce1jYamye7iDZFtellZae5SOcYCucK6+Vc=
X-Sasl-enc: EzPvlxDV83SBi/V5hryE2t4fSV8FLvohTwOZxjrROPrZ 1368840603
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 1B263C80007; Fri, 17 May 2013 21:30:03 -0400 (EDT)
Message-ID: <5196D997.7030909@network-heretics.com>
Date: Fri, 17 May 2013 21:29:59 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net> <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.com>
In-Reply-To: <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.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: Sat, 18 May 2013 01:30:14 -0000

On 05/17/2013 04:36 PM, Yoav Nir wrote:
> On May 17, 2013, at 6:37 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>
>> On 5/17/2013 7:01 AM, Keith Moore wrote:
>>> But WGs should be able to periodically summarize what they're doing -
>>> what problem they're trying to solve, what approach they're taking, what
>>> technologies they're using, what major decisions they've made, what the
>>> current sticking points seem to be, what problems are as yet unresolved,
>>> what potential for cross-group and cross-area effects have been
>>> identified, and what efforts have been made to get the affected parties
>>> in the loop.   For most groups that summary should be maybe 2-3 pages.
>>> The ADs should be able to verify that those summaries are accurate and
>>> reasonably complete, or appoint a trusted WG observer other than the
>>> chair to review each summary. ADs and other members of the community
>>> should be able to view those summaries and comment on their accuracy.
>>
>> The idea that working groups should be required to issue periodic project progress reports seems strikingly reasonable and useful.
>>
>> This makes the folks who are the most knowledgeable responsible for assessing their work, and should facilitate public review. Recording the sequence of reports into the wg datatracker could nicely allow evaluating progress over time.
>>
>> It also, of course, nicely distributes the work.
>>
>> d/
> "
> From: WG Chair
> To: ietf@ietf.org
> Sunbject: Progress Report - Foo WG
>
> There has been zero activity on the FOO list in the last three months (except for that "Fake Conference" message everybody got last month). I've tried emailing the WG document authors twice, but they're not answering my emails.
>
> So, the WG has 2 documents: draft-ietf-foo-use-cases-03, and draft-ietf-foo-proto-01.
>
> The use case document is just about done, but we haven't really started discussing the proto document. We haven't met in Orlando, and are unlikely to meet in Berlin
>
> That's it for this report.
>
> Cheers
>
> WGC
>
> "

Instead of a WG progress report, what I had in mind was a separate 
report for each work item.   The report should briefly describe

1. The purpose of the work being undertaken
2. A description of the work being undertaken (including mention of 
major technologies on which the work is based)
3. All known parties and interests likely to be affected by the work
4. The current state of the work (what's been done, what hasn't been done)
5. Any major issues that have been identified but not resolved
6. Pointers to the WG's charter, the datatracker pages for each of the 
current draft document(s) associated with that work item, and any other 
useful material (e.g. open issues list, summaries of design decisions 
already taken and the rationale for each)

A person who is knowledgeable about current Internet protocols should be 
able to read that single document and understand what the WG is doing 
with this particular work item, what state it's in, whether or not it 
will affect that person's are of interest, and where to look for 
detailed information.

Keith


From moore@network-heretics.com  Fri May 17 19:30:09 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A663721F8FB3 for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:30:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.662
X-Spam-Level: 
X-Spam-Status: No, score=-3.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uFnR6thQEZUD for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:30:04 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 8C06621F8F24 for <ietf@ietf.org>; Fri, 17 May 2013 19:30:03 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CBB7E20920; Fri, 17 May 2013 22:30:02 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 17 May 2013 22:30:02 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=ws2ldEcIbdtRU+utHkU290 uO4Tk=; b=i48nao0E3no0XmrM5gXGybABUyb2GwN6Xe9q3IaaaRQpOlnyWGW8tJ KQz0DCVgSqDS0YmOcE2QIXUFSl8ilwcdmD0Q3wHujcMeW3RdFezAVNHiuV9DfCKn sRgSAhVJhv8hXvH+9KSiUCE7GvrE3zd9ufIoPHqWigwHoJalcLMpg=
X-Sasl-enc: z+OMTaV9+AeKuoNiLHMU7iTgXUXorFEoPlVdM4OSZi4k 1368844202
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 0A593C80008; Fri, 17 May 2013 22:30:01 -0400 (EDT)
Message-ID: <5196E7A6.9000807@network-heretics.com>
Date: Fri, 17 May 2013 22:29:58 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net> <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.com> <5196D997.7030909@network-heretics.com> <CABCOCHSZrG1U-Gzt6P9gygjopbeAm5QW2qkuBcSg2HoigAcfrw@mail.gmail.com>
In-Reply-To: <CABCOCHSZrG1U-Gzt6P9gygjopbeAm5QW2qkuBcSg2HoigAcfrw@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: Sat, 18 May 2013 02:30:09 -0000

On 05/17/2013 10:21 PM, Andy Bierman wrote:
>
> I notice that nowhere on this list is any mention of the charter 
> milestones
> or dates.  Is the Foo Proto draft due in 14 months or is it 14 months 
> behind
> schedule?  If the latter, why isn't the Foo WG meeting at the IETF?
>

I don't think milestones will be useful unless and until:

(a) they're defined in terms of not only concrete but also meaningful 
goals (e.g. "complete problem definition", "identify affected parties 
and groups representing their interests", "complete outline of initial 
design", but NOT "revise document X");
(b) we start automatically suspending the activities of groups that fail 
to meet them (no meetings, no new I-Ds accepted, mailing list traffic 
blocked), until such groups are formally rechartered; and
(c) IESG is reluctant to recharter groups that have repeatedly failed to 
meet milestones, especially if those groups haven't produced evidence of 
significant progress.

Keith


From moore@network-heretics.com  Fri May 17 19:52:05 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C84021F93BF for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:52:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.657
X-Spam-Level: 
X-Spam-Status: No, score=-3.657 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohMAX1jSoi0O for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:52:00 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 68A6121F9307 for <ietf@ietf.org>; Fri, 17 May 2013 19:52:00 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E15A420625; Fri, 17 May 2013 22:51:59 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Fri, 17 May 2013 22:51:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type; s=smtpout; bh=biib FzeiaqBSKxpVaMa1N4r8UHA=; b=g9Uf3QVEVLlDJ9lGlm+CXU2jEQWbB3QvgRTy mQukJBb0D+f+yj8gZsevzhSsnIxw9pogFrKYrIDH1UsB+cx4RMZb+WgujlDlOnyL +CuKhD4+zbG8Ap2zv9os9YDLeTm+x3qsC+rK/OjA8EuMYGl5XNrknWss5T9lpAF4 beLuTYc=
X-Sasl-enc: yenmjhRgfaF3PvfICyBsH6SqQo841YTTYUd2tf7tIdDI 1368845519
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id CB19B2000D3; Fri, 17 May 2013 22:51:58 -0400 (EDT)
Message-ID: <5196ECCA.8070801@network-heretics.com>
Date: Fri, 17 May 2013 22:51:54 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net> <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.com> <5196D997.7030909@network-heretics.com> <CABCOCHSZrG1U-Gzt6P9gygjopbeAm5QW2qkuBcSg2HoigAcfrw@mail.gmail.com> <5196E7A6.9000807@network-heretics.com> <CABCOCHSsMaCGEHxpyKeuyXoQdMqTVUtc0sw69MNeMmhy0wmLDw@mail.gmail.com>
In-Reply-To: <CABCOCHSsMaCGEHxpyKeuyXoQdMqTVUtc0sw69MNeMmhy0wmLDw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------080806090104030204060005"
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, 18 May 2013 02:52:05 -0000

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

On 05/17/2013 10:37 PM, Andy Bierman wrote:
>
> On Fri, May 17, 2013 at 7:29 PM, Keith Moore 
> <moore@network-heretics.com <mailto:moore@network-heretics.com>> wrote:
>
>
>     I don't think milestones will be useful unless and until:
>
>     (a) they're defined in terms of not only concrete but also
>     meaningful goals (e.g. "complete problem definition", "identify
>     affected parties and groups representing their interests",
>     "complete outline of initial design", but NOT "revise document X");
>     (b) we start automatically suspending the activities of groups
>     that fail to meet them (no meetings, no new I-Ds accepted, mailing
>     list traffic blocked), until such groups are formally rechartered; and
>     (c) IESG is reluctant to recharter groups that have repeatedly
>     failed to meet milestones, especially if those groups haven't
>     produced evidence of significant progress.
>
>
> I think we can find some middle ground between "ignore charter 
> milestones completely"
> and "autobot to terminate WGs behind schedule". :-)
>
Actually I think it might require an autobot.   Because someone 
(probably the responsible AD) has to evaluate a WG's progress, and ADs 
don't want to take the heat for shutting WGs down.   Better to put the 
responsibility on the chairs for completing the milestones and reporting 
to the AD before the shutdown deadline.

(of course, there could be a generous grace period between the milestone 
deadline and the actual shutdown, with warning messages sent to the WG 
chairs and ADs, etc.)

Keith


--------------080806090104030204060005
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 05/17/2013 10:37 PM, Andy Bierman
      wrote:<br>
    </div>
    <blockquote
cite="mid:CABCOCHSsMaCGEHxpyKeuyXoQdMqTVUtc0sw69MNeMmhy0wmLDw@mail.gmail.com"
      type="cite"><br>
      <div class="gmail_quote">On Fri, May 17, 2013 at 7:29 PM, Keith
        Moore <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:moore@network-heretics.com" target="_blank">moore@network-heretics.com</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <br>
          I don't think milestones will be useful unless and until:<br>
          <br>
          (a) they're defined in terms of not only concrete but also
          meaningful goals (e.g. "complete problem definition",
          "identify affected parties and groups representing their
          interests", "complete outline of initial design", but NOT
          "revise document X");<br>
          (b) we start automatically suspending the activities of groups
          that fail to meet them (no meetings, no new I-Ds accepted,
          mailing list traffic blocked), until such groups are formally
          rechartered; and<br>
          (c) IESG is reluctant to recharter groups that have repeatedly
          failed to meet milestones, especially if those groups haven't
          produced evidence of significant progress.<span class="HOEnZb"><font
              color="#888888"><br>
              <br>
            </font></span></blockquote>
        <div><br>
        </div>
        <div>I think we can find some middle ground between "ignore
          charter milestones completely"</div>
        <div>and "autobot to terminate WGs behind schedule". :-)</div>
        <br>
      </div>
    </blockquote>
    Actually I think it might require an autobot.&nbsp;&nbsp; Because someone
    (probably the responsible AD) has to evaluate a WG's progress, and
    ADs don't want to take the heat for shutting WGs down.&nbsp;&nbsp; Better to
    put the responsibility on the chairs for completing the milestones
    and reporting to the AD before the shutdown deadline.<br>
    <br>
    (of course, there could be a generous grace period between the
    milestone deadline and the actual shutdown, with warning messages
    sent to the WG chairs and ADs, etc.)<br>
    <br>
    Keith<br>
    <br>
  </body>
</html>

--------------080806090104030204060005--

From abdussalambaryun@gmail.com  Sat May 18 01:07:47 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C086F21F93BA for <ietf@ietfa.amsl.com>; Sat, 18 May 2013 01:07:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.127
X-Spam-Level: 
X-Spam-Status: No, score=-3.127 tagged_above=-999 required=5 tests=[AWL=0.472,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfy90THAv-IQ for <ietf@ietfa.amsl.com>; Sat, 18 May 2013 01:07:43 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4F421F9307 for <ietf@ietf.org>; Sat, 18 May 2013 01:07:43 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so4246792pab.27 for <ietf@ietf.org>; Sat, 18 May 2013 01:07:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=A9DyCRokxn+8ycY+8gfAC2arooXEJ3m1L1HWRVQVd60=; b=cd62g3rULAFD4wzFQzf3gqAdEm9w8t34Td0JBw+C2c2Gn9AsZP42oCwEmta8guNGbJ mjgRyw6BmKY9q/zVvFOycCnsybvqmQSUbl0vb/6opDogkV+IGwjpezjKeXe9DQZURXjC JAZ9BjrbBZt72qV2hGroHcszJBKRr+pnY2PakZR4PWwSYkhQs3m3PRljWdB82GBJOmTs 6f2q4Eu3KvvHQUnuY3B3XtHE5XgXJ2BPOqilUzwrm+Qx7oQTr5u2FnFu0tekHYsE0F3A E74MiwS6RMaHLqqwW+/tGH9FlmLBtZ9rf4YNxgh3mxZxarz5rW0vS+6yZKAXOiCc2BaE aIvg==
MIME-Version: 1.0
X-Received: by 10.66.144.5 with SMTP id si5mr52705989pab.6.1368864463352; Sat, 18 May 2013 01:07:43 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Sat, 18 May 2013 01:07:43 -0700 (PDT)
Date: Sat, 18 May 2013 10:07:43 +0200
Message-ID: <CADnDZ8-xsLVKfk=iSh2SfmVwSNazT0CV2_2O1bo3n8VcVAqRkQ@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 May 2013 08:07:48 -0000

The problem is that WG participants SHOULD follow/update their
milestones and take responsibility to progress work to thoes goals
direction. The Chair SHOULD follow the WG requests, or the Chair
SHOULD encourage discussing the milestones. I already requested before
that all WGs SHOULD discuss their milestones and update it in each
meeting or on the list. If no one cares then the result is WG failing
some-goals which no one realise until long, but some people outside
the IETF are watching such performance.

AB

On Fri, May 17, 2013 at 7:29 PM, Keith Moore <moore at
> network-heretics.com> wrote:
>
>
> I don't think milestones will be useful unless and until:
>
> (a) they're defined in terms of not only concrete but also meaningful
> goals (e.g. "complete problem definition", "identify affected parties
> and groups representing their interests", "complete outline of initial
> design", but NOT "revise document X");
> (b) we start automatically suspending the activities of groups that
> fail to meet them (no meetings, no new I-Ds accepted, mailing list
> traffic blocked), until such groups are formally rechartered; and
> (c) IESG is reluctant to recharter groups that have repeatedly failed
> to meet milestones, especially if those groups haven't produced
> evidence of significant progress.
>

From abdussalambaryun@gmail.com  Sat May 18 01:14:06 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC5B21F84D9 for <ietf@ietfa.amsl.com>; Sat, 18 May 2013 01:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0r1kHKxdc--S for <ietf@ietfa.amsl.com>; Sat, 18 May 2013 01:14:06 -0700 (PDT)
Received: from mail-da0-x233.google.com (mail-da0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id BB1BF21F93BF for <ietf@ietf.org>; Sat, 18 May 2013 01:14:05 -0700 (PDT)
Received: by mail-da0-f51.google.com with SMTP id h15so2818466dan.24 for <ietf@ietf.org>; Sat, 18 May 2013 01:14:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Af5tj119rD3k5QgUapVBsiYicKiAGiDVg2v6ESukcW8=; b=RQEWQG3I9CSnmciOcxxndaNAIelAKOnaC3sNHGYNYue/lfdN1fKIc34h72rcjE63wM EYcKF5rjEXoZrWnJQe1PewtzbHrQcqdVYxPPrvD9kGJlUccD8ER61Yrv2ic4ZkFVCUek +KV3MJLfoCE9ueOefUBWeCmo6n1jb2iaH1LZ+6PoyyRISU5A/ncdPA4XFE6bULHJiWmI 3H/s/KtKFus6N6AGIwbEZeCFcTzxzHIoryKBQe7Sqts1BBHrd7+sxV6BLSbSpqaMoITJ 10HYHSmrAI69xecj61linVT+3Aub/S4MBgjfb3i8wvwIbfF2f/JSzsC7nlWQW2lKIA5j Lt8Q==
MIME-Version: 1.0
X-Received: by 10.66.163.133 with SMTP id yi5mr45820453pab.93.1368864845466; Sat, 18 May 2013 01:14:05 -0700 (PDT)
Received: by 10.68.143.132 with HTTP; Sat, 18 May 2013 01:14:05 -0700 (PDT)
In-Reply-To: <CADnDZ8-xsLVKfk=iSh2SfmVwSNazT0CV2_2O1bo3n8VcVAqRkQ@mail.gmail.com>
References: <CADnDZ8-xsLVKfk=iSh2SfmVwSNazT0CV2_2O1bo3n8VcVAqRkQ@mail.gmail.com>
Date: Sat, 18 May 2013 10:14:05 +0200
Message-ID: <CADnDZ886sMEpcB0+g3Kut0K6rMguTCOE0MqQQDhEj=PA5O5FVg@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: moore@network-heretics.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 May 2013 08:14:06 -0000

> Instead of a WG progress report, what I had in mind was a separate report for each work item. The report should briefly describe

I agree with you totally, that work-item-report SHOULD be copied to AD
and WG. That report is needed mostly when the work does not target its
milestone, requesting new milestone with plans/reason.

AB

From l.wood@surrey.ac.uk  Sat May 18 04:40:11 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA1B121F92CB for <ietf@ietfa.amsl.com>; Sat, 18 May 2013 04:40:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elXtqyf8Uv-I for <ietf@ietfa.amsl.com>; Sat, 18 May 2013 04:40:07 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id BB46F21F92B7 for <ietf@ietf.org>; Sat, 18 May 2013 04:40:06 -0700 (PDT)
Received: from [195.245.231.67:58249] by server-11.bemta-5.messagelabs.com id CE/E7-26693-59867915; Sat, 18 May 2013 11:40:05 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-3.tower-82.messagelabs.com!1368877204!29938606!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26812 invoked from network); 18 May 2013 11:40:04 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-3.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 18 May 2013 11:40:04 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sat, 18 May 2013 12:40:03 +0100
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <ietf@ietf.org>
Date: Sat, 18 May 2013 12:40:03 +0100
Subject: RE: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Topic: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
Thread-Index: Ac5TnuXzOh4pmnGCTImkr/k5WfhgQQAHJQ+P
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E8A@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8-xsLVKfk=iSh2SfmVwSNazT0CV2_2O1bo3n8VcVAqRkQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-xsLVKfk=iSh2SfmVwSNazT0CV2_2O1bo3n8VcVAqRkQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 May 2013 11:40:12 -0000

> I already requested before that all WGs SHOULD
> discuss their milestones and update it in each
> meeting or on the list.

No-one cares what you requested.

Didn't you get banned from the MANET list for lack of useful content?

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

From jmh@joelhalpern.com  Sun May 19 11:58:15 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C2D21F8D70; Sun, 19 May 2013 11:58:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnPdHgmJCIaE; Sun, 19 May 2013 11:58:10 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0B621F8D71; Sun, 19 May 2013 11:58:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 02C731C0526; Sun, 19 May 2013 11:58:06 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-20.clppva.east.verizon.net [70.106.134.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 0F43B1C04D7; Sun, 19 May 2013 11:58:04 -0700 (PDT)
Message-ID: <519920BA.9040308@joelhalpern.com>
Date: Sun, 19 May 2013 14:58:02 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "A. Jean Mahoney" <mahoney@nostrum.com>
Subject: [Gen-art] review: draft-ietf-cuss-sip-uui-10
References: <5195550A.3000608@nostrum.com>
In-Reply-To: <5195550A.3000608@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, draft-ietf-cuss-sip-uui-all@tools.ietf.org, IETF discussion list <ietf@ietf.org>, cuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 May 2013 18:58:15 -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-cuss-sip-uui-10
     A Mechanism for Transporting User to User
         Call Control Information in SIP
Reviewer: Joel M. Halpern
Review Date: 19-May-2013
IETF LC End Date: 29-May-2013
IESG Telechat date: N/A

Summary: This document is nearly ready for publication as a Proposed 
Standard

Major issues:

Minor issues:
     The requirements discussions for redirection and referral (second 
paragraph of section 3, in regards REQ-3) includes what appears to be 
normative requirements on redirecting devices.
a) This would seem to belong in section 4 on Normative Definition.
b) It would seem that there ought to be some discussion of what happens 
with redirecting devices that do not understand this new UUI. (I presume 
things work, but I don't see how.)

Nits/editorial comments:
     In section 8.2, given that this is a WG document, should the "the 
authors believe" actually be "the WG believes"?  Or even, given IETF 
rough consensus on this document, "the IETF believes"?

From john-ietf@jck.com  Mon May 20 07:18:37 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF7D21F95E5 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 07:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G49p6jIrO7Hs for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 07:18:27 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB6921F8B07 for <ietf@ietf.org>; Mon, 20 May 2013 07:18:27 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UeQuw-0007h3-7a for ietf@ietf.org; Mon, 20 May 2013 10:18:26 -0400
Date: Mon, 20 May 2013 10:18:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
Message-ID: <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>
In-Reply-To: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 14:18:37 -0000

--On Monday, May 20, 2013 06:44 -0700 The IESG
<iesg-secretary@ietf.org> wrote:

> 
> The IESG has received a request from an individual submitter
> to consider the following document:
> - 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>   <draft-jabley-dnsext-eui48-eui64-rrtypes-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-06-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.

This is not my primary (or even secondary) area of expertise
but, given that the RR space is not unlimited even though it is
large, wouldn't it be better to have a single RRtype for
IEEE-based EUIs with a flag or other indicator in the DATA field
as to whether a 48 bit or 64 bit identifier was present?

In addition to saving an RRTYPE slot, my recollection of the
uses of EUI-64 is that an application trying to look up an EUI
may not, in the general case, know whether the device and its
EUI are of the 48 or 64 bit persuasions.  If that is correct, a
single RRTYPE and a length/type indicator in the DATA would
avoid a two-stage lookup and/or unnecessary use of QTYPE=ANY.
The same one RRTYPE model would, with even a modicum of good
design, make transition easier when the IEEE goes interplanetary
or interstellar and discovers a need for EUI-128 (or some other
length > 64).

If there really are significant advantages to having two
separate RRTYPEs that override the considerations above, it
seems to me that the reasoning for doing so should at least be
briefly explained in the document.

    john


From joelja@bogus.com  Mon May 20 07:53:37 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1552421F9048 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 07:53:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_53=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AEHo6mDy3HyI for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 07:53:36 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 73D0A21F8976 for <ietf@ietf.org>; Mon, 20 May 2013 07:53:36 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4KErZ8M084143 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 20 May 2013 14:53:35 GMT (envelope-from joelja@bogus.com)
Message-ID: <519A38E9.3050601@bogus.com>
Date: Mon, 20 May 2013 07:53:29 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>
In-Reply-To: <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 20 May 2013 14:53:35 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 14:53:37 -0000

On 5/20/13 7:18 AM, John C Klensin wrote:
>
> --On Monday, May 20, 2013 06:44 -0700 The IESG
> <iesg-secretary@ietf.org> wrote:
>
>> The IESG has received a request from an individual submitter
>> to consider the following document:
>> - 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>>    <draft-jabley-dnsext-eui48-eui64-rrtypes-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-06-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.
> This is not my primary (or even secondary) area of expertise
> but, given that the RR space is not unlimited even though it is
> large, wouldn't it be better to have a single RRtype for
> IEEE-based EUIs with a flag or other indicator in the DATA field
> as to whether a 48 bit or 64 bit identifier was present?
the basis for assignment of rr-types is expert review. Whether the draft 
advances or not the rr-types have been assigned.

http://tools.ietf.org/html/rfc6895#section-3.1.1

http://www.iana.org/assignments/dns-parameters/dns-parameters.xml#dns-parameters-3

> In addition to saving an RRTYPE slot, my recollection of the
> uses of EUI-64 is that an application trying to look up an EUI
> may not, in the general case, know whether the device and its
> EUI are of the 48 or 64 bit persuasions.  If that is correct, a
> single RRTYPE and a length/type indicator in the DATA would
> avoid a two-stage lookup and/or unnecessary use of QTYPE=ANY.
> The same one RRTYPE model would, with even a modicum of good
> design, make transition easier when the IEEE goes interplanetary
> or interstellar and discovers a need for EUI-128 (or some other
> length > 64).
>
> If there really are significant advantages to having two
> separate RRTYPEs that override the considerations above, it
> seems to me that the reasoning for doing so should at least be
> briefly explained in the document.
>
>      john
>


From john-ietf@jck.com  Mon May 20 08:56:29 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5BD21F8EB2 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 08:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZWMt+Db8PUn for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 08:56:25 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DAD1F21F934B for <ietf@ietf.org>; Mon, 20 May 2013 08:56:24 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UeSRj-0007pC-BB; Mon, 20 May 2013 11:56:23 -0400
Date: Mon, 20 May 2013 11:56:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
Message-ID: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 15:56:29 -0000

--On Monday, May 20, 2013 07:53 -0700 joel jaeggli
<joelja@bogus.com> wrote:

>...
>> This is not my primary (or even secondary) area of expertise
>> but, given that the RR space is not unlimited even though it
>> is large, wouldn't it be better to have a single RRtype for
>> IEEE-based EUIs with a flag or other indicator in the DATA
>> field as to whether a 48 bit or 64 bit identifier was present?

> the basis for assignment of rr-types is expert review. Whether
> the draft advances or not the rr-types have been assigned.
> 
> http://tools.ietf.org/html/rfc6895#section-3.1.1
> 
> http://www.iana.org/assignments/dns-parameters/dns-parameters.
> xml#dns-parameters-3

Joel,

I don't know who the current expert is and, for the moment, am
glad I don't and don't intend to check.  I believe there is
broad consensus in the community that having something as
significant as an RRTYPE documented in the RFC Series is a good
idea.  Certainly leaving the reference pointing, long-term, to
an I-D would not be a good idea (and would violate several other
principles).

However, if 

(i) the expert review consists largely of making sure
	that the template contains the right information and the
	ducks are not obviously out of line rather than a
	design/architectural review with at least meaningful
	potential for community review of the request, and 
	
(ii) the response to a design/architectural concern
	raised during IETF LC is essentially "too late, code
	points already allocated", and
	
(iii) "Proposed Standard" still does not imply
	"recommended" and the alternative to approving the I-D
	for that category is non-publication,
	
then I would like to understand, as a procedural matter, what
the IETF Last Call is about.  Certainly it is not for editorial
review; that is the RFC Editor's job and there are, IMO, no
glaring editorial problems.  If the RRTYPEs have been allocated
and can't be un-allocated and this is in use, then there is
nothing to propose as an individual submission for
standardization: an informational document to inform the
community about what this is about would be both appropriate and
sufficient.  

Beyond that, your shepherd's report implies that the issue I
raised may have been discussed and successfully resolved in
DNSEXT.   If that is the case, an explanation in the document
about the tradeoffs and decision would still be appropriate.

Alternatively and especially if there wasn't clear consensus in
DNSEXT, if this really is to be processed as a Proposed
Standard, then a suggestion during IETF Last Call that the IETF
Standard way to represent EUIs in the DNS should be a single
RRTYPE with length/type information in the DATA is still in
order: the community could reasonably conclude that the single
RRTYPE is a better solution, that the single type should be
allocated, and that these two types should be deprecated.   We
have certainly done similar things before with other protocols
and parameters that were already in use before standardization
was proposed from an individual submission.

    john

p.s. I've tried reading your shepherd writeup now in three
different browsers.  It appears to be formatted for extremely
long (paragraph-length) lines, with no provision for automatic
wrapping to fit the page frame.  That means that trying to read
and understand it requires extensive horizontal scrolling, which
is a fairly large impediment and, although I assume
unintentionally, a way to discourage anyone but the most
determined of readers from actually reading it.  May I suggest
that the IESG, on a priority basis, either get the format of
those writeup pages changed so that they wrap appropriately or
that it insist that writeups conform to RFC/I-D norms for line
lengths.



From paul.hoffman@vpnc.org  Mon May 20 09:24:16 2013
Return-Path: <paul.hoffman@vpnc.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 279C721F8ED8 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:24:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level: 
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DnTf-j6LBmrR for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:24:15 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8A88821F8D90 for <ietf@ietf.org>; Mon, 20 May 2013 09:24:15 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4KGODAS033204 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 20 May 2013 09:24:13 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
Date: Mon, 20 May 2013 09:24:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <130972D1-30A7-45FE-8A31-7B6B1EEA33EE@vpnc.org>
References: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
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, 20 May 2013 16:24:16 -0000

On May 20, 2013, at 8:56 AM, John C Klensin <john-ietf@jck.com> wrote:

> However, if=20
>=20
> (i) the expert review consists largely of making sure
> 	that the template contains the right information and the
> 	ducks are not obviously out of line rather than a
> 	design/architectural review with at least meaningful
> 	potential for community review of the request, and=20
> =09
> (ii) the response to a design/architectural concern
> 	raised during IETF LC is essentially "too late, code
> 	points already allocated", and
> =09
> (iii) "Proposed Standard" still does not imply
> 	"recommended" and the alternative to approving the I-D
> 	for that category is non-publication,
> =09
> then I would like to understand, as a procedural matter, what
> the IETF Last Call is about.

Whether or not the document clear enough for an implementor to create =
interoperable software from. That's what the IETF is supposed to be =
doing, yes?

>  Certainly it is not for editorial
> review; that is the RFC Editor's job and there are, IMO, no
> glaring editorial problems.

Correct.

>  If the RRTYPEs have been allocated
> and can't be un-allocated and this is in use, then there is
> nothing to propose as an individual submission for
> standardization: an informational document to inform the
> community about what this is about would be both appropriate and
> sufficient.

...only if the authors don't care about interoperability between =
implementations.

An author asking for IETF-wide review seems like something that should =
be encouraged, not pecked to death.

--Paul Hoffman=

From d3e3e3@gmail.com  Mon May 20 09:26:52 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 743EC21F92FC for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yzLrOfBGB7HG for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:26:51 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2539A21F92E8 for <ietf@ietf.org>; Mon, 20 May 2013 09:26:51 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id un3so7245545obb.19 for <ietf@ietf.org>; Mon, 20 May 2013 09:26:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=Y1fyU4NHG/HpnOFsAL5bSeK6892oZA4Q4qL6TxC+eAk=; b=xmTb7+tO8pIsS8W8vEZnJ54BE99g4ApDWjjLvP3te2riQqWz1Y1bjJQFKb1q6z+ayL 5r8oHvp7doW4gFnUMS6JE/mpCIjnhC5/QQJYRluJgzTX6YGey1uCQ0G2d/wurYfjTZvG mSL5w5vE0HXfpLrvE1HI+1u/GUotPQLY6Ff5NXCf8BbViNkTnaccYkskK6Q2vYIWejyR ThZDB8xn+ezME0e5JvIQsbjgO4crPR7UbxROwuKGxG8Wl8bv0rJCqp5xeX2vqmgd81xp CkDRoqoFWRyXcrtiumyEVP/2mCoQ23RqWaieHVGAMAgOxdDH3sMhvkohVPxbxYhENGMw tz7g==
X-Received: by 10.60.145.239 with SMTP id sx15mr22246285oeb.57.1369067210674;  Mon, 20 May 2013 09:26:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.162.233 with HTTP; Mon, 20 May 2013 09:26:30 -0700 (PDT)
In-Reply-To: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
References: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 20 May 2013 12:26:30 -0400
Message-ID: <CAF4+nEH0DtFVAENeq3vOq_nrykmbJPgzV5TGtYzJ61VP=vtmgQ@mail.gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 16:26:52 -0000

Hi John,

On Mon, May 20, 2013 at 11:56 AM, John C Klensin <john-ietf@jck.com> wrote:
> --On Monday, May 20, 2013 07:53 -0700 joel jaeggli
> <joelja@bogus.com> wrote:
>
>>...
>>> This is not my primary (or even secondary) area of expertise
>>> but, given that the RR space is not unlimited even though it
>>> is large, wouldn't it be better to have a single RRtype for
>>> IEEE-based EUIs with a flag or other indicator in the DATA
>>> field as to whether a 48 bit or 64 bit identifier was present?
>
>> the basis for assignment of rr-types is expert review. Whether
>> the draft advances or not the rr-types have been assigned.
>>
>> http://tools.ietf.org/html/rfc6895#section-3.1.1
>>
>> http://www.iana.org/assignments/dns-parameters/dns-parameters.
>> xml#dns-parameters-3
>
> Joel,
>
> I don't know who the current expert is and, for the moment, am
> glad I don't and don't intend to check.  I believe there is
> broad consensus in the community that having something as
> significant as an RRTYPE documented in the RFC Series is a good
> idea.  Certainly leaving the reference pointing, long-term, to
> an I-D would not be a good idea (and would violate several other
> principles).

There has been a long term fight to make RRTYPEs easy to get, a fight
in which substantial victory has only recently been achieved
(RFC6895). The result of tight control over RRTYPEs is that most new
uses just take the path of least resistance and overload the TXT
RRTYPE, something which requires no one's permission but, as per RFC
5507, has significant long term disadvantages. One lesson of the
Internet has been the benefits of FREEDOM TO INNOVATE. In my opinion,
most IETF WGs impose tighter control over code points that necessary
most of the time (note most, not all).

> However, if
>
> (i) the expert review consists largely of making sure
>         that the template contains the right information and the
>         ducks are not obviously out of line rather than a
>         design/architectural review with at least meaningful
>         potential for community review of the request, and

The guidelines are in RFC 6895 which I recommend you consult. There is
no requirement for community review. A primary concern is that the
RRTYPE can be safely handled an unknown RRTYPE (or is an ignorable
meta RRTYPE). The community has people that will complain about and
delay andy new RRTYPE.

How is an RRTYPE any more earth-shaking than, say, an AFN number, a
range of which are available on a first-come, first-served basis? What
are these "principles" you refer to above that require RFC
documentation of RRTPYEs when no documentation whatsoever is required
for some AFN numbers?

> (ii) the response to a design/architectural concern
>         raised during IETF LC is essentially "too late, code
>         points already allocated", and
>
> (iii) "Proposed Standard" still does not imply
>         "recommended" and the alternative to approving the I-D
>         for that category is non-publication,
>
> then I would like to understand, as a procedural matter, what
> the IETF Last Call is about.  Certainly it is not for editorial
> review; that is the RFC Editor's job and there are, IMO, no
> glaring editorial problems.  If the RRTYPEs have been allocated
> and can't be un-allocated and this is in use, then there is
> nothing to propose as an individual submission for
> standardization: an informational document to inform the
> community about what this is about would be both appropriate and
> sufficient.

Perhaps it should be informational. I believe the author was
originally going to submit as an Informational Independent submission.
Others, including myself, suggested different paths. Perhaps we were
mistaken.

The perfect is always the enemy of the good.

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

> Beyond that, your shepherd's report implies that the issue I
> raised may have been discussed and successfully resolved in
> DNSEXT.   If that is the case, an explanation in the document
> about the tradeoffs and decision would still be appropriate.
>
> Alternatively and especially if there wasn't clear consensus in
> DNSEXT, if this really is to be processed as a Proposed
> Standard, then a suggestion during IETF Last Call that the IETF
> Standard way to represent EUIs in the DNS should be a single
> RRTYPE with length/type information in the DATA is still in
> order: the community could reasonably conclude that the single
> RRTYPE is a better solution, that the single type should be
> allocated, and that these two types should be deprecated.   We
> have certainly done similar things before with other protocols
> and parameters that were already in use before standardization
> was proposed from an individual submission.
>
>     john
>
> p.s. I've tried reading your shepherd writeup now in three
> different browsers.  It appears to be formatted for extremely
> long (paragraph-length) lines, with no provision for automatic
> wrapping to fit the page frame.  That means that trying to read
> and understand it requires extensive horizontal scrolling, which
> is a fairly large impediment and, although I assume
> unintentionally, a way to discourage anyone but the most
> determined of readers from actually reading it.  May I suggest
> that the IESG, on a priority basis, either get the format of
> those writeup pages changed so that they wrap appropriately or
> that it insist that writeups conform to RFC/I-D norms for line
> lengths.

From barryleiba.mailing.lists@gmail.com  Mon May 20 09:31:12 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B5A21F95EA for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.772
X-Spam-Level: 
X-Spam-Status: No, score=-102.772 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QqEHmq7uvPnN for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:31:07 -0700 (PDT)
Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) by ietfa.amsl.com (Postfix) with ESMTP id 39F5621F95EB for <ietf@ietf.org>; Mon, 20 May 2013 09:31:05 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hv10so5292816vcb.6 for <ietf@ietf.org>; Mon, 20 May 2013 09:31:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=PGDHN/MpT4GBlhyp1kFjGi28A+HlJwkAYdPP+wtvTw4=; b=KR7eUl1GB4Z8l4muGS+8Ky3WL0iNOcx5pNW3IN3TEWro3sKnHUotENuvDfBi5cLYyc caIH908VUkaSnyGTvf7xrUxjAdYCdEOT4bhiZezGcLWBd9LRBF0be3KMemmJPvhAfBo0 q+9UGYevOGUX7SleXV4dFuVFTb/xK0oRZPwLBsGkDb4Ye+E5RffkMPD6+HdGbvgoiDi/ rw/T/mXa2IhyjbiWdg0uTHZkD26eiX231yJCSHDLF7eW1O6e1Ja+AY17AF2qcrs9WKFx PoM6P7LGaElnewW/nTVzg4yDy+yOQqWXgKb/V99FyOFe5WAZ7CsepdAVT3Ju5UUm4VUr Zzmg==
MIME-Version: 1.0
X-Received: by 10.221.9.70 with SMTP id ov6mr34517818vcb.72.1369067464219; Mon, 20 May 2013 09:31:04 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.6.233 with HTTP; Mon, 20 May 2013 09:31:04 -0700 (PDT)
In-Reply-To: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
References: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
Date: Mon, 20 May 2013 12:31:04 -0400
X-Google-Sender-Auth: qxJwDXkeuH5bMfQ600el52HXKFs
Message-ID: <CAC4RtVCNDV1L=_Wkpxp3=GXGC4d0USu_w+6_f=NjVh5pKyOBrA@mail.gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
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, 20 May 2013 16:31:12 -0000

Just on the writeup tooling question:

> p.s. I've tried reading your shepherd writeup now in three
> different browsers.  It appears to be formatted for extremely
> long (paragraph-length) lines, with no provision for automatic
> wrapping to fit the page frame.  That means that trying to read
> and understand it requires extensive horizontal scrolling, which
> is a fairly large impediment and, although I assume
> unintentionally, a way to discourage anyone but the most
> determined of readers from actually reading it.  May I suggest
> that the IESG, on a priority basis, either get the format of
> those writeup pages changed so that they wrap appropriately or
> that it insist that writeups conform to RFC/I-D norms for line
> lengths.

This happens in a number of places in the datatracker, and there's an
open ticket for the tools team to make a general fix.  In the
meantime, we have to try to remember to put in line-breaks manually.
When I encounter something that doesn't have them, I just copy/paste
into my favourite local editor, and read it there.

Barry

From andy@yumaworks.com  Fri May 17 19:21:07 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86BCE21F949D for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.725
X-Spam-Level: 
X-Spam-Status: No, score=-1.725 tagged_above=-999 required=5 tests=[AWL=0.252,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3H3RoIBfYeI for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:21:06 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 90CC521F9488 for <ietf@ietf.org>; Fri, 17 May 2013 19:21:05 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 16so10802761iea.31 for <ietf@ietf.org>; Fri, 17 May 2013 19:21:05 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=AQcPTLLjIvtVWpQpLG1mLiQKP9GwznCUCbPyteuv5yE=; b=l+BAo6z/80eXP6lrT8hbL7gf149c6PVk9VrvLLAcy5tlcTujmafjPWR3Hn4HH+tSqx D01ZP+VtHpE4V584U/SS9ecA5NZTxir3BpSRGFyaaG1KSNjayERPbQ9zwTcK3G9xTKAX aLszG88rb2D4Bk7NHhqYfO89h8TXUORrDdcibfv2OnviVHhEz3CDLMQAlSUOWH4vUU9U ex+Wu6rSBHW/czhK4Oi4gwwXXZZhuLKb9xWGpGoVeYMzvuZPRQrLZxI/K9Gb9JsmgkgL +8XW4dxs3fsFGP6fDY0PY7TghgmDYbKWO/kSo8JzYmVKAP/FRMNXW2B1qwySIkY7l/bj MmLw==
MIME-Version: 1.0
X-Received: by 10.50.25.36 with SMTP id z4mr128518igf.33.1368843665101; Fri, 17 May 2013 19:21:05 -0700 (PDT)
Received: by 10.231.120.74 with HTTP; Fri, 17 May 2013 19:21:04 -0700 (PDT)
In-Reply-To: <5196D997.7030909@network-heretics.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net> <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.com> <5196D997.7030909@network-heretics.com>
Date: Fri, 17 May 2013 19:21:04 -0700
Message-ID: <CABCOCHSZrG1U-Gzt6P9gygjopbeAm5QW2qkuBcSg2HoigAcfrw@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Andy Bierman <andy@yumaworks.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=047d7bd75b2069859604dcf4c0fc
X-Gm-Message-State: ALoCoQnuamUKr2IhQsxiV4DOm1NxOPArqSPFlVO1fT+dbt/np4WG5MSuay9KV9+d2TRHv5GNJyq6
X-Mailman-Approved-At: Mon, 20 May 2013 09:54:27 -0700
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, 18 May 2013 02:21:07 -0000

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

On Fri, May 17, 2013 at 6:29 PM, Keith Moore <moore@network-heretics.com>wrote:

> On 05/17/2013 04:36 PM, Yoav Nir wrote:
>
>> On May 17, 2013, at 6:37 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>>
>>  On 5/17/2013 7:01 AM, Keith Moore wrote:
>>>
>>>> But WGs should be able to periodically summarize what they're doing -
>>>> what problem they're trying to solve, what approach they're taking, what
>>>> technologies they're using, what major decisions they've made, what the
>>>> current sticking points seem to be, what problems are as yet unresolved,
>>>> what potential for cross-group and cross-area effects have been
>>>> identified, and what efforts have been made to get the affected parties
>>>> in the loop.   For most groups that summary should be maybe 2-3 pages.
>>>> The ADs should be able to verify that those summaries are accurate and
>>>> reasonably complete, or appoint a trusted WG observer other than the
>>>> chair to review each summary. ADs and other members of the community
>>>> should be able to view those summaries and comment on their accuracy.
>>>>
>>>
>>> The idea that working groups should be required to issue periodic
>>> project progress reports seems strikingly reasonable and useful.
>>>
>>> This makes the folks who are the most knowledgeable responsible for
>>> assessing their work, and should facilitate public review. Recording the
>>> sequence of reports into the wg datatracker could nicely allow evaluating
>>> progress over time.
>>>
>>> It also, of course, nicely distributes the work.
>>>
>>> d/
>>>
>> "
>> From: WG Chair
>> To: ietf@ietf.org
>> Sunbject: Progress Report - Foo WG
>>
>> There has been zero activity on the FOO list in the last three months
>> (except for that "Fake Conference" message everybody got last month). I've
>> tried emailing the WG document authors twice, but they're not answering my
>> emails.
>>
>> So, the WG has 2 documents: draft-ietf-foo-use-cases-03, and
>> draft-ietf-foo-proto-01.
>>
>> The use case document is just about done, but we haven't really started
>> discussing the proto document. We haven't met in Orlando, and are unlikely
>> to meet in Berlin
>>
>> That's it for this report.
>>
>> Cheers
>>
>> WGC
>>
>> "
>>
>
> Instead of a WG progress report, what I had in mind was a separate report
> for each work item.   The report should briefly describe
>
> 1. The purpose of the work being undertaken
> 2. A description of the work being undertaken (including mention of major
> technologies on which the work is based)
> 3. All known parties and interests likely to be affected by the work
> 4. The current state of the work (what's been done, what hasn't been done)
> 5. Any major issues that have been identified but not resolved
> 6. Pointers to the WG's charter, the datatracker pages for each of the
> current draft document(s) associated with that work item, and any other
> useful material (e.g. open issues list, summaries of design decisions
> already taken and the rationale for each)
>
> A person who is knowledgeable about current Internet protocols should be
> able to read that single document and understand what the WG is doing with
> this particular work item, what state it's in, whether or not it will
> affect that person's are of interest, and where to look for detailed
> information.
>
>
This seems like a good idea, although maybe a bit formal.
IMO, big surprises at the tail end that cause lots of work to
be thrown out are evidence of a management failure.
The IESG and WG chairs should be more proactive wrt/ avoiding
late surprises from ever happening.

I notice that nowhere on this list is any mention of the charter milestones
or dates.  Is the Foo Proto draft due in 14 months or is it 14 months behind
schedule?  If the latter, why isn't the Foo WG meeting at the IETF?



Keith
>
>
Andy

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

<br><br><div class=3D"gmail_quote">On Fri, May 17, 2013 at 6:29 PM, Keith M=
oore <span dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" ta=
rget=3D"_blank">moore@network-heretics.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
On 05/17/2013 04:36 PM, Yoav Nir wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On May 17, 2013, at 6:37 PM, Dave Crocker &lt;<a href=3D"mailto:dhc@dcrocke=
r.net" target=3D"_blank">dhc@dcrocker.net</a>&gt; wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 5/17/2013 7:01 AM, Keith Moore wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
But WGs should be able to periodically summarize what they&#39;re doing -<b=
r>
what problem they&#39;re trying to solve, what approach they&#39;re taking,=
 what<br>
technologies they&#39;re using, what major decisions they&#39;ve made, what=
 the<br>
current sticking points seem to be, what problems are as yet unresolved,<br=
>
what potential for cross-group and cross-area effects have been<br>
identified, and what efforts have been made to get the affected parties<br>
in the loop. =A0 For most groups that summary should be maybe 2-3 pages.<br=
>
The ADs should be able to verify that those summaries are accurate and<br>
reasonably complete, or appoint a trusted WG observer other than the<br>
chair to review each summary. ADs and other members of the community<br>
should be able to view those summaries and comment on their accuracy.<br>
</blockquote>
<br>
The idea that working groups should be required to issue periodic project p=
rogress reports seems strikingly reasonable and useful.<br>
<br>
This makes the folks who are the most knowledgeable responsible for assessi=
ng their work, and should facilitate public review. Recording the sequence =
of reports into the wg datatracker could nicely allow evaluating progress o=
ver time.<br>

<br>
It also, of course, nicely distributes the work.<br>
<br>
d/<br>
</blockquote>
&quot;<br>
From: WG Chair<br>
To: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br=
>
Sunbject: Progress Report - Foo WG<br>
<br>
There has been zero activity on the FOO list in the last three months (exce=
pt for that &quot;Fake Conference&quot; message everybody got last month). =
I&#39;ve tried emailing the WG document authors twice, but they&#39;re not =
answering my emails.<br>

<br>
So, the WG has 2 documents: draft-ietf-foo-use-cases-03, and draft-ietf-foo=
-proto-01.<br>
<br>
The use case document is just about done, but we haven&#39;t really started=
 discussing the proto document. We haven&#39;t met in Orlando, and are unli=
kely to meet in Berlin<br>
<br>
That&#39;s it for this report.<br>
<br>
Cheers<br>
<br>
WGC<br>
<br>
&quot;<br>
</blockquote>
<br>
Instead of a WG progress report, what I had in mind was a separate report f=
or each work item. =A0 The report should briefly describe<br>
<br>
1. The purpose of the work being undertaken<br>
2. A description of the work being undertaken (including mention of major t=
echnologies on which the work is based)<br>
3. All known parties and interests likely to be affected by the work<br>
4. The current state of the work (what&#39;s been done, what hasn&#39;t bee=
n done)<br>
5. Any major issues that have been identified but not resolved<br>
6. Pointers to the WG&#39;s charter, the datatracker pages for each of the =
current draft document(s) associated with that work item, and any other use=
ful material (e.g. open issues list, summaries of design decisions already =
taken and the rationale for each)<br>

<br>
A person who is knowledgeable about current Internet protocols should be ab=
le to read that single document and understand what the WG is doing with th=
is particular work item, what state it&#39;s in, whether or not it will aff=
ect that person&#39;s are of interest, and where to look for detailed infor=
mation.<span class=3D"HOEnZb"><font color=3D"#888888"><br>

<br></font></span></blockquote><div><br></div><div>This seems like a good i=
dea, although maybe a bit formal.</div><div>IMO, big surprises at the tail =
end that cause lots of work to</div><div>be thrown out are evidence of a ma=
nagement failure.=A0</div>
<div>The IESG and WG chairs should be more proactive wrt/ avoiding</div><di=
v>late surprises from ever happening.</div><div><br></div><div>I notice tha=
t nowhere on this list is any mention of the charter milestones</div><div>
or dates. =A0Is the Foo Proto draft due in 14 months or is it 14 months beh=
ind</div><div>schedule? =A0If the latter, why isn&#39;t the Foo WG meeting =
at the IETF?</div><div><br></div><div><br></div><div><br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888">
Keith<br>
<br>
</font></span></blockquote></div><br><div>Andy</div><div><br></div>

--047d7bd75b2069859604dcf4c0fc--

From andy@yumaworks.com  Fri May 17 19:37:25 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99A7521F90EB for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.741
X-Spam-Level: 
X-Spam-Status: No, score=-1.741 tagged_above=-999 required=5 tests=[AWL=0.236,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q7UxcNK4zKMv for <ietf@ietfa.amsl.com>; Fri, 17 May 2013 19:37:25 -0700 (PDT)
Received: from mail-ia0-x235.google.com (mail-ia0-x235.google.com [IPv6:2607:f8b0:4001:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id E1BC621F90AC for <ietf@ietf.org>; Fri, 17 May 2013 19:37:23 -0700 (PDT)
Received: by mail-ia0-f181.google.com with SMTP id y25so5517506iay.40 for <ietf@ietf.org>; Fri, 17 May 2013 19:37:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=IZdgzyN67vZF4TcFxU3PU6WsjBXp8fl9NOUysDOHiGw=; b=VaDW2nQrHPri9AX5ItVKkyBkft7bIq/5dUPeIeYaUhVKLL0+HLERErsIJ+ASi2zWG3 k22guXhjaeGax3jKiA/iYfIH9AgLwDyYbl7ILDWDn9x3kUo+FeLb4u1fbZfFp+pfnmVa c78xwz4JqePO2OHmsj1HhQIribIyjUx9uUF/eadnkuIEGG4G51awEYJPiNajBdHOJ/fj OYEGpkSjjtC45T7WzRwapHxThdKqcxeEsEbDBlXNM9/RcuMb02LHVRWSBSH1GPsNJlxs ZnyBYEPtFtoye1ljWFQ3JvCW0eFupRvQwIohDSYB4IfuXJ63OZGXkh0hs/wFdzOw6vwp jiyA==
MIME-Version: 1.0
X-Received: by 10.50.61.232 with SMTP id t8mr136883igr.37.1368844643452; Fri, 17 May 2013 19:37:23 -0700 (PDT)
Received: by 10.231.120.74 with HTTP; Fri, 17 May 2013 19:37:23 -0700 (PDT)
In-Reply-To: <5196E7A6.9000807@network-heretics.com>
References: <00c301ce51ab$090b8350$1b2289f0$@olddog.co.uk> <519507ED.4090805@dcrocker.net> <CAPv4CP-GpA7nV_joEF4Z5NQ5R1F8iCpF1dSGo8u5jo0DcLpqEw@mail.gmail.com> <F46B3DFB-DC3C-4AD4-8D1A-5694E89D6E9F@checkpoint.com> <51955685.2060009@network-heretics.com> <4209D121-0428-422E-8636-2352D0DF436C@checkpoint.com> <51963854.2050001@network-heretics.com> <51964EBE.4070709@dcrocker.net> <1C4EEA5C-3496-4D43-A2B9-849ACCB75565@checkpoint.com> <5196D997.7030909@network-heretics.com> <CABCOCHSZrG1U-Gzt6P9gygjopbeAm5QW2qkuBcSg2HoigAcfrw@mail.gmail.com> <5196E7A6.9000807@network-heretics.com>
Date: Fri, 17 May 2013 19:37:23 -0700
Message-ID: <CABCOCHSsMaCGEHxpyKeuyXoQdMqTVUtc0sw69MNeMmhy0wmLDw@mail.gmail.com>
Subject: Re: Is this an elephant? [Was: call for ideas: tail-heavy IETF process]
From: Andy Bierman <andy@yumaworks.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=047d7bdc05e8b9d9df04dcf4fa8b
X-Gm-Message-State: ALoCoQlM9XHjW8JMbgb2qkqm72XM2jGw9MbHjId0wNZ2xkVWSEb7tQJMEZVDTvyqhJKu/fWfIjCB
X-Mailman-Approved-At: Mon, 20 May 2013 09:54:27 -0700
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, 18 May 2013 02:37:25 -0000

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

On Fri, May 17, 2013 at 7:29 PM, Keith Moore <moore@network-heretics.com>wrote:

> On 05/17/2013 10:21 PM, Andy Bierman wrote:
>
>>
>> I notice that nowhere on this list is any mention of the charter
>> milestones
>> or dates.  Is the Foo Proto draft due in 14 months or is it 14 months
>> behind
>> schedule?  If the latter, why isn't the Foo WG meeting at the IETF?
>>
>>
> I don't think milestones will be useful unless and until:
>
> (a) they're defined in terms of not only concrete but also meaningful
> goals (e.g. "complete problem definition", "identify affected parties and
> groups representing their interests", "complete outline of initial design",
> but NOT "revise document X");
> (b) we start automatically suspending the activities of groups that fail
> to meet them (no meetings, no new I-Ds accepted, mailing list traffic
> blocked), until such groups are formally rechartered; and
> (c) IESG is reluctant to recharter groups that have repeatedly failed to
> meet milestones, especially if those groups haven't produced evidence of
> significant progress.
>
>
I think we can find some middle ground between "ignore charter milestones
completely"
and "autobot to terminate WGs behind schedule". :-)

Keith
>
>
Andy

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

<br><br><div class=3D"gmail_quote">On Fri, May 17, 2013 at 7:29 PM, Keith M=
oore <span dir=3D"ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" ta=
rget=3D"_blank">moore@network-heretics.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
On 05/17/2013 10:21 PM, Andy Bierman wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I notice that nowhere on this list is any mention of the charter milestones=
<br>
or dates. =A0Is the Foo Proto draft due in 14 months or is it 14 months beh=
ind<br>
schedule? =A0If the latter, why isn&#39;t the Foo WG meeting at the IETF?<b=
r>
<br>
</blockquote>
<br>
I don&#39;t think milestones will be useful unless and until:<br>
<br>
(a) they&#39;re defined in terms of not only concrete but also meaningful g=
oals (e.g. &quot;complete problem definition&quot;, &quot;identify affected=
 parties and groups representing their interests&quot;, &quot;complete outl=
ine of initial design&quot;, but NOT &quot;revise document X&quot;);<br>

(b) we start automatically suspending the activities of groups that fail to=
 meet them (no meetings, no new I-Ds accepted, mailing list traffic blocked=
), until such groups are formally rechartered; and<br>
(c) IESG is reluctant to recharter groups that have repeatedly failed to me=
et milestones, especially if those groups haven&#39;t produced evidence of =
significant progress.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br></font></span></blockquote><div><br></div><div>I think we can find some=
 middle ground between &quot;ignore charter milestones completely&quot;</di=
v><div>and &quot;autobot to terminate WGs behind schedule&quot;. :-)</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font =
color=3D"#888888">
Keith<br>
<br>
</font></span></blockquote></div><br><div>Andy</div><div><br></div>

--047d7bdc05e8b9d9df04dcf4fa8b--

From joelja@bogus.com  Mon May 20 09:55:20 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A66321F96B8 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:55:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.631
X-Spam-Level: 
X-Spam-Status: No, score=-102.631 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzxcm4r78qZE for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 09:55:19 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7A29121F9648 for <ietf@ietf.org>; Mon, 20 May 2013 09:55:19 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4KGtIME085480 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 20 May 2013 16:55:19 GMT (envelope-from joelja@bogus.com)
Message-ID: <519A5571.10708@bogus.com>
Date: Mon, 20 May 2013 09:55:13 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
References: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
In-Reply-To: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 20 May 2013 16:55:19 +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, 20 May 2013 16:55:20 -0000

On 5/20/13 8:56 AM, John C Klensin wrote:
> --On Monday, May 20, 2013 07:53 -0700 joel jaeggli
> <joelja@bogus.com> wrote:
>
>> ...
>>> This is not my primary (or even secondary) area of expertise
>>> but, given that the RR space is not unlimited even though it
>>> is large, wouldn't it be better to have a single RRtype for
>>> IEEE-based EUIs with a flag or other indicator in the DATA
>>> field as to whether a 48 bit or 64 bit identifier was present?
>> the basis for assignment of rr-types is expert review. Whether
>> the draft advances or not the rr-types have been assigned.
>>
>> http://tools.ietf.org/html/rfc6895#section-3.1.1
>>
>> http://www.iana.org/assignments/dns-parameters/dns-parameters.
>> xml#dns-parameters-3
> Joel,
>
> I don't know who the current expert is and, for the moment, am
> glad I don't and don't intend to check.  I believe there is
> broad consensus in the community that having something as
> significant as an RRTYPE documented in the RFC Series is a good
> idea.
IETF consensus tends to indicate that is is better to assign new 
RR-types then it is to keep having developers jam these usages into text 
RRs.
>   Certainly leaving the reference pointing, long-term, to
> an I-D would not be a good idea (and would violate several other
> principles).
an ISE submission for documentary purposes would minimal impediment and 
documentary value would be preserved an rr-type assignement might well 
point at an external resource.
> However, if
>
> (i) the expert review consists largely of making sure
> 	that the template contains the right information and the
> 	ducks are not obviously out of line rather than a
> 	design/architectural review with at least meaningful
> 	potential for community review of the request, and
> 	
> (ii) the response to a design/architectural concern
> 	raised during IETF LC is essentially "too late, code
> 	points already allocated", and
> 	
IETF LC should be, "can we live with this?" The document has been 
discussed in dnsext and reviews were requested, I was prevailed on to 
take it on as that WG is supposed to be shutting down.
> (iii) "Proposed Standard" still does not imply
> 	"recommended" and the alternative to approving the I-D
> 	for that category is non-publication,
> 	
> then I would like to understand, as a procedural matter, what
> the IETF Last Call is about.  Certainly it is not for editorial
> review; that is the RFC Editor's job and there are, IMO, no
> glaring editorial problems.  If the RRTYPEs have been allocated
> and can't be un-allocated and this is in use, then there is
> nothing to propose as an individual submission for
> standardization: an informational document to inform the
> community about what this is about would be both appropriate and
> sufficient.
>
> Beyond that, your shepherd's report implies that the issue I
> raised may have been discussed and successfully resolved in
> DNSEXT.   If that is the case, an explanation in the document
> about the tradeoffs and decision would still be appropriate.
>
> Alternatively and especially if there wasn't clear consensus in
> DNSEXT, if this really is to be processed as a Proposed
> Standard, then a suggestion during IETF Last Call that the IETF
> Standard way to represent EUIs in the DNS should be a single
> RRTYPE with length/type information in the DATA is still in
> order: the community could reasonably conclude that the single
> RRTYPE is a better solution, that the single type should be
> allocated, and that these two types should be deprecated.   We
> have certainly done similar things before with other protocols
> and parameters that were already in use before standardization
> was proposed from an individual submission.
So, I don't have a  problem philosophically or otherwise with the fact 
that there my be a better solution out there. It takes somebody to do 
that work. The can obviously get an rr-type for that application.

In the use cases associated with provisioning systems I would expect 
that knowledge of media type would drive usage of one rr type or another 
e.g. if you're provisioning 6lowpan/zigbee/802.15.4 devices you probably 
don't have to query for eui48.

     john

p.s. I've tried reading your shepherd writeup now in three
different browsers.  It appears to be formatted for extremely
long (paragraph-length) lines, with no provision for automatic
wrapping to fit the page frame.

I can fix that by editing the text. a tool fix for that is forthcoming iirc.
>    That means that trying to read
> and understand it requires extensive horizontal scrolling, which
> is a fairly large impediment and, although I assume
> unintentionally, a way to discourage anyone but the most
> determined of readers from actually reading it.  May I suggest
> that the IESG, on a priority basis, either get the format of
> those writeup pages changed so that they wrap appropriately or
> that it insist that writeups conform to RFC/I-D norms for line
> lengths.
>
>


From sm@resistor.net  Mon May 20 10:51:28 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D1B621F9540 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 10:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.434
X-Spam-Level: 
X-Spam-Status: No, score=-102.434 tagged_above=-999 required=5 tests=[AWL=0.165, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JacDggMk+KQl for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 10:51:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E6721F93E5 for <ietf@ietf.org>; Mon, 20 May 2013 10:51:22 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4KHpCiW007385; Mon, 20 May 2013 10:51:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369072281; bh=jQ0zS8bpozRSxTgV7eD+x5r4FVNUv2o90116/8+YT6I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SBMHbHJYsYXlvY4lrs2WrvnFf7uMgtLoTkvjJDLKRj0WPZoDFX/+XHD6r/jPQXTDD K8AAVI5ik7KD7FS6p45tVGAE0RnbyAA7Ow4aP4UpHvcTxeHvFU5SlsjbqvheH6Lti0 FNNfXThUd++lCMRlJrKnV0XaGgFd+mL0QLFnTDAw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369072281; i=@resistor.net; bh=jQ0zS8bpozRSxTgV7eD+x5r4FVNUv2o90116/8+YT6I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=T/slk8mG1U9i2HQR3lZXU1cCyU8tEW6bls2FhivQPA2brd1sEGutVI3gY/Awujj2E SPY8gyIBsrYSFqKJItF4D3DA3hRtBEEwGciWSUEk8bLerqdnl36tad6HYc4RXn6CGL HaPOwsSeyd31Iv2u7vEfGQ4UCHAdgKMRIbODLH64=
Message-Id: <6.2.5.6.2.20130520081827.0c1add00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 20 May 2013 09:48:33 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-Reply-To: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Joe Abley <jabley@teksavvy.ca>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 17:51:28 -0000

At 06:44 20-05-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>   <draft-jabley-dnsext-eui48-eui64-rrtypes-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-06-17. Exceptionally, comments may be

This draft is about putting MAC addresses in the DNS.  The purpose is 
for IP address tracking by vendors.  As the RRTYPE has already been 
allocated it is useful to document the format.  In my humble opinion 
it is not a good idea to put MAC address in the DNS.  There is some 
text in Section 9 about why it may not be a good idea.  In Section 9:

   "These potential concerns can be mitigated through restricting access
    to zones containing EUI48 or EUI64 RRs or storing such information
    under a domain name whose construction requires that the querier
    already know some other permanent identifier."

The "querier already know some other permanent identifier" reminds me 
of security through obscurity.  I'll do some selective quoting from 
another document:

   "Once the MAC-derived suffix mechanism was standardized, it
    was perceived to be required and therefore became part of compliance
    suites, which continue to compel implementations to support it many
    years after the associated vulnerabilities have been identified."

   "A comprehensive privacy threat model was never developed (which seems
    to be a recurring theme with older protocol development efforts)"

The write-up mentions: "The intended status is standards track with 
the label of propsed standard".  Why is the intended status "Proposed 
Standard"?

As a comment to Joe, the first line in Appendix A.2 was entertaining. :-)

Regards,
-sm 


From d3e3e3@gmail.com  Mon May 20 12:11:18 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB0F421F9677 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 12:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8REO68-qYKO for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 12:11:18 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 16DAC21F9687 for <ietf@ietf.org>; Mon, 20 May 2013 12:11:11 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id un3so7480597obb.33 for <ietf@ietf.org>; Mon, 20 May 2013 12:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=h0KWEDJiJC7VQAGNqHuHyx69W5J4OVNu8M9QxJjz4b8=; b=Li2vzPWGTlb2khsionCMzRCosGWZaaX+Ngf2SSnjOJuwRn39EwKbw8/pRV66tzSnU5 8X4yUDNSymcDfQlM3OBPqTLMnHyalN8diukzpIkgtCJtyKS33qfYQaC7rcRFcz9CY6WJ DtUQ3D6aHGBlASfvYN5K8hKDHbFTxP5zcuAcstfr+f8lKYMwyWTisbl06CBPkxH/htWX Eh7nw0R5vMt6fprXBFr/kgPGqGp8pegz9q6ZHeVKrXZCE7qrtRQcVD5NF/tRXbFeqTsn EHAQBjLZFhrGqSjf25TcTytukGmSsdH/ef1eFjE3L3mVL5SqAlyJx7BicQMgbFXVrrNK sYYA==
X-Received: by 10.182.113.169 with SMTP id iz9mr27377244obb.40.1369077067372;  Mon, 20 May 2013 12:11:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.162.233 with HTTP; Mon, 20 May 2013 12:10:46 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130520081827.0c1add00@resistor.net>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130520081827.0c1add00@resistor.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 20 May 2013 15:10:46 -0400
Message-ID: <CAF4+nEFddQbHix604+Qe2qPADLttegEJMf5XBhHb8snanAhibA@mail.gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Joe Abley <jabley@teksavvy.ca>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 19:11:18 -0000

People were already storing MAC addresses in DNS for the reason given
in the draft and perhaps others, it is just that they were doing so in
a variety of proprietary ways.

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


On Mon, May 20, 2013 at 12:48 PM, SM <sm@resistor.net> wrote:
> At 06:44 20-05-2013, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>>   <draft-jabley-dnsext-eui48-eui64-rrtypes-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-06-17. Exceptionally, comments may be
>
>
> This draft is about putting MAC addresses in the DNS.  The purpose is for IP
> address tracking by vendors.  As the RRTYPE has already been allocated it is
> useful to document the format.  In my humble opinion it is not a good idea
> to put MAC address in the DNS.  There is some text in Section 9 about why it
> may not be a good idea.  In Section 9:
>
>   "These potential concerns can be mitigated through restricting access
>    to zones containing EUI48 or EUI64 RRs or storing such information
>    under a domain name whose construction requires that the querier
>    already know some other permanent identifier."
>
> The "querier already know some other permanent identifier" reminds me of
> security through obscurity.  I'll do some selective quoting from another
> document:
>
>   "Once the MAC-derived suffix mechanism was standardized, it
>    was perceived to be required and therefore became part of compliance
>    suites, which continue to compel implementations to support it many
>    years after the associated vulnerabilities have been identified."
>
>   "A comprehensive privacy threat model was never developed (which seems
>    to be a recurring theme with older protocol development efforts)"
>
> The write-up mentions: "The intended status is standards track with the
> label of propsed standard".  Why is the intended status "Proposed Standard"?
>
> As a comment to Joe, the first line in Appendix A.2 was entertaining. :-)
>
> Regards,
> -sm

From john-ietf@jck.com  Mon May 20 12:18:05 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0B721F96B6 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 12:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UcNuQrh1Pvji for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 12:17:59 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1348221F961B for <ietf@ietf.org>; Mon, 20 May 2013 12:17:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UeVao-00083q-0x; Mon, 20 May 2013 15:17:58 -0400
Date: Mon, 20 May 2013 15:17:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
Message-ID: <2C950B049B1411621F4AB719@JcK-HP8200.jck.com>
In-Reply-To: <519A5571.10708@bogus.com>
References: <DE23D901D6B5A1B2197C9127@JcK-HP8200.jck.com> <519A5571.10708@bogus.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: Mon, 20 May 2013 19:18:05 -0000

--On Monday, May 20, 2013 09:55 -0700 joel jaeggli
<joelja@bogus.com> wrote:

>> I don't know who the current expert is and, for the moment, am
>> glad I don't and don't intend to check.  I believe there is
>> broad consensus in the community that having something as
>> significant as an RRTYPE documented in the RFC Series is a
>> good idea.

> IETF consensus tends to indicate that is is better to assign
> new RR-types then it is to keep having developers jam these
> usages into text RRs.

I certainly agree with that.  If I had my druthers, the IETF
would have loosened up on registrations and issued a strong
statement discouraging the use of text RRs for anything other
than what I believe was their original purpose -- unstructured
textual comments to be read by humans.  So no disagreement
there.    But even in the pre-1999 IANA days and with registries
that were almost purely FCFS, the then-universal expert reviewer
felt it was reasonable to deal with an application for two code
points by saying something equivalent to "hey, can't you use one
and a different data structure?".  It is, IMO, an obvious
question and, other issues aside, I think the answer should be
explained in the document.  How strong "should" is depends on
another consideration; see below.

>>   Certainly leaving the reference pointing, long-term, to
>> an I-D would not be a good idea (and would violate several
>> other principles).

> an ISE submission for documentary purposes would minimal
> impediment and documentary value would be preserved an rr-type
> assignement might well point at an external resource.

Yes.  And?    I didn't say "no external reference", I said "no
permanent reference to an I-D".   Remember that "not an archival
series", "reference only as work in progress", etc., stuff?
Again, see below.

>> However, if
>> 
>> (i) the expert review consists largely of making sure
>> 	that the template contains the right information and the
>> 	ducks are not obviously out of line rather than a
>> 	design/architectural review with at least meaningful
>> 	potential for community review of the request, and
>> 	
>> (ii) the response to a design/architectural concern
>> 	raised during IETF LC is essentially "too late, code
>> 	points already allocated", and

> IETF LC should be, "can we live with this?" The document has
> been discussed in dnsext and reviews were requested, I was
> prevailed on to take it on as that WG is supposed to be
> shutting down.

See below.
 
>> (iii) "Proposed Standard" still does not imply
>> 	"recommended" and the alternative to approving the I-D
>> 	for that category is non-publication,
>...
> So, I don't have a  problem philosophically or otherwise with
> the fact that there my be a better solution out there. It
> takes somebody to do that work. The can obviously get an
> rr-type for that application.
>...
  
Somewhat informed by your note and the other responses to my
original one, let me clarify what I'm suggesting...

(1) As indicated above, I think that an easy application and
registration process is A Good Thing for RRTYPEs (and lots of
other things).  Unless there is some substantial reason to not
do so, I think that such registrations should be bound to
sufficient information to make interoperability easy or at least
feasible.  In the general case, I don't think it makes any
difference where that information is recorded as long as the
document location or maintenance arrangements are sufficiently
stable to create a plausible expectation of long-term
accessibility of the description.  I note that the latter has
been an IANA requirement since before there was an IETF and that
occasional exceptions have been made for almost that long.

(2)  I think publication of descriptions of RRTYPE values (and
other parameters) in the RFC Series is generally A Good Thing
and that it should be encouraged.  If that results in better
quality documentation or documentation that is easier to
interpret in ways that increase interoperability, that is great.

(3) However, if someone wants both a code point (in this case,
RRTYPE) or two and an IETF Standards Track document, they should
expect to conform to IETF norms about standards track
specifications.  I think those norms include the expectation of
a meaningful IETF Last Call that could, e.g., question design
decisions, expect substantive responses, and expect changes if
the consensus leads that way.  The situation with a WG document
being processed inside a WG and with an individual submission
for Standards Track ought to be the same: design decisions
belong to the WG or IETF, not the authors.  A registration
procedure should not be able to be used to create a back door
and preempt that principle, so the would-be registrants can use
the expert process to register whatever they would like but, in
doing so, they should accept that, if they want to publish in
the RFC Series, the result will be Informational.  Or, if they
want whatever value that IETF Standardization adds, they need to
make a proposal to the IETF and let it be reviewed, and possibly
changed, by the process.  If they pick the latter course, it
will usually be preferable to defer registering until the IETF
reaches consensus but, if that is not feasible, they need to be
prepared for the IETF to agree on something else, expect to be
asked to reflect that in their document, register the
agreed-upon solution, and then deprecate the earlier
registrations (possibly leaving their documentation in an
appendix to the Standards Track RFC).  

It seems to me that, if someone can register something, ask for
Standards Track status, and then reject requests to discuss
changes on the basis that the registration has already occurred
and expect the document to be standardized anyway, the standards
process is headed toward fairly difficult territory.

     john

p.s. Thanks to you and Barry for the explanation of the
shepherd/ tracker problem.


From brian.e.carpenter@gmail.com  Mon May 20 13:08:43 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BED8821F961B for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 13:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.826
X-Spam-Level: 
X-Spam-Status: No, score=-102.826 tagged_above=-999 required=5 tests=[AWL=-0.227, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5r68kiA22Xyh for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 13:08:43 -0700 (PDT)
Received: from mail-da0-x229.google.com (mail-da0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2106621F9612 for <ietf@ietf.org>; Mon, 20 May 2013 13:08:43 -0700 (PDT)
Received: by mail-da0-f41.google.com with SMTP id y19so1968842dan.28 for <ietf@ietf.org>; Mon, 20 May 2013 13:08:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SbJRfLsk6aJzsdmVVVYR5JdcAKNjAyJWtZjyNNgMkx8=; b=YZDfg/0+PfPexZwPGPcWaFiC9SSypzOKhbGd4xjFXoLaHlaJzfssC8lwKrExNzLeAF hSnPpkccN8TTtM754efaJYZKqeGSbypjP48ILC76hFyOGrV/qtbVRV5rF1LVKpk8lw9H h6Uha5nEmqOR0YfLtJ9JcDqOHx8RGVq0REb3bUg6vViFIyLdf11o5H+XaNdtF9FTEXDz XaedTjhk55NKwh7yN2DJODst0Bdwvfieyj780n1ULoUjjzhvcH7uYwq5iEBdRpr6e99s CrcTf+flw6ZYG3BjDOr6AYSCZVQhlv/MotMZAGKhyhpmUr0SwD5eNlA7r2+xyriH7i4c xGFA==
X-Received: by 10.68.226.225 with SMTP id rv1mr59239519pbc.55.1369080518601; Mon, 20 May 2013 13:08:38 -0700 (PDT)
Received: from [192.168.1.4] (103.201.252.27.dyn.cust.vf.net.nz. [27.252.201.103]) by mx.google.com with ESMTPSA id uq10sm25362936pbc.5.2013.05.20.13.08.34 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 13:08:37 -0700 (PDT)
Message-ID: <519A82B9.7090305@gmail.com>
Date: Tue, 21 May 2013 08:08:25 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
In-Reply-To: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 20:08:44 -0000

>    Publication of EUI-48 or EUI-64 addresses in the global DNS may
>    result in privacy issues in the form of unique trackable identities.

This might also result in such MAC addresses being spoofed, thereby allowing
some sort of direct attack. So it isn't just a privacy concern.

...
>    These potential concerns can be mitigated through restricting access
>    to zones containing EUI48 or EUI64 RRs or storing such information
>    under a domain name whose construction requires that the querier
>    already know some other permanent identifier.

This "can be" seems too weak. Shouldn't we have a MUST here? Also, I doubt
that the second option (a shared secret) is sufficient.

Regards
   Brian Carpenter

From john-ietf@jck.com  Mon May 20 15:01:39 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3149021F9649 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 15:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OBcCCFq-ZW-Q for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 15:01:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 14F2021F9634 for <ietf@ietf.org>; Mon, 20 May 2013 15:01:32 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UeY96-0008Eb-81; Mon, 20 May 2013 18:01:32 -0400
Date: Mon, 20 May 2013 18:01:24 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
Message-ID: <1869EF1209DCB17ACA6041BC@JcK-HP8200.jck.com>
In-Reply-To: <519A82B9.7090305@gmail.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@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: Mon, 20 May 2013 22:01:39 -0000

--On Tuesday, May 21, 2013 08:08 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>>    These potential concerns can be mitigated through
>>    restricting access to zones containing EUI48 or EUI64 RRs
>>    or storing such information under a domain name whose
>>    construction requires that the querier already know some
>>    other permanent identifier.
> 
> This "can be" seems too weak. Shouldn't we have a MUST here?
> Also, I doubt that the second option (a shared secret) is
> sufficient.

I'd guess that, in the actual use cases, a MUST would be ignored
and am consequently would be reasonably happy with the existing
text even if it said less, thereby reducing the sensation of
hand waving.

A shared secret or other mechanism for obscuring a name might be
sufficient if the privacy requirement was to prevent casual data
mining and resulting attacks.  What is, or is not, sufficient
really depends on the risk analysis and assessment of how
serious a failure might be, an analysis that is missing from the
document.  That said, if serious protection were needed,
wouldn't it make sense to incorporate some provision for data
encryption in the RRTYPE itself rather than trying to use an
obscured domain name?  I wouldn't really propose that.  Instead,
I think the bottom line is closer to "if some data really need
to be secure and private, the public DNS is probably not the
right place to put them".

Comparing this to my earlier comments, I think an IETF Proposed
Standard really needs to discuss and resolve these issues and
that Brian's question is important in that context.  If hand
waving is appropriate, it should say why.  If an obscured
identifier is sufficient, it should explain why that is the case
or the circumstances under which it is the case.    The same
problems could be solved with an Informational document by
clearly describing the RRTYPE and then, if this sort of
information is needed at all, making it clear that it represents
the authors' opinion and how they expect their RRTYPE to be used
rather than, e.g., IETF consensus.

   john


From sra@hactrn.net  Mon May 20 16:49:14 2013
Return-Path: <sra@hactrn.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 D57DD21F9674 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 16:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RysixPsUxAij for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 16:49:14 -0700 (PDT)
Received: from cyteen.hactrn.net (cyteen.hactrn.net [IPv6:2002:425c:4242:0:210:5aff:fe86:1f54]) by ietfa.amsl.com (Postfix) with ESMTP id 2F74E21F964C for <ietf@ietf.org>; Mon, 20 May 2013 16:49:14 -0700 (PDT)
Received: from thrintun.hactrn.net (thrintun.hactrn.net [10.0.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thrintun.hactrn.net", Issuer "Grunchweather Associates" (verified OK)) by cyteen.hactrn.net (Postfix) with ESMTPS id AC5679B428; Mon, 20 May 2013 23:49:11 +0000 (UTC)
Received: from thrintun.hactrn.net (localhost [IPv6:::1]) by thrintun.hactrn.net (Postfix) with ESMTP id 80F07170F3; Mon, 20 May 2013 19:49:11 -0400 (EDT)
Date: Mon, 20 May 2013 19:49:11 -0400
From: Rob Austein <sra@hactrn.net>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
In-Reply-To: <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/23.4 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20130520234911.80F07170F3@thrintun.hactrn.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, 20 May 2013 23:49:15 -0000

At Mon, 20 May 2013 10:18:21 -0400, John C. Klensin wrote:
> 
> This is not my primary (or even secondary) area of expertise
> but, given that the RR space is not unlimited even though it is
> large, wouldn't it be better to have a single RRtype for
> IEEE-based EUIs with a flag or other indicator in the DATA field
> as to whether a 48 bit or 64 bit identifier was present?

Short answer: Probably not, but it depends on the application.

Longer answer: See RFC 5507.

From sm@resistor.net  Mon May 20 16:53:20 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEDE521F96C5 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 16:53:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.475
X-Spam-Level: 
X-Spam-Status: No, score=-102.475 tagged_above=-999 required=5 tests=[AWL=0.124, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1L+O423EfODG for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 16:53:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7580321F90DF for <ietf@ietf.org>; Mon, 20 May 2013 16:53:17 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4KNr69p003756; Mon, 20 May 2013 16:53:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369093992; bh=9j/ZohQjYrIOcC5JbKGteCkY3WEoBgcFIdHmTClJfYM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=O6qumKjLlYN3p6I6SP7cz176ZjRHYgw1jdD9Jj9zmt+B92PQmFtm5t6dJRHsAVwf2 w6Pd5oTG8RJ25Et5n4J+Ky9PVe4reX09xapEOlfGDlP+Hey4/b8r6DYKJ+3KdLdO5e 3UMSSNggOVPDMEszOYxfAmVBN52p3XEYkqwzuZu0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369093992; i=@resistor.net; bh=9j/ZohQjYrIOcC5JbKGteCkY3WEoBgcFIdHmTClJfYM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=A4Xd9SkRlKJi5eYgo2h484CqFXfHTTnHF195wSincUqTWzf1oOjt/PyfhPVS5I+E3 zUdazVLQWXQIVIEXyfYjXUjEjcHNzZiwsyndHjQgUnzuYnMb1ynZbWEa9kl95jI7Mc hS54SuvgQtdRnJdhD0L5Ch7V9gJgG/2DKnt1MglY=
Message-Id: <6.2.5.6.2.20130520144607.0c9c7ae8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 20 May 2013 16:41:25 -0700
To: Donald Eastlake <d3e3e3@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-Reply-To: <CAF4+nEFddQbHix604+Qe2qPADLttegEJMf5XBhHb8snanAhibA@mail.g mail.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130520081827.0c1add00@resistor.net> <CAF4+nEFddQbHix604+Qe2qPADLttegEJMf5XBhHb8snanAhibA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Joe Abley <jabley@teksavvy.ca>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 May 2013 23:53:20 -0000

Hi Donald,
At 12:10 20-05-2013, Donald Eastlake wrote:
>People were already storing MAC addresses in DNS for the reason given
>in the draft and perhaps others, it is just that they were doing so in
>a variety of proprietary ways.

Thanks for the explanation.  I'll make a general comment.

 From what I understand the use case is about Canadian ISPs using 
AXFR to (privately) transfer information about IP addresses, EUI-48 
and EUI-64 addresses.  A MAC address is usually tied to a device 
[1][2].  I understand the interoperability argument.  That is 
addressed by the code point allocation.

I personally do not think that it is a good idea to encourage [3] 
storing MAC addresses in the (public) DNS even though people might 
already be doing that.  It has become difficult to reconcile what a 
proposed standard is about.  I prefer that it does not "mean just 
what I choose it to mean - neither more nor less".

Regards,
-sm

1. 
http://www.canlii.org/eliisa/highlight.do?language=en&searchTitle=British+Columbia&path=/en/bc/bcca/doc/2005/2005bcca334/2005bcca334.html
2. http://www.priv.gc.ca/media/sp-d/2011/sp-d_20110125_pk_e.asp
3. I could not find an appropriate word. 


From marka@isc.org  Mon May 20 17:26:56 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB3B021F9721; Mon, 20 May 2013 17:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id urWdbuQ-6aVA; Mon, 20 May 2013 17:26:56 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id E8E2321F9711; Mon, 20 May 2013 17:26:55 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 2769B5F988D; Tue, 21 May 2013 00:26:44 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369096014; bh=ipgKYB0ZydR4pbbsaDqUoI1lYOkyyAhSy5gq4LiKT+M=; h=To:Cc:From:Subject:Date; b=AneAyMgJR0XRuouYyfD5j5Q+/CG4FeE7WkR3u6STMcXtnf4jskXDAwjgw7ttUx/nF kgYJcrfu95cu8MA25jVQ/kWpZXxPuSSj1eHcOW0KeUshy/E0hwnCLbzCiGVCqN85xI PTEA78RU9vwTVZtgU81VxkCPrH5qvhLqvqweGR9o=
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id D9AF5216C40; Tue, 21 May 2013 00:26:42 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id E75D9348D265; Tue, 21 May 2013 10:26:39 +1000 (EST)
To: iesg@ietf.org
From: Mark Andrews <marka@isc.org>
Subject: Deployment of standards compliant nameservers
Date: Tue, 21 May 2013 10:26:39 +1000
Message-Id: <20130521002639.E75D9348D265@drugs.dv.isc.org>
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, 21 May 2013 00:26:56 -0000

	I call upon the IESG to discuss with IANA, the RIRs, ICANN
and TLD operators how to deal with the problems caused by the
deployment of non standards compliant nameservers.

	For a long time there have been operational problems
cause by the deployment of non standards compliant nameservers that
fail to respond to DNS queries directed at them or respond incorrectly.

	The biggest problem with respect to deployment of new
types is nameservers that fail to respond to types they don't
understand.  RFC 1034 allows for several different responses:

* name error
* no error no data
* not implemented
* refused
* formerr

"Name error" and "no error no data" are the expected responses for
queries with unknown types.  This is reinforced by RFC 3597.  But
any of the other responses is acceptable.  Failure to respond however
is not acceptable.  It introduces systematic timeouts which are
indistinguishable from network errors without extended analysis of
query response behaviour.

While the percentage of nameservers misbehaving like this are
relatively small they have a disproportionate effect on protocol
development.  They are also easily identifiable when looked for by
querying for a know type at a name that is know to exist, the zone
apex, that is supported by virtually all nameservers (e.g. A) and
querying for a random unallocated type, then querying again for the
original type.  If you get a answer, no response, answer then the
nameserver in question almost certainly has this issue and you are
not looking at a dead server or network congestion issue.

I'm not sure what the solution should be but regular audits of
delegated nameservers by infrastructure operator and removal of
delegations after a grace period to correct the faulty nameserver
and checking of nameserver behaviour at registration time would go
a long way to addressing the problem.

Removal of the delegation is one of the suggested remediations
identified in RFC 1034 for nameservers that are causing operational
problems.  It is not the first step by it is a step in the process.

Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org

From bmanning@isi.edu  Mon May 20 17:38:59 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 287BD21F9749; Mon, 20 May 2013 17:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gE1SkGvFIHU; Mon, 20 May 2013 17:38:54 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 145C821F8F12; Mon, 20 May 2013 17:38:53 -0700 (PDT)
Received: from [192.168.0.4] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4L0bnHU001297 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 20 May 2013 17:37:59 -0700 (PDT)
Subject: Re: Deployment of standards compliant nameservers
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20130521002639.E75D9348D265@drugs.dv.isc.org>
Date: Mon, 20 May 2013 17:37:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: Manning Bill <bmanning@isi.edu>, The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 00:38:59 -0000

I believe that there are a couple of problems with this plea=85

1) - The IETF has -never- tested for or assured compliance with their =
document series.
2) - The only DNS test suite I am aware of is the older TAHI test suite =
from http://www.tahi.org/ - which was focused on IPv6 development and is =
now closed.
3) - The full DNS standards fail to include the RFC 2026 language that =
would suggest mandatory capabilities.

So, while a nice idea, it is hardly practical from an IETF (or any =
top-down) perspective=85

/bill



On 20May2013Monday, at 17:26, Mark Andrews wrote:

>=20
> 	I call upon the IESG to discuss with IANA, the RIRs, ICANN
> and TLD operators how to deal with the problems caused by the
> deployment of non standards compliant nameservers.
>=20
> 	For a long time there have been operational problems
> cause by the deployment of non standards compliant nameservers that
> fail to respond to DNS queries directed at them or respond =
incorrectly.
>=20
> 	The biggest problem with respect to deployment of new
> types is nameservers that fail to respond to types they don't
> understand.  RFC 1034 allows for several different responses:
>=20
> * name error
> * no error no data
> * not implemented
> * refused
> * formerr
>=20
> "Name error" and "no error no data" are the expected responses for
> queries with unknown types.  This is reinforced by RFC 3597.  But
> any of the other responses is acceptable.  Failure to respond however
> is not acceptable.  It introduces systematic timeouts which are
> indistinguishable from network errors without extended analysis of
> query response behaviour.
>=20
> While the percentage of nameservers misbehaving like this are
> relatively small they have a disproportionate effect on protocol
> development.  They are also easily identifiable when looked for by
> querying for a know type at a name that is know to exist, the zone
> apex, that is supported by virtually all nameservers (e.g. A) and
> querying for a random unallocated type, then querying again for the
> original type.  If you get a answer, no response, answer then the
> nameserver in question almost certainly has this issue and you are
> not looking at a dead server or network congestion issue.
>=20
> I'm not sure what the solution should be but regular audits of
> delegated nameservers by infrastructure operator and removal of
> delegations after a grace period to correct the faulty nameserver
> and checking of nameserver behaviour at registration time would go
> a long way to addressing the problem.
>=20
> Removal of the delegation is one of the suggested remediations
> identified in RFC 1034 for nameservers that are causing operational
> problems.  It is not the first step by it is a step in the process.
>=20
> Mark
>=20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org


From john-ietf@jck.com  Mon May 20 18:07:05 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C00CF21F9742 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 18:07:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07hogjNMo+4I for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 18:06:59 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C163D21F8F1E for <ietf@ietf.org>; Mon, 20 May 2013 18:06:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ueb2Y-0008Sw-Mj; Mon, 20 May 2013 21:06:58 -0400
Date: Mon, 20 May 2013 21:06:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: Rob Austein <sra@hactrn.net>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
Message-ID: <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
In-Reply-To: <20130520234911.80F07170F3@thrintun.hactrn.net>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com> <20130520234911.80F07170F3@thrintun.hactrn.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 01:07:05 -0000

--On Monday, May 20, 2013 19:49 -0400 Rob Austein
<sra@hactrn.net> wrote:

> At Mon, 20 May 2013 10:18:21 -0400, John C. Klensin wrote:
>> 
>> This is not my primary (or even secondary) area of expertise
>> but, given that the RR space is not unlimited even though it
>> is large, wouldn't it be better to have a single RRtype for
>> IEEE-based EUIs with a flag or other indicator in the DATA
>> field as to whether a 48 bit or 64 bit identifier was present?
> 
> Short answer: Probably not, but it depends on the application.
> 
> Longer answer: See RFC 5507.

Rob,

I've reread 5507 and did so again before writing my second note
today.  I don't see that it helps.

I haven't heard anyone proposing use of TXT (or any existing
RRTYPE) instead, so that is presumably a non-issue.

The discussion in 3.1 clearly applies to relatively complex
schemes like NAPTR, but it is not clear that it has anything to
do with this case.  In particular, if I correctly understand the
IEEE's allocation scheme for longer identifiers (and I may not)
than a given device gets only one -- this is not analogous to a
dual-stack IPv4/IPv6 arrangement -- and an application gets back
whatever it gets back (whether the query is addressed to the
DNS, read off a label on the device and entered manually, or
something else).  If so, then one RRTYPE with the appropriate
identifier in the data is the right answer.   

If not... if, for example, different types of applications will
look for only one type-length of identifier and will either find
it or give up (not try falling back to the other because that
would make no sense), then the use of two RRTYPEs is entirely
reasonable.  But, if that is the case and this is going to be
standards track, I expect to see an explanation in the document.
That explanation could be as simple as a statement to that
effect and an example or two of the types of applications that
would use each identifier and/or a reference to IEEE materials
that describe the circumstances under which one example or the
other is used.

I'm not opposed to having two separate RRTYPEs -- I just want to
see the rationale.  And what passes for use cases in the draft
appears to me to be  completely silent on that issue.

     john


From marka@isc.org  Mon May 20 18:23:31 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8CE21F971A; Mon, 20 May 2013 18:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xKB3aN2a7ly2; Mon, 20 May 2013 18:23:31 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 2848621F960B; Mon, 20 May 2013 18:23:30 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 9C3D5C942D; Tue, 21 May 2013 01:23:21 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369099410; bh=a5l7HmhQ/oelvZlhqX0HUCGgc2Fg5gZSmFUVHuvi4zM=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=fWT3rCzqZTeMpDimUoGKB+44bteO0/eKGj12NzmpoYTgJDFaUOWhtH6jHN2hAH9pc 1o5bV18Bba+nj9RTpDUyiem+ukH6jyONx0M7dLpxt0ZTyQOmMVI/gFveofN/iYEeXl 3vnZ907XCv4W72YX1/hZK+Q7zsS+Cdtuaf+14g9o=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 21 May 2013 01:23:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id E724D216C43; Tue, 21 May 2013 01:23:20 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id DD44F348D8D1; Tue, 21 May 2013 11:23:17 +1000 (EST)
To: manning bill <bmanning@isi.edu>
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Mon, 20 May 2013 17:37:48 -0700." <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>
Date: Tue, 21 May 2013 11:23:17 +1000
Message-Id: <20130521012317.DD44F348D8D1@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 01:23:32 -0000

In message <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>, manning bill writes:
> I believe that there are a couple of problems with this plea.
>
> 1) - The IETF has -never- tested for or assured compliance with their
> document series.

Which has what to do with requesting that a known problem get fixed?
One that is clearly caused by nameservers operating outside the
expected behaviour of nameservers.

> 2) - The only DNS test suite I am aware of is the older TAHI test suite
> from http://www.tahi.org/ - which was focused on IPv6 development and is
> now closed.

Well I didn't ask for a complete compliance test to be run.  I ask for
a specific test for a known problematic issue to be run.

> 3) - The full DNS standards fail to include the RFC 2026 language that
> would suggest mandatory capabilities.

And this has what to do with the issue?  Yes older RFCs don't all
use the formal language of RFC 2026.  That doesn't mean that the
intent was not clear or that one should not address operational
issues that arise.

> So, while a nice idea, it is hardly practical from an IETF (or any
> top-down) perspective.
>
> /bill
>
> On 20May2013Monday, at 17:26, Mark Andrews wrote:
>
> >
> > 	I call upon the IESG to discuss with IANA, the RIRs, ICANN
> > and TLD operators how to deal with the problems caused by the
> > deployment of non standards compliant nameservers.
> >
> > 	For a long time there have been operational problems
> > cause by the deployment of non standards compliant nameservers that
> > fail to respond to DNS queries directed at them or respond incorrectly.
> >
> > 	The biggest problem with respect to deployment of new
> > types is nameservers that fail to respond to types they don't
> > understand.  RFC 1034 allows for several different responses:
> >
> > * name error
> > * no error no data
> > * not implemented
> > * refused
> > * formerr
> >
> > "Name error" and "no error no data" are the expected responses for
> > queries with unknown types.  This is reinforced by RFC 3597.  But
> > any of the other responses is acceptable.  Failure to respond however
> > is not acceptable.  It introduces systematic timeouts which are
> > indistinguishable from network errors without extended analysis of
> > query response behaviour.
> >
> > While the percentage of nameservers misbehaving like this are
> > relatively small they have a disproportionate effect on protocol
> > development.  They are also easily identifiable when looked for by
> > querying for a know type at a name that is know to exist, the zone
> > apex, that is supported by virtually all nameservers (e.g. A) and
> > querying for a random unallocated type, then querying again for the
> > original type.  If you get a answer, no response, answer then the
> > nameserver in question almost certainly has this issue and you are
> > not looking at a dead server or network congestion issue.
> >
> > I'm not sure what the solution should be but regular audits of
> > delegated nameservers by infrastructure operator and removal of
> > delegations after a grace period to correct the faulty nameserver
> > and checking of nameserver behaviour at registration time would go
> > a long way to addressing the problem.
> >
> > Removal of the delegation is one of the suggested remediations
> > identified in RFC 1034 for nameservers that are causing operational
> > problems.  It is not the first step by it is a step in the process.
> >
> > Mark
> >
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE:	+61 2 9871 4742		         INTERNET: marka@isc.org
>

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From paul.hoffman@vpnc.org  Mon May 20 18:41:19 2013
Return-Path: <paul.hoffman@vpnc.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 5C24F21F9726; Mon, 20 May 2013 18:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3HVecEZn6ngF; Mon, 20 May 2013 18:41:18 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECE921F938E; Mon, 20 May 2013 18:41:18 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4L1fHUh056350 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 20 May 2013 18:41:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Deployment of standards compliant nameservers
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20130521012317.DD44F348D8D1@drugs.dv.isc.org>
Date: Mon, 20 May 2013 18:41:16 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu> <20130521012317.DD44F348D8D1@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1503)
Cc: The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 01:41:19 -0000

On May 20, 2013, at 6:23 PM, Mark Andrews <marka@isc.org> wrote:

>=20
> In message <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>, manning =
bill writes:
>> I believe that there are a couple of problems with this plea.
>>=20
>> 1) - The IETF has -never- tested for or assured compliance with their
>> document series.
>=20
> Which has what to do with requesting that a known problem get fixed?

One has to test for compliance in order to determine if the problem =
exists in a particular implementation.

> One that is clearly caused by nameservers operating outside the
> expected behaviour of nameservers.

No offense, but your view of "clearly" and "expected" have sometimes =
been at odds with other folks in the DNS protocol community. Your =
request that the IETF do conformance testing might first be based on =
assurance that the DNS protocol community agrees on those. After that, =
"someone" can probably do testing. And after that, "someone" might be =
able to get people to take action against non-conformant =
implementations.

--Paul Hoffman=

From brian.e.carpenter@gmail.com  Mon May 20 18:42:37 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02AEA21F9734 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 18:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.803
X-Spam-Level: 
X-Spam-Status: No, score=-102.803 tagged_above=-999 required=5 tests=[AWL=-0.204, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saz+2vyCdSvc for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 18:42:31 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 6171E21F9728 for <ietf@ietf.org>; Mon, 20 May 2013 18:42:27 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id u11so88311pdi.8 for <ietf@ietf.org>; Mon, 20 May 2013 18:42:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ujuv07/nzxcVJts3awT1r+2aiib9nXQYvX8nWaeSFdw=; b=WkITO2d7v1Wo+j4fb6YBXp5fN1IX6wV4HuLWtXfdvWAsEXvVbyvNeZvo3mx8P1hTCN eYehLIKXbwkfCUf16fJT1308TBC2Wx6Ay5CS2R+gvvcPAyqwgr7KvZaDCqdVU2gY1RK/ Jv8HVQHczxF8esFTO/s5n+B1qZTUFPFMMceylhR1cYb2Saq/tEuS0bqGl0sFstE8jUOZ bwjgozUjRqd86ZuCJv9ro9T9oVEWpvgyH7lgL2WMRMsKe4Hs9Y5PdFZ54vnse9FAyqKA a3YdtsIN6io0BDbimkgRZBMkR0+UTgG6Pjyvhra1th+x/lXiDGrGEWu5X6aBqajvZ341 IuVA==
X-Received: by 10.68.213.200 with SMTP id nu8mr224872pbc.80.1369100547065; Mon, 20 May 2013 18:42:27 -0700 (PDT)
Received: from [192.168.1.4] (103.201.252.27.dyn.cust.vf.net.nz. [27.252.201.103]) by mx.google.com with ESMTPSA id gh9sm366243pbc.37.2013.05.20.18.42.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 18:42:25 -0700 (PDT)
Message-ID: <519AD100.5040305@gmail.com>
Date: Tue, 21 May 2013 13:42:24 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>	<20130520234911.80F07170F3@thrintun.hactrn.net> <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
In-Reply-To: <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Rob Austein <sra@hactrn.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: Tue, 21 May 2013 01:42:37 -0000

On 21/05/2013 13:06, John C Klensin wrote:
> 
> --On Monday, May 20, 2013 19:49 -0400 Rob Austein
> <sra@hactrn.net> wrote:
> 
>> At Mon, 20 May 2013 10:18:21 -0400, John C. Klensin wrote:
>>> This is not my primary (or even secondary) area of expertise
>>> but, given that the RR space is not unlimited even though it
>>> is large, wouldn't it be better to have a single RRtype for
>>> IEEE-based EUIs with a flag or other indicator in the DATA
>>> field as to whether a 48 bit or 64 bit identifier was present?
>> Short answer: Probably not, but it depends on the application.
>>
>> Longer answer: See RFC 5507.
> 
> Rob,
> 
> I've reread 5507 and did so again before writing my second note
> today.  I don't see that it helps.
> 
> I haven't heard anyone proposing use of TXT (or any existing
> RRTYPE) instead, so that is presumably a non-issue.
> 
> The discussion in 3.1 clearly applies to relatively complex
> schemes like NAPTR, but it is not clear that it has anything to
> do with this case.  In particular, if I correctly understand the
> IEEE's allocation scheme for longer identifiers (and I may not)
> than a given device gets only one -- this is not analogous to a
> dual-stack IPv4/IPv6 arrangement -- and an application gets back
> whatever it gets back (whether the query is addressed to the
> DNS, read off a label on the device and entered manually, or
> something else).  If so, then one RRTYPE with the appropriate
> identifier in the data is the right answer.   
> 
> If not... if, for example, different types of applications will
> look for only one type-length of identifier and will either find
> it or give up (not try falling back to the other because that
> would make no sense), then the use of two RRTYPEs is entirely
> reasonable.  But, if that is the case and this is going to be
> standards track, I expect to see an explanation in the document.
> That explanation could be as simple as a statement to that
> effect and an example or two of the types of applications that
> would use each identifier and/or a reference to IEEE materials
> that describe the circumstances under which one example or the
> other is used.
> 
> I'm not opposed to having two separate RRTYPEs -- I just want to
> see the rationale.  And what passes for use cases in the draft
> appears to me to be  completely silent on that issue.

Especially since there is an IEEE-defined method for representing
a 48-bit address in the 64-bit format. Now you mention it, why can't
that be used in all cases?

    Brian

From moore@network-heretics.com  Mon May 20 18:44:53 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D129921F93F0; Mon, 20 May 2013 18:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.655
X-Spam-Level: 
X-Spam-Status: No, score=-3.655 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eDoCEaKnOS1f; Mon, 20 May 2013 18:44:48 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF4821F913E; Mon, 20 May 2013 18:44:47 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id B753E20804; Mon, 20 May 2013 21:44:42 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 20 May 2013 21:44:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=tKNvUO1nhwdJxieFF8gByX l/VB4=; b=a9uCYl5+6qP73HaR6DGEjkPaHSNmY30hksr4NouCR8TgUbaTHDAmUx 9T38ma0BOkK52NEP8EszN5osqMdo3MpFRL6YzbeSuOrruFtbxpB7IsL1NyUXtwBO idvtxw7dyZiPANVKAzjUeXpPsSIbZFPoXlmP8B/7KjvSE41s3QHic=
X-Sasl-enc: Bjyt8krdJjXOwAJal7exhRupxCyd+wJf3Kr6Al/nKDTa 1369100681
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 94EBEC8000D; Mon, 20 May 2013 21:44:41 -0400 (EDT)
Message-ID: <519AD17D.8040501@network-heretics.com>
Date: Mon, 20 May 2013 21:44:29 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: Deployment of standards compliant nameservers
References: <20130521002639.E75D9348D265@drugs.dv.isc.org>
In-Reply-To: <20130521002639.E75D9348D265@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 01:44:54 -0000

It seems like a first step might be to set up a web page and/or write up 
an I-D with

a) a description of the problem
b) documentation a procedure and/or code that can be used to test name 
server software for compliance
c) recommendations for zone operators that delegate to other zones

The next step might be for TLD operators to encourage the TLD registrars 
to (a) inform their customers of this issue, (b) test their customers' 
servers, and report the test results to their customers.   Ideally those 
registrars would be able to refer their customers to updated or improved 
servers.

Longer term it might be appropriate to do some other things, like
a) define standard tests for compliance
b) define a mechanism by which a server could be queried to find out its 
implementation name, version, etc.

Keith

p.s. I wonder if the problem you describe might at least partially be 
caused by DNS proxies and interception proxies, including but not 
limited to those incorporated in consumer-grade routers.

On 05/20/2013 08:26 PM, Mark Andrews wrote:
> 	I call upon the IESG to discuss with IANA, the RIRs, ICANN
> and TLD operators how to deal with the problems caused by the
> deployment of non standards compliant nameservers.
>
> 	For a long time there have been operational problems
> cause by the deployment of non standards compliant nameservers that
> fail to respond to DNS queries directed at them or respond incorrectly.
>
> 	The biggest problem with respect to deployment of new
> types is nameservers that fail to respond to types they don't
> understand.  RFC 1034 allows for several different responses:
>
> * name error
> * no error no data
> * not implemented
> * refused
> * formerr
>
> "Name error" and "no error no data" are the expected responses for
> queries with unknown types.  This is reinforced by RFC 3597.  But
> any of the other responses is acceptable.  Failure to respond however
> is not acceptable.  It introduces systematic timeouts which are
> indistinguishable from network errors without extended analysis of
> query response behaviour.
>
> While the percentage of nameservers misbehaving like this are
> relatively small they have a disproportionate effect on protocol
> development.  They are also easily identifiable when looked for by
> querying for a know type at a name that is know to exist, the zone
> apex, that is supported by virtually all nameservers (e.g. A) and
> querying for a random unallocated type, then querying again for the
> original type.  If you get a answer, no response, answer then the
> nameserver in question almost certainly has this issue and you are
> not looking at a dead server or network congestion issue.
>
> I'm not sure what the solution should be but regular audits of
> delegated nameservers by infrastructure operator and removal of
> delegations after a grace period to correct the faulty nameserver
> and checking of nameserver behaviour at registration time would go
> a long way to addressing the problem.
>
> Removal of the delegation is one of the suggested remediations
> identified in RFC 1034 for nameservers that are causing operational
> problems.  It is not the first step by it is a step in the process.
>
> Mark
>


From d3e3e3@gmail.com  Mon May 20 18:54:16 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1684E21F9704 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 18:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.329
X-Spam-Level: 
X-Spam-Status: No, score=-103.329 tagged_above=-999 required=5 tests=[AWL=0.270, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id edXSiH+kcjlO for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 18:54:11 -0700 (PDT)
Received: from mail-oa0-f47.google.com (mail-oa0-f47.google.com [209.85.219.47]) by ietfa.amsl.com (Postfix) with ESMTP id DDE9321F9746 for <ietf@ietf.org>; Mon, 20 May 2013 18:54:10 -0700 (PDT)
Received: by mail-oa0-f47.google.com with SMTP id m1so123436oag.6 for <ietf@ietf.org>; Mon, 20 May 2013 18:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=d8urSg/ARBhUuem7eedXag4JhsRdlUHJ9jg04BdiNWg=; b=VnCL4Ia83LgZ58LOJ3zuoGqIWUrGL0k8KBwWj5qp0hs9nV6mV0lWTYNpaOFSSCSiaX Y6hgX/AamJGqfUr7YLfdHFSkM+WGM/e9zLcd/21s6IAPx+cUfnjbbg9LynqA0/3/vlJa wpnNxvn53/HYSvA+3L9pSY2ZtwWR/QosSvCuLjiQD3BNmBhdfE9/Bg9HDlDjsYNiH3Rr fBmOwiEEwmfAyUgqmwRkR4OHHE8OVwv1o8z8plfCJKcuWZ4uX7H2NLAV0n5OKqS4wtQx dhtXqnRAWZEVQz0y02FBg0ODdxAnRilwOqIRIcrxS3BcY9qKZcO7KdseP9KC22luRNeV 7MFQ==
X-Received: by 10.182.102.234 with SMTP id fr10mr82290obb.85.1369101250457; Mon, 20 May 2013 18:54:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.162.233 with HTTP; Mon, 20 May 2013 18:53:50 -0700 (PDT)
In-Reply-To: <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com> <20130520234911.80F07170F3@thrintun.hactrn.net> <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 20 May 2013 21:53:50 -0400
Message-ID: <CAF4+nEEb3kSJqW2E_dnhd7epjYSZHKZDkDDePdvJO3UN=66ETQ@mail.gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Rob Austein <sra@hactrn.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: Tue, 21 May 2013 01:54:16 -0000

Hi,

On Mon, May 20, 2013 at 9:06 PM, John C Klensin <john-ietf@jck.com> wrote:
>
>
>>...
>...
> The discussion in 3.1 clearly applies to relatively complex
> schemes like NAPTR, but it is not clear that it has anything to
> do with this case.  In particular, if I correctly understand the
> IEEE's allocation scheme for longer identifiers (and I may not)
> than a given device gets only one -- this is not analogous to a
> dual-stack IPv4/IPv6 arrangement -- and an application gets back
> whatever it gets back (whether the query is addressed to the
> DNS, read off a label on the device and entered manually, or
> something else).  If so, then one RRTYPE with the appropriate
> identifier in the data is the right answer.

If you are getting an address to connect with a device on an Ethernet
link, you just have to know what the right address size is. After
whatever start of frame mark there is, it is just DA-SA and using the
wrong size MAC addresses isn't going to work.

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

> If not... if, for example, different types of applications will
> look for only one type-length of identifier and will either find
> it or give up (not try falling back to the other because that
> would make no sense), then the use of two RRTYPEs is entirely
> reasonable.  But, if that is the case and this is going to be
> standards track, I expect to see an explanation in the document.
> That explanation could be as simple as a statement to that
> effect and an example or two of the types of applications that
> would use each identifier and/or a reference to IEEE materials
> that describe the circumstances under which one example or the
> other is used.
>
> I'm not opposed to having two separate RRTYPEs -- I just want to
> see the rationale.  And what passes for use cases in the draft
> appears to me to be  completely silent on that issue.
>
>      john
>

From marka@isc.org  Mon May 20 19:20:19 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C62C21F9788; Mon, 20 May 2013 19:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJwKCIyXrwr1; Mon, 20 May 2013 19:20:18 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 735AD21F9761; Mon, 20 May 2013 19:20:18 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 52D76C9478; Tue, 21 May 2013 02:20:09 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369102816; bh=bKEK5YE6y3NJRhjufzqmxTAI1Rao+qoriSJnhZOQGuo=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=qvq/e2h2vKnzu/AxmR59tI5fLWfqJTbrz1BeLdr4TG+3NzzPUeLbpgKKriWKFUsJe pqGsVouNFTbHgECVdS+BgBMjn+Vqej27QOpfWyEiZFXQ+ikKHQ9FspjYtmlK8c9tX3 cw9wrJFr8xXpTSTRROzazA0YUsp0YuHdSMc2UReI=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 21 May 2013 02:20:09 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A25E4216C43; Tue, 21 May 2013 02:20:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 6594C348DB16; Tue, 21 May 2013 12:20:05 +1000 (EST)
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu> <20130521012317.DD44F348D8D1@drugs.dv.isc.org> <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Mon, 20 May 2013 18:41:16 -0700." <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org>
Date: Tue, 21 May 2013 12:20:05 +1000
Message-Id: <20130521022005.6594C348DB16@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 02:20:19 -0000

In message <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org>, Paul Hoffman writes:
> On May 20, 2013, at 6:23 PM, Mark Andrews <marka@isc.org> wrote:
>
> >
> > In message <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>, manning bill
> writes:
> >> I believe that there are a couple of problems with this plea.
> >>
> >> 1) - The IETF has -never- tested for or assured compliance with their
> >> document series.
> >
> > Which has what to do with requesting that a known problem get fixed?
>
> One has to test for compliance in order to determine if the problem
> exists in a particular implementation.

It doesn't have to be the IETF that does the testing.  In fact the
IETF doesn't have access to the list of servers that need to be
tested however the operators of the parent zones do.  Alternatively
it can be done on a piecemeal basis by examine logs and then looking
up whois entries and complaining that the nameservers are causing
operational problems to the operators,  the complaining to the
parent zone, then complaining to the courts when the parent zone
operators fail to take action as directed by RFC 1034.

> > One that is clearly caused by nameservers operating outside the
> > expected behaviour of nameservers.
>
> No offense, but your view of "clearly" and "expected" have sometimes been
> at odds with other folks in the DNS protocol community. Your request that
> the IETF do conformance testing might first be based on assurance that
> the DNS protocol community agrees on those. After that, "someone" can
> probably do testing. And after that, "someone" might be able to get
> people to take action against non-conformant implementations.

RFC 1034 describes how to answer a query.  It clearly states that new
query types are expected.

"However, the domain system is intentionally extensible.  Researchers are
continuously proposing, implementing and experimenting with new data
types, query types, classes, functions, etc.  Thus while the components
of the official protocol are expected to stay essentially unchanged and
operate as a production service, experimental behavior should always be
expected in extensions beyond the official protocol.  Experimental or
obsolete features are clearly marked in these RFCs, and such information
should be used with caution."

It also states how to constuct a response and it doesn't state
"only known types".

   3. Start matching down, label by label, in the zone.  The
      matching process can terminate several ways:

         a. If the whole of QNAME is matched, we have found the
            node.

            If the data at the node is a CNAME, and QTYPE doesn't
            match CNAME, copy the CNAME RR into the answer section
            of the response, change QNAME to the canonical name in
            the CNAME RR, and go back to step 1.

            Otherwise, copy all RRs which match QTYPE into the
            answer section and go to step 6.

The DNS also has response codes to say that a nameserver doesn't
implement a part if the specification, that it don't want to answer
a particular query, that a internal error occured, that you don't
understand or can parse the query.  These response codes cover just
about any conceivable error condition.  It is a query/response
protocol and a response is expected except under exceptional
circumstances.

Mark

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From bmanning@isi.edu  Mon May 20 19:42:41 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72A2421F95EE; Mon, 20 May 2013 19:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H7x6HJxYygxD; Mon, 20 May 2013 19:42:35 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7A63A21F960B; Mon, 20 May 2013 19:42:35 -0700 (PDT)
Received: from [192.168.0.4] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r4L2foTC021150 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 20 May 2013 19:42:00 -0700 (PDT)
Subject: Re: Deployment of standards compliant nameservers
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20130521022005.6594C348DB16@drugs.dv.isc.org>
Date: Mon, 20 May 2013 19:41:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B852A518-4E41-4785-8603-2168C6E86533@isi.edu>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu> <20130521012317.DD44F348D8D1@drugs.dv.isc.org> <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org> <20130521022005.6594C348DB16@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: IETF discussion list <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 02:42:41 -0000

as mentioned earlier,  only -ONE- known, public DNS conformance test =
suite has existed
and it was shut down last year due to lack of use.

since you want the courts involved, you are making some significant =
presumptions about the
liability of adherence to voluntary standards.

dead issue =85 move on.  Or persuade Yokogawa Electric Corporation to =
spin the test suite back up.

/bill

On 20May2013Monday, at 19:20, Mark Andrews wrote:

>=20
> In message <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org>, Paul =
Hoffman writes:
>> On May 20, 2013, at 6:23 PM, Mark Andrews <marka@isc.org> wrote:
>>=20
>>>=20
>>> In message <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu>, manning =
bill
>> writes:
>>>> I believe that there are a couple of problems with this plea.
>>>>=20
>>>> 1) - The IETF has -never- tested for or assured compliance with =
their
>>>> document series.
>>>=20
>>> Which has what to do with requesting that a known problem get fixed?
>>=20
>> One has to test for compliance in order to determine if the problem
>> exists in a particular implementation.
>=20
> It doesn't have to be the IETF that does the testing.  In fact the
> IETF doesn't have access to the list of servers that need to be
> tested however the operators of the parent zones do.  Alternatively
> it can be done on a piecemeal basis by examine logs and then looking
> up whois entries and complaining that the nameservers are causing
> operational problems to the operators,  the complaining to the
> parent zone, then complaining to the courts when the parent zone
> operators fail to take action as directed by RFC 1034.
>=20
>>> One that is clearly caused by nameservers operating outside the
>>> expected behaviour of nameservers.
>>=20
>> No offense, but your view of "clearly" and "expected" have sometimes =
been
>> at odds with other folks in the DNS protocol community. Your request =
that
>> the IETF do conformance testing might first be based on assurance =
that
>> the DNS protocol community agrees on those. After that, "someone" can
>> probably do testing. And after that, "someone" might be able to get
>> people to take action against non-conformant implementations.
>=20
> RFC 1034 describes how to answer a query.  It clearly states that new
> query types are expected.
>=20
> "However, the domain system is intentionally extensible.  Researchers =
are
> continuously proposing, implementing and experimenting with new data
> types, query types, classes, functions, etc.  Thus while the =
components
> of the official protocol are expected to stay essentially unchanged =
and
> operate as a production service, experimental behavior should always =
be
> expected in extensions beyond the official protocol.  Experimental or
> obsolete features are clearly marked in these RFCs, and such =
information
> should be used with caution."
>=20
> It also states how to constuct a response and it doesn't state
> "only known types".
>=20
>   3. Start matching down, label by label, in the zone.  The
>      matching process can terminate several ways:
>=20
>         a. If the whole of QNAME is matched, we have found the
>            node.
>=20
>            If the data at the node is a CNAME, and QTYPE doesn't
>            match CNAME, copy the CNAME RR into the answer section
>            of the response, change QNAME to the canonical name in
>            the CNAME RR, and go back to step 1.
>=20
>            Otherwise, copy all RRs which match QTYPE into the
>            answer section and go to step 6.
>=20
> The DNS also has response codes to say that a nameserver doesn't
> implement a part if the specification, that it don't want to answer
> a particular query, that a internal error occured, that you don't
> understand or can parse the query.  These response codes cover just
> about any conceivable error condition.  It is a query/response
> protocol and a response is expected except under exceptional
> circumstances.
>=20
> Mark
>=20
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From marka@isc.org  Mon May 20 19:45:16 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2D521F90B1; Mon, 20 May 2013 19:45:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U4oAROGkytFv; Mon, 20 May 2013 19:45:15 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 6963521F8F28; Mon, 20 May 2013 19:45:15 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id AD848C9432; Tue, 21 May 2013 02:45:08 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369104315; bh=qmbvioiQ30PemCfaefcsMsdf6puw7W4bqJQu6YmK+tY=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=GI9C+C+D1vCqqYzHugstHAMwxN7Pe1ZeWCURQ4nNj7B/vTbsNFZ0vTvakQuX5aJeb F6EQtBO7/hLzk0/9U/NqHbVzI2tru3J6JzlwYJKB6E34tjlZSY+L0Kfn/81rXH3kqj I+KWpkq4/nsNYy+pUR8qtsvEN3yxwi1nWFvWLxwU=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 21 May 2013 02:45:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:40a8:9c11:7963:52bc]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 6E95F216C40; Tue, 21 May 2013 02:45:08 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 5F0C0348DCBE; Tue, 21 May 2013 12:45:06 +1000 (EST)
To: Keith Moore <moore@network-heretics.com>
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <519AD17D.8040501@network-heretics.com>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Mon, 20 May 2013 21:44:29 -0400." <519AD17D.8040501@network-heretics.com>
Date: Tue, 21 May 2013 12:45:06 +1000
Message-Id: <20130521024506.5F0C0348DCBE@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 02:45:16 -0000

In message <519AD17D.8040501@network-heretics.com>, Keith Moore writes:
> It seems like a first step might be to set up a web page and/or write up 
> an I-D with
> 
> a) a description of the problem
> b) documentation a procedure and/or code that can be used to test name 
> server software for compliance
> c) recommendations for zone operators that delegate to other zones
> 
> The next step might be for TLD operators to encourage the TLD registrars 
> to (a) inform their customers of this issue, (b) test their customers' 
> servers, and report the test results to their customers.   Ideally those 
> registrars would be able to refer their customers to updated or improved 
> servers.

Ack.
 
> Longer term it might be appropriate to do some other things, like
> a) define standard tests for compliance
> b) define a mechanism by which a server could be queried to find out its 
> implementation name, version, etc.
> 
> Keith
> 
> p.s. I wonder if the problem you describe might at least partially be 
> caused by DNS proxies and interception proxies, including but not 
> limited to those incorporated in consumer-grade routers.

When the problems exist on the nameservers of Fortune 500 companies
nameservers it isn't consumer-grade routers.  It is badly designed
nameservers or their load distributing front ends.

This is similar to the name error issue a nameserver vendor had
when responding to unknown types (e.g. AAAA) in the past.  The BBC's
nameservers were a prime example at the time (now fixed).  They
returned name error for a existing name (www.bbc.co.uk from memory).

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From john-ietf@jck.com  Mon May 20 21:49:00 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D2C21F975B for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 21:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bmrymv4qG-P for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 21:48:55 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EF04921F9769 for <ietf@ietf.org>; Mon, 20 May 2013 21:48:54 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UeeVI-0008fz-8i; Tue, 21 May 2013 00:48:52 -0400
Date: Tue, 21 May 2013 00:48:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
Message-ID: <E62ECED0806C467A681C88D4@JcK-HP8200.jck.com>
In-Reply-To: <519AD100.5040305@gmail.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com> <20130520234911.80F07170F3@thrintun.hactrn.net> <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com> <519AD100.5040305@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: Rob Austein <sra@hactrn.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: Tue, 21 May 2013 04:49:00 -0000

--On Tuesday, May 21, 2013 13:42 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
>> I'm not opposed to having two separate RRTYPEs -- I just want
>> to see the rationale.  And what passes for use cases in the
>> draft appears to me to be  completely silent on that issue.
> 
> Especially since there is an IEEE-defined method for
> representing a 48-bit address in the 64-bit format. Now you
> mention it, why can't that be used in all cases?

I think that just proves the point I was trying to make while
stumbling around in ignorance.  No need at all for two RRTYPEs
or even for an indicator in the data other than IEEE's own
methods.  Or do I misunderstand your comment?

   john


From sra@hactrn.net  Mon May 20 22:04:11 2013
Return-Path: <sra@hactrn.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 5AC7D21F970A for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 22:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nAOSSqF+dU5H for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 22:04:05 -0700 (PDT)
Received: from cyteen.hactrn.net (cyteen.hactrn.net [66.92.66.68]) by ietfa.amsl.com (Postfix) with ESMTP id 288C421F96F9 for <ietf@ietf.org>; Mon, 20 May 2013 22:04:02 -0700 (PDT)
Received: from thrintun.hactrn.net (thrintun.hactrn.net [10.0.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thrintun.hactrn.net", Issuer "Grunchweather Associates" (verified OK)) by cyteen.hactrn.net (Postfix) with ESMTPS id 868FF9B428; Tue, 21 May 2013 05:03:59 +0000 (UTC)
Received: from thrintun.hactrn.net (localhost [IPv6:::1]) by thrintun.hactrn.net (Postfix) with ESMTP id 1BCDC170F3; Tue, 21 May 2013 01:03:59 -0400 (EDT)
Date: Tue, 21 May 2013 01:03:59 -0400
From: Rob Austein <sra@hactrn.net>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
In-Reply-To: <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com> <20130520234911.80F07170F3@thrintun.hactrn.net> <05EC3943E635A1609CE9F018@JcK-HP8200.jck.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/23.4 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20130521050359.1BCDC170F3@thrintun.hactrn.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: Tue, 21 May 2013 05:04:11 -0000

At Mon, 20 May 2013 21:06:53 -0400, John C. Klensin wrote:
> 
> I've reread 5507 and did so again before writing my second note
> today.  I don't see that it helps.

I was mostly referring to the discussion in section 3.1.

> The discussion in 3.1 clearly applies to relatively complex
> schemes like NAPTR, but it is not clear that it has anything to
> do with this case.  In particular, if I correctly understand the
> IEEE's allocation scheme for longer identifiers (and I may not)
> than a given device gets only one -- this is not analogous to a
> dual-stack IPv4/IPv6 arrangement -- and an application gets back
> whatever it gets back (whether the query is addressed to the
> DNS, read off a label on the device and entered manually, or
> something else).  If so, then one RRTYPE with the appropriate
> identifier in the data is the right answer.   
> 
> If not... if, for example, different types of applications will
> look for only one type-length of identifier and will either find
> it or give up (not try falling back to the other because that
> would make no sense), then the use of two RRTYPEs is entirely
> reasonable.

The usual criteria are:

- Does the entire set of records need to be retrieved as an atomic
  unit (eg, to avoid internal consistency problems)?  If so, it should
  be a single RRset, thus a single new type.

- If there's no internal consistency requirement, might an application
  reasonably want to retrieve only one flavor of data (eg, 48-bit EUIs
  in this case)?  If so, multiple RRsets make more sense, thus
  multiple new types.

- Is the total size of an RRset likely to be large if all cases are
  lumped into a single type?  If so, multiple new types might be
  better, because large RRsets are a problem (amplification attacks,
  message truncation, DNSSEC verification failure due to truncation,
  etcetera ad nausium).

If none of the above apply, it's mostly a matter of taste.  My own
bias is against sub-typing, both because we've been burned before by
misguided (albeit well-intentioned) use of sub-typing and also
because, other things being equal, I prefer the simplest RDATA
structure that will get the job done (parsing code for this stuff is
often written in low-level languages which make stupid coding mistakes
all too easy, so, other things being equal, I prefer to reduce the
number of gratuitous opportunities for code exploits).

But if there really is no reason to expect that an application
retrieving EUIs have any sane need to say it only wants the 48-bit
ones or whatever, then a single RR type may be appropriate.  I don't
understand the intended uses well enough to have an informed opinion.

> But, if that is the case and this is going to be standards track, I
> expect to see an explanation in the document.  That explanation
> could be as simple as a statement to that effect and an example or
> two of the types of applications that would use each identifier
> and/or a reference to IEEE materials that describe the circumstances
> under which one example or the other is used.
> 
> I'm not opposed to having two separate RRTYPEs -- I just want to
> see the rationale.  And what passes for use cases in the draft
> appears to me to be  completely silent on that issue.

Fair enough.

From marka@isc.org  Mon May 20 23:03:12 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1817321F9726; Mon, 20 May 2013 23:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.853
X-Spam-Level: 
X-Spam-Status: No, score=-1.853 tagged_above=-999 required=5 tests=[AWL=-0.546, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJKRn985mBND; Mon, 20 May 2013 23:03:11 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 505EA21F9725; Mon, 20 May 2013 23:03:11 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 932BEC9423; Tue, 21 May 2013 06:03:04 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369116191; bh=vsscKGgfI5BNveVkZt5bhSEQ5MGbW2qBb/Gj5Et2fyE=; h=Cc:From:References:Subject:In-reply-to:Date; b=V8Mw1wGPSX42nMo/6kHyq6cOJdsG3M1oiwHWvhxmRjAy/WBVB0rFTqP3YJrpG9/3e iHeljGw4o+FxGJ/DYNTnyo84USs58zLeN5Shn0e7mIfpDoG7yTlbcD6f/PRDjkV0ol 0v05QnKsOZXb96ajpbQ9jOyJ6XNxInN/R4S8Z99k=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Tue, 21 May 2013 06:03:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 4EDF3216C40; Tue, 21 May 2013 06:03:04 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 587E0348E641; Tue, 21 May 2013 16:03:01 +1000 (EST)
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <6A13CEB4-8906-4EC5-9210-571D5474E7FC@isi.edu> <20130521012317.DD44F348D8D1@drugs.dv.isc.org> <7E5B1B3D-8AF1-4FFE-BDA2-47EFB6D35188@vpnc.org> <20130521022005.6594C348DB16@drugs.dv.isc.org>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Tue, 21 May 2013 12:20:05 +1000." <20130521022005.6594C348DB16@drugs.dv.isc.org>
Date: Tue, 21 May 2013 16:03:01 +1000
Message-Id: <20130521060301.587E0348E641@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: The IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 06:03:12 -0000

Keith asked for a ID.

Filename:        draft-andrews-dns-no-response-issue
Revision:        00
Title:           A Common Operational Problem in DNS Servers - Failure To Respond.
Creation date:   2013-05-21
Group:           Individual Submission
Number of pages: 5
URL:             http://www.ietf.org/internet-drafts/draft-andrews-dns-no-response-issue-00.txt
Status:          http://datatracker.ietf.org/doc/draft-andrews-dns-no-response-issue
Htmlized:        http://tools.ietf.org/html/draft-andrews-dns-no-response-issue-00

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From joelja@bogus.com  Mon May 20 23:38:50 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEA0921F9737 for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 23:38:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OEY+gyfDjL0m for <ietf@ietfa.amsl.com>; Mon, 20 May 2013 23:38:50 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1B24621F9735 for <ietf@ietf.org>; Mon, 20 May 2013 23:38:50 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4L6ckmn094287 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 21 May 2013 06:38:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <519B1671.3020802@bogus.com>
Date: Mon, 20 May 2013 23:38:41 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<36C767C6E8C81DBD7D29FA26@JcK-HP8200.jck.com>	<20130520234911.80F07170F3@thrintun.hactrn.net>	<05EC3943E635A1609CE9F018@JcK-HP8200.jck.com> <519AD100.5040305@gmail.com>
In-Reply-To: <519AD100.5040305@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 May 2013 06:38:47 +0000 (UTC)
Cc: Rob Austein <sra@hactrn.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: Tue, 21 May 2013 06:38:50 -0000

On 5/20/13 6:42 PM, Brian E Carpenter wrote:
> On 21/05/2013 13:06, John C Klensin wrote:
>> --On Monday, May 20, 2013 19:49 -0400 Rob Austein
>> <sra@hactrn.net> wrote:
>>
>>> At Mon, 20 May 2013 10:18:21 -0400, John C. Klensin wrote:
>>>> This is not my primary (or even secondary) area of expertise
>>>> but, given that the RR space is not unlimited even though it
>>>> is large, wouldn't it be better to have a single RRtype for
>>>> IEEE-based EUIs with a flag or other indicator in the DATA
>>>> field as to whether a 48 bit or 64 bit identifier was present?
>>> Short answer: Probably not, but it depends on the application.
>>>
>>> Longer answer: See RFC 5507.
>> Rob,
>>
>> I've reread 5507 and did so again before writing my second note
>> today.  I don't see that it helps.
>>
>> I haven't heard anyone proposing use of TXT (or any existing
>> RRTYPE) instead, so that is presumably a non-issue.
>>
>> The discussion in 3.1 clearly applies to relatively complex
>> schemes like NAPTR, but it is not clear that it has anything to
>> do with this case.  In particular, if I correctly understand the
>> IEEE's allocation scheme for longer identifiers (and I may not)
>> than a given device gets only one -- this is not analogous to a
>> dual-stack IPv4/IPv6 arrangement -- and an application gets back
>> whatever it gets back (whether the query is addressed to the
>> DNS, read off a label on the device and entered manually, or
>> something else).  If so, then one RRTYPE with the appropriate
>> identifier in the data is the right answer.
>>
>> If not... if, for example, different types of applications will
>> look for only one type-length of identifier and will either find
>> it or give up (not try falling back to the other because that
>> would make no sense), then the use of two RRTYPEs is entirely
>> reasonable.  But, if that is the case and this is going to be
>> standards track, I expect to see an explanation in the document.
>> That explanation could be as simple as a statement to that
>> effect and an example or two of the types of applications that
>> would use each identifier and/or a reference to IEEE materials
>> that describe the circumstances under which one example or the
>> other is used.
>>
>> I'm not opposed to having two separate RRTYPEs -- I just want to
>> see the rationale.  And what passes for use cases in the draft
>> appears to me to be  completely silent on that issue.
> Especially since there is an IEEE-defined method for representing
> a 48-bit address in the 64-bit format. Now you mention it, why can't
> that be used in all cases?
two observations

If you have an iab range the eui label would get inserted in the middle 
of the IAB base value iirc. that sounds sort of appauling to read/decode.

Second it's not just a representation it's an encapsulation (you could 
if you so choose use a mac-48 on an eui-64 supporting link layer 
legitimately using the encapsulation).  I'm sure some ugly bridge device 
that I want nothing to do with will do that some time in the future, it 
does therefore seem slightly desirable to render them as they are rather 
than in some canonical form that is both.
>      Brian
>


From Steve@shinkuro.com  Tue May 21 01:43:11 2013
Return-Path: <Steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37A921F97A8 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 01:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DSL=1.129, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2X42vhky70ak for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 01:43:06 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 92A7E21F90BB for <ietf@ietf.org>; Tue, 21 May 2013 01:43:02 -0700 (PDT)
Received: from dummy.name; Tue, 21 May 2013 08:42:58 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
From: Steve Crocker <Steve@shinkuro.com>
In-Reply-To: <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org>
Date: Tue, 21 May 2013 09:42:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org>
To: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 08:43:11 -0000

Dan and John,

Thanks for the exchange last week.  As chair of ICANN's Board of =
Directors and an active participant in ICANN's current effort to take a =
fresh look at the Whois architecture and operation, your notes catch my =
attention in multiple ways.  But first, for the benefit of under forty =
crowd, let me briefly introduce myself.  In the late 1960s I chaired the =
ARPANET's Network Working Group, which eventually morphed into today's =
IETF.  I created the RFC series and I was one of the architects of the =
three facets of openness that are the foundation of the Internet =
protocol process, viz open architecture, open participation and open =
publication.  In the late 1980s and early 1990s I served as the first =
area director for security and later on the IAB.  I also co-chaired the =
POSIED Working Group that revised the standardization process, moving =
the authority from the IAB to the IESG, and in the mid 2000s I served on =
the ISOC board and participated in the formation and initial operation =
of the IETF Administrative Support Activity (IASA) and I served on its =
IAOC.  For the past 11 years I've been active in ICANN, serving for =
several years as the chair of the Security and Stability Advisory =
Committee and also on the board of ICANN, and about two years ago I was =
elected chair of the ICANN board.  And despite having spent a great deal =
of time in management and political roles in this environment, I remain =
fundamentally a technical person.

I want to share two thoughts, one about the role of the IETF, ICANN and =
other organizations within the Internet ecosystem, and one about Whois.

The great strength of the IETF is it's a forum for technical people to =
come together, work out the details of protocols, and publish consensus =
documents.  The IETF does not have any formal powers granted by legal =
authorities.  IETF standards are effective because they're accepted and =
they work, not because they're imposed on anyone.  IETF standards are =
respected around the world because they embody the wisdom and experience =
of the technical community.  No one is obliged to use the protocols =
created within the IETF, but, of course, a huge portion of the world =
does use these protocols.

ICANN was created in 1998 to operate the IANA function and to expand and =
organize the marketplace in domain names.  The IANA function is =
fundamentally a clerical service.  It records the assignment of unique =
identifiers that are used throughout the Internet, and it does so in =
accordance with the values and policies established by the community.  =
The IANA service includes publication of the IETF's protocol parameters, =
allocation of blocks of AS numbers, IPv6 address blocks, and, until =
recently, IPv4 blocks to RIRs, and administration of the top level of =
the domain name hierarchy.

Like the IETF, ICANN is also an open organization.  ICANN meetings are =
free, and a veritable ocean of documents are published regularly, many =
in multiple languages to increase availability.

ICANN is purposefully organized to include participation from a range of =
communities, e.g. business, civil society, governments, and the =
technical community.  As I write this, I am at a retreat for the ICANN =
Board focusing on strategic planning.  One of the seats on the Board is =
allocated to a liaison from the IETF, and thus I am actually sitting at =
the time I drafted this note in between Thomas Narten and Jonne =
Soininen, the outgoing and incoming IETF liaisons to the ICANN Board.

One of the large and often time-consuming activities within ICANN is the =
development of policies that pertain to the domain name system.  John =
Curran wrote:

> To be abundantly clear, you are hypothesizing a difference of opinion =
between the=20
> IETF/IESG and the ICANN/RIR communities, wherein the technical =
guidance of the IETF=20
> was considered during the ICANN/RIR decision process, but in the end =
the outcome was=20
> contrary to IETF expectations.
>=20
> This would be an unfortunate (but not impossible) situation, as many =
folks in the=20
> combined community would likely have been involved during the process =
trying to=20
> figure out why there is such a significant difference in views and =
facilitating
> sharing of the beliefs and thought processes that underlie the =
situation.

I agree completely with John.  It is indeed possible for ICANN to adopt =
policies that are not perfectly aligned with IETF recommendations.  =
Possible, but not usual.  Over here at ICANN we pay a LOT of attention =
to the IETF.  We depend heavily on the IETF's work and we never seek to =
duplicate or ignore it.  (I sometimes have to explain to my colleagues =
at ICANN who have not had the benefit of the IETF experience that "let's =
send it over to the IETF" doesn't work.  The IETF isn't a standing army =
ready to do ours or anyone else's work.  Rather, I say, it's a place =
where the relevant people can get together to get their work done.  And, =
indeed, a number of ICANN people actively participate in various IETF =
working groups.)

The roster of topics active within ICANN at any given time is fully =
documented and publicized, and I invite anyone who is interested to =
participate.  We listen to everyone, and we publish tentative results, =
tentative policies, etc. for everyone to critique.

Let me now turn to Whois.  The Whois system's origins go back to the =
earliest days of the Arpanet.  The roles of technical point of contact =
and administrative point of contact were usually the system =
administrator and his administrative manager for the time-sharing system =
at the laboratory at that site.  Each time-sharing system served =
somewhere between a few dozen and a few hundred users.  The users were =
not listed, just the administrators for the system.  There weren't =
really any issues of accuracy, privacy or accountability.  Today, of =
course, these terms apply to the registrants and supporting personnel =
for *each* domain name, and there are well over 100,000,000 domain names =
registered just within the generic top level domains.  The country code =
top level domains are roughly the same number, and their Whois =
structures and policies are each controlled by the individual ccTLD =
operator and their communities.

Last November, the ICANN Board accepted the recommendations of the Whois =
Review Team, an expert group commissioned under the Affirmation of =
Commitments (AoC) ICANN signed with the U.S. Department of Commerce in =
2009.  The terms of reference included in the AoC continued the original =
model that the structure of Whois remain the same and that access be =
free and available to everyone.  A number of us on the ICANN Board had =
been concerned for a long time that purpose of the Whois system had =
evolved far away from its original purpose, and that it was well past =
time to take a fresh look at the entire system.  Accordingly, the Board =
initiated an effort, in parallel with acceptance and implementation of =
the Whois Review Team's recommendations, to start with a clean slate and =
think through whether we might be better served by a revised system.  An =
expert working group was assembled and is currently working through =
these issues.  Its output will be a consideration of the issues and =
recommendations for further work.  It is not yet clear whether the =
result of this effort will lead to a large change, a small change, or no =
change at all.  What is clear is that the results of this working group =
will become fully public, and any decisions will come through our usual =
policy development process.

As I said above, I invite anyone who is interested to participate.

The IETF, ICANN, the RIRs, ISOC, W3C and other organizations have all =
arisen within the ecosystem that accompanies the growth and prevalence =
of the Internet.  It is natural for there to be some tension, =
competition and rivalry among our institutions, but we have all been =
part of the same grand enterprise, we all share the same core values, =
and we all work toward the same goal of an open, innovative, expanding =
Internet.

Steve Crocker,
Chair, ICANN Board of Directors







On May 17, 2013, at 2:13 PM, John Curran <jcurran@istaff.org> wrote:

> On May 15, 2013, at 7:50 PM, David Farmer <farmer@umn.edu> wrote:
>=20
>> So lets play a little hypothetical here;  What if an RIR or ICANN =
through a global policy decided Whois Data no longer should be public =
for overriding privacy reasons.  My read of Section 5, is that would be =
proper path for such a change, and long as the technical guidance of the =
IETF is considered in the process.  But then through RFC 2860 and =
Section 5, if the IETF objected on technical or architectural grounds, =
and formally through the IESG, then the IAB would essentially adjudicate =
the issue.  And ICANN or the RIR are obligated to accept the decision of =
the IAB.  Do I have that right?
>=20
> To be abundantly clear, you are hypothesizing a difference of opinion =
between the=20
> IETF/IESG and the ICANN/RIR communities, wherein the technical =
guidance of the IETF=20
> was considered during the ICANN/RIR decision process, but in the end =
the outcome was=20
> contrary to IETF expectations.
>=20
> This would be an unfortunate (but not impossible) situation, as many =
folks in the=20
> combined community would likely have been involved during the process =
trying to=20
> figure out why there is such a significant difference in views and =
facilitating
> sharing of the beliefs and thought processes that underlie the =
situation.  (btw,
> these types of efforts happen in more contexts than just the =
hypothetical one you=20
> suggest, and are a good reason to ask "Have you hugged your AD =
recently"? ;-)
>=20
>> To be clear, I'm not advocating Whois should or shouldn't remain =
public, or that anything is wrong with the Section 5.  This just seemed =
like a plausible hypothetical to explore how the puzzle pieces work =
together to make the Internet Numbers Registry System.  Also, I just =
want to fully understand what Section 5 really means.
>=20
> Ultimately, your hypothetical situation could result in the breakdown =
of the present
> relationship between IETF and ICANN/RIR organizations (ref: RFC 2860, =
section 2), with=20
> otherwise indeterminate consequences...  i.e. "It would be bad."   =
When the various=20
> Internet organizations are aligned in the coordination of Internet =
critical resources=20
> (DNS, IP addresses, protocol & parameter #'s), then the result is well =
understood. =20
> We lack experience with the alternative, and it is not clear whether =
chair remains=20
> upright when missing one or more legs.
>=20
> FYI,
> /John
>=20
> p.s. Disclaimer:  My views alone.
>=20


From bortzmeyer@nic.fr  Tue May 21 02:08:35 2013
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD24C21F97D4; Tue, 21 May 2013 02:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NJY3SQ92IoHU; Tue, 21 May 2013 02:08:30 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id AE26221F97D0; Tue, 21 May 2013 02:08:29 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9376A28019E; Tue, 21 May 2013 11:07:57 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 8E71628010A; Tue, 21 May 2013 11:07:57 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:113]) by relay2.nic.fr (Postfix) with ESMTP id 8CDAAB38071; Tue, 21 May 2013 11:07:27 +0200 (CEST)
Date: Tue, 21 May 2013 11:07:27 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Andrews <marka@isc.org>
Subject: Re: Deployment of standards compliant nameservers
Message-ID: <20130521090727.GB17630@nic.fr>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130521002639.E75D9348D265@drugs.dv.isc.org>
X-Operating-System: Debian GNU/Linux 7.0
X-Kernel: Linux 3.2.0-4-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 09:08:35 -0000

On Tue, May 21, 2013 at 10:26:39AM +1000,
 Mark Andrews <marka@isc.org> wrote 
 a message of 52 lines which said:

> I'm not sure what the solution should be but regular audits of
> delegated nameservers by infrastructure operator and removal of
> delegations after a grace period

Let's not reinvent the wheel: I suggest to first study the experience
of the TLD which did exactly that. .fr had mandatory technical tests
of the name servers almost from its inception, until december
2012. The tool used for the tests was Zonecheck
<http://www.zonecheck.fr/>

Although these tests certainly contributed to the good technical
quality of the name servers, they were removed both for commercial
reasons (a registry has to make money to pay its employees) and
because it was easier to have the same rules for ccTLDs and gTLDs (and
ICANN forbids these technical tests in gTLDs).




From randy@psg.com  Tue May 21 02:58:51 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D8C21F89BA for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 02:58:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.483
X-Spam-Level: 
X-Spam-Status: No, score=-2.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Fhlt61N6FAM for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 02:58:50 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D0E5921F898B for <ietf@ietf.org>; Tue, 21 May 2013 02:58:50 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UejLD-000HXs-C8; Tue, 21 May 2013 09:58:49 +0000
Date: Tue, 21 May 2013 16:58:44 +0700
Message-ID: <m2ppwkhcx7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Steve Crocker <Steve@shinkuro.com>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt>	(The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 09:58:51 -0000

dear emperor, despite the braggadocio, there seems to be a shortage of
attire.  icann is notorious for pretending to be open but being
effectively closed.  it solicits public comment and ignores it.  i could
go on and on, but i am far less wordy.

randy

From ocl@gih.com  Tue May 21 03:00:33 2013
Return-Path: <ocl@gih.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEFB321F91A3 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 03:00:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqvUOSPUnmJ4 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 03:00:33 -0700 (PDT)
Received: from waikiki.gih.co.uk (salsa.gih.co.uk [IPv6:2a00:19e8:10:5::b]) by ietfa.amsl.com (Postfix) with ESMTP id 980B121F919D for <ietf@ietf.org>; Tue, 21 May 2013 03:00:32 -0700 (PDT)
Received: from waikiki.gih.co.uk (localhost6.localdomain6 [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id 0828318F3C3 for <ietf@ietf.org>; Tue, 21 May 2013 11:00:31 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gih.com; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mahalo1; bh=hczoJq5ux kT6YbLhmoDdOKarFKY=; b=YIj5oTRYaUTVZojY+h7kDB8BafP526BJSBmQC8hG+ zyA/vfhRbFs188aEV9XMN6bTUrPLZ6FPLDYUpQQ7aWQXYPuAtScS47P8V8dTEKFv Qq7KHR9Son8Krzk1+PITglRDRkbvRvwpld6S/Akh1GntfhPn9hNgUzg2FX11Keea 8U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gih.com; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mahalo1; b=GbU NApFGColU1KBClRbOXrcXx2X50Q0/3jVyoYB8qnCIfnm/3AYHxwZCqXFojMuL8+A RzXLJUFJfdWB1i+7AYdgcka5UlNuDN6CdfjS/BfDKm37IGiuOd15QiMoNdTiUmBs mehjAZ5zxiPNU1pW0HHEW1UMWzw8p0+IyFa4mViY=
Received: from [192.168.1.22] (131.145.10.93.rev.sfr.net [93.10.145.131]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by waikiki.gih.co.uk (Postfix) with ESMTPSA id 60B5018F3C1 for <ietf@ietf.org>; Tue, 21 May 2013 11:00:29 +0100 (BST)
Message-ID: <519B45B8.70306@gih.com>
Date: Tue, 21 May 2013 12:00:24 +0200
From: Olivier MJ Crepin-Leblond <ocl@gih.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com>
In-Reply-To: <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 10:00:33 -0000

On 21/05/2013 10:42, Steve Crocker wrote:
> As I said above, I invite anyone who is interested to participate.
>
> The IETF, ICANN, the RIRs, ISOC, W3C and other organizations have all a=
risen within the ecosystem that accompanies the growth and prevalence of =
the Internet.  It is natural for there to be some tension, competition an=
d rivalry among our institutions, but we have all been part of the same g=
rand enterprise, we all share the same core values, and we all work towar=
d the same goal of an open, innovative, expanding Internet.

+1 to everything Steve has said.
And I take this opportunity to remind you that you can directly
influence the outcome of *all* the work at ICANN by taking part in it.
There are several avenues for this.

One of them is through the ALAC: the At-Large Advisory Committee's
(ALAC) role is to facilitate input from Internet users into the ICANN
policy processes. It does not purport to "represent" Internet users, but
it tries as much as it can to act in the *best interests* of Internet
users. But without your input and particularly on technical issues where
we need as much help as we can get, the ALAC cannot issue Statements
that adhere to the general point of view of Internet users.
How can you take part?
The North American region allows for individual membership. Other
regions require that you are part of an At-Large Structure (ALS) to
participate - but if you see the list, you'll notice there are a LOT of
ALSes, many of which are ISOC Chapters.
And you do NOT need to be part of an At-Large Structure to participate
in the At-Large Working Groups. Membership is only needed for matters of
voting - and since we operate by consensus, that's a rare occurrence,
usually only kept to selection of leadership.

A few links:
ALAC Correspondence: http://www.atlarge.icann.org/correspondence
ALAC Policy Development: https://community.icann.org/x/bwFO
ALAC Working Groups: https://community.icann.org/x/loIi

I know this is a shameless plug but in the face of the threat posed by
non-multi-stakeholder systems of governance, I felt a follow-up on
Steve's post was necessary. As Steve says so eloquently, we need to all
work toward the goal of an open, innovative, expanding Internet.

Warm regards,

Olivier MJ Cr=E9pin-Leblond
ALAC Chair
https://community.icann.org/x/ppEi

From ocl@gih.com  Tue May 21 03:25:23 2013
Return-Path: <ocl@gih.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 485A921F85DC for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 03:25:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VYKNDJ9FgF-U for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 03:25:22 -0700 (PDT)
Received: from waikiki.gih.co.uk (salsa.gih.co.uk [IPv6:2a00:19e8:10:5::b]) by ietfa.amsl.com (Postfix) with ESMTP id 0868521F8916 for <ietf@ietf.org>; Tue, 21 May 2013 03:25:21 -0700 (PDT)
Received: from waikiki.gih.co.uk (localhost6.localdomain6 [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id 49C0218F3C3; Tue, 21 May 2013 11:25:20 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gih.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=mahalo1; bh=/TqyhKTyA EvKhlDgDgeo0fOQsuc=; b=wCsrKKjD5x83VFLGEhdOH+NSekcH7scpfAiLMT2qx gnZelpk0TZF8PnJYd8vZHa4OHQUDO8cPCyKkV9caRGBeDgugLPgxDguGu2qG1Jw1 9k6dBgDuhk8242BXtpcmdm5G0DT4bizQLv9M+g/uZGMGdFV7LdlxyAFZnDjbJixW n4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gih.com; h=message-id:date :from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=mahalo1; b=WOa qu9rtP+yJMTIdrJbyibXCeODAGkmfJvjb1hTMZlQatrJ+cXK4p5ImB7OAHTZCxy/ ldL1KwKJdLsA5t6c/aRsiaixdCDuKrLDdDUty0GmMEWFz12L0q1IY9tYbYkjXV4l NJiQMol+5kr3MAyhsovtKU9Xj2Qq56zlZEz+ghA4=
Received: from [192.168.1.34] (ANice-651-1-391-74.w86-205.abo.wanadoo.fr [86.205.23.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by waikiki.gih.co.uk (Postfix) with ESMTPSA id 9E08418F3C1; Tue, 21 May 2013 11:25:19 +0100 (BST)
Message-ID: <519B4B8F.8070105@gih.com>
Date: Tue, 21 May 2013 12:25:19 +0200
From: Olivier MJ Crepin-Leblond <ocl@gih.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com> <m2ppwkhcx7.wl%randy@psg.com>
In-Reply-To: <m2ppwkhcx7.wl%randy@psg.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 10:25:23 -0000

Dear Randy,

On 21/05/2013 11:58, Randy Bush wrote:
> dear emperor, despite the braggadocio, there seems to be a shortage of
> attire.  icann is notorious for pretending to be open but being
> effectively closed.  it solicits public comment and ignores it.  i coul=
d
> go on and on, but i am far less wordy.
>
> randy
>

Quite frankly, I used to have the same feeling... until very recently.
With Steve at the wheel, things have improved a lot. Whilst as recently
as 3 years ago, we often used to feel that ALAC advice was tossed over
the wall and we'd never hear any feedback & be blatantly ignored, things
have improved and we are heard and more importantly listened to a lot
more. Credit for this is due to the new Leadership Teams, both on the
volunteer & Staff parts of ICANN. Today, it's still not perfect, but you
cannot fix a bus by shooting it - work on it instead, to fix it. I
believe it's fixable.
Start here: http://www.icann.org/en/news/public-comment/atrt2-02apr13-en.=
htm

Kind regards,

Olivier
(not wearing any hat)

--=20
Olivier MJ Cr=E9pin-Leblond, PhD
http://www.gih.com/ocl.html


From marka@isc.org  Tue May 21 05:37:51 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC70A21F971C; Tue, 21 May 2013 05:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vP0kNImGm2bk; Tue, 21 May 2013 05:37:50 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id C16AF21F970A; Tue, 21 May 2013 05:37:50 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id EB3735F98CB; Tue, 21 May 2013 12:37:39 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369139868; bh=2hnqC5YjvgcEdkXInVrCtUBrRrXr2F6dcGYw81vVqqk=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=vIT4EWZmwwYszKx2+iCJTjX+WxIRUYpQb3TkS4lgHnv4RSkl+bIoHwNigHGDUjR/V UyYKozMzmMHBvbv2Sf6AyMsAXoa+zBO1kpyD2yP9VPmt8t4HDZhJYTtpMshF1qLxdr 8FiFYNfvgyQV1w8KIrlHN9L77VVCaLcMx1s05jmI=
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:b:4b64:c10:3d68]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 2AC51216C40; Tue, 21 May 2013 12:37:38 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 34AB33491C69; Tue, 21 May 2013 22:37:35 +1000 (EST)
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Tue, 21 May 2013 11:07:27 +0200." <20130521090727.GB17630@nic.fr>
Date: Tue, 21 May 2013 22:37:35 +1000
Message-Id: <20130521123735.34AB33491C69@drugs.dv.isc.org>
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 12:37:51 -0000

In message <20130521090727.GB17630@nic.fr>, Stephane Bortzmeyer writes:
> On Tue, May 21, 2013 at 10:26:39AM +1000,
>  Mark Andrews <marka@isc.org> wrote 
>  a message of 52 lines which said:
> 
> > I'm not sure what the solution should be but regular audits of
> > delegated nameservers by infrastructure operator and removal of
> > delegations after a grace period
> 
> Let's not reinvent the wheel: I suggest to first study the experience
> of the TLD which did exactly that. .fr had mandatory technical tests
> of the name servers almost from its inception, until december
> 2012. The tool used for the tests was Zonecheck
> <http://www.zonecheck.fr/>
> 
> Although these tests certainly contributed to the good technical
> quality of the name servers, they were removed both for commercial
> reasons (a registry has to make money to pay its employees) and
> because it was easier to have the same rules for ccTLDs and gTLDs (and
> ICANN forbids these technical tests in gTLDs).

Which is one of the reasons I wanted to IESG to bring ICANN into
the discussions.  It need to be a level playing field applied to
everyone.  Not also this is not checking the delegation.  It is
checking to nameserver implementation.  All ICANN documents I have
read presume that a RFC compliant nameservers are being deployed.

Nameservers that fail to respond are not RFC compliant.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From moore@network-heretics.com  Tue May 21 06:36:55 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4584521F93FB for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 06:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.652
X-Spam-Level: 
X-Spam-Status: No, score=-3.652 tagged_above=-999 required=5 tests=[AWL=-0.053, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SEp1JcDBVN0a for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 06:36:50 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA2021F9401 for <ietf@ietf.org>; Tue, 21 May 2013 06:36:46 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6F9DC2024C; Tue, 21 May 2013 09:36:45 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 21 May 2013 09:36:45 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=y8UX7y6QuGQADU9WIaFER/ /TW1s=; b=ILMQl1GWEcGbMHIb8a4cGNXiBZL+lAWTdHK0s0x719cCAMyvJAKwg/ Lj2YJ+nqYLhnvx4znyUkGf6hah66vlSyvY9tUFvk/gwJ1MYTEXs05xjcUgFzx84d wicO9oWADHOoJ0Rrk8Kpmbh+acdfo/DXHayj1BWOtmEbI99sjnVAQ=
X-Sasl-enc: 61Z8gR1Wgh6+x2t7pq5Q43Cd4ubcku3WRvamtzZ/n6Cu 1369143405
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id C080E200099; Tue, 21 May 2013 09:36:44 -0400 (EDT)
Message-ID: <519B785E.7060208@network-heretics.com>
Date: Tue, 21 May 2013 09:36:30 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com>
In-Reply-To: <519A82B9.7090305@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: Tue, 21 May 2013 13:36:55 -0000

On 05/20/2013 04:08 PM, Brian E Carpenter wrote:
>>     Publication of EUI-48 or EUI-64 addresses in the global DNS may
>>     result in privacy issues in the form of unique trackable identities.
> This might also result in such MAC addresses being spoofed, thereby allowing
> some sort of direct attack. So it isn't just a privacy concern.
>
> ...
>>     These potential concerns can be mitigated through restricting access
>>     to zones containing EUI48 or EUI64 RRs or storing such information
>>     under a domain name whose construction requires that the querier
>>     already know some other permanent identifier.
> This "can be" seems too weak. Shouldn't we have a MUST here? Also, I doubt
> that the second option (a shared secret) is sufficient.
And yet, multifaced DNS is also a bad idea, and probably not the sort of 
thing that IETF should encourage with a MUST.

Publishing EUI-XX addresses in the DNS is a bad idea.

I get the impression that we're bending over backwards to try to create 
new security risks with this document, and people are trying to justify 
it by citing freedom to innovate.      IMO, that's not the kind of 
"innovation" that IETF should be endorsing.

Keith


From jabley@hopcount.ca  Tue May 21 07:04:13 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 464FB21F9787 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 07:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5q2Orqzj7vif for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 07:04:08 -0700 (PDT)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id CFC1821F9786 for <ietf@ietf.org>; Tue, 21 May 2013 07:04:08 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa10so741277pad.5 for <ietf@ietf.org>; Tue, 21 May 2013 07:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=arF8jD+mHySSMHCHCM6g4vqv5Exgp3Z/MbjIxNC1O1s=; b=k9ZVsL9EBHg9L8fhWUDZkoLXXJYu0c9o47/Zb/gYkyOZCiPsMCrt3am5/DhEFzdPSR 06p3L9AD8/4QcZZSpQPNDoeJzqv3tpNNCYbMCWZ5kWe98G8tI2VMEQbYF4HGcC83nDx+ /hweQzugtLllz5NZk2DHjZ4uOw7sSOM+8YGVM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=arF8jD+mHySSMHCHCM6g4vqv5Exgp3Z/MbjIxNC1O1s=; b=jaDH7Uk9DfDd3kEPR/cqMyKaibDJMl88MaxTgHMj816fYHRBc+gB6Hm2z2TILvlNuO N+5ru81wJze7Nddx/dPNjUBvXAvG6cMbeX3Ef7NN+z9bBkdZcXJ/vTt7cDSzK/d9YIBL nb5g+qz8vKq4LTDl2wCrhoi/r1UwkMn2lgcrmHvXKhq8+MyOD1EF8Jzg1V46eKMIstDV 0yKur0PwMcSLsMyrcNXs2EhpvtRILiir6Aft3ptVKup4Cyd+c5C3zz83p/uwVqyNv/GZ qavd5yuVzaWooR7FzPyBzr8Abp9KBsNleB+9mCWLNpwp4EQELpkRMiivjhZNu2lj6eFa 5ZrA==
X-Received: by 10.66.121.108 with SMTP id lj12mr3482561pab.51.1369145048559; Tue, 21 May 2013 07:04:08 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:ece6:5489:6d0:a836? ([2001:4900:1042:100:ece6:5489:6d0:a836]) by mx.google.com with ESMTPSA id ih1sm2827489pbb.44.2013.05.21.07.04.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 07:04:07 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <519B785E.7060208@network-heretics.com>
Date: Tue, 21 May 2013 10:04:10 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQmRasqtN+QuX5GOG+vr8hJsUlqheqiz7m1cNv08VRVFfiNJi2xzTyb3L98PamkfYxAsOcLj
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, 21 May 2013 14:04:13 -0000

On 2013-05-21, at 09:36, Keith Moore <moore@network-heretics.com> wrote:

> Publishing EUI-XX addresses in the DNS is a bad idea.

With respect, *my* question as the author of this document is simply =
whether the specification provided is unambiguous and sufficient. It was =
my understanding that this was the question before the community in this =
last call.

There has been very little review of the actual specification in this =
thread to date.

RRType assignments are made based on expert review, not IETF consensus, =
document published, or any other criteria. In this case, the RRTypes =
have been assigned and are known to have three independent =
implementations. I'm not sure how the Internet benefits from not =
publishing a specification in a sensible place (and the RFC series is =
surely the most sensible place). *I* think it's a good idea for this =
specification to be published as an RFC.

The topics of whether the current RRType assignment process is =
appropriate, or whether storing these IEEE addresses in the DNS is a =
good or bad idea or whether sub-typing would be useful in any as-yet =
unknown future use case seem entirely tangential. This is not to say =
they are not useful topics, but I don't see how they relate to this =
document. Whether or not this document proceeds has nothing to do with =
any of that.

> I get the impression that we're bending over backwards to try to =
create new security risks with this document, and people are trying to =
justify it by citing freedom to innovate.      IMO, that's not the kind =
of "innovation" that IETF should be endorsing.

I have no real idea where you get that impression. The goal of this =
document is to document the use of RRTypes that have already been =
assigned, to provide a more structured option for encoding data that is =
already published in the DNS using non-interoperable and clumsy encoding =
schemes. Nothing more.


Joe=

From moore@network-heretics.com  Tue May 21 07:19:04 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 872C521F9769 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 07:19:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.649
X-Spam-Level: 
X-Spam-Status: No, score=-3.649 tagged_above=-999 required=5 tests=[AWL=-0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9l-AyOtLcCzO for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 07:18:59 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDF021F9795 for <ietf@ietf.org>; Tue, 21 May 2013 07:18:58 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CBFE0210A2; Tue, 21 May 2013 10:18:55 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 21 May 2013 10:18:55 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=VSOvzLwjp1g90NQU3dLFxz DfYVw=; b=g5d9lnwZWTztjxgMaK7jR3aN0KzOGhf3uweKfjBg3ozbcUfHk/5b8b 9utb5OhLFDFLgtabsVmdKyCVoe3sKay0Ykr1s+WpI1DIjSGfP391nZR8QYEMOS4d eKQ8xlQzwiCmvp0HlBf292OVe71zLE9F9Ams4vDCW4JmZLvsy5H3U=
X-Sasl-enc: Rro1oViX1QEanmhsbSlC9ZBwLm/mIcx+c7bqyt5TfohC 1369145935
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 15F8920008B; Tue, 21 May 2013 10:18:54 -0400 (EDT)
Message-ID: <519B8241.501@network-heretics.com>
Date: Tue, 21 May 2013 10:18:41 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca>
In-Reply-To: <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 14:19:04 -0000

On 05/21/2013 10:04 AM, Joe Abley wrote:
> On 2013-05-21, at 09:36, Keith Moore <moore@network-heretics.com> wrote:
>
>> Publishing EUI-XX addresses in the DNS is a bad idea.
> With respect, *my* question as the author of this document is simply whether the specification provided is unambiguous and sufficient. It was my understanding that this was the question before the community in this last call.

The criteria for Proposed Standard are quite a bit higher than that.   
See RFC 2026 section 4.1.1.

> TThe topics of whether the current RRType assignment process is appropriate, or whether storing these IEEE addresses in the DNS is a good or bad idea or whether sub-typing would be useful in any as-yet unknown future use case seem entirely tangential.

Assignment of the RR types (though IMO unfortunate) is a separate 
issue.    Granting Proposed Standard status would essentially be an 
endorsement of this practice by IETF.

> This is not to say they are not useful topics, but I don't see how they relate to this document. Whether or not this document proceeds has nothing to do with any of that.
>
>> I get the impression that we're bending over backwards to try to create new security risks with this document, and people are trying to justify it by citing freedom to innovate.      IMO, that's not the kind of "innovation" that IETF should be endorsing.
> I have no real idea where you get that impression. The goal of this document is to document the use of RRTypes that have already been assigned, to provide a more structured option for encoding data that is already published in the DNS using non-interoperable and clumsy encoding schemes. Nothing more.

Perhaps Informational or Experimental would be a better label for this 
document, then.

Keith


From jabley@hopcount.ca  Tue May 21 07:30:53 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72AD721F972D for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 07:30:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RN0-PPKUk8Gt for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 07:30:47 -0700 (PDT)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 861EB21F977F for <ietf@ietf.org>; Tue, 21 May 2013 07:30:39 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n9so870719oag.28 for <ietf@ietf.org>; Tue, 21 May 2013 07:30:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=JPqedcXRlobtZl/ZqGpqK8Fem65P78lWtciDjwwPAB8=; b=Ybvry3v6RiNImYQ5f9y1gku5qwRHdWPR+rSG7mci/MIc8lJQbe9VUuWBkQM5K0TyM0 OV53PN0U26FLVBj5xFBXA5P9vXZcJSQxIu3gigirx1wgVlYq9kj7lJhUOUIDBVNH81Aw GhClawGZCxlH84FvHdGirII3MPkAHIkxI2YZU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=JPqedcXRlobtZl/ZqGpqK8Fem65P78lWtciDjwwPAB8=; b=MTs2ebHqwJpIWGPabWOQ8HYtK8b65+z3pcknIq72ULQ2NdrKRXsSWw/M7AaUrhZ1Wc bALUTLUmzYRUz5IbUBAsFPqdDNXuSti+kSAw0s8tRqMuAHCYwqo6o1ZudPvm9IETi05e HHCwzqrjf9LTvV49nuUxytgUaWocY+a8h6IxGoR9XnM7DaaDkuF050MQYVGhjKGsy0/M FAXkkKculiKTYufkE6DAC/ThRA/Sr/Qmei6uBZMJO8Ig8yhoXo5FzXHorHGCdOArybU+ P1n29EoKIL77pgVomlIJGvIoQid9nBps/Sa9RLrTwGM86tSRdti3J0XU8mgud1RbymXl 6Z0A==
X-Received: by 10.60.102.145 with SMTP id fo17mr1554732oeb.76.1369146638472; Tue, 21 May 2013 07:30:38 -0700 (PDT)
Received: from dev-qa-ref.chatham.teksavvy.ca (nat.teksavvy.com. [206.248.154.94]) by mx.google.com with ESMTPSA id q4sm2617882obl.1.2013.05.21.07.30.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 07:30:37 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <519B8241.501@network-heretics.com>
Date: Tue, 21 May 2013 10:30:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQlJBvFWYnPOCHDSLgslud/AKeXMXf5Z2nU79iieaSdOsnVC21fYpnWLyOaYImzmB6C9cPWR
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, 21 May 2013 14:30:53 -0000

On 2013-05-21, at 10:18, Keith Moore <moore@network-heretics.com> wrote:

> Perhaps Informational or Experimental would be a better label for this =
document, then.

Informational was my original plan; I was persuaded by Some People that =
the standards track was more appropriate. As I mentioned, my objective =
is simply to publish the specification.

If the community is more comfortable with the publication objective =
being met with informational rather than standards track, I'm fine with =
that.


Joe=

From john-ietf@jck.com  Tue May 21 08:07:15 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F0721F9831 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:07:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjaOu5vO++iq for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:07:06 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 54DF221F981F for <ietf@ietf.org>; Tue, 21 May 2013 08:07:05 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ueo9R-0009gk-9u; Tue, 21 May 2013 11:06:57 -0400
Date: Tue, 21 May 2013 11:06:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joe Abley <jabley@hopcount.ca>, Keith Moore <moore@network-heretics.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Message-ID: <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com>
In-Reply-To: <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 15:07:15 -0000

--On Tuesday, May 21, 2013 10:04 -0400 Joe Abley
<jabley@hopcount.ca> wrote:

>...
> There has been very little review of the actual specification
> in this thread to date.
> 
> RRType assignments are made based on expert review, not IETF
> consensus, document published, or any other criteria. In this
> case, the RRTypes have been assigned and are known to have
> three independent implementations. I'm not sure how the
> Internet benefits from not publishing a specification in a
> sensible place (and the RFC series is surely the most sensible
> place). *I* think it's a good idea for this specification to
> be published as an RFC.

Joe, as the person with the dubious distinction of having
started this thread when the Last Call was announced, I'm not
questioning the desirability of good documentation of any
RRTYPE, nor do I doubt the fact that these were properly
assigned and are deployed.  I also agree with you that questions
about the expert review process belong elsewhere (and I don't
know that I'd want to change it in any formal way).

Had you written this document as a "this is how it is -- this is
to tell the community about what is deployed" informational one
that described the RRTYPEs and asked that it be published as
Informational, I wouldn't have been likely to raise any
objections.  Had the Security Considerations section or privacy
discussion described the risks, possibly explained how they
might be mitigated, but basically said "if those are a big
enough problem for you, don't use this facility", that wouldn't
have been a problem for me: I can't speak for Keith, but you
might have not heard from him either.

But the document has been Last Called as an Proposed Standard,
not that type of informational document.  That, at least to me,
makes both discussions of your design decisions and the relevant
security and privacy mechanisms entirely appropriate because
Proposed Standard requires IETF consensus approval of the whole
package, quite independently of your ability to register a new
RRTYPE (or two or three).   All I'm asking for is that, if you
want this as a Proposed Standard you carefully and convincingly
describe your design rationale.  I want that both because it
seems generally appropriate in this case and because, if someone
comes along and wants to register the EUI64-with-embedding or
EUI-with-48-64-switch RRTYPEs and there is pushback because
EUI48 and EUI64 are already registered, I think it is important
that pushback be based on documented and well-reasoned design
choices, not an appeal to the supposed authority of the IETF.  

You wrote a bit later:

> Informational was my original plan; I was persuaded by Some
> People that the standards track was more appropriate. As I
> mentioned, my objective is simply to publish the specification.

It might be that no one could know before this discussion
started but, at least in retrospect, those Some People may have
steered you in the wrong direction if your goal and theirs was
to get something published without putting various design
decisions into the spotlight.  To say what Keith may be saying
in different language, there is lots of stuff floating around
the Internet of which the IETF might not approve.  Publishing
Informational RFCs containing descriptions of them so they can
be understood is still a good thing.  If someone wants to follow
those RFCs with "considered harmful or at least disgusting"
commentary and try to get it published, that is a separate
issue.  But asking for Proposed Standard is a rather different
matter because it requires an IETF consensus assertion that the
criteria of RFC 2026 have been satisfied.   

If you don't think that level of scrutiny is appropriate for
this situation, ask that the document be pulled from Last Call,
review it to make it as descriptive and declarative as possible
rather than even implicitly normative (I'd have to reread, but I
think it is at least close on that criterion), and then resubmit
it as an individual or independent submission for Informational
publication.

> I have no real idea where you get that impression. The goal of
> this document is to document the use of RRTypes that have
> already been assigned, to provide a more structured option for
> encoding data that is already published in the DNS using
> non-interoperable and clumsy encoding schemes. Nothing more.

Ok.  That, to me, is a perfect recipe for an Informational
document.  It may, separately, be a call for a much more
aggressive denunciation and deprecation of overloaded and
trickily-encoded TXT RRs than RFC 5507 provides, maybe as a BCP
rather than IAB-Informational but that is also a separate issue
and problem.

best,
   john



From randy@psg.com  Tue May 21 08:23:16 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7E921F97BE for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:23:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8iVQigcbu95l for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:23:15 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 456FB21F979B for <ietf@ietf.org>; Tue, 21 May 2013 08:23:15 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UeoPA-000If5-6i; Tue, 21 May 2013 15:23:13 +0000
Date: Tue, 21 May 2013 22:23:03 +0700
Message-ID: <m24ndwgxwo.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
In-Reply-To: <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 15:23:16 -0000

joe,

i have read the draft.  if published, i would prefer it as a proposed
standard as it does specify protocol data objects.

< where you goin' with that gun in your hand? >
i am not at all sanguine about the issues raised in the in sec cons.  i
accept that NTRE038D may have asked that these be in the dns, but seems
to me that it is ill advised and some other means to meet their actual
needs might be found.  e.g. what's the matter with logs?

nits you are welcome to ignore.

1 - intro - do we have a standard way to refer to the dns specs as tuned
    	    in 42 subsequent rfcs since 1035?

3.2 and 4.2 the presentation format specs might be simpler if the
    	    examples in 5 were moved there

6 - the example use case is as much or more a motivation as an example

randy

From ajs@anvilwalrusden.com  Tue May 21 08:40:43 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C523321F96D6 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqqEM0EYd9f3 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:40:32 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E293A21F96B2 for <ietf@ietf.org>; Tue, 21 May 2013 08:40:31 -0700 (PDT)
Received: from mx1.yitter.info (unknown [38.126.117.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 6A8328A031 for <ietf@ietf.org>; Tue, 21 May 2013 15:40:30 +0000 (UTC)
Date: Tue, 21 May 2013 11:40:24 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Message-ID: <20130521154024.GA36906@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m24ndwgxwo.wl%randy@psg.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 15:40:43 -0000

Not related to the draft as such (whose publication, incidentally, I
support):

On Tue, May 21, 2013 at 10:23:03PM +0700, Randy Bush wrote:
> 
> 1 - intro - do we have a standard way to refer to the dns specs as tuned
>     	    in 42 subsequent rfcs since 1035?

Alas, no.  Some time ago, DNSEXT was re-vivified in an effort to write
a "protocol profile" that would have been a nice roll-up document to
do this.  But there was no energy to get the work done and the drafts
languished for months without any changes.  It still seems a
worthwhile project, but there is no evidence that we have a population
interested enough to do the work.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From joelja@bogus.com  Tue May 21 08:46:55 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322E721F9787 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:46:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vTBB7wYDsrpb for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:46:54 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id BFD6821F9669 for <ietf@ietf.org>; Tue, 21 May 2013 08:46:54 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4LFkpQe099893 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 21 May 2013 15:46:52 GMT (envelope-from joelja@bogus.com)
Message-ID: <519B96E5.9040207@bogus.com>
Date: Tue, 21 May 2013 08:46:45 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Joe Abley <jabley@hopcount.ca>, Keith Moore <moore@network-heretics.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com>
In-Reply-To: <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 21 May 2013 15:46:52 +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, 21 May 2013 15:46:55 -0000

On 5/21/13 8:06 AM, John C Klensin wrote:
>
>    All I'm asking for is that, if you
> want this as a Proposed Standard you carefully and convincingly
> describe your design rationale.  I want that both because it
> seems generally appropriate in this case and because, if someone
> comes along and wants to register the EUI64-with-embedding or
> EUI-with-48-64-switch RRTYPEs and there is pushback because
> EUI48 and EUI64 are already registered,
It seems like we're still re-arguing the assignment of the rr-types. It 
doesn't seem like future assignments are likely to have anymore pushback 
than present.

With respect to the question of proposed standard. What changes if the 
requested status is informational?

From moore@network-heretics.com  Tue May 21 08:50:53 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9896021F979D for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.647
X-Spam-Level: 
X-Spam-Status: No, score=-3.647 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eJbfhdj1GzV2 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:50:48 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 093F521F97A5 for <ietf@ietf.org>; Tue, 21 May 2013 08:50:47 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 72CD9214EB; Tue, 21 May 2013 11:50:44 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 21 May 2013 11:50:44 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=nTCJwm3TGTbsbQVY+GKfN7 j1LFw=; b=cfI664S1mV3huA9OXCt7m+loDd2CFM1OZAXmuUS15gFKY31RaLZGxR C+vrscJ/sAo/boclC/VrtYSiXCV/RIV1e2D8FWtgCU4rPBFi13wNf1Y8NvTEQugN kHs69Wr5if46oRM0khz3z7RfXG/ZPAoDjFS0rC+KQhzFyNZ2myfmQ=
X-Sasl-enc: GLeqsGWtkzWmz7WijXVhnyuSGbeNW7o9+pn9ybl12T7j 1369151444
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 8A0A8200188; Tue, 21 May 2013 11:50:43 -0400 (EDT)
Message-ID: <519B97C5.6010901@network-heretics.com>
Date: Tue, 21 May 2013 11:50:29 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com>
In-Reply-To: <519B96E5.9040207@bogus.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: Tue, 21 May 2013 15:50:53 -0000

On 05/21/2013 11:46 AM, joel jaeggli wrote:
>
> With respect to the question of proposed standard. What changes if the 
> requested status is informational?

I think just get rid of the normative language - SHOULDs, MUSTs, etc.

Given that the RR types have already been assigned, documenting them 
seems entirely appropriate.

Keith


From jabley@hopcount.ca  Tue May 21 08:52:49 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB2B21F97CF for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I0Hy4RX-say7 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:52:44 -0700 (PDT)
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7C21321F97A0 for <ietf@ietf.org>; Tue, 21 May 2013 08:52:44 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id r11so753798pdi.35 for <ietf@ietf.org>; Tue, 21 May 2013 08:52:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=MPbLMDLDjfisZFzSoH4D3/CnEwNg2lQLlWYY2HKPQ7g=; b=fKxA7OanM4Ua2Kd4femLXqJJivib4sIW4d9OH/Rmbu1HHnadXjCfnnrq68nY0mYgKI /kDkqbZ27iXtk0/5eczTrwQu1dMnJCbpq6AAl6rdw4irQluSHaaAfYYuK69UFrNdBhzX QY/MCMliOokCTHvqdC7cflW6oHsx3NJbD523E=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=MPbLMDLDjfisZFzSoH4D3/CnEwNg2lQLlWYY2HKPQ7g=; b=into8RMzbRgY7Tzqiw/KtsibWUN7GHqkdBU7Xjin5bNiZehtgdSH+HJRS+TdblOTOU mG0abIQnyE6YYlFg/u1nLEF3ThUfKfyNJzwtkw5nRsTPzMSLqJXwxrXtIM/BxJB3Goit D5bS2l+4YBrYJk73HyAJ4SoEq0JgaTKd4lpaFqu4u2biVRvb1b7qChKx+hDL29Wys9q7 Eag1/mkJHZLdelZLgUq+eEP6l6I8OoLrG22Jm1p64m6nZhVHI9REo45a93gbbqp8Uru0 sVCJh/y6fQRIn7gdtAINg9xcn3apRAdmDh7CXEt0O5bjY0+69eme3PKnNEkVM6o5dq5m xrGg==
X-Received: by 10.66.216.225 with SMTP id ot1mr3868256pac.154.1369151564111; Tue, 21 May 2013 08:52:44 -0700 (PDT)
Received: from [199.212.90.40] ([199.212.90.40]) by mx.google.com with ESMTPSA id j10sm3210983pbh.23.2013.05.21.08.52.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 08:52:43 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <519B97C5.6010901@network-heretics.com>
Date: Tue, 21 May 2013 11:52:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQllZE/42GIFykvFF0KH9Jv/aS15QuNG9CR/ziobzJkvobjDLrXYNTNnieISLky9Xq2AYOOf
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, 21 May 2013 15:52:49 -0000

On 2013-05-21, at 11:50, Keith Moore <moore@network-heretics.com> wrote:

> On 05/21/2013 11:46 AM, joel jaeggli wrote:
>>=20
>> With respect to the question of proposed standard. What changes if =
the requested status is informational?
>=20
> I think just get rid of the normative language - SHOULDs, MUSTs, etc.

=46rom the perspective of giving guidance to people implementing these =
RRTypes, it seems to me that the normative language is useful, perhaps =
even necessary, to ensure interoperability.

I admit I have not done my homework here; is the suggestion that the =
2119 normative language cannot (MUST NOT? :-) appear in an informational =
document?


Joe


From moore@network-heretics.com  Tue May 21 08:56:39 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0B321F96CB for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.644
X-Spam-Level: 
X-Spam-Status: No, score=-3.644 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uYHJgzrjQmp9 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:56:34 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 9B67E21F96D6 for <ietf@ietf.org>; Tue, 21 May 2013 08:56:30 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0F52F20DD7; Tue, 21 May 2013 11:56:28 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 21 May 2013 11:56:30 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=Yo3FewhGizWRHX7cdTo50/ b7dbY=; b=gJ8Gu4+O1V9+PLUv5h3VcL4jT0YAY0hsamBkV9fKpqUoZS6eGMmCA1 V+s5B3lwdNk7NvwFKPnqTYp3CJ8MG1zXmimQ6dLRQrBAo6+SR0YdiM84WPGRYjZ9 fxWSagw+HmDYycZlvoXW3V2kgpPa68LwKekEZOBRg5iWc8SubxR/8=
X-Sasl-enc: WNeO87y7paSSr3PrWIcJNA/Dc/5PZ8rkwKkvoz49+aKw 1369151788
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id A6C22C8001B; Tue, 21 May 2013 11:56:27 -0400 (EDT)
Message-ID: <519B991D.4040804@network-heretics.com>
Date: Tue, 21 May 2013 11:56:13 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca>
In-Reply-To: <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca>
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: Tue, 21 May 2013 15:56:39 -0000

On 05/21/2013 11:52 AM, Joe Abley wrote:
> On 2013-05-21, at 11:50, Keith Moore <moore@network-heretics.com> wrote:
>
>> On 05/21/2013 11:46 AM, joel jaeggli wrote:
>>> With respect to the question of proposed standard. What changes if the requested status is informational?
>> I think just get rid of the normative language - SHOULDs, MUSTs, etc.
>  From the perspective of giving guidance to people implementing these RRTypes, it seems to me that the normative language is useful, perhaps even necessary, to ensure interoperability.
>
> I admit I have not done my homework here; is the suggestion that the 2119 normative language cannot (MUST NOT? :-) appear in an informational document?

2119 language is intended to describe requirements of standards-track 
documents.    Informational documents cannot impose requirements.

Keith


From jabley@hopcount.ca  Tue May 21 08:57:28 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ADCE21F97ED for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ezqgPlHpeP8w for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 08:57:27 -0700 (PDT)
Received: from mail-da0-x229.google.com (mail-da0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id 67C2E21F97D9 for <ietf@ietf.org>; Tue, 21 May 2013 08:57:27 -0700 (PDT)
Received: by mail-da0-f41.google.com with SMTP id y19so518160dan.14 for <ietf@ietf.org>; Tue, 21 May 2013 08:57:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=m7orcnpvdiwPv4HMBS5H5O/MTTz5YDkeBwDk7HBSP3E=; b=jiPUalsPqM11BE/8izOUZHvv303csTktIkTgyP6IFmOHNQd4UZFMiRGfps58SFBzV1 YZUId2cN+gpqbVrKqwQJDiYEcDmVz3RvIbsJuCfkB+EIjJNgJsRp63fe4QVYIODYl1Gv 579pbgDetgLy1IX31FaN9FS9MtYI/TYyppv7Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=m7orcnpvdiwPv4HMBS5H5O/MTTz5YDkeBwDk7HBSP3E=; b=btbQW1Hczb+979LbBcmB0beWU+UDpUNBSWX/zM3YX8e8DP+WwWq6oq6wv7of2E52+D cSHjbwHvbQJ6NIyy31TxQgnQJlnN2yMTP3qlJ1m1VBv71Ru0uO/SA+37edkUQy1iCH70 C2zLqkWLQf7Mh7d2Wf5cUwId0m6AR35SN0NSOPngeNf3h9kyHV8t14RR/KtfM/k9i8Bk iKM0BkYNSfwvBnVzBZvZuQTHELHnKDudhltqPxdK2tQNSbOyKRY73ht3PUODM0gBEHhF HUQjJGarsBHVeuVI2XaJ8EXfXk3/fIt42BU0eaEGMNRyaHlPD6ongsM7Vs7eIgZ5iRGs uUEQ==
X-Received: by 10.68.106.196 with SMTP id gw4mr3383895pbb.126.1369151847120; Tue, 21 May 2013 08:57:27 -0700 (PDT)
Received: from [199.212.90.40] ([199.212.90.40]) by mx.google.com with ESMTPSA id wi6sm3224796pbc.22.2013.05.21.08.57.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 08:57:26 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <519B991D.4040804@network-heretics.com>
Date: Tue, 21 May 2013 11:57:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D17764B0-B627-4DC2-A1B4-26898655E9EC@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQkegHhChVtxpOYZ9x9If9jD1C+RUPhAkrrPaGwBkAR4s60zgye1A4cEZxPo9166/iUHgEhd
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, 21 May 2013 15:57:28 -0000

On 2013-05-21, at 11:56, Keith Moore <moore@network-heretics.com> wrote:

> On 05/21/2013 11:52 AM, Joe Abley wrote:
>> On 2013-05-21, at 11:50, Keith Moore <moore@network-heretics.com> =
wrote:
>>=20
>>> On 05/21/2013 11:46 AM, joel jaeggli wrote:
>>>> With respect to the question of proposed standard. What changes if =
the requested status is informational?
>>> I think just get rid of the normative language - SHOULDs, MUSTs, =
etc.
>> =46rom the perspective of giving guidance to people implementing =
these RRTypes, it seems to me that the normative language is useful, =
perhaps even necessary, to ensure interoperability.
>>=20
>> I admit I have not done my homework here; is the suggestion that the =
2119 normative language cannot (MUST NOT? :-) appear in an informational =
document?
>=20
> 2119 language is intended to describe requirements of standards-track =
documents.    Informational documents cannot impose requirements.

Then I think we've just identified a reason why this document should be =
on the standards track.


Joe


From moore@network-heretics.com  Tue May 21 09:02:44 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13AF421F9806 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.642
X-Spam-Level: 
X-Spam-Status: No, score=-3.642 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMDE9fsRgibx for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:02:39 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0409821F97D2 for <ietf@ietf.org>; Tue, 21 May 2013 09:02:38 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 71C22215C0; Tue, 21 May 2013 12:02:38 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute5.internal (MEProxy); Tue, 21 May 2013 12:02:38 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=/X4TDJmQZUDUscBw1bxjP1 gd+cA=; b=OxEnMrpaf70XJLxiL5UJdL1F9aYMk57Q6Nm1ymSDhx40y2e55QrCqs y93y5I53FapF/NducEuHpK+AIVN1YMuCH2eBBHvOU6H9N+nzmjJb4WcKE8ZqBzKz ZENk7vxyj5TLlFyHi5hDNPuVSEnPzKtfvMdE93T2N1ij9D9lPYQYk=
X-Sasl-enc: 3NExBv9TqfiyhMV1iTecMQvGOcb/cu6oR7id/mfB9stC 1369152158
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 908F92000DB; Tue, 21 May 2013 12:02:37 -0400 (EDT)
Message-ID: <519B9A8F.70701@network-heretics.com>
Date: Tue, 21 May 2013 12:02:23 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <D17764B0-B627-4DC2-A1B4-26898655E9EC@hopcount.ca>
In-Reply-To: <D17764B0-B627-4DC2-A1B4-26898655E9EC@hopcount.ca>
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: Tue, 21 May 2013 16:02:44 -0000

On 05/21/2013 11:57 AM, Joe Abley wrote:
> On 2013-05-21, at 11:56, Keith Moore <moore@network-heretics.com> wrote:
>
>> 2119 language is intended to describe requirements of standards-track documents.    Informational documents cannot impose requirements.
> Then I think we've just identified a reason why this document should be on the standards track.
>
Actually I think that what we need is a BCP that says that DNS is not 
intended, not designed, and SHOULD NOT be used for dissemination of any 
information that is not deemed acceptable for widespread public 
distribution.   Neither the DNS protocol nor DNS implementations are 
designed to meet the security requirements of such applications, and DNS 
is too widely deployed to change that.

Keith


From Ray.Bellis@nominet.org.uk  Tue May 21 09:04:22 2013
Return-Path: <Ray.Bellis@nominet.org.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 35A3221F97D2; Tue, 21 May 2013 09:04:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XyJi6nfCDur; Tue, 21 May 2013 09:04:17 -0700 (PDT)
Received: from mx1.nominet.org.uk (mail.nominet.org.uk [213.248.242.48]) by ietfa.amsl.com (Postfix) with ESMTP id 412B121F9837; Tue, 21 May 2013 09:04:11 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:Received:Received:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=nAuXoW6acv5zqDNXwLyv5pjxIyyrCrnaTfINrP3Rk53GxjtOWzJiD1vl b12j80ZzTHO5Phdl208C2WNbvM/9/5pcZgnm8MTWWgctcHYqBN8Yrc13o yIilFuC8brq1hlH;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1369152251; x=1400688251; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=AT/FiLx9tdZ3OSaToPHGPH2nR0FYxf8EBCRZS/9NNpQ=; b=PBlk6/H7K2bgDZ+/179kEcp6UkhKmuTlVCKp2ixA8rTptZwvuPOc7+rS VEbuxT35e2Fi90XWgN7TcEiv3VpXe4AOKu+Y7WZidMDxyf0hawyrFi4wP S4qdxfxoPjyXQAx;
X-IronPort-AV: E=Sophos;i="4.87,714,1363132800";  d="scan'208";a="828066"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx1.nominet.org.uk with ESMTP; 21 May 2013 17:03:41 +0100
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%17]) with mapi id 14.02.0318.004; Tue, 21 May 2013 17:03:41 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Deployment of standards compliant nameservers
Thread-Topic: Deployment of standards compliant nameservers
Thread-Index: AQHOVbn/v/XQ3kzhmU2h0u3XmPRdzpkOzT+AgADwDgA=
Date: Tue, 21 May 2013 16:03:40 +0000
Message-ID: <53F00E5CD8B2E34C81C0C89EB0B4FE732DD1B862@wds-exc1.okna.nominet.org.uk>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <519AD17D.8040501@network-heretics.com>
In-Reply-To: <519AD17D.8040501@network-heretics.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <406F90F43443744BB0E9CCCEC4DE9811@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "iesg@ietf.org" <iesg@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, 21 May 2013 16:04:22 -0000

On 21 May 2013, at 02:44, Keith Moore <moore@network-heretics.com> wrote:

> p.s. I wonder if the problem you describe might at least partially be cau=
sed by DNS proxies and interception proxies, including but not limited to t=
hose incorporated in consumer-grade routers.

Those are already addressed in RFC 5625.

kind regards,

Ray



From hartmans@mit.edu  Tue May 21 09:08:18 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8B3221F9265 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:08:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tcQhPG0APIEk for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:08:13 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 91C8F21F91BC for <ietf@ietf.org>; Tue, 21 May 2013 09:08:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 60E4820556; Tue, 21 May 2013 12:05:15 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id effumRCLJJ5s; Tue, 21 May 2013 12:05:13 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 21 May 2013 12:05:13 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 610B4440B; Tue, 21 May 2013 12:08:10 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com>
Date: Tue, 21 May 2013 12:08:10 -0400
In-Reply-To: <519B991D.4040804@network-heretics.com> (Keith Moore's message of "Tue, 21 May 2013 11:56:13 -0400")
Message-ID: <tslppwkuxhx.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: 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, 21 May 2013 16:08:18 -0000

>>>>> "Keith" == Keith Moore <moore@network-heretics.com> writes:


    Keith> 2119 language is intended to describe requirements of
    Keith> standards-track documents.  Informational documents cannot
    Keith> impose requirements.

i think using 2119 language in informational documents is often
appropriate and there are certainly plenty of examples of informational
documents that use 2119 language.

From paul.hoffman@vpnc.org  Tue May 21 09:08:33 2013
Return-Path: <paul.hoffman@vpnc.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 4CA6521F9833 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.614
X-Spam-Level: 
X-Spam-Status: No, score=-102.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aco7m7orY3rj for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:08:32 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id E056321F97D3 for <ietf@ietf.org>; Tue, 21 May 2013 09:08:32 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4LG8TNT096613 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 May 2013 09:08:30 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <519B991D.4040804@network-heretics.com>
Date: Tue, 21 May 2013 09:08:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <146962B9-CA4F-4CF1-B5C6-82B165F6E34A@vpnc.org>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
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, 21 May 2013 16:08:33 -0000

On May 21, 2013, at 8:56 AM, Keith Moore <moore@network-heretics.com> =
wrote:

> 2119 language is intended to describe requirements of standards-track =
documents.   =20

Can you support that statement with a reference to an RFC or an IESG =
statement that supports it?

> Informational documents cannot impose requirements.

Same request.

I don't find either statement supported by RFC 2119 or 2026, or any =
updates to the latter, but I may have missed it.

--Paul Hoffman=

From jabley@hopcount.ca  Tue May 21 09:08:55 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4521221F984B for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:08:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2maXXww2OKYF for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:08:50 -0700 (PDT)
Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by ietfa.amsl.com (Postfix) with ESMTP id CA83721F984E for <ietf@ietf.org>; Tue, 21 May 2013 09:08:39 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id kp6so860008pab.7 for <ietf@ietf.org>; Tue, 21 May 2013 09:08:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=NrnqNWu5j91OkMFXG88aMaRacHUjmn3R1rhQTbisyN0=; b=SDv6b4gBnIGs6WwNCe/BionSmo6eYo62jw5ndNIkR6D24eA0tOhFM9pyqp7H8rV+aa bc8ov2n3oXmI33W1vdzUHMUcIKjGFuQfM2EGJbanzQFWtT98D0QqxyBRfbSAp3QW9Jlc RAga2sIpZS2JnynmTsT1i5sPhuWjjO2+esozU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=NrnqNWu5j91OkMFXG88aMaRacHUjmn3R1rhQTbisyN0=; b=WA29+US639PCi/4GSPIw1l1fUxbh+M8hd/HiXiL5IJ58Er4jqnRWeB6WhzcF8ZcZ3m nyA1Tuh75ywynsUS069TSE6GM1jJZ04FBokDCrgR5ho4H0nhDOHAFt6IVOq1zy9P0J5q DeE1Y+yTJW+xY+TO9N+ecNj6XSi5qWmkQYNr2iJB5+50qtlX13/m0Pz87lF2p1SqM0SY s1B9ks035aTlb7QbfQpFGlmPsZplicBA5ec5YLx5v9VMTSAAEEosU0s6mfJdNDhk9s5U vjeGqWj0LNo8vVlBW2DgIruzgWe9KTYypgvbXYGAmqhjdtJHkwhjqTOdeoYfpPKD2/OT A6yA==
X-Received: by 10.66.102.97 with SMTP id fn1mr3986707pab.116.1369152519457; Tue, 21 May 2013 09:08:39 -0700 (PDT)
Received: from [199.212.90.40] ([199.212.90.40]) by mx.google.com with ESMTPSA id xl10sm3888088pac.15.2013.05.21.09.08.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 09:08:38 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <519B9A8F.70701@network-heretics.com>
Date: Tue, 21 May 2013 12:08:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <159EE16A-5867-4BA6-9F34-11ED6914ECF8@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <D17764B0-B627-4DC2-A1B4-26898655E9EC@hopcount.ca> <519B9A8F.70701@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQni238B4gw6rjIDHrO+ibP2KDT9I8vBMu6GuTlLpBHfJ6+HZwfXL8g4ccqKtP6MB6ztfJmm
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, 21 May 2013 16:08:55 -0000

On 2013-05-21, at 12:02, Keith Moore <moore@network-heretics.com> wrote:

> Actually I think that what we need is a BCP that says that DNS is not =
intended, not designed, and SHOULD NOT be used for dissemination of any =
information that is not deemed acceptable for widespread public =
distribution.   Neither the DNS protocol nor DNS implementations are =
designed to meet the security requirements of such applications, and DNS =
is too widely deployed to change that.

I'd be quite happy to work on such a document if there were others keen =
to contribute, review, etc, but I don't see it as anything specific to =
the specifications under discussion here.

What am I missing?

How is EUI48 more dangerous to the world than (say) TXT or NSAP?


Joe=

From sm@resistor.net  Tue May 21 09:21:23 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5FD521F9731 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.099,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GodHeuATwJ0c for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:21:22 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9A721F9747 for <ietf@ietf.org>; Tue, 21 May 2013 09:21:18 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4LGLBDx014545; Tue, 21 May 2013 09:21:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369153276; bh=Z4drBuT8I164NcxwvhaqP1t4F+9rj+nP6bO1ckTEMjs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bBpB9GH1oUqBkv4cZ866yWB0dRUBzBXXkXNnYRWJEL1u15verJ9HyOXwPwrePO/0g EdMAqVQyA6V4weUvXihSYwn9oBWyFpb/VJwt80vAM8j1GFdUOT0HdlRRZOSA0boTXQ Zdi9rKBOhV5VGAicrp8pODYjgkeV3sqMz9TQrCiU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369153276; i=@resistor.net; bh=Z4drBuT8I164NcxwvhaqP1t4F+9rj+nP6bO1ckTEMjs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dMPcQG7NVZaK0qhmHS74Roc+Ww1yipHOC9FKDJp4axMTxhNVr8Udv30wrWDX1Od5h cN7IJfDzmJX66qITl5GxyZCZp1Q+xY7gGp2cVyL2nHHQD74QvGxPwjrC15MthsinSA QtPpoSjygDQKKNRuXFQ2d99lAYOQd9odCBqiLPY8=
Message-Id: <6.2.5.6.2.20130521033110.0ba545d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 21 May 2013 08:50:27 -0700
To: Steve Crocker <Steve@shinkuro.com>
From: SM <sm@resistor.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.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: Tue, 21 May 2013 16:21:23 -0000

Hi Steve,
At 01:42 21-05-2013, Steve Crocker wrote:
>I want to share two thoughts, one about the role of the IETF, ICANN 
>and other organizations within the Internet ecosystem, and one about Whois.
>
>The great strength of the IETF is it's a forum for technical people 
>to come together, work out the details of protocols, and publish 
>consensus documents.  The IETF does not have any formal powers 
>granted by legal authorities.  IETF standards are effective because 
>they're accepted and they work, not because they're imposed on 
>anyone.  IETF standards are respected around the world because they 
>embody the wisdom and experience of the technical community.  No one 
>is obliged to use the protocols created within the IETF, but, of 
>course, a huge portion of the world does use these protocols.

IETF standards are  "de facto" standards.  It is doubtful whether 
some of the RFCs embody the wisdom and experience of the IETF 
community.  Nobody may be obliged to use these "standards".  However, 
do people have a choice?  How would I contact the IETF if my mail 
server uses another "standard"?

>Like the IETF, ICANN is also an open organization.  ICANN meetings 
>are free, and a veritable ocean of documents are published 
>regularly, many in multiple languages to increase availability.

I note that IETF meetings are not free.  Everyone can claim to be open.

>ICANN is purposefully organized to include participation from a 
>range of communities, e.g. business, civil society, governments, and 
>the technical community.  As I write this, I am at a retreat for the 
>ICANN Board focusing on strategic planning.  One of the seats on the 
>Board is allocated to a liaison from the IETF, and thus I am 
>actually sitting at the time I drafted this note in between Thomas 
>Narten and Jonne Soininen, the outgoing and incoming IETF liaisons 
>to the ICANN Board.

There are currently three comments about the proposed Whois 
Information Status Policy ( 
http://www.icann.org/en/news/public-comment/wisp-10may13-en.htm 
).  There's more comments than that for some IETF Last Calls (e.g. 
http://www.ietf.org/mail-archive/web/ietf/current/msg79366.html 
).  The IETF Chair posted an article on his blog.  There is a long 
thread about it ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg78984.html 
).  The ICANN range of communities seem to be having problems sending 
mail as I don't see any trace of their participation.

If I want to know what the IESG is up to, I read a web page and I find:

   "abstract: the draft does stuff, it doesn't 'set out to' do stuff, 
at least not anymore"

>  of the IETF experience that "let's send it over to the IETF" 
> doesn't work.  The IETF isn't a standing army ready to do ours or 
> anyone else's work.  Rather, I say, it's a place where the relevant 
> people can get together to get their work done.  And, indeed, a 
> number of ICANN people

Agreed.

>  actively participate in various IETF working groups.)

I do not see ICANN people participating in an IETF Last Call.  I 
would not call it active participation.

>The roster of topics active within ICANN at any given time is fully 
>documented and publicized, and I invite anyone who is interested to 
>participate.  We listen to everyone, and we publish tentative 
>results, tentative policies, etc. for everyone to critique.

I am curious about where the ICANN "process" is documented.  I could 
not find anything that looks like RFC 2026.

>within the generic top level domains.  The country code top level 
>domains are roughly the same number, and their Whois structures and 
>policies are each controlled by the individual ccTLD operator and 
>their communities.

With all due respect I find it hard to believe that Whois structures 
and policies are controlled by the respective communities.

>and think through whether we might be better served by a revised 
>system.  An expert working group was assembled and is currently 
>working through these issues.  Its output will be a consideration of 
>the issues and recommendations for further work.  It is not yet 
>clear whether the result of this effort will lead to a large change, 
>a small change, or no change at all.  What is clear is that the 
>results of this working group will become fully public, and any 
>decisions will come through our usual policy development process.

The output of that working group was lacking.  If an IETF working 
group cannot produce useful results it should be shut down.  It seems 
that ICANN's measure is "public" and "process" instead of a 
results-oriented approach.

>The IETF, ICANN, the RIRs, ISOC, W3C and other organizations have 
>all arisen within the ecosystem that accompanies the growth and 
>prevalence of the Internet.  It is natural for there to be some 
>tension, competition and rivalry among our institutions, but we have 
>all been part of the same grand enterprise, we all share the same 
>core values, and we all work toward the same goal of an open, 
>innovative, expanding Internet.

Please note that I can only speak for myself.  I don't see any 
reflection of the "functional geographic, and cultural diversity of 
the Internet  at all levels of policy development and 
decision-making" in the IETF.  The IETF does not share that core 
value.  I did not find anything in IETF documents about "depending on 
market mechanisms to promote and sustain a competitive 
environment".  I did not see anything in IETF documents about 
introducing and promoting competition".  I don't see anything in IETF 
documents about promoting decisions based on expert advice.  Someone 
in the IETF will likely correct me if I am incorrect about all this.

If there are statements in a document which appear to assert 
something but subtly imply something different, opposite, or stronger 
in the way they are made it is possible to materially affect the 
outcome by commenting about that.  The IESG could ignore the comments 
if it wishes.  That might not be a good idea though as something can 
be done about it.

ICANN's curse is having a community where people might burn it to the 
ground to get what they want.  That's possible in the IETF too.  The 
IETF's curse is having this mailing list.

I gather that everyone is aware that civil society has been somewhat 
uncivil lately.  That society has not made any significant negative 
comments about the IETF.  It has made negative comments about other 
organizations.  It is left to the reader to draw his or her conclusions.

Regards,
-sm  


From sm@resistor.net  Tue May 21 09:21:27 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6418121F97D2 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:21:27 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqXAxTPCVbKg for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:21:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D5C0B21F9731 for <ietf@ietf.org>; Tue, 21 May 2013 09:21:25 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4LGLBE1014545; Tue, 21 May 2013 09:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369153280; bh=kDTv4iLHW7kNtLcdM3/pJpDb16UMuFtVPJRLAWm/ng0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fdXvfRkpE+ybduw/EyqYSKHCQPFBlCDrrbUdj8dSO9dqnij69gCnx46q3E3+HupAi hge99/EljJ8189ckmF2ibhH4pRfrpnE8D7igwV6qvFBgqmB22daGc3c32PR6OAR+hd N6pDUYAQuNaZOHplUJ8m8HacDuq32L0s35IY4xm4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369153280; i=@resistor.net; bh=kDTv4iLHW7kNtLcdM3/pJpDb16UMuFtVPJRLAWm/ng0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zrjkIMWiq23KBuMlKVcVzEjQ12fF5nRB95mlArV0q2ftiG5mmM//H0wuVdt9TENjP 5rwakx5nHk32Ivfjo1G/9dPHIlEeQtDfffKfNgfeZaQ6uNOnDMe3BOXQGaz9mu/0c6 Id0pUo9BLZfnNhM8d3npE1eTbSU2mVphWEZgKMh0=
Message-Id: <6.2.5.6.2.20130521085128.0797e4d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 21 May 2013 09:09:37 -0700
To: Olivier MJ Crepin-Leblond <ocl@gih.com>
From: SM <sm@resistor.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <519B45B8.70306@gih.com>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com> <519B45B8.70306@gih.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: Tue, 21 May 2013 16:21:27 -0000

Hi Olivier,
At 03:00 21-05-2013, Olivier MJ Crepin-Leblond wrote:
>And you do NOT need to be part of an At-Large Structure to participate
>in the At-Large Working Groups. Membership is only needed for matters of
>voting - and since we operate by consensus, that's a rare occurrence,
>usually only kept to selection of leadership.

The voting and consensus part reminds me of the ITU.  The vote that 
happened last year has been the subject of numerous comments.

>I know this is a shameless plug but in the face of the threat posed by
>non-multi-stakeholder systems of governance, I felt a follow-up on
>Steve's post was necessary. As Steve says so eloquently, we need to all
>work toward the goal of an open, innovative, expanding Internet.

I don't see any threat.  What I see are words defined or redefined to 
suit the interests of the day.

Regards,
-sm 


From moore@network-heretics.com  Tue May 21 09:23:50 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A1821F98B7 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHEdIHMo3MYF for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:23:45 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id ADE8421F98B0 for <ietf@ietf.org>; Tue, 21 May 2013 09:23:45 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 331EE207E1; Tue, 21 May 2013 12:23:45 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute4.internal (MEProxy); Tue, 21 May 2013 12:23:45 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:from :subject:date:to; s=smtpout; bh=ktSfyl5QrCyg+mAv3G0QrTxtKS0=; b= hRUeqgG14TzSAwkSzVteoHZOMfOKhKT4ZpyE/0oaLFiIBeu30ojIHOOf5+olv4JO Nsm/PJw2tFXPzt6mrKSpTDamHqKE/DdXffHm+p/MGY9GKFwRHx2YuygDqV7T4FJf VgrDIEokbk+MYbY7isv4vTbJzOoRdoJMXdhyQhRN+no=
X-Sasl-enc: 0UOE/YevTwDkYQtl58s6XFN3oWVrlx1yap8DODz30N3j 1369153424
Received: from [21.147.197.232] (unknown [66.87.153.232]) by mail.messagingengine.com (Postfix) with ESMTPA id BC811200161; Tue, 21 May 2013 12:23:44 -0400 (EDT)
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <146962B9-CA4F-4CF1-B5C6-82B165F6E34A@vpnc.org>
In-Reply-To: <146962B9-CA4F-4CF1-B5C6-82B165F6E34A@vpnc.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <6A42DCE4-542E-4A37-9808-75D14455B444@network-heretics.com>
X-Mailer: iPhone Mail (10B329)
From: Keith Moore <moore@network-heretics.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Date: Tue, 21 May 2013 12:23:44 -0400
To: Paul Hoffman <paul.hoffman@vpnc.org>
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 16:23:51 -0000

The scope of RFC 2119 is clearly standards-track documents.  Documents that a=
ren't standards should not be worded as if they were; this is likely to caus=
e confusion about the status of the document.

Sent from my iPhone

On May 21, 2013, at 12:08 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On May 21, 2013, at 8:56 AM, Keith Moore <moore@network-heretics.com> wrot=
e:
>=20
>> 2119 language is intended to describe requirements of standards-track doc=
uments.   =20
>=20
> Can you support that statement with a reference to an RFC or an IESG state=
ment that supports it?
>=20
>> Informational documents cannot impose requirements.
>=20
> Same request.
>=20
> I don't find either statement supported by RFC 2119 or 2026, or any update=
s to the latter, but I may have missed it.
>=20
> --Paul Hoffman

From ogawa.kentaro@lab.ntt.co.jp  Mon May 20 22:14:39 2013
Return-Path: <ogawa.kentaro@lab.ntt.co.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 282D221F8F4A; Mon, 20 May 2013 22:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.71
X-Spam-Level: *
X-Spam-Status: No, score=1.71 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_25=0.6, J_CHICKENPOX_72=0.6, J_CHICKENPOX_73=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ZO2hg11+HEG; Mon, 20 May 2013 22:14:33 -0700 (PDT)
Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by ietfa.amsl.com (Postfix) with ESMTP id 7453521F8481; Mon, 20 May 2013 22:14:33 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id r4L5EOOi007791; Tue, 21 May 2013 14:14:24 +0900
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost.localdomain [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 43293E0209; Tue, 21 May 2013 14:14:24 +0900 (JST)
Received: from imail2.m.ecl.ntt.co.jp (imail2.m.ecl.ntt.co.jp [129.60.5.247]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 37402E0208; Tue, 21 May 2013 14:14:24 +0900 (JST)
Received: from [IPv6:::1] ([129.60.80.52]) by imail2.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id r4L5E2O8004376;  Tue, 21 May 2013 14:14:24 +0900
Message-ID: <519B03D4.7040007@lab.ntt.co.jp>
Date: Tue, 21 May 2013 14:19:16 +0900
From: Kentaro Ogawa <ogawa.kentaro@lab.ntt.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
Subject: Re: Gen-ART LC Review of draft-ietf-forces-interop-07
References: <8EC701FD-4258-4382-9711-B76EFBB3E1BA@nostrum.com> <BLU0-SMTP270A16556E20F95AC04C613C9AC0@phx.gbl>
In-Reply-To: <BLU0-SMTP270A16556E20F95AC04C613C9AC0@phx.gbl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
To: "Wang,Weiming" <wmwang2001@hotmail.com>
X-Mailman-Approved-At: Tue, 21 May 2013 09:27:08 -0700
Cc: IETF-Discussion list <ietf@ietf.org>, draft-ietf-forces-interop.all@tools.ietf.org, gen-art@ietf.org, forces-chairs@tools.ietf.org, wmwang@zjsu.edu.cn, 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: Tue, 21 May 2013 05:14:39 -0000

I agree with the modification points of the draft from Evangelos and 
Weiming.

Regards,
Kentaro Ogawa

-------- Original Message --------

> Hi Ben,
>
> Thank you very much for the review comments. Please see inline responses from authors of the document on the comments.
>
> Hi Sherpherd and AD,
>
> we will update a version very soon.
>
> thanks a lot.
> Weiming
>
> ----- Original Message -----
> From: "Ben Campbell" <ben@nostrum.com>
>
> 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-forces-interop-07
> Reviewer: Ben Campbell
> Review Date: 2013-05-13
> IETF LC End Date: 2013-05-13
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as an informational RFC. I have a few minor questions and editorial comments that may be worth considering prior to publication.
>
> *** Major issues:
>
> None.
>
> *** Minor issues:
>
> -- The draft mentions a couple of instances of tests that failed because of an incorrect implementation or differing encapsulation formats. Does this suggest that the specifications should be clarified? In particular, in the case of encapsulation format mismatch, should the specs include stronger requirements to be able to receive all encapsulation formats? Or should the number of options be reduced?
> [Re. by Î•Î—] The protocol provides a number of different approaches
> [Re. by Weiming] The key issue is still from the deep understanding of the protocol from implementations. I still have not seen need for any urgent change for the protocol.
>
> -- I have a mild concern that the use of origin country names for each implementation could confuse readers into thinking that the countries themselves officially participated, rather than organizations from each country.
>
>
> [Re by EH]Makes sense. We should possibly change this.
> In the beginning of section 2.2.1 where it says:
> "The University of Patras implementation joined remotely from Greece"
> Change to:
> "The University of Patras (UoP) implementation joined remotely from Greece"
> And then use UoP after that for us.
>
> [Re. by Weiming] I agree with Evangelos on this. If possible (key issue might be the text space for some figures) we may change the G to UoP, the J to NTT, the C to ZJSU ?
> Other authors, please show your views. Thanks.
>
> -- section 4.4, last paragraph:
>
> The text says that since the mentioned failures were likely the result of bugs, it doesn't indicate an interoperability problem in the specs. I have to point out that, it also doesn't prove interoperability in both directions for the particular test. It would also be worth commenting on whether the probably bugs were programming errors rather than misunderstandings of the specification.
> [Re. by Weiming] to change the whole paragraph to:
>    <t> The two test items failed. Note that Test #7 and #8 were identical to the tests, only with CE and FE implementers were exchanged. Moreover, test #12 and #13 showed that the redirect channel worked well. Therefore, it can be reasonably inferred that the problem caused the failure was from the implementations, rather than from the ForCES protocol itself or from misunderstanding of implementations on the protocol specification. Although the failure made the OSPF interoperability test incomplete, it did not show interoperability problem. More test work is needed to verify the OSPF interoperability.</t>
>
> *** Nits/editorial comments:
>
> -- The draft uses inconsistent verb tense throughout. I found this a bit confusing, as I assume the draft talks entirely about tests that have already occurred.
> [Re. by Î•Î—] We will stick with the past tense.
>
> -- IDNits points out that you have several references without explicit citations. I see that you called the references out by name in the text, but it would be better to include the citations.
> [Re. by Weiming]We will try to fix this as much as possible.
>
> -- Section 1, paragraph 6:
>
> Please expand abbreviations on first mention.
> [Re. by Weiming] Yes.
>
> -- Section 1.1:
>
> Please expand FE on first mention.
> [Re. by Weiming] Yes.
>
> -- section 2.2.2, paragraph 1: "... from China and Japan implementations..."
>
> Missing "the".
>
> Is it possible to add a reference for details on the Smartbits testing machine?
>
> -- Figure 2:
>
> Do you really want to publish the IP addresses used in an RFC? RFCs live forever...
>
> -- Section 2.2.2, paragraph after figure 2:
>
> First sentence does not parse.
>
> [Re. by Weiming] In Figure 2, changed the '124.90.146.218 (ADSL)' to ' (ADSL)'.  In Figure 3, changed the '150.140.254.110(VPN)' to '(VPN)' to avoid personal IP address in public.
>
> Section 2.2.2, paragraph after figure 2, first sentence is changed to:
> <t>CE and FE from the Greece implementation were located within the
>     University of Patras, Greece, and were connected together using LAN as
>     shown in <xref target="Figure-3"/>. Connetion to the Internet was via a VPN channel.
> </t>
> [/Re]
>
> -- Figure 3:
>
> The figure has some formatting issues, at least in the PDF version. Also, is it possible to avoid splitting the figure across the page break?
>
> [Re. by Weiming] ok, we'll try.
> [/Re]
>
> -- section 3.2, paragraph 3: "Because of system deficiency to deploy IPSec over TML in Greece,..."
>
> Phrase doesn't parse.
>
> -- section 3.2, paragraph 4: "... over IPSec channel."
>
> Missing "the".
>
> "...to have established..."
>
> to establish.
> [Re. by Weiming] The section 3.2 para.3 has been changed to:
> <t>... Because there came unfortunately a problem with the test system in Greece to deploy IPSec over TML during the test process, this test only took place between test systems in China and Japan.</t>
> Other nits are also corrected.
> thanks.
> [/Re]
> -- section 4 and subsections:
>
> It seems like some of the test descriptions in 4.X may be redundant to the previous scenario descriptions.
>
> [Re. by Weiming] previous section 3.x is the scenario description, and the 4.x related section is the test results.
>
> -- section 4.1, notes on 28 and 29:
>
> Sentence does not parse.
>
> ... notes on 30 and 31:
>
> Missing articles.
> [Re. by Weiming]The two notes (Note on test #28 and #29 and note on test #30 and #31 are vaguae.  After considerations, we decide to remove thess two notes.
> Thanks.
> [/Re.]
>
> -- section 5.1, last paragraph in list item "2.": "The interoperability test witnessed that..."
>
> The test _showed_...   [or the _testers_ witnessed...]
>
> [Re. by Weiming] modified to 'The interoperability testers witnessed that...".  Thanks.
> [/Re.]
>
> -- section 9:
>
> It would be worth mentioning that you explicitly tested for IPSec support.
>
> [Re. by Weiming] As a result, the section has been updated as:
>
>   9.  Security Considerations
>
>     Developers of ForCES FEs and CEs must take the security
>     considerations of the ForCES Framework [RFC3746]  and the ForCES
>     Protocol [RFC5810]  into account.  Also, as specified in the security
>     considerations section of the SCTP-Based TML for the ForCES Protocol
>     [RFC5811], the transport-level security has to be ensured by IPsec.Test
>     results of TML with IPsec supported have been shown in Section 4.2 of the document.
> [/Re.]
>
>



From paul.hoffman@vpnc.org  Tue May 21 09:31:13 2013
Return-Path: <paul.hoffman@vpnc.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 6FABD21F9354 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.613
X-Spam-Level: 
X-Spam-Status: No, score=-102.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1bOqfPHVeJoQ for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:31:01 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3B07421F91A0 for <ietf@ietf.org>; Tue, 21 May 2013 09:30:59 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4LGUuMN097976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 May 2013 09:30:56 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6A42DCE4-542E-4A37-9808-75D14455B444@network-heretics.com>
Date: Tue, 21 May 2013 09:30:58 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F7D929F-49E9-460B-BB17-51EC326AB52D@vpnc.org>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <146962B9-CA4F-4CF1-B5C6-82B165F6E34A@vpnc.org> <6A42DCE4-542E-4A37-9808-75D14455B444@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 16:31:16 -0000

On May 21, 2013, at 9:23 AM, Keith Moore <moore@network-heretics.com> =
wrote:

> The scope of RFC 2119 is clearly standards-track documents. =20

I'll take that as a "no". The "scope" is mentioned exactly once, in the =
abstract but not in the body of the document.=20

> Documents that aren't standards should not be worded as if they were; =
this is likely to cause confusion about the status of the document.

I'm pretty sure that you as AD approved Informational RFCs that used =
2119 language, and that this was discussed during your tenure on the =
IESG. The fact that there none of the updates to RFC 2026 even mention =
this suggests that there was not IETF consensus to the opinion.

--Paul Hoffman=

From john-ietf@jck.com  Tue May 21 09:51:47 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5B121F9731 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:51:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vK1HRea+v6DL for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 09:51:41 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C44CE21F9714 for <ietf@ietf.org>; Tue, 21 May 2013 09:51:40 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uepmj-0009oi-Et; Tue, 21 May 2013 12:51:37 -0400
Date: Tue, 21 May 2013 12:51:32 -0400
From: John C Klensin <john-ietf@jck.com>
To: joel jaeggli <joelja@bogus.com>, Joe Abley <jabley@hopcount.ca>, Keith Moore <moore@network-heretics.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
Message-ID: <82E1266FCB5D52A088145964@JcK-HP8200.jck.com>
In-Reply-To: <519B96E5.9040207@bogus.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 16:51:47 -0000

--On Tuesday, May 21, 2013 08:46 -0700 joel jaeggli
<joelja@bogus.com> wrote:

> On 5/21/13 8:06 AM, John C Klensin wrote:
>> 
>>    All I'm asking for is that, if you
>> want this as a Proposed Standard you carefully and
>> convincingly describe your design rationale.  I want that
>> both because it seems generally appropriate in this case and
>> because, if someone comes along and wants to register the
>> EUI64-with-embedding or EUI-with-48-64-switch RRTYPEs and
>> there is pushback because EUI48 and EUI64 are already
>> registered,

> It seems like we're still re-arguing the assignment of the
> rr-types.

I, at least, am not.

> It doesn't seem like future assignments are likely
> to have anymore pushback than present.

Unless you are going to join the group that says it is perfectly
ok to have multiple IETF standards-track documents that specify
conflicting ways to do almost the same thing, it seems to me
that pushback against other ways to handle EUI data is inherent
in the standards track designation.  The last time the IETF had
the argument about conflicting standards, I think there was
rough consensus that it was generally a bad idea even if some of
us thought that exceptions might occasionally be desirable.

> With respect to the question of proposed standard. What
> changes if the requested status is informational?

I don't agree with Keith that the removal of the keywords
specified in 2119 is either necessary or sufficient (nor with
the generalization that such language should never appear in
Informational documents).  Like Sam, I think that such language
may sometimes be entirely appropriate to an
informational/descriptive document although I also believe that
it should be used with care.

Since I don't have such an easy solution, answering your
question would require a paragraph-by-paragraph review of the
document, not the more overview-level reading I gave it before
participating in this thread.  Having made that proposal, I feel
obligated to do that reading --essentially an editing pass-- but
only if 

(i) you and Joe are inclined to process the document as
	Informational if the edit is satisfactory  and
	
(ii) it is understood that those edits will almost
	certainly not resolve the security and privacy concerns
	that have been raised, notably by Keith and Brian if the
	simple change to Informational does not do so.

Note that (i) is not a request for a promise or decision, only a
good-faith willingness to move in that direction.   

If I am going to do this, I'd prefer to make a pass and then
sort out residual editorial details off list with Joe and anyone
else who is significantly interested rather than trying to do
editing on this list.  If that seems reasonable and appropriate,
I can commit to getting this done within the next week, maybe
sooner, but not today.

   best,
    john


From dhc@dcrocker.net  Tue May 21 10:03:59 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D77C021F9718 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.509
X-Spam-Level: 
X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GiJFEvp72hEC for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:03:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7415421F95EE for <ietf@ietf.org>; Tue, 21 May 2013 10:03:54 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4LH3oW1010222 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 May 2013 10:03:54 -0700
Message-ID: <519BA8F3.70709@dcrocker.net>
Date: Tue, 21 May 2013 10:03:47 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com> <6.2.5.6.2.20130521033110.0ba545d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130521033110.0ba545d0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 21 May 2013 10:03:54 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 17:04:00 -0000

On 5/21/2013 8:50 AM, SM wrote:
> I gather that everyone is aware that civil society has been somewhat
> uncivil lately.  That society has not made any significant negative
> comments about the IETF.


Actually it has.  Since he's such a long-active figure in those circles, 
check out Milton Mueller's Ruling the Root, from 10 years ago.  He was 
quite critical and dismissive of the technical community, including the 
IETF:

    http://bbiw.net/musings.html#rootreviewl

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From superuser@gmail.com  Tue May 21 10:28:07 2013
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7964E21F8CE9; Tue, 21 May 2013 10:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zz5NUqZErqn7; Tue, 21 May 2013 10:28:06 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3A7C021F93C4; Tue, 21 May 2013 10:28:06 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id e11so534095wgh.14 for <multiple recipients>; Tue, 21 May 2013 10:28:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9KdH/kIG6ilwdob2jM7TY0AjGSALHKM9qQ1hFGic/4E=; b=PnKOSiirnPFrRO9DF+vgqGcyYSErh/RQN2NVe1E0eaR/Ve+WeIGK7blbJ5ipe40cTR nkClMBGVuSlQ1aFlW+Z+tM3PVmvLequRY+jUyLJT/xk1pBc/GEPpWtA5S/iUj+Qmsl2o GS9Rvjs+xt++JdJD/8Qc9Rz8tlSDb4b/VdPeqb1RDzWrIOmlqwLVPHiJp10FkXt/RWqU cuYlpoGEYbLPFRYYIb3qE768vOn0asV+1vKktmVtUIicUATDhLIbHpOPsA2209HPHNce LrpCvRmWcKL2adAvf+69OKzxcESBLhQi/p3qt8fJ/Gkn4xrL1XYmBLS2OOwHZqzgdnq2 60kQ==
MIME-Version: 1.0
X-Received: by 10.180.189.41 with SMTP id gf9mr6888738wic.32.1369157285284; Tue, 21 May 2013 10:28:05 -0700 (PDT)
Received: by 10.180.14.34 with HTTP; Tue, 21 May 2013 10:28:05 -0700 (PDT)
In-Reply-To: <519AD17D.8040501@network-heretics.com>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <519AD17D.8040501@network-heretics.com>
Date: Tue, 21 May 2013 10:28:05 -0700
Message-ID: <CAL0qLwbgZ+uews3xLVyU0nGzCDOvQ_rwHD9vfN7fiO-A2uS4ww@mail.gmail.com>
Subject: Re: Deployment of standards compliant nameservers
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=001a11c34830a1929704dd3dc525
Cc: The IESG <iesg@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 17:28:07 -0000

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

On Mon, May 20, 2013 at 6:44 PM, Keith Moore <moore@network-heretics.com>wrote:

> p.s. I wonder if the problem you describe might at least partially be
> caused by DNS proxies and interception proxies, including but not limited
> to those incorporated in consumer-grade routers.
>
>
>
Given the funny things some firewalls used to do to SMTP sessions, I
suggest tossing firewalls into that list.

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

<div dir=3D"ltr">On Mon, May 20, 2013 at 6:44 PM, Keith Moore <span dir=3D"=
ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" target=3D"_blank">mo=
ore@network-heretics.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra=
"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">p.s. I wonder if the problem you describe mi=
ght at least partially be caused by DNS proxies and interception proxies, i=
ncluding but not limited to those incorporated in consumer-grade routers.<d=
iv class=3D"HOEnZb">
<div class=3D"h5"><br><br></div></div></blockquote><div><br></div><div>Give=
n the funny things some firewalls used to do to SMTP sessions, I suggest to=
ssing firewalls into that list. <br></div></div><br></div></div>

--001a11c34830a1929704dd3dc525--

From john-ietf@jck.com  Tue May 21 10:33:06 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E200B21F9346 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CRBivpbMLzX for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:33:01 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E24FB21F925A for <ietf@ietf.org>; Tue, 21 May 2013 10:33:00 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UeqQl-0009rl-1h; Tue, 21 May 2013 13:32:59 -0400
Date: Tue, 21 May 2013 13:32:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Joe Abley <jabley@hopcount.ca>
Subject: Proposed Standards and Expert Review (was: Re: Last Call <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard))
Message-ID: <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com>
In-Reply-To: <m24ndwgxwo.wl%randy@psg.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.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: Tue, 21 May 2013 17:33:07 -0000

(Changing Subject lines -- this is about a set of general
principles that might affect this document, not about the
document)

--On Tuesday, May 21, 2013 22:23 +0700 Randy Bush
<randy@psg.com> wrote:

> joe,
> 
> i have read the draft.  if published, i would prefer it as a
> proposed standard as it does specify protocol data objects.

I would generally have that preference too.  But it seems to me
that the combination of

	-- RRTYPEs (and a bunch of other protocol data objects
	associated with different protocols) are allocated on
	expert review
		
	-- The fact that those protocol data objects have
	already been allocated is used to preempt IETF
	consideration of issues that normally go into Standards
	Track documents, including the criteria for Proposed
	Standards in 2026.

is fundamentally bad news for reasons that have little to do
with this document or RRTYPEs specifically.  If the combination
is allowed, it provides an attack vector on the standards
process itself because someone can get a parameter approved on
the basis of ability to fill out a template and then insist that
the IETF approve and standardize it simply because it is
registered and in use.    That would turn allocation of
parameters by expert review (and some related issues connected
to "deployed therefore it is ok" -- watch for another note) into
a rather large back door for standardization that could bypass
the 2026 and other less formal criteria, the IETF's
historically-strong position on change control, and so on.

These are not new issues and we have historically dealt with
them in a number of ways that don't require moving away from
liberal allocation policies and toward "the IETF is in charge of
the Internet and has to approve everything".  For example, we
have decided that media types don't have to be standardized
although certain types of names do.  People then get to choose
between easy and quick registration and standardization, but
don't get to use the first to leverage the second.  One could
argue that the pre-IETF (and very early) division between
"system" and "user" port numbers reflects the same sort of
distinction between a high standard for justification and
documentation and much lower ones.

It is possible (although I'm not convinced) that this discussion
should suggest some tuning of the allocation model for RRTYPEs.
Probably that model is ok and we just need to figure out clearer
ways to say "if you want standards track, don't get an
allocation first and try to use that as justification because
you will get a real Last Call anyway and everyone will end up a
little irritated".   Or something else may be appropriate.  But
it seems to me that, as soon as one wants to say "all protocol
parameters or other data values should be standardized" then
allocation models based on expert review are inappropriate.  For
the RRTYPE case, that issue should, IMO, have been pushed with
the relevant WG when the decision to allow expert review was
made (and, again, IMO, that cure would be worse than the disease
because it would indirectly drive more folks toward overloading
of TXT and other existing types).

best,
    john





> 
> < where you goin' with that gun in your hand? >
> i am not at all sanguine about the issues raised in the in sec
> cons.  i accept that NTRE038D may have asked that these be in
> the dns, but seems to me that it is ill advised and some other
> means to meet their actual needs might be found.  e.g. what's
> the matter with logs?





From joelja@bogus.com  Tue May 21 10:35:50 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9161F21F9679 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:35:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.626
X-Spam-Level: 
X-Spam-Status: No, score=-102.626 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fT6elEkdq6Ue for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:35:50 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id ED2C821F96CB for <ietf@ietf.org>; Tue, 21 May 2013 10:35:49 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4LHZlvQ001388 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 21 May 2013 17:35:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <519BB06D.1050804@bogus.com>
Date: Tue, 21 May 2013 10:35:41 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>, Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <D17764B0-B627-4DC2-A1B4-26898655E9EC@hopcount.ca> <519B9A8F.70701@network-heretics.com>
In-Reply-To: <519B9A8F.70701@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]); Tue, 21 May 2013 17:35:47 +0000 (UTC)
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, 21 May 2013 17:35:50 -0000

On 5/21/13 9:02 AM, Keith Moore wrote:
> On 05/21/2013 11:57 AM, Joe Abley wrote:
>> On 2013-05-21, at 11:56, Keith Moore <moore@network-heretics.com> wrote:
>>
>>> 2119 language is intended to describe requirements of 
>>> standards-track documents.    Informational documents cannot impose 
>>> requirements.
>> Then I think we've just identified a reason why this document should 
>> be on the standards track.
>>
> Actually I think that what we need is a BCP that says that DNS is not 
> intended, not designed, and SHOULD NOT be used for dissemination of 
> any information that is not deemed acceptable for widespread public 
> distribution.
The basically rules out every internal split  horizon use of DNS in 
existence.

scope matters for this application just as it does for any zone you 
shouldn't be exposing to the outside world.
>    Neither the DNS protocol nor DNS implementations are designed to 
> meet the security requirements of such applications, and DNS is too 
> widely deployed to change that.
> Keith
>


From moore@network-heretics.com  Tue May 21 10:41:16 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E270221F9763 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.641
X-Spam-Level: 
X-Spam-Status: No, score=-3.641 tagged_above=-999 required=5 tests=[AWL=-0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6KxrJw8-a12 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 10:41:11 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id BB84121F9778 for <ietf@ietf.org>; Tue, 21 May 2013 10:41:11 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2EC232148B; Tue, 21 May 2013 13:41:10 -0400 (EDT)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 21 May 2013 13:41:11 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=0TgboHyQkkU3PHS2AiHN6r n7tHY=; b=PnLUY5VxIpwzZkOMzYrBzbLPYazqMiJKNj24uLHjiHjX+nOxh0tbYc C1J3E0Ai3zPl5IioS63klwCe1PL2rYcvC/4EZncfuuYRCvVuDpNPRkZAHB908UaL Ercd93TcPC28yjIS6NevYTmKz74kfCp04ARqAFabQkrPrA0QTGDpM=
X-Sasl-enc: hSxBjSpQ6bz9jo+0r6qxT78iXHznxG2oLMvk3ioP5Ngu 1369158070
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id ECBF9C80004; Tue, 21 May 2013 13:41:09 -0400 (EDT)
Message-ID: <519BB1A7.6060607@network-heretics.com>
Date: Tue, 21 May 2013 13:40:55 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<519A82B9.7090305@gmail.com>	<519B785E.7060208@network-heretics.com>	<BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <D17764B0-B627-4DC2-A1B4-26898655E9EC@hopcount.ca> <519B9A8F.70701@network-heretics.com> <519BB06D.1050804@bogus.com>
In-Reply-To: <519BB06D.1050804@bogus.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: Tue, 21 May 2013 17:41:17 -0000

On 05/21/2013 01:35 PM, joel jaeggli wrote:
> On 5/21/13 9:02 AM, Keith Moore wrote:
>> On 05/21/2013 11:57 AM, Joe Abley wrote:
>>> On 2013-05-21, at 11:56, Keith Moore <moore@network-heretics.com> 
>>> wrote:
>>>
>>>> 2119 language is intended to describe requirements of 
>>>> standards-track documents.    Informational documents cannot impose 
>>>> requirements.
>>> Then I think we've just identified a reason why this document should 
>>> be on the standards track.
>>>
>> Actually I think that what we need is a BCP that says that DNS is not 
>> intended, not designed, and SHOULD NOT be used for dissemination of 
>> any information that is not deemed acceptable for widespread public 
>> distribution.
> The basically rules out every internal split  horizon use of DNS in 
> existence.

Indeed.  Things have gotten way too far out of hand.  Again, DNS was not 
engineered for this purpose, and the hacks that people have employed 
like split-horizon DNS do not and cannot fix the underlying problems.

Keith


From moore@network-heretics.com  Tue May 21 11:54:03 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C71721F96CB for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 11:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.639
X-Spam-Level: 
X-Spam-Status: No, score=-3.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIxD85q1RouO for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 11:53:58 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 3F08221F9588 for <ietf@ietf.org>; Tue, 21 May 2013 11:53:58 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 75DA921590; Tue, 21 May 2013 14:53:55 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 21 May 2013 14:53:56 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=iBQQMypM99R3KxXm7lAbOW 9TbSs=; b=CQbPw7PGRtsjGKR+5iaV7NvM9/Gwm3WtQdzs2sll83sV2pCVhB0H1S c9BnxcWceZKT8P9G6Qs4vO5ueEumW+RZmKrIq0QPuw2xGqUlxLok5ax057Uea80F YlKVB+y8C/Oo7AXLUwABIzZExCn+tBB4VRTE6xz31O1A0gMPEkA4A=
X-Sasl-enc: vbVmFG5B5QqMWz0NC5JhQNAKfoUF55xu7tG1nZnGP3sb 1369162435
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id DDD17200188; Tue, 21 May 2013 14:53:54 -0400 (EDT)
Message-ID: <519BC2B4.1070002@network-heretics.com>
Date: Tue, 21 May 2013 14:53:40 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca> <519B991D.4040804@network-heretics.com> <146962B9-CA4F-4CF1-B5C6-82B165F6E34A@vpnc.org> <6A42DCE4-542E-4A37-9808-75D14455B444@network-heretics.com> <2F7D929F-49E9-460B-BB17-51EC326AB52D@vpnc.org>
In-Reply-To: <2F7D929F-49E9-460B-BB17-51EC326AB52D@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 18:54:03 -0000

On 05/21/2013 12:30 PM, Paul Hoffman wrote:
>> Documents that aren't standards should not be worded as if they were; this is likely to cause confusion about the status of the document.
> I'm pretty sure that you as AD approved Informational RFCs that used 2119 language, and that this was discussed during your tenure on the IESG.
My recollection is that other ADs were the ones who insisted that 2119 
language not be used for Informational documents.   I was more concerned 
about other things, but I could see their point.

If the document is going to be published as Informational, rewording the 
document to remove 2119 language is my recommendation.  But it's not 
something I feel like making a huge fuss over.

If the document is still being considered as Proposed Standard, 2119 
language would be appropriate.   But I believe that this RRtype is 
fundamentally inappropriate for the standards track.

Keith


From moore@network-heretics.com  Tue May 21 12:08:44 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B062B11E80AE for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:08:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.637
X-Spam-Level: 
X-Spam-Status: No, score=-3.637 tagged_above=-999 required=5 tests=[AWL=-0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPeQdMtPg2WW for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:08:39 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA9F21F92E7 for <ietf@ietf.org>; Tue, 21 May 2013 12:08:39 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id AC06721845; Tue, 21 May 2013 15:08:37 -0400 (EDT)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 21 May 2013 15:08:37 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=cYIuyfMcSWgT7FIxKwYeGE W+joo=; b=aSJUFTu+cSO7t2Mxl9Hx7xhvfgTYJCOxBtGRE0FjjjZrg4lK5O31KR 6GTxlRMfUblscIpPhA2yiGEx73k8ChgU19mqUwssXXla9ZJeLrEKMwx84uG5TvQN uHlhvK/sqCrEunClo+guTquQlsQi1UQw24yGQnL5vWFXEmMEA0GCU=
X-Sasl-enc: ZSBn4t1SoeaR0IFuurcXBja6h+UqxvWO84S8Rs7QY9lz 1369163317
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id D425720010A; Tue, 21 May 2013 15:08:36 -0400 (EDT)
Message-ID: <519BC626.7030006@network-heretics.com>
Date: Tue, 21 May 2013 15:08:22 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Proposed Standards and Expert Review
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com>
In-Reply-To: <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 19:08:44 -0000

Without responding in detail to John's note, I'll say that I agree 
substantially with the notion that the fact that someone manages to get 
a protocol name or number registered, should not be any kind of 
justification for standardization of a document that describes use of 
that name or number.

(For that matter, just because a document describes "protocol data 
objects" is also not a justification for standardization of that document.)

More generally, IETF standardization should not be a rubber stamp.   And 
to the extent that people have that notion, we would do well to 
discourage it.

Keith


From jabley@hopcount.ca  Tue May 21 12:24:57 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D193821F9104 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gE-o48rYwvFx for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:24:52 -0700 (PDT)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by ietfa.amsl.com (Postfix) with ESMTP id CCA8221F911B for <ietf@ietf.org>; Tue, 21 May 2013 12:24:47 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kl13so1039986pab.20 for <ietf@ietf.org>; Tue, 21 May 2013 12:24:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=jkcm292+u78EmbKAGX/J+MB8uDKshlgJwhoPaKe9BSo=; b=d4IT/4dKes7Qu86img/Yoe31100QedzDKgJg9xnvcYp2rG09OeAAAA+nyaiy6ifuwX CdBAAKuvWWC5yQMnOfLnFKncju8W3vovHfZ13FjPskVShPUGwGHowcd8n/0J5z6RJ6nw 1ZOz6qWYCDa5mhlw7BN0kB8zJHu+9Hr9p2FeM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=jkcm292+u78EmbKAGX/J+MB8uDKshlgJwhoPaKe9BSo=; b=RoqmYTRWmkYthwDg06HkpCjvO6FNLMqCzooXNqpeBMAz/5jdkdsR2ftgyE4T8NpkCQ L4b7HPMc1ZTrSEfRWkHlLvumRKTNip+Snfzx/ZmI9nNWG8n85V6m/NhcgpZge3/zY3Rq gvQDgQim6woG3MqX8PZbMLEJy6OxoMFaaK8JVYDukl4lKUV2aPIQIjBAhDlZ5w7iW8oW d6GLsOBi+9dJ/8mx6Ne5r02+0Uyeh0HyZWhwHpn0sAmQ/UyHKCnjXfsgWeyvgK15lAhy lG50QMrEG6AYFAMSQKOtaRR8mP8uGlz5oJiLcNh99SbG5b0ffhjnDOC1zFtUgM7XkqgM JxvQ==
X-Received: by 10.66.226.233 with SMTP id rv9mr2800941pac.155.1369164287167; Tue, 21 May 2013 12:24:47 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:8ab:501b:f159:f1a8? ([2001:4900:1042:100:8ab:501b:f159:f1a8]) by mx.google.com with ESMTPSA id at1sm3837470pbc.10.2013.05.21.12.24.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 21 May 2013 12:24:46 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Proposed Standards and Expert Review
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <519BC626.7030006@network-heretics.com>
Date: Tue, 21 May 2013 15:24:42 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <255F3EAB-1DAD-457A-8081-AD166951482A@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com> <519BC626.7030006@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQliDf7+fkI4FSXpE1aV4BVoOkqafPS23sh042O4NUxrBaeMKaJjBj1LLgeY/q8sUwudybdp
Cc: John C Klensin <john-ietf@jck.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 19:24:57 -0000

On 2013-05-21, at 15:08, Keith Moore <moore@network-heretics.com> wrote:

> Without responding in detail to John's note, I'll say that I agree =
substantially with the notion that the fact that someone manages to get =
a protocol name or number registered, should not be any kind of =
justification for standardization of a document that describes use of =
that name or number.

If such a justification was inferred in my document, the problem is =
presumably my unclear language because no such justification was =
intended.

(I am very happy for my document to be re-pointed at informational, =
incidentally, for which wheels are in motion. I will likely leave the =
normative language in, in the interests of improved interop, and see how =
far I get.)

Code-points in the RRType registry are assigned by expert review (not =
simply by "filling out a template" as someone suggested earlier). If the =
suggestion is that the standards track is not available for any work =
that involves a code point that was assigned early, then I wonder what =
process is imagined for any future DNS work which aims at the standards =
track.


Joe


From dougb@dougbarton.us  Tue May 21 12:27:10 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6950111E80D9 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02M+NSEkMy96 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:27:06 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 2F16411E80D2 for <ietf@ietf.org>; Tue, 21 May 2013 12:27:06 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id A148A22B0C for <ietf@ietf.org>; Tue, 21 May 2013 19:27:05 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1369164425; bh=tY6FpH58s17uEM6MpPhvAyNCUskNryE0ZvIP3m5/JHw=; h=Date:From:To:Subject:References:In-Reply-To; b=SzYqAfUIj5wLGq+7UsLhpXFTW5bPpJ+/nOsm9N5AToAfy18ML4V8BMgFy7umoibx4 yzhPgykeVFEGoWX3YSHvWb8WegqFMbtHqrrYEXK4cgAILwjAJ9aHhkWHGhHhrmp8YE zYgJKm66NUK2cUoxT6j6iXJju7H89/gd34YIOof4=
Message-ID: <519BCA89.50702@dougbarton.us>
Date: Tue, 21 May 2013 12:27:05 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Proposed Standards and Expert Review
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com> <519BC626.7030006@network-heretics.com>
In-Reply-To: <519BC626.7030006@network-heretics.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 19:27:10 -0000

On 05/21/2013 12:08 PM, Keith Moore wrote:
> Without responding in detail to John's note, I'll say that I agree
> substantially with the notion that the fact that someone manages to get
> a protocol name or number registered, should not be any kind of
> justification for standardization of a document that describes use of
> that name or number.
>
> (For that matter, just because a document describes "protocol data
> objects" is also not a justification for standardization of that document.)
>
> More generally, IETF standardization should not be a rubber stamp.   And
> to the extent that people have that notion, we would do well to
> discourage it.

John has raised some excellent points. I tried to raise similar concerns 
on dnsext, albeit much more clumsily, and was told "the code points are 
already assigned, so go away."

There needs to be a happy medium, where getting new RRtypes assigned is 
not as difficult as it used to be, but some thought is given to whether 
or not the proposed solution is the best one, or even a good idea at 
all. It's a hard problem to solve, and I don't claim to know the right 
answer.

Doug


From ogud@ogud.com  Tue May 21 12:42:19 2013
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC3921F940B for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kgUKichzWC2w for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:42:14 -0700 (PDT)
Received: from smtp110.ord1c.emailsrvr.com (smtp110.ord1c.emailsrvr.com [108.166.43.110]) by ietfa.amsl.com (Postfix) with ESMTP id 6190D11E810E for <ietf@ietf.org>; Tue, 21 May 2013 12:42:14 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7F7BE98149; Tue, 21 May 2013 15:42:13 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 8B35E980CC;  Tue, 21 May 2013 15:42:10 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Proposed Standards and Expert Review (was: Re: Last Call <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com>
Date: Tue, 21 May 2013 15:42:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE7F48DE-CE92-4A92-9EB2-F72E9DEED8D9@ogud.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 19:42:19 -0000

On May 21, 2013, at 1:32 PM, John C Klensin <john-ietf@jck.com> wrote:

> (Changing Subject lines -- this is about a set of general
> principles that might affect this document, not about the
> document)
>=20
> --On Tuesday, May 21, 2013 22:23 +0700 Randy Bush
> <randy@psg.com> wrote:
>=20
>> joe,
>>=20
>> i have read the draft.  if published, i would prefer it as a
>> proposed standard as it does specify protocol data objects.
>=20
> I would generally have that preference too.  But it seems to me
> that the combination of
>=20
> 	-- RRTYPEs (and a bunch of other protocol data objects
> 	associated with different protocols) are allocated on
> 	expert review
> 	=09
> 	-- The fact that those protocol data objects have
> 	already been allocated is used to preempt IETF
> 	consideration of issues that normally go into Standards
> 	Track documents, including the criteria for Proposed
> 	Standards in 2026.
>=20
> is fundamentally bad news for reasons that have little to do
> with this document or RRTYPEs specifically.  If the combination
> is allowed, it provides an attack vector on the standards
> process itself because someone can get a parameter approved on
> the basis of ability to fill out a template and then insist that
> the IETF approve and standardize it simply because it is
> registered and in use.    That would turn allocation of
> parameters by expert review (and some related issues connected
> to "deployed therefore it is ok" -- watch for another note) into
> a rather large back door for standardization that could bypass
> the 2026 and other less formal criteria, the IETF's
> historically-strong position on change control, and so on.

John,=20
There are basically 3 different kinds of DNS RRtypes,=20
	- types that affect the behavior of the DNS protocol and are =
cached by resolvers,=20
	- types that have DATA and are cached by resolvers=20
	- meta Types that may affect processing but are not cached.=20

DNSEXT in its wisdom has deemed the second group to be "harmless" as far =
as
DNS is concerned and getting code to store data in DNS is a good thing, =
thus it is easy to get=20
it. Getting code for the other classes requires IETF standards action.=20=


Documents that describe the DATA types use are encouraged to be =
published as=20
Informational or some other stable reference.=20

>=20
> These are not new issues and we have historically dealt with
> them in a number of ways that don't require moving away from
> liberal allocation policies and toward "the IETF is in charge of
> the Internet and has to approve everything".  For example, we
> have decided that media types don't have to be standardized
> although certain types of names do.  People then get to choose
> between easy and quick registration and standardization, but
> don't get to use the first to leverage the second.  One could
> argue that the pre-IETF (and very early) division between
> "system" and "user" port numbers reflects the same sort of
> distinction between a high standard for justification and
> documentation and much lower ones.
>=20
As I explained DNS RRtype allocation has this separation.=20

> It is possible (although I'm not convinced) that this discussion
> should suggest some tuning of the allocation model for RRTYPEs.
> Probably that model is ok and we just need to figure out clearer
> ways to say "if you want standards track, don't get an
> allocation first and try to use that as justification because
> you will get a real Last Call anyway and everyone will end up a
> little irritated".   Or something else may be appropriate.  But
> it seems to me that, as soon as one wants to say "all protocol
> parameters or other data values should be standardized" then
> allocation models based on expert review are inappropriate.  For
> the RRTYPE case, that issue should, IMO, have been pushed with
> the relevant WG when the decision to allow expert review was
> made (and, again, IMO, that cure would be worse than the disease
> because it would indirectly drive more folks toward overloading
> of TXT and other existing types).

If the expert thinks an application crosses from DATA space to Control =
space=20
he is expected to reject the application and ask for clarification.=20

So far nothing has shown up that crosses this boundary, so there is no =
problem.=20
I will go as far as saying why should there be higher bar for getting a =
DNS RRTYPE than MIME media type ?=20

	Olafur



From sm@resistor.net  Tue May 21 12:54:13 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3B611E811B for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ukMQS0NsVfAJ for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 12:54:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CCB11E80FB for <ietf@ietf.org>; Tue, 21 May 2013 12:54:11 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4LJrv9n021341; Tue, 21 May 2013 12:54:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369166042; bh=e2lYjPEAJhNTOxIXKZOn3bcumbA38jzaNzVn+OUbTAQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lvPChiHFAlEbxRGPj7/E0ELoLg5OI1tGpDULKjxJ5sN6XzaNOdeuKRpFveVy+1f1i ufAF2EIHov+SuSruVoiKGqvraTY53opMG4YNeRJe2S+QmKlLow+/mBuGTT9IOavXHP TfgqDmhmk0w7MED99+8sqPuPepBkmbyCocNs1CwQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369166042; i=@resistor.net; bh=e2lYjPEAJhNTOxIXKZOn3bcumbA38jzaNzVn+OUbTAQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KL/7DpXqQAyxQMb9ryHr9Rr++GjlQS4qjBpraRxLPdhybFmjQbVlInx2jiimjv0Jc 74L98YJckPcT1pcjzkvXpveH8JhxWnaOWB87/40tIQTxiBHo5d2nmktqT16uYL5yip Uwx2Ergco5yrhC4YUes2r4IVb1Dq7V2gLGvgP6yA=
Message-Id: <6.2.5.6.2.20130521121114.0c4f8ef8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 21 May 2013 12:51:25 -0700
To: dcrocker@bbiw.net
From: SM <sm@resistor.net>
Subject: Re: IETF, ICANN and Whois (Was Re: Last Call: <draft-housley-rfc2050bis-01.txt> (The Internet Numbers Registry System) to Informational RFC)
In-Reply-To: <519BA8F3.70709@dcrocker.net>
References: <20130416230618.31243.43068.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130510103049.0ca25050@resistor.net> <D8079A6C-3A65-433E-8D12-5B53E645E48E@virtualized.org> <6.2.5.6.2.20130510231552.0df99d90@resistor.net> <51927C4B.6090400@umn.edu> <5607B91D-161D-48DE-82E0-F19E5AA43570@virtualized.org> <51941F5F.7060201@umn.edu> <805538F3-7A28-4AE7-8185-2E68C50415BD@istaff.org> <E4536428-194D-4C10-BF7B-24BF1D18DAC0@shinkuro.com> <6.2.5.6.2.20130521033110.0ba545d0@resistor.net> <519BA8F3.70709@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 19:54:13 -0000

Hi Dave,
At 10:03 21-05-2013, Dave Crocker wrote:
>Actually it has.  Since he's such a long-active figure in those 
>circles, check out Milton Mueller's Ruling the Root, from 10 years 
>ago.  He was quite critical and dismissive of the technical 
>community, including the IETF:

Thanks for the reference.  I have read some messages [1][2] from the 
person.  I don't recall reading the book.  As the subject line 
mentions Whois I found something to read [3].

Regards,
-sm

1. http://lists.arin.net/pipermail/arin-ppml/2012-April/024498.html
2. http://lists.ripe.net/pipermail/address-policy-wg/2012-April/006888.html
3. 
http://www.mendeley.com/download/public/777611/2362103122/da394283f86f68aa168abaf59d919f78d7c8f2b8/dl.pdf


From ben@nostrum.com  Tue May 21 13:34:10 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D5F11E80FA; Tue, 21 May 2013 13:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level: 
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0EUfIK8XOqq7; Tue, 21 May 2013 13:34:09 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5448911E80DE; Tue, 21 May 2013 13:34:08 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4LKXlaU006208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 May 2013 15:33:48 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: Gen-ART LC Review of draft-ietf-forces-interop-07
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=utf-8
From: Ben Campbell <ben@nostrum.com>
X-Priority: 3
In-Reply-To: <BLU0-SMTP270A16556E20F95AC04C613C9AC0@phx.gbl>
Date: Tue, 21 May 2013 15:33:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3BEFC69D-7959-4549-997B-113A53C30637@nostrum.com>
References: <8EC701FD-4258-4382-9711-B76EFBB3E1BA@nostrum.com> <BLU0-SMTP270A16556E20F95AC04C613C9AC0@phx.gbl>
To: "Wang,Weiming" <wmwang2001@hotmail.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: IETF-Discussion list <ietf@ietf.org>, draft-ietf-forces-interop.all@tools.ietf.org, gen-art@ietf.org, forces-chairs@tools.ietf.org, wmwang@zjsu.edu.cn, 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: Tue, 21 May 2013 20:34:10 -0000

Thanks for the response. Comments inline. I removed sections for which I =
have no further comment.

Thanks!

Ben.

On May 16, 2013, at 10:19 PM, "Wang,Weiming" <wmwang2001@hotmail.com> =
wrote:
>=20

[...]

> -- The draft mentions a couple of instances of tests that failed =
because of an incorrect implementation or differing encapsulation =
formats. Does this suggest that the specifications should be clarified? =
In particular, in the case of encapsulation format mismatch, should the =
specs include stronger requirements to be able to receive all =
encapsulation formats? Or should the number of options be reduced?
> [Re. by =CE=95=CE=97] The protocol provides a number of different =
approaches=20
> [Re. by Weiming] The key issue is still from the deep understanding of =
the protocol from implementations. I still have not seen need for any =
urgent change for the protocol.=20

I don't have enough knowledge of the protocol to form a specific =
opinion, but it's been my experience in other areas that when =
implementors interpret things differently, there's often room for =
clarification, even if the text is formally correct. I agree it doesn't =
imply an urgent need, but would it be worth one or more errata?

[...]


> -- section 4.4, last paragraph:
>=20
> The text says that since the mentioned failures were likely the result =
of bugs, it doesn't indicate an interoperability problem in the specs. I =
have to point out that, it also doesn't prove interoperability in both =
directions for the particular test. It would also be worth commenting on =
whether the probably bugs were programming errors rather than =
misunderstandings of the specification.
> [Re. by Weiming] to change the whole paragraph to:
>  <t> The two test items failed. Note that Test #7 and #8 were =
identical to the tests, only with CE and FE implementers were exchanged. =
Moreover, test #12 and #13 showed that the redirect channel worked well. =
Therefore, it can be reasonably inferred that the problem caused the =
failure was from the implementations, rather than from the ForCES =
protocol itself or from misunderstanding of implementations on the =
protocol specification. Although the failure made the OSPF =
interoperability test incomplete, it did not show interoperability =
problem. More test work is needed to verify the OSPF =
interoperability.</t>

Works for me, thanks!

[...]


[Re. by Weiming] The section 3.2 para.3 has been changed to:=20
> <t>... Because there came unfortunately a problem with the test system =
in Greece to deploy IPSec over TML during the test process, this test =
only took place between test systems in China and Japan.</t>

The sentence is still hard to parse. Do you mean the following?

"Because an unfortunate problem with the test system in Greece prevented =
the deployment of IPSec over TML, this test only took place between the =
test systems in China and Japan."

[...]


From randy@psg.com  Tue May 21 13:34:56 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A06021F93E5 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 13:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.206
X-Spam-Level: 
X-Spam-Status: No, score=-2.206 tagged_above=-999 required=5 tests=[AWL=-0.207, BAYES_00=-2.599, J_CHICKENPOX_21=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUn2CgQKuZEV for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 13:34:55 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B6CAD21F93E1 for <ietf@ietf.org>; Tue, 21 May 2013 13:34:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UetGg-000Jji-Jr; Tue, 21 May 2013 20:34:46 +0000
Date: Wed, 22 May 2013 03:34:44 +0700
Message-ID: <m2zjvof4wr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Proposed Standards and Expert Review
In-Reply-To: <519BC626.7030006@network-heretics.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com> <519BC626.7030006@network-heretics.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 Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 May 2013 20:34:56 -0000

> Without responding in detail to John's note, I'll say that I agree 
> substantially with the notion that the fact that someone manages to get 
> a protocol name or number registered, should not be any kind of 
> justification for standardization of a document that describes use of 
> that name or number.
> 
> (For that matter, just because a document describes "protocol data 
> objects" is also not a justification for standardization of that document.)
> 
> More generally, IETF standardization should not be a rubber stamp.   And 
> to the extent that people have that notion, we would do well to 
> discourage it.

please leave me off the cc:s of your deep discussions of process and who
has the prerogative to do what.

i am merely reviewing the draft for content, not drm and ietf sausage.

randy

From john-ietf@jck.com  Tue May 21 13:51:25 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D0261F0D23 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 13:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZbcdOIDrA57 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 13:51:15 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 557B91F0D2D for <ietf@ietf.org>; Tue, 21 May 2013 13:51:15 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UetWZ-000A6G-08; Tue, 21 May 2013 16:51:11 -0400
Date: Tue, 21 May 2013 16:51:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Proposed Standards and Expert Review (was: Re: Last Call <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard))
Message-ID: <CFEC40E9985AA5EE5071A4A7@JcK-HP8200.jck.com>
In-Reply-To: <BE7F48DE-CE92-4A92-9EB2-F72E9DEED8D9@ogud.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com> <BE7F48DE-CE92-4A92-9EB2-F72E9DEED8D9@ogud.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: Tue, 21 May 2013 20:51:25 -0000

--On Tuesday, May 21, 2013 15:42 -0400 Olafur Gudmundsson
<ogud@ogud.com> wrote:

>...
> John, 
> There are basically 3 different kinds of DNS RRtypes, 
> 	- types that affect the behavior of the DNS protocol and are
> cached by resolvers,
>  - types that have DATA and are cached by resolvers 
> 	- meta Types that may affect processing but are not cached. 
> 
> DNSEXT in its wisdom has deemed the second group to be
> "harmless" as far as DNS is concerned and getting code to
> store data in DNS is a good thing, thus it is easy to get  it.
> Getting code for the other classes requires IETF standards
> action. 

Seems perfectly reasonable

> Documents that describe the DATA types use are encouraged to
> be published as  Informational or some other stable reference. 

Reasonable too.  My problem here, which I hope was clear from
the note from which you quoted, is that a request/document in
the second category was proposed for Standards Track and then
that comments that would be entirely appropriate for a Last Call
on a Standards Track document were essentially rejected on the
grounds that they would require changes to already-registered
RRTYPEs.

>> These are not new issues and we have historically dealt with
>> them in a number of ways that don't require moving away from
>> liberal allocation policies and toward "the IETF is in charge
>> of the Internet and has to approve everything".  For example,
>> we have decided that media types don't have to be standardized
>> although certain types of names do.  People then get to choose
>> between easy and quick registration and standardization, but
>> don't get to use the first to leverage the second.  One could
>> argue that the pre-IETF (and very early) division between
>> "system" and "user" port numbers reflects the same sort of
>> distinction between a high standard for justification and
>> documentation and much lower ones.
>> 
> As I explained DNS RRtype allocation has this separation. 

But the request for publication in the Standards Track violates
it.

>> It is possible (although I'm not convinced) that this
>> discussion should suggest some tuning of the allocation model
>> for RRTYPEs. Probably that model is ok and we just need to
>> figure out clearer ways to say "if you want standards track,
>> don't get an allocation first and try to use that as
>> justification because you will get a real Last Call anyway
>> and everyone will end up a little irritated".   Or something
>> else may be appropriate.  But it seems to me that, as soon as
>> one wants to say "all protocol parameters or other data
>> values should be standardized" then allocation models based
>> on expert review are inappropriate.  For the RRTYPE case,
>> that issue should, IMO, have been pushed with the relevant WG
>> when the decision to allow expert review was made (and,
>> again, IMO, that cure would be worse than the disease because
>> it would indirectly drive more folks toward overloading of
>> TXT and other existing types).
> 
> If the expert thinks an application crosses from DATA space to
> Control space  he is expected to reject the application and
> ask for clarification. 

We are agreed that isn't an issue here.

> So far nothing has shown up that crosses this boundary, so
> there is no problem.  I will go as far as saying why should
> there be higher bar for getting a DNS RRTYPE than MIME media
> type ? 

With the understanding that I don't think it has anything to do
with this situation, one could justify a different (and maybe
higher) bar in two ways.  First, the media type names are
structured so that, a few historical exceptions aside, one can
tell what category they are in by looking at the names.  To get
that effect with RRTYPEs, one would have to take the categories
you spell out about and create (as a silly example) type names
starting in "1" for the first category, "2" for the second, and
so on, or otherwise lexically distinguish the second category
from the other two.  Second, the potential code space for media
types may be a tad larger than the potential RRTYPE code space.
But, again, I think the question is irrelevant here -- I've not
advocating changing the allocation rules, only keeping the
relationship between already-allocated RRTYPEs and the Standards
Track into the categories you have described above.

--On Tuesday, May 21, 2013 15:24 -0400 Joe Abley
<jabley@hopcount.ca> wrote:

> Code-points in the RRType registry are assigned by expert
> review (not simply by "filling out a template" as someone
> suggested earlier). 

I was the one who said "filling out a template"  and that
reflects a bad attitude toward many expert reviews.  That
attitude and what underlies it has nothing to do with this
situation.

> If the suggestion is that the standards
> track is not available for any work that involves a code point
> that was assigned early, then I wonder what process is
> imagined for any future DNS work which aims at the standards
> track.

Presumably the same mechanism that has now been used for other
registrations that are normally expert review (or less) but that
interact with standards-track work:  one develops a
specification normally, puts it through the standards track, and
only then asks IANA to register the relevant parameters (and
either asks or directs the expert to sign off).  If the existing
RRTYPE registration rules prohibit that, I would suggest they
are badly broken but I can't imagine how they could be written
to specify such a prohibition.  

One could argue that all of our "expert review" procedures
should say "expert review except where the standards track is
used for other reasons" but the application of good sense says
that the expert should either consider the IETF Standards Track
review adequate and sign off or should be screaming loudly about
the deficiencies during Last Call.

Once more, the only important thing I'm objecting to here is
registering the RRTYPEs using the expert method, then asking for
Standards Track publication, then responding to Last Call
comments by saying something equivalent to "you don't get to
discuss that because these types are already registered".    I
think one can either say "standards track is not needed, publish
the description of the types as Informational" or that there is
an obligation on whomever is proposing standards track to figure
out how to make the review process work properly and without the
existing registrations being considered as a constraint.   I
don't think that is very complex or unreasonable.  YMMD.
 
    john


From randy@psg.com  Tue May 21 23:35:39 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BF321F936E for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 23:35:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level: 
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[AWL=0.112,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F-xjrTmcWHE8 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 23:35:39 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 7263321F92BB for <ietf@ietf.org>; Tue, 21 May 2013 23:35:39 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Uf2e6-000M0v-Jz; Wed, 22 May 2013 06:35:35 +0000
Date: Wed, 22 May 2013 15:35:31 +0900
Message-ID: <m2k3mrfrnw.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed	Standard
In-Reply-To: <519B97C5.6010901@network-heretics.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.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: Wed, 22 May 2013 06:35:40 -0000

>> With respect to the question of proposed standard. What changes if the 
>> requested status is informational?
> 
> I think just get rid of the normative language - SHOULDs, MUSTs, etc.

that is orthogonal to info/ps

next unnecessary rathole, please

randy

From randy@psg.com  Tue May 21 23:43:00 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1A721F93B1 for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 23:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.497
X-Spam-Level: 
X-Spam-Status: No, score=-2.497 tagged_above=-999 required=5 tests=[AWL=0.102,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jJ1embjNCOE for <ietf@ietfa.amsl.com>; Tue, 21 May 2013 23:42:59 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 7505A21F92F5 for <ietf@ietf.org>; Tue, 21 May 2013 23:42:59 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Uf2lF-000M2S-Up; Wed, 22 May 2013 06:42:58 +0000
Date: Wed, 22 May 2013 15:42:55 +0900
Message-ID: <m2ip2bfrbk.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the	DNS)	to Proposed Standard
In-Reply-To: <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <A1C292CF5EC7FA783DC4A479@JcK-HP8200.jck.com> <519B96E5.9040207@bogus.com> <519B97C5.6010901@network-heretics.com> <24901600-F1C7-49CE-9458-7130A3AAF0B7@hopcount.ca>
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: Wed, 22 May 2013 06:43:00 -0000

joe,

i spent time actually reading the document and commenting on it, one was
a substantive comment, at least to me.

any chance you could pull yourself away from the exemplary
anti-productive nitpicking maelstrom for a few minutes and respond?

thanks.

randy

From john-ietf@jck.com  Wed May 22 05:10:44 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5CEF21F9590; Wed, 22 May 2013 05:10:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PBVZNf18iwvD; Wed, 22 May 2013 05:10:38 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BE6A321F9588; Wed, 22 May 2013 05:10:37 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uf7sH-000BaN-7L; Wed, 22 May 2013 08:10:33 -0400
Date: Wed, 22 May 2013 08:10:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Mark Andrews <marka@isc.org>
Subject: Re: Deployment of standards compliant nameservers
Message-ID: <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com>
In-Reply-To: <20130521090727.GB17630@nic.fr>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 12:10:45 -0000

--On Tuesday, May 21, 2013 11:07 +0200 Stephane Bortzmeyer
<bortzmeyer@nic.fr> wrote:

>...
> Although these tests certainly contributed to the good
> technical quality of the name servers, they were removed both
> for commercial reasons (a registry has to make money to pay
> its employees) and because it was easier to have the same
> rules for ccTLDs and gTLDs (and ICANN forbids these technical
> tests in gTLDs).

Occasional fantasies about IETF enforcement power and the
Protocol Police notwithstanding, it seems to me that, if one
wanted to require standards-conforming nameservers, the most
(and maybe only) effective way to do that would be requirements
in the contractual agreements between TLD registries and their
registrants.  Recursively applying requirements down the tree is
not a new idea; RFC 1591 uses that language more than once.

If we believe that standards-compliance would improve Internet
stability and/or security (to say nothing of the predictability
of the user experience), then ICANN's forbidding registries from
imposing technical conformance requirements, if true, would seem
to violate their charter and bylaws.  Do you have any idea where
that restriction came from?   Or what Mark and others should do
to get it changed?
 
best,
   john





From ynir@checkpoint.com  Wed May 22 05:30:08 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C81521F9640; Wed, 22 May 2013 05:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.436
X-Spam-Level: 
X-Spam-Status: No, score=-10.436 tagged_above=-999 required=5 tests=[AWL=0.163, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KyWxwbS44Vw; Wed, 22 May 2013 05:30:02 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id AB65821F9638; Wed, 22 May 2013 05:30:01 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4MCTwsU026549; Wed, 22 May 2013 15:29:59 +0300
X-CheckPoint: {519CB7F9-8-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Wed, 22 May 2013 15:29:58 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Deployment of standards compliant nameservers
Thread-Topic: Deployment of standards compliant nameservers
Thread-Index: AQHOVbn0re8TMjG0REmyibnzVrQjA5kPJ3yAgAHFdwCAAAVzAA==
Date: Wed, 22 May 2013 12:29:58 +0000
Message-ID: <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com>
In-Reply-To: <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.55]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11ba209c7a2dd6a8b81d0aa6c80073f9f7d30b9799
Content-Type: text/plain; charset="us-ascii"
Content-ID: <017ED6AF8DECFD4182226A85E2A485AE@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<iesg@ietf.org>" <iesg@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 12:30:08 -0000

On May 22, 2013, at 3:10 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Tuesday, May 21, 2013 11:07 +0200 Stephane Bortzmeyer
> <bortzmeyer@nic.fr> wrote:
>=20
>> ...
>> Although these tests certainly contributed to the good
>> technical quality of the name servers, they were removed both
>> for commercial reasons (a registry has to make money to pay
>> its employees) and because it was easier to have the same
>> rules for ccTLDs and gTLDs (and ICANN forbids these technical
>> tests in gTLDs).
>=20
> Occasional fantasies about IETF enforcement power and the
> Protocol Police notwithstanding, it seems to me that, if one
> wanted to require standards-conforming nameservers, the most
> (and maybe only) effective way to do that would be requirements
> in the contractual agreements between TLD registries and their
> registrants.  Recursively applying requirements down the tree is
> not a new idea; RFC 1591 uses that language more than once.

We should be careful about requiring things like this (for whatever value o=
f "we"). Recursively applying requirements means that "we" are requiring se=
rvice providers (in this case registries) to pick fights with their custome=
rs. So instead of having an IETF protocol police, "we" expect service provi=
ders to act as local sheriffs.

It's not that service providers would never do this. There is some success =
in getting ISPs to shut down spammers, but they are likely to cooperate whe=
n the actions of the offenders are likely to damage either the service prov=
ider's infrastructure, or harm other customers.  This is not the case here.=
 A DNS server that ignores unknown record types does not hurt anyone who on=
ly queries for A and AAAA records. And MX. It hurts people who try to deplo=
y new record types, so for now, it hurts experiments. It reduces the likeli=
hood of a major browser deploying a version with DANE enabled by default.  =
This is definitely harm, but beating one bad server into compliance does no=
t fix the problem.=20

So "we" would be asking service providers to take a step with positive cost=
s (periodically testing servers, contacting customers, threatening them, an=
d following up), all to prevent a kind of harm that would only be prevented=
 if all other registrars in the world (or at least a vast majority) would d=
o the same. And if that harm was mitigated, and all the DNS servers in the =
world were fixed, hardly anyone would notice.

Seems like a tough sell to me.

Yoav


From jabley@hopcount.ca  Wed May 22 05:31:12 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9E421F96A4 for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 05:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G+RGIgBi+HDk for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 05:31:11 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1170521F967B for <ietf@ietf.org>; Wed, 22 May 2013 05:31:10 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ii15so2769804qab.4 for <ietf@ietf.org>; Wed, 22 May 2013 05:31:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=b2L2eM69BxlIQJb5SKhbE2xMP/5FHvH/z+EZ8xGd6LI=; b=gOgF28mSf6WQf4VmkNpmIXZfUT75Q5A/dAgjCI+k1BrCCZq1zy0sxeWyK+XGfRxbI8 THG92h0ccOqnBjv/YKEzrcIJrXdqldyY6HoOgfcUr2IbTi439GmZbktO8szsTcHXRRq/ kDJFxKBDryF/ulc8j1Sp+8Aoe7yIGkwJpLtow=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=b2L2eM69BxlIQJb5SKhbE2xMP/5FHvH/z+EZ8xGd6LI=; b=OjIiToYEkRiOju4wV/xfn408UwHBgZ8eDUBkOXnHazpX3tEIpXVQdRhg9pylbyP9yy KLDXic2htXPKvIkyGtV3JKJGBWwMg+iTxiw5R7xdMog+wdcrjcLRu4rPetdSBemTpUfn X4Nxl3+Bp8AQteieOCnEME82iw4GWNGsBODE5xPBgPx0GBRfiaGtXFXhnH8whG8sXFLa mLSvzpfs3Dzs1K62ueFUJm9I//EpsKNF3i1ifNgFnChwXBEzlzGDkmc86bBR8/rkhKdl /ZxgycRzePSlZ0ZhWB8VuTXr0E5erESSQS5IPMXYvKKA9B13Q2JLXCNULivoHYZrJc4A 97Jg==
X-Received: by 10.49.73.202 with SMTP id n10mr7303779qev.55.1369225870502; Wed, 22 May 2013 05:31:10 -0700 (PDT)
Received: from ?IPv6:2001:4900:1042:100:bd5c:e958:4b59:b8a? ([2001:4900:1042:100:bd5c:e958:4b59:b8a]) by mx.google.com with ESMTPSA id d5sm6765247qel.4.2013.05.22.05.31.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 May 2013 05:31:09 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS)	to Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <m24ndwgxwo.wl%randy@psg.com>
Date: Wed, 22 May 2013 08:31:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AD8521F-DFA3-4BDC-AA9F-A5637C6B2672@hopcount.ca>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQmke6sQmsnUoi6nKcnb22CMj2YLZeFO2woCvavb6VQ68fGgpLEn0gI2COKoJFA10nuRZeSe
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: Wed, 22 May 2013 12:31:12 -0000

Hi Randy,

On 2013-05-21, at 11:23, Randy Bush <randy@psg.com> wrote:

> i have read the draft.  if published, i would prefer it as a proposed
> standard as it does specify protocol data objects.

Noted, thanks.

It does seem that the main objection to the standards track for this =
document is that I accidentally erred on the side of running code before =
the document was last-called. This does seem like a poor reason to move =
the document to informational, but since my primary goal with this has =
always been to provide a specification (and since the specification is =
trivial) it's not especially clear to me why a fight for the standards =
track would have more than semantic benefits.

> < where you goin' with that gun in your hand? >

Going to kill my old lady. Not really.

> i am not at all sanguine about the issues raised in the in sec cons.  =
i
> accept that NTRE038D may have asked that these be in the dns, but =
seems
> to me that it is ill advised and some other means to meet their actual
> needs might be found.  e.g. what's the matter with logs?

I agree it was a strange implementation decision, almost as though more =
neutral, technical common sense might have been helpful in the process, =
an unusual situation for a regulator to find themselves in, no doubt. =
But at this point, it is what it is.

The distaste of many here notwithstanding, the DNS is widely used today =
as a convenient distributed database for the storage of non-public data. =
I've had feedback from others who say that they are doing similar things =
with TXT records, and who welcomed the availability of a specific type, =
so regardless of the merits of NTRE038D the idea seems to have more =
general applicability.

The text in the Security Considerations section was a response to =
concerns raised on the dnsext list that someone might look at the RRType =
spec and conclude that publishing subscriber (or other privacy-busting) =
link-layer addresses in the public namespace was something that was =
desirable or necessary. I don't personally see that as a great concern =
(I don't think operators are sufficiently naive) but the warning that =
subsequently appeared in section 8 did not seem inappropriate.

> nits you are welcome to ignore.
>=20
> 1 - intro - do we have a standard way to refer to the dns specs as =
tuned
>    	    in 42 subsequent rfcs since 1035?

No, as Andrew mentioned.

> 3.2 and 4.2 the presentation format specs might be simpler if the
>    	    examples in 5 were moved there

Good idea.

> 6 - the example use case is as much or more a motivation as an example

It was certainly the motivation for the draft; the ugly and varied RR =
schemas used made me reach for grep to find the sensible way to store =
MAC-48 addresses in the DNS; there wasn't one. In a brief moment of =
spring-cleaning fervour I decided to try and make things better for the =
next person who has to parse this kind of stuff.

I could just as well have made that section title "Motivation for =
Bothering" but "Example Use Case" seemed like a better fit for the =
context I imagined future readers might have.


Joe=

From kathleen.moriarty@emc.com  Wed May 22 05:57:09 2013
Return-Path: <kathleen.moriarty@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 355BB21F968F; Wed, 22 May 2013 05:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCxdgGfvmPAJ; Wed, 22 May 2013 05:57:04 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 0907921F96AA; Wed, 22 May 2013 05:57:03 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r4MCuop0006924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 May 2013 08:56:53 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd01.lss.emc.com [10.254.221.251]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 22 May 2013 08:56:45 -0400
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 r4MCufH3006942; Wed, 22 May 2013 08:56:44 -0400
Received: from mx15a.corp.emc.com ([169.254.1.105]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Wed, 22 May 2013 08:56:41 -0400
From: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>
To: Yoav Nir <ynir@checkpoint.com>, John C Klensin <john-ietf@jck.com>
Date: Wed, 22 May 2013 08:56:41 -0400
Subject: RE: Deployment of standards compliant nameservers
Thread-Topic: Deployment of standards compliant nameservers
Thread-Index: AQHOVbn0re8TMjG0REmyibnzVrQjA5kPJ3yAgAHFdwCAAAVzAIAAMyRA
Message-ID: <F5063677821E3B4F81ACFB7905573F24DC22DEFA@MX15A.corp.emc.com>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com>, <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com>
In-Reply-To: <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
Cc: "<iesg@ietf.org>" <iesg@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 12:57:09 -0000

Back when I worked at a service provider, we helped customers with their DN=
S configurations, Sendmail, usenet news (yes, it was a long time ago), and =
other services.  If they were new customers, we would help them with the se=
tup or if something was broken we would look at the configuration, look at =
dig results, etc. =20

Shouldn't we be at the point where the applications running DNS services ca=
n ensure configurations are correct?  Wouldn't it be more efficient to work=
 with the implementations to provide configuration validation or have easie=
r input screens?  It was fine in 1997 to call someone at you SP, but this d=
oes not scale even with lots of service providers.  While tying this to con=
tracts seems like a good idea, that is out of our hands at the IETF.  If we=
 went down the path of enforcement through contracts, I wouldn't view this =
as picking fights, but rather a proactive service to 'help' customers.  Hav=
ing said that, I think if we can improve the applications that generate the=
ir DNS files, it would be more effective long term.  While some teams are t=
echnical enough to validate their own DNS, others prefer more full service =
applications. =20

Maybe a review of existing applications would be helpful for the community?=
  I just see the following on Wikipedia:
http://en.wikipedia.org/wiki/Comparison_of_DNS_server_software
and
http://en.wikipedia.org/wiki/DNS_management_software

How about adding a column for compliance to RFCs?  Or a description that ma=
kes people aware of configuration problems caused when using certain packag=
es?  This may start with known problems and work arounds, but ultimately le=
ad to fixes in the products with automatic configuration validation.  This =
may not be the job of the IETF, but there must be groups we can work with t=
o accomplish things like this.

Just a thought...

Best regards,
Kathleen
________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Yoav Nir [=
ynir@checkpoint.com]
Sent: Wednesday, May 22, 2013 8:29 AM
To: John C Klensin
Cc: <iesg@ietf.org>; <ietf@ietf.org>
Subject: Re: Deployment of standards compliant nameservers

On May 22, 2013, at 3:10 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Tuesday, May 21, 2013 11:07 +0200 Stephane Bortzmeyer
> <bortzmeyer@nic.fr> wrote:
>
>> ...
>> Although these tests certainly contributed to the good
>> technical quality of the name servers, they were removed both
>> for commercial reasons (a registry has to make money to pay
>> its employees) and because it was easier to have the same
>> rules for ccTLDs and gTLDs (and ICANN forbids these technical
>> tests in gTLDs).
>
> Occasional fantasies about IETF enforcement power and the
> Protocol Police notwithstanding, it seems to me that, if one
> wanted to require standards-conforming nameservers, the most
> (and maybe only) effective way to do that would be requirements
> in the contractual agreements between TLD registries and their
> registrants.  Recursively applying requirements down the tree is
> not a new idea; RFC 1591 uses that language more than once.

We should be careful about requiring things like this (for whatever value o=
f "we"). Recursively applying requirements means that "we" are requiring se=
rvice providers (in this case registries) to pick fights with their custome=
rs. So instead of having an IETF protocol police, "we" expect service provi=
ders to act as local sheriffs.

It's not that service providers would never do this. There is some success =
in getting ISPs to shut down spammers, but they are likely to cooperate whe=
n the actions of the offenders are likely to damage either the service prov=
ider's infrastructure, or harm other customers.  This is not the case here.=
 A DNS server that ignores unknown record types does not hurt anyone who on=
ly queries for A and AAAA records. And MX. It hurts people who try to deplo=
y new record types, so for now, it hurts experiments. It reduces the likeli=
hood of a major browser deploying a version with DANE enabled by default.  =
This is definitely harm, but beating one bad server into compliance does no=
t fix the problem.

So "we" would be asking service providers to take a step with positive cost=
s (periodically testing servers, contacting customers, threatening them, an=
d following up), all to prevent a kind of harm that would only be prevented=
 if all other registrars in the world (or at least a vast majority) would d=
o the same. And if that harm was mitigated, and all the DNS servers in the =
world were fixed, hardly anyone would notice.

Seems like a tough sell to me.

Yoav


From john-ietf@jck.com  Wed May 22 07:01:18 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4619A21F91BF; Wed, 22 May 2013 07:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UANxvrw3oPfB; Wed, 22 May 2013 07:01:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5372D21F91B1; Wed, 22 May 2013 07:01:12 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uf9bD-000C4a-Pg; Wed, 22 May 2013 10:01:03 -0400
Date: Wed, 22 May 2013 10:00:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Deployment of standards compliant nameservers
Message-ID: <9506594E9E3CB989AFBC02A8@JcK-HP8200.jck.com>
In-Reply-To: <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com> <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.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: "<iesg@ietf.org>" <iesg@ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 14:01:18 -0000

--On Wednesday, May 22, 2013 12:29 +0000 Yoav Nir
<ynir@checkpoint.com> wrote:

>> Occasional fantasies about IETF enforcement power and the
>> Protocol Police notwithstanding, it seems to me that, if one
>> wanted to require standards-conforming nameservers, the most
>> (and maybe only) effective way to do that would be
>> requirements in the contractual agreements between TLD
>> registries and their registrants.  Recursively applying
>> requirements down the tree is not a new idea; RFC 1591 uses
>> that language more than once.
> 
> We should be careful about requiring things like this (for
> whatever value of "we"). Recursively applying requirements
> means that "we" are requiring service providers (in this case
> registries) to pick fights with their customers. So instead of
> having an IETF protocol police, "we" expect service providers
> to act as local sheriffs.
>...
> Seems like a tough sell to me.

Actually, I was thinking about something a little different (and
should have been more explicit).  

I wouldn't suggest trying to mandate anything top-down.  If
nothing else, ICANN's track record for being able to enforce its
mandates is very poor (and that is arguably a good thing).  On
the other, we talk a lot about reputations and the advantages of
end sites being able to base policies on them.   If whatever the
actual restrictions that, according to Stephane, forbid TLDs
from imposing "we require you to have a competent nameserver and
will test" were removed then, especially with the coming huge
increase in TLDs, it would make it possible for registries to
compete on the degree to which they wanted to offer assurances
of quality DNS servers and services in subsidiary zones.
Would-be registrants who didn't want to play would have the
option of finding TLDs who did not have those restrictions.
That would create a new opportunity for enhanced competition and
differentiation among TLDs (which ICANN presumably favors along
with favoring security and stability) and would create a basis
for some DNS server certification activities (and even a
business model for them).

No mandate from the top, just elimination of whatever
restrictions now prevent registries from insisting on quality
operations in registrants if they wanted to.

It wouldn't get us to "everyone has to run a conforming server"
--which I consider impossible as long as producing
non-conforming servers is legal with governments enforcing the
rules if servers don't conform (and I really don't think  we
want to go there)-- but it would at least give a resolver an
indication of where conforming ones were guarantees and what
responses or non-responses they couldn't trust.

    john




From wmwang2001@hotmail.com  Wed May 22 08:38:38 2013
Return-Path: <wmwang2001@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4688021F93E1; Wed, 22 May 2013 08:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=x tagged_above=-999 required=5 tests=[]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hpf1Sp8X1PD1; Wed, 22 May 2013 08:38:37 -0700 (PDT)
Received: from blu0-omc2-s36.blu0.hotmail.com (blu0-omc2-s36.blu0.hotmail.com [65.55.111.111]) by ietfa.amsl.com (Postfix) with ESMTP id 0BEE721F91BC; Wed, 22 May 2013 08:38:36 -0700 (PDT)
Received: from BLU0-SMTP117 ([65.55.111.71]) by blu0-omc2-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 22 May 2013 08:38:36 -0700
X-EIP: [cHudoBnnoM6Xmc1QaZzCRX/7GxhM2fhs]
X-Originating-Email: [wmwang2001@hotmail.com]
Message-ID: <BLU0-SMTP117E1F0968A630DF0A05E81C9A90@phx.gbl>
Received: from WmwangHome ([125.120.89.142]) by BLU0-SMTP117.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 22 May 2013 08:38:21 -0700
From: "Wang,Weiming" <wmwang2001@hotmail.com>
To: "Ben Campbell" <ben@nostrum.com>
References: <8EC701FD-4258-4382-9711-B76EFBB3E1BA@nostrum.com> <BLU0-SMTP270A16556E20F95AC04C613C9AC0@phx.gbl> <3BEFC69D-7959-4549-997B-113A53C30637@nostrum.com>
Subject: Re: Gen-ART LC Review of draft-ietf-forces-interop-07
Date: Wed, 22 May 2013 23:38:15 +0800
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_01D6_01CE5745.6E793440"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-OriginalArrivalTime: 22 May 2013 15:38:21.0716 (UTC) FILETIME=[63DAD540:01CE5702]
Cc: IETF-Discussion list <ietf@ietf.org>, draft-ietf-forces-interop.all@tools.ietf.org, gen-art@ietf.org, forces-chairs@tools.ietf.org, 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: Wed, 22 May 2013 15:38:38 -0000

------=_NextPart_000_01D6_01CE5745.6E793440
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

SGkgQmVuIGFuZCBhbGwsDQoNClNvbWUgbW9yZSByZXBsaWVzIGFyZSBpbmxpbmUuIA0KDQpBdHRh
Y2hlZCBpcyB0aGUgdXAgdG8gZGF0ZSBzdWItdmVyc2lvbigwOHYxKSBvZiB0aGUgZG9jdW1lbnQg
YW5kIHRoZSBhc3NvY2lhdGVkIGRpZmYgZmlsZSB3aXRoIGxhc3QgdmVyc2lvbiAwNy4gIA0KDQpJ
IGhhdmUgdG8gbWV0aW9uIEkgc3RpbGwgaGF2ZSBub3QgeWV0IGZpbmlzaGVkIHRvIGNoYW5nZSBs
YXN0IHBhZ2VzIG9mIHRoZSBkb2N1bWVudCB0byBwYXN0IHRlbnNlLiBJJ2wgY29udGludWUgZG9p
bmcgaXQuDQoNCkhvcGUgdG8gc2VlIG1vcmUgY29tbWVudHMgYW5kIHRoZW4gd2l0aCBtb3JlIG1v
ZGlmaWNhdGlvbiwgSSBob3BlIHRvIHVwZGF0ZSB0byBJRVRGIHdpdGggdGhhdCB2ZXJzaW9uLiAN
Cg0KdGhhbmtzIGEgbG90Lg0KDQpXZWltaW5nDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0t
LS0gDQpGcm9tOiAiQmVuIENhbXBiZWxsIiA8YmVuQG5vc3RydW0uY29tPg0KDQpUaGFua3MgZm9y
IHRoZSByZXNwb25zZS4gQ29tbWVudHMgaW5saW5lLiBJIHJlbW92ZWQgc2VjdGlvbnMgZm9yIHdo
aWNoIEkgaGF2ZSBubyBmdXJ0aGVyIGNvbW1lbnQuDQoNClRoYW5rcyENCg0KQmVuLg0KDQpPbiBN
YXkgMTYsIDIwMTMsIGF0IDEwOjE5IFBNLCAiV2FuZyxXZWltaW5nIiA8d213YW5nMjAwMUBob3Rt
YWlsLmNvbT4gd3JvdGU6DQo+IA0KDQpbLi4uXQ0KDQo+IC0tIFRoZSBkcmFmdCBtZW50aW9ucyBh
IGNvdXBsZSBvZiBpbnN0YW5jZXMgb2YgdGVzdHMgdGhhdCBmYWlsZWQgYmVjYXVzZSBvZiBhbiBp
bmNvcnJlY3QgaW1wbGVtZW50YXRpb24gb3IgZGlmZmVyaW5nIGVuY2Fwc3VsYXRpb24gZm9ybWF0
cy4gRG9lcyB0aGlzIHN1Z2dlc3QgdGhhdCB0aGUgc3BlY2lmaWNhdGlvbnMgc2hvdWxkIGJlIGNs
YXJpZmllZD8gSW4gcGFydGljdWxhciwgaW4gdGhlIGNhc2Ugb2YgZW5jYXBzdWxhdGlvbiBmb3Jt
YXQgbWlzbWF0Y2gsIHNob3VsZCB0aGUgc3BlY3MgaW5jbHVkZSBzdHJvbmdlciByZXF1aXJlbWVu
dHMgdG8gYmUgYWJsZSB0byByZWNlaXZlIGFsbCBlbmNhcHN1bGF0aW9uIGZvcm1hdHM/IE9yIHNo
b3VsZCB0aGUgbnVtYmVyIG9mIG9wdGlvbnMgYmUgcmVkdWNlZD8NCj4gW1JlLiBieSDOlc6XXSBU
aGUgcHJvdG9jb2wgcHJvdmlkZXMgYSBudW1iZXIgb2YgZGlmZmVyZW50IGFwcHJvYWNoZXMgDQo+
IFtSZS4gYnkgV2VpbWluZ10gVGhlIGtleSBpc3N1ZSBpcyBzdGlsbCBmcm9tIHRoZSBkZWVwIHVu
ZGVyc3RhbmRpbmcgb2YgdGhlIHByb3RvY29sIGZyb20gaW1wbGVtZW50YXRpb25zLiBJIHN0aWxs
IGhhdmUgbm90IHNlZW4gbmVlZCBmb3IgYW55IHVyZ2VudCBjaGFuZ2UgZm9yIHRoZSBwcm90b2Nv
bC4gDQoNCkkgZG9uJ3QgaGF2ZSBlbm91Z2gga25vd2xlZGdlIG9mIHRoZSBwcm90b2NvbCB0byBm
b3JtIGEgc3BlY2lmaWMgb3BpbmlvbiwgYnV0IGl0J3MgYmVlbiBteSBleHBlcmllbmNlIGluIG90
aGVyIGFyZWFzIHRoYXQgd2hlbiBpbXBsZW1lbnRvcnMgaW50ZXJwcmV0IHRoaW5ncyBkaWZmZXJl
bnRseSwgdGhlcmUncyBvZnRlbiByb29tIGZvciBjbGFyaWZpY2F0aW9uLCBldmVuIGlmIHRoZSB0
ZXh0IGlzIGZvcm1hbGx5IGNvcnJlY3QuIEkgYWdyZWUgaXQgZG9lc24ndCBpbXBseSBhbiB1cmdl
bnQgbmVlZCwgYnV0IHdvdWxkIGl0IGJlIHdvcnRoIG9uZSBvciBtb3JlIGVycmF0YT8NCg0KW1Jl
Ol0gV2UgaGF2ZSBhY3R1YWxseSBzdWJtaXR0ZWQgYSBzdWdnZXN0aW9uIHRvIGVycmF0YSBvZiBS
RkMgNTgxMCwgYnV0IHdhcyBkZW5pZWQgd2l0aCB0aGUgcmVhc29uIHRoYXQgbXV0dWFsIHVuZGVy
c3RhbmRpbmcgb2YgZGlmZmVyZW50IGVuY2Fwc3VsYXRpb24gZm9ybWF0cyBhcmUgZXNzZW50aWFs
IHRvIHByb3RvY29sIGltcGxlbWVudGF0aW9ucywgYW5kIG5lZWQgbm90IGEgc3BlY2lmaWMgbm90
aWZpY2F0aW9uLg0KIA0KWy4uLl0NCg0KPiAtLSBzZWN0aW9uIDQuNCwgbGFzdCBwYXJhZ3JhcGg6
DQo+IA0KPiBUaGUgdGV4dCBzYXlzIHRoYXQgc2luY2UgdGhlIG1lbnRpb25lZCBmYWlsdXJlcyB3
ZXJlIGxpa2VseSB0aGUgcmVzdWx0IG9mIGJ1Z3MsIGl0IGRvZXNuJ3QgaW5kaWNhdGUgYW4gaW50
ZXJvcGVyYWJpbGl0eSBwcm9ibGVtIGluIHRoZSBzcGVjcy4gSSBoYXZlIHRvIHBvaW50IG91dCB0
aGF0LCBpdCBhbHNvIGRvZXNuJ3QgcHJvdmUgaW50ZXJvcGVyYWJpbGl0eSBpbiBib3RoIGRpcmVj
dGlvbnMgZm9yIHRoZSBwYXJ0aWN1bGFyIHRlc3QuIEl0IHdvdWxkIGFsc28gYmUgd29ydGggY29t
bWVudGluZyBvbiB3aGV0aGVyIHRoZSBwcm9iYWJseSBidWdzIHdlcmUgcHJvZ3JhbW1pbmcgZXJy
b3JzIHJhdGhlciB0aGFuIG1pc3VuZGVyc3RhbmRpbmdzIG9mIHRoZSBzcGVjaWZpY2F0aW9uLg0K
PiBbUmUuIGJ5IFdlaW1pbmddIHRvIGNoYW5nZSB0aGUgd2hvbGUgcGFyYWdyYXBoIHRvOg0KPiAg
PHQ+IFRoZSB0d28gdGVzdCBpdGVtcyBmYWlsZWQuIE5vdGUgdGhhdCBUZXN0ICM3IGFuZCAjOCB3
ZXJlIGlkZW50aWNhbCB0byB0aGUgdGVzdHMsIG9ubHkgd2l0aCBDRSBhbmQgRkUgaW1wbGVtZW50
ZXJzIHdlcmUgZXhjaGFuZ2VkLiBNb3Jlb3ZlciwgdGVzdCAjMTIgYW5kICMxMyBzaG93ZWQgdGhh
dCB0aGUgcmVkaXJlY3QgY2hhbm5lbCB3b3JrZWQgd2VsbC4gVGhlcmVmb3JlLCBpdCBjYW4gYmUg
cmVhc29uYWJseSBpbmZlcnJlZCB0aGF0IHRoZSBwcm9ibGVtIGNhdXNlZCB0aGUgZmFpbHVyZSB3
YXMgZnJvbSB0aGUgaW1wbGVtZW50YXRpb25zLCByYXRoZXIgdGhhbiBmcm9tIHRoZSBGb3JDRVMg
cHJvdG9jb2wgaXRzZWxmIG9yIGZyb20gbWlzdW5kZXJzdGFuZGluZyBvZiBpbXBsZW1lbnRhdGlv
bnMgb24gdGhlIHByb3RvY29sIHNwZWNpZmljYXRpb24uIEFsdGhvdWdoIHRoZSBmYWlsdXJlIG1h
ZGUgdGhlIE9TUEYgaW50ZXJvcGVyYWJpbGl0eSB0ZXN0IGluY29tcGxldGUsIGl0IGRpZCBub3Qg
c2hvdyBpbnRlcm9wZXJhYmlsaXR5IHByb2JsZW0uIE1vcmUgdGVzdCB3b3JrIGlzIG5lZWRlZCB0
byB2ZXJpZnkgdGhlIE9TUEYgaW50ZXJvcGVyYWJpbGl0eS48L3Q+DQoNCldvcmtzIGZvciBtZSwg
dGhhbmtzIQ0KW1JlOiBdIFRoYW5rcyB0b28uDQoNClsuLi5dDQoNCg0KW1JlLiBieSBXZWltaW5n
XSBUaGUgc2VjdGlvbiAzLjIgcGFyYS4zIGhhcyBiZWVuIGNoYW5nZWQgdG86IA0KPiA8dD4uLi4g
QmVjYXVzZSB0aGVyZSBjYW1lIHVuZm9ydHVuYXRlbHkgYSBwcm9ibGVtIHdpdGggdGhlIHRlc3Qg
c3lzdGVtIGluIEdyZWVjZSB0byBkZXBsb3kgSVBTZWMgb3ZlciBUTUwgZHVyaW5nIHRoZSB0ZXN0
IHByb2Nlc3MsIHRoaXMgdGVzdCBvbmx5IHRvb2sgcGxhY2UgYmV0d2VlbiB0ZXN0IHN5c3RlbXMg
aW4gQ2hpbmEgYW5kIEphcGFuLjwvdD4NCg0KVGhlIHNlbnRlbmNlIGlzIHN0aWxsIGhhcmQgdG8g
cGFyc2UuIERvIHlvdSBtZWFuIHRoZSBmb2xsb3dpbmc/DQoNCiJCZWNhdXNlIGFuIHVuZm9ydHVu
YXRlIHByb2JsZW0gd2l0aCB0aGUgdGVzdCBzeXN0ZW0gaW4gR3JlZWNlIHByZXZlbnRlZCB0aGUg
ZGVwbG95bWVudCBvZiBJUFNlYyBvdmVyIFRNTCwgdGhpcyB0ZXN0IG9ubHkgdG9vayBwbGFjZSBi
ZXR3ZWVuIHRoZSB0ZXN0IHN5c3RlbXMgaW4gQ2hpbmEgYW5kIEphcGFuLiINCltSZS5dIFRoYW5r
cyBhZ2Fpbi4gSSd2IGp1c3QgaW5jb3JwYXJhdGVkIGl0LiANCg0KWy4uLl0NCg==

------=_NextPart_000_01D6_01CE5745.6E793440
Content-Type: text/html; name="Diff draft-ietf-forces-interop-08v1_txt -
 draft-ietf-forces-interop-07_txt.htm"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; filename="Diff
 draft-ietf-forces-interop-08v1_txt - draft-ietf-forces-interop-07_txt.htm"

=0A=
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" =
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> =0A=
<!-- Generated by rfcdiff 1.41: rfcdiff  --> =0A=
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->=0A=
<!-- System: Linux gamay 2.6.26-2-686 #1 SMP Tue Mar 9 17:35:51 UTC 2010 =
i686 GNU/Linux --> =0A=
<!-- Using awk: /usr/bin/gawk: GNU Awk 3.1.8 --> =0A=
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 3.2 --> =0A=
<!-- Using wdiff: /usr/bin/wdiff: wdiff (GNU wdiff) 0.6.5 --> =0A=
<html> =0A=
<head> =0A=
  <meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Diso-8859-1" /> =0A=
  <meta http-equiv=3D"Content-Style-Type" content=3D"text/css" /> =0A=
  <title>Diff: draft-ietf-forces-interop-08v1.txt - =
draft-ietf-forces-interop-07.txt</title> =0A=
  <style type=3D"text/css"> =0A=
    body    { margin: 0.4ex; margin-right: auto; } =0A=
    tr      { } =0A=
    td      { white-space: pre; font-family: monospace; vertical-align: =
top; font-size: 0.86em;} =0A=
    th      { font-size: 0.86em; } =0A=
    .small  { font-size: 0.6em; font-style: italic; font-family: =
Verdana, Helvetica, sans-serif; } =0A=
    .left   { background-color: #EEE; } =0A=
    .right  { background-color: #FFF; } =0A=
    .diff   { background-color: #CCF; } =0A=
    .lblock { background-color: #BFB; } =0A=
    .rblock { background-color: #FF8; } =0A=
    .insert { background-color: #8FF; } =0A=
    .delete { background-color: #ACF; } =0A=
    .void   { background-color: #FFB; } =0A=
    .cont   { background-color: #EEE; } =0A=
    .linebr { background-color: #AAA; } =0A=
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; =
text-align: right; padding: 0 2px; } =0A=
    .elipsis{ background-color: #AAA; } =0A=
    .left .cont { background-color: #DDD; } =0A=
    .right .cont { background-color: #EEE; } =0A=
    .lblock .cont { background-color: #9D9; } =0A=
    .rblock .cont { background-color: #DD6; } =0A=
    .insert .cont { background-color: #0DD; } =0A=
    .delete .cont { background-color: #8AD; } =0A=
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px =
0; } =0A=
  </style> =0A=
</head> =0A=
<body > =0A=
  <table border=3D"0" cellpadding=3D"0" cellspacing=3D"0"> =0A=
  <tr bgcolor=3D"orange"><th></th><th><a =
href=3D"/rfcdiff?url2=3Ddraft-ietf-forces-interop-08v1.txt" =
style=3D"color:#008; text-decoration:none;">&lt;</a>&nbsp;<a =
href=3D"/html/draft-ietf-forces-interop-08v1.txt" =
style=3D"color:#008">draft-ietf-forces-interop-08v1.txt</a>&nbsp;</th><th=
> </th><th>&nbsp;<a href=3D"/html/draft-ietf-forces-interop-07.txt" =
style=3D"color:#008">draft-ietf-forces-interop-07.txt</a>&nbsp;<a =
href=3D"/rfcdiff?url1=3Ddraft-ietf-forces-interop-07.txt" =
style=3D"color:#008; text-decoration:none;">&gt;</a></th><th></th></tr> =0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Internet Engineering Task Force                           =
       W. Wang</td><td> </td><td class=3D"right">Internet Engineering =
Task Force                                  W. Wang</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Internet-Draft                             Zhejiang =
Gongshang University</td><td> </td><td class=3D"right">Internet-Draft    =
                         Zhejiang Gongshang University</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Updates: 6053 (if approved)                               =
      K. Ogawa</td><td> </td><td class=3D"right">Updates: 6053 (if =
approved)                                     K. Ogawa</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Intended status: Informational                           =
NTT Corporation</td><td> </td><td class=3D"right">Intended status: =
Informational                           NTT Corporation</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0001" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock">Expires: <span class=3D"delete">November 23, =
2013</span>                                 E. Haleplidis</td><td> =
</td><td class=3D"rblock">Expires: <span class=3D"insert">October 17, =
2013 </span>                                 E. Haleplidis</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                                 University of =
Patras</td><td> </td><td class=3D"right">                                =
                    University of Patras</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                                               M. =
Gao</td><td> </td><td class=3D"right">                                   =
                               M. Gao</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                               Hangzhou BAUD =
Networks</td><td> </td><td class=3D"right">                              =
                    Hangzhou BAUD Networks</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                                        J. Hadi =
Salim</td><td> </td><td class=3D"right">                                 =
                          J. Hadi Salim</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                                    Mojatatu =
Networks</td><td> </td><td class=3D"right">                              =
                         Mojatatu Networks</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0002" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                                         <span =
class=3D"delete">  May 22</span>, 2013</td><td> </td><td =
class=3D"rblock">                                                        =
  <span class=3D"insert">April 15</span>, 2013</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left"> =
Interoperability Report for Forwarding and Control Element =
Separation</td><td> </td><td class=3D"right"> Interoperability Report =
for Forwarding and Control Element Separation</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                             (ForCES)</td><td> </td><td class=3D"right"> =
                               (ForCES)</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0003" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                     draft-ietf-forces-interop-0<span =
class=3D"delete">8</span></td><td> </td><td class=3D"rblock">            =
          draft-ietf-forces-interop-0<span =
class=3D"insert">7</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Abstract</td><td> </td><td =
class=3D"right">Abstract</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0004" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  This document capture<span class=3D"delete">d</span> results of the =
second Forwarding and Control</td><td> </td><td class=3D"rblock">   This =
document capture<span class=3D"insert">s</span> results of the second =
Forwarding and Control</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Element Separation (ForCES) interoperability test which took place =
on</td><td> </td><td class=3D"right">   Element Separation (ForCES) =
interoperability test which took place on</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
February 24-25, 2011 in the Internet Technology Lab (ITL) of =
Zhejiang</td><td> </td><td class=3D"right">   February 24-25, 2011 in =
the Internet Technology Lab (ITL) of Zhejiang</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0005" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Gongshang University, China.  RFC 6053 <span =
class=3D"delete">had</span> reported the results of</td><td> </td><td =
class=3D"rblock">   Gongshang University, China.  RFC 6053 reported the =
results of the</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  the first ForCES interoperability test, and this document updates =
RFC</td><td> </td><td class=3D"rblock">   first ForCES interoperability =
test, and this document updates RFC</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
6053 by providing further interoperability results.</td><td> </td><td =
class=3D"right">   6053 by providing further interoperability =
results.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0006" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock">Status of <span class=3D"delete">t</span>his =
Memo</td><td> </td><td class=3D"rblock">Status of <span =
class=3D"insert">T</span>his Memo</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
This Internet-Draft is submitted in full conformance with the</td><td> =
</td><td class=3D"right">   This Internet-Draft is submitted in full =
conformance with the</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
provisions of BCP 78 and BCP 79.</td><td> </td><td class=3D"right">   =
provisions of BCP 78 and BCP 79.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Internet-Drafts are working documents of the Internet =
Engineering</td><td> </td><td class=3D"right">   Internet-Drafts are =
working documents of the Internet Engineering</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Task Force (IETF).  Note that other groups may also distribute</td><td> =
</td><td class=3D"right">   Task Force (IETF).  Note that other groups =
may also distribute</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
working documents as Internet-Drafts.  The list of current =
Internet-</td><td> </td><td class=3D"right">   working documents as =
Internet-Drafts.  The list of current Internet-</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> =
</td><td class=3D"right">   Drafts is at =
http://datatracker.ietf.org/drafts/current/.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Internet-Drafts are draft documents valid for a maximum of six =
months</td><td> </td><td class=3D"right">   Internet-Drafts are draft =
documents valid for a maximum of six months</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
and may be updated, replaced, or obsoleted by other documents at =
any</td><td> </td><td class=3D"right">   and may be updated, replaced, =
or obsoleted by other documents at any</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
time.  It is inappropriate to use Internet-Drafts as reference</td><td> =
</td><td class=3D"right">   time.  It is inappropriate to use =
Internet-Drafts as reference</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
material or to cite them other than as "work in progress."</td><td> =
</td><td class=3D"right">   material or to cite them other than as "work =
in progress."</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0007" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  This Internet-Draft will expire on <span class=3D"delete">November =
23</span>, 2013.</td><td> </td><td class=3D"rblock">   This =
Internet-Draft will expire on <span class=3D"insert">October 17</span>, =
2013.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Copyright Notice</td><td> </td><td =
class=3D"right">Copyright Notice</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Copyright (c) 2013 IETF Trust and the persons identified as the</td><td> =
</td><td class=3D"right">   Copyright (c) 2013 IETF Trust and the =
persons identified as the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
document authors.  All rights reserved.</td><td> </td><td =
class=3D"right">   document authors.  All rights reserved.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
This document is subject to BCP 78 and the IETF Trust's Legal</td><td> =
</td><td class=3D"right">   This document is subject to BCP 78 and the =
IETF Trust's Legal</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Provisions Relating to IETF Documents</td><td> </td><td class=3D"right"> =
  Provisions Relating to IETF Documents</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
(http://trustee.ietf.org/license-info) in effect on the date of</td><td> =
</td><td class=3D"right">   (http://trustee.ietf.org/license-info) in =
effect on the date of</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
publication of this document.  Please review these documents</td><td> =
</td><td class=3D"right">   publication of this document.  Please review =
these documents</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
carefully, as they describe your rights and restrictions with =
respect</td><td> </td><td class=3D"right">   carefully, as they describe =
your rights and restrictions with respect</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
to this document.  Code Components extracted from this document =
must</td><td> </td><td class=3D"right">   to this document.  Code =
Components extracted from this document must</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
include Simplified BSD License text as described in Section 4.e =
of</td><td> </td><td class=3D"right">   include Simplified BSD License =
text as described in Section 4.e of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the Trust Legal Provisions and are provided without warranty as</td><td> =
</td><td class=3D"right">   the Trust Legal Provisions and are provided =
without warranty as</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
described in the Simplified BSD License.</td><td> </td><td =
class=3D"right">   described in the Simplified BSD License.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Table of Contents</td><td> </td><td class=3D"right">Table =
of Contents</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0008" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">.</span>  3</td><td> </td><td class=3D"rblock">   1.  =
Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   =
3</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    1.1.  ForCES Protocol  . . . . . . . . . . . . . . . . . . . . .  =
3</td><td> </td><td class=3D"rblock">     1.1.  ForCES Protocol . . . . =
. . . . . . . . . . . . . . . . .   3</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    1.2.  ForCES FE Model  . . . . . . . . . . . . . . . . . . . . .  =
<span class=3D"delete">4</span></td><td> </td><td class=3D"rblock">     =
1.2.  ForCES FE Model . . . . . . . . . . . . . . . . . . . . .   <span =
class=3D"insert">3</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    1.3.  Transport Mapping Layer  . . . . . . . . . . . . . . . . .  =
4</td><td> </td><td class=3D"rblock">     1.3.  Transport Mapping Layer =
. . . . . . . . . . . . . . . . .   4</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    1.4.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  =
4</td><td> </td><td class=3D"rblock">     1.4.  Definitions . . . . . . =
. . . . . . . . . . . . . . . . .   4</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">.  5</span></td><td> </td><td class=3D"rblock">   2.  =
Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   <span =
class=3D"insert">4</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    2.1.  Date, Location, and Participants . . . . . . . . . . . . <span =
class=3D"delete">.  5</span></td><td> </td><td class=3D"rblock">     =
2.1.  Date, Location, and Participants  . . . . . . . . . . . .   <span =
class=3D"insert">4</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    2.2.  Testbed Configuration  . . . . . . . . . . . . . . . . . .  =
5</td><td> </td><td class=3D"rblock">     2.2.  Testbed Configuration . =
. . . . . . . . . . . . . . . . .   5</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
      2.2.1.  Participants Access  . . . . . . . . . . . . . . . . .  =
<span class=3D"delete">6</span></td><td> </td><td class=3D"rblock">      =
 2.2.1.  Participants Access . . . . . . . . . . . . . . . . .   <span =
class=3D"insert">5</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
      2.2.2.  Testbed Configuration  . . . . . . . . . . . . . . . .  =
6</td><td> </td><td class=3D"rblock">       2.2.2.  Testbed =
Configuration . . . . . . . . . . . . . . . .   6</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  3.  Scenarios  . . . . . . . . . . . . . . . . . . . . . . . . . .  =
<span class=3D"delete">9</span></td><td> </td><td class=3D"rblock">   3. =
 Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . .   <span =
class=3D"insert">7</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    3.1.  Scenario 1 - LFB Operation . . . . . . . . . . . . . . . <span =
class=3D"delete">.  9</span></td><td> </td><td class=3D"rblock">     =
3.1.  Scenario 1 - LFB Operation  . . . . . . . . . . . . . . .   <span =
class=3D"insert">7</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    3.2.  Scenario 2 - TML with IPSec  . . . . . . . . . . . . . . .  =
<span class=3D"delete">9</span></td><td> </td><td class=3D"rblock">     =
3.2.  Scenario 2 - TML with IPSec . . . . . . . . . . . . . . .   <span =
class=3D"insert">8</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    3.3.  Scenario 3 - CE High Availability  . . . . . . . . . . . . =
<span class=3D"delete">10</span></td><td> </td><td class=3D"rblock">     =
3.3.  Scenario 3 - CE High Availability . . . . . . . . . . . .   <span =
class=3D"insert">9</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    3.4.  Scenario 4 - Packet forwarding . . . . . . . . . . . . . <span =
class=3D"delete">. 12</span></td><td> </td><td class=3D"rblock">     =
3.4.  Scenario 4 - Packet forwarding  . . . . . . . . . . . . .  <span =
class=3D"insert">10</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  4.  Test Results . . . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 15</span></td><td> </td><td class=3D"rblock">   4.  =
Test Results  . . . . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">12</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    4.1.  LFB Operation Test . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 15</span></td><td> </td><td class=3D"rblock">     =
4.1.  LFB Operation Test  . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">12</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    4.2.  TML with IPSec Test  . . . . . . . . . . . . . . . . . . . =
<span class=3D"delete">20</span></td><td> </td><td class=3D"rblock">     =
4.2.  TML with IPSec Test . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">18</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    4.3.  CE High Availability Test  . . . . . . . . . . . . . . . . =
<span class=3D"delete">21</span></td><td> </td><td class=3D"rblock">     =
4.3.  CE High Availability Test . . . . . . . . . . . . . . . .  <span =
class=3D"insert">19</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    4.4.  Packet Forwarding Test . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 22</span></td><td> </td><td class=3D"rblock">     =
4.4.  Packet Forwarding Test  . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">19</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  5.  Discussions  . . . . . . . . . . . . . . . . . . . . . . . . . =
<span class=3D"delete">25</span></td><td> </td><td class=3D"rblock">   =
5.  Discussions . . . . . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">22</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    5.1.  On Data Encapsulation Format . . . . . . . . . . . . . . <span =
class=3D"delete">. 25</span></td><td> </td><td class=3D"rblock">     =
5.1.  On Data Encapsulation Format  . . . . . . . . . . . . . .  <span =
class=3D"insert">22</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  6.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 28</span></td><td> </td><td class=3D"rblock">   6.  =
Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">24</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 29</span></td><td> </td><td class=3D"rblock">   7.  =
Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">25</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . =
<span class=3D"delete">30</span></td><td> </td><td class=3D"rblock">   =
8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">25</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  9.  Security Considerations  . . . . . . . . . . . . . . . . . . . =
<span class=3D"delete">31</span></td><td> </td><td class=3D"rblock">   =
9.  Security Considerations . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">25</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  10. References . . . . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 32</span></td><td> </td><td class=3D"rblock">   10. =
References  . . . . . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">25</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    10.1. Normative References . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 32</span></td><td> </td><td class=3D"rblock">     =
10.1.  Normative References . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">26</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
    10.2. Informative References . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 32</span></td><td> </td><td class=3D"rblock">     =
10.2.  Informative References . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">26</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <span =
class=3D"delete">. 34</span></td><td> </td><td class=3D"rblock">   =
Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  <span =
class=3D"insert">27</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">1. =
 Introduction</td><td> </td><td class=3D"right">1.  Introduction</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0009" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  This document capture<span class=3D"delete">d</span> results of the =
second interoperability test of</td><td> </td><td class=3D"rblock">   =
This document capture<span class=3D"insert">s</span> results of the =
second interoperability test of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the Forwarding and Control Element Separation (ForCES) which =
took</td><td> </td><td class=3D"right">   the Forwarding and Control =
Element Separation (ForCES) which took</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
place February 24-25, 2011 in the Internet Technology Lab (ITL) =
of</td><td> </td><td class=3D"right">   place February 24-25, 2011 in =
the Internet Technology Lab (ITL) of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Zhejiang Gongshang University, China.  The test involved =
protocol</td><td> </td><td class=3D"right">   Zhejiang Gongshang =
University, China.  The test involved protocol</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
elements described in several documents namely:</td><td> </td><td =
class=3D"right">   elements described in several documents =
namely:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   - ForCES Protocol [RFC5810]</td><td> </td><td class=3D"right">      - =
ForCES Protocol [RFC5810]</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0010" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     - ForCES Forwarding Element <span class=3D"delete">(FE)</span> =
Model [RFC5812]</td><td> </td><td class=3D"rblock">      - ForCES =
Forwarding Element Model [RFC5812]</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     - ForCES Transport Mapping Layer <span =
class=3D"delete">(TML)</span> [RFC5811]</td><td> </td><td =
class=3D"rblock">      - ForCES Transport Mapping Layer =
[RFC5811]</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The test also involved protocol elements described in the then-</td><td> =
</td><td class=3D"right">   The test also involved protocol elements =
described in the then-</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
current versions of two Internet-Drafts.  Although these =
documents</td><td> </td><td class=3D"right">   current versions of two =
Internet-Drafts.  Although these documents</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
have subsequently been revised and advanced, it is important to</td><td> =
</td><td class=3D"right">   have subsequently been revised and advanced, =
it is important to</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
understand which versions of the work were used during this =
test.</td><td> </td><td class=3D"right">   understand which versions of =
the work were used during this test.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0011" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The then-current Internet-Drafts <span =
class=3D"delete">we</span>re:</td><td> </td><td class=3D"rblock">   The =
then-current Internet-Drafts <span class=3D"insert">a</span>re:</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   - ForCES Logical Function Block (LFB) Library</td><td> </td><td =
class=3D"right">      - ForCES Logical Function Block (LFB) =
Library</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   [I-D.ietf-forces-lfb-lib-03].</td><td> </td><td class=3D"right">      =
[I-D.ietf-forces-lfb-lib-03].</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   - ForCES Intra-NE High Availability =
[I-D.ietf-forces-ceha-00].</td><td> </td><td class=3D"right">      - =
ForCES Intra-NE High Availability [I-D.ietf-forces-ceha-00].</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0012" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">Up to date, the 'ForCES Logical Function Block =
(LFB) Library'</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   document has been publilshed =
by IETF as RFC 6956.</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                                                        =
</td><td> </td><td class=3D"rblock"></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Three independent ForCES implementations participated in the =
test.</td><td> </td><td class=3D"right">   Three independent ForCES =
implementations participated in the test.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Scenarios of ForCES LFB Operation, TML with IPSec, CE High</td><td> =
</td><td class=3D"right">   Scenarios of ForCES LFB Operation, TML with =
IPSec, CE High</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0013" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Availability, and Packet Forwarding <span class=3D"delete">were</span> =
constructed.  Series of</td><td> </td><td class=3D"rblock">   =
Availability, and Packet Forwarding <span class=3D"insert">are</span> =
constructed.  Series of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  testing items for every scenario <span class=3D"delete">were</span> =
carried out and</td><td> </td><td class=3D"rblock">   testing items for =
every scenario <span class=3D"insert">are</span> carried out and =
interoperability</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  interoperability results <span class=3D"delete">were</span> achieved.  =
Popular packet analyzers</td><td> </td><td class=3D"rblock">   results =
<span class=3D"insert">are</span> achieved.  Popular packet analyzers =
<span class=3D"insert">Ethereal/</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">Ethereal/Wireshark[Ethereal]</span> and =
Tcpdump[Tcpdump] <span class=3D"delete">were</span> used to =
verify</td><td> </td><td class=3D"rblock"><span class=3D"insert">   =
Wireshark[Ethereal]</span> and Tcpdump[Tcpdump] <span =
class=3D"insert">are</span> used to verify the wire</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  the wire results.</td><td> </td><td class=3D"rblock">   =
results.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
This document is an update to RFC 6053, which captured the results =
of</td><td> </td><td class=3D"right">   This document is an update to =
RFC 6053, which captured the results of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the first ForCES interoperability test.  The first test on ForCES =
was</td><td> </td><td class=3D"right">   the first ForCES =
interoperability test.  The first test on ForCES was</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
held in July 2008 at the University of Patras, Greece.  That =
test</td><td> </td><td class=3D"right">   held in July 2008 at the =
University of Patras, Greece.  That test</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
focused on validating the basic semantics of the ForCES protocol =
and</td><td> </td><td class=3D"right">   focused on validating the basic =
semantics of the ForCES protocol and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
ForCES FE model.</td><td> </td><td class=3D"right">   ForCES FE =
model.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">1.1.  ForCES Protocol</td><td> </td><td =
class=3D"right">1.1.  ForCES Protocol</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0014" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The ForCES protocol works in a master-slave mode in which <span =
class=3D"delete">Forwarding</span></td><td> </td><td class=3D"rblock">   =
The ForCES protocol works in a master-slave mode in which <span =
class=3D"insert">FEs</span> are</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   Elements (FEs)</span> are =
slaves and <span class=3D"delete">Control Elements (CEs)</span> are =
masters.</td><td> </td><td class=3D"rblock">   slaves and <span =
class=3D"insert">CEs</span> are masters.  The protocol includes commands =
for</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The protocol includes commands for transport of Logical =
Function</td><td> </td><td class=3D"rblock">   transport of Logical =
Function Block (LFB) configuration information,</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Block (LFB) configuration information, association setup, status, =
and</td><td> </td><td class=3D"rblock">   association setup, status, and =
event notifications, etc.  The reader</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  event notifications, etc.  The reader is encouraged to read =
the</td><td> </td><td class=3D"rblock">   is encouraged to read the =
ForCES protocol specification [RFC5810] for</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  ForCES protocol specification [RFC5810] for further =
information.</td><td> </td><td class=3D"rblock">   further =
information.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">1.2.  ForCES FE Model</td><td> </td><td =
class=3D"right">1.2.  ForCES FE Model</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0015" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                                                        =
</td><td> </td><td class=3D"rblock">   The ForCES <span =
class=3D"insert">FE</span> model [RFC5812]  presents a formal way to =
define FE</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The ForCES <span class=3D"delete">Forwarding Element (FE)</span> model =
[RFC5812] presents a formal</td><td> </td><td class=3D"rblock">   =
Logical Function Blocks (LFBs) using XML.  LFB configuration</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  way to define FE Logical Function Blocks (LFBs) using XML.  =
LFB</td><td> </td><td class=3D"rblock">   components, capabilities, and =
associated events are defined when the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  configuration components, capabilities, and associated events =
are</td><td> </td><td class=3D"rblock">   LFB is formally created.  The =
LFBs within the FE are accordingly</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  defined when the LFB is formally created.  The LFBs within the FE =
are</td><td> </td><td class=3D"rblock">   controlled in a standardized =
way by the ForCES protocol.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  accordingly controlled in a standardized way by the ForCES =
protocol.</td><td> </td><td class=3D"rblock"></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">1.3.  Transport Mapping Layer</td><td> </td><td =
class=3D"right">1.3.  Transport Mapping Layer</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The ForCES Transport Mapping Layer (TML) transports the ForCES</td><td> =
</td><td class=3D"right">   The ForCES Transport Mapping Layer (TML) =
transports the ForCES</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Protocol Layer (PL) messages.  The TML is where the issues of how =
to</td><td> </td><td class=3D"right">   Protocol Layer (PL) messages.  =
The TML is where the issues of how to</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
achieve transport level reliability, congestion control, =
multicast,</td><td> </td><td class=3D"right">   achieve transport level =
reliability, congestion control, multicast,</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
ordering, etc are handled.  It is expected that more than one =
TML</td><td> </td><td class=3D"right">   ordering, etc are handled.  It =
is expected that more than one TML</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
will be standardized.  RFC 5811 specifies an SCTP-Based =
Transport</td><td> </td><td class=3D"right">   will be standardized.  =
RFC 5811 specifies an SCTP-Based Transport</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Mapping Layer (TML) for ForCES protocol, which is a mandated TML =
for</td><td> </td><td class=3D"right">   Mapping Layer (TML) for ForCES =
protocol, which is a mandated TML for</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
ForCES.  See RFC 5811 for more details.</td><td> </td><td =
class=3D"right">   ForCES.  See RFC 5811 for more details.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno"></td><td class=3D"left"></td><td> =
</td><td class=3D"right"></td><td class=3D"lineno"></td></tr>=0A=
      <tr bgcolor=3D"gray" ><td></td><th><a name=3D"part-l2" =
/><small>skipping to change at</small><em> page 5, line 16</em></th><th> =
</th><th><a name=3D"part-r2" /><small>skipping to change at</small><em> =
page 4, line 37</em></th><td></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">2.1.  Date, Location, and Participants</td><td> </td><td =
class=3D"right">2.1.  Date, Location, and Participants</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The second ForCES interoperability test meeting was held by =
IETF</td><td> </td><td class=3D"right">   The second ForCES =
interoperability test meeting was held by IETF</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
ForCES Working Group on February 24-25, 2011, and was chaired =
by</td><td> </td><td class=3D"right">   ForCES Working Group on February =
24-25, 2011, and was chaired by</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Jamal Hadi Salim.  Three independent ForCES implementations</td><td> =
</td><td class=3D"right">   Jamal Hadi Salim.  Three independent ForCES =
implementations</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
participated in the test:</td><td> </td><td class=3D"right">   =
participated in the test:</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  Zhejiang Gongshang University/Hangzhou BAUD Corporation of</td><td> =
</td><td class=3D"right">   o  Zhejiang Gongshang University/Hangzhou =
BAUD Corporation of</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   Information and Networks Technology (Hangzhou BAUD =
Networks),</td><td> </td><td class=3D"right">      Information and =
Networks Technology (Hangzhou BAUD Networks),</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0016" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     China.  This implementation is referred to as <span =
class=3D"delete">"ZJSU"</span> or in some</td><td> </td><td =
class=3D"rblock">      China.  This implementation is referred to as =
<span class=3D"insert">"China"</span> or in some</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     cases <span class=3D"delete">"Z"</span> in the document for the =
sake of brevity.</td><td> </td><td class=3D"rblock">      cases <span =
class=3D"insert">"C"</span> in the document for the sake of =
brevity.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  NTT Corporation, Japan.  This implementation is referred to =
as</td><td> </td><td class=3D"right">   o  NTT Corporation, Japan.  This =
implementation is referred to as</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0017" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     "<span class=3D"delete">NTT" or in some cases "N</span>" in the =
document for the sake of</td><td> </td><td class=3D"rblock">      "<span =
class=3D"insert">Japan" or in some cases "J</span>" in the document for =
the sake of</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   brevity.</td><td> </td><td class=3D"right">      brevity.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  The University of Patras, Greece.  This implementation is =
referred</td><td> </td><td class=3D"right">   o  The University of =
Patras, Greece.  This implementation is referred</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0018" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     to as <span class=3D"delete">"UoP"</span> or in some cases <span =
class=3D"delete">"P"</span> in the document for the sake of</td><td> =
</td><td class=3D"rblock">      to as <span =
class=3D"insert">"Greece"</span> or in some cases <span =
class=3D"insert">"G"</span> in the document for the sake</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
     brevity.</td><td> </td><td class=3D"rblock">      of =
brevity.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Two other organizations, Mojatatu Networks and Hangzhou BAUD =
Networks</td><td> </td><td class=3D"right">   Two other organizations, =
Mojatatu Networks and Hangzhou BAUD Networks</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Corporation, which independently extended two different well =
known</td><td> </td><td class=3D"right">   Corporation, which =
independently extended two different well known</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
public domain protocol analyzers, Ethereal/Wireshark [Ethereal] =
and</td><td> </td><td class=3D"right">   public domain protocol =
analyzers, Ethereal/Wireshark [Ethereal] and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Tcpdump [Tcpdump], also participated in the interop test.  During =
the</td><td> </td><td class=3D"right">   Tcpdump [Tcpdump], also =
participated in the interop test.  During the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
interoperability test, the two protocol analyzers were used to =
verify</td><td> </td><td class=3D"right">   interoperability test, the =
two protocol analyzers were used to verify</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the validity of ForCES protocol messages and in some cases =
semantics.</td><td> </td><td class=3D"right">   the validity of ForCES =
protocol messages and in some cases semantics.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Some issues related to interoperability among implementations =
were</td><td> </td><td class=3D"right">   Some issues related to =
interoperability among implementations were</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
discovered.  Most of the issues were solved on site during the =
test.</td><td> </td><td class=3D"right">   discovered.  Most of the =
issues were solved on site during the test.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The most contentious issue found was on the format of =
encapsulation</td><td> </td><td class=3D"right">   The most contentious =
issue found was on the format of encapsulation</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
for protocol TLV (Refer to Section 5.1 ).</td><td> </td><td =
class=3D"right">   for protocol TLV (Refer to Section 5.1 ).</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Some errata related to ForCES document were found by the</td><td> =
</td><td class=3D"right">   Some errata related to ForCES document were =
found by the</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
interoperability test.  The errata has been reported to related =
IETF</td><td> </td><td class=3D"right">   interoperability test.  The =
errata has been reported to related IETF</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
RFCs.</td><td> </td><td class=3D"right">   RFCs.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
At times, interoperability testing was exercised between two =
instead</td><td> </td><td class=3D"right">   At times, interoperability =
testing was exercised between two instead</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
of all three representative implementations due to a third one</td><td> =
</td><td class=3D"right">   of all three representative implementations =
due to a third one</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
lacking a specific feature; however, in ensuing discussions, =
all</td><td> </td><td class=3D"right">   lacking a specific feature; =
however, in ensuing discussions, all</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0019" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  implementers mentioned they <span class=3D"delete">would</span> be =
implementing any missing</td><td> </td><td class=3D"rblock">   =
implementers mentioned they <span class=3D"insert">will</span> be =
implementing any missing features</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  features in the future.</td><td> </td><td class=3D"rblock">   in the =
future.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">2.2.  Testbed Configuration</td><td> </td><td =
class=3D"right">2.2.  Testbed Configuration</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0020" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">                                                        =
                 </span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">2.2.1.  Participants Access</td><td> </td><td =
class=3D"right">2.2.1.  Participants Access</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0021" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">NTT</span> and <span =
class=3D"delete">ZJSU</span> physically attended on site at the Internet =
Technology</td><td> </td><td class=3D"rblock">   <span =
class=3D"insert">Japan</span> and <span class=3D"insert">China</span> =
physically attended on site at the Internet</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Lab (ITL) of Zhejiang Gongshang University in China.  The =
University</td><td> </td><td class=3D"rblock">   Technology Lab (ITL) of =
Zhejiang Gongshang University in China.  The</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  of Patras implementation joined remotely from Greece.  The =
chair,</td><td> </td><td class=3D"rblock">   University of Patras =
implementation joined remotely from Greece.  The</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Jamal Hadi Salim, joined remotely from Canada by using the =
Teamviewer</td><td> </td><td class=3D"rblock">   chair, Jamal Hadi =
Salim, joined remotely from Canada by using the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  as the monitoring tool[Teamviewer].  The approach is as shown =
in</td><td> </td><td class=3D"rblock">   Teamviewer as the monitoring =
tool[Teamviewer].  The approach is as</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Figure 1.  In the figure, FE/CE refers to FE or CE that the</td><td> =
</td><td class=3D"rblock">   shown in Figure 1.  In the figure, FE/CE =
refers to FE or CE that the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
implementer may act alternatively.</td><td> </td><td class=3D"right">   =
implementer may act alternatively.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
     +---------+     +----+                    +----------+</td><td> =
</td><td class=3D"right">        +---------+     +----+                  =
  +----------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
     |  FE/CE  |     |    |                +---|Monitoring|</td><td> =
</td><td class=3D"right">        |  FE/CE  |     |    |                =
+---|Monitoring|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0022" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
       |  <span class=3D"delete">ZJSU</span>   |-----|    |    =
/\/\/\/\/\  |   |(TeamViewer)</td><td> </td><td class=3D"rblock">        =
|  <span class=3D"insert">China</span>  |-----|    |    /\/\/\/\/\  |   =
|(TeamViewer)</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
       +---------+     |    |    \Internet/  |   | <span =
class=3D"delete">Mojatatu</span> |</td><td> </td><td class=3D"rblock">   =
     +---------+     |    |    \Internet/  |   |  <span =
class=3D"insert">Canada</span>  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                     |LAN |----/        \--|   +----------+</td><td> =
</td><td class=3D"right">                        |LAN |----/        \--| =
  +----------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
     +---------+     |    |    \/\/\/\/\/  |   +----------+</td><td> =
</td><td class=3D"right">        +---------+     |    |    \/\/\/\/\/  | =
  +----------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
     |  FE/CE  |-----|    |                |   |  FE/CE   |</td><td> =
</td><td class=3D"right">        |  FE/CE  |-----|    |                | =
  |  FE/CE   |</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0023" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
       |  <span class=3D"delete"> NTT   |     |    |                =
+---|   UoP  </span>  |</td><td> </td><td class=3D"rblock">        |  =
<span class=3D"insert">Japan  |     |    |                +---|  =
Greece</span>  |</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
     +---------+     +----+                    +----------+</td><td> =
</td><td class=3D"right">        +---------+     +----+                  =
  +----------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                  Figure 1: Access for Participants</td><td> </td><td =
class=3D"right">                     Figure 1: Access for =
Participants</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
As specified in RFC 5811, all CEs and FEs shall implement IPSec</td><td> =
</td><td class=3D"right">   As specified in RFC 5811, all CEs and FEs =
shall implement IPSec</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
security in the TML.</td><td> </td><td class=3D"right">   security in =
the TML.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
On the internet boundary, gateways used must allow for IPSec, =
SCTP</td><td> </td><td class=3D"right">   On the internet boundary, =
gateways used must allow for IPSec, SCTP</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
protocol and SCTP ports as defined in the ForCES SCTP-TML [RFC5811] =
.</td><td> </td><td class=3D"right">   protocol and SCTP ports as =
defined in the ForCES SCTP-TML [RFC5811] .</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">2.2.2.  Testbed Configuration</td><td> </td><td =
class=3D"right">2.2.2.  Testbed Configuration</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0024" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  CEs and FEs from <span class=3D"delete">ZJSU</span> and <span =
class=3D"delete">NTT</span> implementations were physically =
located</td><td> </td><td class=3D"rblock">   CEs and FEs from <span =
class=3D"insert">China</span> and <span class=3D"insert">Japan</span> =
implementations were physically</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  within the ITL Lab of Zhejiang Gongshang University and =
connected</td><td> </td><td class=3D"rblock">   located within the ITL =
Lab of Zhejiang Gongshang University and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  together using Ethernet switches.  The configuration can be seen =
in</td><td> </td><td class=3D"rblock">   connected together using =
Ethernet switches.  The configuration can be</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Figure 2.  In the figure, the SmartBits <span =
class=3D"delete">was</span> a third-party supplied</td><td> </td><td =
class=3D"rblock">   seen in Figure 2.  In the figure, the SmartBits =
<span class=3D"insert">is</span> a third-party</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  routing protocol testing machine, which <span =
class=3D"delete">acted</span> as a router running</td><td> </td><td =
class=3D"rblock">   supplied routing protocol testing machine, which =
<span class=3D"insert">acts</span> as a router</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  OSPF and RIP and <span class=3D"delete">exchanged</span> routing =
protocol messages with ForCES</td><td> </td><td class=3D"rblock">   =
running OSPF and RIP and <span class=3D"insert">exchanges</span> routing =
protocol messages with</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  routers in the network.  <span class=3D"delete">Connection to =
the</span> Internet <span class=3D"delete">was</span> via an =
ADSL</td><td> </td><td class=3D"rblock">   ForCES routers in the =
network.  <span class=3D"insert">The</span> Internet <span =
class=3D"insert">is connected</span> via an ADSL</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
channel.</td><td> </td><td class=3D"right">   channel.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                           /\/\/\/\/\</td><td> </td><td class=3D"right"> =
                             /\/\/\/\/\</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                           \Internet/</td><td> </td><td class=3D"right"> =
                             \Internet/</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                           /        \</td><td> </td><td class=3D"right"> =
                             /        \</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                           \/\/\/\/\/</td><td> </td><td class=3D"right"> =
                             \/\/\/\/\/</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |</td><td> </td><td class=3D"right">      =
                            |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0025" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                 |(ADSL)</td><td> </td><td =
class=3D"rblock">                                  |<span =
class=3D"insert">124.90.146.218 </span>(ADSL)</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |</td><td> </td><td class=3D"right">      =
                            |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+------------------------------------------------------------------+</td>=
<td> </td><td class=3D"right">   =
+------------------------------------------------------------------+</td>=
<td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|                      LAN  (10.20.0.0/24)                         =
|</td><td> </td><td class=3D"right">   |                      LAN  =
(10.20.0.0/24)                         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+------------------------------------------------------------------+</td>=
<td> </td><td class=3D"right">   =
+------------------------------------------------------------------+</td>=
<td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   |        |        |               |               |         =
|</td><td> </td><td class=3D"right">      |        |        |            =
   |               |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   |        |        |               |               |         =
|</td><td> </td><td class=3D"right">      |        |        |            =
   |               |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   |.222    |.230    |.221           |.179           |.231     =
|.220</td><td> </td><td class=3D"right">      |.222    |.230    |.221    =
       |.179           |.231     |.220</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+  +-----+  +-----+         +-----+         +-----+ =
+---------+</td><td> </td><td class=3D"right">   +-----+  +-----+  =
+-----+         +-----+         +-----+ +---------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
| CE  |  | CE  |  |     |         |     |         |     | | =
Protocol|</td><td> </td><td class=3D"right">   | CE  |  | CE  |  |     | =
        |     |         |     | | Protocol|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0026" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">|ZJSU |  | NTT |</span>  | FE1 |.1     .2| FE  =
|.1     .2| FE2 | | Analyzer|</td><td> </td><td class=3D"rblock">   =
<span class=3D"insert">|China|  |Japan|</span>  | FE1 |.1     .2| FE  =
|.1     .2| FE2 | | Analyzer|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  +-----+  +-----+  <span class=3D"delete">|ZJSU |---------| NTT =
|---------|ZJSU |</span> +---------+</td><td> </td><td class=3D"rblock"> =
  +-----+  +-----+  <span =
class=3D"insert">|China|---------|Japan|---------|China|</span> =
+---------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        +---------|     |192.169. |     | 192.168.|     =
|------+</td><td> </td><td class=3D"right">           +---------|     =
|192.169. |     | 192.168.|     |------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        |      .2 +-----+ 20.0.24 +-----+  30.0/24+-----+ .2   =
|</td><td> </td><td class=3D"right">           |      .2 +-----+ 20.0.24 =
+-----+  30.0/24+-----+ .2   |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        |         .12|                               |.12      =
|</td><td> </td><td class=3D"right">           |         .12|            =
                   |.12      |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        |            |                               |         =
|</td><td> </td><td class=3D"right">           |            |            =
                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
  192.168.50.0/24    |                               =
|192.168.60.0/24</td><td> </td><td class=3D"right">     192.168.50.0/24  =
  |                               |192.168.60.0/24</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        |       192.168.10.0/24              192.168.40.0/24   =
|</td><td> </td><td class=3D"right">           |       192.168.10.0/24   =
           192.168.40.0/24   |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
     .1 |            |.11                            |.11      =
|.1</td><td> </td><td class=3D"right">        .1 |            |.11       =
                     |.11      |.1</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   +--------+     +--------------------------------------+ =
+--------+</td><td> </td><td class=3D"right">      +--------+     =
+--------------------------------------+ +--------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   |Terminal|     |               Smartbits              | =
|Terminal|</td><td> </td><td class=3D"right">      |Terminal|     |      =
         Smartbits              | |Terminal|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   +--------+     +--------------------------------------+ =
+--------+</td><td> </td><td class=3D"right">      +--------+     =
+--------------------------------------+ +--------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
      Figure 2: Testbed Configuration Located in ITL Lab,China</td><td> =
</td><td class=3D"right">         Figure 2: Testbed Configuration =
Located in ITL Lab,China</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0027" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">CE</span> and <span class=3D"delete">FE from =
the UoP implementation</span> were located within the</td><td> </td><td =
class=3D"rblock">   <span class=3D"insert">Hardware</span> and <span =
class=3D"insert">Software (CE and FE) of Greece those</span> were =
located within</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  University of Patras, Greece, <span class=3D"delete">and</span> were =
connected together using LAN</td><td> </td><td class=3D"rblock">   the =
University of Patras, Greece, were connected together using LAN</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  as shown in Figure 3.  <span class=3D"delete">Connection to the</span> =
Internet <span class=3D"delete">was</span> via a VPN</td><td> </td><td =
class=3D"rblock">   as shown in Figure 3.  <span =
class=3D"insert">The</span> Internet <span class=3D"insert">is =
connected</span> via a VPN channel.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  channel.</td><td> </td><td class=3D"rblock"></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            /\/\/\/\/\</td><td> </td><td =
class=3D"right">                               /\/\/\/\/\</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            \Internet/</td><td> </td><td =
class=3D"right">                               \Internet/</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            /        \</td><td> </td><td =
class=3D"right">                               /        \</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            \/\/\/\/\/</td><td> </td><td =
class=3D"right">                               \/\/\/\/\/</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0028" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                  |</td><td> </td><td class=3D"rblock">  =
                             |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                  <span =
class=3D"delete">|(VPN)</span></td><td> </td><td class=3D"rblock">       =
                            <span =
class=3D"insert">|150.140.254.110(VPN)</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                |</td><td> </td><td class=3D"right">     =
                              |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
             +------------------------------------+</td><td> </td><td =
class=3D"right">                =
+------------------------------------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
             |                LAN                 |</td><td> </td><td =
class=3D"right">                |                LAN                 =
|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
             +------------------------------------+</td><td> </td><td =
class=3D"right">                =
+------------------------------------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                  |           |             |</td><td> </td><td =
class=3D"right">                     |           |             |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                  |           |             |</td><td> </td><td =
class=3D"right">                     |           |             |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
              +------+    +--------+     +------+</td><td> </td><td =
class=3D"right">                 +------+    +--------+     =
+------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
              |  FE  |    |Protocol|     |  CE  |</td><td> </td><td =
class=3D"right">                 |  FE  |    |Protocol|     |  CE  =
|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0029" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                |<span class=3D"delete"> UoP  |    |Analyzer|     |  UoP =
</span>|</td><td> </td><td class=3D"rblock">                 |<span =
class=3D"insert">Greece|    |Analyzer|     |Greece</span>|</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
              +------+    +--------+     +------+</td><td> </td><td =
class=3D"right">                 +------+    +--------+     =
+------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    Figure 3: Testbed Configuration Located in the University =
of</td><td> </td><td class=3D"right">       Figure 3: Testbed =
Configuration Located in the University of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            Patras,Greece</td><td> </td><td =
class=3D"right">                               Patras,Greece</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0030" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  All above testbed configurations <span class=3D"delete">were</span> =
then <span class=3D"delete">able to</span> satisfy</td><td> </td><td =
class=3D"rblock">   All above testbed configurations <span =
class=3D"insert">can</span> then satisfy requirements of all</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  requirements of all the interoperability test scenarios that <span =
class=3D"delete">were</span></td><td> </td><td class=3D"rblock">   the =
interoperability test scenarios that <span class=3D"insert">are</span> =
mentioned in this</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  mentioned in this document.</td><td> </td><td class=3D"rblock">   =
document.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">3. =
 Scenarios</td><td> </td><td class=3D"right">3.  Scenarios</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">3.1.  Scenario 1 - LFB Operation</td><td> </td><td =
class=3D"right">3.1.  Scenario 1 - LFB Operation</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0031" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  This scenario <span class=3D"delete">was</span> to test the =
interoperability on LFB operations</td><td> </td><td class=3D"rblock">   =
This scenario <span class=3D"insert">is</span> to test the =
interoperability on LFB operations among</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  among the participants.  The connection diagram for the =
participants</td><td> </td><td class=3D"rblock">   the participants.  =
The connection diagram for the participants is as</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  is as shown in Figure 4.</td><td> </td><td class=3D"rblock">   shown =
in Figure 4.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0032" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   +------+    +------+    +------+    +------+    +------+    =
+------+</td><td> </td><td class=3D"rblock">   +------+    +------+    =
+------+    +------+    +------+    +------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   |  CE  |    |  CE  |    |  CE  |    |  CE  |    |  CE  |    |  CE  =
|</td><td> </td><td class=3D"rblock">   |  CE  |    |  CE  |    |  CE  | =
   |  CE  |    |  CE  |    |  CE  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   | <span class=3D"delete">ZJSU</span> |    | <span =
class=3D"delete">NTT  |    | ZJSU |    |  UoP |    |  NTT |    |  =
UoP</span> |</td><td> </td><td class=3D"rblock">   | <span =
class=3D"insert">China|</span>    | <span class=3D"insert">Japan|</span> =
   | <span class=3D"insert">China|    |Greece|</span>    | <span =
class=3D"insert">Japan|    |Greece|</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   +------+    +------+    +------+    +------+    +------+    =
+------+</td><td> </td><td class=3D"rblock">   +------+    +------+    =
+------+    +------+    +------+    +------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
      |           |           |           |           |           =
|</td><td> </td><td class=3D"rblock">      |           |           |     =
      |           |           |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
      |           |           |           |           |           =
|</td><td> </td><td class=3D"rblock">      |           |           |     =
      |           |           |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   +------+    +------+    +------+    +------+    +------+    =
+------+</td><td> </td><td class=3D"rblock">   +------+    +------+    =
+------+    +------+    +------+    +------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   |  FE  |    |  FE  |    |  FE  |    |  FE  |    |  FE  |    |  FE  =
|</td><td> </td><td class=3D"rblock">   |  FE  |    |  FE  |    |  FE  | =
   |  FE  |    |  FE  |    |  FE  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   | <span class=3D"delete">NTT  |    | ZJSU |    | UoP  |    | ZJSU |   =
 |  UoP</span> |    |  <span class=3D"delete">NTT</span> |</td><td> =
</td><td class=3D"rblock">   <span class=3D"insert">|Japan</span> |    =
<span class=3D"insert">|China</span> |    <span =
class=3D"insert">|Greece|    |China</span> |    <span =
class=3D"insert">|Greece|    |Japan</span> |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
   +------+    +------+    +------+    +------+    +------+    =
+------+</td><td> </td><td class=3D"rblock">   +------+    +------+    =
+------+    +------+    +------+    +------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                Figure 4: Scenario for LFB Operation</td><td> </td><td =
class=3D"right">                   Figure 4: Scenario for LFB =
Operation</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
In order to make interoperability more credible, the three</td><td> =
</td><td class=3D"right">   In order to make interoperability more =
credible, the three</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0033" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  implementers <span class=3D"delete">were</span> required to carry out =
the test in a way acting as</td><td> </td><td class=3D"rblock">   =
implementers <span class=3D"insert">are</span> required to carry out the =
test in a way acting as CE</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  CE or FE alternatively.  As a result, every LFB operation <span =
class=3D"delete">was</span></td><td> </td><td class=3D"rblock">   or FE =
alternatively.  As a result, every LFB operation <span =
class=3D"insert">is</span> combined</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  combined with 6 scenarios, as shown by Figure 4.</td><td> </td><td =
class=3D"rblock">   with 6 scenarios, as shown by Figure 4.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0034" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The test scenario <span class=3D"delete">wa</span>s designed with the =
following purposes:</td><td> </td><td class=3D"rblock">   The test =
scenario <span class=3D"insert">i</span>s designed with the following =
purposes:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0035" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Firstly, the scenario <span class=3D"delete">wa</span>s designed to =
verify all kinds of protocol</td><td> </td><td class=3D"rblock">   =
Firstly, the scenario <span class=3D"insert">i</span>s designed to =
verify all kinds of protocol</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
messages with their complex data formats, which are defined in =
RFC</td><td> </td><td class=3D"right">   messages with their complex =
data formats, which are defined in RFC</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0036" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  5810.  Specially, we tr<span class=3D"delete">ied</span> to verify the =
data format of a PATH-DATA</td><td> </td><td class=3D"rblock">   5810.  =
Specially, we tr<span class=3D"insert">y</span> to verify the data =
format of a PATH-DATA</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
with nested PATH-DATAs, and the operation(SET, GET, DEL) of an =
array</td><td> </td><td class=3D"right">   with nested PATH-DATAs, and =
the operation(SET, GET, DEL) of an array</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
or an array with a nested array.</td><td> </td><td class=3D"right">   or =
an array with a nested array.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0037" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Secondly, the scenario <span class=3D"delete">was</span> designed to =
verify the definition of</td><td> </td><td class=3D"rblock">   Secondly, =
the scenario <span class=3D"insert">is</span> designed to verify the =
definition of ForCES</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  ForCES LFB Library [I-D.ietf-forces-lfb-lib-03], which <span =
class=3D"delete">defined</span> a base</td><td> </td><td =
class=3D"rblock">   LFB Library [I-D.ietf-forces-lfb-lib-03], which =
<span class=3D"insert">defines</span> a base set of</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  set of ForCES LFB classes for typical router functions.  =
Successful</td><td> </td><td class=3D"rblock">   ForCES LFB classes for =
typical router functions.  Successful test</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  test under this scenario <span class=3D"delete">may help</span> the =
validity of the LFB</td><td> </td><td class=3D"rblock">   under this =
scenario <span class=3D"insert">also means</span> the validity of the =
LFB definitions.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  definitions.</td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">3.2.  Scenario 2 - TML with IPSec</td><td> </td><td =
class=3D"right">3.2.  Scenario 2 - TML with IPSec</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0038" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  This scenario <span class=3D"delete">was</span> designed to implement =
a TML with IPSec, which is</td><td> </td><td class=3D"rblock">   This =
scenario <span class=3D"insert">is</span> designed to implement a TML =
with IPSec, which is the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  the requirement by RFC 5811.  TML with IPSec was not implemented =
in</td><td> </td><td class=3D"rblock">   requirement by RFC 5811.  TML =
with IPSec was not implemented in the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  the first ForCES interoperability test as reported by RFC 6053.  =
For</td><td> </td><td class=3D"rblock">   first ForCES interoperability =
test as reported by RFC 6053.  For this</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  this reason, in the second interoperability test, we =
specifically</td><td> </td><td class=3D"rblock">   reason, in the second =
interoperability test, we specifically designed</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  designed the test scenario to verify the TML over IPSec =
channel.</td><td> </td><td class=3D"rblock">   the test scenario to =
verify the TML over IPSec channel.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
In this scenario, tests on LFB operations for Scenario 1 were</td><td> =
</td><td class=3D"right">   In this scenario, tests on LFB operations =
for Scenario 1 were</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
repeated with the difference that TML was secured via IPSec.  =
This</td><td> </td><td class=3D"right">   repeated with the difference =
that TML was secured via IPSec.  This</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0039" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  setup scenario <span class=3D"delete">allowed</span> us to verify =
whether all interactions between</td><td> </td><td class=3D"rblock">   =
setup scenario <span class=3D"insert">allows</span> us to verify whether =
all interactions between</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  CE and FE <span class=3D"delete">could</span> be made correctly under =
an IPSec TML environment.</td><td> </td><td class=3D"rblock">   CE and =
FE <span class=3D"insert">can</span> be made correctly under an IPSec =
TML environment.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0040" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The connection diagram for this scenario <span =
class=3D"delete">was</span> shown as Figure 5.</td><td> </td><td =
class=3D"rblock">   The connection diagram for this scenario <span =
class=3D"insert">is</span> shown as Figure 5.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Because <span class=3D"delete">an unfortunate problem with the test =
system in UoP prevented</span></td><td> </td><td class=3D"rblock">   =
Because of <span class=3D"insert">system deficiency to deploy</span> =
IPSec over <span class=3D"insert">TML in Greece, the</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   the deployment</span> of =
IPSec over <span class=3D"delete">TML, this test</span> only took place =
between</td><td> </td><td class=3D"rblock"><span class=3D"insert">   =
text</span> only took place between <span class=3D"insert">China</span> =
and <span class=3D"insert">Japan.</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">the test systems in ZJSU</span> and <span =
class=3D"delete">NTT.</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0041" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                +------+                 +------+</td><td> </td><td =
class=3D"rblock">              +------+                 +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                |  CE  |                 |  CE  |</td><td> </td><td =
class=3D"rblock">              |  CE  |                 |  CE  |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                | <span class=3D"delete">ZJSU |                 |  =
NTT</span> |</td><td> </td><td class=3D"rblock">              | <span =
class=3D"insert">China|</span>                 | <span =
class=3D"insert">Japan|</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                +------+                 +------+</td><td> </td><td =
class=3D"rblock">              +------+                 +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                   |                        |</td><td> </td><td =
class=3D"rblock">                 |                        |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                   |TML over IPSec          |TML over IPSec</td><td> =
</td><td class=3D"rblock">                 |TML over IPSec          |TML =
over IPSec</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                +------+                 +------+</td><td> </td><td =
class=3D"rblock">              +------+                 +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                |  FE  |                 |  FE  |</td><td> </td><td =
class=3D"rblock">              |  FE  |                 |  FE  |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                | <span class=3D"delete">NTT  |                 | =
ZJSU</span> |</td><td> </td><td class=3D"rblock">              <span =
class=3D"insert">|Japan</span> |                 <span =
class=3D"insert">|China</span> |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                +------+                 +------+</td><td> </td><td =
class=3D"rblock">              +------+                 +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
      Figure 5: Scenario for LFB Operation with TML over IPSec</td><td> =
</td><td class=3D"right">         Figure 5: Scenario for LFB Operation =
with TML over IPSec</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0042" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In this scenario, ForCES TML was run over <span class=3D"delete">the =
</span>IPSec channel.</td><td> </td><td class=3D"rblock">   In this =
scenario, ForCES TML was run over IPSec channel.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Implementers joined in this interoperability have used the same</td><td> =
</td><td class=3D"right">   Implementers joined in this interoperability =
have used the same</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0043" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  third-party software 'racoon' to <span =
class=3D"delete">establish</span> the IPSec channel.  <span =
class=3D"delete">The</span></td><td> </td><td class=3D"rblock">   =
third-party software 'racoon' to <span class=3D"insert">have =
established</span> the IPSec channel.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   'racoon' in NetBSD is a =
well-known IKE daemon performing the IPsec</span></td><td> </td><td =
class=3D"rblock"></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   Key Exchange (IKE) with the =
peers.</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0044" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">ZJSU</span> and <span =
class=3D"delete">NTT</span> made a successful test with the scenario, =
and the</td><td> </td><td class=3D"rblock">   <span =
class=3D"insert">China</span> and <span class=3D"insert">Japan =
have</span> made a successful test with the scenario, and</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  following items <span class=3D"delete">were</span> realized:</td><td> =
</td><td class=3D"rblock">   the following items <span =
class=3D"insert">have been</span> realized:</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  Internet Key Exchange (IKE) with certificates for endpoint</td><td> =
</td><td class=3D"right">   o  Internet Key Exchange (IKE) with =
certificates for endpoint</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   authentication.</td><td> </td><td class=3D"right">      =
authentication.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  Transport Mode Encapsulating Security Payload (ESP).  =
HMAC-SHA1-96</td><td> </td><td class=3D"right">   o  Transport Mode =
Encapsulating Security Payload (ESP).  HMAC-SHA1-96</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
   for message integrity protection.</td><td> </td><td class=3D"right">  =
    for message integrity protection.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">3.3.  Scenario 3 - CE High Availability</td><td> </td><td =
class=3D"right">3.3.  Scenario 3 - CE High Availability</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
CE High Availability (CEHA) was tested based on the ForCES CEHA</td><td> =
</td><td class=3D"right">   CE High Availability (CEHA) was tested based =
on the ForCES CEHA</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
document [I-D.ietf-forces-ceha-00]</td><td> </td><td class=3D"right">   =
document [I-D.ietf-forces-ceha-00]</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The design of the setup and the scenario for the CEHA were =
simplified</td><td> </td><td class=3D"right">   The design of the setup =
and the scenario for the CEHA were simplified</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0045" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  so as to focus mostly on the mechanics of the CEHA, which <span =
class=3D"delete">we</span>re:</td><td> </td><td class=3D"rblock">   so =
as to focus mostly on the mechanics of the CEHA, which <span =
class=3D"insert">a</span>re:</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  Associating with more than one CE.</td><td> </td><td class=3D"right"> =
  o  Associating with more than one CE.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
o  Switching to backup CE on master CE failure.</td><td> </td><td =
class=3D"right">   o  Switching to backup CE on master CE =
failure.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0046" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The connection diagram for the scenario <span =
class=3D"delete">wa</span>s as shown in Figure 6.</td><td> </td><td =
class=3D"rblock">   The connection diagram for the scenario <span =
class=3D"insert">i</span>s as shown in Figure 6.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0047" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           master     standby            master     standby</td><td> =
</td><td class=3D"rblock">         master     standby            master  =
   standby</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           +------+    +------+          +------+    +------+</td><td> =
</td><td class=3D"rblock">         +------+    +------+          =
+------+    +------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           |  CE  |    |  CE  |          |  CE  |    |  CE  |</td><td> =
</td><td class=3D"rblock">         |  CE  |    |  CE  |          |  CE  =
|    |  CE  |</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           | <span class=3D"delete">ZJSU |    |  UoP |          | NTT  | =
   |  UoP</span> |</td><td> </td><td class=3D"rblock">         | <span =
class=3D"insert">China|    |Greece|          |Japan</span> |    <span =
class=3D"insert">|Greece|</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           +------+    +------+          +------+    +------+</td><td> =
</td><td class=3D"rblock">         +------+    +------+          =
+------+    +------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
              |          |                  |           |</td><td> =
</td><td class=3D"rblock">            |          |                  |    =
       |</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
              +----------+                  +-----------+</td><td> =
</td><td class=3D"rblock">            +----------+                  =
+-----------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
              |                             |</td><td> </td><td =
class=3D"rblock">            |                             |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           +------+                      +------+</td><td> </td><td =
class=3D"rblock">         +------+                      +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           |  FE  |                      |  FE  |</td><td> </td><td =
class=3D"rblock">         |  FE  |                      |  FE  |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           <span class=3D"delete">| UoP  |                      | UoP  =
|</span></td><td> </td><td class=3D"rblock">         <span =
class=3D"insert">|Greece|                      |Greece|</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
           +------+                      +------+</td><td> </td><td =
class=3D"rblock">         +------+                      +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                  (a)                           (b)</td><td> </td><td =
class=3D"rblock">                (a)                           =
(b)</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
             Figure 6: Scenario for CE High Availability</td><td> =
</td><td class=3D"right">                Figure 6: Scenario for CE High =
Availability</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0048" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In this scenario one FE <span class=3D"delete">wa</span>s connected =
and associated to a master CE</td><td> </td><td class=3D"rblock">   In =
this scenario one FE <span class=3D"insert">i</span>s connected and =
associated to a master CE</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
and a backup CE.  In the pre-association phase, the FE would be</td><td> =
</td><td class=3D"right">   and a backup CE.  In the pre-association =
phase, the FE would be</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0049" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  configured to have <span class=3D"delete">ZJSU's</span> or <span =
class=3D"delete">NTT's</span> CE as master CE and <span =
class=3D"delete">UoP's</span> CE as</td><td> </td><td class=3D"rblock">  =
 configured to have <span class=3D"insert">China's</span> or <span =
class=3D"insert">Japan's</span> CE as master CE and <span =
class=3D"insert">Greece's</span> CE</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  standby CE.  The CEFailoverPolicy component of the FE Protocol =
Object</td><td> </td><td class=3D"rblock">   as standby CE.  The =
CEFailoverPolicy component of the FE Protocol</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  LFB that <span class=3D"delete">specified</span> whether the FE <span =
class=3D"delete">was</span> in High Availability mode</td><td> </td><td =
class=3D"rblock">   Object LFB that <span =
class=3D"insert">specifies</span> whether the FE <span =
class=3D"insert">is</span> in High Availability mode</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
(value 2 or 3) would either be set in the pre-association phase =
by</td><td> </td><td class=3D"right">   (value 2 or 3) would either be =
set in the pre-association phase by</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the FEM interface or in post-association phase by the master =
CE.</td><td> </td><td class=3D"right">   the FEM interface or in =
post-association phase by the master CE.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0050" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  If the CEFailoverPolicy value <span class=3D"delete">was</span> set to =
2 or 3, the FE (in the post-</td><td> </td><td class=3D"rblock">   If =
the CEFailoverPolicy value <span class=3D"insert">is</span> set to 2 or =
3, the FE (in the post-</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  association phase) <span class=3D"delete">would</span> attempt to =
connect and associate with the</td><td> </td><td class=3D"rblock">   =
association phase) <span class=3D"insert">will</span> attempt to connect =
and associate with the</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
standby CE.</td><td> </td><td class=3D"right">   standby CE.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0051" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  When the master CE <span class=3D"delete">was</span> deemed =
disconnected, either by a TearDown,</td><td> </td><td class=3D"rblock">  =
 When the master CE <span class=3D"insert">is</span> deemed =
disconnected, either by a TearDown, Loss</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Loss of Heartbeats or physically disconnected, the FE would =
assume</td><td> </td><td class=3D"rblock">   of Heartbeats or physically =
disconnected, the FE would assume that</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  that the standby CE <span class=3D"delete">was</span> now the master =
CE.  The FE <span class=3D"delete">would</span> then send an</td><td> =
</td><td class=3D"rblock">   the standby CE <span =
class=3D"insert">is</span> now the master CE.  The FE <span =
class=3D"insert">will</span> then send an Event</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Event Notification, Primary CE Down,to all associated CEs, only =
the</td><td> </td><td class=3D"rblock">   Notification, Primary CE =
Down,to all associated CEs, only the standby</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  standby CE in this case, with the value of the new master CEID.  =
The</td><td> </td><td class=3D"rblock">   CE in this case, with the =
value of the new master CEID.  The standby</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  standby CE <span class=3D"delete">would</span> then respond by sending =
a configuration message to</td><td> </td><td class=3D"rblock">   CE =
<span class=3D"insert">will</span> then respond by sending a =
configuration message to the CEID</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  the CEID component of the FE Protocol Object with its own ID =
to</td><td> </td><td class=3D"rblock">   component of the FE Protocol =
Object with its own ID to confirm that</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  confirm that the CE <span class=3D"delete">considered</span> itself as =
the master as well.</td><td> </td><td class=3D"rblock">   the CE <span =
class=3D"insert">considers</span> itself as the master as well.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0052" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The steps of the CEHA test scenario <span class=3D"delete">we</span>re =
as follows:</td><td> </td><td class=3D"rblock">   The steps of the CEHA =
test scenario <span class=3D"insert">a</span>re as follows:</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
1.  In the pre-association phase, setup of FE with master CE =
and</td><td> </td><td class=3D"right">   1.  In the pre-association =
phase, setup of FE with master CE and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    backup CE</td><td> </td><td class=3D"right">       backup CE</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
2.  FE connecting and associating with master CE.</td><td> </td><td =
class=3D"right">   2.  FE connecting and associating with master =
CE.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
3.  When CEFailoverPolicy is set to 2 or 3, the FE will connect =
and</td><td> </td><td class=3D"right">   3.  When CEFailoverPolicy is =
set to 2 or 3, the FE will connect and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    associate with backup CE.</td><td> </td><td class=3D"right">       =
associate with backup CE.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
4.  Once the master CE is considered disconnected then the FE =
chooses</td><td> </td><td class=3D"right">   4.  Once the master CE is =
considered disconnected then the FE chooses</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno"></td><td class=3D"left"></td><td> =
</td><td class=3D"right"></td><td class=3D"lineno"></td></tr>=0A=
      <tr bgcolor=3D"gray" ><td></td><th><a name=3D"part-l3" =
/><small>skipping to change at</small><em> page 12, line =
22</em></th><th> </th><th><a name=3D"part-r3" /><small>skipping to =
change at</small><em> page 10, line 40</em></th><td></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
5.  It sends an Event Notification specifying that the master CE =
is</td><td> </td><td class=3D"right">   5.  It sends an Event =
Notification specifying that the master CE is</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    down and who is now the master CE.</td><td> </td><td =
class=3D"right">       down and who is now the master CE.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
6.  The new master CE sends a SET Configuration message to the =
FE</td><td> </td><td class=3D"right">   6.  The new master CE sends a =
SET Configuration message to the FE</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    setting the CEID value to who is now the new master CE =
completing</td><td> </td><td class=3D"right">       setting the CEID =
value to who is now the new master CE completing</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    the switch.</td><td> </td><td class=3D"right">       the =
switch.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">3.4.  Scenario 4 - Packet forwarding</td><td> </td><td =
class=3D"right">3.4.  Scenario 4 - Packet forwarding</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0053" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  This test scenario <span class=3D"delete">wa</span>s to verify LFBs =
like RedirectIn, RedirectOut,</td><td> </td><td class=3D"rblock">   This =
test scenario <span class=3D"insert">i</span>s to verify LFBs like =
RedirectIn, RedirectOut,</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
IPv4NextHop, IPv4UcastLPM defined by the ForCES LFB library =
document</td><td> </td><td class=3D"right">   IPv4NextHop, IPv4UcastLPM =
defined by the ForCES LFB library document</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[I-D.ietf-forces-lfb-lib-03], and more importantly, to verify =
the</td><td> </td><td class=3D"right">   [I-D.ietf-forces-lfb-lib-03], =
and more importantly, to verify the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
combination of the LFBs to implement IP packet forwarding.</td><td> =
</td><td class=3D"right">   combination of the LFBs to implement IP =
packet forwarding.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0054" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The connection diagram for this scenario <span =
class=3D"delete">wa</span>s as Figure 7.</td><td> </td><td =
class=3D"rblock">   The connection diagram for this scenario <span =
class=3D"insert">i</span>s as Figure 7.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            +------+</td><td> </td><td class=3D"right">  =
                             +------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            |  CE  |</td><td> </td><td class=3D"right">  =
                             |  CE  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0055" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                              | <span class=3D"delete"> NTT =
</span>|</td><td> </td><td class=3D"rblock">                             =
  | <span class=3D"insert">Japan</span>|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            +------+</td><td> </td><td class=3D"right">  =
                             +------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |  ^</td><td> </td><td class=3D"right">   =
                               |  ^</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |  | OSPF</td><td> </td><td =
class=3D"right">                                  |  | OSPF</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |  +-------&gt;</td><td> </td><td =
class=3D"right">                                  |  =
+-------&gt;</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            +------+       +------+</td><td> </td><td =
class=3D"right">                               +------+       =
+------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            +--------+      |  FE  |       | OSPF |      =
+--------+</td><td> </td><td class=3D"right">               +--------+   =
   |  FE  |       | OSPF |      +--------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0056" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
              |Terminal|------|<span class=3D"delete"> ZJSU</span> =
|-------|Router|------|Terminal|</td><td> </td><td class=3D"rblock">     =
          |Terminal|------|<span class=3D"insert">China</span> =
|-------|Router|------|Terminal|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            +--------+      +------+       +------+      =
+--------+</td><td> </td><td class=3D"right">               +--------+   =
   +------+       +------+      +--------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
              =
&lt;--------------------------------------------&gt;</td><td> </td><td =
class=3D"right">                 =
&lt;--------------------------------------------&gt;</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                          Packet Forwarding</td><td> </td><td =
class=3D"right">                             Packet Forwarding</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                 (a)</td><td> </td><td class=3D"right">  =
                                  (a)</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                   +------+</td><td> </td><td =
class=3D"right">                                      +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                   |  CE  |</td><td> </td><td =
class=3D"right">                                      |  CE  |</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0057" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                                     | <span class=3D"delete">ZJSU =
</span>|</td><td> </td><td class=3D"rblock">                             =
         | <span class=3D"insert">China</span>|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                   +------+</td><td> </td><td =
class=3D"right">                                      +------+</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                    ^  |  ^</td><td> </td><td =
class=3D"right">                                       ^  |  ^</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               OSPF |  |  | OSPF</td><td> </td><td =
class=3D"right">                                  OSPF |  |  | =
OSPF</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0058" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">                                 =
                                        </span></td><td> </td><td =
class=3D"rblock"></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                              &lt;-----+  |  +-----&gt;</td><td> =
</td><td class=3D"right">                                 &lt;-----+  |  =
+-----&gt;</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                      +-------+    +------+     +------+</td><td> =
</td><td class=3D"right">                         +-------+    +------+  =
   +------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        +--------+    | OSPF  |    |  FE  |     | OSPF |  =
+--------+</td><td> </td><td class=3D"right">           +--------+    | =
OSPF  |    |  FE  |     | OSPF |  +--------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0059" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          |Terminal|----|Router |----|<span class=3D"delete"> NTT =
</span> |-----|Router|--|Terminal|</td><td> </td><td class=3D"rblock">   =
        |Terminal|----|Router |----|<span class=3D"insert">Japan</span> =
|-----|Router|--|Terminal|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        +--------+    +-------+    +------+     +------+  =
+--------+</td><td> </td><td class=3D"right">           +--------+    =
+-------+    +------+     +------+  +--------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                =
&lt;--------------------------------------------&gt;</td><td> </td><td =
class=3D"right">                   =
&lt;--------------------------------------------&gt;</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                          Packet Forwarding</td><td> </td><td =
class=3D"right">                             Packet Forwarding</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                 (b)</td><td> </td><td class=3D"right">  =
                                  (b)</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            +------+       +------+</td><td> </td><td =
class=3D"right">                               +------+       =
+------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            |  CE  |       |  CE  |</td><td> </td><td =
class=3D"right">                               |  CE  |       |  CE  =
|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0060" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
                              | <span class=3D"delete">NTT  |       | =
ZJSU </span>|</td><td> </td><td class=3D"rblock">                        =
       | <span class=3D"insert">Japan|       | China</span>|</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            +------+       +------+</td><td> </td><td =
class=3D"right">                               +------+       =
+------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |  ^          ^ |</td><td> </td><td =
class=3D"right">                                  |  ^          ^ =
|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |  |   OSPF   | |</td><td> </td><td =
class=3D"right">                                  |  |   OSPF   | =
|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                               |  +----------+ |</td><td> </td><td =
class=3D"right">                                  |  +----------+ =
|</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                            +------+       +------+</td><td> </td><td =
class=3D"right">                               +------+       =
+------+</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            +--------+      |  FE  |       |  FE  |      =
+--------+</td><td> </td><td class=3D"right">               +--------+   =
   |  FE  |       |  FE  |      +--------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0061" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
              |Terminal|------|<span class=3D"delete"> ZJSU |-------|  =
NTT</span> |------|Terminal|</td><td> </td><td class=3D"rblock">         =
      |Terminal|------|<span class=3D"insert">China =
|-------|Japan</span> |------|Terminal|</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            +--------+      +------+       +------+      =
+--------+</td><td> </td><td class=3D"right">               +--------+   =
   +------+       +------+      +--------+</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
              =
&lt;--------------------------------------------&gt;</td><td> </td><td =
class=3D"right">                 =
&lt;--------------------------------------------&gt;</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                           Packet Forwarding</td><td> </td><td =
class=3D"right">                              Packet Forwarding</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                                 (c)</td><td> </td><td class=3D"right">  =
                                  (c)</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
             Figure 7: Scenario for IP Packet forwarding</td><td> =
</td><td class=3D"right">                Figure 7: Scenario for IP =
Packet forwarding</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0062" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In case (a), a CE by <span class=3D"delete">NTT was connected to an FE =
by ZJSU</span> to form a</td><td> </td><td class=3D"rblock">   In case =
(a), a CE by <span class=3D"insert">Japan is connected to an FE by =
China</span> to form a</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
ForCES router.  A Smartbits test machine with its routing =
protocol</td><td> </td><td class=3D"right">   ForCES router.  A =
Smartbits test machine with its routing protocol</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0063" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  software <span class=3D"delete">were used to simulate an OSPF router =
and we</span>re connected with</td><td> </td><td class=3D"rblock">   =
software <span class=3D"insert">are used to simulate an OSPF router and =
a</span>re connected with</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the ForCES router to try to exchange OSPF hello packets and LSA</td><td> =
</td><td class=3D"right">   the ForCES router to try to exchange OSPF =
hello packets and LSA</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0064" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  packets among them.  Terminals <span class=3D"delete">were</span> =
simulated by Smartbits to send</td><td> </td><td class=3D"rblock">   =
packets among them.  Terminals <span class=3D"insert">are</span> =
simulated by Smartbits to send and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  and receive packets.  As a result, the CE in the ForCES router <span =
class=3D"delete">needed</span></td><td> </td><td class=3D"rblock">   =
receive packets.  As a result, the CE in the ForCES router <span =
class=3D"insert">need</span> to be</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  to be configured to run and support OSPF routing protocol.</td><td> =
</td><td class=3D"rblock">   configured to run and support OSPF routing =
protocol.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0065" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In case (b), a CE by <span class=3D"delete">ZJSU was</span> connected =
to an FE by <span class=3D"delete">NTT</span> to form a</td><td> =
</td><td class=3D"rblock">   In case (b), a CE by <span =
class=3D"insert">China is</span> connected to an FE by <span =
class=3D"insert">Japan</span> to form a</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  ForCES router.  Two routers running OSPF <span =
class=3D"delete">were</span> simulated and connected</td><td> </td><td =
class=3D"rblock">   ForCES router.  Two routers running OSPF <span =
class=3D"insert">are</span> simulated and connected</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  to the ForCES router to test if the ForCES router <span =
class=3D"delete">could</span> support OSPF</td><td> </td><td =
class=3D"rblock">   to the ForCES router to test if the ForCES router =
<span class=3D"insert">can</span> support OSPF</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
protocol and support packet forwarding.</td><td> </td><td =
class=3D"right">   protocol and support packet forwarding.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0066" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In case (c), two ForCES routers <span class=3D"delete">were</span> =
constructed.  One <span class=3D"delete">was</span> with CE by</td><td> =
</td><td class=3D"rblock">   In case (c), two ForCES routers <span =
class=3D"insert">are</span> constructed.  One <span =
class=3D"insert">is</span> with CE by</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">NTT</span> and FE by <span =
class=3D"delete">ZJSU</span> and the other <span =
class=3D"delete">was</span> opposite.  OSPF and packet</td><td> </td><td =
class=3D"rblock">   <span class=3D"insert">Japan</span> and FE by <span =
class=3D"insert">China</span> and the other <span =
class=3D"insert">is</span> opposite.  OSPF and packet</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  forwarding <span class=3D"delete">were</span> tested in the =
environment.</td><td> </td><td class=3D"rblock">   forwarding <span =
class=3D"insert">are</span> tested in the environment.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0067" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Testing process for this scenario <span class=3D"delete">wa</span>s as =
below:</td><td> </td><td class=3D"rblock">   Testing process for this =
scenario <span class=3D"insert">i</span>s as below:</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
1.  Boot terminals and routers, and set IP addresses of their</td><td> =
</td><td class=3D"right">   1.  Boot terminals and routers, and set IP =
addresses of their</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    interfaces.</td><td> </td><td class=3D"right">       =
interfaces.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
2.  Boot CE and FE.</td><td> </td><td class=3D"right">   2.  Boot CE and =
FE.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
3.  Establish association between CE and FE, and set IP addresses =
of</td><td> </td><td class=3D"right">   3.  Establish association =
between CE and FE, and set IP addresses of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    FEs interfaces.</td><td> </td><td class=3D"right">       FEs =
interfaces.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
4.  Start OSPF among CE and routers, and set FIB on FE.</td><td> =
</td><td class=3D"right">   4.  Start OSPF among CE and routers, and set =
FIB on FE.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
5.  Send packets between terminals.</td><td> </td><td class=3D"right">   =
5.  Send packets between terminals.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">4. =
 Test Results</td><td> </td><td class=3D"right">4.  Test Results</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">4.1.  LFB Operation Test</td><td> </td><td =
class=3D"right">4.1.  LFB Operation Test</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0068" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The test result <span class=3D"delete">was</span> as reported by =
Figure 8.  For the convenience</td><td> </td><td class=3D"rblock">   The =
test result <span class=3D"insert">is</span> as reported by Figure 8.  =
For the convenience</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  sake, as mentioned earlier, abbreviations of <span =
class=3D"delete">'Z'</span> in the table means</td><td> </td><td =
class=3D"rblock">   sake, as mentioned earlier, abbreviations of <span =
class=3D"insert">'C'</span> in the table means</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  implementation from <span class=3D"delete">ZJSU ,'N' NTT</span> =
implementation, and <span class=3D"delete">'P' UoP</span></td><td> =
</td><td class=3D"rblock">   implementation from <span =
class=3D"insert">China,'J'Japan</span> implementation, and <span =
class=3D"insert">'G' Greece</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
implementation.</td><td> </td><td class=3D"right">   =
implementation.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|Test#| CE |FE(s)|Oper |      LFB     |     Component     | Result  =
|</td><td> </td><td class=3D"right">   |Test#| CE |FE(s)|Oper |      LFB =
    |     Component     | Result  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |    /Capability    |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |    /Capability    |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0069" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  1  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |   FEObject   |    LFBTopology    | =
Success |</td><td> </td><td class=3D"rblock">   |  1  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |   =
FEObject   |    LFBTopology    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0070" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  2  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |   FEObject   |    LFBSelector    | =
Success |</td><td> </td><td class=3D"rblock">   |  2  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |   =
FEObject   |    LFBSelector    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0071" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  3  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |     PHYPortID     | =
Success |</td><td> </td><td class=3D"rblock">   |  3  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |     PHYPortID     | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0072" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  4  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |    AdminStatus    | =
Success |</td><td> </td><td class=3D"rblock">   |  4  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |    AdminStatus    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0073" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  5  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |     OperStatus    | =
Success |</td><td> </td><td class=3D"rblock">   |  5  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |     OperStatus    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0074" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  6  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |  AdminLinkSpeed   | =
Success |</td><td> </td><td class=3D"rblock">   |  6  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |  AdminLinkSpeed   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0075" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  7  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |   OperLinkSpeed   | =
Success |</td><td> </td><td class=3D"rblock">   |  7  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |   OperLinkSpeed   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0076" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  8  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |  AdminDuplexSpeed | =
Success |</td><td> </td><td class=3D"rblock">   |  8  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |  AdminDuplexSpeed | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0077" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  9  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |  OperDuplexSpeed  | =
Success |</td><td> </td><td class=3D"rblock">   |  9  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |  OperDuplexSpeed  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0078" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  10 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherPHYCop |   CarrierStatus   | =
Success |</td><td> </td><td class=3D"rblock">   |  10 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherPHYCop |   CarrierStatus   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0079" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  11 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  |    AdminStatus    | =
Success |</td><td> </td><td class=3D"rblock">   |  11 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  |    AdminStatus    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0080" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  12 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  | LocalMacAddresses | =
Success |</td><td> </td><td class=3D"rblock">   |  12 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  | LocalMacAddresses | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0081" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  13 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  |    L2Bridging     | =
Success |</td><td> </td><td class=3D"rblock">   |  13 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  |    L2Bridging     | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |   PathEnable      | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |   PathEnable      | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0082" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  14 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  |  PromiscuousMode  | =
Success |</td><td> </td><td class=3D"rblock">   |  14 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  |  PromiscuousMode  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0083" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  15 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  |   TxFlowControl   | =
Success |</td><td> </td><td class=3D"rblock">   |  15 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  |   TxFlowControl   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0084" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  16 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  |   RxFlowControl   | =
Success |</td><td> </td><td class=3D"rblock">   |  16 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  |   RxFlowControl   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0085" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  17 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACIn  |     MACInStats    | =
Success |</td><td> </td><td class=3D"rblock">   |  17 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACIn  |     MACInStats    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0086" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  | 18  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET | EtherMACOut  |     AdminStatus   | =
Success |</td><td> </td><td class=3D"rblock">   | 18  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET | =
EtherMACOut  |     AdminStatus   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0087" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  | 19  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACOut |          MTU      | =
Success |</td><td> </td><td class=3D"rblock">   | 19  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACOut |          MTU      | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0088" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  20 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACOut |    TxFlowControl  | =
Success |</td><td> </td><td class=3D"rblock">   |  20 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACOut |    TxFlowControl  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0089" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  21 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACOut |    TxFlowControl  | =
Success |</td><td> </td><td class=3D"rblock">   |  21 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACOut |    TxFlowControl  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0090" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  22 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |  EtherMACOut |     MACOutStats   | =
Success |</td><td> </td><td class=3D"rblock">   |  22 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |  =
EtherMACOut |     MACOutStats   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0091" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  23 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |      ARP     |PortV4AddrInfoTable| =
Success |</td><td> </td><td class=3D"rblock">   |  23 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |   =
   ARP     |PortV4AddrInfoTable| Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0092" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  24 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |      ARP     |PortV4AddrInfoTable| =
Success |</td><td> </td><td class=3D"rblock">   |  24 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |   =
   ARP     |PortV4AddrInfoTable| Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0093" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  25 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | DEL |      ARP     |PortV4AddrInfoTable| =
Success |</td><td> </td><td class=3D"rblock">   |  25 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | DEL |   =
   ARP     |PortV4AddrInfoTable| Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0094" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  26 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |  EtherMACIn  | LocalMACAddresses | =
Success |</td><td> </td><td class=3D"rblock">   |  26 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |  =
EtherMACIn  | LocalMACAddresses | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0095" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  27 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |  EtherMACIn  |          MTU      | =
Success |</td><td> </td><td class=3D"rblock">   |  27 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |  =
EtherMACIn  |          MTU      | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0096" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  28 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |  IPv4NextHop |  IPv4NextHopTable | =
Success |</td><td> </td><td class=3D"rblock">   |  28 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |  =
IPv4NextHop |  IPv4NextHopTable | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0097" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  29 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET | IPv4UcastLPM |  IPv4PrefixTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  29 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET | =
IPv4UcastLPM |  IPv4PrefixTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0098" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  30 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | DEL |  IPv4NextHop |  IPv4NextHopTable | =
Success |</td><td> </td><td class=3D"rblock">   |  30 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | DEL |  =
IPv4NextHop |  IPv4NextHopTable | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0099" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  31 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | DEL | IPv4UcastLPM |  IPv4PrefixTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  31 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | DEL | =
IPv4UcastLPM |  IPv4PrefixTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0100" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  32 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |  EtherPHYCop |     AdminStatus   | =
Success |</td><td> </td><td class=3D"rblock">   |  32 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |  =
EtherPHYCop |     AdminStatus   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0101" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  33 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |     Ether    |   VlanInputTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  33 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |   =
  Ether    |   VlanInputTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |  Classifier  |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |  =
Classifier  |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0102" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  34 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | DEL |     Ether    |   VlanInputTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  34 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | DEL |   =
  Ether    |   VlanInputTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |  Classifier  |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |  =
Classifier  |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0103" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  35 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |   Ether      |  VlanOutputTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  35 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |   =
Ether      |  VlanOutputTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     | Encapsulator |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     | =
Encapsulator |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0104" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  36 | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | DEL |    Ether     |   VlanOutputTable | =
Success |</td><td> </td><td class=3D"rblock">   |  36 | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | DEL |   =
 Ether     |   VlanOutputTable | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     | Encapsulator |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     | =
Encapsulator |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">P</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">G</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">P</span>  |  <span =
class=3D"delete">N</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">G</span>  |  <span class=3D"insert">J</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                Figure 8: LFB Operation Test Results</td><td> </td><td =
class=3D"right">                   Figure 8: LFB Operation Test =
Results</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0105" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Note on test <span class=3D"delete">#1</span>:</td><td> </td><td =
class=3D"rblock">   Note on test <span =
class=3D"insert">1#</span>:</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
On the wire format of encapsulation on array, only the case of</td><td> =
</td><td class=3D"right">   On the wire format of encapsulation on =
array, only the case of</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
FULLDATA-in-FULLDATA was tested.</td><td> </td><td class=3D"right">   =
FULLDATA-in-FULLDATA was tested.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0106" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In <span class=3D"delete">ZJSU's implementation, after test #2</span> =
CE have to get all LFBs'</td><td> </td><td class=3D"rblock">   In <span =
class=3D"insert">China's implementation, after test 2#</span> CE have to =
get all LFBs'</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
instance data actively according to the queried component of</td><td> =
</td><td class=3D"right">   instance data actively according to the =
queried component of</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
LFBSelectors.</td><td> </td><td class=3D"right">   LFBSelectors.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0107" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock">   <span =
class=3D"insert">Note on test 28# and 29#:</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert"></span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   Only had new reachable network destination been set, =
can route entry</span></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   be added into system.</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert"></span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   Note on test 30# and 31#:</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert"></span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   Corresponding nexthop entry must be deleted before =
prefix entry which</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   is decided by FE's routing =
management.</span></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock">                    =
                                                     </td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">4.2.  TML with IPSec Test</td><td> </td><td =
class=3D"right">4.2.  TML with IPSec Test</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0108" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  In this scenario, the ForCES TML <span class=3D"delete">was</span> run =
over IPSec.  Implementers</td><td> </td><td class=3D"rblock">   In this =
scenario, the ForCES TML <span class=3D"insert">is</span> run over =
IPSec.  Implementers</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  joined this interoperability test <span class=3D"delete">used</span> =
the same third-party tool</td><td> </td><td class=3D"rblock">   joined =
this interoperability test <span class=3D"insert">use</span> the same =
third-party tool</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
software 'racoon' to establish IPSec channel.  Some typical LFB</td><td> =
</td><td class=3D"right">   software 'racoon' to establish IPSec =
channel.  Some typical LFB</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0109" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  operation tests as in Scenario 1 <span class=3D"delete">we</span>re =
repeated with the IPSec enabled</td><td> </td><td class=3D"rblock">   =
operation tests as in Scenario 1 <span class=3D"insert">a</span>re =
repeated with the IPSec enabled</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
TML.</td><td> </td><td class=3D"right">   TML.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0110" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">As mentioned,</span> this scenario only took =
place between <span class=3D"delete">implementers of</span></td><td> =
</td><td class=3D"rblock">   <span class=3D"insert">A note on this test =
is, because of the system difficulty to implement</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   ZJSU</span> and <span =
class=3D"delete">NTT.</span></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   IPSec over TML, Greece did not join in the test.  =
Therefore,</span> this</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock">   scenario only =
took place between <span class=3D"insert">C</span> and <span =
class=3D"insert">J.</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The TML with IPSec test results are reported by Figure 9.</td><td> =
</td><td class=3D"right">   The TML with IPSec test results are reported =
by Figure 9.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|Test#| CE |FE(s)|Oper |       LFB    |     Component/    | Result  =
|</td><td> </td><td class=3D"right">   |Test#| CE |FE(s)|Oper |       =
LFB    |     Component/    | Result  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |     Capability    |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |     Capability    |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0111" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  1  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |   FEObject   |   LFBTopology     | =
Success |</td><td> </td><td class=3D"rblock">   |  1  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |   =
FEObject   |   LFBTopology     | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0112" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  2  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | GET |   FEObject   |   LFBSelectors    | =
Success |</td><td> </td><td class=3D"rblock">   |  2  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | GET |   =
FEObject   |   LFBSelectors    | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     |              |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     |   =
           |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0113" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  3  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | SET |   Ether      |   VlanInputTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  3  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | SET |   =
Ether      |   VlanInputTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     | Classifier   |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     | =
Classifier   |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     |              |                   |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     |          =
    |                   |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0114" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  4  | <span class=3D"delete">Z</span>  |  <span =
class=3D"delete">N</span>  | DEL |   Ether      |   VlanInputTable  | =
Success |</td><td> </td><td class=3D"rblock">   |  4  | <span =
class=3D"insert">C</span>  |  <span class=3D"insert">J</span>  | DEL |   =
Ether      |   VlanInputTable  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |     | <span class=3D"delete">N</span>  |  <span =
class=3D"delete">Z</span>  |     | Classifier   |                   | =
Success |</td><td> </td><td class=3D"rblock">   |     | <span =
class=3D"insert">J</span>  |  <span class=3D"insert">C</span>  |     | =
Classifier   |                   | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-----+--------------+-------------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                Figure 9: TML with IPSec Test Results</td><td> </td><td =
class=3D"right">                   Figure 9: TML with IPSec Test =
Results</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">4.3.  CE High Availability Test</td><td> </td><td =
class=3D"right">4.3.  CE High Availability Test</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
In this scenario one FE connects and associates with a master CE =
and</td><td> </td><td class=3D"right">   In this scenario one FE =
connects and associates with a master CE and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
a backup CE.  When the master CE is deemed disconnected the FE =
would</td><td> </td><td class=3D"right">   a backup CE.  When the master =
CE is deemed disconnected the FE would</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
attempt to find another associated CE to become the master CE.</td><td> =
</td><td class=3D"right">   attempt to find another associated CE to =
become the master CE.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno"></td><td class=3D"left"></td><td> =
</td><td class=3D"right"></td><td class=3D"lineno"></td></tr>=0A=
      <tr bgcolor=3D"gray" ><td></td><th><a name=3D"part-l4" =
/><small>skipping to change at</small><em> page 22, line =
34</em></th><th> </th><th><a name=3D"part-r4" /><small>skipping to =
change at</small><em> page 20, line 29</em></th><td></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
By running OSPF, the CE in the ForCES router can generate new =
routes</td><td> </td><td class=3D"right">   By running OSPF, the CE in =
the ForCES router can generate new routes</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
and load them to routing table in FE.  The FE is then able to =
forward</td><td> </td><td class=3D"right">   and load them to routing =
table in FE.  The FE is then able to forward</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
packets according to the routing table.</td><td> </td><td =
class=3D"right">   packets according to the routing table.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The test is reported with the results in Figure 10</td><td> </td><td =
class=3D"right">   The test is reported with the results in Figure =
10</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-------------------------+--------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-------------------------+--------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|Test#| CE |FE(s)|           Item          | LFBs Related | Result  =
|</td><td> </td><td class=3D"right">   |Test#| CE |FE(s)|           Item =
         | LFBs Related | Result  |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-------------------------+--------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-------------------------+--------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0115" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  1  | <span class=3D"delete">N  |  Z</span>  |  IPv4NextHopTable SET =
  | IPv4NextHop  | Success |</td><td> </td><td class=3D"rblock">   |  1  =
| <span class=3D"insert">J  |  C</span>  |  IPv4NextHopTable SET   | =
IPv4NextHop  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0116" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  2  | <span class=3D"delete">N  |  Z</span>  |   IPv4PrefixTable SET =
  | IPv4UcastLPM | Success |</td><td> </td><td class=3D"rblock">   |  2  =
| <span class=3D"insert">J  |  C</span>  |   IPv4PrefixTable SET   | =
IPv4UcastLPM | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0117" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  3  | <span class=3D"delete">N  |  Z</span>  |Redirect OSPF packet =
from|  RedirectIn  | Success |</td><td> </td><td class=3D"rblock">   |  =
3  | <span class=3D"insert">J  |  C</span>  |Redirect OSPF packet from|  =
RedirectIn  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     CE to SmartBits     |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     CE to =
SmartBits     |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0118" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  4  | <span class=3D"delete">N  |  Z</span>  |Redirect OSPF packet =
from|  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  =
4  | <span class=3D"insert">J  |  C</span>  |Redirect OSPF packet from|  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     SmartBits to CE     |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     SmartBits =
to CE     |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0119" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  5  | <span class=3D"delete">N  |  Z</span>  |       Metadata in     =
  |  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  5  =
| <span class=3D"insert">J  |  C</span>  |       Metadata in       |  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     redirect message    |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     redirect =
message    |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0120" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  6  | <span class=3D"delete">N  |  Z</span>  | OSPF neighbor =
discovery |  RedirectOut | Success |</td><td> </td><td class=3D"rblock"> =
  |  6  | <span class=3D"insert">J  |  C</span>  | OSPF neighbor =
discovery |  RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0121" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  7  | <span class=3D"delete">N  |  Z</span>  |     OSPF DD exchange  =
  |  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  7  =
| <span class=3D"insert">J  |  C</span>  |     OSPF DD exchange    |  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4NextHop |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4NextHop |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0122" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  8  | <span class=3D"delete">N  |  Z</span>  |    OSPF LSA exchange  =
  |  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  8  =
| <span class=3D"insert">J  |  C</span>  |    OSPF LSA exchange    |  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4NextHop |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4NextHop |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4UcastLPM|         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4UcastLPM|         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0123" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  9  | <span class=3D"delete">N  |  Z</span>  |     Data Forwarding   =
  |  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  9  =
| <span class=3D"insert">J  |  C</span>  |     Data Forwarding     |  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4NextHop |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4NextHop |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4UcastLPM|         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4UcastLPM|         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0124" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  10 | <span class=3D"delete">Z  |  N</span>  |  IPv4NextHopTable SET =
  |  IPv4NextHop | Success |</td><td> </td><td class=3D"rblock">   |  10 =
| <span class=3D"insert">C  |  J</span>  |  IPv4NextHopTable SET   |  =
IPv4NextHop | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0125" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  11 | <span class=3D"delete">Z  |  N</span>  |   IPv4PrefixTable SET =
  |  IPv4UcastLPM| Success |</td><td> </td><td class=3D"rblock">   |  11 =
| <span class=3D"insert">C  |  J</span>  |   IPv4PrefixTable SET   |  =
IPv4UcastLPM| Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0126" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  12 | <span class=3D"delete">Z  |  N</span>  |Redirect OSPF packet =
from|  RedirectIn  | Success |</td><td> </td><td class=3D"rblock">   |  =
12 | <span class=3D"insert">C  |  J</span>  |Redirect OSPF packet from|  =
RedirectIn  | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     | CE to other OSPF router |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     | CE to other =
OSPF router |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0127" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  13 | <span class=3D"delete">Z  |  N</span>  |Redirect OSPF packet =
from|  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  =
13 | <span class=3D"insert">C  |  J</span>  |Redirect OSPF packet from|  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |other OSPF router to CE  |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |other OSPF =
router to CE  |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0128" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  14 | <span class=3D"delete">Z  |  N</span>  |       Metadata in     =
  |  RedirectOut | Success |</td><td> </td><td class=3D"rblock">   |  14 =
| <span class=3D"insert">C  |  J</span>  |       Metadata in       |  =
RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |     redirect message    |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |     redirect =
message    |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0129" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  15 | <span class=3D"delete">Z  |  N</span>  |OSPF neighbor =
discovery  |  RedirectOut | Success |</td><td> </td><td =
class=3D"rblock">   |  15 | <span class=3D"insert">C  |  J</span>  |OSPF =
neighbor discovery  |  RedirectOut | Success |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0130" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  16 | <span class=3D"delete">Z  |  N</span>  |    OSPF DD exchange   =
  |  RedirectOut | Failure |</td><td> </td><td class=3D"rblock">   |  16 =
| <span class=3D"insert">C  |  J</span>  |    OSPF DD exchange     |  =
RedirectOut | Failure |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4NextHop |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4NextHop |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |              |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |              |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0131" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  |  17 | <span class=3D"delete">Z  |  N</span>  |    OSPF LSA exchange  =
  |  RedirectOut | Failure |</td><td> </td><td class=3D"rblock">   |  17 =
| <span class=3D"insert">C  |  J</span>  |    OSPF LSA exchange    |  =
RedirectOut | Failure |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  RedirectIn  |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  RedirectIn  |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4NextHop |         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4NextHop |         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
|     |    |     |                         |  IPv4UcastLPM|         =
|</td><td> </td><td class=3D"right">   |     |    |     |                =
         |  IPv4UcastLPM|         |</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
+-----+----+-----+-------------------------+--------------+---------+</td=
><td> </td><td class=3D"right">   =
+-----+----+-----+-------------------------+--------------+---------+</td=
><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
              Figure 10: Packet Forwarding Test Results</td><td> =
</td><td class=3D"right">                 Figure 10: Packet Forwarding =
Test Results</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0132" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Note on test <span class=3D"delete">#1 and #2</span>:</td><td> =
</td><td class=3D"rblock">   Note on test <span class=3D"insert">1# and =
2#</span>:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
A multicast route pointed to localhost was manually set before</td><td> =
</td><td class=3D"right">   A multicast route pointed to localhost was =
manually set before</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
redirect channel could work normally.</td><td> </td><td class=3D"right"> =
  redirect channel could work normally.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0133" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Note on test <span class=3D"delete">#3 to #9</span>:</td><td> </td><td =
class=3D"rblock">   Note on test <span class=3D"insert">3# to =
9#</span>:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
During the tests, OSPF packets received from CE were found by</td><td> =
</td><td class=3D"right">   During the tests, OSPF packets received from =
CE were found by</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0134" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Ethereal/Wireshark with checksum errors.  <span =
class=3D"delete">ZJSU</span>'s FE corrected the</td><td> </td><td =
class=3D"rblock">   Ethereal/Wireshark with checksum errors.  <span =
class=3D"insert">China</span>'s FE corrected the</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
checksum in FE so that the Smartbits would not drop the packets =
and</td><td> </td><td class=3D"right">   checksum in FE so that the =
Smartbits would not drop the packets and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the neighbor discovery can continue.  Such correcting action does =
not</td><td> </td><td class=3D"right">   the neighbor discovery can =
continue.  Such correcting action does not</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
affect the test scenarios and the results.</td><td> </td><td =
class=3D"right">   affect the test scenarios and the results.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Comment on Test #16 and #17:</td><td> </td><td class=3D"right">   =
Comment on Test #16 and #17:</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0135" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The two test items failed.  Note that Test #7 and #8 <span =
class=3D"delete">were identical</span></td><td> </td><td =
class=3D"rblock">   The two test items failed.  Note that Test #7 and #8 =
<span class=3D"insert">are exactly</span> the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   to</span> the tests, only =
with CE and FE implementers <span class=3D"delete">were =
exchanged.</span></td><td> </td><td class=3D"rblock">   <span =
class=3D"insert">same as these</span> tests, only with CE and FE =
implementers <span class=3D"insert">are exchanged,</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   Moreover, test</span> #12 and =
#13 <span class=3D"delete">showed that</span> the redirect channel <span =
class=3D"delete">worked</span></td><td> </td><td class=3D"rblock"><span =
class=3D"insert">   and Test</span> #12 and #13 <span =
class=3D"insert">show</span> the redirect channel <span =
class=3D"insert">works</span> well.  <span class=3D"insert">As =
a</span></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  well.  <span class=3D"delete">Therefore,</span> it can be <span =
class=3D"delete">reasonably</span> inferred that the problem</td><td> =
</td><td class=3D"rblock"><span class=3D"insert">   result,</span> it =
can be inferred that the problem caused the <span =
class=3D"insert">test</span> failure</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  caused the failure was from the <span =
class=3D"delete">implementations,</span> rather than from the</td><td> =
</td><td class=3D"rblock">   was <span class=3D"insert">almost =
certainly</span> from the <span class=3D"insert">implementation of the =
related LFBs</span></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  ForCES protocol <span class=3D"delete">itself or from misunderstanding =
of implementations on</span></td><td> </td><td class=3D"rblock">   =
rather than from the ForCES protocol <span class=3D"insert">design =
problem, therefore</span> the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   the protocol specification.  =
Although</span> the failure <span class=3D"delete">made the =
OSPF</span></td><td> </td><td class=3D"rblock">   failure <span =
class=3D"insert">does</span> not <span class=3D"insert">lead</span> to =
the <span class=3D"insert">interoperability problem on =
ForCES.</span></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   interoperability test =
incomplete, it did</span> not <span class=3D"delete">show =
interoperability</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   problem.  More test work is =
needed</span> to <span class=3D"delete">verify</span> the <span =
class=3D"delete">OSPF</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   =
interoperability.</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">5. =
 Discussions</td><td> </td><td class=3D"right">5.  Discussions</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">5.1.  On Data Encapsulation Format</td><td> </td><td =
class=3D"right">5.1.  On Data Encapsulation Format</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
In the first day of the test, it was found that the LFB inter-</td><td> =
</td><td class=3D"right">   In the first day of the test, it was found =
that the LFB inter-</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
operations about tables all failed.  The reason is found to be =
the</td><td> </td><td class=3D"right">   operations about tables all =
failed.  The reason is found to be the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
different ForCES protocol data encapsulation method among =
different</td><td> </td><td class=3D"right">   different ForCES protocol =
data encapsulation method among different</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
implementations.  The encapsulation issues are detailed as =
below:</td><td> </td><td class=3D"right">   implementations.  The =
encapsulation issues are detailed as below:</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Assuming that an LFB has two components, one is a struct with ID =
1</td><td> </td><td class=3D"right">   Assuming that an LFB has two =
components, one is a struct with ID 1</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
and the other an array with ID 2, further with two components of =
u32</td><td> </td><td class=3D"right">   and the other an array with ID =
2, further with two components of u32</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
both inside, as below:</td><td> </td><td class=3D"right">   both inside, =
as below:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
struct1: type struct, ID=3D1</td><td> </td><td class=3D"right">   =
struct1: type struct, ID=3D1</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0136" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          components are:</td><td> </td><td class=3D"rblock">       =
components are:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          a, type u32, ID=3D1</td><td> </td><td class=3D"rblock">       =
a, type u32, ID=3D1</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          b, type u32, ID=3D2</td><td> </td><td class=3D"rblock">       =
b, type u32, ID=3D2</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
table1: type array, ID=3D2</td><td> </td><td class=3D"right">   table1: =
type array, ID=3D2</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0137" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          components for each row are (a struct of):</td><td> </td><td =
class=3D"rblock">       components for each row are (a struct =
of):</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          x, type u32, ID=3D1</td><td> </td><td class=3D"rblock">       =
x, type u32, ID=3D1</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
          y, type u32, ID=3D2</td><td> </td><td class=3D"rblock">       =
y, type u32, ID=3D2</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
1.  On response of PATH-DATA format</td><td> </td><td class=3D"right">   =
1.  On response of PATH-DATA format</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
When a CE sends a config/query ForCES protocol message to an FE =
from</td><td> </td><td class=3D"right">   When a CE sends a config/query =
ForCES protocol message to an FE from</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
a different implementer, the CE probably receives response from =
the</td><td> </td><td class=3D"right">   a different implementer, the CE =
probably receives response from the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
FE with different PATH-DATA encapsulation format.  For example, if =
a</td><td> </td><td class=3D"right">   FE with different PATH-DATA =
encapsulation format.  For example, if a</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
CE sends a query message with a path of 1 to a third party FE =
to</td><td> </td><td class=3D"right">   CE sends a query message with a =
path of 1 to a third party FE to</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
manipulate struct 1 as defined above, the FE is probable to =
generate</td><td> </td><td class=3D"right">   manipulate struct 1 as =
defined above, the FE is probable to generate</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
response with two different PATH-DATA encapsulation format: one =
is</td><td> </td><td class=3D"right">   response with two different =
PATH-DATA encapsulation format: one is</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the value with FULL/SPARSE-DATA and the other is the value with =
many</td><td> </td><td class=3D"right">   the value with =
FULL/SPARSE-DATA and the other is the value with many</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno"></td><td class=3D"left"></td><td> =
</td><td class=3D"right"></td><td class=3D"lineno"></td></tr>=0A=
      <tr bgcolor=3D"gray" ><td></td><th><a name=3D"part-l5" =
/><small>skipping to change at</small><em> page 26, line 6</em></th><th> =
</th><th><a name=3D"part-r5" /><small>skipping to change at</small><em> =
page 23, line 18</em></th><td></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
    OPER =3D GET-RESPONSE-TLV</td><td> </td><td class=3D"right">       =
OPER =3D GET-RESPONSE-TLV</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
        PATH-DATA-TLV:</td><td> </td><td class=3D"right">           =
PATH-DATA-TLV:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            IDs=3D1</td><td> </td><td class=3D"right">               =
IDs=3D1</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            PATH-DATA-TLV:</td><td> </td><td class=3D"right">            =
   PATH-DATA-TLV:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                IDs=3D1</td><td> </td><td class=3D"right">               =
    IDs=3D1</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                FULLDATA-TLV containing valueof(a)</td><td> </td><td =
class=3D"right">                   FULLDATA-TLV containing =
valueof(a)</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
            PATH-DATA-TLV:</td><td> </td><td class=3D"right">            =
   PATH-DATA-TLV:</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                IDs=3D2</td><td> </td><td class=3D"right">               =
    IDs=3D2</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
                FULLDATA-TLV containing valueof(b)</td><td> </td><td =
class=3D"right">                   FULLDATA-TLV containing =
valueof(b)</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0138" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  The interoperability <span class=3D"delete">testers</span> witnessed =
that a ForCES element (CE or</td><td> </td><td class=3D"rblock">   The =
interoperability <span class=3D"insert">test</span> witnessed that a =
ForCES element (CE or FE)</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  FE) sender is free to choose whatever data structure that IETF =
ForCES</td><td> </td><td class=3D"rblock">   sender is free to choose =
whatever data structure that IETF ForCES</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
documents define and best suits the element, while a ForCES =
element</td><td> </td><td class=3D"right">   documents define and best =
suits the element, while a ForCES element</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
(CE or FE) should be able to accept and process information =
(requests</td><td> </td><td class=3D"right">   (CE or FE) should be able =
to accept and process information (requests</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
and responses) that use any legitimate structure defined by =
IETF</td><td> </td><td class=3D"right">   and responses) that use any =
legitimate structure defined by IETF</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
ForCES documents.  While in the case a ForCES element is free =
to</td><td> </td><td class=3D"right">   ForCES documents.  While in the =
case a ForCES element is free to</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
choose any legitimate data structure as a response, it is =
preferred</td><td> </td><td class=3D"right">   choose any legitimate =
data structure as a response, it is preferred</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
the ForCES element responds in the same format that the request =
was</td><td> </td><td class=3D"right">   the ForCES element responds in =
the same format that the request was</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
made, as it is most probably the data structure is the request =
sender</td><td> </td><td class=3D"right">   made, as it is most probably =
the data structure is the request sender</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
looks forward to receive.</td><td> </td><td class=3D"right">   looks =
forward to receive.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
2.  On operation to array</td><td> </td><td class=3D"right">   2.  On =
operation to array</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno"></td><td class=3D"left"></td><td> =
</td><td class=3D"right"></td><td class=3D"lineno"></td></tr>=0A=
      <tr bgcolor=3D"gray" ><td></td><th><a name=3D"part-l6" =
/><small>skipping to change at</small><em> page 31, line 8</em></th><th> =
</th><th><a name=3D"part-r6" /><small>skipping to change at</small><em> =
page 25, line 40</em></th><td></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
The authors also thank very much to Adrian Farrel and Joel =
Halpern</td><td> </td><td class=3D"right">   The authors also thank very =
much to Adrian Farrel and Joel Halpern</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
for their important help in the document publication process.</td><td> =
</td><td class=3D"right">   for their important help in the document =
publication process.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">8. =
 IANA Considerations</td><td> </td><td class=3D"right">8.  IANA =
Considerations</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
This memo includes no request to IANA.</td><td> </td><td =
class=3D"right">   This memo includes no request to IANA.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">9. =
 Security Considerations</td><td> </td><td class=3D"right">9.  Security =
Considerations</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Developers of ForCES FEs and CEs must take the security</td><td> =
</td><td class=3D"right">   Developers of ForCES FEs and CEs must take =
the security</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0139" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  considerations of the ForCES Framework [RFC3746] and the =
ForCES</td><td> </td><td class=3D"rblock">   considerations of the =
ForCES Framework [RFC3746]  and the ForCES</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Protocol [RFC5810] into account.  Also, as specified in the =
security</td><td> </td><td class=3D"rblock">   Protocol [RFC5810]  into =
account.  Also, as specified in the security</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
considerations section of the SCTP-Based TML for the ForCES =
Protocol</td><td> </td><td class=3D"right">   considerations section of =
the SCTP-Based TML for the ForCES Protocol</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5811], the transport-level security has to be ensured by =
IPsec.</td><td> </td><td class=3D"right">   [RFC5811], the =
transport-level security has to be ensured by IPsec.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0140" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">Test results of TML with IPsec supported have =
been shown in</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   Section 4.2 of the =
document.</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">10.  References</td><td> </td><td class=3D"right">10.  =
References</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0141" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">                                 =
                                        </span></td><td> </td><td =
class=3D"rblock"></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">10.1.  Normative References</td><td> </td><td =
class=3D"right">10.1.  Normative References</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5810]  Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., =
Wang,</td><td> </td><td class=3D"right">   [RFC5810]  Doria, A., Hadi =
Salim, J., Haas, R., Khosravi, H., Wang,</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           W., Dong, L., Gopal, R., and J. Halpern, "Forwarding =
and</td><td> </td><td class=3D"right">              W., Dong, L., Gopal, =
R., and J. Halpern, "Forwarding and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Control Element Separation (ForCES) Protocol</td><td> =
</td><td class=3D"right">              Control Element Separation =
(ForCES) Protocol</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Specification", RFC 5810, March 2010.</td><td> </td><td =
class=3D"right">              Specification", RFC 5810, March =
2010.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5811]  Hadi Salim, J. and K. Ogawa, "SCTP-Based Transport =
Mapping</td><td> </td><td class=3D"right">   [RFC5811]  Hadi Salim, J. =
and K. Ogawa, "SCTP-Based Transport Mapping</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Layer (TML) for the Forwarding and Control Element</td><td> =
</td><td class=3D"right">              Layer (TML) for the Forwarding =
and Control Element</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Separation (ForCES) Protocol", RFC 5811, March 2010.</td><td> =
</td><td class=3D"right">              Separation (ForCES) Protocol", =
RFC 5811, March 2010.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno"></td><td class=3D"left"></td><td> =
</td><td class=3D"right"></td><td class=3D"lineno"></td></tr>=0A=
      <tr bgcolor=3D"gray" ><td></td><th><a name=3D"part-l7" =
/><small>skipping to change at</small><em> page 32, line =
19</em></th><th> </th><th><a name=3D"part-r7" /><small>skipping to =
change at</small><em> page 26, line 16</em></th><td></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5810]  Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., =
Wang,</td><td> </td><td class=3D"right">   [RFC5810]  Doria, A., Hadi =
Salim, J., Haas, R., Khosravi, H., Wang,</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           W., Dong, L., Gopal, R., and J. Halpern, "Forwarding =
and</td><td> </td><td class=3D"right">              W., Dong, L., Gopal, =
R., and J. Halpern, "Forwarding and</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Control Element Separation (ForCES) Protocol</td><td> =
</td><td class=3D"right">              Control Element Separation =
(ForCES) Protocol</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Specification", RFC 5810, March 2010.</td><td> </td><td =
class=3D"right">              Specification", RFC 5810, March =
2010.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5811]  Hadi Salim, J. and K. Ogawa, "SCTP-Based Transport =
Mapping</td><td> </td><td class=3D"right">   [RFC5811]  Hadi Salim, J. =
and K. Ogawa, "SCTP-Based Transport Mapping</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Layer (TML) for the Forwarding and Control Element</td><td> =
</td><td class=3D"right">              Layer (TML) for the Forwarding =
and Control Element</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Separation (ForCES) Protocol", RFC 5811, March 2010.</td><td> =
</td><td class=3D"right">              Separation (ForCES) Protocol", =
RFC 5811, March 2010.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5812]  Halpern, J. and J. Hadi Salim, "Forwarding and =
Control</td><td> </td><td class=3D"right">   [RFC5812]  Halpern, J. and =
J. Hadi Salim, "Forwarding and Control</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0142" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             Element Separation (ForCES) Forwarding Element =
Model",</td><td> </td><td class=3D"rblock">              Element =
Separation (ForCES) Forwarding Element Model", RFC</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             RFC 5812, March 2010.</td><td> </td><td class=3D"rblock">   =
           5812, March 2010.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC5813]  Haas, R., "Forwarding and Control Element Separation</td><td> =
</td><td class=3D"right">   [RFC5813]  Haas, R., "Forwarding and Control =
Element Separation</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           (ForCES) MIB", RFC 5813, March 2010.</td><td> </td><td =
class=3D"right">              (ForCES) MIB", RFC 5813, March =
2010.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">10.2.  Informative References</td><td> </td><td =
class=3D"right">10.2.  Informative References</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[Ethereal]</td><td> </td><td class=3D"right">   [Ethereal]</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0143" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             "Ethereal, also named Wireshark, is a protocol =
analyzer.</td><td> </td><td class=3D"rblock">              <span =
class=3D"insert">, </span>"Ethereal, also named Wireshark, is a protocol =
analyzer.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           The specific Ethereal that was used is an updated</td><td> =
</td><td class=3D"right">              The specific Ethereal that was =
used is an updated</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Ethereal, by Fenggen Jia, that can analyze and decode =
the</td><td> </td><td class=3D"right">              Ethereal, by Fenggen =
Jia, that can analyze and decode the</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0144" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             ForCES protocol messages", <span =
class=3D"delete">http://www.ietf.org/</span></td><td> </td><td =
class=3D"rblock">              ForCES protocol messages", <span =
class=3D"insert">http://www.ietf.org/mail-</span></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">              =
mail-archive/web/forces/current/msg03687.html</span> .</td><td> </td><td =
class=3D"rblock"><span class=3D"insert">              =
archive/web/forces/current/msg03687.html ,</span> .</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[I-D.ietf-forces-ceha-00]</td><td> </td><td class=3D"right">   =
[I-D.ietf-forces-ceha-00]</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Ogawa, K., Wang, W., Haleplidis, E., and J. Salim, =
"ForCES</td><td> </td><td class=3D"right">              Ogawa, K., Wang, =
W., Haleplidis, E., and J. Salim, "ForCES</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Intra-NE High Availability", =
draft-ietf-forces-ceha-00</td><td> </td><td class=3D"right">             =
 Intra-NE High Availability", draft-ietf-forces-ceha-00</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0145" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             (work in <span class=3D"delete"> </span>progress) [RFC =
Editor Note: This reference is</td><td> </td><td class=3D"rblock">       =
       (work in progress) [RFC Editor Note: This reference is</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           intended to indicate a specific version of an =
Internet-</td><td> </td><td class=3D"right">              intended to =
indicate a specific version of an Internet-</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Draft that was used during interop testing. Please Do =
NOT</td><td> </td><td class=3D"right">              Draft that was used =
during interop testing. Please Do NOT</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0146" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             update this reference to a <span class=3D"delete"> =
</span>more recent version of the</td><td> </td><td class=3D"rblock">    =
          update this reference to a more recent version of the</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           draft or to an RFC. Please remove this note before</td><td> =
</td><td class=3D"right">              draft or to an RFC. Please remove =
this note before</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           publication] , October 2010.</td><td> </td><td =
class=3D"right">              publication] , October 2010.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[I-D.ietf-forces-lfb-lib-03]</td><td> </td><td class=3D"right">   =
[I-D.ietf-forces-lfb-lib-03]</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Wang, W., Haleplidis, E., Ogawa, K., Li, C., and J.</td><td> =
</td><td class=3D"right">              Wang, W., Haleplidis, E., Ogawa, =
K., Li, C., and J.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Halpern, "ForCES Logical Function Block (LFB) =
Library",</td><td> </td><td class=3D"right">              Halpern, =
"ForCES Logical Function Block (LFB) Library",</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0147" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             draft-ietf-forces-lfb-lib-03 (work in <span =
class=3D"delete"> </span>progress) [RFC</td><td> </td><td =
class=3D"rblock">              draft-ietf-forces-lfb-lib-03 (work in =
progress) [RFC</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Editor Note: This reference is intended to indicate =
a</td><td> </td><td class=3D"right">              Editor Note: This =
reference is intended to indicate a</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           specific version of an Internet-Draft that was used =
during</td><td> </td><td class=3D"right">              specific version =
of an Internet-Draft that was used during</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           interop testing. Please Do NOT update this reference to =
a</td><td> </td><td class=3D"right">              interop testing. =
Please Do NOT update this reference to a</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           more recent version of the draft or to an RFC. =
Please</td><td> </td><td class=3D"right">              more recent =
version of the draft or to an RFC. Please</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           remove this note before publication] , December =
2010.</td><td> </td><td class=3D"right">              remove this note =
before publication] , December 2010.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC3654]  Khosravi, H. and T. Anderson, "Requirements for =
Separation</td><td> </td><td class=3D"right">   [RFC3654]  Khosravi, H. =
and T. Anderson, "Requirements for Separation</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           of IP Control and Forwarding", RFC 3654, November =
2003.</td><td> </td><td class=3D"right">              of IP Control and =
Forwarding", RFC 3654, November 2003.</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC3746]  Yang, L., Dantu, R., Anderson, T., and R. Gopal,</td><td> =
</td><td class=3D"right">   [RFC3746]  Yang, L., Dantu, R., Anderson, =
T., and R. Gopal,</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           "Forwarding and Control Element Separation (ForCES)</td><td> =
</td><td class=3D"right">              "Forwarding and Control Element =
Separation (ForCES)</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Framework", RFC 3746, April 2004.</td><td> </td><td =
class=3D"right">              Framework", RFC 3746, April 2004.</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[RFC6053]  Haleplidis, E., Ogawa, K., Wang, W., and J. Hadi =
Salim,</td><td> </td><td class=3D"right">   [RFC6053]  Haleplidis, E., =
Ogawa, K., Wang, W., and J. Hadi Salim,</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           "Implementation Report for Forwarding and Control =
Element</td><td> </td><td class=3D"right">              "Implementation =
Report for Forwarding and Control Element</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Separation (ForCES)", RFC 6053, November 2010.</td><td> =
</td><td class=3D"right">              Separation (ForCES)", RFC 6053, =
November 2010.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0148" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  [Tcpdump]  "Tcpdump is a Linux protocol analyzer. The =
specific</td><td> </td><td class=3D"rblock">   [Tcpdump]  <span =
class=3D"insert">, </span>"Tcpdump is a Linux protocol analyzer. The =
specific</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           tcpdump that was used is a modified tcpdump, by Jamal =
Hadi</td><td> </td><td class=3D"right">              tcpdump that was =
used is a modified tcpdump, by Jamal Hadi</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           Salim, that can analyze and decode the ForCES =
protocol</td><td> </td><td class=3D"right">              Salim, that can =
analyze and decode the ForCES protocol</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
           messages", =
http://www.ietf.org/mail-archive/web/forces/</td><td> </td><td =
class=3D"right">              messages", =
http://www.ietf.org/mail-archive/web/forces/</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0149" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             current/msg03811.html .</td><td> </td><td class=3D"rblock"> =
             current/msg03811.html <span class=3D"insert">, =
</span>.</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
[Teamviewer]</td><td> </td><td class=3D"right">   [Teamviewer]</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0150" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             "TeamViewer connects to any PC or server around the =
world</td><td> </td><td class=3D"rblock">              <span =
class=3D"insert">,</span> "TeamViewer connects to any PC or server =
around the</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
             within a few <span class=3D"delete">seconds.",</span> =
http://www.teamviewer.com/ .</td><td> </td><td class=3D"rblock">         =
     world within a few <span class=3D"insert">seconds. ",</span> =
http://www.teamviewer.com/</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"></td><td> </td><td class=3D"rblock">              <span =
class=3D"insert">,</span> .</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left">Authors' Addresses</td><td> </td><td =
class=3D"right">Authors' Addresses</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Weiming Wang</td><td> </td><td class=3D"right">   Weiming Wang</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Zhejiang Gongshang University</td><td> </td><td class=3D"right">   =
Zhejiang Gongshang University</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
18 Xuezheng Str., Xiasha University Town</td><td> </td><td =
class=3D"right">   18 Xuezheng Str., Xiasha University Town</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0151" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Hangzhou<span class=3D"delete">, </span>  310018</td><td> </td><td =
class=3D"rblock">   Hangzhou  310018</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
P.R.China</td><td> </td><td class=3D"right">   P.R.China</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Phone: +86-571-28877721</td><td> </td><td class=3D"right">   Phone: =
+86-571-28877721</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Email: wmwang@zjsu.edu.cn</td><td> </td><td class=3D"right">   Email: =
wmwang@zjsu.edu.cn</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Kentaro Ogawa</td><td> </td><td class=3D"right">   Kentaro Ogawa</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
NTT Corporation</td><td> </td><td class=3D"right">   NTT =
Corporation</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0152" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Tokyo<span class=3D"delete">,</span></td><td> </td><td =
class=3D"rblock">   Tokyo</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Japan</td><td> </td><td class=3D"right">   Japan</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Email: ogawa.kentaro@lab.ntt.co.jp</td><td> </td><td class=3D"right">   =
Email: ogawa.kentaro@lab.ntt.co.jp</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Evangelos Haleplidis</td><td> </td><td class=3D"right">   Evangelos =
Haleplidis</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
University of Patras</td><td> </td><td class=3D"right">   University of =
Patras</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0153" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  <span class=3D"delete">Department of Electrical &amp; Computer =
Engineering</span></td><td> </td><td class=3D"rblock">   <span =
class=3D"insert">Patras</span></td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">   Patras,   =
26500</span></td><td> </td><td class=3D"rblock"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Greece</td><td> </td><td class=3D"right">   Greece</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Email: ehalep@ece.upatras.gr</td><td> </td><td class=3D"right">   Email: =
ehalep@ece.upatras.gr</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0154" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"lblock"><span class=3D"delete">                                 =
                                        </span></td><td> </td><td =
class=3D"rblock"></td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Ming Gao</td><td> </td><td class=3D"right">   Ming Gao</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Hangzhou BAUD Networks</td><td> </td><td class=3D"right">   Hangzhou =
BAUD Networks</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
408 Wen-San Road</td><td> </td><td class=3D"right">   408 Wen-San =
Road</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td><a name=3D"diff0155" /></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"lblock"> =
  Hangzhou<span class=3D"delete">, </span>  310012</td><td> </td><td =
class=3D"rblock">   Hangzhou  310012</td><td class=3D"lineno" =
valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
P.R.China</td><td> </td><td class=3D"right">   P.R.China</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Email: gmyyqno1@zjsu.edu.cn</td><td> </td><td class=3D"right">   Email: =
gmyyqno1@zjsu.edu.cn</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Jamal Hadi Salim</td><td> </td><td class=3D"right">   Jamal Hadi =
Salim</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Mojatatu Networks</td><td> </td><td class=3D"right">   Mojatatu =
Networks</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Ottawa</td><td> </td><td class=3D"right">   Ottawa</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Canada</td><td> </td><td class=3D"right">   Canada</td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td =
class=3D"left"></td><td> </td><td class=3D"right"></td><td =
class=3D"lineno" valign=3D"top"></td></tr>=0A=
      <tr><td class=3D"lineno" valign=3D"top"></td><td class=3D"left">   =
Email: hadi@mojatatu.com</td><td> </td><td class=3D"right">   Email: =
hadi@mojatatu.com</td><td class=3D"lineno" valign=3D"top"></td></tr>=0A=
=0A=
     <tr><td></td><td class=3D"left"></td><td> </td><td =
class=3D"right"></td><td></td></tr>=0A=
     <tr bgcolor=3D"gray"><th colspan=3D"5" align=3D"center"><a =
name=3D"end">&nbsp;End of changes. 155 change blocks.&nbsp;</a></th></tr>=0A=
     <tr class=3D"stats"><td></td><th><i>494 lines changed or =
deleted</i></th><th><i> </i></th><th><i>489 lines changed or =
added</i></th><td></td></tr>=0A=
     <tr><td colspan=3D"5" align=3D"center" class=3D"small"><br/>This =
html diff was produced by rfcdiff 1.41. The latest version is available =
from <a href=3D"http://www.tools.ietf.org/tools/rfcdiff/" =
>http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>=0A=
   </table>=0A=
   </body>=0A=
   </html>=0A=

------=_NextPart_000_01D6_01CE5745.6E793440
Content-Type: text/plain; name="draft-ietf-forces-interop-08v1.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
	filename="draft-ietf-forces-interop-08v1.txt"

=0A=
=0A=
=0A=
Internet Engineering Task Force                                  W. Wang=0A=
Internet-Draft                             Zhejiang Gongshang University=0A=
Updates: 6053 (if approved)                                     K. Ogawa=0A=
Intended status: Informational                           NTT Corporation=0A=
Expires: November 23, 2013                                 E. Haleplidis=0A=
                                                    University of Patras=0A=
                                                                  M. Gao=0A=
                                                  Hangzhou BAUD Networks=0A=
                                                           J. Hadi Salim=0A=
                                                       Mojatatu Networks=0A=
                                                            May 22, 2013=0A=
=0A=
=0A=
 Interoperability Report for Forwarding and Control Element Separation=0A=
                                (ForCES)=0A=
                      draft-ietf-forces-interop-08=0A=
=0A=
Abstract=0A=
=0A=
   This document captured results of the second Forwarding and Control=0A=
   Element Separation (ForCES) interoperability test which took place on=0A=
   February 24-25, 2011 in the Internet Technology Lab (ITL) of Zhejiang=0A=
   Gongshang University, China.  RFC 6053 had reported the results of=0A=
   the first ForCES interoperability test, and this document updates RFC=0A=
   6053 by providing further interoperability results.=0A=
=0A=
Status of this Memo=0A=
=0A=
   This Internet-Draft is submitted in full conformance with the=0A=
   provisions of BCP 78 and BCP 79.=0A=
=0A=
   Internet-Drafts are working documents of the Internet Engineering=0A=
   Task Force (IETF).  Note that other groups may also distribute=0A=
   working documents as Internet-Drafts.  The list of current Internet-=0A=
   Drafts is at http://datatracker.ietf.org/drafts/current/.=0A=
=0A=
   Internet-Drafts are draft documents valid for a maximum of six months=0A=
   and may be updated, replaced, or obsoleted by other documents at any=0A=
   time.  It is inappropriate to use Internet-Drafts as reference=0A=
   material or to cite them other than as "work in progress."=0A=
=0A=
   This Internet-Draft will expire on November 23, 2013.=0A=
=0A=
Copyright Notice=0A=
=0A=
   Copyright (c) 2013 IETF Trust and the persons identified as the=0A=
   document authors.  All rights reserved.=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 1]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   This document is subject to BCP 78 and the IETF Trust's Legal=0A=
   Provisions Relating to IETF Documents=0A=
   (http://trustee.ietf.org/license-info) in effect on the date of=0A=
   publication of this document.  Please review these documents=0A=
   carefully, as they describe your rights and restrictions with respect=0A=
   to this document.  Code Components extracted from this document must=0A=
   include Simplified BSD License text as described in Section 4.e of=0A=
   the Trust Legal Provisions and are provided without warranty as=0A=
   described in the Simplified BSD License.=0A=
=0A=
=0A=
Table of Contents=0A=
=0A=
   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3=0A=
     1.1.  ForCES Protocol  . . . . . . . . . . . . . . . . . . . . .  3=0A=
     1.2.  ForCES FE Model  . . . . . . . . . . . . . . . . . . . . .  4=0A=
     1.3.  Transport Mapping Layer  . . . . . . . . . . . . . . . . .  4=0A=
     1.4.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  4=0A=
   2.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  5=0A=
     2.1.  Date, Location, and Participants . . . . . . . . . . . . .  5=0A=
     2.2.  Testbed Configuration  . . . . . . . . . . . . . . . . . .  5=0A=
       2.2.1.  Participants Access  . . . . . . . . . . . . . . . . .  6=0A=
       2.2.2.  Testbed Configuration  . . . . . . . . . . . . . . . .  6=0A=
   3.  Scenarios  . . . . . . . . . . . . . . . . . . . . . . . . . .  9=0A=
     3.1.  Scenario 1 - LFB Operation . . . . . . . . . . . . . . . .  9=0A=
     3.2.  Scenario 2 - TML with IPSec  . . . . . . . . . . . . . . .  9=0A=
     3.3.  Scenario 3 - CE High Availability  . . . . . . . . . . . . 10=0A=
     3.4.  Scenario 4 - Packet forwarding . . . . . . . . . . . . . . 12=0A=
   4.  Test Results . . . . . . . . . . . . . . . . . . . . . . . . . 15=0A=
     4.1.  LFB Operation Test . . . . . . . . . . . . . . . . . . . . 15=0A=
     4.2.  TML with IPSec Test  . . . . . . . . . . . . . . . . . . . 20=0A=
     4.3.  CE High Availability Test  . . . . . . . . . . . . . . . . 21=0A=
     4.4.  Packet Forwarding Test . . . . . . . . . . . . . . . . . . 22=0A=
   5.  Discussions  . . . . . . . . . . . . . . . . . . . . . . . . . 25=0A=
     5.1.  On Data Encapsulation Format . . . . . . . . . . . . . . . 25=0A=
   6.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 28=0A=
   7.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 29=0A=
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 30=0A=
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 31=0A=
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32=0A=
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 32=0A=
     10.2. Informative References . . . . . . . . . . . . . . . . . . 32=0A=
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 34=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 2]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
1.  Introduction=0A=
=0A=
   This document captured results of the second interoperability test of=0A=
   the Forwarding and Control Element Separation (ForCES) which took=0A=
   place February 24-25, 2011 in the Internet Technology Lab (ITL) of=0A=
   Zhejiang Gongshang University, China.  The test involved protocol=0A=
   elements described in several documents namely:=0A=
=0A=
      - ForCES Protocol [RFC5810]=0A=
      - ForCES Forwarding Element (FE) Model [RFC5812]=0A=
      - ForCES Transport Mapping Layer (TML) [RFC5811]=0A=
=0A=
   The test also involved protocol elements described in the then-=0A=
   current versions of two Internet-Drafts.  Although these documents=0A=
   have subsequently been revised and advanced, it is important to=0A=
   understand which versions of the work were used during this test.=0A=
   The then-current Internet-Drafts were:=0A=
=0A=
      - ForCES Logical Function Block (LFB) Library=0A=
      [I-D.ietf-forces-lfb-lib-03].=0A=
      - ForCES Intra-NE High Availability [I-D.ietf-forces-ceha-00].=0A=
=0A=
   Up to date, the 'ForCES Logical Function Block (LFB) Library'=0A=
   document has been publilshed by IETF as RFC 6956.=0A=
=0A=
   Three independent ForCES implementations participated in the test.=0A=
=0A=
   Scenarios of ForCES LFB Operation, TML with IPSec, CE High=0A=
   Availability, and Packet Forwarding were constructed.  Series of=0A=
   testing items for every scenario were carried out and=0A=
   interoperability results were achieved.  Popular packet analyzers=0A=
   Ethereal/Wireshark[Ethereal] and Tcpdump[Tcpdump] were used to verify=0A=
   the wire results.=0A=
=0A=
   This document is an update to RFC 6053, which captured the results of=0A=
   the first ForCES interoperability test.  The first test on ForCES was=0A=
   held in July 2008 at the University of Patras, Greece.  That test=0A=
   focused on validating the basic semantics of the ForCES protocol and=0A=
   ForCES FE model.=0A=
=0A=
1.1.  ForCES Protocol=0A=
=0A=
   The ForCES protocol works in a master-slave mode in which Forwarding=0A=
   Elements (FEs) are slaves and Control Elements (CEs) are masters.=0A=
   The protocol includes commands for transport of Logical Function=0A=
   Block (LFB) configuration information, association setup, status, and=0A=
   event notifications, etc.  The reader is encouraged to read the=0A=
   ForCES protocol specification [RFC5810] for further information.=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 3]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
1.2.  ForCES FE Model=0A=
=0A=
   The ForCES Forwarding Element (FE) model [RFC5812] presents a formal=0A=
   way to define FE Logical Function Blocks (LFBs) using XML.  LFB=0A=
   configuration components, capabilities, and associated events are=0A=
   defined when the LFB is formally created.  The LFBs within the FE are=0A=
   accordingly controlled in a standardized way by the ForCES protocol.=0A=
=0A=
1.3.  Transport Mapping Layer=0A=
=0A=
   The ForCES Transport Mapping Layer (TML) transports the ForCES=0A=
   Protocol Layer (PL) messages.  The TML is where the issues of how to=0A=
   achieve transport level reliability, congestion control, multicast,=0A=
   ordering, etc are handled.  It is expected that more than one TML=0A=
   will be standardized.  RFC 5811 specifies an SCTP-Based Transport=0A=
   Mapping Layer (TML) for ForCES protocol, which is a mandated TML for=0A=
   ForCES.  See RFC 5811 for more details.=0A=
=0A=
1.4.  Definitions=0A=
=0A=
   This document follows the terminology defined by ForCES related=0A=
   documents, including RFC3654, RFC3746, RFC5810, RFC5811, RFC5812,=0A=
   RFC5813, etc.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 4]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
2.  Overview=0A=
=0A=
2.1.  Date, Location, and Participants=0A=
=0A=
   The second ForCES interoperability test meeting was held by IETF=0A=
   ForCES Working Group on February 24-25, 2011, and was chaired by=0A=
   Jamal Hadi Salim.  Three independent ForCES implementations=0A=
   participated in the test:=0A=
=0A=
   o  Zhejiang Gongshang University/Hangzhou BAUD Corporation of=0A=
      Information and Networks Technology (Hangzhou BAUD Networks),=0A=
      China.  This implementation is referred to as "ZJSU" or in some=0A=
      cases "Z" in the document for the sake of brevity.=0A=
=0A=
   o  NTT Corporation, Japan.  This implementation is referred to as=0A=
      "NTT" or in some cases "N" in the document for the sake of=0A=
      brevity.=0A=
=0A=
   o  The University of Patras, Greece.  This implementation is referred=0A=
      to as "UoP" or in some cases "P" in the document for the sake of=0A=
      brevity.=0A=
=0A=
   Two other organizations, Mojatatu Networks and Hangzhou BAUD Networks=0A=
   Corporation, which independently extended two different well known=0A=
   public domain protocol analyzers, Ethereal/Wireshark [Ethereal] and=0A=
   Tcpdump [Tcpdump], also participated in the interop test.  During the=0A=
   interoperability test, the two protocol analyzers were used to verify=0A=
   the validity of ForCES protocol messages and in some cases semantics.=0A=
=0A=
   Some issues related to interoperability among implementations were=0A=
   discovered.  Most of the issues were solved on site during the test.=0A=
   The most contentious issue found was on the format of encapsulation=0A=
   for protocol TLV (Refer to Section 5.1 ).=0A=
=0A=
   Some errata related to ForCES document were found by the=0A=
   interoperability test.  The errata has been reported to related IETF=0A=
   RFCs.=0A=
=0A=
   At times, interoperability testing was exercised between two instead=0A=
   of all three representative implementations due to a third one=0A=
   lacking a specific feature; however, in ensuing discussions, all=0A=
   implementers mentioned they would be implementing any missing=0A=
   features in the future.=0A=
=0A=
2.2.  Testbed Configuration=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 5]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
2.2.1.  Participants Access=0A=
=0A=
   NTT and ZJSU physically attended on site at the Internet Technology=0A=
   Lab (ITL) of Zhejiang Gongshang University in China.  The University=0A=
   of Patras implementation joined remotely from Greece.  The chair,=0A=
   Jamal Hadi Salim, joined remotely from Canada by using the Teamviewer=0A=
   as the monitoring tool[Teamviewer].  The approach is as shown in=0A=
   Figure 1.  In the figure, FE/CE refers to FE or CE that the=0A=
   implementer may act alternatively.=0A=
=0A=
=0A=
        +---------+     +----+                    +----------+=0A=
        |  FE/CE  |     |    |                +---|Monitoring|=0A=
        |  ZJSU   |-----|    |    /\/\/\/\/\  |   |(TeamViewer)=0A=
        +---------+     |    |    \Internet/  |   | Mojatatu |=0A=
                        |LAN |----/        \--|   +----------+=0A=
        +---------+     |    |    \/\/\/\/\/  |   +----------+=0A=
        |  FE/CE  |-----|    |                |   |  FE/CE   |=0A=
        |   NTT   |     |    |                +---|   UoP    |=0A=
        +---------+     +----+                    +----------+=0A=
=0A=
                     Figure 1: Access for Participants=0A=
=0A=
   As specified in RFC 5811, all CEs and FEs shall implement IPSec=0A=
   security in the TML.=0A=
=0A=
   On the internet boundary, gateways used must allow for IPSec, SCTP=0A=
   protocol and SCTP ports as defined in the ForCES SCTP-TML [RFC5811] .=0A=
=0A=
2.2.2.  Testbed Configuration=0A=
=0A=
   CEs and FEs from ZJSU and NTT implementations were physically located=0A=
   within the ITL Lab of Zhejiang Gongshang University and connected=0A=
   together using Ethernet switches.  The configuration can be seen in=0A=
   Figure 2.  In the figure, the SmartBits was a third-party supplied=0A=
   routing protocol testing machine, which acted as a router running=0A=
   OSPF and RIP and exchanged routing protocol messages with ForCES=0A=
   routers in the network.  Connection to the Internet was via an ADSL=0A=
   channel.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 6]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
                              /\/\/\/\/\=0A=
                              \Internet/=0A=
                              /        \=0A=
                              \/\/\/\/\/=0A=
                                  |=0A=
                                  |(ADSL)=0A=
                                  |=0A=
   +------------------------------------------------------------------+=0A=
   |                      LAN  (10.20.0.0/24)                         |=0A=
   +------------------------------------------------------------------+=0A=
      |        |        |               |               |         |=0A=
      |        |        |               |               |         |=0A=
      |.222    |.230    |.221           |.179           |.231     |.220=0A=
   +-----+  +-----+  +-----+         +-----+         +-----+ +---------+=0A=
   | CE  |  | CE  |  |     |         |     |         |     | | Protocol|=0A=
   |ZJSU |  | NTT |  | FE1 |.1     .2| FE  |.1     .2| FE2 | | Analyzer|=0A=
   +-----+  +-----+  |ZJSU |---------| NTT |---------|ZJSU | +---------+=0A=
           +---------|     |192.169. |     | 192.168.|     |------+=0A=
           |      .2 +-----+ 20.0.24 +-----+  30.0/24+-----+ .2   |=0A=
           |         .12|                               |.12      |=0A=
           |            |                               |         |=0A=
     192.168.50.0/24    |                               |192.168.60.0/24=0A=
           |       192.168.10.0/24              192.168.40.0/24   |=0A=
        .1 |            |.11                            |.11      |.1=0A=
      +--------+     +--------------------------------------+ +--------+=0A=
      |Terminal|     |               Smartbits              | |Terminal|=0A=
      +--------+     +--------------------------------------+ +--------+=0A=
=0A=
         Figure 2: Testbed Configuration Located in ITL Lab,China=0A=
=0A=
   CE and FE from the UoP implementation were located within the=0A=
   University of Patras, Greece, and were connected together using LAN=0A=
   as shown in Figure 3.  Connection to the Internet was via a VPN=0A=
   channel.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 7]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
                               /\/\/\/\/\=0A=
                               \Internet/=0A=
                               /        \=0A=
                               \/\/\/\/\/=0A=
                                   |=0A=
                                   |(VPN)=0A=
                                   |=0A=
                +------------------------------------+=0A=
                |                LAN                 |=0A=
                +------------------------------------+=0A=
                     |           |             |=0A=
                     |           |             |=0A=
                 +------+    +--------+     +------+=0A=
                 |  FE  |    |Protocol|     |  CE  |=0A=
                 | UoP  |    |Analyzer|     |  UoP |=0A=
                 +------+    +--------+     +------+=0A=
=0A=
       Figure 3: Testbed Configuration Located in the University of=0A=
                               Patras,Greece=0A=
=0A=
   All above testbed configurations were then able to satisfy=0A=
   requirements of all the interoperability test scenarios that were=0A=
   mentioned in this document.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 8]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
3.  Scenarios=0A=
=0A=
3.1.  Scenario 1 - LFB Operation=0A=
=0A=
   This scenario was to test the interoperability on LFB operations=0A=
   among the participants.  The connection diagram for the participants=0A=
   is as shown in Figure 4.=0A=
=0A=
    +------+    +------+    +------+    +------+    +------+    +------+=0A=
    |  CE  |    |  CE  |    |  CE  |    |  CE  |    |  CE  |    |  CE  |=0A=
    | ZJSU |    | NTT  |    | ZJSU |    |  UoP |    |  NTT |    |  UoP |=0A=
    +------+    +------+    +------+    +------+    +------+    +------+=0A=
       |           |           |           |           |           |=0A=
       |           |           |           |           |           |=0A=
    +------+    +------+    +------+    +------+    +------+    +------+=0A=
    |  FE  |    |  FE  |    |  FE  |    |  FE  |    |  FE  |    |  FE  |=0A=
    | NTT  |    | ZJSU |    | UoP  |    | ZJSU |    |  UoP |    |  NTT |=0A=
    +------+    +------+    +------+    +------+    +------+    +------+=0A=
=0A=
                   Figure 4: Scenario for LFB Operation=0A=
=0A=
   In order to make interoperability more credible, the three=0A=
   implementers were required to carry out the test in a way acting as=0A=
   CE or FE alternatively.  As a result, every LFB operation was=0A=
   combined with 6 scenarios, as shown by Figure 4.=0A=
=0A=
   The test scenario was designed with the following purposes:=0A=
=0A=
   Firstly, the scenario was designed to verify all kinds of protocol=0A=
   messages with their complex data formats, which are defined in RFC=0A=
   5810.  Specially, we tried to verify the data format of a PATH-DATA=0A=
   with nested PATH-DATAs, and the operation(SET, GET, DEL) of an array=0A=
   or an array with a nested array.=0A=
=0A=
   Secondly, the scenario was designed to verify the definition of=0A=
   ForCES LFB Library [I-D.ietf-forces-lfb-lib-03], which defined a base=0A=
   set of ForCES LFB classes for typical router functions.  Successful=0A=
   test under this scenario may help the validity of the LFB=0A=
   definitions.=0A=
=0A=
3.2.  Scenario 2 - TML with IPSec=0A=
=0A=
   This scenario was designed to implement a TML with IPSec, which is=0A=
   the requirement by RFC 5811.  TML with IPSec was not implemented in=0A=
   the first ForCES interoperability test as reported by RFC 6053.  For=0A=
   this reason, in the second interoperability test, we specifically=0A=
   designed the test scenario to verify the TML over IPSec channel.=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013               [Page 9]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   In this scenario, tests on LFB operations for Scenario 1 were=0A=
   repeated with the difference that TML was secured via IPSec.  This=0A=
   setup scenario allowed us to verify whether all interactions between=0A=
   CE and FE could be made correctly under an IPSec TML environment.=0A=
=0A=
   The connection diagram for this scenario was shown as Figure 5.=0A=
   Because an unfortunate problem with the test system in UoP prevented=0A=
   the deployment of IPSec over TML, this test only took place between=0A=
   the test systems in ZJSU and NTT.=0A=
=0A=
                 +------+                 +------+=0A=
                 |  CE  |                 |  CE  |=0A=
                 | ZJSU |                 |  NTT |=0A=
                 +------+                 +------+=0A=
                    |                        |=0A=
                    |TML over IPSec          |TML over IPSec=0A=
                 +------+                 +------+=0A=
                 |  FE  |                 |  FE  |=0A=
                 | NTT  |                 | ZJSU |=0A=
                 +------+                 +------+=0A=
=0A=
         Figure 5: Scenario for LFB Operation with TML over IPSec=0A=
=0A=
   In this scenario, ForCES TML was run over the IPSec channel.=0A=
   Implementers joined in this interoperability have used the same=0A=
   third-party software 'racoon' to establish the IPSec channel.  The=0A=
   'racoon' in NetBSD is a well-known IKE daemon performing the IPsec=0A=
   Key Exchange (IKE) with the peers.=0A=
=0A=
   ZJSU and NTT made a successful test with the scenario, and the=0A=
   following items were realized:=0A=
=0A=
   o  Internet Key Exchange (IKE) with certificates for endpoint=0A=
      authentication.=0A=
=0A=
   o  Transport Mode Encapsulating Security Payload (ESP).  HMAC-SHA1-96=0A=
      for message integrity protection.=0A=
=0A=
3.3.  Scenario 3 - CE High Availability=0A=
=0A=
   CE High Availability (CEHA) was tested based on the ForCES CEHA=0A=
   document [I-D.ietf-forces-ceha-00]=0A=
=0A=
   The design of the setup and the scenario for the CEHA were simplified=0A=
   so as to focus mostly on the mechanics of the CEHA, which were:=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 10]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   o  Associating with more than one CE.=0A=
=0A=
   o  Switching to backup CE on master CE failure.=0A=
=0A=
   The connection diagram for the scenario was as shown in Figure 6.=0A=
=0A=
            master     standby            master     standby=0A=
            +------+    +------+          +------+    +------+=0A=
            |  CE  |    |  CE  |          |  CE  |    |  CE  |=0A=
            | ZJSU |    |  UoP |          | NTT  |    |  UoP |=0A=
            +------+    +------+          +------+    +------+=0A=
               |          |                  |           |=0A=
               +----------+                  +-----------+=0A=
               |                             |=0A=
            +------+                      +------+=0A=
            |  FE  |                      |  FE  |=0A=
            | UoP  |                      | UoP  |=0A=
            +------+                      +------+=0A=
                   (a)                           (b)=0A=
=0A=
                Figure 6: Scenario for CE High Availability=0A=
=0A=
   In this scenario one FE was connected and associated to a master CE=0A=
   and a backup CE.  In the pre-association phase, the FE would be=0A=
   configured to have ZJSU's or NTT's CE as master CE and UoP's CE as=0A=
   standby CE.  The CEFailoverPolicy component of the FE Protocol Object=0A=
   LFB that specified whether the FE was in High Availability mode=0A=
   (value 2 or 3) would either be set in the pre-association phase by=0A=
   the FEM interface or in post-association phase by the master CE.=0A=
=0A=
   If the CEFailoverPolicy value was set to 2 or 3, the FE (in the post-=0A=
   association phase) would attempt to connect and associate with the=0A=
   standby CE.=0A=
=0A=
   When the master CE was deemed disconnected, either by a TearDown,=0A=
   Loss of Heartbeats or physically disconnected, the FE would assume=0A=
   that the standby CE was now the master CE.  The FE would then send an=0A=
   Event Notification, Primary CE Down,to all associated CEs, only the=0A=
   standby CE in this case, with the value of the new master CEID.  The=0A=
   standby CE would then respond by sending a configuration message to=0A=
   the CEID component of the FE Protocol Object with its own ID to=0A=
   confirm that the CE considered itself as the master as well.=0A=
=0A=
   The steps of the CEHA test scenario were as follows:=0A=
=0A=
   1.  In the pre-association phase, setup of FE with master CE and=0A=
       backup CE=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 11]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   2.  FE connecting and associating with master CE.=0A=
=0A=
   3.  When CEFailoverPolicy is set to 2 or 3, the FE will connect and=0A=
       associate with backup CE.=0A=
=0A=
   4.  Once the master CE is considered disconnected then the FE chooses=0A=
       the first Associated backup CE.=0A=
=0A=
   5.  It sends an Event Notification specifying that the master CE is=0A=
       down and who is now the master CE.=0A=
=0A=
   6.  The new master CE sends a SET Configuration message to the FE=0A=
       setting the CEID value to who is now the new master CE completing=0A=
       the switch.=0A=
=0A=
3.4.  Scenario 4 - Packet forwarding=0A=
=0A=
   This test scenario was to verify LFBs like RedirectIn, RedirectOut,=0A=
   IPv4NextHop, IPv4UcastLPM defined by the ForCES LFB library document=0A=
   [I-D.ietf-forces-lfb-lib-03], and more importantly, to verify the=0A=
   combination of the LFBs to implement IP packet forwarding.=0A=
=0A=
   The connection diagram for this scenario was as Figure 7.=0A=
=0A=
                               +------+=0A=
                               |  CE  |=0A=
                               |  NTT |=0A=
                               +------+=0A=
                                  |  ^=0A=
                                  |  | OSPF=0A=
                                  |  +------->=0A=
                               +------+       +------+=0A=
               +--------+      |  FE  |       | OSPF |      +--------+=0A=
               |Terminal|------| ZJSU |-------|Router|------|Terminal|=0A=
               +--------+      +------+       +------+      +--------+=0A=
=0A=
                 <-------------------------------------------->=0A=
                             Packet Forwarding=0A=
=0A=
                                    (a)=0A=
=0A=
=0A=
                                      +------+=0A=
                                      |  CE  |=0A=
                                      | ZJSU |=0A=
                                      +------+=0A=
                                       ^  |  ^=0A=
                                  OSPF |  |  | OSPF=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 12]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
                                 <-----+  |  +----->=0A=
                         +-------+    +------+     +------+=0A=
           +--------+    | OSPF  |    |  FE  |     | OSPF |  +--------+=0A=
           |Terminal|----|Router |----| NTT  |-----|Router|--|Terminal|=0A=
           +--------+    +-------+    +------+     +------+  +--------+=0A=
=0A=
                   <-------------------------------------------->=0A=
                             Packet Forwarding=0A=
=0A=
                                    (b)=0A=
=0A=
=0A=
                               +------+       +------+=0A=
                               |  CE  |       |  CE  |=0A=
                               | NTT  |       | ZJSU |=0A=
                               +------+       +------+=0A=
                                  |  ^          ^ |=0A=
                                  |  |   OSPF   | |=0A=
                                  |  +----------+ |=0A=
                               +------+       +------+=0A=
               +--------+      |  FE  |       |  FE  |      +--------+=0A=
               |Terminal|------| ZJSU |-------|  NTT |------|Terminal|=0A=
               +--------+      +------+       +------+      +--------+=0A=
=0A=
                 <-------------------------------------------->=0A=
                              Packet Forwarding=0A=
=0A=
                                    (c)=0A=
=0A=
                Figure 7: Scenario for IP Packet forwarding=0A=
=0A=
   In case (a), a CE by NTT was connected to an FE by ZJSU to form a=0A=
   ForCES router.  A Smartbits test machine with its routing protocol=0A=
   software were used to simulate an OSPF router and were connected with=0A=
   the ForCES router to try to exchange OSPF hello packets and LSA=0A=
   packets among them.  Terminals were simulated by Smartbits to send=0A=
   and receive packets.  As a result, the CE in the ForCES router needed=0A=
   to be configured to run and support OSPF routing protocol.=0A=
=0A=
   In case (b), a CE by ZJSU was connected to an FE by NTT to form a=0A=
   ForCES router.  Two routers running OSPF were simulated and connected=0A=
   to the ForCES router to test if the ForCES router could support OSPF=0A=
   protocol and support packet forwarding.=0A=
=0A=
   In case (c), two ForCES routers were constructed.  One was with CE by=0A=
   NTT and FE by ZJSU and the other was opposite.  OSPF and packet=0A=
   forwarding were tested in the environment.=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 13]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   Testing process for this scenario was as below:=0A=
=0A=
   1.  Boot terminals and routers, and set IP addresses of their=0A=
       interfaces.=0A=
=0A=
   2.  Boot CE and FE.=0A=
=0A=
   3.  Establish association between CE and FE, and set IP addresses of=0A=
       FEs interfaces.=0A=
=0A=
   4.  Start OSPF among CE and routers, and set FIB on FE.=0A=
=0A=
   5.  Send packets between terminals.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 14]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
4.  Test Results=0A=
=0A=
4.1.  LFB Operation Test=0A=
=0A=
   The test result was as reported by Figure 8.  For the convenience=0A=
   sake, as mentioned earlier, abbreviations of 'Z' in the table means=0A=
   implementation from ZJSU ,'N' NTT implementation, and 'P' UoP=0A=
   implementation.=0A=
=0A=
   +-----+----+-----+-----+--------------+-------------------+---------+=0A=
   |Test#| CE |FE(s)|Oper |      LFB     |     Component     | Result  |=0A=
   |     |    |     |     |              |    /Capability    |         |=0A=
   +-----+----+-----+-----+--------------+-------------------+---------+=0A=
   |  1  | Z  |  N  | GET |   FEObject   |    LFBTopology    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  2  | Z  |  N  | GET |   FEObject   |    LFBSelector    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  3  | Z  |  N  | GET |  EtherPHYCop |     PHYPortID     | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  4  | Z  |  N  | GET |  EtherPHYCop |    AdminStatus    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  5  | Z  |  N  | GET |  EtherPHYCop |     OperStatus    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  6  | Z  |  N  | GET |  EtherPHYCop |  AdminLinkSpeed   | Success |=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 15]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  7  | Z  |  N  | GET |  EtherPHYCop |   OperLinkSpeed   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  8  | Z  |  N  | GET |  EtherPHYCop |  AdminDuplexSpeed | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  9  | Z  |  N  | GET |  EtherPHYCop |  OperDuplexSpeed  | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  10 | Z  |  N  | GET |  EtherPHYCop |   CarrierStatus   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  11 | Z  |  N  | GET |  EtherMACIn  |    AdminStatus    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  12 | Z  |  N  | GET |  EtherMACIn  | LocalMacAddresses | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 16]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   |  13 | Z  |  N  | GET |  EtherMACIn  |    L2Bridging     | Success |=0A=
   |     | N  |  Z  |     |              |   PathEnable      | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  14 | Z  |  N  | GET |  EtherMACIn  |  PromiscuousMode  | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  15 | Z  |  N  | GET |  EtherMACIn  |   TxFlowControl   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  16 | Z  |  N  | GET |  EtherMACIn  |   RxFlowControl   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  17 | Z  |  N  | GET |  EtherMACIn  |     MACInStats    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   | 18  | Z  |  N  | GET | EtherMACOut  |     AdminStatus   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   | 19  | Z  |  N  | GET |  EtherMACOut |          MTU      | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 17]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  20 | Z  |  N  | GET |  EtherMACOut |    TxFlowControl  | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  21 | Z  |  N  | GET |  EtherMACOut |    TxFlowControl  | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  22 | Z  |  N  | GET |  EtherMACOut |     MACOutStats   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  23 | Z  |  N  | GET |      ARP     |PortV4AddrInfoTable| Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  24 | Z  |  N  | SET |      ARP     |PortV4AddrInfoTable| Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  25 | Z  |  N  | DEL |      ARP     |PortV4AddrInfoTable| Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  26 | Z  |  N  | SET |  EtherMACIn  | LocalMACAddresses | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 18]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  27 | Z  |  N  | SET |  EtherMACIn  |          MTU      | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  28 | Z  |  N  | SET |  IPv4NextHop |  IPv4NextHopTable | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  29 | Z  |  N  | SET | IPv4UcastLPM |  IPv4PrefixTable  | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  30 | Z  |  N  | DEL |  IPv4NextHop |  IPv4NextHopTable | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  31 | Z  |  N  | DEL | IPv4UcastLPM |  IPv4PrefixTable  | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  32 | Z  |  N  | SET |  EtherPHYCop |     AdminStatus   | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  33 | Z  |  N  | SET |     Ether    |   VlanInputTable  | Success |=0A=
   |     | N  |  Z  |     |  Classifier  |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 19]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  34 | Z  |  N  | DEL |     Ether    |   VlanInputTable  | Success |=0A=
   |     | N  |  Z  |     |  Classifier  |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  35 | Z  |  N  | SET |   Ether      |  VlanOutputTable  | Success |=0A=
   |     | N  |  Z  |     | Encapsulator |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  36 | Z  |  N  | DEL |    Ether     |   VlanOutputTable | Success |=0A=
   |     | N  |  Z  |     | Encapsulator |                   | Success |=0A=
   |     | Z  |  P  |     |              |                   | Success |=0A=
   |     | P  |  Z  |     |              |                   | Success |=0A=
   |     | N  |  P  |     |              |                   | Success |=0A=
   |     | P  |  N  |     |              |                   | Success |=0A=
   +-----+----+-----+-----+--------------+-------------------+---------+=0A=
=0A=
                   Figure 8: LFB Operation Test Results=0A=
=0A=
   Note on test #1:=0A=
=0A=
   On the wire format of encapsulation on array, only the case of=0A=
   FULLDATA-in-FULLDATA was tested.=0A=
=0A=
   In ZJSU's implementation, after test #2 CE have to get all LFBs'=0A=
   instance data actively according to the queried component of=0A=
   LFBSelectors.=0A=
=0A=
4.2.  TML with IPSec Test=0A=
=0A=
   In this scenario, the ForCES TML was run over IPSec.  Implementers=0A=
   joined this interoperability test used the same third-party tool=0A=
   software 'racoon' to establish IPSec channel.  Some typical LFB=0A=
   operation tests as in Scenario 1 were repeated with the IPSec enabled=0A=
   TML.=0A=
=0A=
   As mentioned, this scenario only took place between implementers of=0A=
   ZJSU and NTT.=0A=
=0A=
   The TML with IPSec test results are reported by Figure 9.=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 20]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   +-----+----+-----+-----+--------------+-------------------+---------+=0A=
   |Test#| CE |FE(s)|Oper |       LFB    |     Component/    | Result  |=0A=
   |     |    |     |     |              |     Capability    |         |=0A=
   +-----+----+-----+-----+--------------+-------------------+---------+=0A=
   |  1  | Z  |  N  | GET |   FEObject   |   LFBTopology     | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  2  | Z  |  N  | GET |   FEObject   |   LFBSelectors    | Success |=0A=
   |     | N  |  Z  |     |              |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  3  | Z  |  N  | SET |   Ether      |   VlanInputTable  | Success |=0A=
   |     | N  |  Z  |     | Classifier   |                   | Success |=0A=
   |     |    |     |     |              |                   |         |=0A=
   |  4  | Z  |  N  | DEL |   Ether      |   VlanInputTable  | Success |=0A=
   |     | N  |  Z  |     | Classifier   |                   | Success |=0A=
   +-----+----+-----+-----+--------------+-------------------+---------+=0A=
=0A=
                   Figure 9: TML with IPSec Test Results=0A=
=0A=
4.3.  CE High Availability Test=0A=
=0A=
   In this scenario one FE connects and associates with a master CE and=0A=
   a backup CE.  When the master CE is deemed disconnected the FE would=0A=
   attempt to find another associated CE to become the master CE.=0A=
=0A=
   The CEHA scenario as is described in Scenario 3 was completed=0A=
   successfully for both setups.=0A=
=0A=
   Due to a bug in one of the FEs, a interesting issue was caught: it=0A=
   was observed that the buggy FE took up to a second to failover.  It=0A=
   was eventually found that the issue was due to the FE's=0A=
   prioritization of the different CEs.  All messages from the backup CE=0A=
   were being ignored unless the master CE is disconnected.=0A=
=0A=
   While the bug was fixed and the CEHA scenario was completed=0A=
   successfully, the authors feel it was important to capture the=0A=
   implementation issue in this document.  The recommended approach is=0A=
   the following:=0A=
=0A=
   o  The FE should receive and handle messages first from the master CE=0A=
      on all priority channels to maintain proper functionality and then=0A=
      receive and handle messages from the backup CEs.=0A=
=0A=
   o  Only when the FE is attempting to associate with the backup CEs,=0A=
      then the FE should receive and handle messages per priority=0A=
      channel from all CEs.  When all backup CEs are associated with or=0A=
      deemed unreachable, then the FE should return to receiving and=0A=
      handling messages first from the master CE.=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 21]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
4.4.  Packet Forwarding Test=0A=
=0A=
   As described in the ForCES LFB library [I-D.ietf-forces-lfb-lib-03],=0A=
   packet forwarding is implemented by a set of LFB classes that compose=0A=
   a processing path for packets.  In this test scenario, as shown in=0A=
   Figure 7, a ForCES router running OSPF protocol was constructed.  In=0A=
   addition, a set of LFBs including RedirectIn, RedirectOut,=0A=
   IPv4UcastLPM, and IPv4NextHop LFBs are used.  RedirectIn and=0A=
   RedirectOut LFBs redirect OSPF hello and LSA packets from and to CE.=0A=
   A Smartbits test machine is used to simulate an OSPF router and=0A=
   exchange the OSPF hello and LSA packets with CE in ForCES router.=0A=
=0A=
   Cases (a) and (b) in Figure 7 both need a RedirectIn LFB to send OSPF=0A=
   packets generated by CE to FE by use of ForCES packet redirect=0A=
   messages.  The OSPF packets are further sent to an outside OSPF=0A=
   Router by the FE via forwarding LFBs including IPv4NextHop and=0A=
   IPv4UcastLPM LFBs.  A RedirectOut LFB in the FE is used to send OSPF=0A=
   packets received from outside OSPF Router to CE by ForCES packet=0A=
   redirect messages.=0A=
=0A=
   By running OSPF, the CE in the ForCES router can generate new routes=0A=
   and load them to routing table in FE.  The FE is then able to forward=0A=
   packets according to the routing table.=0A=
=0A=
   The test is reported with the results in Figure 10=0A=
=0A=
   +-----+----+-----+-------------------------+--------------+---------+=0A=
   |Test#| CE |FE(s)|           Item          | LFBs Related | Result  |=0A=
   +-----+----+-----+-------------------------+--------------+---------+=0A=
   |  1  | N  |  Z  |  IPv4NextHopTable SET   | IPv4NextHop  | Success |=0A=
   |     |    |     |                         |              |         |=0A=
   |  2  | N  |  Z  |   IPv4PrefixTable SET   | IPv4UcastLPM | Success |=0A=
   |     |    |     |                         |              |         |=0A=
   |  3  | N  |  Z  |Redirect OSPF packet from|  RedirectIn  | Success |=0A=
   |     |    |     |     CE to SmartBits     |              |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  4  | N  |  Z  |Redirect OSPF packet from|  RedirectOut | Success |=0A=
   |     |    |     |     SmartBits to CE     |              |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  5  | N  |  Z  |       Metadata in       |  RedirectOut | Success |=0A=
   |     |    |     |     redirect message    |  RedirectIn  |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  6  | N  |  Z  | OSPF neighbor discovery |  RedirectOut | Success |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  7  | N  |  Z  |     OSPF DD exchange    |  RedirectOut | Success |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |  IPv4NextHop |         |=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 22]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   |     |    |     |                         |              |         |=0A=
   |  8  | N  |  Z  |    OSPF LSA exchange    |  RedirectOut | Success |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |  IPv4NextHop |         |=0A=
   |     |    |     |                         |  IPv4UcastLPM|         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  9  | N  |  Z  |     Data Forwarding     |  RedirectOut | Success |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |  IPv4NextHop |         |=0A=
   |     |    |     |                         |  IPv4UcastLPM|         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  10 | Z  |  N  |  IPv4NextHopTable SET   |  IPv4NextHop | Success |=0A=
   |     |    |     |                         |              |         |=0A=
   |  11 | Z  |  N  |   IPv4PrefixTable SET   |  IPv4UcastLPM| Success |=0A=
   |     |    |     |                         |              |         |=0A=
   |  12 | Z  |  N  |Redirect OSPF packet from|  RedirectIn  | Success |=0A=
   |     |    |     | CE to other OSPF router |              |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  13 | Z  |  N  |Redirect OSPF packet from|  RedirectOut | Success |=0A=
   |     |    |     |other OSPF router to CE  |              |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  14 | Z  |  N  |       Metadata in       |  RedirectOut | Success |=0A=
   |     |    |     |     redirect message    |  RedirectIn  |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  15 | Z  |  N  |OSPF neighbor discovery  |  RedirectOut | Success |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  16 | Z  |  N  |    OSPF DD exchange     |  RedirectOut | Failure |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |  IPv4NextHop |         |=0A=
   |     |    |     |                         |              |         |=0A=
   |  17 | Z  |  N  |    OSPF LSA exchange    |  RedirectOut | Failure |=0A=
   |     |    |     |                         |  RedirectIn  |         |=0A=
   |     |    |     |                         |  IPv4NextHop |         |=0A=
   |     |    |     |                         |  IPv4UcastLPM|         |=0A=
   +-----+----+-----+-------------------------+--------------+---------+=0A=
=0A=
                 Figure 10: Packet Forwarding Test Results=0A=
=0A=
   Note on test #1 and #2:=0A=
=0A=
   A multicast route pointed to localhost was manually set before=0A=
   redirect channel could work normally.=0A=
=0A=
   Note on test #3 to #9:=0A=
=0A=
   During the tests, OSPF packets received from CE were found by=0A=
   Ethereal/Wireshark with checksum errors.  ZJSU's FE corrected the=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 23]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   checksum in FE so that the Smartbits would not drop the packets and=0A=
   the neighbor discovery can continue.  Such correcting action does not=0A=
   affect the test scenarios and the results.=0A=
=0A=
   Comment on Test #16 and #17:=0A=
=0A=
   The two test items failed.  Note that Test #7 and #8 were identical=0A=
   to the tests, only with CE and FE implementers were exchanged.=0A=
   Moreover, test #12 and #13 showed that the redirect channel worked=0A=
   well.  Therefore, it can be reasonably inferred that the problem=0A=
   caused the failure was from the implementations, rather than from the=0A=
   ForCES protocol itself or from misunderstanding of implementations on=0A=
   the protocol specification.  Although the failure made the OSPF=0A=
   interoperability test incomplete, it did not show interoperability=0A=
   problem.  More test work is needed to verify the OSPF=0A=
   interoperability.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 24]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
5.  Discussions=0A=
=0A=
5.1.  On Data Encapsulation Format=0A=
=0A=
   In the first day of the test, it was found that the LFB inter-=0A=
   operations about tables all failed.  The reason is found to be the=0A=
   different ForCES protocol data encapsulation method among different=0A=
   implementations.  The encapsulation issues are detailed as below:=0A=
=0A=
   Assuming that an LFB has two components, one is a struct with ID 1=0A=
   and the other an array with ID 2, further with two components of u32=0A=
   both inside, as below:=0A=
=0A=
   struct1: type struct, ID=3D1=0A=
           components are:=0A=
           a, type u32, ID=3D1=0A=
           b, type u32, ID=3D2=0A=
=0A=
   table1: type array, ID=3D2=0A=
           components for each row are (a struct of):=0A=
           x, type u32, ID=3D1=0A=
           y, type u32, ID=3D2=0A=
=0A=
   1.  On response of PATH-DATA format=0A=
=0A=
   When a CE sends a config/query ForCES protocol message to an FE from=0A=
   a different implementer, the CE probably receives response from the=0A=
   FE with different PATH-DATA encapsulation format.  For example, if a=0A=
   CE sends a query message with a path of 1 to a third party FE to=0A=
   manipulate struct 1 as defined above, the FE is probable to generate=0A=
   response with two different PATH-DATA encapsulation format: one is=0A=
   the value with FULL/SPARSE-DATA and the other is the value with many=0A=
   parallel PATH-DATA TLV and nested PATH-DATA TLV, as below:=0A=
=0A=
   format 1:=0A=
       OPER =3D GET-RESPONSE-TLV=0A=
           PATH-DATA-TLV:=0A=
               IDs=3D1=0A=
               FULLDATA-TLV containing valueof(a),valueof(b)=0A=
   format 2:=0A=
       OPER =3D GET-RESPONSE-TLV=0A=
           PATH-DATA-TLV:=0A=
               IDs=3D1=0A=
               PATH-DATA-TLV:=0A=
                   IDs=3D1=0A=
                   FULLDATA-TLV containing valueof(a)=0A=
               PATH-DATA-TLV:=0A=
                   IDs=3D2=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 25]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
                   FULLDATA-TLV containing valueof(b)=0A=
=0A=
   The interoperability testers witnessed that a ForCES element (CE or=0A=
   FE) sender is free to choose whatever data structure that IETF ForCES=0A=
   documents define and best suits the element, while a ForCES element=0A=
   (CE or FE) should be able to accept and process information (requests=0A=
   and responses) that use any legitimate structure defined by IETF=0A=
   ForCES documents.  While in the case a ForCES element is free to=0A=
   choose any legitimate data structure as a response, it is preferred=0A=
   the ForCES element responds in the same format that the request was=0A=
   made, as it is most probably the data structure is the request sender=0A=
   looks forward to receive.=0A=
=0A=
   2.  On operation to array=0A=
=0A=
   An array operation may also have several different data encapsulation=0A=
   formats.  For instance, if a CE sends a config message to table 1=0A=
   with a path of (2.1), which refers to component with ID=3D2, which is=0A=
   an array, and the second ID is the row, so row 1, it may be=0A=
   encapsulated with three formats as below:=0A=
=0A=
   format 1:=0A=
       OPER =3D SET-TLV=0A=
           PATH-DATA-TLV:=0A=
               IDs=3D2.1=0A=
               FULLDATA-TLV containing valueof(x),valueof(y)=0A=
   format 2:=0A=
       OPER =3D SET-TLV=0A=
           PATH-DATA-TLV:=0A=
               IDs=3D2.1=0A=
               PATH-DATA-TLV:=0A=
                   IDs=3D1=0A=
                   FULLDATA-TLV containing valueof(x)=0A=
               PATH-DATA-TLV=0A=
                   IDs=3D2=0A=
                   FULLDATA-TLV containing valueof(y)=0A=
=0A=
   Moreover, if CE is targeting the whole array, for example if the=0A=
   array is empty and CE wants to add the first row to the table, it=0A=
   could also adopt another format:=0A=
=0A=
   format 3:=0A=
       OPER =3D SET-TLV=0A=
           PATH-DATA-TLV:=0A=
               IDs=3D2=0A=
               FULLDATA-TLV containing rowindex=3D1,valueof(x),valueof(y)=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 26]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   The interoperability test experience shows that format 1 and format=0A=
   3, which take full advantage of multiple data elements description in=0A=
   one TLV of FULLDATA-TLV, get more efficiency, although format 2 can=0A=
   also get the same operating goal.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 27]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
6.  Contributors=0A=
=0A=
   Contributors who have made major contributions to the=0A=
   interoperability test are as below:=0A=
=0A=
      Hirofumi Yamazaki=0A=
      NTT Corporation=0A=
      Tokyo=0A=
      Japan=0A=
      Email: yamazaki.horofumi@lab.ntt.co.jp=0A=
=0A=
      Rong Jin=0A=
      Zhejiang Gongshang University=0A=
      Hangzhou=0A=
      P.R.China=0A=
      Email: jinrong@zjsu.edu.cn=0A=
=0A=
      Yuta Watanabe=0A=
      NTT Corporation=0A=
      Tokyo=0A=
      Japan=0A=
      Email: yuta.watanabe@ntt-at.co.jp=0A=
=0A=
      Xiaochun Wu=0A=
      Zhejiang Gongshang University=0A=
      Hangzhou=0A=
      P.R.China=0A=
      Email: spring-403@zjsu.edu.cn=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 28]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
7.  Acknowledgements=0A=
=0A=
   The authors thank the following test participants:=0A=
=0A=
      Chuanhuang Li, Hangzhou BAUD Networks=0A=
      Ligang Dong, Zhejiang Gongshang University=0A=
      Bin Zhuge, Zhejiang Gongshang University=0A=
      Jingjing Zhou, Zhejiang Gongshang University=0A=
      Liaoyuan Ke, Hangzhou BAUD Networks=0A=
      Kelei Jin, Hangzhou BAUD Networks=0A=
=0A=
   The authors also thank very much to Adrian Farrel and Joel Halpern=0A=
   for their important help in the document publication process.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 29]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
8.  IANA Considerations=0A=
=0A=
   This memo includes no request to IANA.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 30]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
9.  Security Considerations=0A=
=0A=
   Developers of ForCES FEs and CEs must take the security=0A=
   considerations of the ForCES Framework [RFC3746] and the ForCES=0A=
   Protocol [RFC5810] into account.  Also, as specified in the security=0A=
   considerations section of the SCTP-Based TML for the ForCES Protocol=0A=
   [RFC5811], the transport-level security has to be ensured by IPsec.=0A=
   Test results of TML with IPsec supported have been shown in=0A=
   Section 4.2 of the document.=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 31]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
10.  References=0A=
=0A=
10.1.  Normative References=0A=
=0A=
   [RFC5810]  Doria, A., Hadi Salim, J., Haas, R., Khosravi, H., Wang,=0A=
              W., Dong, L., Gopal, R., and J. Halpern, "Forwarding and=0A=
              Control Element Separation (ForCES) Protocol=0A=
              Specification", RFC 5810, March 2010.=0A=
=0A=
   [RFC5811]  Hadi Salim, J. and K. Ogawa, "SCTP-Based Transport Mapping=0A=
              Layer (TML) for the Forwarding and Control Element=0A=
              Separation (ForCES) Protocol", RFC 5811, March 2010.=0A=
=0A=
   [RFC5812]  Halpern, J. and J. Hadi Salim, "Forwarding and Control=0A=
              Element Separation (ForCES) Forwarding Element Model",=0A=
              RFC 5812, March 2010.=0A=
=0A=
   [RFC5813]  Haas, R., "Forwarding and Control Element Separation=0A=
              (ForCES) MIB", RFC 5813, March 2010.=0A=
=0A=
10.2.  Informative References=0A=
=0A=
   [Ethereal]=0A=
              "Ethereal, also named Wireshark, is a protocol analyzer.=0A=
              The specific Ethereal that was used is an updated=0A=
              Ethereal, by Fenggen Jia, that can analyze and decode the=0A=
              ForCES protocol messages", http://www.ietf.org/=0A=
              mail-archive/web/forces/current/msg03687.html .=0A=
=0A=
   [I-D.ietf-forces-ceha-00]=0A=
              Ogawa, K., Wang, W., Haleplidis, E., and J. Salim, "ForCES=0A=
              Intra-NE High Availability", draft-ietf-forces-ceha-00=0A=
              (work in  progress) [RFC Editor Note: This reference is=0A=
              intended to indicate a specific version of an Internet-=0A=
              Draft that was used during interop testing. Please Do NOT=0A=
              update this reference to a  more recent version of the=0A=
              draft or to an RFC. Please remove this note before=0A=
              publication] , October 2010.=0A=
=0A=
   [I-D.ietf-forces-lfb-lib-03]=0A=
              Wang, W., Haleplidis, E., Ogawa, K., Li, C., and J.=0A=
              Halpern, "ForCES Logical Function Block (LFB) Library",=0A=
              draft-ietf-forces-lfb-lib-03 (work in  progress) [RFC=0A=
              Editor Note: This reference is intended to indicate a=0A=
              specific version of an Internet-Draft that was used during=0A=
              interop testing. Please Do NOT update this reference to a=0A=
              more recent version of the draft or to an RFC. Please=0A=
              remove this note before publication] , December 2010.=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 32]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
   [RFC3654]  Khosravi, H. and T. Anderson, "Requirements for Separation=0A=
              of IP Control and Forwarding", RFC 3654, November 2003.=0A=
=0A=
   [RFC3746]  Yang, L., Dantu, R., Anderson, T., and R. Gopal,=0A=
              "Forwarding and Control Element Separation (ForCES)=0A=
              Framework", RFC 3746, April 2004.=0A=
=0A=
   [RFC6053]  Haleplidis, E., Ogawa, K., Wang, W., and J. Hadi Salim,=0A=
              "Implementation Report for Forwarding and Control Element=0A=
              Separation (ForCES)", RFC 6053, November 2010.=0A=
=0A=
   [Tcpdump]  "Tcpdump is a Linux protocol analyzer. The specific=0A=
              tcpdump that was used is a modified tcpdump, by Jamal Hadi=0A=
              Salim, that can analyze and decode the ForCES protocol=0A=
              messages", http://www.ietf.org/mail-archive/web/forces/=0A=
              current/msg03811.html .=0A=
=0A=
   [Teamviewer]=0A=
              "TeamViewer connects to any PC or server around the world=0A=
              within a few seconds.", http://www.teamviewer.com/ .=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 33]=0A=
=0C=0A=
Internet-Draft            ForCES Interop Report                 May 2013=0A=
=0A=
=0A=
Authors' Addresses=0A=
=0A=
   Weiming Wang=0A=
   Zhejiang Gongshang University=0A=
   18 Xuezheng Str., Xiasha University Town=0A=
   Hangzhou,   310018=0A=
   P.R.China=0A=
=0A=
   Phone: +86-571-28877721=0A=
   Email: wmwang@zjsu.edu.cn=0A=
=0A=
=0A=
   Kentaro Ogawa=0A=
   NTT Corporation=0A=
   Tokyo,=0A=
   Japan=0A=
=0A=
   Email: ogawa.kentaro@lab.ntt.co.jp=0A=
=0A=
=0A=
   Evangelos Haleplidis=0A=
   University of Patras=0A=
   Department of Electrical & Computer Engineering=0A=
   Patras,   26500=0A=
   Greece=0A=
=0A=
   Email: ehalep@ece.upatras.gr=0A=
=0A=
=0A=
   Ming Gao=0A=
   Hangzhou BAUD Networks=0A=
   408 Wen-San Road=0A=
   Hangzhou,   310012=0A=
   P.R.China=0A=
=0A=
   Email: gmyyqno1@zjsu.edu.cn=0A=
=0A=
=0A=
   Jamal Hadi Salim=0A=
   Mojatatu Networks=0A=
   Ottawa=0A=
   Canada=0A=
=0A=
   Email: hadi@mojatatu.com=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Wang, et al.            Expires November 23, 2013              [Page 34]=0A=
=0C=0A=

------=_NextPart_000_01D6_01CE5745.6E793440--

From sm@resistor.net  Wed May 22 15:49:17 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA6321F90EE for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 15:49:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.537
X-Spam-Level: 
X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IVrAb9dSTRhj for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 15:49:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44B7221F90DF for <ietf@ietf.org>; Wed, 22 May 2013 15:49:16 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4MMmwPt027023; Wed, 22 May 2013 15:49:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369262944; bh=OIDYznALgdS9cPKwnlItLbpOuVqxnkUIz6z80Qctxww=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=T0gWleiVHBWKzn9+7ZBtm8x9ZimXqB3nL4bl2wKSCqj7n3g3JJ/khm65HE84i0Mrh k4Dx2PnDkkNBlBpjTDej9GPa8myYzLLKK9GagvnWmQXXa+ZTDxtFipwghyqfyUDtLy co2TyH1cd6GBYUoJniHQWrvOsYP3AJlhDGbHTnFQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369262944; i=@resistor.net; bh=OIDYznALgdS9cPKwnlItLbpOuVqxnkUIz6z80Qctxww=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=kkzXNhT/hCOvFEJTEfGHnpzFXd9oIm+wCrqj+wsiwWpDaTD7qF03I3y4r/DB6ZlhH i0Tp82mnrIKoHKsRSYy6Ja7NAl07gkNXJkEIrVnrTSmAQyizsBCtm5G7FNCGnTNXcd byWE2RY9ehM/tXl85+cbVs/W9wxBU2i5rmOFHNDY=
Message-Id: <6.2.5.6.2.20130522123025.0b3efed0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 22 May 2013 13:57:10 -0700
To: "Moriarty, Kathleen" <kathleen.moriarty@emc.com>, John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: RE: Deployment of standards compliant nameservers
In-Reply-To: <F5063677821E3B4F81ACFB7905573F24DC22DEFA@MX15A.corp.emc.co m>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com> <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com> <F5063677821E3B4F81ACFB7905573F24DC22DEFA@MX15A.corp.emc.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: Wed, 22 May 2013 22:49:18 -0000

At 05:56 22-05-2013, Moriarty, Kathleen wrote:
>providers.  While tying this to contracts seems like a good idea, 
>that is out of our hands at the IETF.  If we went down the path of 
>enforcement through contracts, I wouldn't view this as picking 
>fights, but rather a proactive service to 'help' customers.  Having
>  said that, I think if we can improve the applications that 
> generate their DNS files, it would be more effective long 
> term.  While some teams are technical enough to validate their own 
> DNS, others prefer more full service applications.
>
>Maybe a review of existing applications would be helpful for the 
>community?  I just see the following on Wikipedia:
>http://en.wikipedia.org/wiki/Comparison_of_DNS_server_software
>and
>http://en.wikipedia.org/wiki/DNS_management_software
>
>How about adding a column for compliance to RFCs?  Or a description 
>that makes people

RFC 1035 is updated by 24 RFCs.  There are a few errata which has 
been filed.  The topic says "standards complaint".  Which standard(s) 
does that refer to?  I read "compliance to RFCs", which RFCs does the 
implementation have to comply with?

It has been mentioned [1] on this mailing list that:

   "But there was no energy to get the work done and the drafts languished
    for months without any changes.  It still seems a worthwhile project,
    but there is no evidence that we have a population interested enough
    to do the work."

If the IETF discusses about contracts the discussion will evolve into 
turf wars (an acrimonious dispute between rival groups over territory 
or a particular sphere of influence).  The interesting point in the 
message (quoted above) is about providing information so that people 
can assess what's good or bad.  In my opinion it's doable (note that 
I am leaving out a few minor details :-)).

At 07:00 22-05-2013, John C Klensin wrote:
>I wouldn't suggest trying to mandate anything top-down.  If
>nothing else, ICANN's track record for being able to enforce its
>mandates is very poor (and that is arguably a good thing).  On

:-)

>the other, we talk a lot about reputations and the advantages of
>end sites being able to base policies on them.   If whatever the
>actual restrictions that, according to Stephane, forbid TLDs
>from imposing "we require you to have a competent nameserver and
>will test" were removed then, especially with the coming huge
>increase in TLDs, it would make it possible for registries to
>compete on the degree to which they wanted to offer assurances
>of quality DNS servers and services in subsidiary zones.

Yes.  I gather that domain name are registered to advertise services 
and that these services rely on working nameservers.

I was reading the following [2] (the reader is cautioned against 
drawing hasty conclusions):

   "AFNIC (The sole registrar of .fr domains) does not follow the 
ICANN policies
    for name server queries."

Here's a gem:

   "Other registrars are fully able to query our name servers on TCP port 43
   (the ICANN required port)."

Nameservers hosting Icelandic domains (.IS domains) must comply with 
requirements [3].

More reading [4]:

   "The .DE registry has certain requirements for nameservers that 
can be applied
    to .DE domains. Some of those requirements are that the 
nameserver IP addresses
    must be in separate class C networks, and that the nameserver 
must provide SOA."

For .NL domains, the nameservers must comply with the registry 
requirements [5].

People put more effort and money in trademarking strings than making 
the strings work.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf/current/msg79409.html
2. https://my.bluehost.com/cgi/help/536
3. http://www.isnic.is/en/host/req
4. http://www.namecheap.com/support/knowledgebase/article.aspx/294/
5. http://www.opensrs.com/docs/opensrsrwi/nl_dns_requirements.htm 


From marka@isc.org  Wed May 22 16:42:29 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52C6D11E814E for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 16:42:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7SM0P+5AjsiC for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 16:42:25 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 9394211E8161 for <ietf@ietf.org>; Wed, 22 May 2013 16:42:24 -0700 (PDT)
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id CBD27C947B; Wed, 22 May 2013 23:42:13 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369266142; bh=UpiqtARxmzAyIH4ujknP2e//GGpouPIBscw8BlZpHKI=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=rKIBYM54xtZuJBdN+ktOEPhdxnkrxejpvlfRFPELL09tHcQYk+wSfhdQAKVXfKPAm G2/g9Z+eVMyNFZQWU8SkKw7o6FliB29Pe1VOSFvO7UEmu1xB87PaTGyB5LcphuPwFe kNGgrKFh8VLMtzjNUYP05X8l+V5r5UVaxpctgriw=
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS; Wed, 22 May 2013 23:42:13 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 1B35A216C40; Wed, 22 May 2013 23:42:13 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id D8883349B78F; Thu, 23 May 2013 09:42:09 +1000 (EST)
To: SM <sm@resistor.net>
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com> <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com> <F5063677821E3B4F81ACFB7905573F24DC22DEFA@MX15A.corp.emc.com> <6.2.5.6.2.20130522123025.0b3efed0@resistor.net>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Wed, 22 May 2013 13:57:10 -0700." <6.2.5.6.2.20130522123025.0b3efed0@resistor.net>
Date: Thu, 23 May 2013 09:42:09 +1000
Message-Id: <20130522234209.D8883349B78F@drugs.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 23:42:29 -0000

In message <6.2.5.6.2.20130522123025.0b3efed0@resistor.net>, SM writes:
> At 05:56 22-05-2013, Moriarty, Kathleen wrote:
> >providers.  While tying this to contracts seems like a good idea, 
> >that is out of our hands at the IETF.  If we went down the path of 
> >enforcement through contracts, I wouldn't view this as picking 
> >fights, but rather a proactive service to 'help' customers.  Having
> >  said that, I think if we can improve the applications that 
> > generate their DNS files, it would be more effective long 
> > term.  While some teams are technical enough to validate their own 
> > DNS, others prefer more full service applications.
> >
> >Maybe a review of existing applications would be helpful for the 
> >community?  I just see the following on Wikipedia:
> >http://en.wikipedia.org/wiki/Comparison_of_DNS_server_software
> >and
> >http://en.wikipedia.org/wiki/DNS_management_software
> >
> >How about adding a column for compliance to RFCs?  Or a description 
> >that makes people
> 
> RFC 1035 is updated by 24 RFCs.  There are a few errata which has 
> been filed.  The topic says "standards complaint".  Which standard(s) 
> does that refer to?  I read "compliance to RFCs", which RFCs does the 
> implementation have to comply with?
 
RFC 1034 and RFC 1035 I've tried to capture the reason why I started
this thread in:
http://tools.ietf.org/html/draft-andrews-dns-no-response-issue-01

Basically nameservers are supposed to reply to queries directed at
them.  RFC 1034 and RFC 1035 have enough error codes that you
should be able to reply to every query sent to them.   You don't
have to return the data.  You don't even have to understand the
query.  You do have to respond.

So if the message is 12 octets or bigger and the QR bit is set to
1 you should be able to respond.  RFC 1034 and RFC 1035 have a
response code for *every* possible message you receive.

> It has been mentioned [1] on this mailing list that:
> 
>    "But there was no energy to get the work done and the drafts languished
>     for months without any changes.  It still seems a worthwhile project,
>     but there is no evidence that we have a population interested enough
>     to do the work."
> 
> If the IETF discusses about contracts the discussion will evolve into 
> turf wars (an acrimonious dispute between rival groups over territory 
> or a particular sphere of influence).  The interesting point in the 
> message (quoted above) is about providing information so that people 
> can assess what's good or bad.  In my opinion it's doable (note that 
> I am leaving out a few minor details :-)).
> 
> At 07:00 22-05-2013, John C Klensin wrote:
> >I wouldn't suggest trying to mandate anything top-down.  If
> >nothing else, ICANN's track record for being able to enforce its
> >mandates is very poor (and that is arguably a good thing).  On
> 
> :-)
> 
> >the other, we talk a lot about reputations and the advantages of
> >end sites being able to base policies on them.   If whatever the
> >actual restrictions that, according to Stephane, forbid TLDs
> >from imposing "we require you to have a competent nameserver and
> >will test" were removed then, especially with the coming huge
> >increase in TLDs, it would make it possible for registries to
> >compete on the degree to which they wanted to offer assurances
> >of quality DNS servers and services in subsidiary zones.
> 
> Yes.  I gather that domain name are registered to advertise services 
> and that these services rely on working nameservers.
> 
> I was reading the following [2] (the reader is cautioned against 
> drawing hasty conclusions):
> 
>    "AFNIC (The sole registrar of .fr domains) does not follow the 
> ICANN policies
>     for name server queries."
> 
> Here's a gem:
> 
>    "Other registrars are fully able to query our name servers on TCP port 43
>    (the ICANN required port)."
> 
> Nameservers hosting Icelandic domains (.IS domains) must comply with 
> requirements [3].
> 
> More reading [4]:
> 
>    "The .DE registry has certain requirements for nameservers that 
> can be applied
>     to .DE domains. Some of those requirements are that the 
> nameserver IP addresses
>     must be in separate class C networks, and that the nameserver 
> must provide SOA."
> 
> For .NL domains, the nameservers must comply with the registry 
> requirements [5].
> 
> People put more effort and money in trademarking strings than making 
> the strings work.
> 
> Regards,
> -sm
> 
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg79409.html
> 2. https://my.bluehost.com/cgi/help/536
> 3. http://www.isnic.is/en/host/req
> 4. http://www.namecheap.com/support/knowledgebase/article.aspx/294/
> 5. http://www.opensrs.com/docs/opensrsrwi/nl_dns_requirements.htm 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From worley@shell01.TheWorld.com  Wed May 22 19:04:12 2013
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 E113E11E815B for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 19:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bj2-eAV2lEks for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 19:04:06 -0700 (PDT)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE3911E812A for <ietf@ietf.org>; Wed, 22 May 2013 19:04:02 -0700 (PDT)
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 r4N23sY7006196; Wed, 22 May 2013 22:03:56 -0400
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 r4N23sfT5287223; Wed, 22 May 2013 22:03:54 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r4N23sFt5238253; Wed, 22 May 2013 22:03:54 -0400 (EDT)
Date: Wed, 22 May 2013 22:03:54 -0400 (EDT)
Message-Id: <201305230203.r4N23sFt5238253@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: John C Klensin <john-ietf@jck.com>
In-reply-to: <CFEC40E9985AA5EE5071A4A7@JcK-HP8200.jck.com> (john-ietf@jck.com)
Subject: Re: Proposed Standards and Expert Review (was: Re: Last Call <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard))
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <B1F5E27A-4079-403C-8FFF-317C83FAFFF7@hopcount.ca> <m24ndwgxwo.wl%randy@psg.com> <8E31C837E8AF0E8E70DD2538@JcK-HP8200.jck.com> <BE7F48DE-CE92-4A92-9EB2-F72E9DEED8D9@ogud.com> <CFEC40E9985AA5EE5071A4A7@JcK-HP8200.jck.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: Thu, 23 May 2013 02:04:12 -0000

> From: John C Klensin <john-ietf@jck.com>
> 
> My problem here, which I hope was clear from
> the note from which you quoted, is that a request/document in
> the second category was proposed for Standards Track and then
> that comments that would be entirely appropriate for a Last Call
> on a Standards Track document were essentially rejected on the
> grounds that they would require changes to already-registered
> RRTYPEs.

This seems to be the only truly controversial point, and it is very
important.  The IETF does not promote something to a standard just
because someone (or even lots of people) are already doing it.

It is, however, perfectly acceptable to document it, and even to
document that some other group has anointed it as a standard within
*their* practice.

Dale

From worley@shell01.TheWorld.com  Wed May 22 19:04:12 2013
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 65AD811E812A for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 19:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7KXNUWQ0g-i for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 19:04:06 -0700 (PDT)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 6F93C11E812C for <ietf@ietf.org>; Wed, 22 May 2013 19:04:02 -0700 (PDT)
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 r4N23PZs012944; Wed, 22 May 2013 22:03:27 -0400
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 r4N23Pl35266327; Wed, 22 May 2013 22:03:25 -0400 (EDT)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r4N23Ov05285419; Wed, 22 May 2013 22:03:24 -0400 (EDT)
Date: Wed, 22 May 2013 22:03:24 -0400 (EDT)
Message-Id: <201305230203.r4N23Ov05285419@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Keith Moore <moore@network-heretics.com>
In-reply-to: <519B8241.501@network-heretics.com> (moore@network-heretics.com)
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.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: Thu, 23 May 2013 02:04:12 -0000

> From: Keith Moore <moore@network-heretics.com>
> 
> On 05/21/2013 10:04 AM, Joe Abley wrote:
> 
> > With respect, *my* question as the author of this document is
> > simply whether the specification provided is unambiguous and
> > sufficient. It was my understanding that this was the question
> > before the community in this last call.
> 
> The criteria for Proposed Standard are quite a bit higher than that.   
> See RFC 2026 section 4.1.1.

Coming into this from the outside, the issues are interesting.

I originally thought RRTYPEs are scarce, since all the ones I was
aware of are less than 256.  But it turns out that RRTYPEs are 16 bit
integers, and we've only consumed about 110 of them in ~25 years; we
have about 15,000 years' supply of them.  So they can be handed out
rather generously.

There actually is a standard for allocating RRTYPEs, which is RFC 6195
(section 3.1).  RRTYPEs are to be handed out rather freely.

OTOH, the standards for Proposed Standard are stricter.

In regard to the question of whether to use one RRTYPE or two, it
seems that the question is whether, in practice, it is common to want
to query for both EUI-48 and EUI-64 for the same domain name at the
same time.

In regard to *how* to subtype a single RRTYPE, the resource records
themselves contain a "DATA length" field (RDLENGTH, see RFC 1035
section 3.2.1), so if we used only one RRTYPE, the RDLENGTH field
would differentiate EUI-48 from EUI-64.

There are 768 RFCs that have INFORMATIONAL status and contain the word
"MUST" -- and that is over 10% of the total number of RFCs published
to date.  So it looks like RFC 2119 terminology is commonly used in
informational RFCs.  Personally, it seems like a good idea.  If you
want to notify the world of a privately-developed protocol, you want
to be able to say MUST and SHOULD; labeling it as INFORMATIONAL makes
clear that the IETF hasn't endorsed the protocol.

Dale

From d3e3e3@gmail.com  Wed May 22 19:44:31 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A289A21F8F27 for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 19:44:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRPmaNf9V-lE for <ietf@ietfa.amsl.com>; Wed, 22 May 2013 19:44:31 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 128E121F8F24 for <ietf@ietf.org>; Wed, 22 May 2013 19:44:30 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id eh20so3352648obb.32 for <ietf@ietf.org>; Wed, 22 May 2013 19:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1pxdtoxz/eZxKFJUElzcIVqDdUjGdw+GTjgE5V+XVC0=; b=gquLmSa3XJbn9eIbiOVYDhD2EMfd0Ic47kjIV+M0SemPRp1TNr3MdWIfVAU7STk9yt HafMfDJYIgB7dmmmUGwkMKtIMTmnrybujkPs7Rd1MVyzcq9+Yc2a7cUzCaFPwDfK1QFk baJN2pOfgUluUIqvse2LzdpYfQ+0vAzdOhSIAzyKgMtoaufOYvY1bVZm7UqI+kHfGfGh jwS/K5chDRjN/+BTnxX9Sc0BW0tjvVtxnBZ9IXko9Mzkj6MeQhUv6Lcla6y4LosXBLGq bqFmtd41UTIXFAQjLhRKgeksmc0P22VCYhqXuaqYaZ6p/fAHw+DaTTQ5SUcvgFJ80Kxf R4cA==
X-Received: by 10.60.42.140 with SMTP id o12mr7157288oel.60.1369277070241; Wed, 22 May 2013 19:44:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.162.233 with HTTP; Wed, 22 May 2013 19:44:10 -0700 (PDT)
In-Reply-To: <201305230203.r4N23Ov05285419@shell01.TheWorld.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <519A82B9.7090305@gmail.com> <519B785E.7060208@network-heretics.com> <BB0046EF-3C7F-466F-8CA9-9A5C237AD599@hopcount.ca> <519B8241.501@network-heretics.com> <201305230203.r4N23Ov05285419@shell01.TheWorld.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 22 May 2013 22:44:10 -0400
Message-ID: <CAF4+nEGLv02QT2oRJPx=EMXiOfXCo4w+mWQch_+3WajPpcJBRA@mail.gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 02:44:31 -0000

On Wed, May 22, 2013 at 10:03 PM, Dale R. Worley <worley@ariadne.com> wrote:
>...
>
> Coming into this from the outside, the issues are interesting.
>
> I originally thought RRTYPEs are scarce, since all the ones I was
> aware of are less than 256.  But it turns out that RRTYPEs are 16 bit
> integers, and we've only consumed about 110 of them in ~25 years; we
> have about 15,000 years' supply of them.  So they can be handed out
> rather generously.
>
> There actually is a standard for allocating RRTYPEs, which is RFC 6195
> (section 3.1).  RRTYPEs are to be handed out rather freely.

Obsoleted by RFC 6895 but not too much change.

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

From marka@isc.org  Wed May 22 19:50:04 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A73121F8F2C; Wed, 22 May 2013 19:50:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.129,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TK5iPi0PX07k; Wed, 22 May 2013 19:50:03 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id F033221F8EDF; Wed, 22 May 2013 19:50:02 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id DDF955F9861; Thu, 23 May 2013 02:49:51 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369277402; bh=0NFNZe7I0KaQilr/nm2tDH1LGOGiR8aWdTHXBZqrwSg=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=YFSwV6VN4KRDqYGskOAE3OB8gkz5tEBFGhWZ1TXlLHvVvPfbSB7wbQEfXkWtf6Q1L 7vCphNEuWzpr3eboUseYm5Rn8jvA36E1qcY9X/qTaxD2lzsJJkCUezhcUU8jBN1bZY 8yNUiJIbiiCkZCb6scuaPMLFpIzF3nrwOd4cQHwo=
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A5AA7216C43; Thu, 23 May 2013 02:49:49 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id B64B3349C99A; Thu, 23 May 2013 12:49:45 +1000 (EST)
To: John C Klensin <john-ietf@jck.com>
From: Mark Andrews <marka@isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com> <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com> <9506594E9E3CB989AFBC02A8@JcK-HP8200.jck.com>
Subject: Re: Deployment of standards compliant nameservers
In-reply-to: Your message of "Wed, 22 May 2013 10:00:58 -0400." <9506594E9E3CB989AFBC02A8@JcK-HP8200.jck.com>
Date: Thu, 23 May 2013 12:49:45 +1000
Message-Id: <20130523024945.B64B3349C99A@drugs.dv.isc.org>
Cc: "<iesg@ietf.org>" <iesg@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: Thu, 23 May 2013 02:50:04 -0000

In message <9506594E9E3CB989AFBC02A8@JcK-HP8200.jck.com>, John C Klensin writes:
> 
> 
> --On Wednesday, May 22, 2013 12:29 +0000 Yoav Nir
> <ynir@checkpoint.com> wrote:
> 
> >> Occasional fantasies about IETF enforcement power and the
> >> Protocol Police notwithstanding, it seems to me that, if one
> >> wanted to require standards-conforming nameservers, the most
> >> (and maybe only) effective way to do that would be
> >> requirements in the contractual agreements between TLD
> >> registries and their registrants.  Recursively applying
> >> requirements down the tree is not a new idea; RFC 1591 uses
> >> that language more than once.
> > 
> > We should be careful about requiring things like this (for
> > whatever value of "we"). Recursively applying requirements
> > means that "we" are requiring service providers (in this case
> > registries) to pick fights with their customers. So instead of
> > having an IETF protocol police, "we" expect service providers
> > to act as local sheriffs.
> >...
> > Seems like a tough sell to me.
> 
> Actually, I was thinking about something a little different (and
> should have been more explicit).  
> 
> I wouldn't suggest trying to mandate anything top-down.  If
> nothing else, ICANN's track record for being able to enforce its
> mandates is very poor (and that is arguably a good thing).

Asking people to run a nameserver which "responds" to queries isn't
unreasonable by any stretch of the imagination regardless of their
economic circumstances.  The nameservers that people used in the
1980's did this correctly.  The default nameservers on general
purpose OS as shipped for the last 2 decades have done this correctly.

This includes free and commercial operating systems.

The one exception I am aware of is a Windows release where the server
responds to the first EDNS query but not to subsequent EDNS queries.
This only becomes a issue when the first response is lost or multiple
recursive servers share the same IP address.  Microsoft has fixed
this issue in later releases.  I am not sure if there is a service
pack that fixes this.

Requiring vendors to supply fixes to code that was never "fit for
purpose" regardless of its age is also reasonable.

> On
> the other, we talk a lot about reputations and the advantages of
> end sites being able to base policies on them.   If whatever the
> actual restrictions that, according to Stephane, forbid TLDs
> from imposing "we require you to have a competent nameserver and
> will test" were removed then, especially with the coming huge
> increase in TLDs, it would make it possible for registries to
> compete on the degree to which they wanted to offer assurances
> of quality DNS servers and services in subsidiary zones.
> Would-be registrants who didn't want to play would have the
> option of finding TLDs who did not have those restrictions.
> That would create a new opportunity for enhanced competition and
> differentiation among TLDs (which ICANN presumably favors along
> with favoring security and stability) and would create a basis
> for some DNS server certification activities (and even a
> business model for them).
>
> No mandate from the top, just elimination of whatever
> restrictions now prevent registries from insisting on quality
> operations in registrants if they wanted to.
> 
> It wouldn't get us to "everyone has to run a conforming server"
> --which I consider impossible as long as producing
> non-conforming servers is legal with governments enforcing the
> rules if servers don't conform (and I really don't think  we
> want to go there)-- but it would at least give a resolver an
> indication of where conforming ones were guarantees and what
> responses or non-responses they couldn't trust.
> 
>     john
> 
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mansaxel@besserwisser.org  Thu May 23 00:41:49 2013
Return-Path: <mansaxel@besserwisser.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 1ED8121F96D8; Thu, 23 May 2013 00:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lNj7mukpvxPr; Thu, 23 May 2013 00:41:48 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id 8D2CD21F96D6; Thu, 23 May 2013 00:41:47 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 32AA89EF6; Thu, 23 May 2013 09:41:45 +0200 (CEST)
Date: Thu, 23 May 2013 09:41:45 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Deployment of standards compliant nameservers
Message-ID: <20130523074144.GM31267@besserwisser.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com> <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="P9KQiUGMzYCFwWCN"
Content-Disposition: inline
In-Reply-To: <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: John C Klensin <john-ietf@jck.com>, "<iesg@ietf.org>" <iesg@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: Thu, 23 May 2013 07:41:49 -0000

--P9KQiUGMzYCFwWCN
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Deployment of standards compliant nameservers Date: Wed, May 2=
2, 2013 at 12:29:58PM +0000 Quoting Yoav Nir (ynir@checkpoint.com):
=20
> Seems like a tough sell to me.

Not worse than BCP38 ;-)=20

OTOH, I have _personally_ done this. I introduced and enforced and got set
into policy that name servers hosting domains under .SE should actually
have the domain set up and working before we (I was at the registry then,
performing transfers between DNS hosting providers and similar work,
all very manual and pre-web 1.0) transfered the domain delegation to
the new set of servers.

I got yelled at quite a lot, but a lot of domain name holders
approved. Mostly the anger was from lazy hosting companies that didn't
mind having their customers with flapping delegations for a week.

It can be done, it won't be popular, but the side effects are good. Mostly.=
=20

Due to <some pressure from someone> this policy has been discontinued. I
am not responsible anymore.

OTTH, I think Marks proposal has some merit. I have a pretty good idea=20
where this comes from, but I think that we -- mostly -- have the tools=20
in 1591, and other documents.=20

OTFH, this won't help until the people shelling out money and other
resources to build and run infrastructure start paying attention.
The grunt work to be made here is mostly about making certain people
know that they should request compliance with the actual standards and
not a subset conveniently fitting the preselected candidate.

It is unclear to me whether people who are not reading the present set
of standards will start reading and paying attention this time around.


--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
I'm GLAD I remembered to XEROX all my UNDERSHIRTS!!

--P9KQiUGMzYCFwWCN
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlGdyDgACgkQ02/pMZDM1cUlNgCfZT72+lFBQgP3t/5NQdZemjn/
EUwAn32qdPuCvow2W1C+Ww7fAHvrauhS
=JTWs
-----END PGP SIGNATURE-----

--P9KQiUGMzYCFwWCN--

From john-ietf@jck.com  Thu May 23 03:37:36 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50EB021F9662; Thu, 23 May 2013 03:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.581
X-Spam-Level: 
X-Spam-Status: No, score=-103.581 tagged_above=-999 required=5 tests=[AWL=1.018, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RTqZnQOFzFOd; Thu, 23 May 2013 03:37:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2A921F8E93; Thu, 23 May 2013 03:37:24 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UfStQ-000E6W-NN; Thu, 23 May 2013 06:37:08 -0400
Date: Thu, 23 May 2013 06:37:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: Deployment of standards compliant nameservers
Message-ID: <EFC8BED02034C667624E85E5@JcK-HP8200.jck.com>
In-Reply-To: <20130523024945.B64B3349C99A@drugs.dv.isc.org>
References: <20130521002639.E75D9348D265@drugs.dv.isc.org> <20130521090727.GB17630@nic.fr> <E9FF169B8AB44429ECA7D7F5@JcK-HP8200.jck.com> <F6477BC2-8B81-435C-B79F-F0FF73A2DB45@checkpoint.com> <9506594E9E3CB989AFBC02A8@JcK-HP8200.jck.com> <20130523024945.B64B3349C99A@drugs.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: "<iesg@ietf.org>" <iesg@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: Thu, 23 May 2013 10:37:36 -0000

--On Thursday, May 23, 2013 12:49 +1000 Mark Andrews
<marka@isc.org> wrote:

> Asking people to run a nameserver which "responds" to queries
> isn't unreasonable by any stretch of the imagination
> regardless of their economic circumstances.  The nameservers
> that people used in the 1980's did this correctly.  The
> default nameservers on general purpose OS as shipped for the
> last 2 decades have done this correctly.
>...
> Requiring vendors to supply fixes to code that was never "fit
> for purpose" regardless of its age is also reasonable.

Mark,

Once more and then I'm dropping out of this discussion.  You may
think "requiring... is reasonable".  I might even agree with you
and note that such a requirement, if applied to software across
the board and especially if "promptly" were inserted somewhere
in the sentence, would cure many of the world's ills, not just
this problem with the DNS.   As a examples that causes even more
visible damage than DNS non-responses, I'd be delighted if every
system and web site that rejects email local-parts with "+" in
them as invalid were "required" to fix those bugs or if every
spammer were "required" to stop doing anything that violates the
letter or spirit of applicable protocols or laws.

Where I have a problem is with "required", especially having the
IETF require it.  If you like, write up a draft for a BCP that
would specify eternal damnation to any vendor who gets this
wrong and doesn't release a patch within three months.  I
suspect that most of the objections to approval of such a
document would be about how it would make us look silly, not
about whether the vendors deserve it.   The difficulties are
that we have no enforcement power at all and that the very
nature of an open Internet and voluntary standards implies that
people can ignore the latter.   =20

I wish every vendor were better behaved but the only steps I can
see that would actually make progress on the problem you are
trying to solve are:

* Removing obstacles to requirements and enforcement where the
latter is really possible.  If there is an ICANN barrier to TLDs
requiring working nameservers for names that are delegated,
interpreting "working" as conforming, and enforcing that
requirement, removing it would probably be a good idea, as would
an SSAC statement encouraging the practice in the name of a
stable and secure Internet.  (As you probably know, there was a
time when the "show that you have working nameservers first"
rule that M=C3=A5ns mentioned for .SE was pretty much the norm =
for
TLDs.)  But that isn't an IETF problem and this isn't the right
place to discuss it unless you think our approving a document
that says "1035 says don't do this, you really, _really_
shouldn't do this" would accomplish anything other than raising
the stress level between ICANN and the IETF.

* Educational methods to raise vendor awareness of the problem
and that point out that it shouldn't be hard to fix.  If you
think flaming a few of them by name or other methods of
education would be appropriate, go to it.  As others have sort
of suggested, a few "these packages are broken and their vendors
are clueless and unresponsive" web pages might be interesting --
just see how well ones with similar intent have worked in
stopping spam. Just don't bother doing it here: I not seen a
single posting that disagrees with you about how the DNS is
supposed to work.   Few, if any, of the offending vendors are
reading this list and those that are and haven't already rushed
out to fix their products presumably don't care.

* In principle, if any ICANN barriers to voluntary TLD
enforcement were removed, large-deployment DNS software vendors
could follow the model that some web browser applications used
with IDNA: figure out what policies are appropriate for a good
user or operations experience and then arrange to deliver a
really bad experience to those who don't voluntarily comply.=20

* Governments do have the ability to make rules and enforce
them.  I personally believe that legislating conformance to a
government's understanding of Internet protocols would work out
badly but, if you disagree, try it locally and let us know how
it works out.  I look forward to reading that Australia has
incarcerated (or, better yet, flogged) a vendor of DNS software
that doesn't conformed to your norms or someone who was
irresponsible enough to run such software.

But, otherwise, hyperbole about "require" is just that:
hyperbole.

   best,
    john



What is don't see is=20



From bob.hinden@gmail.com  Thu May 23 08:54:58 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C11C21F8EBC; Thu, 23 May 2013 08:54:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBaPpNCQh+MN; Thu, 23 May 2013 08:54:51 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A65621F9842; Thu, 23 May 2013 08:54:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: The IAOC <bob.hinden@gmail.com>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF Meeting in South America
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
Date: Thu, 23 May 2013 08:54:12 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 15:54:59 -0000

As you may know the IAOC has been investigating the feasibility of having a=
n IETF
meeting in South America.  There was a site visit to South America last Feb=
ruary. =

We have found two venues that we believe will support a successful IETF mee=
ting
and we would like to get feedback from the community.

The venues are in Buenos Aires.  They meet our requirements for the meeting
space, networking, nearby restaurants and bars, hotel room rates in the mid=
 $200
dollar range, nearby alternate hotels at a broad range of prices, nice area=
 in the
city, safe, direct international flights, and accessible visas.  The IAOC t=
hinks we
could have a successful IETF meeting in Buenos Aires and that attendees wou=
ld
like the venues.

There has been a consistent level of IETF participation from South and Cent=
ral
America, and it has been growing since IETF82.  The data on this is posted =
at =


   http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.  =


The current meeting regional rotation (announced at IETF79) allows for an
occasional IETF meeting outside of our main regions (Europe, North America,
Asia/Pacific).  =


IETF standards are made more valuable the more relevant they are and the mo=
re
uptake they get.  IETF standards are also made more robust when all perspec=
tives
are represented during their development.  Encouraging growing participation
will help strengthen the Internet, further encourage participation from tho=
se areas
that will see the most growth in the coming years, and will help advance th=
e IETF
in political and international circles which is becoming more of an imperat=
ive.

We have asked the IESG for their feedback and they are supportive of a meet=
ing in
South America if there is community support and active participants attend.

Things to consider are that it will be a long trip for the majority of IETF=
ers and the
air fares are more expensive (about 10% to 20% higher than average), though
restaurants are less expensive.  This would be a case where most IETFers wo=
uld
bear more travel pain and expense.  =


The IAOC would like to understand if the IETF community thinks that the IETF
should have a meeting in the next few years in Buenos Aires.  The IAOC would
also like to get feedback on how we can ensure the meeting is as successful=
 as
possible and on ways to grow participation in the region.

We have set up a survey at  https://www.surveymonkey.com/s/NWYLQCD  where
you can indicate your likelihood of attending, and we encourage you to send=
 your
general feedback to the IETF list <ietf@ietf.org>.

Thanks,
Bob Hinden
IAOC Chair

From agmalis@gmail.com  Thu May 23 10:24:29 2013
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 B510E21F8FE9 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 10:24:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fd16GErDepzL for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 10:24:18 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F003921F96C6 for <ietf@ietf.org>; Thu, 23 May 2013 10:13:25 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id hn14so4711283wib.8 for <ietf@ietf.org>; Thu, 23 May 2013 10:13:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Stsp4LeTnS4T7i5uL7MtNErpIJ+4rgNR7wmErB78u40=; b=rkZrp0vR4B5r9vzXw5GliXOL2PMoBVwgLlYaPNPHMP124lWRlTuvq4/4fUx+FKC9A6 YnmNqVlKwe1lgxPX6WnvJQufrFXFyX0IDK2FGxtQLrrbcJMOhxyOxgaXi02mNEKStOhD Log+CoOVZpbp4Boorb8nvhUE3bJd1GWwgyc6hPsFteSuC5R3nuP5oj32UM2Z8rlk1Y+m ZjPyka7EkPV+KFMjCni25M/usWTgLc2HOjVJqstW2o9A6kA2Qv28j8h90yvFGLXoYQxB y59+N96UU0KEgjRjuoLhm8ZQuwYji6eSKtGIX/lOrhIKjV5ro3Fh4ZZWySYcNhEuO3RJ Qm8A==
X-Received: by 10.180.74.172 with SMTP id u12mr6755364wiv.0.1369329204816; Thu, 23 May 2013 10:13:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.83.5 with HTTP; Thu, 23 May 2013 10:13:04 -0700 (PDT)
In-Reply-To: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 23 May 2013 13:13:04 -0400
Message-ID: <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>
Subject: Re: IETF Meeting in South America
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d04389001d5849104dd65cca7
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 17:24:30 -0000

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

I think this is an excellent idea. The Adelaide meeting worked out fine,
and this would be a lot closer for a great many participants than that
meeting was.

Cheers,
Andy



On Thu, May 23, 2013 at 11:54 AM, The IAOC <bob.hinden@gmail.com> wrote:

> As you may know the IAOC has been investigating the feasibility of having
> an IETF
> meeting in South America.  There was a site visit to South America last
> February.
> We have found two venues that we believe will support a successful IETF
> meeting
> and we would like to get feedback from the community.
>
> The venues are in Buenos Aires.  They meet our requirements for the meeting
> space, networking, nearby restaurants and bars, hotel room rates in the
> mid $200
> dollar range, nearby alternate hotels at a broad range of prices, nice
> area in the
> city, safe, direct international flights, and accessible visas.  The IAOC
> thinks we
> could have a successful IETF meeting in Buenos Aires and that attendees
> would
> like the venues.
>
> There has been a consistent level of IETF participation from South and
> Central
> America, and it has been growing since IETF82.  The data on this is posted
> at
>
>    http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.
>
> The current meeting regional rotation (announced at IETF79) allows for an
> occasional IETF meeting outside of our main regions (Europe, North America,
> Asia/Pacific).
>
> IETF standards are made more valuable the more relevant they are and the
> more
> uptake they get.  IETF standards are also made more robust when all
> perspectives
> are represented during their development.  Encouraging growing
> participation
> will help strengthen the Internet, further encourage participation from
> those areas
> that will see the most growth in the coming years, and will help advance
> the IETF
> in political and international circles which is becoming more of an
> imperative.
>
> We have asked the IESG for their feedback and they are supportive of a
> meeting in
> South America if there is community support and active participants attend.
>
> Things to consider are that it will be a long trip for the majority of
> IETFers and the
> air fares are more expensive (about 10% to 20% higher than average), though
> restaurants are less expensive.  This would be a case where most IETFers
> would
> bear more travel pain and expense.
>
> The IAOC would like to understand if the IETF community thinks that the
> IETF
> should have a meeting in the next few years in Buenos Aires.  The IAOC
> would
> also like to get feedback on how we can ensure the meeting is as
> successful as
> possible and on ways to grow participation in the region.
>
> We have set up a survey at  https://www.surveymonkey.com/s/NWYLQCD  where
> you can indicate your likelihood of attending, and we encourage you to
> send your
> general feedback to the IETF list <ietf@ietf.org>.
>
> Thanks,
> Bob Hinden
> IAOC Chair
>

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

<div dir=3D"ltr"><div>I think this is an excellent idea. The Adelaide meeti=
ng worked out fine, and this would be a lot closer for a great many partici=
pants than that meeting was.<br><br></div>Cheers,<br>Andy<br><br></div><div=
 class=3D"gmail_extra">

<br><br><div class=3D"gmail_quote">On Thu, May 23, 2013 at 11:54 AM, The IA=
OC <span dir=3D"ltr">&lt;<a href=3D"mailto:bob.hinden@gmail.com" target=3D"=
_blank">bob.hinden@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">

As you may know the IAOC has been investigating the feasibility of having a=
n IETF<br>
meeting in South America. =A0There was a site visit to South America last F=
ebruary.<br>
We have found two venues that we believe will support a successful IETF mee=
ting<br>
and we would like to get feedback from the community.<br>
<br>
The venues are in Buenos Aires. =A0They meet our requirements for the meeti=
ng<br>
space, networking, nearby restaurants and bars, hotel room rates in the mid=
 $200<br>
dollar range, nearby alternate hotels at a broad range of prices, nice area=
 in the<br>
city, safe, direct international flights, and accessible visas. =A0The IAOC=
 thinks we<br>
could have a successful IETF meeting in Buenos Aires and that attendees wou=
ld<br>
like the venues.<br>
<br>
There has been a consistent level of IETF participation from South and Cent=
ral<br>
America, and it has been growing since IETF82. =A0The data on this is poste=
d at<br>
<br>
=A0 =A0<a href=3D"http://iaoc.ietf.org/documents/IETF-Regional-Attendance-0=
0.pdf" target=3D"_blank">http://iaoc.ietf.org/documents/IETF-Regional-Atten=
dance-00.pdf</a>.<br>
<br>
The current meeting regional rotation (announced at IETF79) allows for an<b=
r>
occasional IETF meeting outside of our main regions (Europe, North America,=
<br>
Asia/Pacific).<br>
<br>
IETF standards are made more valuable the more relevant they are and the mo=
re<br>
uptake they get. =A0IETF standards are also made more robust when all persp=
ectives<br>
are represented during their development. =A0Encouraging growing participat=
ion<br>
will help strengthen the Internet, further encourage participation from tho=
se areas<br>
that will see the most growth in the coming years, and will help advance th=
e IETF<br>
in political and international circles which is becoming more of an imperat=
ive.<br>
<br>
We have asked the IESG for their feedback and they are supportive of a meet=
ing in<br>
South America if there is community support and active participants attend.=
<br>
<br>
Things to consider are that it will be a long trip for the majority of IETF=
ers and the<br>
air fares are more expensive (about 10% to 20% higher than average), though=
<br>
restaurants are less expensive. =A0This would be a case where most IETFers =
would<br>
bear more travel pain and expense.<br>
<br>
The IAOC would like to understand if the IETF community thinks that the IET=
F<br>
should have a meeting in the next few years in Buenos Aires. =A0The IAOC wo=
uld<br>
also like to get feedback on how we can ensure the meeting is as successful=
 as<br>
possible and on ways to grow participation in the region.<br>
<br>
We have set up a survey at =A0<a href=3D"https://www.surveymonkey.com/s/NWY=
LQCD" target=3D"_blank">https://www.surveymonkey.com/s/NWYLQCD</a> =A0where=
<br>
you can indicate your likelihood of attending, and we encourage you to send=
 your<br>
general feedback to the IETF list &lt;<a href=3D"mailto:ietf@ietf.org">ietf=
@ietf.org</a>&gt;.<br>
<br>
Thanks,<br>
Bob Hinden<br>
IAOC Chair<br>
</blockquote></div><br></div>

--f46d04389001d5849104dd65cca7--

From dmm@1-4-5.net  Thu May 23 10:53:25 2013
Return-Path: <dmm@1-4-5.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A398021F96A3 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 10:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[AWL=-0.776, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJ2fBLWHuRRK for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 10:52:58 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id B479021F8630 for <ietf@ietf.org>; Thu, 23 May 2013 10:39:51 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id fp13so3549069lab.36 for <ietf@ietf.org>; Thu, 23 May 2013 10:39:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=qWTKcT3iyHT5s3kKap+T7XWbt08Q4WSN4abrMiR9vvE=; b=PIYJGPcwaxS53W2HIamLojfKFk5VxW4NNQmP3ydtiNXmM88r1TE527QYO72gR/RsJX /n8I7uj27AevHvkhipO0PZYo6c8zHAUMuZsZRyrcMA7noOVia2n+/ZvjdYkYlphWD2QB JWnRHqsx1YNRAK0DGACE3BH+4BSy0Kl0x5RTp/6DdODxO+3OF5Q/csHEF5VRCBoKBBSS BeQUEWXKt9UYRJwgv2KrvGCzW2CYdqIMaxB71T38Y8dM998yPP5O/he1Xr2LOESThsOk YAaaMoDcc+jetoL3fxYYsTSQPoPm1VI2eE40p6n9iRoeNrroMNHAml8d05T11Eyd3Hab lzlQ==
MIME-Version: 1.0
X-Received: by 10.112.141.38 with SMTP id rl6mr7030953lbb.101.1369330790502; Thu, 23 May 2013 10:39:50 -0700 (PDT)
Received: by 10.112.129.165 with HTTP; Thu, 23 May 2013 10:39:50 -0700 (PDT)
X-Originating-IP: [209.6.156.63]
In-Reply-To: <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>
Date: Thu, 23 May 2013 13:39:50 -0400
Message-ID: <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: David Meyer <dmm@1-4-5.net>
To: "Andrew G. Malis" <agmalis@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQne00/yZzcsxPuWH9I3KkplHPYCpaS4+JF8Z726LKFsZ8hufQ5xWCXnx35zaQSMRuA8ZXP4
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, 23 May 2013 17:53:26 -0000

On Thu, May 23, 2013 at 1:13 PM, Andrew G. Malis <agmalis@gmail.com> wrote:
> I think this is an excellent idea. The Adelaide meeting worked out fine, and
> this would be a lot closer for a great many participants than that meeting
> was.

Likewise. --dmm
>
> Cheers,
> Andy
>
>
>
> On Thu, May 23, 2013 at 11:54 AM, The IAOC <bob.hinden@gmail.com> wrote:
>>
>> As you may know the IAOC has been investigating the feasibility of having
>> an IETF
>> meeting in South America.  There was a site visit to South America last
>> February.
>> We have found two venues that we believe will support a successful IETF
>> meeting
>> and we would like to get feedback from the community.
>>
>> The venues are in Buenos Aires.  They meet our requirements for the
>> meeting
>> space, networking, nearby restaurants and bars, hotel room rates in the
>> mid $200
>> dollar range, nearby alternate hotels at a broad range of prices, nice
>> area in the
>> city, safe, direct international flights, and accessible visas.  The IAOC
>> thinks we
>> could have a successful IETF meeting in Buenos Aires and that attendees
>> would
>> like the venues.
>>
>> There has been a consistent level of IETF participation from South and
>> Central
>> America, and it has been growing since IETF82.  The data on this is posted
>> at
>>
>>    http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.
>>
>> The current meeting regional rotation (announced at IETF79) allows for an
>> occasional IETF meeting outside of our main regions (Europe, North
>> America,
>> Asia/Pacific).
>>
>> IETF standards are made more valuable the more relevant they are and the
>> more
>> uptake they get.  IETF standards are also made more robust when all
>> perspectives
>> are represented during their development.  Encouraging growing
>> participation
>> will help strengthen the Internet, further encourage participation from
>> those areas
>> that will see the most growth in the coming years, and will help advance
>> the IETF
>> in political and international circles which is becoming more of an
>> imperative.
>>
>> We have asked the IESG for their feedback and they are supportive of a
>> meeting in
>> South America if there is community support and active participants
>> attend.
>>
>> Things to consider are that it will be a long trip for the majority of
>> IETFers and the
>> air fares are more expensive (about 10% to 20% higher than average),
>> though
>> restaurants are less expensive.  This would be a case where most IETFers
>> would
>> bear more travel pain and expense.
>>
>> The IAOC would like to understand if the IETF community thinks that the
>> IETF
>> should have a meeting in the next few years in Buenos Aires.  The IAOC
>> would
>> also like to get feedback on how we can ensure the meeting is as
>> successful as
>> possible and on ways to grow participation in the region.
>>
>> We have set up a survey at  https://www.surveymonkey.com/s/NWYLQCD  where
>> you can indicate your likelihood of attending, and we encourage you to
>> send your
>> general feedback to the IETF list <ietf@ietf.org>.
>>
>> Thanks,
>> Bob Hinden
>> IAOC Chair
>
>

From spromano@unina.it  Thu May 23 10:55:25 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDFB21F9206 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 10:55:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FmUxnJYAo6b for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 10:55:11 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 8ACF221F9416 for <ietf@ietf.org>; Thu, 23 May 2013 10:41:04 -0700 (PDT)
Received: from [192.168.1.100] (host121-140-dynamic.42-79-r.retail.telecomitalia.it [79.42.140.121]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r4NHf2rR027095 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 23 May 2013 19:41:02 +0200
From: Simon Pietro Romano <spromano@unina.it>
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8569388B-A287-4782-97DF-21A7B2A238BC"
Subject: Re: IETF Meeting in South America
Date: Thu, 23 May 2013 19:41:03 +0200
In-Reply-To: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
To: IETF list <ietf@ietf.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
Message-Id: <CC54BFB1-7311-4BDF-AD7A-6CE3C611F01C@unina.it>
X-Mailer: Apple Mail (2.1283)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 17:55:26 -0000

--Apple-Mail=_8569388B-A287-4782-97DF-21A7B2A238BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Being a tango addict, Buenos Aires deserves a huge +1 from me!

Cheers,

Simon

Simon

Il giorno 23/mag/2013, alle ore 17:54, The IAOC ha scritto:

> As you may know the IAOC has been investigating the feasibility of =
having an IETF
> meeting in South America.  There was a site visit to South America =
last February.=20
> We have found two venues that we believe will support a successful =
IETF meeting
> and we would like to get feedback from the community.
>=20
> The venues are in Buenos Aires.  They meet our requirements for the =
meeting
> space, networking, nearby restaurants and bars, hotel room rates in =
the mid $200
> dollar range, nearby alternate hotels at a broad range of prices, nice =
area in the
> city, safe, direct international flights, and accessible visas.  The =
IAOC thinks we
> could have a successful IETF meeting in Buenos Aires and that =
attendees would
> like the venues.
>=20
> There has been a consistent level of IETF participation from South and =
Central
> America, and it has been growing since IETF82.  The data on this is =
posted at=20
>=20
>   http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf. =20
>=20
> The current meeting regional rotation (announced at IETF79) allows for =
an
> occasional IETF meeting outside of our main regions (Europe, North =
America,
> Asia/Pacific). =20
>=20
> IETF standards are made more valuable the more relevant they are and =
the more
> uptake they get.  IETF standards are also made more robust when all =
perspectives
> are represented during their development.  Encouraging growing =
participation
> will help strengthen the Internet, further encourage participation =
from those areas
> that will see the most growth in the coming years, and will help =
advance the IETF
> in political and international circles which is becoming more of an =
imperative.
>=20
> We have asked the IESG for their feedback and they are supportive of a =
meeting in
> South America if there is community support and active participants =
attend.
>=20
> Things to consider are that it will be a long trip for the majority of =
IETFers and the
> air fares are more expensive (about 10% to 20% higher than average), =
though
> restaurants are less expensive.  This would be a case where most =
IETFers would
> bear more travel pain and expense. =20
>=20
> The IAOC would like to understand if the IETF community thinks that =
the IETF
> should have a meeting in the next few years in Buenos Aires.  The IAOC =
would
> also like to get feedback on how we can ensure the meeting is as =
successful as
> possible and on ways to grow participation in the region.
>=20
> We have set up a survey at  https://www.surveymonkey.com/s/NWYLQCD  =
where
> you can indicate your likelihood of attending, and we encourage you to =
send your
> general feedback to the IETF list <ietf@ietf.org>.
>=20
> Thanks,
> Bob Hinden
> IAOC Chair
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_8569388B-A287-4782-97DF-21A7B2A238BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Being =
a tango addict, Buenos Aires deserves a huge +1 from =
me!<div><br></div><div>Cheers,</div><div><br></div><div>Simon<br><div><br>=
</div><div>Simon</div><div><br><div><div>Il giorno 23/mag/2013, alle ore =
17:54, The IAOC ha scritto:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>As =
you may know the IAOC has been investigating the feasibility of having =
an IETF<br>meeting in South America. &nbsp;There was a site visit to =
South America last February. <br>We have found two venues that we =
believe will support a successful IETF meeting<br>and we would like to =
get feedback from the community.<br><br>The venues are in Buenos Aires. =
&nbsp;They meet our requirements for the meeting<br>space, networking, =
nearby restaurants and bars, hotel room rates in the mid $200<br>dollar =
range, nearby alternate hotels at a broad range of prices, nice area in =
the<br>city, safe, direct international flights, and accessible visas. =
&nbsp;The IAOC thinks we<br>could have a successful IETF meeting in =
Buenos Aires and that attendees would<br>like the venues.<br><br>There =
has been a consistent level of IETF participation from South and =
Central<br>America, and it has been growing since IETF82. &nbsp;The data =
on this is posted at <br><br> &nbsp;&nbsp;<a =
href=3D"http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf">ht=
tp://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf</a>. =
&nbsp;<br><br>The current meeting regional rotation (announced at =
IETF79) allows for an<br>occasional IETF meeting outside of our main =
regions (Europe, North America,<br>Asia/Pacific). &nbsp;<br><br>IETF =
standards are made more valuable the more relevant they are and the =
more<br>uptake they get. &nbsp;IETF standards are also made more robust =
when all perspectives<br>are represented during their development. =
&nbsp;Encouraging growing participation<br>will help strengthen the =
Internet, further encourage participation from those areas<br>that will =
see the most growth in the coming years, and will help advance the =
IETF<br>in political and international circles which is becoming more of =
an imperative.<br><br>We have asked the IESG for their feedback and they =
are supportive of a meeting in<br>South America if there is community =
support and active participants attend.<br><br>Things to consider are =
that it will be a long trip for the majority of IETFers and the<br>air =
fares are more expensive (about 10% to 20% higher than average), =
though<br>restaurants are less expensive. &nbsp;This would be a case =
where most IETFers would<br>bear more travel pain and expense. =
&nbsp;<br><br>The IAOC would like to understand if the IETF community =
thinks that the IETF<br>should have a meeting in the next few years in =
Buenos Aires. &nbsp;The IAOC would<br>also like to get feedback on how =
we can ensure the meeting is as successful as<br>possible and on ways to =
grow participation in the region.<br><br>We have set up a survey at =
&nbsp;<a =
href=3D"https://www.surveymonkey.com/s/NWYLQCD">https://www.surveymonkey.c=
om/s/NWYLQCD</a> &nbsp;where<br>you can indicate your likelihood of =
attending, and we encourage you to send your<br>general feedback to the =
IETF list &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;.<br><br>Thanks,<br>Bob=
 Hinden<br>IAOC Chair<br><br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></div></body></html>=

--Apple-Mail=_8569388B-A287-4782-97DF-21A7B2A238BC--

From paul.hoffman@vpnc.org  Thu May 23 11:18:04 2013
Return-Path: <paul.hoffman@vpnc.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 BD91021F8433 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 11:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.608
X-Spam-Level: 
X-Spam-Status: No, score=-102.608 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOKd2bqEqqEW for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 11:17:53 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0F84D21F96E4 for <ietf@ietf.org>; Thu, 23 May 2013 10:59:30 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4NHxRSU002965 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 23 May 2013 10:59:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>
Date: Thu, 23 May 2013 10:59:27 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 23 May 2013 18:18:05 -0000

On May 23, 2013, at 10:13 AM, Andrew G. Malis <agmalis@gmail.com> wrote:

> I think this is an excellent idea. The Adelaide meeting worked out =
fine, and this would be a lot closer for a great many participants than =
that meeting was.

(Not that they want us commenting on this thread; that's what the poll =
is for...)

I suspect that if the meeting is approved, the food in Buenos Aires will =
be more interesting than it was in Adelaide, at least for many of us. =
The locals speaking English might also be more understandable. :-)

--Paul Hoffman=

From akatlas@gmail.com  Thu May 23 11:54:51 2013
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E13421F8793 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 11:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHLZTOom3FaG for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 11:54:37 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE3D21F9330 for <ietf@ietf.org>; Thu, 23 May 2013 11:30:35 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id k5so9728990iea.32 for <ietf@ietf.org>; Thu, 23 May 2013 11:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jml4UJxxtFfn70Ndldf3pDa5yustmOuaLcLH6lo3zKo=; b=Bkv67hd/3ntM1Zw/iqrzzYhHJMtLikBxhBdQWAcCgnZrfUo0e7/o1Ng0DCvxQ1I514 3MVyJtSgby1X8aZaxqZgJNIts/HPnb7AivDc4AQ4AEpyNr04NIa5wyNoxXp0sbXB/zqi ML3uKLTcxGEcY8tNDXIDaUpDZdPdLiQfe2/ZTBi7yCyRx5nCC0/rqM0KQAUKZkSWEFNC osLGggoc2h5ta8fyaI9em+TWb2rrTwObY8+THP+6bpxCGaE0U3HcVU3x7wOaVKJlB4Nk 89PgDgbTIznRq6kJSq3Rl3TA/eNdQVXLoQ9eYFy3lyTzhlEouZ5ecoyjBrabV/pJOmdk qdwA==
MIME-Version: 1.0
X-Received: by 10.42.26.12 with SMTP id d12mr10484050icc.1.1369333834849; Thu, 23 May 2013 11:30:34 -0700 (PDT)
Received: by 10.64.24.170 with HTTP; Thu, 23 May 2013 11:30:34 -0700 (PDT)
In-Reply-To: <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com>
Date: Thu, 23 May 2013 14:30:34 -0400
Message-ID: <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Alia Atlas <akatlas@gmail.com>
To: David Meyer <dmm@1-4-5.net>
Content-Type: multipart/alternative; boundary=20cf3042702ece250304dd66e045
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, 23 May 2013 18:54:51 -0000

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

Never been to Buenos Aires - but it sounds like a great idea.  I know that
the search has been on for
an acceptable venue in South America for a long while.

Alia


On Thu, May 23, 2013 at 1:39 PM, David Meyer <dmm@1-4-5.net> wrote:

> On Thu, May 23, 2013 at 1:13 PM, Andrew G. Malis <agmalis@gmail.com>
> wrote:
> > I think this is an excellent idea. The Adelaide meeting worked out fine,
> and
> > this would be a lot closer for a great many participants than that
> meeting
> > was.
>
> Likewise. --dmm
> >
> > Cheers,
> > Andy
> >
>

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

<div dir=3D"ltr">Never been to Buenos Aires - but it sounds like a great id=
ea. =A0I know that the search has been on for<div>an acceptable venue in So=
uth America for a long while.</div><div><br></div><div>Alia<br><div class=
=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, May 23, 2013 at 1:39 PM, David M=
eyer <span dir=3D"ltr">&lt;<a href=3D"mailto:dmm@1-4-5.net" target=3D"_blan=
k">dmm@1-4-5.net</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">
On Thu, May 23, 2013 at 1:13 PM, Andrew G. Malis &lt;<a href=3D"mailto:agma=
lis@gmail.com">agmalis@gmail.com</a>&gt; wrote:<br>
&gt; I think this is an excellent idea. The Adelaide meeting worked out fin=
e, and<br>
&gt; this would be a lot closer for a great many participants than that mee=
ting<br>
&gt; was.<br>
<br>
Likewise. --dmm<br>
&gt;<br>
&gt; Cheers,<br>
&gt; Andy<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt;</div></div></blockquote></div>=
</div></div></div>

--20cf3042702ece250304dd66e045--

From sarikaya2012@gmail.com  Thu May 23 12:07:40 2013
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7119821F9737 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 12:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oC1wr-AV6BKa for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 12:07:30 -0700 (PDT)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 287D821F8CA0 for <ietf@ietf.org>; Thu, 23 May 2013 11:42:49 -0700 (PDT)
Received: by mail-la0-f51.google.com with SMTP id lx15so3629211lab.10 for <ietf@ietf.org>; Thu, 23 May 2013 11:42:49 -0700 (PDT)
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=a8lZgE6KjIYZN6sciXToVKU0lxID/VyST7DJAYgpvVs=; b=kxmT0OF6glpw9rDjfPHb8aT643gxOToFVaf4pCn/jyqmUhwE0eyHe0ByUGsIhwe5fp L36tS7FjoyqAia7Ho7CaSTp/NS0stVjGExon6BImAFRErY+Zvp7LVb8/tLktylYubfsw 2Vwph3IvwnWWK6rQYSYhiUANTEXfGsiPa8UyrI+iG0dCk02SCAlJC1tJQmy4QFbRoHh0 mZebsepqv0XnhA7XA0y6HNhrv3axefe+80vUQ0dcM0zudoUoi3XzYnBGH9ACHsfAvPkV k9JdUnb0C6hjcHlFmWTtqQj0X5aM3N3arO/Fs11hawMwxE7faNREN4Hgny4rfdG6M9Ad OVgg==
MIME-Version: 1.0
X-Received: by 10.112.133.137 with SMTP id pc9mr7078122lbb.74.1369334569019; Thu, 23 May 2013 11:42:49 -0700 (PDT)
Received: by 10.114.62.195 with HTTP; Thu, 23 May 2013 11:42:48 -0700 (PDT)
In-Reply-To: <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org>
Date: Thu, 23 May 2013 13:42:48 -0500
Message-ID: <CAC8QAcfnmbyKDnum9hAPGYyRqc9yJuD3U_nFDBxTNpbkGU9dxg@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=047d7b3439a490b03704dd670c1b
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 19:07:40 -0000

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

On Thu, May 23, 2013 at 12:59 PM, Paul Hoffman <paul.hoffman@vpnc.org>wrote:

> On May 23, 2013, at 10:13 AM, Andrew G. Malis <agmalis@gmail.com> wrote:
>
> > I think this is an excellent idea. The Adelaide meeting worked out fine,
> and this would be a lot closer for a great many participants than that
> meeting was.
>
> (Not that they want us commenting on this thread; that's what the poll is
> for...)
>
> I suspect that if the meeting is approved, the food in Buenos Aires will
> be more interesting than it was in Adelaide, at least for many of us.




> The locals speaking English might also be more understandable. :-)
>
>
In my recent trip to Santiago, Chile, locals not speaking English turned
out to be really painful for someone who can not speak Spanish, like myself.

I hope this is different in BA, but I doubt so.

Behcet

> --Paul Hoffman

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

<br><br><div class=3D"gmail_quote">On Thu, May 23, 2013 at 12:59 PM, Paul H=
offman <span dir=3D"ltr">&lt;<a href=3D"mailto:paul.hoffman@vpnc.org" targe=
t=3D"_blank">paul.hoffman@vpnc.org</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">
<div class=3D"im">On May 23, 2013, at 10:13 AM, Andrew G. Malis &lt;<a href=
=3D"mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt; wrote:<br>
<br>
&gt; I think this is an excellent idea. The Adelaide meeting worked out fin=
e, and this would be a lot closer for a great many participants than that m=
eeting was.<br>
<br>
</div>(Not that they want us commenting on this thread; that&#39;s what the=
 poll is for...)<br>
<br>
I suspect that if the meeting is approved, the food in Buenos Aires will be=
 more interesting than it was in Adelaide, at least for many of us. </block=
quote><div><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The locals speaking English might also be more understandable. :-)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br>In my recent trip to Santiago, Chile, locals not speaking Engli=
sh turned out to be really painful for someone who can not speak Spanish, l=
ike myself.<br>
<br>I hope this is different in BA, but I doubt so.<br><br>Behcet <br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"HOEnZb"><font color=3D"#8888=
88">
--Paul Hoffman</font></span></blockquote></div><br>

--047d7b3439a490b03704dd670c1b--

From john-ietf@jck.com  Thu May 23 12:16:03 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E78D921F980C for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 12:16:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.638
X-Spam-Level: 
X-Spam-Status: No, score=-102.638 tagged_above=-999 required=5 tests=[AWL=-0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5a6RCLTn27P for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 12:15:48 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1B421F901A for <ietf@ietf.org>; Thu, 23 May 2013 11:49:15 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UfaZd-000F7t-Eh; Thu, 23 May 2013 14:49:13 -0400
Date: Thu, 23 May 2013 14:49:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: IETF Meeting in South America
Message-ID: <EDC205179818A3788DA272C3@JcK-HP8200.jck.com>
In-Reply-To: <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF 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, 23 May 2013 19:16:04 -0000

--On Thursday, May 23, 2013 10:59 -0700 Paul Hoffman
<paul.hoffman@vpnc.org> wrote:

> (Not that they want us commenting on this thread; that's what
> the poll is for...)

They explicitly asked for comments on this list.

> I suspect that if the meeting is approved, the food in Buenos
> Aires will be more interesting than it was in Adelaide, at
> least for many of us. 

Based on the last business meeting I attended there, there would
certainly be a larger variety of ways in which burned cow is
prepared :-(

But I rather liked Adelaide and would have no objection in
principle to going back there or to some other appropriate Oz or
NZ location.

    john




From melinda.shore@gmail.com  Thu May 23 12:40:17 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62E1821F871D for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 12:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.766
X-Spam-Level: 
X-Spam-Status: No, score=-2.766 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDF78sNAQPiZ for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 12:40:01 -0700 (PDT)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) by ietfa.amsl.com (Postfix) with ESMTP id BB1F121F9678 for <ietf@ietf.org>; Thu, 23 May 2013 12:05:25 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q11so3229328pdj.38 for <ietf@ietf.org>; Thu, 23 May 2013 12:05:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=BIYQVy0XhIP6NTvcTzV0ISYriCdA4EW5CrXY0NPVKD4=; b=EoRx1CffkqKo2kAhzfoHyK+1jvPVqJkvKZ3QiFcMb7EykrrNrZeF+2zjMRJR8ixnfW d68xNSmEf1j54gN13MO+PsI5hFULoyvLPSxXAsJJnJDZ6eqCwhB3t1/wQv3Bnd/cpgYH HNViOQfpfhEbaNnU9OhSUJCUrhdhv+FotMak8LhzXVJsEHqHGVdbx20hOTYDdlaF/+2R m3ilyqqp4DXhGw8Mn0UBMghgvsa3kTrnUOzJoO3wHuQ9MGu3oms9/sQFuwwvjNTquqsB m2pVYoSZzIVFOVGhijKF54f7pFWIOz3NgwnGzwEcPNMeTXcZkM9C2tggRgirZT74NyEa ckFg==
X-Received: by 10.68.99.226 with SMTP id et2mr14196394pbb.91.1369335925431; Thu, 23 May 2013 12:05:25 -0700 (PDT)
Received: from spandex.local (66-230-83-62-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.62]) by mx.google.com with ESMTPSA id pb5sm12343968pbc.29.2013.05.23.12.05.23 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 12:05:24 -0700 (PDT)
Message-ID: <519E6872.9000100@gmail.com>
Date: Thu, 23 May 2013 11:05:22 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>
In-Reply-To: <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 19:40:17 -0000

On 5/23/13 10:30 AM, Alia Atlas wrote:
> Never been to Buenos Aires - but it sounds like a great idea. 

I'm skeptical that it will change much - it seems likely to me
that we'll get a bunch of one-time attendees and that we'll be
doing really well to get one new person who becomes a continuing
participant.  That said, I do think it will be *extremely*
valuable to get feedback from those one-time attendees about
what they're seeing in our documents, and that we should be
trying to figure out ahead of time how to engage those one-time
attendees.

Traveling from Fairbanks, pretty much anywhere is a long, long
trip and quite expensive relative to what most people pay for
airfare, so actual location doesn't make that much of a difference
to me personally.  I also don't think it's that big a deal if a
few regulars miss one meeting because it's too far or too
costly or whatever.

So as I said, I'm skeptical, but I think the potential benefits
of giving this a shot outweigh the likely downsides.

Melinda


From johnl@iecc.com  Thu May 23 13:22:23 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E7E921F96C0 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 13:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.051
X-Spam-Level: 
X-Spam-Status: No, score=-111.051 tagged_above=-999 required=5 tests=[AWL=0.148, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WPNqOE0K0f00 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 13:22:02 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id BFC8821F871D for <ietf@ietf.org>; Thu, 23 May 2013 12:41:38 -0700 (PDT)
Received: (qmail 97486 invoked from network); 23 May 2013 19:41:37 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 23 May 2013 19:41:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519e70f1.xn--i8sz2z.k1305; i=johnl@user.iecc.com; bh=KedKL/ypAoCWQAvZCgWXZ9zgpGbxR+xmGvOqDZIlwmQ=; b=o38fEToHLdhreFc8mPr2pfGJMdRhS1lz7efS55ZBBCyScLfK3ftNQ3eUTEp+U8Tp+BwNKTvjHHTszP0cSADp6ze4QxiMAXYOdAB8S1+f+8o+wahbLlyebQ5M9Xo/ntttlxvL1HZJPZ8CA9Uw7XEzK0UElWi+ay9I9iPc2vdu50M=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519e70f1.xn--i8sz2z.k1305; olt=johnl@user.iecc.com; bh=KedKL/ypAoCWQAvZCgWXZ9zgpGbxR+xmGvOqDZIlwmQ=; b=HI/cb/qh29CSKDUp6qJ1hPeODhvjtCGTHYgjxlwjDkzIOgRmLKqJI/pEkvnJdV9MN4OXBOA+oRIbCr1BZBPhHU7K+5I8AsfHWtZ5zyR5JHwlMQ0QfmiSvCyohXMRm/LU2Nim4Mo4K637EY3Wsoy+QmKcnv3m2Za3G+opACG+3w4=
Date: 23 May 2013 19:41:15 -0000
Message-ID: <20130523194115.27200.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
In-Reply-To: <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paul.hoffman@vpnc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 20:22:23 -0000

> I suspect that if the meeting is approved, the food in Buenos Aires
> will be more interesting than it was in Adelaide, at least for many of
> us. The locals speaking English might also be more understandable. :-)

If you like steak or pizza and lots of pretty good red wine, the food
in Buenos Aires is quite excellent.  If you want something else, it's
spotty.  But I agree that it's likely to be as good a place in South
America as any to meet.

R's,
John

From john-ietf@jck.com  Thu May 23 13:56:14 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C43A21F97B3 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 13:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.636
X-Spam-Level: 
X-Spam-Status: No, score=-102.636 tagged_above=-999 required=5 tests=[AWL=-0.037, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6xpsgSFTcA7 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 13:55:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B55EE21F97DB for <ietf@ietf.org>; Thu, 23 May 2013 13:13:09 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ufbsq-000FDb-Gg; Thu, 23 May 2013 16:13:08 -0400
Date: Thu, 23 May 2013 16:13:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: sarikaya@ieee.org
Subject: Re: IETF Meeting in South America
Message-ID: <71938FD78E10FF779D65E42A@JcK-HP8200.jck.com>
In-Reply-To: <CAC8QAcfnmbyKDnum9hAPGYyRqc9yJuD3U_nFDBxTNpbkGU9dxg@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <D8428961-8C88-4701-A6BB-BD45F6AE8C1B@vpnc.org> <CAC8QAcfnmbyKDnum9hAPGYyRqc9yJuD3U_nFDBxTNpbkGU9dxg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 20:56:14 -0000

--On Thursday, May 23, 2013 13:42 -0500 Behcet Sarikaya
<sarikaya2012@gmail.com> wrote:

>> The locals speaking English might also be more
>> understandable. :-)
>> 
>> 
> In my recent trip to Santiago, Chile, locals not speaking
> English turned out to be really painful for someone who can
> not speak Spanish, like myself.
> 
> I hope this is different in BA, but I doubt so.

Probably about the same as Santiago, at least in my experience
with both.  The comment about English is Adelaide was presumably
intended as a joke -- The various dialects of Aussie are
probably not a different language from American English, but the
point is occasionally debated.

   john


From arturo.servin@gmail.com  Thu May 23 14:23:10 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 421C321F8DFC for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 14:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t9QZoTPN05V2 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 14:22:53 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 9D89621F97A9 for <ietf@ietf.org>; Thu, 23 May 2013 13:39:27 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id ii15so3671598qab.4 for <ietf@ietf.org>; Thu, 23 May 2013 13:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/KQRcjqAXrZ7nbU3BKjUvfIDu9TUewp7AoTfu8VNpe8=; b=m6l0NP5OcabR0pQXD/RMn98XwT6OPwABl3VY9YGbnYaGtYUZs/HDVkKWAjGjT/uTMb yfSKbBasCKgwjaATdySutBqZPGq6wFenARSyWMHOuv6t/plsmtsYpIm8GgcFQDETIWaS djzsiGI6MstJy3HEdZyrxU9o1xgI7vps0E/FdfMOOjngjFu55VXakW6R0lbgT/81DVKr w0Ru1O5YOAxTPRjQhm3qGZ51IRXhywDfaZrs4nWlo3rCj/9vfS4Yr3TsxaLqBd9TMCvh 3OSJoCCHYWR1hGzVH8vAs3/Z/2QHrhLBwTEFksHFSJOmrDiJE0PqnRKjWsrFvg/ph+Aj ajcg==
X-Received: by 10.49.75.134 with SMTP id c6mr15032600qew.47.1369341567009; Thu, 23 May 2013 13:39:27 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (r186-49-10-198.dialup.adsl.anteldata.net.uy. [186.49.10.198]) by mx.google.com with ESMTPSA id y14sm12097710qac.0.2013.05.23.13.39.25 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 13:39:26 -0700 (PDT)
Message-ID: <519E7E83.9000809@gmail.com>
Date: Thu, 23 May 2013 17:39:31 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>
In-Reply-To: <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 21:23:10 -0000

	This is very good news. If done, it would show how the IETF is evolving
and adapting to this new world that it is own creation "the Internet"
has make us live in.

Regards,
as

On 5/23/13 3:30 PM, Alia Atlas wrote:
> Never been to Buenos Aires - but it sounds like a great idea.  I know
> that the search has been on for
> an acceptable venue in South America for a long while.
> 
> Alia

From d3e3e3@gmail.com  Thu May 23 15:29:15 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5397421F9651 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 15:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DuJ8N56y28nJ for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 15:29:14 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 048B221F992E for <ietf@ietf.org>; Thu, 23 May 2013 14:48:18 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id tb18so4701039obb.3 for <ietf@ietf.org>; Thu, 23 May 2013 14:48:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=XSLFO+DG/261fZpN6lwEHVe7OBaKlcXijsPBU1c6HrA=; b=ou2KFgMj6g8ajmueWA5ZrNlWzD6UwmcrnhEUP0NGNsxI/djn0+Mt8BKqnSxs58N9p1 EYOFJhP3GxPZcn7tDsAysHBvkyyh/5MSg1sxg5zgSxc9cH7NI7NW26dD1zcVLKvsVZQO r+XeXoZO9ukSeEQAWRaLRWLiOjyUCeABMpMw5F92yIkh8EAW3n72VCT0BD3wUgpRLOau 6oE+kI5D/2VeX6SveA2LTQ40Ro/jlGaWNUCZxZV8EpBrRevxAXRqAssm0XZsgFie4LNe ohL30z9dTft+OkzBMBqm3lJeYx5Mu4Lzd7VR+RBiYY1zCkWLUYJK+kPD3s6g9JxUEbIG ENXg==
X-Received: by 10.182.131.133 with SMTP id om5mr10019212obb.79.1369345698499;  Thu, 23 May 2013 14:48:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.162.233 with HTTP; Thu, 23 May 2013 14:47:58 -0700 (PDT)
In-Reply-To: <519E7E83.9000809@gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 23 May 2013 17:47:58 -0400
Message-ID: <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com>
Subject: Re: IETF Meeting in South America
To: Arturo Servin <arturo.servin@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 22:29:15 -0000

On Thu, May 23, 2013 at 4:39 PM, Arturo Servin <arturo.servin@gmail.com> wrote:
>
>         This is very good news. If done, it would show how the IETF is evolving
> and adapting to this new world that it is own creation "the Internet"
> has make us live in.

You seem slightly confused. If you look at the original message, it
talks about there having been increased attendance at IETF meetings
from South and Central America.

As far as I know, it has been and is still more or less the policy of
the IETF to hold meetings where attendees have been coming from. The
purpose of IETF meetings is to contribute to standards development,
not "outreach" or something, which is a goal for other organizations.
If few attend from some part of the world, there will be few/no IETF
meetings there no matter what the population or amount of network use
in that part of the world. I do not see and do not particularly want
any "evolving" in how the IETF decides where to meet.

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

> Regards,
> as
>
> On 5/23/13 3:30 PM, Alia Atlas wrote:
>> Never been to Buenos Aires - but it sounds like a great idea.  I know
>> that the search has been on for
>> an acceptable venue in South America for a long while.
>>
>> Alia

From arturo.servin@gmail.com  Thu May 23 15:36:40 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18FD221F904B for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 15:36:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DjtzgaUsbNmB for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 15:36:39 -0700 (PDT)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFE621F9831 for <ietf@ietf.org>; Thu, 23 May 2013 15:14:01 -0700 (PDT)
Received: by mail-qc0-f170.google.com with SMTP id s11so2098483qcw.29 for <ietf@ietf.org>; Thu, 23 May 2013 15:14:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8b8Opa72BWMPh99LH0K07fC3BZBVm1LRhQ5JzUiDIPs=; b=xqEEOZBzI3ZWmwstscvfgr6F45dim5c2qD3Z5KHvjUBZZAmL0siCBuJcxdGbpPxBVa ESJIZfKcG4okXX9sRENCIr8wN7O5b2903fwKUamTa2wXRkvtRAj6324bmz6QG4JY+M20 3zgxLnIC6PuNncjvcXckpG/rV7lPXpghMJrFsEh5OD6tQPgwOXiLngJOP7vPZOiCw8jm gz3/FMc/dueLk91imWy9f5HSwk1l3lTXuHjBys5FimSklAJQSJkHe68NY/lmeCeF6yCk slXbySlPRZOfBr/EaHg5nWWqpdhRxej0817u5LoT6ebiphspOv5aW2nPX6tb+LQjj03x nODw==
X-Received: by 10.49.83.231 with SMTP id t7mr15866478qey.9.1369347240653; Thu, 23 May 2013 15:14:00 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (r186-49-10-198.dialup.adsl.anteldata.net.uy. [186.49.10.198]) by mx.google.com with ESMTPSA id db3sm13995266qab.4.2013.05.23.15.13.58 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 15:13:59 -0700 (PDT)
Message-ID: <519E94AC.3060500@gmail.com>
Date: Thu, 23 May 2013 19:14:04 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com>
In-Reply-To: <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.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, 23 May 2013 22:36:40 -0000

	Today is not enough to only have meetings where attendees are coming
from. That is a parading that we need to break and I think that we are
moving in that direction.

	I am not expecting to agree with me as I do not agree that we only
contribute to standards development.

Regards,
as

On 5/23/13 6:47 PM, Donald Eastlake wrote:
> On Thu, May 23, 2013 at 4:39 PM, Arturo Servin <arturo.servin@gmail.com> wrote:
>>
>>         This is very good news. If done, it would show how the IETF is evolving
>> and adapting to this new world that it is own creation "the Internet"
>> has make us live in.
> 
> You seem slightly confused. If you look at the original message, it
> talks about there having been increased attendance at IETF meetings
> from South and Central America.
> 
> As far as I know, it has been and is still more or less the policy of
> the IETF to hold meetings where attendees have been coming from. The
> purpose of IETF meetings is to contribute to standards development,
> not "outreach" or something, which is a goal for other organizations.
> If few attend from some part of the world, there will be few/no IETF
> meetings there no matter what the population or amount of network use
> in that part of the world. I do not see and do not particularly want
> any "evolving" in how the IETF decides where to meet.
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
> 
>> Regards,
>> as
>>
>> On 5/23/13 3:30 PM, Alia Atlas wrote:
>>> Never been to Buenos Aires - but it sounds like a great idea.  I know
>>> that the search has been on for
>>> an acceptable venue in South America for a long while.
>>>
>>> Alia

From jari.arkko@piuha.net  Thu May 23 15:39:03 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B796221F9600 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 15:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4L7KI7OVd9vP for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 15:38:58 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EF44521F91CB for <ietf@ietf.org>; Thu, 23 May 2013 15:25:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8C1812CC48; Fri, 24 May 2013 01:25:07 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39mcXaNdWXQt; Fri, 24 May 2013 01:25:07 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E863A2CC3C; Fri, 24 May 2013 01:25:06 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
Date: Fri, 24 May 2013 01:25:06 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
To: The IAOC <bob.hinden@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 22:39:03 -0000

For what it is worth, I wanted to provide my perspective on this. I of =
course believe that it is important that the IETF reaches out to an even =
more international participation than it already has. This is first of =
all because we really need the views from different types of =
organisations and different parts of the world. For instance, I recently =
had an opportunity to talk to a number of people about peering in =
different regions. It really opened my eyes about how the Internet =
experience can differ from what I've been used to so far. We also need =
to understand how regionally changing requirements for, e.g., emergency =
communications or whitespace management affect our work. Finally, our =
international coverage is not just important for our work but also for =
how we are perceived. For all of these reasons, reaching out to =
different parts of the world is important, and one aspect of that is =
rotating through meeting locations around the world.

I would also like to highlight one part of the message from Bob:

> The IAOC would
> also like to get feedback on how we can ensure the meeting is as =
successful as
> possible and on ways to grow participation in the region.

This is really important, and I hope that we get good feedback on what =
kinds of things would be useful to do in order to achieve this. That is, =
we're not just asking a binary question if the meeting is or is not ok.=20=


Just meeting in some place does not bring too many new participants, at =
least not in a lasting manner. But combined with some other actions, =
this may be possible. Are there specific companies or research teams =
that we could reach out to, and who might want to be involved in the =
IETF? Are there local events where where it would be useful to have =
someone from the IETF give a talk? Are there specific IETF or IRTF =
efforts where we could get more people from South America involved? =
Should the ISOC fellows program target something different than it has =
so far, or be scaled up? Other ideas?

Jari

P.S. By coincidence, I happened to visit Buenos Aires last year, and =
found it to be a fun city. I felt safe and despite not speaking the =
local language I was able to talk to the friendly locals, order food, =
access the network, acquire a SIM card (albeit with some bureaucratic =
and technical difficulties, but I think I can still dig up the MNC =
numbers that were needed to configure the phone correctly :-), use the =
airports, rent a car, and find a Finnish sauna. I think the city offers =
all the essential ingredients for life :-)


From fred@cisco.com  Thu May 23 16:06:21 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C6421F95E4 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 16:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.354
X-Spam-Level: 
X-Spam-Status: No, score=-110.354 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N+eVkvr+14KT for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 16:06:11 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAD921F95E1 for <ietf@ietf.org>; Thu, 23 May 2013 16:06:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3307; q=dns/txt; s=iport; t=1369350371; x=1370559971; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=8+bM2neu2RWM/z8odo1PRVuvX5lSwHRBOAn38qsdcDw=; b=TUeTn1Aq4ktRpxy6G7k+iq1yCtWb30ht4FvrPcFujVm/l9wO6N5XE3oM JSSx5+gRRs5IElDwrYEY+8FVapyconigvb+qJodFZPUU/foITEnvlPW3M mGx7sR63V/QYlq9CZD+3VL9V2dJbcXZPDK18U4u/cBX46NMG68GJ8NjjH k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFANmfnlGtJV2Y/2dsb2JhbABZgwjCX4EMFnSCIwEBAQMBGFYLBQsCAQgiJCERJQIEDgUIh3MDCQaxJw2IV4xGgiQCMQeCc2EDiGeMbo4DhSODD4Im
X-IronPort-AV: E=Sophos;i="4.87,730,1363132800"; d="scan'208";a="214379552"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP; 23 May 2013 23:06:08 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4NN68Z3024596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 May 2013 23:06:08 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Thu, 23 May 2013 18:06:08 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Arturo Servin <arturo.servin@gmail.com>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV84ZK1H1cwSoGEybXfeog56LNJkTVccAgAAHewCAAA4tAIAAJAeAgAATIACAAAdLAIAADoiA
Date: Thu, 23 May 2013 23:06:07 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com>
In-Reply-To: <519E94AC.3060500@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <EEA1C0E38EF99940BED3D527E76E28DF@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 23:06:21 -0000

On May 23, 2013, at 3:14 PM, Arturo Servin <arturo.servin@gmail.com>
 wrote:

> I am not expecting to agree with me as I do not agree that we only contri=
bute to standards development.

I agree with the substance of Donald's comment. Let me talk for a moment ab=
out Adelaide.

In March 2000, the IETF met in Adelaide. I was the person who made the deci=
sion to go there. My logic was, as Don's is in this thread, that we have a =
primary purpose, and that the positioning of meetings was largely about whe=
re our attendees came from. At the time, the IETF was perhaps 1500 people, =
of whom about 675 posted Internet Drafts (I know the number, because I sent=
 them individual emails, in effect running a survey about the advisability =
of a meeting in Adelaide). We had 8 people from Australia that had been wor=
king in the IETF for a number of years, and AARNET was willing to host a me=
eting. Also at the time, about one author in six was from Europe, and we ha=
d very few from Asia. So we were operating on the principle that one meetin=
g in six should be in Europe. I took the perspective that on our 40th meeti=
ng, we could have 1/40 in a place that we had a few faithful participants t=
hat was well out of the way.

It was not billed or intended as a developmental activity, and it didn't tu=
rn out to be one. We still have a small percentage of people from Australia=
, and thy are still faithful. As far as I know, having a meeting there didn=
't affect that positively or negatively. It was a fairness thing, extending=
 a courtesy to people who were doing good work over a long period of time.

We now have roughly 1/3 of our attendees and authors from Asia, 1/3 from Eu=
rope, and 1/3 from North America. We have a few people from South America, =
of which you are one, and the only time we have people from Africa is when =
ISOC pays for them to come. We try to position meetings in those continents=
 once a year, it doesn't quite work for reasons that require an adult bever=
age to discuss, but we do try. And we get a lot of commentary from folks th=
at would like the IETF to be a development organization.=20

There is a political aspect. The ITU pays the air fare for people from deve=
loping countries, and friends vote for friends. This is relevant in WSIS/WC=
IT/WTF, where the ITU periodically offers itself as the SDO of the future. =
I won't go into that further, but it is the elephant in the room, and there=
, I have said it.

To my way of thinking, the argument for a meeting in South America is not t=
hat maybe possibly we will get more attendees. If they have a reason to com=
e, they will first be on the various mailing lists and contribute in that w=
ay, and in time will find it in their business interest to attend in person=
. You did that, Fernando did that, it's what our Asian colleagues did a dec=
ade ago, and it's what our European colleagues did a decade before that. Fr=
om my perspective, the argument for an IETF meeting in South America, wheth=
er in Buenos Aires or somewhere else, is that we have people doing good wor=
k (show us the Internet Drafts) that have been participating over a period =
of time, and - well, we meet where our participants come from, like we did =
in Adelaide.=

From mnot@mnot.net  Thu May 23 16:28:06 2013
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 E58E921F962A for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 16:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.672
X-Spam-Level: 
X-Spam-Status: No, score=-105.672 tagged_above=-999 required=5 tests=[AWL=-3.073, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p2-bO3+dNckn for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 16:28:01 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 5F45821F9626 for <ietf@ietf.org>; Thu, 23 May 2013 16:28:01 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.66.111]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7AF17509B5; Thu, 23 May 2013 19:27:59 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com>
Date: Fri, 24 May 2013 09:27:54 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com>
To: Fred Baker (fred) <fred@cisco.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 23:28:07 -0000

On 24/05/2013, at 9:06 AM, Fred Baker (fred) <fred@cisco.com> wrote:

> I took the perspective that on our 40th meeting, we could have 1/40 in =
a place that we had a few faithful participants that was well out of the =
way.

Does this imply that, if we have a meeting in South America, I'll need =
to wait another 10 years before I fly less than 24 hours to get to an =
IETF meeting?

Cheers from Melbourne,

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




From juliao@braga.eti.br  Thu May 23 18:35:04 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D2A21F85E8 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 18:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id juiK5e7WygP2 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 18:34:57 -0700 (PDT)
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by ietfa.amsl.com (Postfix) with ESMTP id 23BC021F85C9 for <ietf@ietf.org>; Thu, 23 May 2013 18:34:56 -0700 (PDT)
Received: by mail-vc0-f178.google.com with SMTP id id13so2707858vcb.23 for <ietf@ietf.org>; Thu, 23 May 2013 18:34:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=2WdI6u+Vhb1oq0igLLCs+T3Hu6agy17DVxAdgR0IUNc=; b=M0A6VEwXFIhRrNwRvSyLN+IVdvq4MFZa3gn9sFDnbJ7SR46ZjzaxAVRw8okTKn7/k+ g7IjDXNHZkkuDjjiofQ1JWqAKb9Fp2XZn2udmmXK7kL3DA83y4fQohmihmTbEeWNr7fV swjQv/qOkjrtaig2pDQJ48+Tu6M7C/ER32Z58r3TY63+f4szmSYy3fGwnlYtbCwhO8Dc K+p7i6bJjgLfu3TtGktk8/1X6hZG5AeguZTkseClEBXfi5dzsGji96knSCWHn9I0zFAz 0yR/OJQFuKSerDLL/amcXUdSo0bSXd26BF8xGPcPtI95TiROo4AadW4UjbHSOH0zqAPt XBjw==
X-Received: by 10.58.234.134 with SMTP id ue6mr7175866vec.20.1369359296159; Thu, 23 May 2013 18:34:56 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id s9sm7062918vdh.4.2013.05.23.18.34.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 18:34:55 -0700 (PDT)
Message-ID: <519EC3BA.9010908@braga.eti.br>
Date: Thu, 23 May 2013 22:34:50 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org, j@braga.net.br
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
In-Reply-To: <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQk4VLSuNfthD+c406UeodUaMd3w2cA7WkTjE50M/ehKu1B/VRb27TN4NbXNP8vdKodwP4VO
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 01:35:04 -0000

I stare at the map of where the IETF meetings occurred
(http://ws.org.br/index.php/IETF_Meetings) and wondering if the fact of
bringing some of the meetings to below the Equator could lead to
increase people participation.

The answer is always negative. Will not increase participation of more
people.

Fellowships will help? Certainly not. Resources are finite.

How then can we increase participation in meetings of the IETF? My
answer to the question may seem strange: increasing the number of annual
meetings.

Currently there are three. How many? To twelve meetings per year, for
example!

As follows:

1. Pass the Annual Meetings of the IETF for two: say late March and late
November;
2. Create two annual meetings in each one of the five RIR regions. For
example, early February and early October. Will be Regional Meetings,
with the same focus of current meetings with an emphasis on contribute
to the next Annual Meeting.

The dates above are only examples. But consider the folowing
complementary ideas:

a. Encourage grants for regional events
b. Create well-defined rules, so that EVERYONE countries in the region
are sequentially headquarters of the regional event, with the exceptions
of the local situation.
c. Annual Events can occur at fixed locations. Innovative and tireless
people could think of IETF City, IETF University, etc. The logistics
personnel could imagine where in the world, the Annual Events would be
great for everyone.
d. Create special Fellowships for participation in Annual Events based
on regional activity of the grantee.
e. Etc.

Regards,

Julião

From melinda.shore@gmail.com  Thu May 23 18:46:21 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9EE21F9539 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 18:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.724
X-Spam-Level: 
X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGAk0Ee0lN4U for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 18:46:15 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id D4A6C21F9362 for <ietf@ietf.org>; Thu, 23 May 2013 18:46:15 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id 10so3559507pdi.31 for <ietf@ietf.org>; Thu, 23 May 2013 18:46:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=0g/BgDWRSpHaEdC7EMzowj9b5Y2nIoDhnnex2QYlbpg=; b=cbEEa0Z9iJSNX1SFfsyUdZQyfZMmccTNFEgGo0KF7OHwRCT1Rleo3WOGOJt5QO7oUz 3hImXV362iUwSj4x9PWQCHfEyZG/EbYzT3O74jp/UDR3znmP6A5VvjqL6PvzeZmEt7Vw WQtQdHvJuoaTSWBkBOZVwF3ZH38WuDGJqffzfI/xtmMsyqzp4R5eSPdOcRAzptFSc3ZA HDW5fNXD6P+McEFjdoIcoaQlWYBgqjLuP8dENzKSQpr1MZI5Nu3dTk3MM3EYITsvSVQ/ wF/5V2YLl0kgu5yKqLQf4JY7YcXjLPYhfJv6l73SOGUcquZRTd87Bey3n0knnEs6NryO EmSQ==
X-Received: by 10.66.218.170 with SMTP id ph10mr16269609pac.134.1369359975470;  Thu, 23 May 2013 18:46:15 -0700 (PDT)
Received: from spandex.local (66-230-83-62-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.62]) by mx.google.com with ESMTPSA id vm10sm15094934pab.5.2013.05.23.18.46.13 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 18:46:14 -0700 (PDT)
Message-ID: <519EC664.5050806@gmail.com>
Date: Thu, 23 May 2013 17:46:12 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br>
In-Reply-To: <519EC3BA.9010908@braga.eti.br>
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, 24 May 2013 01:46:21 -0000

On 5/23/13 5:34 PM, Juliao Braga wrote:
> Currently there are three. How many? To twelve meetings per year, for
> example!

Sounds like a sure-fire way to shift the participation from
skewing towards working engineers to skewing towards professional
standardizers.

How can we encourage people from underrepresented areas to 1)
submit internet drafts, 2) review working group drafts, and 3)
participate in mailing list discussions?

Melinda


From juliao@braga.eti.br  Thu May 23 19:37:59 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D58421F91B2 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 19:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UwQ09lP6HjPO for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 19:37:54 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id CE51D21F9060 for <ietf@ietf.org>; Thu, 23 May 2013 19:37:53 -0700 (PDT)
Received: by mail-gh0-f172.google.com with SMTP id r18so1421786ghr.3 for <ietf@ietf.org>; Thu, 23 May 2013 19:37:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=NGoG200HswJn0Ej9tmlNTab/sHiULxiHYLR/Qqmhrgo=; b=F0Ju2S4Ro4CFg/FNiLdy5pKfJ1fIUyINWfU4FkZXARn3fHs3lfV4QmPC7byt2/n02O QxWrheXz9uq+DvkNSsVuoiF1QxyJWItM/cElGdTYcjxYdgD3EUOxxlyG46oI+j453KIj ddiN1SkfvTa0si5LkvDVjVHb+353Y2+CE5FDvhBSkmQJXUUAXXnX+vVrtYU8XXhQkdXD kj6+sI6ZMo+N8Corp3mU5zdV4Oq4fAvUn9YHt6tcARozNBblxCQGFnK0EpbCycI3ul9Z XeRjoC1bjp0cLwh8TGg2tiabDl6Khf9pwucKJi0KbEx+ensEFTb4/kltd3xzthnoYHum q2Uw==
X-Received: by 10.236.129.236 with SMTP id h72mr1306978yhi.142.1369363073183;  Thu, 23 May 2013 19:37:53 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id u69sm21258358yhf.23.2013.05.23.19.37.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 19:37:52 -0700 (PDT)
Message-ID: <519ED27D.9050709@braga.eti.br>
Date: Thu, 23 May 2013 23:37:49 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org, j@braga.net.br
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com>
In-Reply-To: <519EC664.5050806@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQmPJq+Vq5Swwpnfv8oVlIURNiqZNQtjQtipLxAmAHkX7VTgQZJp2fZFyvVhiumzPZhdm9TV
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 02:37:59 -0000

I think we will have new challenges to be defined. New opportunities for
change that can stimulate, for example, the coming of researchers
immersed in universities and / or research centers, not yet
participating in the IETF. Maybe they can not submit drafts, but can
contribute to foster the knowledge of those who produce drafts or
working as reviewers. Regarding the participation in discussions of the
mailing lists, I think that they might be involved with reasonable
intensity, ideas, and knowledge.

The IETF can create new types of publications other than RFCs (calling
attention to the debate about in diversity and erica lists).

Perhaps the IETF should and can change (not where it has always been a
success) to capture new people.

Julião

Em 23/05/2013 22:46, Melinda Shore escreveu:
> On 5/23/13 5:34 PM, Juliao Braga wrote:
>> Currently there are three. How many? To twelve meetings per year, for
>> example!
> 
> Sounds like a sure-fire way to shift the participation from
> skewing towards working engineers to skewing towards professional
> standardizers.
> 
> How can we encourage people from underrepresented areas to 1)
> submit internet drafts, 2) review working group drafts, and 3)
> participate in mailing list discussions?
> 
> Melinda
> 
> 

From melinda.shore@gmail.com  Thu May 23 19:44:07 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 196F021F93D1 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 19:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gDzdG8JQv7VO for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 19:44:06 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 52F5021F9418 for <ietf@ietf.org>; Thu, 23 May 2013 19:44:05 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id uo1so3670138pbc.15 for <ietf@ietf.org>; Thu, 23 May 2013 19:44:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=nj1pzWqmvPbg1J7pna1eDqfNZS8T3Fb271OQwPcl020=; b=czCpgA9+Chz3rmyj2rMfNm18dsn1Nc47STPXDJNXcfP5pGg6jh8NnSX/eu+NKRKBar XGqXhVvPePxrsFWVilaHwi30jrgaaAY5XJXWXnA9WNL3I8ESZBPxmcXZMEeXyTi6t+lK GR0Clt6xhDmhifcriWX6tuT85Jh2Qo0LV/xIY61u3emaJ1tFM60LPzwzGIKC3Fb/SuUv vsefAgfO+oGP5ig1Pi+aBTnkFvEzyMQ+j2MOjGwMWwmH9G1v4ovS6AeuDEV7gR3ATdny Zl82IRhJf24unykypcUkpjCEG9xIHUy+dn72t9kr1y19w1rWJszUE6NxbVjcpB4uZek0 yY0w==
X-Received: by 10.68.191.167 with SMTP id gz7mr16007159pbc.16.1369363443506; Thu, 23 May 2013 19:44:03 -0700 (PDT)
Received: from spandex.local (66-230-83-62-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.62]) by mx.google.com with ESMTPSA id v7sm14106303pbq.32.2013.05.23.19.44.01 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 May 2013 19:44:02 -0700 (PDT)
Message-ID: <519ED3F0.40300@gmail.com>
Date: Thu, 23 May 2013 18:44:00 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br>
In-Reply-To: <519ED27D.9050709@braga.eti.br>
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, 24 May 2013 02:44:07 -0000

On 5/23/13 6:37 PM, Juliao Braga wrote:
> Maybe they can not submit drafts, but can
> contribute to foster the knowledge of those who produce drafts or
> working as reviewers. 

Anyone can submit a draft and anyone can review a draft.  The
barrier to that sort of participation is extremely low.  So
the question is why we aren't seeing more drafts, reviews, and
discussions from people in Central and South America, and
what we can do as an organization to change that.  I have no
problem with meeting in Buenos Aires but I do not have reason
to think that having a meeting there will do anything to
increase active participation from that region.

Melinda


From drc@virtualized.org  Thu May 23 20:03:03 2013
Return-Path: <drc@virtualized.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 7F4C921F93B1 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sav9pK+414oz for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:02:57 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id B42B321F942D for <ietf@ietf.org>; Thu, 23 May 2013 20:02:57 -0700 (PDT)
Received: from [10.0.1.4] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 5F2DA172A2; Fri, 24 May 2013 03:02:56 +0000 (UTC)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: David Conrad <drc@virtualized.org>
In-Reply-To: <519ED3F0.40300@gmail.com>
Date: Thu, 23 May 2013 20:02:55 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 24 May 2013 03:03:03 -0000

On May 23, 2013, at 7:44 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> So the question is why we aren't seeing more drafts, reviews, and
> discussions from people in Central and South America,

Language?

Regards,
-drc



From johnl@iecc.com  Thu May 23 20:31:28 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 721F721F960C for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.06
X-Spam-Level: 
X-Spam-Status: No, score=-111.06 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mItDMssyoEHB for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:31:24 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A868821F8FAF for <ietf@ietf.org>; Thu, 23 May 2013 20:31:21 -0700 (PDT)
Received: (qmail 96727 invoked from network); 24 May 2013 03:31:19 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 May 2013 03:31:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519edf07.xn--30v786c.k1305; i=johnl@user.iecc.com; bh=wZGYlZzUJMrIqXH0owjj4Kltqb3Ea2AaOyTrqgqGNuk=; b=e68Ad7kVbwUIE3GRpTwoFHd3/dy3vwA6j0vhqeZiBb+3J6SEnrgvF0ux5iKPO7vqUm0gveJm4yOx/O5RcvsRQ+vp3Z1XhczgGyTVLj3fUP4jsTTjqVhrPiAEQGBGS2JTMhg8hmwh9SahdyIeM5x4yOK9XReRjcFtG/ZXtch7LiU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519edf07.xn--30v786c.k1305; olt=johnl@user.iecc.com; bh=wZGYlZzUJMrIqXH0owjj4Kltqb3Ea2AaOyTrqgqGNuk=; b=DG1tVJX4/eln3yYA9YY9W8h0GbiJ7ClKWBFuDqf+ng6OZF8FnC0AJLI2ZIynL4yA517tnezD3z0S5i9CWnNf/3OZZ5tcjwTcy8WMZe6Z4oUXwyiga/n7Ap9hngdpXhxaxgc0lrbEb3v3B9sj1vQHQMdPqq8TUHiySAUa3RVLti0=
Date: 24 May 2013 03:30:57 -0000
Message-ID: <20130524033057.36345.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
In-Reply-To: <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 03:31:28 -0000

>On May 23, 2013, at 7:44 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
>> So the question is why we aren't seeing more drafts, reviews, and
>> discussions from people in Central and South America,
>
>Language?

Possibly, but we get quite a lot from parts of Asia where I'd think
the language issue would be more severe.

I agree with Melinda, it would be good to figure out how to get people
in South America more involved in the IETF, but I also agree that
there is no reason to expect that an IETF meeting there would make any
difference.


From vinayakh@gmail.com  Thu May 23 20:34:37 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE9F21F965B for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:34:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MpxsXTrLGmqa for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:34:32 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3C921F9678 for <ietf@ietf.org>; Thu, 23 May 2013 20:34:32 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id u11so3659333pdi.36 for <ietf@ietf.org>; Thu, 23 May 2013 20:34:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gjKLfQoGqIdYa2wPZlUJA0t4jGQQH+qozZOuA8Y/3FY=; b=fK52gi1cHf07qdGUiM/bHl6mwH6D6CrL6C8/z1SnAOyX/DOAlwkWejcnEXNzO1eJcX DnVCEnCAeKyTE27z/sNEUp0Xn187/Xrf2OYAiESvoPEfN4lb2l0Fil2ArXv31c9xUIVT HpMZ/3F1bG1g0o2EfhTCyNDhiO1bRIRDY2N9ZYZnrptZh9aQQMLJMSnRfQDaKlf+U0Gi qNXztDkVZ9zUuUy2K58lVWWgOjASQ7ngcXr+27GoszGRUNbtzykcPGDydxW9H71LgF16 EBV496y5fGb0/Oy6ZKqE/fkRDiVG7fHXhosjKF96UOvrv+7gUatd/uinEo5eycIF+M/p 5nfw==
MIME-Version: 1.0
X-Received: by 10.66.82.162 with SMTP id j2mr16508540pay.168.1369366471974; Thu, 23 May 2013 20:34:31 -0700 (PDT)
Received: by 10.66.156.234 with HTTP; Thu, 23 May 2013 20:34:31 -0700 (PDT)
In-Reply-To: <519ED3F0.40300@gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com>
Date: Fri, 24 May 2013 09:04:31 +0530
Message-ID: <CAKe6YvPtobuu0DDk_xDQE4KDD7YCyenBjRC+B2WcBAi13FF8EA@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Vinayak Hegde <vinayakh@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=f46d042de633213b7b04dd6e7aa2
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, 24 May 2013 03:34:37 -0000

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

On Fri, May 24, 2013 at 8:14 AM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 5/23/13 6:37 PM, Juliao Braga wrote:
> > Maybe they can not submit drafts, but can
> > contribute to foster the knowledge of those who produce drafts or
> > working as reviewers.
>
> Anyone can submit a draft and anyone can review a draft.  The
> barrier to that sort of participation is extremely low.  So
> the question is why we aren't seeing more drafts, reviews, and
> discussions from people in Central and South America, and
> what we can do as an organization to change that.  I have no
> problem with meeting in Buenos Aires but I do not have reason
> to think that having a meeting there will do anything to
> increase active participation from that region.


English is not a first language in many countries other than the US.
Spanish is the predominant language in Central and South America. There are
several cultural barriers as well such as people being hesitant to ask
questions if they have not met people in real life. Not everything about
the IETF is googlable or RTFM'ed. Maybe several co-located meetings or
having people from the IETF speak at universities and regional ISOC
chapters around the meeting might help. Also showcasing the good work done
by their Latin American peers might help as well.

-- Vinayak

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

<div class=3D"gmail_quote">On Fri, May 24, 2013 at 8:14 AM, Melinda Shore <=
span dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_=
blank">melinda.shore@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">
<div class=3D"im">On 5/23/13 6:37 PM, Juliao Braga wrote:<br>
&gt; Maybe they can not submit drafts, but can<br>
&gt; contribute to foster the knowledge of those who produce drafts or<br>
&gt; working as reviewers.<br>
<br>
</div>Anyone can submit a draft and anyone can review a draft. =A0The<br>
barrier to that sort of participation is extremely low. =A0So<br>
the question is why we aren&#39;t seeing more drafts, reviews, and<br>
discussions from people in Central and South America, and<br>
what we can do as an organization to change that. =A0I have no<br>
problem with meeting in Buenos Aires but I do not have reason<br>
to think that having a meeting there will do anything to<br>
increase active participation from that region.</blockquote><div><br>Englis=
h is not a first language in many countries other than the US. Spanish is t=
he predominant language in Central and South America. There are several cul=
tural barriers as well such as people being hesitant to ask questions if th=
ey have not met people in real life. Not everything about the IETF is googl=
able or RTFM&#39;ed. Maybe several co-located meetings or having people fro=
m the IETF speak at universities and regional ISOC chapters around the meet=
ing might help. Also showcasing the good work done by their Latin American =
peers might help as well.<br>
<br>-- Vinayak<br></div></div>

--f46d042de633213b7b04dd6e7aa2--

From jmamodio@gmail.com  Thu May 23 20:42:42 2013
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 990F621F96EE for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VEWfrR1KgLXM for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 20:42:42 -0700 (PDT)
Received: from mail-vb0-x22b.google.com (mail-vb0-x22b.google.com [IPv6:2607:f8b0:400c:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 977E621F9608 for <ietf@ietf.org>; Thu, 23 May 2013 20:42:41 -0700 (PDT)
Received: by mail-vb0-f43.google.com with SMTP id e12so493536vbg.2 for <ietf@ietf.org>; Thu, 23 May 2013 20:42:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5Gxm/MAffGEGouCe9xy4GpnFIjhuIpnlufUQPvNtwoM=; b=Y7oags4P0dN92BcINuoxfQ/qmCiBQzlxrxCsaNfnCMU5U8JwjRO+gQNCFfraHfSPbE HodGu8rorV3Ae3F/ChpVNZSgGeL+B+Z1K/35oyUO3hlZVICES+TIGhZswJwc+oXlD981 fBNAXRB8NEzG1Uqs0q0M924v2yBhp1E/MhZKAILzLF+GafXvKAfW2uPo4T+jUGSC9xbV +NCjBYwzkGnAaxtNt0BXD/Wytajax8xs8brjn/yYRHE7kxv56KCr2eleqUSedOq5W/za gxKdgC3dcvKnK1A88sR0STxpCsDMFOisFNg3r9HssyIUMztKlfwbuhTEQCV24h9mJQO6 +LSA==
MIME-Version: 1.0
X-Received: by 10.221.5.7 with SMTP id oe7mr7319213vcb.20.1369366961019; Thu, 23 May 2013 20:42:41 -0700 (PDT)
Received: by 10.58.54.115 with HTTP; Thu, 23 May 2013 20:42:40 -0700 (PDT)
In-Reply-To: <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>
Date: Thu, 23 May 2013 22:42:40 -0500
Message-ID: <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Jorge Amodio <jmamodio@gmail.com>
To: David Conrad <drc@virtualized.org>
Content-Type: multipart/alternative; boundary=089e013a0b504762c804dd6e97b0
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: Fri, 24 May 2013 03:42:42 -0000

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

Besides the language there is a big digital divide particularly in South
America.

Many of you know that actively participating in this type of forums
requires a non trivial amount of time (plus skills and knowledge.) In
developed countries some IETF members have a better financial situation or
are being sponsored/supported by an array of organizations or other
activities that help pay the bills.

Researchers, students, engineers, you name it, in other parts of the world
including South America are in a daily battle to subsist, including trying
to survive some stupid regulations that do not help development, like
restrictions or taxes on publications, tools, materials, etc. Often is very
hard to obtain the resources to participate at international meetings like
IETF, and in the particular case of Argentina travel expenses are very high
and flight times are longer and with many stops. This is not something new,
in the early days (when I lived in AR) we were always begging to get
support to be able to participate on meetings or similar activities.

One thing that could help is if some companies like Cisco, Google, Juniper,
etc, with presence in the region start sponsoring some individuals that
have been participating or are interested to participate at IETF so they
can have more time and financial resources.

Taking the IETF meeting to Buenos Aires is not a bad idea, but when the
meeting is over the root problem will still be there.

My .02
Jorge




On Thu, May 23, 2013 at 10:02 PM, David Conrad <drc@virtualized.org> wrote:

> On May 23, 2013, at 7:44 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
> > So the question is why we aren't seeing more drafts, reviews, and
> > discussions from people in Central and South America,
>
> Language?
>
> Regards,
> -drc
>
>
>

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

<div dir=3D"ltr"><br><div style>Besides the language there is a big digital=
 divide particularly in South America.</div><div style><br></div><div style=
>Many of you know that actively participating in this type of forums requir=
es a non trivial amount of time (plus skills and knowledge.) In developed c=
ountries some IETF members have a better financial situation or are being s=
ponsored/supported by an array of organizations or other activities that he=
lp pay the bills.</div>
<div style><br></div><div style>Researchers, students, engineers, you name =
it, in other parts of the world including South America are in a daily batt=
le to subsist, including trying to survive some stupid regulations that do =
not help development, like restrictions or taxes on publications, tools, ma=
terials, etc. Often is very hard to obtain the resources to participate at =
international meetings like IETF, and in the particular case of Argentina t=
ravel expenses are very high and flight times are longer and with many stop=
s. This is not something new, in the early days (when I lived in AR) we wer=
e always begging to get support to be able to participate on meetings or si=
milar activities.</div>
<div style><br></div><div style>One thing that could help is if some compan=
ies like Cisco, Google, Juniper, etc, with presence in the region start spo=
nsoring some individuals that have been participating or are interested to =
participate at IETF so they can have more time and financial resources.</di=
v>
<div style><br></div><div style>Taking the IETF meeting to Buenos Aires is =
not a bad idea, but when the meeting is over the root problem will still be=
 there.</div><div style><br></div><div style>My .02</div><div style>Jorge</=
div>
<div style><br></div><div style>=A0</div></div><div class=3D"gmail_extra"><=
br><br><div class=3D"gmail_quote">On Thu, May 23, 2013 at 10:02 PM, David C=
onrad <span dir=3D"ltr">&lt;<a href=3D"mailto:drc@virtualized.org" target=
=3D"_blank">drc@virtualized.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On May 23, 2013, at 7:44 P=
M, Melinda Shore &lt;<a href=3D"mailto:melinda.shore@gmail.com">melinda.sho=
re@gmail.com</a>&gt; wrote:<br>

&gt; So the question is why we aren&#39;t seeing more drafts, reviews, and<=
br>
&gt; discussions from people in Central and South America,<br>
<br>
</div>Language?<br>
<br>
Regards,<br>
-drc<br>
<br>
<br>
</blockquote></div><br></div>

--089e013a0b504762c804dd6e97b0--

From fred@cisco.com  Thu May 23 21:11:04 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9866821F9690 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.424
X-Spam-Level: 
X-Spam-Status: No, score=-110.424 tagged_above=-999 required=5 tests=[AWL=0.175, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RknM9ArIZ+pa for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:10:59 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8AB21F85B8 for <ietf@ietf.org>; Thu, 23 May 2013 21:10:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=731; q=dns/txt; s=iport; t=1369368659; x=1370578259; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zjJBze8MDnMU3XaSZVALrGnyGMxwK/WoU+DtkEPwMH0=; b=ehos0MIlVegUYjcN53mL3w2RxPOQ/bMrJN9BxdsYncVIbm0FHrnK5fve RsPQp4Ezcd1M1KOKe0y3lnclrVMihG7GwjYbmB8+5VqXIpJB4jXNVf+zm bgcbreP4QI+SE45qbqpu6Tx3JwLvmvwk8tOKSOou0zQE+3n3VNBc2xTlP M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFADXnnlGtJV2d/2dsb2JhbABZgwiDJL80gQsWdIIjAQEBAwF5EAIBCA4KCiQyJQIEDgUIh38GukmOagIxB4JzYQOIZ6AUgw+CJg
X-IronPort-AV: E=Sophos;i="4.87,732,1363132800"; d="scan'208";a="211456727"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 24 May 2013 04:10:58 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4O4Awih028281 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 May 2013 04:10:58 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Thu, 23 May 2013 23:10:51 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV84ZK1H1cwSoGEybXfeog56LNJkTVccAgAAHewCAAA4tAIAAJAeAgAATIACAAAdLAIAADoiAgAAGGACAAE8LAA==
Date: Fri, 24 May 2013 04:10:51 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8F53F9@xmb-rcd-x09.cisco.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
In-Reply-To: <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FD621B75DA1C0E4CB3C296CBD9BDA609@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 04:11:04 -0000

On May 23, 2013, at 4:27 PM, Mark Nottingham <mnot@mnot.net> wrote:

>=20
> On 24/05/2013, at 9:06 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
>> I took the perspective that on our 40th meeting, we could have 1/40 in a=
 place that we had a few faithful participants that was well out of the way=
.
>=20
> Does this imply that, if we have a meeting in South America, I'll need to=
 wait another 10 years before I fly less than 24 hours to get to an IETF me=
eting?
>=20
> Cheers from Melbourne,

That's a question for the IAOC. For the record, when IETF meetings are not =
in North America, it's a similar duration trip for me. You're not alone. Li=
ke Melinda (in Alaska), you're just an extreme case.=

From stpeter@stpeter.im  Thu May 23 21:16:36 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4076E21F955E for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:16:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QdDa9xTjFyZ7 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:16:31 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 13BF621F8FBE for <ietf@ietf.org>; Thu, 23 May 2013 21:16:30 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 11C4441177; Thu, 23 May 2013 22:29:00 -0600 (MDT)
Message-ID: <519EE99D.7000801@stpeter.im>
Date: Thu, 23 May 2013 22:16:29 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
In-Reply-To: <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 04:16:36 -0000

On 5/23/13 5:27 PM, Mark Nottingham wrote:
> 
> On 24/05/2013, at 9:06 AM, Fred Baker (fred) <fred@cisco.com> wrote:
> 
>> I took the perspective that on our 40th meeting, we could have 1/40
>> in a place that we had a few faithful participants that was well
>> out of the way.
> 
> Does this imply that, if we have a meeting in South America, I'll
> need to wait another 10 years before I fly less than 24 hours to get
> to an IETF meeting?

Just in time for you to chair those WG sessions on HTTP/3.0... ;-)

Peter

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



From narten@us.ibm.com  Thu May 23 21:53:15 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD9221F8CA0 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQ+LR8iztVNs for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:53:08 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id F3D5D21F8C1A for <ietf@ietf.org>; Thu, 23 May 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 24 May 2013 00:53:07 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 24 May 2013 00:53:05 -0400
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 1B1E738C801A for <ietf@ietf.org>; Fri, 24 May 2013 00:53:04 -0400 (EDT)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4O4r4PE274558 for <ietf@ietf.org>; Fri, 24 May 2013 00:53:04 -0400
Received: from d01av05.pok.ibm.com (loopback [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4O4r4Sl027389 for <ietf@ietf.org>; Fri, 24 May 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4O4r3G3027386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 24 May 2013 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r4O4r3QO012441 for <ietf@ietf.org>; Fri, 24 May 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r4O4r3XA012410 for ietf@ietf.org; Fri, 24 May 2013 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201305240453.r4O4r3XA012410@rotala.raleigh.ibm.com>
Date: Fri, 24 May 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13052404-7182-0000-0000-000006E68504
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 04:53:15 -0000

Total of 149 messages in the last 7 days.
 
script run at: Fri May 24 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  0.67% |    1 | 28.96% |   458641 | wmwang2001@hotmail.com
 12.75% |   19 |  9.43% |   149309 | john-ietf@jck.com
 12.08% |   18 |  8.28% |   131074 | moore@network-heretics.com
  5.37% |    8 |  4.16% |    65831 | marka@isc.org
  4.70% |    7 |  3.42% |    54157 | jabley@hopcount.ca
  4.03% |    6 |  3.06% |    48437 | sm@resistor.net
  4.03% |    6 |  2.00% |    31668 | randy@psg.com
  3.36% |    5 |  2.46% |    38892 | d3e3e3@gmail.com
  3.36% |    5 |  2.37% |    37601 | joelja@bogus.com
  3.36% |    5 |  2.32% |    36759 | brian.e.carpenter@gmail.com
  3.36% |    5 |  2.21% |    34948 | ynir@checkpoint.com
  3.36% |    5 |  1.85% |    29302 | paul.hoffman@vpnc.org
  2.01% |    3 |  2.50% |    39573 | andy@yumaworks.com
  2.01% |    3 |  1.24% |    19594 | melinda.shore@gmail.com
  2.01% |    3 |  1.18% |    18718 | dhc@dcrocker.net
  1.34% |    2 |  1.05% |    16594 | bmanning@isi.edu
  1.34% |    2 |  0.99% |    15622 | ocl@gih.com
  1.34% |    2 |  0.94% |    14898 | juliao@braga.eti.br
  1.34% |    2 |  0.88% |    13975 | jari.arkko@piuha.net
  1.34% |    2 |  0.86% |    13649 | sra@hactrn.net
  1.34% |    2 |  0.86% |    13635 | arturo.servin@gmail.com
  1.34% |    2 |  0.80% |    12725 | worley@ariadne.com
  1.34% |    2 |  0.74% |    11717 | abdussalambaryun@gmail.com
  1.34% |    2 |  0.73% |    11526 | johnl@taugh.com
  0.67% |    1 |  1.10% |    17501 | spromano@unina.it
  0.67% |    1 |  0.97% |    15328 | steve@shinkuro.com
  0.67% |    1 |  0.80% |    12736 | ogawa.kentaro@lab.ntt.co.jp
  0.67% |    1 |  0.75% |    11936 | agmalis@gmail.com
  0.67% |    1 |  0.65% |    10346 | jmamodio@gmail.com
  0.67% |    1 |  0.64% |    10099 | kathleen.moriarty@emc.com
  0.67% |    1 |  0.60% |     9569 | ogud@ogud.com
  0.67% |    1 |  0.60% |     9457 | fred@cisco.com
  0.67% |    1 |  0.59% |     9378 | narten@us.ibm.com
  0.67% |    1 |  0.57% |     9040 | kotecha_kamal@yahoo.com
  0.67% |    1 |  0.56% |     8946 | vinayakh@gmail.com
  0.67% |    1 |  0.54% |     8557 | dmm@1-4-5.net
  0.67% |    1 |  0.52% |     8301 | daedulus@btconnect.com
  0.67% |    1 |  0.51% |     8057 | sarikaya2012@gmail.com
  0.67% |    1 |  0.49% |     7828 | ben@nostrum.com
  0.67% |    1 |  0.48% |     7548 | jcurran@istaff.org
  0.67% |    1 |  0.45% |     7121 | stephen.farrell@cs.tcd.ie
  0.67% |    1 |  0.45% |     7080 | akatlas@gmail.com
  0.67% |    1 |  0.44% |     7018 | brian@innovationslab.net
  0.67% |    1 |  0.44% |     7005 | mansaxel@besserwisser.org
  0.67% |    1 |  0.42% |     6688 | bob.hinden@gmail.com
  0.67% |    1 |  0.42% |     6602 | superuser@gmail.com
  0.67% |    1 |  0.41% |     6415 | ray.bellis@nominet.org.uk
  0.67% |    1 |  0.40% |     6405 | barryleiba@computer.org
  0.67% |    1 |  0.40% |     6355 | dougb@dougbarton.us
  0.67% |    1 |  0.38% |     6072 | jmh@joelhalpern.com
  0.67% |    1 |  0.37% |     5937 | hartmans-ietf@mit.edu
  0.67% |    1 |  0.36% |     5631 | l.wood@surrey.ac.uk
  0.67% |    1 |  0.35% |     5584 | bortzmeyer@nic.fr
  0.67% |    1 |  0.35% |     5558 | mnot@mnot.net
  0.67% |    1 |  0.35% |     5489 | ajs@anvilwalrusden.com
  0.67% |    1 |  0.34% |     5388 | drc@virtualized.org
--------+------+--------+----------+------------------------
100.00% |  149 |100.00% |  1583820 | Total


From mnot@mnot.net  Thu May 23 21:55:57 2013
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 5B47121F9545 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.295
X-Spam-Level: 
X-Spam-Status: No, score=-99.295 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_ILLEGAL_IP=1.908, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFzUU4DmxXxh for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 21:55:51 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 9390621F9539 for <ietf@ietf.org>; Thu, 23 May 2013 21:55:51 -0700 (PDT)
Received: from [10.222.121.133] (unknown [1.157.74.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id B3A3E509B6; Fri, 24 May 2013 00:55:50 -0400 (EDT)
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <8C48B86A895913448548E6D15DA7553B8F53F9@xmb-rcd-x09.cisco.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <8C48B86A895913448548E6D15DA7553B8F53F9@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <BE5A96BD-9E55-4A9F-BE99-FCD615756B55@mnot.net>
X-Mailer: iPhone Mail (10B329)
From: Mark Nottingham <mnot@mnot.net>
Subject: Re: IETF Meeting in South America
Date: Fri, 24 May 2013 14:55:46 +1000
To: "Fred Baker (fred)" <fred@cisco.com>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 04:55:57 -0000

I weep for you - those NA meetings being=20

Sent from my iPhone

On 24/05/2013, at 2:10 PM, "Fred Baker (fred)" <fred@cisco.com> wrote:

>=20
> On May 23, 2013, at 4:27 PM, Mark Nottingham <mnot@mnot.net> wrote:
>=20
>>=20
>> On 24/05/2013, at 9:06 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>>=20
>>> I took the perspective that on our 40th meeting, we could have 1/40 in a=
 place that we had a few faithful participants that was well out of the way.=

>>=20
>> Does this imply that, if we have a meeting in South America, I'll need to=
 wait another 10 years before I fly less than 24 hours to get to an IETF mee=
ting?
>>=20
>> Cheers from Melbourne,
>=20
> That's a question for the IAOC. For the record, when IETF meetings are not=
 in North America, it's a similar duration trip for me. You're not alone. Li=
ke Melinda (in Alaska), you're just an extreme case.

From swmike@swm.pp.se  Thu May 23 22:04:49 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B02121F8CEC for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 22:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5jnDqdmu0GRi for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 22:04:48 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id A12E721F8956 for <ietf@ietf.org>; Thu, 23 May 2013 22:04:48 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C84A29C; Fri, 24 May 2013 07:04:46 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id BD6A19A for <ietf@ietf.org>; Fri, 24 May 2013 07:04:46 +0200 (CEST)
Date: Fri, 24 May 2013 07:04:46 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
In-Reply-To: <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1305240702030.24367@uplift.swm.pp.se>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org> <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
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: Fri, 24 May 2013 05:04:49 -0000

On Thu, 23 May 2013, Jorge Amodio wrote:

> One thing that could help is if some companies like Cisco, Google, 
> Juniper, etc, with presence in the region start sponsoring some 
> individuals that have been participating or are interested to 
> participate at IETF so they can have more time and financial resources.

My take on this is that it would be a good start if someone (not limited 
to the list above, ICANN for instance?) could do more "marketing" for 
IETF, perhaps identifying universities with courses that cater towards 
network engineering, making sure they know how Internet standards are 
developed and how to participate.

Where is a good "executive summary" to give to upper management, outlining 
why they should dedicate resources towards participating in the IETF?

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

From fred@cisco.com  Thu May 23 22:17:52 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B1921F9670 for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 22:17:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WB7XCj2T69VL for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 22:17:46 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 4FABE21F9648 for <ietf@ietf.org>; Thu, 23 May 2013 22:17:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1394; q=dns/txt; s=iport; t=1369372666; x=1370582266; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=yfyb7rC/YVaXZbofUDfV+gMv1WZcoMOPiZ7sxdTifqQ=; b=ZctCyUfrOyUHeXihbQ06Ebryp+5pdSJBEPxiBqNDH3P7V6QhxjjULS3o UnTh3Pfa6NbcNPHMKnyp7DeLZ2HDaxcx18zNj6KiwEte9JJvvnR3whjZm 58+SlYHVtxvdMotln6YUIpUXr85JUmCuFZeQIO2I0LpZFvrKt2m4n4w+U I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiMFAL/2nlGtJXG8/2dsb2JhbABZgwjCWIEHFnSCIwEBAQMBOjUKBQsCAQgOCgoUEDIlAgQOBQiHfwa6RI1lgQUCMQeCc2EDqHuDD4FoPg
X-IronPort-AV: E=Sophos;i="4.87,732,1363132800"; d="scan'208";a="214433841"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-7.cisco.com with ESMTP; 24 May 2013 05:17:46 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r4O5HjQn002662 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 May 2013 05:17:45 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Fri, 24 May 2013 00:17:45 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV84ZK1H1cwSoGEybXfeog56LNJkTVccAgAAHewCAAA4tAIAAJAeAgAATIACAAAdLAIAADoiAgAAGGACAACN3AIAAAy0AgAAObICAAAG7AIAABUmAgAALGwCAABbwAIAAA6AA
Date: Fri, 24 May 2013 05:17:44 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B8F550F@xmb-rcd-x09.cisco.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org> <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com> <alpine.DEB.2.00.1305240702030.24367@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.00.1305240702030.24367@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <633C5654093E214DA1DB2BF84C11A63D@emea.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: Fri, 24 May 2013 05:17:52 -0000

On May 23, 2013, at 10:04 PM, Mikael Abrahamsson <swmike@swm.pp.se>
 wrote:

> On Thu, 23 May 2013, Jorge Amodio wrote:
>=20
>> One thing that could help is if some companies like Cisco, Google, Junip=
er, etc, with presence in the region start sponsoring some individuals that=
 have been participating or are interested to participate at IETF so they c=
an have more time and financial resources.
>=20
> My take on this is that it would be a good start if someone (not limited =
to the list above, ICANN for instance?) could do more "marketing" for IETF,=
 perhaps identifying universities with courses that cater towards network e=
ngineering, making sure they know how Internet standards are developed and =
how to participate.
>=20
> Where is a good "executive summary" to give to upper management, outlinin=
g why they should dedicate resources towards participating in the IETF?

I think some of them might tell you they already do. If nothing else, they =
contribute to ISOC, which in turn sends Fellows. They donate equipment, hos=
t meetings, and oh-by-the-way send scads of people. And they contribute to =
ISOC in other ways too.

BTW, we happen to be working with a university that I shall not name (the M=
OU isn't signed off yet) located in a southern hemisphere continent on a un=
iversity course in networking or network engineering or some such.=

From sm@resistor.net  Thu May 23 23:07:03 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4210F21F93DA for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 23:07:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bZLVPDPJKLCy for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 23:07:02 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C1421F93D2 for <ietf@ietf.org>; Thu, 23 May 2013 23:07:02 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4O66oOU014211; Thu, 23 May 2013 23:06:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369375616; bh=l94CW2RCwwia0Oc7kew5MiFwy15wXWdx/uVOS5g83cQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3ydxubpwmGHNM1NxwSOScvL9cA/0dGI8zIIm0XgKq4NQLwPexoXFmN11AnbWQ1eFJ knISSa7bb+jnvTe02TOpZ0Z76jStYou0GgutG8gFdeodFnpkJQvXZBn88yxjvadY2p oIMderF5bd6yF7pl1/G3kFo7H/Fqb2OfITupjHkI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369375616; i=@resistor.net; bh=l94CW2RCwwia0Oc7kew5MiFwy15wXWdx/uVOS5g83cQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EhLY7XEmbW+HR9cM4LeP5AeownGHmEe5P0rk4n+lEek0yjuCCjVGMXlPtDBOjr3J8 PgCn3b6iUYRFAar1vlX0llpF67YfODiV/FbwchFzbIG+BHKd+mP6VETQbLapi3vLyW AjN/PQ9k+S+L7lIJiHWZ2bCFYj0+G7gA2wVNBTQI=
Message-Id: <6.2.5.6.2.20130523223926.0ca59d30@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 23 May 2013 23:05:46 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: IETF Meeting in South America
In-Reply-To: <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.g mail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org> <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: politicas@lacnic.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, 24 May 2013 06:07:03 -0000

At 20:42 23-05-2013, Jorge Amodio wrote:
>Taking the IETF meeting to Buenos Aires is not a bad idea, but when 
>the meeting is over the root problem will still be there.

Jari Arkko is the Chair of the IETF.  He asked the following 
questions ( http://www.ietf.org/mail-archive/web/ietf/current/msg79470.html ):

   "Just meeting in some place does not bring too many new participants,
    at least not in a lasting manner.  But combined with some other actions,
    this may be possible.  Are there specific companies or research teams that
    we could reach out to, and who might want to be involved in the IETF?

    Are there local events where where it would be useful to have someone
    from the IETF give a talk?

    Are there specific IETF or IRTF efforts where we could get more people
    from South America involved?

    Should the ISOC fellows program target something different than it has
    so far, or be scaled up? Other ideas?"

What he is saying is that he does not plan to come to Buenos Aires 
for an IETF meeting, have a nice time and then forget about South 
America.  He would like to do more than that.  He asked the questions 
mentioned to learn more about what the IETF can do directly or by 
discussing with other organizations to get more people from South 
America to participate in the IETF.

Juliao Braga was the only person from South America to comment about 
the above.  It is not possible to identify what actions the IETF can 
take if people from South America do not respond to the questions.

Regards,
-sm 


From jari.arkko@piuha.net  Thu May 23 23:24:35 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA7021F968F for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 23:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdIlK4e-f6WI for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 23:24:24 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B929E21F9601 for <ietf@ietf.org>; Thu, 23 May 2013 23:24:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 15FFD2CC53; Fri, 24 May 2013 09:24:14 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaRSQ8zP6NG6; Fri, 24 May 2013 09:24:13 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 64CD82CC48; Fri, 24 May 2013 09:24:13 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAKe6YvPtobuu0DDk_xDQE4KDD7YCyenBjRC+B2WcBAi13FF8EA@mail.gmail.com>
Date: Fri, 24 May 2013 09:24:13 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A36A51AA-C3DB-4A3E-99C2-C101F7AAD3F3@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <CAKe6YvPtobuu0DDk_xDQE4KDD7YCyenBjRC+B2WcBAi13FF8EA@mail.gmail.com>
To: Vinayak Hegde <vinayakh@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 24 May 2013 06:24:35 -0000

Vinayak,

> Maybe several co-located meetings or having people from the IETF speak =
at universities and regional ISOC chapters around the meeting might =
help. Also showcasing the good work done by their Latin American peers =
might help as well.

Good ideas. Thanks.

Jari


From adrian@olddog.co.uk  Fri May 24 03:07:28 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D961E21F96F6 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 03:07:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level: 
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[AWL=0.254,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8YZTu8o+51uy for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 03:07:23 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id B9D6F21F8D31 for <ietf@ietf.org>; Fri, 24 May 2013 03:07:22 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4OA7LfW020147 for <ietf@ietf.org>; Fri, 24 May 2013 11:07:21 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4OA7KeN020114 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 24 May 2013 11:07:20 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security	Threats for NHDP) to Informational RFC
Date: Fri, 24 May 2013 11:07:19 +0100
Message-ID: <059801ce5866$7a5b10e0$6f1132a0$@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: Ac5YZcx9FcHb0uN/RtOZ6sfF17vvjA==
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: Fri, 24 May 2013 10:07:29 -0000

In the interests of moving the document forward more briskly, here are my
comments as responsible AD.

Thanks,
Adrian

---

I know it is not the intent of this document to propose solutions or
mitigations to any of the threats described. However, I think two things
would be useful:

1. Please add a statement of exactly this point to the Abstract and to
   the end of the Introduction.

2. Please consider adding a short section that may drive new work by
   suggesting which threats need to be addressed in new protocol work,
   which in deployment, and which by applications.

---

The assumption stated in the Introduction...
   This document is based on the assumption that no additional security
   mechanism (such as IPsec) is used in the IP layer.
...is perfectly fine. You might add a note to explain why this is a 
reasonable assumption (i.e., it is particularly hard to configure
security associations in this type of network) and you might also add a
note about whether none, some, or all of the threats would go away if
this problem could be resolved.

> -----Original Message-----
> From: manet-bounces@ietf.org [mailto:manet-bounces@ietf.org] On Behalf Of
> The IESG
> Sent: 23 May 2013 23:23
> To: IETF-Announce
> Cc: manet@ietf.org
> Subject: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt>
(Security
> Threats for NHDP) to Informational RFC
> 
> 
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'Security Threats for NHDP'
>   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-06. 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.


From aservin@lacnic.net  Fri May 24 07:11:04 2013
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 C57B821F8A54 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EEYG4UySqR4L for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:11:04 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 24A5521F8A14 for <ietf@ietf.org>; Fri, 24 May 2013 07:11:02 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2001:13c7:7001:7000:40a6:320e:562:bfe3]) by mail.lacnic.net.uy (Postfix) with ESMTP id 5BA8E308474 for <ietf@ietf.org>; Fri, 24 May 2013 11:10:46 -0300 (UYT)
Message-ID: <519F74F4.8010904@lacnic.net>
Date: Fri, 24 May 2013 11:11:00 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org> <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com> <6.2.5.6.2.20130523223926.0ca59d30@resistor.net>
In-Reply-To: <6.2.5.6.2.20130523223926.0ca59d30@resistor.net>
X-Enigmail-Version: 1.5.1
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 14:11:04 -0000

On 5/24/13 3:05 AM, SM wrote:
>   "Just meeting in some place does not bring too many new participants,
>    at least not in a lasting manner.  But combined with some other actions,
>    this may be possible.  Are there specific companies or research teams
> that
>    we could reach out to, and who might want to be involved in the IETF?
> 
>    Are there local events where where it would be useful to have someone
>    from the IETF give a talk?

	There are regional events such as LACNOG (once a year), LACNIC (twice a
year), LACTLD (one large meeting a year and some other workshops during
the year), CLARA (the academic network has different events to different
people -academic, CIO/CTOs, networks tech people), CITEL (goverments),
Caribbean events (CARIBNOG, CANTO, LACNIC Caribbean), etc.

	If needed, I could get places, dates and contact information of the
organizers.

> 
>    Are there specific IETF or IRTF efforts where we could get more people
>    from South America involved?

	Initially talks during these events would work. They do not have to be
made by people traveling from other regions, in some cases local or
regional people could help.

	Also I would add that being there and making the effort of traveling it
would be good to organize some talks in local universities.

> 
>    Should the ISOC fellows program target something different than it has
>    so far, or be scaled up? Other ideas?"

	ISOC fellows have done a great job, now it may be time to empower the
program where we could foster new IETF participants (not only bring them
to the IETF) by encouraging/train/prepare them to participate in the
mailing lists by reviewing and writing drafts.

Regards,
as

	


From mcr@sandelman.ca  Fri May 24 07:13:21 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5854721F8A7B for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJWokUeFuIiD for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:13:16 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 0D3E421F8A14 for <ietf@ietf.org>; Fri, 24 May 2013 07:13:16 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 53B0920171 for <ietf@ietf.org>; Fri, 24 May 2013 10:25:29 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id B5CAB63A7E; Fri, 24 May 2013 10:12:31 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A047F63A7C for <ietf@ietf.org>; Fri, 24 May 2013 10:12:31 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
In-Reply-To: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 24 May 2013 10:12:31 -0400
Message-ID: <16454.1369404751@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 14:13:21 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "The" =3D=3D The IAOC <bob.hinden@gmail.com> writes:
    The> The venues are in Buenos Aires.  They meet our requirements for th=
e meeting
    The> space, networking, nearby restaurants and bars, hotel room rates i=
n the mid $200
    The> dollar range, nearby alternate hotels at a broad range of prices, =
nice area in the
    The> city, safe, direct international flights, and accessible visas.  T=
he IAOC thinks we
    The> could have a successful IETF meeting in Buenos Aires and that atte=
ndees would
    The> like the venues.

My question is about whether we would be there during the "peak" season,
and when exactly is that season?

I priced flights for me in July, November and March (2014).
It seems that most flights go through Santiago or Sao Paulo, one went
through Atlanta.  The lowest cost flight for me is similiar to travel to
Europe not in the summer,  but the price rises quite quickly to the $4K
range.  The worse rise seems to be March, but that was also the furthest
in the future.

    The> Things to consider are that it will be a long trip for the majorit=
y of IETFers and the
    The> air fares are more expensive (about 10% to 20% higher than average=
), though
    The> restaurants are less expensive.  This would be a case where most I=
ETFers would
    The> bear more travel pain and expense.=20=20

What are the hotel costs?=20=20=20
(I fund my own attendance)

=2D-=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09


--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUZ91T4qHRg3pndX9AQIW3QQAsMIYKKJeW49xv11o5+5SS04Zk7wXyfhy
Mt8Yq0QbT7B3DFyAbpgCAF+EYKKsB31zZK2DMWgo+aeTacAFljKGtHcesXxWFcvV
gsbUqOoIsTjRlZ1pPkFFj7zUhLgysDaU8ECfhONualF555Z6/WVwBS/QtTouw0FX
olTX7IG9nhc=
=sF7D
-----END PGP SIGNATURE-----
--=-=-=--

From aservin@lacnic.net  Fri May 24 07:36:47 2013
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 A65B621F9418 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHTUvUqqaZkm for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:36:47 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0E26321F89B0 for <ietf@ietf.org>; Fri, 24 May 2013 07:36:46 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2001:13c7:7001:7000:40a6:320e:562:bfe3]) by mail.lacnic.net.uy (Postfix) with ESMTP id DEDFA308424 for <ietf@ietf.org>; Fri, 24 May 2013 11:36:23 -0300 (UYT)
Message-ID: <519F7AF6.9050602@lacnic.net>
Date: Fri, 24 May 2013 11:36:38 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca>
In-Reply-To: <16454.1369404751@sandelman.ca>
X-Enigmail-Version: 1.5.1
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 14:36:47 -0000

	Where are you flying from?

	There are direct flights from Miami, Dallas, Toronto, Washington and
other hubs to Buenos Aires.

	
Regards,
as

On 5/24/13 11:12 AM, Michael Richardson wrote:
> 
>>>>>> "The" == The IAOC <bob.hinden@gmail.com> writes:
> The> The venues are in Buenos Aires.  They meet our requirements
> for the meeting The> space, networking, nearby restaurants and
> bars, hotel room rates in the mid $200 The> dollar range, nearby
> alternate hotels at a broad range of prices, nice area in the The>
> city, safe, direct international flights, and accessible visas.
> The IAOC thinks we The> could have a successful IETF meeting in
> Buenos Aires and that attendees would The> like the venues.
> 
> My question is about whether we would be there during the "peak"
> season, and when exactly is that season?
> 
> I priced flights for me in July, November and March (2014). It
> seems that most flights go through Santiago or Sao Paulo, one went 
> through Atlanta.  The lowest cost flight for me is similiar to
> travel to Europe not in the summer,  but the price rises quite
> quickly to the $4K range.  The worse rise seems to be March, but
> that was also the furthest in the future.
> 
> The> Things to consider are that it will be a long trip for the
> majority of IETFers and the The> air fares are more expensive
> (about 10% to 20% higher than average), though The> restaurants are
> less expensive.  This would be a case where most IETFers would The>
> bear more travel pain and expense.
> 
> What are the hotel costs? (I fund my own attendance)
> 

From juliao@braga.eti.br  Fri May 24 07:52:48 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48B7D21F91C4 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ug1Bzo8z-fpC for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:52:30 -0700 (PDT)
Received: from mail-vb0-x230.google.com (mail-vb0-x230.google.com [IPv6:2607:f8b0:400c:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 8A73921F911B for <ietf@ietf.org>; Fri, 24 May 2013 07:52:29 -0700 (PDT)
Received: by mail-vb0-f48.google.com with SMTP id w8so2195854vbf.7 for <ietf@ietf.org>; Fri, 24 May 2013 07:52:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=bghobqg+2++gWn3W8Wh5vd5iS07IvJnEXkwqBb2p1tI=; b=MVdl/IKbPgVc7ZnvuynZpU0jh7N7d/Gay93Tn0nWztQYdkELfvayKDltJsgQriiUfu WvKEuH4Con8C6NYGjrUVop4ci3zpVGJ+s0f1A8XWOYR2/lUc1DRsl1BgMPDbKLFNdFS9 xP9CveGOo91k95gZQUi553EfYKfYNcVdEyYc/kL+Y7WRPh2Zg4iBlhg52Gu2j4Ato7ik QnlMZtOA6fSoYYFxZ0u7EUSVJIgGGaODwYBqU/aRhmA4C+UJdrud8PaH8sy8R+awSa2H Sg/TnDz+vj8HGi7ti+LrD+Mr1D++5tCJDziQ1A/KUzgprVEjxNG+4UxbPnUaIYSAJkql 967Q==
X-Received: by 10.52.65.144 with SMTP id x16mr7434241vds.123.1369407148756; Fri, 24 May 2013 07:52:28 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id s14sm9043511vdg.6.2013.05.24.07.52.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 07:52:27 -0700 (PDT)
Message-ID: <519F7EA7.2060705@braga.eti.br>
Date: Fri, 24 May 2013 11:52:23 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org, j@braga.net.br
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org> <CAMzo+1Z_w3=Pa9FuzfeTbgQiUTU+zOZqSXNr0LyOqgCNvocNwQ@mail.gmail.com> <6.2.5.6.2.20130523223926.0ca59d30@resistor.net> <519F74F4.8010904@lacnic.net>
In-Reply-To: <519F74F4.8010904@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQn29OxlrL+myQpNL94TX6tBpDew+lF1VPBLf5Wm8CO9wq9AeNWTtPOQO1pHU1/UhZADBjpQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 14:52:53 -0000

Also, there are several events in each country that can be used to
disseminate the actions of IETF. In Brazil, for example, the events
linked to universities and research centers are promoted by the
Brazilian Computer Society (a lot of). Other less formal events but with
participation of people interested in the IETF can be used also, but
should be advised of this because the informal nature makes them fairly
closed.

Immediate action could be, perhaps, the availability of liasons in each
country, evaluating assumptions and indicating alternatives available to
the IAOC or another sector of the IETF. Such liasons should be grouped
regionally leading permanent brainstorm on these issues. Subsequently
divulge the results.

I agree with Vinayak and Melinda concerns.

Julião

Em 24/05/2013 11:11, Arturo Servin escreveu:
> 	There are regional events such as LACNOG (once a year), LACNIC (twice a
> year), LACTLD (one large meeting a year and some other workshops during
> the year), CLARA (the academic network has different events to different
> people -academic, CIO/CTOs, networks tech people), CITEL (goverments),
> Caribbean events (CARIBNOG, CANTO, LACNIC Caribbean), etc.
> 
> 	If needed, I could get places, dates and contact information of the
> organizers.
> 
>> > 
>> >    Are there specific IETF or IRTF efforts where we could get more people
>> >    from South America involved?
> 	Initially talks during these events would work. They do not have to be
> made by people traveling from other regions, in some cases local or
> regional people could help.

From alejandroacostaalamo@gmail.com  Fri May 24 07:57:34 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44CE121F9060 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OVx57Bfu-CmG for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:57:29 -0700 (PDT)
Received: from mail-vc0-f171.google.com (mail-vc0-f171.google.com [209.85.220.171]) by ietfa.amsl.com (Postfix) with ESMTP id 1C63621F8E99 for <ietf@ietf.org>; Fri, 24 May 2013 07:57:29 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id m17so3181815vca.2 for <ietf@ietf.org>; Fri, 24 May 2013 07:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AJbVmMwSyIe7S79dITD0XAgpdI1ko80PCHsS+idXtCw=; b=Kd1Mx410uRs/USJY/9mGzOSI/0boqGlTMRGU0uc72He0YybdJPtOpue74IQK4PlOtd y0Paa0HpgshtP7jqfhd2Nth0Lewc14MSwBwlIGhhZwjPgyxGlv2y+IDOULic+HvixtLu 47YSr7uuj/Kh5JOdV9wuVX6B6MHHy5Fn4staq2WllkcKLMlu9kuXFMPOzsQoM/GURLLg 1F3lXUh9ucqwGScd/od0xl08WbfWhJ0LXSA2RW4wNWWuMV29Za3HXjlWZK6D435LyhDs J1uqIR0IiJwsg5CJaWASNxKZ5aLSLFG5/X/EGvj2dMFxjTSa0sOCcHLvsdGwVD3Grwi6 xRgg==
MIME-Version: 1.0
X-Received: by 10.52.21.227 with SMTP id y3mr4555735vde.49.1369407448512; Fri, 24 May 2013 07:57:28 -0700 (PDT)
Received: by 10.52.76.161 with HTTP; Fri, 24 May 2013 07:57:28 -0700 (PDT)
In-Reply-To: <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net>
Date: Fri, 24 May 2013 10:27:28 -0430
Message-ID: <CAOmxzdzBhA9HdswxDCf59=QyuP-N6GjvPbtfOhPuGgdLtuA=NA@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: The IAOC <bob.hinden@gmail.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 14:57:34 -0000

Hello,
  Just a small comment:

On 5/23/13, Jari Arkko <jari.arkko@piuha.net> wrote:
>
> For what it is worth, I wanted to provide my perspective on this. I of
> course believe that it is important that the IETF reaches out to an even

{...}

> Just meeting in some place does not bring too many new participants, at
> least not in a lasting manner. But combined with some other actions, this
> may be possible.

 I couldn't agree more.

> Are there specific companies or research teams that we
> could reach out to, and who might want to be involved in the IETF?

I believe it's a great start. I think most Latam countries have
certain research entities which involve networking.


> Are there
> local events where where it would be useful to have someone from the IETF
> give a talk?

Plenty of events!.. But I also have to say that ISOC and IETFers have
been very supportive. It's common to have IETFers in our events. This
is always great.

Part of the LATAM participant increase you have seen since IETF82 is
some effort from ISOC to promote the IETF in Latam.

> Are there specific IETF or IRTF efforts where we could get more
> people from South America involved? Should the ISOC fellows program target
> something different than it has so far,

  The ISOC fellow program is terrific, what we can do it to support it :)

> or be scaled up? Other ideas?

  One idea that I have always had is to use local ISOC chapter to
follow certain WGs remotely during an IETF event.  I mean, a bunch of
people join in a certain place and get remote participation to the
event. This is a long shot but the idea is to do it regularly and in
many ISOC chapters (sorry if it's been done but AFAIK no)

>
> Jari
>
> P.S. By coincidence, I happened to visit Buenos Aires last year, and found
> it to be a fun city. I felt safe and despite not speaking the local language
> I was able to talk to the friendly locals, order food, access the network,
> acquire a SIM card (albeit with some bureaucratic and technical
> difficulties, but I think I can still dig up the MNC numbers that were
> needed to configure the phone correctly :-), use the airports, rent a car,
> and find a Finnish sauna. I think the city offers all the essential
> ingredients for life :-)
>
>


-- 
=====
^A.......o$

From sm@resistor.net  Fri May 24 07:58:16 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB80021F93FB for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pA59hilckQq1 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 07:58:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 988DA21F8E99 for <ietf@ietf.org>; Fri, 24 May 2013 07:58:11 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4OEvkjp014232; Fri, 24 May 2013 07:57:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369407472; bh=3BVUY9Hps89G/POhPg5DyHPFcHZY97wOLMm+ANLjZuw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hIPqSKJGT2NTyvJ6y3N1AABfYANQXzMNcnRIHGZZnS/IkpMJxKcGkfxxpLwFOvLlp nu1/EO6U8j7AS+hK121DO82Lm2A+J0L425kvGIa3X5xGS+gfLqFwbyx8j147X04pNp 49AqWHh7OXMnCFyPOSFcQTzNOCwOB/m/ZEuklLbo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369407472; i=@resistor.net; bh=3BVUY9Hps89G/POhPg5DyHPFcHZY97wOLMm+ANLjZuw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eSpNEh/ORwfiXcBGr8D/ChWEn51xaoU/oWLBE/ofEs4A5IyVHLPLRNrdsCxsgH+C/ 5P+qC/ezsuQ1apHuKO2ZCmF5leqtyhtAeJofKA5d10KfSgTKs7eKxeCk+a924NBvfN +LkwA7FR7OEOjfPiLzotuvlvSigg/i0G35GLBX4M=
Message-Id: <6.2.5.6.2.20130524065008.0dbec598@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 May 2013 07:43:42 -0700
To: Juliao Braga <juliao@braga.eti.br>
From: SM <sm@resistor.net>
Subject: Re: IETF Meeting in South America
In-Reply-To: <519EC3BA.9010908@braga.eti.br>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: j@braga.net.br, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 14:58:17 -0000

Hi Juliao,
At 18:34 23-05-2013, Juliao Braga wrote:
>I stare at the map of where the IETF meetings occurred
>(http://ws.org.br/index.php/IETF_Meetings) and wondering if the fact of
>bringing some of the meetings to below the Equator could lead to
>increase people participation.

That's a nice map.  It highlights the division between the northern 
and southern hemispheres.

>The answer is always negative. Will not increase participation of more
>people.
>
>Fellowships will help? Certainly not. Resources are finite.

Agreed.

>How then can we increase participation in meetings of the IETF? My
>answer to the question may seem strange: increasing the number of annual
>meetings.

The answer did sound strange at first.  I think that your answer 
might be appropriate for a different question.

At 19:37 23-05-2013, Juliao Braga wrote:
>I think we will have new challenges to be defined. New opportunities for
>change that can stimulate, for example, the coming of researchers
>immersed in universities and / or research centers, not yet
>participating in the IETF. Maybe they can not submit drafts, but can
>contribute to foster the knowledge of those who produce drafts or
>working as reviewers. Regarding the participation in discussions of the
>mailing lists, I think that they might be involved with reasonable
>intensity, ideas, and knowledge.

Agreed.

>Perhaps the IETF should and can change (not where it has always been a
>success) to capture new people.

It would take a huge effort to do the above.  A person trying to do 
it will make a lot of enemies.

Do you know people in universities or research centers in South 
America who might be interested in contributing their knowledge?  If 
so, could you ask them to comment on ericas?

Regards,
-sm 


From moreiras@nic.br  Thu May 23 14:22:38 2013
Return-Path: <moreiras@nic.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4F821F968E for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 14:22:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlUJACy9FxkN for <ietf@ietfa.amsl.com>; Thu, 23 May 2013 14:22:28 -0700 (PDT)
Received: from mail.nic.br (mail.nic.br [IPv6:2001:12ff:0:4::5]) by ietfa.amsl.com (Postfix) with ESMTP id 70F7521F9827 for <ietf@ietf.org>; Thu, 23 May 2013 13:38:30 -0700 (PDT)
Received: from sarierom-2.local (unknown [IPv6:2801:b6:200:30:d9c2:10ed:4b65:f42b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nic.br (Postfix) with ESMTPSA id 3F2B12080241 for <ietf@ietf.org>; Thu, 23 May 2013 17:38:29 -0300 (BRT)
Message-ID: <519E7E44.1050309@nic.br>
Date: Thu, 23 May 2013 17:38:28 -0300
From: "Antonio M. Moreiras" <moreiras@nic.br>
Organization: NIC.br
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <519E61BF.4030408@nic.br>
In-Reply-To: <519E61BF.4030408@nic.br>
X-Enigmail-Version: 1.5.1
X-Forwarded-Message-Id: <519E61BF.4030408@nic.br>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 24 May 2013 08:12:04 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 May 2013 21:22:38 -0000

Hi. That's great news!

I think that a meeting in Buenos Aires will foster the participation in
our region. Including Brazilian participation. Probably it will be a
great opportunity for a lot of people to participate for the first time,
and come to know the process, and become involved.

It is important to note that sometimes it's not so easy for us
Brazilians, and Latin-americans, in general, to get visas for other
countries. For USA, for instance. And it is true that , in general, it
is easy to get a visa for Argentina.

Regards,
Antonio M. Moreiras.

>>>     -------- Original Message --------
>>>     Subject: IETF Meeting in South America
>>>     Date: Thu, 23 May 2013 08:54:12 -0700
>>>     From: The IAOC <bob.hinden@gmail.com <mailto:bob.hinden@gmail.com>>
>>>     To: IETF Announcement List <ietf-announce@ietf.org
>>>     <mailto:ietf-announce@ietf.org>>
>>>     CC: ietf@ietf.org <mailto:ietf@ietf.org>
>>>
>>>     As you may know the IAOC has been investigating the feasibility of
>>>     having an IETF
>>>     meeting in South America.  There was a site visit to South
>>>     America last
>>>     February.
>>>     We have found two venues that we believe will support a
>>>     successful IETF
>>>     meeting
>>>     and we would like to get feedback from the community.
>>>
>>>     The venues are in Buenos Aires.  They meet our requirements for
>>>     the meeting
>>>     space, networking, nearby restaurants and bars, hotel room rates
>>>     in the
>>>     mid $200
>>>     dollar range, nearby alternate hotels at a broad range of prices,
>>>     nice
>>>     area in the
>>>     city, safe, direct international flights, and accessible visas.  The
>>>     IAOC thinks we
>>>     could have a successful IETF meeting in Buenos Aires and that
>>>     attendees
>>>     would
>>>     like the venues.
>>>
>>>     There has been a consistent level of IETF participation from
>>>     South and
>>>     Central
>>>     America, and it has been growing since IETF82.  The data on this is
>>>     posted at
>>>
>>>        http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.
>>>
>>>     The current meeting regional rotation (announced at IETF79)
>>>     allows for an
>>>     occasional IETF meeting outside of our main regions (Europe,
>>>     North America,
>>>     Asia/Pacific).
>>>
>>>     IETF standards are made more valuable the more relevant they are
>>>     and the
>>>     more
>>>     uptake they get.  IETF standards are also made more robust when all
>>>     perspectives
>>>     are represented during their development.  Encouraging growing
>>>     participation
>>>     will help strengthen the Internet, further encourage
>>>     participation from
>>>     those areas
>>>     that will see the most growth in the coming years, and will help
>>>     advance
>>>     the IETF
>>>     in political and international circles which is becoming more of an
>>>     imperative.
>>>
>>>     We have asked the IESG for their feedback and they are supportive
>>>     of a
>>>     meeting in
>>>     South America if there is community support and active
>>>     participants attend.
>>>
>>>     Things to consider are that it will be a long trip for the
>>>     majority of
>>>     IETFers and the
>>>     air fares are more expensive (about 10% to 20% higher than
>>>     average), though
>>>     restaurants are less expensive.  This would be a case where most
>>>     IETFers
>>>     would
>>>     bear more travel pain and expense.
>>>
>>>     The IAOC would like to understand if the IETF community thinks
>>>     that the IETF
>>>     should have a meeting in the next few years in Buenos Aires.  The
>>>     IAOC would
>>>     also like to get feedback on how we can ensure the meeting is as
>>>     successful as
>>>     possible and on ways to grow participation in the region.
>>>
>>>     We have set up a survey at
>>>      https://www.surveymonkey.com/s/NWYLQCD  where
>>>     you can indicate your likelihood of attending, and we encourage
>>>     you to
>>>     send your
>>>     general feedback to the IETF list <ietf@ietf.org
>>>     <mailto:ietf@ietf.org>>.
>>>
>>>     Thanks,
>>>     Bob Hinden
>>>     IAOC Chair

From jiangsheng@huawei.com  Fri May 24 02:29:48 2013
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EE3021F852D; Fri, 24 May 2013 02:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqZ9PEG3lMlZ; Fri, 24 May 2013 02:29:44 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id EC8F021F93BA; Fri, 24 May 2013 02:29:43 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ARR69501; Fri, 24 May 2013 09:29:38 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 24 May 2013 10:29:20 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 24 May 2013 10:29:35 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.01.0323.007; Fri, 24 May 2013 17:29:32 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: The IAOC <bob.hinden@gmail.com>, IETF Announcement List <ietf-announce@ietf.org>
Subject: RE: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV831a2Not7oT+E2z+fdRKnH2bJkUEAgQ
Date: Fri, 24 May 2013 09:29:30 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC96ED6@nkgeml512-mbx.china.huawei.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
In-Reply-To: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 24 May 2013 08:12:04 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 09:29:48 -0000

U3BlYWtpbmcgYXMgYW4gSUVURiBwYXJ0aWNpcGF0b3IsIGl0IGlzIGdvb2QgZm9yIElFVEYgZGl2
ZXJzaXR5LiBNYW55IHBlb3BsZSB3aWxsIGFsc28gZW5qb3kgdG8gdmlzaXQgYSBuZXcgcGxhY2Vz
IHdpdGggY3VyaW91cy4gQWN0dWFsbHksIEJ1ZW5vcyBBaXJlcyBkaXNhcHBvaW50ZWQgbWUgd2hl
biBJIGZvdW5kIGl0IHdhcyBzbyBzaW1pbGFyIHRvIEV1cm9wZWFuIGNpdGllcy4NCg0KU3BlYWtp
bmcgYXMgYW4gQXNpYW4sIGxhc3QgdGltZSBJIGZsaWdodCB0byBCdWVub3MgQWlyZXMgdG9vayBt
ZSBtb3JlIHRoYW4gMzAgaG91cnMgZG9vci10by1kb29yLiBBbHNvLCBsb25nZXIgZmxpZ2h0IHRp
bWUgbWVhbnMgbW9yZSBleHBlbnNpdmUgYWlyIHRpY2tldHMuIEFzIHJlc3VsdCwgd2UgbWF5IGV4
cGVyaWVuY2UgYSBtZWV0aW5nIHdpdGggbXVjaCBsZXNzIEFzaWFuIHBhcnRpY2lwYXRvcnMuIEkg
YW0gbm90IHN1cmUgdGhlIGluY3JlYXNlIG9mIHBhcnRpY2lwYXRvcnMgZnJvbSBvdGhlciBjb250
aW5lbnRzIGNhbiBtZWV0IHRoZSBnYXAuDQoNCkJlc3QgcmVnYXJkcywNCg0KU2hlbmcNCg0KPi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFtt
YWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgVGhlDQo+SUFPQw0KPlNl
bnQ6IFRodXJzZGF5LCBNYXkgMjMsIDIwMTMgMTE6NTQgUE0NCj5UbzogSUVURiBBbm5vdW5jZW1l
bnQgTGlzdA0KPkNjOiBpZXRmQGlldGYub3JnDQo+U3ViamVjdDogSUVURiBNZWV0aW5nIGluIFNv
dXRoIEFtZXJpY2ENCj4NCj5BcyB5b3UgbWF5IGtub3cgdGhlIElBT0MgaGFzIGJlZW4gaW52ZXN0
aWdhdGluZyB0aGUgZmVhc2liaWxpdHkgb2YgaGF2aW5nIGFuDQo+SUVURg0KPm1lZXRpbmcgaW4g
U291dGggQW1lcmljYS4gIFRoZXJlIHdhcyBhIHNpdGUgdmlzaXQgdG8gU291dGggQW1lcmljYSBs
YXN0DQo+RmVicnVhcnkuDQo+V2UgaGF2ZSBmb3VuZCB0d28gdmVudWVzIHRoYXQgd2UgYmVsaWV2
ZSB3aWxsIHN1cHBvcnQgYSBzdWNjZXNzZnVsIElFVEYNCj5tZWV0aW5nDQo+YW5kIHdlIHdvdWxk
IGxpa2UgdG8gZ2V0IGZlZWRiYWNrIGZyb20gdGhlIGNvbW11bml0eS4NCj4NCj5UaGUgdmVudWVz
IGFyZSBpbiBCdWVub3MgQWlyZXMuICBUaGV5IG1lZXQgb3VyIHJlcXVpcmVtZW50cyBmb3IgdGhl
DQo+bWVldGluZw0KPnNwYWNlLCBuZXR3b3JraW5nLCBuZWFyYnkgcmVzdGF1cmFudHMgYW5kIGJh
cnMsIGhvdGVsIHJvb20gcmF0ZXMgaW4gdGhlIG1pZA0KPiQyMDANCj5kb2xsYXIgcmFuZ2UsIG5l
YXJieSBhbHRlcm5hdGUgaG90ZWxzIGF0IGEgYnJvYWQgcmFuZ2Ugb2YgcHJpY2VzLCBuaWNlIGFy
ZWEgaW4NCj50aGUNCj5jaXR5LCBzYWZlLCBkaXJlY3QgaW50ZXJuYXRpb25hbCBmbGlnaHRzLCBh
bmQgYWNjZXNzaWJsZSB2aXNhcy4gIFRoZSBJQU9DIHRoaW5rcw0KPndlDQo+Y291bGQgaGF2ZSBh
IHN1Y2Nlc3NmdWwgSUVURiBtZWV0aW5nIGluIEJ1ZW5vcyBBaXJlcyBhbmQgdGhhdCBhdHRlbmRl
ZXMNCj53b3VsZA0KPmxpa2UgdGhlIHZlbnVlcy4NCj4NCj5UaGVyZSBoYXMgYmVlbiBhIGNvbnNp
c3RlbnQgbGV2ZWwgb2YgSUVURiBwYXJ0aWNpcGF0aW9uIGZyb20gU291dGggYW5kIENlbnRyYWwN
Cj5BbWVyaWNhLCBhbmQgaXQgaGFzIGJlZW4gZ3Jvd2luZyBzaW5jZSBJRVRGODIuICBUaGUgZGF0
YSBvbiB0aGlzIGlzIHBvc3RlZCBhdA0KPg0KPiAgIGh0dHA6Ly9pYW9jLmlldGYub3JnL2RvY3Vt
ZW50cy9JRVRGLVJlZ2lvbmFsLUF0dGVuZGFuY2UtMDAucGRmLg0KPg0KPlRoZSBjdXJyZW50IG1l
ZXRpbmcgcmVnaW9uYWwgcm90YXRpb24gKGFubm91bmNlZCBhdCBJRVRGNzkpIGFsbG93cyBmb3Ig
YW4NCj5vY2Nhc2lvbmFsIElFVEYgbWVldGluZyBvdXRzaWRlIG9mIG91ciBtYWluIHJlZ2lvbnMg
KEV1cm9wZSwgTm9ydGggQW1lcmljYSwNCj5Bc2lhL1BhY2lmaWMpLg0KPg0KPklFVEYgc3RhbmRh
cmRzIGFyZSBtYWRlIG1vcmUgdmFsdWFibGUgdGhlIG1vcmUgcmVsZXZhbnQgdGhleSBhcmUgYW5k
IHRoZQ0KPm1vcmUNCj51cHRha2UgdGhleSBnZXQuICBJRVRGIHN0YW5kYXJkcyBhcmUgYWxzbyBt
YWRlIG1vcmUgcm9idXN0IHdoZW4gYWxsDQo+cGVyc3BlY3RpdmVzDQo+YXJlIHJlcHJlc2VudGVk
IGR1cmluZyB0aGVpciBkZXZlbG9wbWVudC4gIEVuY291cmFnaW5nIGdyb3dpbmcNCj5wYXJ0aWNp
cGF0aW9uDQo+d2lsbCBoZWxwIHN0cmVuZ3RoZW4gdGhlIEludGVybmV0LCBmdXJ0aGVyIGVuY291
cmFnZSBwYXJ0aWNpcGF0aW9uIGZyb20gdGhvc2UNCj5hcmVhcw0KPnRoYXQgd2lsbCBzZWUgdGhl
IG1vc3QgZ3Jvd3RoIGluIHRoZSBjb21pbmcgeWVhcnMsIGFuZCB3aWxsIGhlbHAgYWR2YW5jZSB0
aGUNCj5JRVRGDQo+aW4gcG9saXRpY2FsIGFuZCBpbnRlcm5hdGlvbmFsIGNpcmNsZXMgd2hpY2gg
aXMgYmVjb21pbmcgbW9yZSBvZiBhbiBpbXBlcmF0aXZlLg0KPg0KPldlIGhhdmUgYXNrZWQgdGhl
IElFU0cgZm9yIHRoZWlyIGZlZWRiYWNrIGFuZCB0aGV5IGFyZSBzdXBwb3J0aXZlIG9mIGENCj5t
ZWV0aW5nIGluDQo+U291dGggQW1lcmljYSBpZiB0aGVyZSBpcyBjb21tdW5pdHkgc3VwcG9ydCBh
bmQgYWN0aXZlIHBhcnRpY2lwYW50cyBhdHRlbmQuDQo+DQo+VGhpbmdzIHRvIGNvbnNpZGVyIGFy
ZSB0aGF0IGl0IHdpbGwgYmUgYSBsb25nIHRyaXAgZm9yIHRoZSBtYWpvcml0eSBvZiBJRVRGZXJz
IGFuZA0KPnRoZQ0KPmFpciBmYXJlcyBhcmUgbW9yZSBleHBlbnNpdmUgKGFib3V0IDEwJSB0byAy
MCUgaGlnaGVyIHRoYW4gYXZlcmFnZSksIHRob3VnaA0KPnJlc3RhdXJhbnRzIGFyZSBsZXNzIGV4
cGVuc2l2ZS4gIFRoaXMgd291bGQgYmUgYSBjYXNlIHdoZXJlIG1vc3QgSUVURmVycw0KPndvdWxk
DQo+YmVhciBtb3JlIHRyYXZlbCBwYWluIGFuZCBleHBlbnNlLg0KPg0KPlRoZSBJQU9DIHdvdWxk
IGxpa2UgdG8gdW5kZXJzdGFuZCBpZiB0aGUgSUVURiBjb21tdW5pdHkgdGhpbmtzIHRoYXQgdGhl
IElFVEYNCj5zaG91bGQgaGF2ZSBhIG1lZXRpbmcgaW4gdGhlIG5leHQgZmV3IHllYXJzIGluIEJ1
ZW5vcyBBaXJlcy4gIFRoZSBJQU9DDQo+d291bGQNCj5hbHNvIGxpa2UgdG8gZ2V0IGZlZWRiYWNr
IG9uIGhvdyB3ZSBjYW4gZW5zdXJlIHRoZSBtZWV0aW5nIGlzIGFzIHN1Y2Nlc3NmdWwNCj5hcw0K
PnBvc3NpYmxlIGFuZCBvbiB3YXlzIHRvIGdyb3cgcGFydGljaXBhdGlvbiBpbiB0aGUgcmVnaW9u
Lg0KPg0KPldlIGhhdmUgc2V0IHVwIGEgc3VydmV5IGF0ICBodHRwczovL3d3dy5zdXJ2ZXltb25r
ZXkuY29tL3MvTldZTFFDRA0KPndoZXJlDQo+eW91IGNhbiBpbmRpY2F0ZSB5b3VyIGxpa2VsaWhv
b2Qgb2YgYXR0ZW5kaW5nLCBhbmQgd2UgZW5jb3VyYWdlIHlvdSB0byBzZW5kDQo+eW91cg0KPmdl
bmVyYWwgZmVlZGJhY2sgdG8gdGhlIElFVEYgbGlzdCA8aWV0ZkBpZXRmLm9yZz4uDQo+DQo+VGhh
bmtzLA0KPkJvYiBIaW5kZW4NCj5JQU9DIENoYWlyDQo=

From ynir@checkpoint.com  Fri May 24 08:31:23 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 640A321F997C for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 08:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.454
X-Spam-Level: 
X-Spam-Status: No, score=-10.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-zm--SvbkKq for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 08:30:52 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0382221F97EF for <ietf@ietf.org>; Fri, 24 May 2013 08:30:47 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4OFUKC8021006; Fri, 24 May 2013 18:30:20 +0300
X-CheckPoint: {519F8523-D-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Fri, 24 May 2013 18:28:19 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV831D4tngZxCqkCGgr/monvqF5kUL46AgAAVLwA=
Date: Fri, 24 May 2013 15:28:18 +0000
Message-ID: <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca>
In-Reply-To: <16454.1369404751@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.204]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A4A414FB75882548B24598B40D17C032@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 15:31:23 -0000

I used Expedia to price flights for me on March 2014:
 - Buenos Aires: $1401 (21h each way)
 - London (where the meeting actually happens): $413 (7h each way. Direct c=
osts a bit more)
 - Vancouver: $1217 (24 h each way????? $1288 with a more reasonable 16h)
 - Honululu: $1535 (28h each way)
 - Melbourne (to minimize the pain for Mark): $2155 (36h)
 - Minneapolis: $1020 (18h)

So Buenos Aires is not much more painful than some other destinations we've=
 been talking about, and I believe the same will be true for most Europeans=
. For Americans, is it much more expensive than a trip to Prague?

Yoav

On May 24, 2013, at 5:12 PM, Michael Richardson <mcr+ietf@sandelman.ca> wro=
te:

>=20
>>>>>> "The" =3D=3D The IAOC <bob.hinden@gmail.com> writes:
>    The> The venues are in Buenos Aires.  They meet our requirements for t=
he meeting
>    The> space, networking, nearby restaurants and bars, hotel room rates =
in the mid $200
>    The> dollar range, nearby alternate hotels at a broad range of prices,=
 nice area in the
>    The> city, safe, direct international flights, and accessible visas.  =
The IAOC thinks we
>    The> could have a successful IETF meeting in Buenos Aires and that att=
endees would
>    The> like the venues.
>=20
> My question is about whether we would be there during the "peak" season,
> and when exactly is that season?
>=20
> I priced flights for me in July, November and March (2014).
> It seems that most flights go through Santiago or Sao Paulo, one went
> through Atlanta.  The lowest cost flight for me is similiar to travel to
> Europe not in the summer,  but the price rises quite quickly to the $4K
> range.  The worse rise seems to be March, but that was also the furthest
> in the future.
>=20
>    The> Things to consider are that it will be a long trip for the majori=
ty of IETFers and the
>    The> air fares are more expensive (about 10% to 20% higher than averag=
e), though
>    The> restaurants are less expensive.  This would be a case where most =
IETFers would
>    The> bear more travel pain and expense. =20
>=20
> What are the hotel costs?  =20
> (I fund my own attendance)
>=20
> --=20
> ]               Never tell me the odds!                 | ipv6 mesh netwo=
rks [=20
> ]   Michael Richardson, Sandelman Software Works        | network archite=
ct  [=20
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails=
    [=20
> =09
>=20


From stephen.farrell@cs.tcd.ie  Fri May 24 08:50:29 2013
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B5621F8FAF for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 08:50:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0XWsrvHRMSgN for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 08:50:24 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 602FF21F8EA5 for <ietf@ietf.org>; Fri, 24 May 2013 08:50:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 42B42BEAF; Fri, 24 May 2013 16:50:02 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id df5LoDltXo5a; Fri, 24 May 2013 16:49:56 +0100 (IST)
Received: from [10.87.48.5] (unknown [86.41.48.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 12EF7BE8A; Fri, 24 May 2013 16:49:56 +0100 (IST)
Message-ID: <519F8C23.3030504@cs.tcd.ie>
Date: Fri, 24 May 2013 16:49:55 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Antonio M. Moreiras" <moreiras@nic.br>
Subject: Re: IETF Meeting in South America
References: <519E61BF.4030408@nic.br> <519E7E44.1050309@nic.br>
In-Reply-To: <519E7E44.1050309@nic.br>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 15:50:29 -0000

On 05/23/2013 09:38 PM, Antonio M. Moreiras wrote:
> Hi. That's great news!
> 
> I think that a meeting in Buenos Aires will foster the participation in
> our region. Including Brazilian participation. Probably it will be a
> great opportunity for a lot of people to participate for the first time,
> and come to know the process, and become involved.

I know many of us know this, but its worth saying. People from
*anywhere* can participate now, via email.

There is no need to wait for a nearby meeting. I'd say starting
to participate via email makes such a meeting far more likely
if participants turn up and do good technical work.

S.


> 
> It is important to note that sometimes it's not so easy for us
> Brazilians, and Latin-americans, in general, to get visas for other
> countries. For USA, for instance. And it is true that , in general, it
> is easy to get a visa for Argentina.
> 
> Regards,
> Antonio M. Moreiras.
> 
>>>>     -------- Original Message --------
>>>>     Subject: IETF Meeting in South America
>>>>     Date: Thu, 23 May 2013 08:54:12 -0700
>>>>     From: The IAOC <bob.hinden@gmail.com <mailto:bob.hinden@gmail.com>>
>>>>     To: IETF Announcement List <ietf-announce@ietf.org
>>>>     <mailto:ietf-announce@ietf.org>>
>>>>     CC: ietf@ietf.org <mailto:ietf@ietf.org>
>>>>
>>>>     As you may know the IAOC has been investigating the feasibility of
>>>>     having an IETF
>>>>     meeting in South America.  There was a site visit to South
>>>>     America last
>>>>     February.
>>>>     We have found two venues that we believe will support a
>>>>     successful IETF
>>>>     meeting
>>>>     and we would like to get feedback from the community.
>>>>
>>>>     The venues are in Buenos Aires.  They meet our requirements for
>>>>     the meeting
>>>>     space, networking, nearby restaurants and bars, hotel room rates
>>>>     in the
>>>>     mid $200
>>>>     dollar range, nearby alternate hotels at a broad range of prices,
>>>>     nice
>>>>     area in the
>>>>     city, safe, direct international flights, and accessible visas.  The
>>>>     IAOC thinks we
>>>>     could have a successful IETF meeting in Buenos Aires and that
>>>>     attendees
>>>>     would
>>>>     like the venues.
>>>>
>>>>     There has been a consistent level of IETF participation from
>>>>     South and
>>>>     Central
>>>>     America, and it has been growing since IETF82.  The data on this is
>>>>     posted at
>>>>
>>>>        http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.
>>>>
>>>>     The current meeting regional rotation (announced at IETF79)
>>>>     allows for an
>>>>     occasional IETF meeting outside of our main regions (Europe,
>>>>     North America,
>>>>     Asia/Pacific).
>>>>
>>>>     IETF standards are made more valuable the more relevant they are
>>>>     and the
>>>>     more
>>>>     uptake they get.  IETF standards are also made more robust when all
>>>>     perspectives
>>>>     are represented during their development.  Encouraging growing
>>>>     participation
>>>>     will help strengthen the Internet, further encourage
>>>>     participation from
>>>>     those areas
>>>>     that will see the most growth in the coming years, and will help
>>>>     advance
>>>>     the IETF
>>>>     in political and international circles which is becoming more of an
>>>>     imperative.
>>>>
>>>>     We have asked the IESG for their feedback and they are supportive
>>>>     of a
>>>>     meeting in
>>>>     South America if there is community support and active
>>>>     participants attend.
>>>>
>>>>     Things to consider are that it will be a long trip for the
>>>>     majority of
>>>>     IETFers and the
>>>>     air fares are more expensive (about 10% to 20% higher than
>>>>     average), though
>>>>     restaurants are less expensive.  This would be a case where most
>>>>     IETFers
>>>>     would
>>>>     bear more travel pain and expense.
>>>>
>>>>     The IAOC would like to understand if the IETF community thinks
>>>>     that the IETF
>>>>     should have a meeting in the next few years in Buenos Aires.  The
>>>>     IAOC would
>>>>     also like to get feedback on how we can ensure the meeting is as
>>>>     successful as
>>>>     possible and on ways to grow participation in the region.
>>>>
>>>>     We have set up a survey at
>>>>      https://www.surveymonkey.com/s/NWYLQCD  where
>>>>     you can indicate your likelihood of attending, and we encourage
>>>>     you to
>>>>     send your
>>>>     general feedback to the IETF list <ietf@ietf.org
>>>>     <mailto:ietf@ietf.org>>.
>>>>
>>>>     Thanks,
>>>>     Bob Hinden
>>>>     IAOC Chair
> 
> 

From swmike@swm.pp.se  Fri May 24 09:06:54 2013
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E226521F85EF for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2I8tqgcAWfIJ for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:06:54 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 835D221F9579 for <ietf@ietf.org>; Fri, 24 May 2013 09:06:51 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C12AC9C; Fri, 24 May 2013 18:06:49 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id B5DB69A for <ietf@ietf.org>; Fri, 24 May 2013 18:06:49 +0200 (CEST)
Date: Fri, 24 May 2013 18:06:49 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
In-Reply-To: <519F8C23.3030504@cs.tcd.ie>
Message-ID: <alpine.DEB.2.00.1305241754310.18252@uplift.swm.pp.se>
References: <519E61BF.4030408@nic.br> <519E7E44.1050309@nic.br> <519F8C23.3030504@cs.tcd.ie>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
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: Fri, 24 May 2013 16:06:55 -0000

On Fri, 24 May 2013, Stephen Farrell wrote:

> There is no need to wait for a nearby meeting. I'd say starting to 
> participate via email makes such a meeting far more likely if 
> participants turn up and do good technical work.

It's my experience that non-native english speakers are more comfortable 
exchanging text than speaking. I've met several people who write excellent 
english but who it's difficult to communicate with verbally.

So if language is considered a barrier, would having an IETF meeting there 
really help? I feel overall that outreach by a few people would be more 
effective in bringing in people to start doing work via email (and 
perhaps, teleconferencing), and then where there is a few more people 
active in South America, then a physical meeting there would be more 
effective?

As a Fidonet user from the late 1980:ties, I felt the IETF had a really 
low barrier of entry. What would a 20-30 year old who started to use the 
Internet 5-10 years ago feel about it? I don't know. What is the target 
audience? A telecommunication professional? A student who might be a 
would-be telecom profession? An App programmer? All of the above?

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

From lberger@labn.net  Fri May 24 09:08:05 2013
Return-Path: <lberger@labn.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 43B3C21F96D4 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.381
X-Spam-Level: 
X-Spam-Status: No, score=-102.381 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aqjn1vqVDeqg for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:08:00 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 4AAEA21F96D9 for <ietf@ietf.org>; Fri, 24 May 2013 09:08:00 -0700 (PDT)
Received: (qmail 29747 invoked by uid 0); 24 May 2013 16:07:13 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy6.bluehost.com with SMTP; 24 May 2013 16:07:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=pSbCOwrHACiQ2kQT+m1Kuq/gMv64VgyaBQJZEJfUdFU=;  b=o/Q9HSSweWlMHcB00FfY3yH+cPUMUZIHbzO4fjy/026nBU9BMwtRREkBX+0dFucULMfWm6a8Gu6rNIhLBrMjU6J4KiXOjJQ6X50Emh2PnowTmuTI5tl7k/pl4Y0XKFuj;
Received: from box313.bluehost.com ([69.89.31.113]:49832 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UfuWM-00015E-VT; Fri, 24 May 2013 10:07:11 -0600
Message-ID: <519F9028.50601@labn.net>
Date: Fri, 24 May 2013 12:07:04 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca> <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com>
In-Reply-To: <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 16:08:05 -0000

> For Americans, is it much more expensive than a trip to Prague?

I just happen to be looking at flights for berlin at the moment.  BA is
pretty much the same +-$1600 if I'm willing to take an extra hop, closer
to $2K for one hop.

I generally find going to Europe in the summer to be pretty expensive so
am not sure this is the best comparison.  As metioned elsewhere in this
thread, time of year does matter.

I personally am a big fan for going to uninteresting locations in their
off season. Although, perhaps I'm alone in liking Minneapolis in the
winter as an IETF destination...

Lou

On 5/24/2013 11:28 AM, Yoav Nir wrote:
> I used Expedia to price flights for me on March 2014:
>  - Buenos Aires: $1401 (21h each way)
>  - London (where the meeting actually happens): $413 (7h each way. Direct costs a bit more)
>  - Vancouver: $1217 (24 h each way????? $1288 with a more reasonable 16h)
>  - Honululu: $1535 (28h each way)
>  - Melbourne (to minimize the pain for Mark): $2155 (36h)
>  - Minneapolis: $1020 (18h)
> 
> So Buenos Aires is not much more painful than some other destinations we've been talking about, and I believe the same will be true for most Europeans. For Americans, is it much more expensive than a trip to Prague?
> 
> Yoav
> 
> On May 24, 2013, at 5:12 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
>>
>>>>>>> "The" == The IAOC <bob.hinden@gmail.com> writes:
>>    The> The venues are in Buenos Aires.  They meet our requirements for the meeting
>>    The> space, networking, nearby restaurants and bars, hotel room rates in the mid $200
>>    The> dollar range, nearby alternate hotels at a broad range of prices, nice area in the
>>    The> city, safe, direct international flights, and accessible visas.  The IAOC thinks we
>>    The> could have a successful IETF meeting in Buenos Aires and that attendees would
>>    The> like the venues.
>>
>> My question is about whether we would be there during the "peak" season,
>> and when exactly is that season?
>>
>> I priced flights for me in July, November and March (2014).
>> It seems that most flights go through Santiago or Sao Paulo, one went
>> through Atlanta.  The lowest cost flight for me is similiar to travel to
>> Europe not in the summer,  but the price rises quite quickly to the $4K
>> range.  The worse rise seems to be March, but that was also the furthest
>> in the future.
>>
>>    The> Things to consider are that it will be a long trip for the majority of IETFers and the
>>    The> air fares are more expensive (about 10% to 20% higher than average), though
>>    The> restaurants are less expensive.  This would be a case where most IETFers would
>>    The> bear more travel pain and expense.  
>>
>> What are the hotel costs?   
>> (I fund my own attendance)
>>
>> -- 
>> ]               Never tell me the odds!                 | ipv6 mesh networks [ 
>> ]   Michael Richardson, Sandelman Software Works        | network architect  [ 
>> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
>> 	
>>
> 
> 
> 
> 
> 

From scott.brim@gmail.com  Fri May 24 09:11:19 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB0A21F8AF7 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QQjTasOAZN2B for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:11:19 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0065A21F89EB for <ietf@ietf.org>; Fri, 24 May 2013 09:11:07 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so2400889obc.20 for <ietf@ietf.org>; Fri, 24 May 2013 09:11:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YnoZxnK79uksxCsdPwKTjSjo70x7Yfu5tuZBsRnsNuU=; b=X+k08Cf/Bvsx1LbsmvBXHjo3x9eJKiR3J1j1w/cSzv5J5NfrERVSDhWICdorXeMS8x 4tgYBCCAd1wS9trLJcVSPENSjXTbdqpps7bwbgEXhzvCYDF6cHSjLrh1x//+5KQpxE+H 6euuZI0WmtLwLDHd2QClSV60unlNfBHxNx8qMk0faGc5wK7tbQwXDNyQRWAAIC50UsCV 0sR+R17IN99IyYV7LJBPyNml418VB7xV7GgCc7WgOc78pj2edY9gqKARU7OrvB8OV7VI Q/7OQvA4XT4wHZ3N0XUJPYGAuhMfQs3D/awoapdB/momEI/NSJORiZCYB1zB50PEAwb7 difQ==
X-Received: by 10.60.80.33 with SMTP id o1mr12523762oex.116.1369411867537; Fri, 24 May 2013 09:11:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.114.193 with HTTP; Fri, 24 May 2013 09:10:47 -0700 (PDT)
In-Reply-To: <alpine.DEB.2.00.1305241754310.18252@uplift.swm.pp.se>
References: <519E61BF.4030408@nic.br> <519E7E44.1050309@nic.br> <519F8C23.3030504@cs.tcd.ie> <alpine.DEB.2.00.1305241754310.18252@uplift.swm.pp.se>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 24 May 2013 12:10:47 -0400
Message-ID: <CAPv4CP_=K85+b_NNhb1B-=d7z2y-o62LFapW-_0R29iGaYULRw@mail.gmail.com>
Subject: Re: IETF Meeting in South America
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=089e0122867eea784c04dd790b78
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, 24 May 2013 16:11:19 -0000

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

On Fri, May 24, 2013 at 12:06 PM, Mikael Abrahamsson <swmike@swm.pp.se>wrote:

> It's my experience that non-native english speakers are more comfortable
> exchanging text than speaking. I've met several people who write excellent
> english but who it's difficult to communicate with verbally.
>

and in some cases I've seen the opposite. :-p

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

On Fri, May 24, 2013 at 12:06 PM, Mikael Abrahamsson <span dir=3D"ltr">&lt;=
<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swmike@swm.pp.se</a>&=
gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">

It&#39;s my experience that non-native english speakers are more comfortabl=
e exchanging text than speaking. I&#39;ve met several people who write exce=
llent english but who it&#39;s difficult to communicate with verbally.<br>

</blockquote><div><br></div><div>and in some cases I&#39;ve seen the opposi=
te. :-p</div><div><br></div><div><br></div></div>

--089e0122867eea784c04dd790b78--

From melinda.shore@gmail.com  Fri May 24 09:18:39 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0EB521F85DC for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPD87dRo6Uqw for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 09:18:34 -0700 (PDT)
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) by ietfa.amsl.com (Postfix) with ESMTP id 154B221F85EF for <ietf@ietf.org>; Fri, 24 May 2013 09:18:34 -0700 (PDT)
Received: by mail-pd0-f176.google.com with SMTP id r11so4285227pdi.7 for <ietf@ietf.org>; Fri, 24 May 2013 09:18:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Kxjsiebr/Ag5lyxAUf9sU8WVrDL1L7pVemlQ53hEAGE=; b=mLLSSLVSLBYWxRaPOopwPF0q+DFmxV/RUq1TczM+7NWZE2YMTEj5b9RXRmwlfWWC3W ycGIPsITgR+ZaidlzsS0AF8yhPd0KgLz9MlF/q3v2HyxBSIUosSC2kfD8f6ylV3OihhU gTSKFaRsa/HgZmIjjnUnB0crLWdYHffFPtz0YC1t9zvfyhaIeeaZkiQJf1o+CxylYGpk Pzqj3qmlLp6yE/Mtlbbc+sd3zhyPLTPMkQJXfuZLJqQYS9fVf2/QvkQEe4Y6UL/4e7Lg 4bes5wD8MCrnuz32BqrHQsUAsRl72D0+cpZsf0ty+TyFKiq9ac4x5LPscpgQkSnExyej 5DNQ==
X-Received: by 10.66.159.130 with SMTP id xc2mr18668478pab.61.1369412313767; Fri, 24 May 2013 09:18:33 -0700 (PDT)
Received: from spandex.local (66-230-83-62-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.62]) by mx.google.com with ESMTPSA id un15sm16373849pab.7.2013.05.24.09.18.32 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 09:18:32 -0700 (PDT)
Message-ID: <519F92D6.3040609@gmail.com>
Date: Fri, 24 May 2013 08:18:30 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca> <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com> <519F9028.50601@labn.net>
In-Reply-To: <519F9028.50601@labn.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: Fri, 24 May 2013 16:18:40 -0000

On 5/24/13 8:07 AM, Lou Berger wrote:
> I personally am a big fan for going to uninteresting locations in their
> off season. Although, perhaps I'm alone in liking Minneapolis in the
> winter as an IETF destination...

No, not alone.

At any rate I think that the core questions about participation
are probably more relevant than a run-down of individual travel
costs.  I've noticed that some of the posters from South
American countries who've expressed enthusiasm for an IETF
meeting in Buenos Aires have not been working group contributors,
and I'm wondering what they feel the barriers to participation
have been, and what can be done that would make it more likely
that they'd, say, review documents.

Melinda


From daedulus@btconnect.com  Fri May 24 10:13:52 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDAD21F961C for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKcrI5gKoO7E for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:13:46 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe001.messaging.microsoft.com [216.32.180.11]) by ietfa.amsl.com (Postfix) with ESMTP id 4E94521F9633 for <ietf@ietf.org>; Fri, 24 May 2013 10:13:46 -0700 (PDT)
Received: from mail6-va3-R.bigfish.com (10.7.14.253) by VA3EHSOBE002.bigfish.com (10.7.40.22) with Microsoft SMTP Server id 14.1.225.23; Fri, 24 May 2013 17:13:45 +0000
Received: from mail6-va3 (localhost [127.0.0.1])	by mail6-va3-R.bigfish.com (Postfix) with ESMTP id 13DB6200170; Fri, 24 May 2013 17:13:45 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz1033IL17326ah8275bh8275dh8275chz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh304l1d11m1155h)
Received: from mail6-va3 (localhost.localdomain [127.0.0.1]) by mail6-va3 (MessageSwitch) id 1369415623976495_6447; Fri, 24 May 2013 17:13:43 +0000 (UTC)
Received: from VA3EHSMHS001.bigfish.com (unknown [10.7.14.253])	by mail6-va3.bigfish.com (Postfix) with ESMTP id DFCD760313; Fri, 24 May 2013 17:13:43 +0000 (UTC)
Received: from AMSPRD0711HT001.eurprd07.prod.outlook.com (157.56.250.181) by VA3EHSMHS001.bigfish.com (10.7.99.11) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 24 May 2013 17:13:41 +0000
Received: from pc6 (86.173.197.168) by pod51017.outlook.com (10.242.14.162) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 24 May 2013 17:13:27 +0000
Message-ID: <066101ce58a1$3b4cf040$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Lou Berger <lberger@labn.net>, Yoav Nir <ynir@checkpoint.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com><16454.1369404751@sandelman.ca><9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com> <519F9028.50601@labn.net>
Subject: Re: IETF Meeting in South America
Date: Fri, 24 May 2013 18:07:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.173.197.168]
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, 24 May 2013 17:13:52 -0000

----- Original Message -----
From: "Lou Berger" <lberger@labn.net>
To: "Yoav Nir" <ynir@checkpoint.com>
Cc: <ietf@ietf.org>
Sent: Friday, May 24, 2013 5:07 PM
Subject: Re: IETF Meeting in South America


> > For Americans, is it much more expensive than a trip to Prague?
>
> I just happen to be looking at flights for berlin at the moment.  BA
is
> pretty much the same +-$1600 if I'm willing to take an extra hop,
closer
> to $2K for one hop.
>
> I generally find going to Europe in the summer to be pretty expensive
so
> am not sure this is the best comparison.  As metioned elsewhere in
this
> thread, time of year does matter.
>
> I personally am a big fan for going to uninteresting locations in
their
> off season. Although, perhaps I'm alone in liking Minneapolis in the
> winter as an IETF destination...

No, it is my favourite too (although Atlanta runs it close).  I would
not recommend London in the winter though, as it can be short of snow
ploughs:-(

Tom Petch

> Lou
>
> On 5/24/2013 11:28 AM, Yoav Nir wrote:
> > I used Expedia to price flights for me on March 2014:
> >  - Buenos Aires: $1401 (21h each way)
> >  - London (where the meeting actually happens): $413 (7h each way.
Direct costs a bit more)
> >  - Vancouver: $1217 (24 h each way????? $1288 with a more reasonable
16h)
> >  - Honululu: $1535 (28h each way)
> >  - Melbourne (to minimize the pain for Mark): $2155 (36h)
> >  - Minneapolis: $1020 (18h)
> >
> > So Buenos Aires is not much more painful than some other
destinations we've been talking about, and I believe the same will be
true for most Europeans. For Americans, is it much more expensive than a
trip to Prague?
> >
> > Yoav
> >
> > On May 24, 2013, at 5:12 PM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
> >
> >>
> >>>>>>> "The" == The IAOC <bob.hinden@gmail.com> writes:
> >>    The> The venues are in Buenos Aires.  They meet our requirements
for the meeting
> >>    The> space, networking, nearby restaurants and bars, hotel room
rates in the mid $200
> >>    The> dollar range, nearby alternate hotels at a broad range of
prices, nice area in the
> >>    The> city, safe, direct international flights, and accessible
visas.  The IAOC thinks we
> >>    The> could have a successful IETF meeting in Buenos Aires and
that attendees would
> >>    The> like the venues.
> >>
> >> My question is about whether we would be there during the "peak"
season,
> >> and when exactly is that season?
> >>
> >> I priced flights for me in July, November and March (2014).
> >> It seems that most flights go through Santiago or Sao Paulo, one
went
> >> through Atlanta.  The lowest cost flight for me is similiar to
travel to
> >> Europe not in the summer,  but the price rises quite quickly to the
$4K
> >> range.  The worse rise seems to be March, but that was also the
furthest
> >> in the future.
> >>
> >>    The> Things to consider are that it will be a long trip for the
majority of IETFers and the
> >>    The> air fares are more expensive (about 10% to 20% higher than
average), though
> >>    The> restaurants are less expensive.  This would be a case where
most IETFers would
> >>    The> bear more travel pain and expense.
> >>
> >> What are the hotel costs?
> >> (I fund my own attendance)
> >>
> >> --
> >> ]               Never tell me the odds!                 | ipv6 mesh
networks [
> >> ]   Michael Richardson, Sandelman Software Works        | network
architect  [
> >> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on
rails    [
> >>
> >>
> >
> >
> >
> >
> >
>



From Ted.Lemon@nominum.com  Fri May 24 10:31:42 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E864D21F9410 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:31:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.558
X-Spam-Level: 
X-Spam-Status: No, score=-106.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-Gwp9LIWrXg for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:31:36 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 1378F21F9403 for <ietf@ietf.org>; Fri, 24 May 2013 10:31:36 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUZ+j92Su7y/s2MxfwzVR6p+paivCRFaQ@postini.com; Fri, 24 May 2013 10:31:36 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 983781B81C4 for <ietf@ietf.org>; Fri, 24 May 2013 10:31:35 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 8C8DD19005D; Fri, 24 May 2013 10:31:35 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 24 May 2013 10:31:35 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Lou Berger <lberger@labn.net>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV84TSGHm8o4FqkygKNhv1BO4YZkU1zGAgAAVLQCAAArVAIAAF5sA
Date: Fri, 24 May 2013 17:31:35 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751B0A0F@mbx-01.win.nominum.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca> <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com> <519F9028.50601@labn.net>
In-Reply-To: <519F9028.50601@labn.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DAD996ACDA47B542BBB4E3968A985B71@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 17:31:43 -0000

On May 24, 2013, at 12:07 PM, Lou Berger <lberger@labn.net> wrote:
> I personally am a big fan for going to uninteresting locations in their
> off season. Although, perhaps I'm alone in liking Minneapolis in the
> winter as an IETF destination...

You are not.   Although Vancouver seems to have taken over for Minneapolis.


From arturo.servin@gmail.com  Fri May 24 10:34:43 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DC021F9617 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w69IMIxKhisJ for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:34:42 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 99C0B21F9602 for <ietf@ietf.org>; Fri, 24 May 2013 10:34:42 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id i57so7837yha.11 for <ietf@ietf.org>; Fri, 24 May 2013 10:34:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=V9vtDd5JKb8WCf5+q1o2ihoEJrYBNz5rjHy7QyJ8MFU=; b=Y3w7wMrHy3ofCtzSkBBsXycwD7DY7/3Utgd8A53yIyF9zsgdL4mpkFJmMy5NLmmzoE 7vQL1eq2DG4YHzfmSc9pRJXUlZHBycPcioIwlyRsn7aoKm4gd6rnX+Nlyrwp0JNvpzw7 ur882yywF86nhsWDW9XSYLw7ji3gaL+Mkesqt3c81Mx1jAMpqYLjg+w6o9na1tck9IRV 2Y+Z6MX2aNiNfEprsFz3kLj5/Y+O9Tz3ZCUlRqqn10DX1RrVrjLq3//grQfK+rdOdkQI EyUXcdNCqFBFeJGBd9uwryF5Pojj/tIV4qsQFbkpcGYYBkqr4TUBlzeH/qiW+cLxvVVf n7Xg==
X-Received: by 10.236.160.136 with SMTP id u8mr10564629yhk.179.1369416882092;  Fri, 24 May 2013 10:34:42 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:dc04:5fac:21ea:43c4]) by mx.google.com with ESMTPSA id w62sm24765206yhd.27.2013.05.24.10.34.40 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 10:34:41 -0700 (PDT)
Message-ID: <519FA4AF.60600@gmail.com>
Date: Fri, 24 May 2013 14:34:39 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca> <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com> <519F9028.50601@labn.net> <519F92D6.3040609@gmail.com>
In-Reply-To: <519F92D6.3040609@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: Fri, 24 May 2013 17:34:43 -0000

	I have been lurking IETF for many years, but it was only after I went
to my first meeting that I really understood how the IETF worked and how
to really participate.

	After that meeting I started to send comments, read drafts, writing
some initial stuff and arguing. Before that meeting I didn't know how to
do it, and how good or bad my comments would be received. I think it
might be cultural, but before my first meeting I felt a bit intimidated
by the ietf and being flamed by a bad comment.

	I didn't stop feeling intimidated after the first meeting, it took me a
bit more but definitely it helped me to understand the ietf, its
community and how to participate.

	I wouldn't be surprised if it were many people just like I was, lurking
the email lists but have never sent anything for the same reasons that I
did.

Regards,
as

	

On 5/24/13 1:18 PM, Melinda Shore wrote:
> On 5/24/13 8:07 AM, Lou Berger wrote:
>> I personally am a big fan for going to uninteresting locations in their
>> off season. Although, perhaps I'm alone in liking Minneapolis in the
>> winter as an IETF destination...
> 
> No, not alone.
> 
> At any rate I think that the core questions about participation
> are probably more relevant than a run-down of individual travel
> costs.  I've noticed that some of the posters from South
> American countries who've expressed enthusiasm for an IETF
> meeting in Buenos Aires have not been working group contributors,
> and I'm wondering what they feel the barriers to participation
> have been, and what can be done that would make it more likely
> that they'd, say, review documents.
> 
> Melinda
> 

From melinda.shore@gmail.com  Fri May 24 10:39:25 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1570421F9633 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level: 
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[AWL=-0.071,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZL0DWog7R5hJ for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:39:19 -0700 (PDT)
Received: from mail-pd0-f178.google.com (mail-pd0-f178.google.com [209.85.192.178]) by ietfa.amsl.com (Postfix) with ESMTP id 0C0A121F962D for <ietf@ietf.org>; Fri, 24 May 2013 10:39:19 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id w11so1365393pde.37 for <ietf@ietf.org>; Fri, 24 May 2013 10:39:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=kyqVtJkiOCp9CSWztb2PipdEMQVzb43hGlLVTPDLvPk=; b=tPbLq0vS+dO3p0ax8jZDwG0eml0iDF9gvb6nztwIvZkY0MJ0YSjxYOjGzNMaicRno8 RYs5u8azwdDVU90RI97ya5gBLGKO6DLaWXYA1cZ8wMOFw/cx2Iln+3eNUi9JRj2RCilJ x5Nk+4Lgr2DA0jhSeBw439/qa+P6Ag26G0UcJY13atFTvMKP1uhEYtXRgIdXJLbRC6UZ OQRwMNUzxEzOCJJH42lHfZq4wlekArKZNAhPZ4e6XoEvnCsYQebdVieguPWsfgVXnvKn sEGq1u0jhHhCv9KQHMnpbAeuJxYuu/kd+FpscAHrLPPGGRVo8jC8fbD+eeekRaqFefkl 3/nA==
X-Received: by 10.68.250.229 with SMTP id zf5mr18595291pbc.148.1369417158714;  Fri, 24 May 2013 10:39:18 -0700 (PDT)
Received: from spandex.local (66-230-83-62-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.83.62]) by mx.google.com with ESMTPSA id b7sm16949842pba.39.2013.05.24.10.39.16 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 10:39:17 -0700 (PDT)
Message-ID: <519FA5C3.1020403@gmail.com>
Date: Fri, 24 May 2013 09:39:15 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca> <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com> <519F9028.50601@labn.net> <8D23D4052ABE7A4490E77B1A012B6307751B0A0F@mbx-01.win.nominum.com>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751B0A0F@mbx-01.win.nominum.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, 24 May 2013 17:39:25 -0000

On 5/24/13 9:31 AM, Ted Lemon wrote:
> You are not.   Although Vancouver seems to have taken over for Minneapolis.

Feh.  There is no winter in Vancouver.  On the other hand there are
salmon and steelhead.

Melinda



From dougb@dougbarton.us  Fri May 24 10:43:25 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A065F21F9318 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:43:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L9QgU39w8XYM for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:43:21 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 506F321F962D for <ietf@ietf.org>; Fri, 24 May 2013 10:43:21 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532] (unknown [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532]) by dougbarton.us (Postfix) with ESMTPSA id 0247122B42 for <ietf@ietf.org>; Fri, 24 May 2013 17:43:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1369417397; bh=bgk2sEyqBFS/ao1HJKF1wsalzTzM1nX+o3DDDCcoBu4=; h=Date:From:To:Subject:References:In-Reply-To; b=F9S9emVKvYNpelb7EIeOrhh2W6979kBofhqLUDgxrov+1bQhWX9a0IiljzByfjbBA 7ZgCxm8oYXls31aO4OanLViKZ0V5v2rq1DbGuIycLPmrNs6fdX26HFce2z4WjPgv5B TedNLvdzrT7hvMcz7JJFzUiOVNJ/PdlyNb7bg66I=
Message-ID: <519FA6B4.3020007@dougbarton.us>
Date: Fri, 24 May 2013 10:43:16 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
In-Reply-To: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 17:43:25 -0000

While it's unlikely that I would be able to attend, I think it's an 
excellent idea for reasons already better stated by others, and BA is a 
very nice city.

The only suggestion I might add that I haven't seen mentioned yet (and 
pardon me if I missed it) would be to perhaps schedule the meeting to 
piggy back on one of the excellent regional meetings that is already 
well established. Arturo gave a good list, IME LACNIC and LACTLD would 
be the best/most obvious candidates. By running the IETF meeting either 
the week before, or the week after one of those meetings we would be 
able to get quite a bit of cross-pollination, especially with the 
availability of day passes.

hth,

Doug

From joelja@bogus.com  Fri May 24 11:03:23 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A81021F9671 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXxBKPgAgrAN for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:03:23 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 16CD621F8E87 for <ietf@ietf.org>; Fri, 24 May 2013 11:03:23 -0700 (PDT)
Received: from joels-MacBook-Air.local (214.sub-70-197-12.myvzw.com [70.197.12.214]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4OI3LQu050800 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 24 May 2013 18:03:22 GMT (envelope-from joelja@bogus.com)
Message-ID: <519FAB64.6030007@bogus.com>
Date: Fri, 24 May 2013 11:03:16 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us>
In-Reply-To: <519FA6B4.3020007@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 24 May 2013 18:03:22 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:03:23 -0000

On 5/24/13 10:43 AM, Doug Barton wrote:
> While it's unlikely that I would be able to attend, I think it's an 
> excellent idea for reasons already better stated by others, and BA is 
> a very nice city.
>
> The only suggestion I might add that I haven't seen mentioned yet (and 
> pardon me if I missed it) would be to perhaps schedule the meeting to 
> piggy back on one of the excellent regional meetings that is already 
> well established. Arturo gave a good list, IME LACNIC and LACTLD would 
> be the best/most obvious candidates. By running the IETF meeting 
> either the week before, or the week after one of those meetings we 
> would be able to get quite a bit of cross-pollination, especially with 
> the availability of day passes.
The dates for our meetings are already fixed out to november 2022.
> hth,
>
> Doug
>


From rlb@ipv.sx  Fri May 24 11:06:00 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8B9021F88BF for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[AWL=0.638,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGEIjNTtboSj for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:05:55 -0700 (PDT)
Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by ietfa.amsl.com (Postfix) with ESMTP id B071811E80AD for <ietf@ietf.org>; Fri, 24 May 2013 11:05:53 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id h2so6500423oag.5 for <ietf@ietf.org>; Fri, 24 May 2013 11:05:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=bUXvQu6xLe3f/3tmbapMm7ykNMsZZykEVKKaMZD6ds4=; b=FCFY+DCz3HOzkHrKBXe45jat/vQmVpXqfo02RyaUpZIztqCr0CPbqJf/tdWLVRx4YZ /yWQN7yjawDFJxjO/JctANkjwxMRW/buo56MpMxuNt40pUIheNfbpfqpHW5KLV9wEwAP /fAC6JyzXXpry4Xvtj1MumUIt9lvLaNp0L8fk3PIAl2eVwJIK1HTRjXfEwP4EQp4NRzL ZFLhRkQhobN3dZaBt0+SF5nYvDNFoU4ijWdGuggqpYcNGMQs818WI2SPwtJ3fEb8A3Xd Qf8MJxJEIdzO4hVisarJm7rMoPz7eLIb8boNfSAXDSXI0SO7Lzsi68X+o/HF2Ki6Yl/N dUeg==
MIME-Version: 1.0
X-Received: by 10.182.133.36 with SMTP id oz4mr12657239obb.52.1369418753295; Fri, 24 May 2013 11:05:53 -0700 (PDT)
Received: by 10.60.102.146 with HTTP; Fri, 24 May 2013 11:05:53 -0700 (PDT)
X-Originating-IP: [128.89.254.202]
In-Reply-To: <519FAB64.6030007@bogus.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com>
Date: Fri, 24 May 2013 14:05:53 -0400
Message-ID: <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Richard Barnes <rlb@ipv.sx>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=e89a8ff1ca2456da5704dd7aa673
X-Gm-Message-State: ALoCoQk4qD5QtrDlQM/N6aeJw2yE8kTwDpkVbv8fcFTs64CxnCG7mVktAp6rGjVn0Pe+xbvIDo7g
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:06:01 -0000

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

On Fri, May 24, 2013 at 2:03 PM, joel jaeggli <joelja@bogus.com> wrote:

> On 5/24/13 10:43 AM, Doug Barton wrote:
>
>> While it's unlikely that I would be able to attend, I think it's an
>> excellent idea for reasons already better stated by others, and BA is a
>> very nice city.
>>
>> The only suggestion I might add that I haven't seen mentioned yet (and
>> pardon me if I missed it) would be to perhaps schedule the meeting to piggy
>> back on one of the excellent regional meetings that is already well
>> established. Arturo gave a good list, IME LACNIC and LACTLD would be the
>> best/most obvious candidates. By running the IETF meeting either the week
>> before, or the week after one of those meetings we would be able to get
>> quite a bit of cross-pollination, especially with the availability of day
>> passes.
>>
> The dates for our meetings are already fixed out to november 2022.
>

Given that I don't think there are stone tablets involved, presumably they
could still be moved if there were a good reason.  It's not like people
have already booked plane tickets to BA.



>  hth,
>>
>> Doug
>>
>>
>

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

<div dir=3D"ltr">On Fri, May 24, 2013 at 2:03 PM, joel jaeggli <span dir=3D=
"ltr">&lt;<a href=3D"mailto:joelja@bogus.com" target=3D"_blank">joelja@bogu=
s.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 5/24/13 10:43 AM, Doug =
Barton wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
While it&#39;s unlikely that I would be able to attend, I think it&#39;s an=
 excellent idea for reasons already better stated by others, and BA is a ve=
ry nice city.<br>
<br>
The only suggestion I might add that I haven&#39;t seen mentioned yet (and =
pardon me if I missed it) would be to perhaps schedule the meeting to piggy=
 back on one of the excellent regional meetings that is already well establ=
ished. Arturo gave a good list, IME LACNIC and LACTLD would be the best/mos=
t obvious candidates. By running the IETF meeting either the week before, o=
r the week after one of those meetings we would be able to get quite a bit =
of cross-pollination, especially with the availability of day passes.<br>

</blockquote></div>
The dates for our meetings are already fixed out to november 2022.<br></blo=
ckquote><div><br></div><div>Given that I don&#39;t think there are stone ta=
blets involved, presumably they could still be moved if there were a good r=
eason. =A0It&#39;s not like people have already booked plane tickets to BA.=
</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">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
hth,<br>
<br>
Doug<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div></div>

--e89a8ff1ca2456da5704dd7aa673--

From arturo.servin@gmail.com  Fri May 24 11:08:52 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4B021F968F for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p6iby8Y7HJHS for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:08:47 -0700 (PDT)
Received: from mail-ye0-f175.google.com (mail-ye0-f175.google.com [209.85.213.175]) by ietfa.amsl.com (Postfix) with ESMTP id E867821F93C4 for <ietf@ietf.org>; Fri, 24 May 2013 11:08:46 -0700 (PDT)
Received: by mail-ye0-f175.google.com with SMTP id q1so376023yen.6 for <ietf@ietf.org>; Fri, 24 May 2013 11:08:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AnLFwV0on9365gJoQHQsh+dpNnZ2syDTmyWH3lZ2zX8=; b=PddRpHiAb5dYSYg6XoElO3eHiR4xvVXsNE1JxZ5uKbp8+7ExuwVZF45CfVI4V+geTF IpIega4L4rXbB6t5N6jWMJT8VttDjbP8vFZDsK80P4MPVwxacjyNaYn5y813bZ/07hal knJOoGn4RJcmTUaYftM4e6B3VkXipXnowDq3aL7fXTnScP7hasG5lugFcsMPW2AZo1O9 IxyqmIxdE5ybTWJdGucml+JzSKklw/0Xy9CdyCDTnRqy4eOWqUPMwJo0tw43GKKTBv6g d9YbArPwLKP+yDdrymzhOoySw0qgoYrrYCNJ0BKmgx9EYgJfadrOdza9IDodqfougj+z PTQA==
X-Received: by 10.236.32.140 with SMTP id o12mr10383241yha.15.1369418924979; Fri, 24 May 2013 11:08:44 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:dc04:5fac:21ea:43c4]) by mx.google.com with ESMTPSA id f19sm24159987yhj.3.2013.05.24.11.08.43 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 11:08:44 -0700 (PDT)
Message-ID: <519FACAA.6030703@gmail.com>
Date: Fri, 24 May 2013 15:08:42 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com>
In-Reply-To: <519FAB64.6030007@bogus.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, 24 May 2013 18:08:52 -0000

	Depending on how the IETF in BA is scheduled, it may be possible or not
to make it before or after of a regional meeting such as LACNIC, LACTLD
or LACNOG.

	I guess the best bet is for the third meeting of the year (IETF is
around the beginning of November, LACNOG/LACNIC are around the end or
middle October).

as

On 5/24/13 3:03 PM, joel jaeggli wrote:
> On 5/24/13 10:43 AM, Doug Barton wrote:
>> While it's unlikely that I would be able to attend, I think it's an
>> excellent idea for reasons already better stated by others, and BA is
>> a very nice city.
>>
>> The only suggestion I might add that I haven't seen mentioned yet (and
>> pardon me if I missed it) would be to perhaps schedule the meeting to
>> piggy back on one of the excellent regional meetings that is already
>> well established. Arturo gave a good list, IME LACNIC and LACTLD would
>> be the best/most obvious candidates. By running the IETF meeting
>> either the week before, or the week after one of those meetings we
>> would be able to get quite a bit of cross-pollination, especially with
>> the availability of day passes.
> The dates for our meetings are already fixed out to november 2022.
>> hth,
>>
>> Doug
>>

From jmpolk@cisco.com  Fri May 24 11:21:10 2013
Return-Path: <jmpolk@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 60DC921F94A6 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwnwSOmhp10N for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:21:05 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id DE9B621F949A for <ietf@ietf.org>; Fri, 24 May 2013 11:21:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3718; q=dns/txt; s=iport; t=1369419665; x=1370629265; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=JKoX2n2Pf/zrA+YtevYnAM+78GkY71ZuAd0FTjn5t8M=; b=C0dXn0BUCQJ9ypYvJWRNCSZa7LQcWrFRt62ORIxYZMVBB0AcyGvMEGQA yFgXxzeT+9cGwWk6a/SHhedknCvl1/iWzNJB9UK7fyKukBmEQ3j3i9Um/ eOhF3egc/enMEaWGgtTOyIUxXBpuPwYpASWmeTbGiQZY1PumNAh0a5lpq g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFABevn1GtJXHB/2dsb2JhbABagwjCXoEHFnSCJAEBBDgCPxAHBCEVEA8KPgYBKwKHcrsCjx0Hg1QDiR+IDIIEO5URgy0e
X-IronPort-AV: E=Sophos;i="4.87,736,1363132800"; d="scan'208";a="214737217"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-6.cisco.com with ESMTP; 24 May 2013 18:21:04 +0000
Received: from jmpolk-WS.cisco.com ([10.89.10.72]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r4OIL33S031511 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 18:21:04 GMT
Message-Id: <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 24 May 2013 13:21:03 -0500
To: Jari Arkko <jari.arkko@piuha.net>, The IAOC <bob.hinden@gmail.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: IETF Meeting in South America
In-Reply-To: <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:21:10 -0000

At 05:25 PM 5/23/2013, Jari Arkko wrote:

>For what it is worth, I wanted to provide my perspective on this. I 
>of course believe that it is important that the IETF reaches out to 
>an even more international participation than it already has. This 
>is first of all because we really need the views from different 
>types of organisations and different parts of the world. For 
>instance, I recently had an opportunity to talk to a number of 
>people about peering in different regions. It really opened my eyes 
>about how the Internet experience can differ from what I've been 
>used to so far. We also need to understand how regionally changing 
>requirements for, e.g., emergency communications

I hate to call you out on this point Jari, but... did you know that 
you have a audio/video realtime interactive communications WG 
churning out proposals and solutions that is *actively* ignoring 
"emergency communications" in its entirety? No? Look at RTCweb, which 
will become a dominant form of interactive communications between 
humans in the near future. You have an equally active WG in the same 
area that is addressing emergency communications (ECRIT) that is 
further along/mature in its documents (i.e., they've already produced 
the bulk of their RFCs, specifically RFC 6443 and 6881).

Given that young people already think contacting a local emergency 
call center (PSAP) can or should be achievable through SMS, IM, 
twitter and Facebook... just how long does anyone think it will be 
before calling 911/112/999 will be requested or mandated through WEBrtc/RTCweb?

Waiting will only make it more painful to retrofit it into the future 
RFCs produced by RTCweb.

humbly

James

>or whitespace management affect our work. Finally, our international 
>coverage is not just important for our work but also for how we are 
>perceived. For all of these reasons, reaching out to different parts 
>of the world is important, and one aspect of that is rotating 
>through meeting locations around the world.
>
>I would also like to highlight one part of the message from Bob:
>
> > The IAOC would
> > also like to get feedback on how we can ensure the meeting is as 
> successful as
> > possible and on ways to grow participation in the region.
>
>This is really important, and I hope that we get good feedback on 
>what kinds of things would be useful to do in order to achieve this. 
>That is, we're not just asking a binary question if the meeting is 
>or is not ok.
>
>Just meeting in some place does not bring too many new participants, 
>at least not in a lasting manner. But combined with some other 
>actions, this may be possible. Are there specific companies or 
>research teams that we could reach out to, and who might want to be 
>involved in the IETF? Are there local events where where it would be 
>useful to have someone from the IETF give a talk? Are there specific 
>IETF or IRTF efforts where we could get more people from South 
>America involved? Should the ISOC fellows program target something 
>different than it has so far, or be scaled up? Other ideas?
>
>Jari
>
>P.S. By coincidence, I happened to visit Buenos Aires last year, and 
>found it to be a fun city. I felt safe and despite not speaking the 
>local language I was able to talk to the friendly locals, order 
>food, access the network, acquire a SIM card (albeit with some 
>bureaucratic and technical difficulties, but I think I can still dig 
>up the MNC numbers that were needed to configure the phone correctly 
>:-), use the airports, rent a car, and find a Finnish sauna. I think 
>the city offers all the essential ingredients for life :-)


From joelja@bogus.com  Fri May 24 11:21:42 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A43D611E80D7 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:21:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXCNkZJd8zDP for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:21:41 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A524F11E80D5 for <ietf@ietf.org>; Fri, 24 May 2013 11:21:41 -0700 (PDT)
Received: from joels-MacBook-Air.local (214.sub-70-197-12.myvzw.com [70.197.12.214]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4OILdr4051063 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 24 May 2013 18:21:40 GMT (envelope-from joelja@bogus.com)
Message-ID: <519FAFAF.3060008@bogus.com>
Date: Fri, 24 May 2013 11:21:35 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<519FA6B4.3020007@dougbarton.us>	<519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com>
In-Reply-To: <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@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.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 24 May 2013 18:21:40 +0000 (UTC)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:21:42 -0000

On 5/24/13 11:05 AM, Richard Barnes wrote:
> On Fri, May 24, 2013 at 2:03 PM, joel jaeggli <joelja@bogus.com 
> <mailto:joelja@bogus.com>> wrote:
>
>     On 5/24/13 10:43 AM, Doug Barton wrote:
>
>         While it's unlikely that I would be able to attend, I think
>         it's an excellent idea for reasons already better stated by
>         others, and BA is a very nice city.
>
>         The only suggestion I might add that I haven't seen mentioned
>         yet (and pardon me if I missed it) would be to perhaps
>         schedule the meeting to piggy back on one of the excellent
>         regional meetings that is already well established. Arturo
>         gave a good list, IME LACNIC and LACTLD would be the best/most
>         obvious candidates. By running the IETF meeting either the
>         week before, or the week after one of those meetings we would
>         be able to get quite a bit of cross-pollination, especially
>         with the availability of day passes.
>
>     The dates for our meetings are already fixed out to november 2022.
>
>
> Given that I don't think there are stone tablets involved, presumably 
> they could still be moved if there were a good reason.
The consistent feedback regarding non-conflict as long as I been 
involved in this tends to indicate otherwise. 18-months to 2 years seems 
much more reasonable to me personally.

While there are various sorts of force majeure events that could no 
doubt alter the dates I don't see it as likely that they are otherwise 
flexible. ieee plenary sessions are scehduled out to july 2018 for example.

http://www.ietf.org/meeting/clash-list.html

is long
> It's not like people have already booked plane tickets to BA.
>
>         hth,
>
>         Doug
>
>
>


From dougb@dougbarton.us  Fri May 24 11:24:44 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7681B21F8709 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JHD9-1PVZ5Ke for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:24:42 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2364911E80E0 for <ietf@ietf.org>; Fri, 24 May 2013 11:24:41 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532] (unknown [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532]) by dougbarton.us (Postfix) with ESMTPSA id C8D0F22B42 for <ietf@ietf.org>; Fri, 24 May 2013 18:24:40 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1369419880; bh=6xxWmb88/YneEL8fFyBMF353Nq2f7XPdx58p8W9HIYY=; h=Date:From:To:Subject:References:In-Reply-To; b=RDdJq0HU+W3o995WvpiBRs1iAUztKCvYlfBzN6HQP/5IiI35Ke5gN/ctQNHNxGn/q LIkwRW9iVA+t7trTsJxfKXnqpsil2g/uMWPlGVUOANmcms0q9YTIO5xY69EKQz73DN WRWHQi3D33SecQhVeW3l97CxqWpC+0GZuY+j9JAs=
Message-ID: <519FB068.9050503@dougbarton.us>
Date: Fri, 24 May 2013 11:24:40 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<519FA6B4.3020007@dougbarton.us>	<519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com>
In-Reply-To: <519FAFAF.3060008@bogus.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:24:45 -0000

On 05/24/2013 11:21 AM, joel jaeggli wrote:
> The consistent feedback regarding non-conflict as long as I been
> involved in this tends to indicate otherwise. 18-months to 2 years seems
> much more reasonable to me personally.

Joel,

You're making several fundamental mistakes in your thinking. Rather than 
focusing on all the reasons you think it cannot happen, why not take the 
suggestion for what it was (it would be nice if we could do ...), and 
let the folks who actually do the scheduling decide if the idea is worth 
pursuing, and if so if it is possible.

Doug

From joelja@bogus.com  Fri May 24 11:29:58 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8EE821F8A6B for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:29:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psQgHgYxdxMS for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:29:58 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7A42821F89E2 for <ietf@ietf.org>; Fri, 24 May 2013 11:29:58 -0700 (PDT)
Received: from joels-MacBook-Air.local (214.sub-70-197-12.myvzw.com [70.197.12.214]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4OITu2L051215 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 24 May 2013 18:29:57 GMT (envelope-from joelja@bogus.com)
Message-ID: <519FB1A0.40208@bogus.com>
Date: Fri, 24 May 2013 11:29:52 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<519FA6B4.3020007@dougbarton.us>	<519FAB64.6030007@bogus.com>	<CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com>	<519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us>
In-Reply-To: <519FB068.9050503@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 24 May 2013 18:29:57 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:29:59 -0000

On 5/24/13 11:24 AM, Doug Barton wrote:
> On 05/24/2013 11:21 AM, joel jaeggli wrote:
>> The consistent feedback regarding non-conflict as long as I been
>> involved in this tends to indicate otherwise. 18-months to 2 years seems
>> much more reasonable to me personally.
>
> Joel,
>
> You're making several fundamental mistakes in your thinking. Rather 
> than focusing on all the reasons you think it cannot happen, why not 
> take the suggestion for what it was (it would be nice if we could do ...),
probably because I've been involved in the planning loop since 44.
> and let the folks who actually do the scheduling decide if the idea is 
> worth pursuing, and if so if it is possible.
> Doug
>


From dougb@dougbarton.us  Fri May 24 11:37:50 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E44A611E80A2 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:37:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gVACo7kD8khz for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 11:37:50 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 548DD11E80BA for <ietf@ietf.org>; Fri, 24 May 2013 11:37:50 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532] (unknown [IPv6:2001:470:d:5e7:1d98:49ee:73d0:a532]) by dougbarton.us (Postfix) with ESMTPSA id 15CE922B42 for <ietf@ietf.org>; Fri, 24 May 2013 18:37:50 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1369420670; bh=rG2zQrO9pIaaBBZtzfXmdH5Ry70VpU8ol2XrmEcuXFE=; h=Date:From:To:Subject:References:In-Reply-To; b=WuMBDSBaNpBdPV3+BzRStksOym57ogDP9uGe+NOaFhIWSoqp77rWO4iDOiFITsacz xUBqzz/ySwGvOv6tMLGiJz1LX8lnmoCoTC48W/ti6IhJQwMd8kE93cN2L1fXqzJx0x vPnS4p4/ZMuYKyj3mvYJwb5Jf4eiojwPjrkDHuHA=
Message-ID: <519FB37D.3060604@dougbarton.us>
Date: Fri, 24 May 2013 11:37:49 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<519FA6B4.3020007@dougbarton.us>	<519FAB64.6030007@bogus.com>	<CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com>	<519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com>
In-Reply-To: <519FB1A0.40208@bogus.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 18:37:51 -0000

On 05/24/2013 11:29 AM, joel jaeggli wrote:
> probably because I've been involved in the planning loop since 44.

... and you're also involved in planning for LACNIC, LACTLD, LACNOG, and 
every other regional organization in Latin America that might be 
interested in running their meeting before or after ours?

From joelja@bogus.com  Fri May 24 12:30:29 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A06D521E8086 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 12:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCQ78VncmyI8 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 12:30:29 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 45E9721F8E2C for <ietf@ietf.org>; Fri, 24 May 2013 12:30:29 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4OJURbL052041 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 24 May 2013 19:30:28 GMT (envelope-from joelja@bogus.com)
Message-ID: <519FBFCF.5020202@bogus.com>
Date: Fri, 24 May 2013 12:30:23 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<519FA6B4.3020007@dougbarton.us>	<519FAB64.6030007@bogus.com>	<CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com>	<519FAFAF.3060008@bogus.com>	<519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us>
In-Reply-To: <519FB37D.3060604@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 24 May 2013 19:30:28 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 19:30:29 -0000

On 5/24/13 11:37 AM, Doug Barton wrote:
> On 05/24/2013 11:29 AM, joel jaeggli wrote:
>> probably because I've been involved in the planning loop since 44.
>
> ... and you're also involved in planning for LACNIC, LACTLD, LACNOG, 
> and every other regional organization in Latin America that might be 
> interested in running their meeting before or after ours?
>
The question was whether the IETF dates are fungible. They aren't. I 
would like them to be rather more fungible and I'm apparently in the 
minority. There is a reason why the colocated ieee meeting with the IETF 
occured something like 6 years after it was proposed.

From juliao@braga.eti.br  Fri May 24 12:55:26 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9486A21F9403 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 12:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WTwqsll+7SSl for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 12:55:25 -0700 (PDT)
Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3DF21F93E1 for <ietf@ietf.org>; Fri, 24 May 2013 12:55:25 -0700 (PDT)
Received: by mail-ve0-f171.google.com with SMTP id m1so3705145ves.16 for <ietf@ietf.org>; Fri, 24 May 2013 12:55:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=lVlav+vrFMsAeHs1RiJlxOSeexXIz9XUXOrRX9hKDt8=; b=Buu88OMGPTRLp1pQhdo7jVqocTa+LgDQTLQIe7gNM7sXGfrO7kFIkqcAM5vXDomEqu aEISc0S2A60bZdUYF6l3xSGwft202hiOcsq20mS5qsgr051OWi2lvnfC/jRYYvdRtvul VmfDxtnw8tBkaxIOYwCoUREt/BeVSMIaPNNISRffP4YFW2cnGkhK6m5kMAX9gvXPYfo1 rgRdi6G2d7OUzYFTNn9oafgS9j/0zGE5aJ08xyxtkrbjNCnaNUO8WB5Ydq4XXFxl74zk X/0XP/069uNJ7XuiLPXfAHa5Bg5/7WJeINH4AlQQ44wDF4W+KBqsOVluPbzhjtyLQU1A 2p0A==
X-Received: by 10.52.18.137 with SMTP id w9mr8144380vdd.50.1369425324999; Fri, 24 May 2013 12:55:24 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id nr3sm9910839veb.4.2013.05.24.12.55.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 May 2013 12:55:24 -0700 (PDT)
Message-ID: <519FC5A6.2020601@braga.eti.br>
Date: Fri, 24 May 2013 16:55:18 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [ericas] IETF Meeting in South America
References: <519FA104.5020902@braga.eti.br> <519FA407.8010102@cs.tcd.ie> <519FB707.1020008@braga.eti.br> <519FBD3B.3050904@cs.tcd.ie>
In-Reply-To: <519FBD3B.3050904@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQkEjNwKziH7gC5z70TZelEstgz1zqPUpoHnp8ZyfpzeRyURuixjIKm6gAHDvdCk4p81HWJZ
Cc: j@braga.net.br
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 19:55:26 -0000

Hi Stephen,

Good answers! Now we know about what we are talking. Thank you.

My comments in the text:

Em 24/05/2013 16:19, Stephen Farrell escreveu:
> In my mind at least there's a 0-th level requirement
> that comes before these:
> 
> 0. Make the Internet better by getting more geographically
> diverse, technically good, input and participation.
> 

Perfect!

> And again you do not need to be at meetings to participate.
> Email is fine.
> 
> Of course if you want to do lots of IETF stuff, then getting
> to meetings becomes important.
>

I think this same way, so.

>> 1. What we looking for?
>> 1.1. Realize a IETF below the Equator line (Buenos Aires is a great option)?
>> 1.2. Encouraging people of so-called "emerging countries" to participate
>> in IETF meetings (in person or remotely)?
> 
> 1.2 for me. But I'm also in favour of 1.1, though at a lower
> priority.
> 

I agree.

>>
>> 2. Why?
>> 2.1. (1.2) <=> (1.1)? My answer is NO!
> 
> I don't get that.
>

To encoraging people is necessary to realize meetings below the Equator
line? To realize meetings below the Equator line will encourage people... ?

You ask this question below when you said that geographic is not a
problem. I think so.

>> 2.2. IETF needs more people to work? My answer is YES! Protocols are in
>> change, new technologies (ontologies, Semantic Web, ...), new
>> techniques, etc.
> 
> Sort of. I think we need more people who are technically
> clueful about stuff, for a wide set of different kinds of
> stuff.
> 

Is my opinion, also.

>> 2.3. We want more people to participate, effectively (a.k.a. Melinda
>> three points)? So, what do we need to do?
>>
>> 3. What kind of things should we discuss?
>> 3.1. Costs of travel and stay? In the context of this can be irrelevant
>> (we can participate remotely...). In any place of the world, costs are
>> equivalent, I think.
>> 3.2. Show what do IETF, ISOC, and others for people who do not know yet?
>> 3.3. Food an meals in the IETF meetings?
> 
> Seems ok, but too much focus on your 3.x often distract people
> on IETF lists.
> 

Correct! :)

>> 4. Some observations:
>> 4.1. The personal attendance at meetings of the IETF are falling after
>> year 2000. See the blue line at Figure 3 (Figura 3, in Portuguese) in
> 
> The dot-com bust was the biggest factor in the decline in
> numbers compared to 1999/2000. That was economic (craziness;-)
> and not geographic.
> 

OK.

>> http://ii.blog.br/2013/01/10/ietf-d-58-como-participar-das-reunioes-do-ietf/,
>> at the end. I do not know about the remote participation. The red line
>> is participation of Brazilians (a real disaster!)
> 
> Yeah. Mind you, the level of Irish participation is also
> pretty crappy;-(
> 

If you think that Irish has 6.5 m inhabitants and Brazil about 200 m,
Brazil is much more than a disaster... We where 5 in Orlando.

>> 4.2. The participation of LACNIC is in the last position (2.? %).
>> 4.3. Clearly the issues related to Infrastructure Internet are becoming
>> more complex. (2.2 above).
>>
>> Finally, where should we discuss this? In ericas list or ietf list
> 
> I'd say generic issues here, BA specifics on the thread on the
> IETF list.

Done.

> 
> Cheers,
> S.

Regards,

Juliao

From ole@cisco.com  Fri May 24 13:07:04 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C28A21F8F4A for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 13:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zRPjDf2VDtOq for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 13:06:59 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECD121F8EDF for <ietf@ietf.org>; Fri, 24 May 2013 13:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1842; q=dns/txt; s=iport; t=1369426019; x=1370635619; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=qc5HwoAV/DTglAbzRIw3Ur9mBvLi6STdfbnHfsX5lyw=; b=XSP1gMzCviUdN0s297lqQVnfgH7Rg7WMVOq8TwIAvAgtmCrw/lmApBZ+ d5yO6k6SZvq2h7Lr4s21IEAestB9eCbxAzmwsCedkJw73ltX2W8YPFzwN HTNudVvBdV2D8JeQgDlg79r2l5wWIB30l1q0cEhWhrA1o8706ti6+xNjo 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkcGAAzHn1GrRDoJ/2dsb2JhbABXA4MIMMIugQcWdIIjAQEBAwEYIj8FCwsYLlcGExSHcwW6Vo1rgSIQBxGDQwOJH5Q6hgKFIIMvHIE1
X-IronPort-AV: E=Sophos;i="4.87,737,1363132800"; d="scan'208";a="82019169"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-4.cisco.com with ESMTP; 24 May 2013 20:06:59 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r4OK6vbE028606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 May 2013 20:06:57 GMT
Date: Fri, 24 May 2013 13:06:57 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: IETF Meeting in South America
In-Reply-To: <519FBFCF.5020202@bogus.com>
Message-ID: <alpine.OSX.2.01.1305241253050.44324@rabdullah.local>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 20:07:04 -0000

Joel,

This isn't 100% true. While our dates are not "fungible," we could 
*consider* a date move, say +/- a week *if* this would give us 
availability in a certain location. This would of course be the 
*exception* and not the rule (which you have correct), but *if* we 
found that, say, moving IETF 127 one week would make everything work 
perfectly, then, yes, we *could* do it. Of course, this would have to 
be done FAR in advance and with ample community input, just like we 
are doing for the South America survey.

(Recall some recent discussion about moving a meeting to avoid some 
holiday [Easter as I recall].)

But you are generally right: our dates are fixed for mostly all good
reasons, it's just that sometimes we find that this can also be to
our detriment. If we are looking ahead several years, I can well 
imagine some negotiation, say with an RIR meeting, etc, etc.

Ole

Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


On Fri, 24 May 2013, joel jaeggli wrote:

> On 5/24/13 11:37 AM, Doug Barton wrote:
> > On 05/24/2013 11:29 AM, joel jaeggli wrote:
> > > probably because I've been involved in the planning loop since 44.
> >
> > ... and you're also involved in planning for LACNIC, LACTLD, LACNOG, and
> > every other regional organization in Latin America that might be interested
> > in running their meeting before or after ours?
> >
> The question was whether the IETF dates are fungible. They aren't. I would
> like them to be rather more fungible and I'm apparently in the minority. There
> is a reason why the colocated ieee meeting with the IETF occured something
> like 6 years after it was proposed.
> 
> 

From pthaler@broadcom.com  Fri May 24 15:27:12 2013
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8864611E80FD for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 15:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0mFWIR9iRDc for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 15:27:08 -0700 (PDT)
Received: from mms3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by ietfa.amsl.com (Postfix) with ESMTP id 2C08311E80F9 for <ietf@ietf.org>; Fri, 24 May 2013 15:27:08 -0700 (PDT)
Received: from [10.9.208.55] by mms3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.5)); Fri, 24 May 2013 15:18:15 -0700
X-Server-Uuid: B86B6450-0931-4310-942E-F00ED04CA7AF
Received: from SJEXCHCAS03.corp.ad.broadcom.com (10.16.203.8) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.1.438.0; Fri, 24 May 2013 15:26:47 -0700
Received: from SJEXCHMB09.corp.ad.broadcom.com ( [fe80::3da7:665e:cc78:181f]) by SJEXCHCAS03.corp.ad.broadcom.com ( [::1]) with mapi id 14.01.0438.000; Fri, 24 May 2013 15:26:47 -0700
From: "Pat Thaler" <pthaler@broadcom.com>
To: "Michael Richardson" <mcr+ietf@sandelman.ca>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV84YF/rrSmWtoUqGUFNgQUr50JkU1zGAgAAIfcA=
Date: Fri, 24 May 2013 22:26:45 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672ADB99EC@SJEXCHMB09.corp.ad.broadcom.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca>
In-Reply-To: <16454.1369404751@sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
MIME-Version: 1.0
X-WSS-ID: 7D8138AD2L822429390-01-01
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 22:27:12 -0000

Carnival is usually around March (I think it moves around being linked to E=
aster like Mardi Gras). I priced flights for November and July from Norther=
n California and it looks like there would be option at less than my travel=
 to Berlin (and about 2 to 3 times travel to East Coast North America). Tra=
vel time is a longer than for Europe at about 24 hours, but not outrageousl=
y longer. I didn't try to price March because it is hard to get a feel for =
prices so far in advance - the airline isn't yet adjusting them for capacit=
y.

Pat

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mic=
hael Richardson
Sent: Friday, May 24, 2013 7:13 AM
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America


>>>>> "The" =3D=3D The IAOC <bob.hinden@gmail.com> writes:
    The> The venues are in Buenos Aires.  They meet our requirements for th=
e meeting
    The> space, networking, nearby restaurants and bars, hotel room rates i=
n the mid $200
    The> dollar range, nearby alternate hotels at a broad range of prices, =
nice area in the
    The> city, safe, direct international flights, and accessible visas.  T=
he IAOC thinks we
    The> could have a successful IETF meeting in Buenos Aires and that atte=
ndees would
    The> like the venues.

My question is about whether we would be there during the "peak" season,
and when exactly is that season?

I priced flights for me in July, November and March (2014).
It seems that most flights go through Santiago or Sao Paulo, one went
through Atlanta.  The lowest cost flight for me is similiar to travel to
Europe not in the summer,  but the price rises quite quickly to the $4K
range.  The worse rise seems to be March, but that was also the furthest
in the future.

    The> Things to consider are that it will be a long trip for the majorit=
y of IETFers and the
    The> air fares are more expensive (about 10% to 20% higher than average=
), though
    The> restaurants are less expensive.  This would be a case where most I=
ETFers would
    The> bear more travel pain and expense. =20

What are the hotel costs?  =20
(I fund my own attendance)

--=20
]               Never tell me the odds!                 | ipv6 mesh network=
s [=20
]   Michael Richardson, Sandelman Software Works        | network architect=
  [=20
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [=20
=09



From vinayakh@gmail.com  Fri May 24 16:23:07 2013
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F70D21F9579 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 16:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5AIUOnubRO52 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 16:23:06 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1C521F960D for <ietf@ietf.org>; Fri, 24 May 2013 16:23:06 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so4777741pbb.34 for <ietf@ietf.org>; Fri, 24 May 2013 16:23:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V9ZpqBQJQZsPoFRDZPbafjSLHXPCwyYoQQlc91n6iIU=; b=GxxJ09/9zf2YWdB7qyjHY8ygrw8u8o0lo2upBKUaFofP9E4ToGQ3hNnNEgzW3T/mAV uQ7YRlqwlRroeS18SeFy4El3tJd7d2KrNbolEMyvO3jlraM2jHJAMoKSS3A1cJbVM/1S NskuFS0Zb5WIWxDhEid/VmFXGM/TiNVKFKe4Wjmwcn/iwjZ+c6OY/UbbAcS6MhMBN9Mk ss6XsIUP19MSd+VKlQvCH4gjoB+9GdCQ3Tx+2TCFKsB3uVMKt3QEg29fWyxXtaPmLneG E4qMJ5uOud8uDsnF+hWN2VdNJxSjSUdJLbuM4q3Q8rIzKBvfRuCtt91cNxvwymcL9mUH cw3A==
MIME-Version: 1.0
X-Received: by 10.68.219.70 with SMTP id pm6mr19801111pbc.154.1369437786098; Fri, 24 May 2013 16:23:06 -0700 (PDT)
Received: by 10.66.156.234 with HTTP; Fri, 24 May 2013 16:23:05 -0700 (PDT)
In-Reply-To: <519FA4AF.60600@gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <16454.1369404751@sandelman.ca> <9B03647D-7E19-42DB-B771-83720914D737@checkpoint.com> <519F9028.50601@labn.net> <519F92D6.3040609@gmail.com> <519FA4AF.60600@gmail.com>
Date: Sat, 25 May 2013 04:53:05 +0530
Message-ID: <CAKe6YvPo0gXKf2iwqvjBUoKoGZhE4Zh2wMTaeyUZyWrNPAkQnQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Vinayak Hegde <vinayakh@gmail.com>
To: Arturo Servin <arturo.servin@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2edff3c850e004dd7f14e6
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, 24 May 2013 23:23:07 -0000

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

On Fri, May 24, 2013 at 11:04 PM, Arturo Servin <arturo.servin@gmail.com>wrote:

>
>         I have been lurking IETF for many years, but it was only after I
> went
> to my first meeting that I really understood how the IETF worked and how
> to really participate.
>
>         After that meeting I started to send comments, read drafts, writing
> some initial stuff and arguing. Before that meeting I didn't know how to
> do it, and how good or bad my comments would be received. I think it
> might be cultural, but before my first meeting I felt a bit intimidated
> by the ietf and being flamed by a bad comment.
>
>         I didn't stop feeling intimidated after the first meeting, it took
> me a
> bit more but definitely it helped me to understand the ietf, its
> community and how to participate.
>
>         I wouldn't be surprised if it were many people just like I was,
> lurking
> the email lists but have never sent anything for the same reasons that I
> did.
>

+1

Couple more obesrevations:

1. I was lurking on the mailing list for sometime before I could get enough
context to even comment. Also much of the content in IETF is trapped in
people's heads. Even after reading the drafts on tools/datatracker AND
following the mailing lists, sometimes it may not be clear why the design
decisions have been made. The archived mailing list format (that can
sometimes help) is not pretty to read or follow. There is not much that can
be dome about it. It is just the nature of email communication. This is
especially true if the area is adjunct (to your domain knowledge) or
somewhat new to you.

2. The directness of communication can be jarring for people from some
cultures where deference and politeness are more important that being
right. The fact that several Asians are contributing to IETF means that
this barrier can be overcome. But it is harder when you do not know anyone
whom you can connect to. Maybe some handholding / mentoring (even remotely)
might help.

There are unfortunately no easy answers for both 1 & 2.

-- Vinayak

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

<div class=3D"gmail_quote">On Fri, May 24, 2013 at 11:04 PM, Arturo Servin =
<span dir=3D"ltr">&lt;<a href=3D"mailto:arturo.servin@gmail.com" target=3D"=
_blank">arturo.servin@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">
<br>
=A0 =A0 =A0 =A0 I have been lurking IETF for many years, but it was only af=
ter I went<br>
to my first meeting that I really understood how the IETF worked and how<br=
>
to really participate.<br>
<br>
=A0 =A0 =A0 =A0 After that meeting I started to send comments, read drafts,=
 writing<br>
some initial stuff and arguing. Before that meeting I didn&#39;t know how t=
o<br>
do it, and how good or bad my comments would be received. I think it<br>
might be cultural, but before my first meeting I felt a bit intimidated<br>
by the ietf and being flamed by a bad comment.<br>
<br>
=A0 =A0 =A0 =A0 I didn&#39;t stop feeling intimidated after the first meeti=
ng, it took me a<br>
bit more but definitely it helped me to understand the ietf, its<br>
community and how to participate.<br>
<br>
=A0 =A0 =A0 =A0 I wouldn&#39;t be surprised if it were many people just lik=
e I was, lurking<br>
the email lists but have never sent anything for the same reasons that I<br=
>
did.<br></blockquote><div><br>+1 <br><br>Couple more obesrevations:<br><br>=
1. I was lurking on the mailing list for sometime before I could get enough=
 context to even comment. Also much of the content in IETF is trapped in pe=
ople&#39;s heads. Even after reading the drafts on tools/datatracker AND fo=
llowing the mailing lists, sometimes it may not be clear why the design dec=
isions have been made. The archived mailing list format (that can sometimes=
 help) is not pretty to read or follow. There is not much that can be dome =
about it. It is just the nature of email communication. This is especially =
true if the area is adjunct (to your domain knowledge) or somewhat new to y=
ou.<br>
<br>2. The directness of communication can be jarring for people from some =
cultures where deference and politeness are more important that being right=
. The fact that several Asians are contributing to IETF means that this bar=
rier can be overcome. But it is harder when you do not know anyone whom you=
 can connect to. Maybe some handholding / mentoring (even remotely) might h=
elp.<br>
<br>There are unfortunately no easy answers for both 1 &amp; 2.<br><br>-- V=
inayak<br></div></div>

--047d7b2edff3c850e004dd7f14e6--

From johnl@iecc.com  Fri May 24 16:38:48 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB2111E80F9 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 16:38:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.068
X-Spam-Level: 
X-Spam-Status: No, score=-111.068 tagged_above=-999 required=5 tests=[AWL=0.131, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XxwqkWOMLWDt for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 16:38:44 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CE97711E80D2 for <ietf@ietf.org>; Fri, 24 May 2013 16:38:43 -0700 (PDT)
Received: (qmail 16106 invoked from network); 24 May 2013 23:38:40 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 May 2013 23:38:40 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519ffa00.xn--hew.k1305; i=johnl@user.iecc.com; bh=7E5vc4At7vzf3UYtPIpTFrEMOchG6cI4vfCzeUfVLAA=; b=m5IyneDlC3Wmu80i6/e1o2aBPybejF/rbhYXObRbJHPF9ccUDqAEqjvMPoXBw40wmnaWDkgFhPyN2qmSvNeZWRgKSV0SDMNrnRONxkCNtompjII2in5HBQIbmA70zg/aDVyJ1Ez1PHsz3h0lgdzB9+CfynyFFYnjJ3zdEMBMRis=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519ffa00.xn--hew.k1305; olt=johnl@user.iecc.com; bh=7E5vc4At7vzf3UYtPIpTFrEMOchG6cI4vfCzeUfVLAA=; b=Wjq72gsFXc+SvxNQRxMdhVyUg6McGWajQvEZ83Dkvpi51CQsjFnxDL9thL05Y934P3GEaJNdGJ51sQl19SKlZaNXCUQo4+idRU7q68IjvGO7FXfZ8ZYrUQugrntT/dHpxEnJa7ZK70G5OWCtqzNqxrSUyQqamigoQH25rttw80c=
Date: 24 May 2013 23:38:18 -0000
Message-ID: <20130524233818.80754.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Meeting in North America
In-Reply-To: <519FA5C3.1020403@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 23:38:48 -0000

>Feh.  There is no winter in Vancouver.  On the other hand there are
>salmon and steelhead.

I distinctly remember a meeting in Vancouver where certain attendees
were complaining about the winter weather, with temperatures plunging
below zero* and snow drifting 1 to 2*.  

The specific complaint was that this made it uncomfortable to wear
sandals.

R's,
John


* - we're engineers, that would be celsius and centimetres



From johnl@iecc.com  Fri May 24 16:47:59 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12A0521F9452 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 16:47:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.075
X-Spam-Level: 
X-Spam-Status: No, score=-111.075 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, UPPERCASE_50_75=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qsMAY25Wumd3 for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 16:47:55 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B52C321F958D for <ietf@ietf.org>; Fri, 24 May 2013 16:47:54 -0700 (PDT)
Received: (qmail 17791 invoked from network); 24 May 2013 23:47:53 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 May 2013 23:47:53 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519ffc29.xn--i8sz2z.k1305; i=johnl@user.iecc.com; bh=VK/7BdfggGHmIjOjSPQYWyxz6huSJlqvWhqZgCJ8kVc=; b=MRp3qTkMyoeqm4lQlfvTCcBbIZrUaKzUBpk+65GB7iEKLtzBCB3ES5Q54oNFWEHalDQSoFiZeHQPRa4ohWmNrFTL1b2WhUFnObWhdCNIo1vtuwUJYULqkLIPTri4lCfYlKmT7n9HYPwOkeUWbvmPFSB3edWD7jL3GK30oajA5Ts=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=519ffc29.xn--i8sz2z.k1305; olt=johnl@user.iecc.com; bh=VK/7BdfggGHmIjOjSPQYWyxz6huSJlqvWhqZgCJ8kVc=; b=XP/TLAszbnM7e03Pg+oZsgjhC21+aZlLxpmZc3dEAS89XGC2SHdWVk1x+jbTTEc2Ohm4a54HwnCo1YZL4nTzbQ+8JTEf1tP3EJPvxK4Af9wA5K84XtyVuNEOGa7aKI4a2i9MtKYodMP/iBMDe2689K1UlK1i/gtY8lTYQl9ueA0=
Date: 24 May 2013 23:47:31 -0000
Message-ID: <20130524234731.80792.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
In-Reply-To: <16454.1369404751@sandelman.ca>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 23:47:59 -0000

>My question is about whether we would be there during the "peak" season,
>and when exactly is that season?

I gather you're in Ottawa.  Here's Air Canada's calendar rules for
their lowest fare to EZE:

 ORIGINATING CANADA -
     PERMITTED 01JAN THROUGH 08JUL OR 06AUG THROUGH 16SEP
     OR 01OCT THROUGH 16DEC OR 24DEC THROUGH 31DEC ON THE
     FIRST INTERNATIONAL SECTOR. SEASON IS BASED ON DATE
     OF ORIGIN.

   ORIGINATING ARGENTINA -
     PERMITTED 13JAN THROUGH 30JUN OR 21JUL THROUGH 02SEP
     OR 17SEP THROUGH 01JAN ON THE FIRST INTERNATIONAL
     SECTOR. SEASON IS BASED ON DATE OF ORIGIN.

I checked some US cities, turned out the cheapest fares were also
AC (rather an odd routing if you're starting at LAX but think of
all those miles) and the dates are:

  ORIGINATING UNITED STATES -
     PERMITTED 01FEB THROUGH 13JUL OR 04SEP THROUGH 30NOV
     ON THE FIRST INTERNATIONAL SECTOR. SEASON IS BASED
     ON DATE OF ORIGIN.

   ORIGINATING ARGENTINA -
     PERMITTED 17SEP THROUGH 31DEC OR 27JAN THROUGH 22FEB
     OR 01APR THROUGH 20JUN ON THE FIRST INTERNATIONAL
     SECTOR. SEASON IS BASED ON DATE OF ORIGIN.

I don't know what happens in B.A. in July and August in the middle of
the winter.  The cheapest fares from Paris have no calendar limits.
The cheapest fares from Frankfurt are only good Aug-Oct.  Go figure.



From jari.arkko@piuha.net  Sat May 25 00:10:16 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3344F21F901A for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 00:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmlPa3vLaIhT for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 00:10:11 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 9475C21F8FEC for <ietf@ietf.org>; Sat, 25 May 2013 00:10:10 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5A53D2CC48; Sat, 25 May 2013 10:10:08 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zj_lb58DD9rX; Sat, 25 May 2013 10:10:07 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 497702CC3C; Sat, 25 May 2013 10:10:07 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com>
Date: Sat, 25 May 2013 10:10:07 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com>
To: James Polk <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2013 07:10:16 -0000

James:

> did you know that you have a audio/video realtime interactive =
communications WG churning out proposals and solutions that is =
*actively* ignoring "emergency communications" in its entirety? No? Look =
at RTCweb, which will become a dominant form of interactive =
communications between humans in the near future. You have an equally =
active WG in the same area that is addressing emergency communications =
(ECRIT) that is further along/mature in its documents (i.e., they've =
already produced the bulk of their RFCs, specifically RFC 6443 and =
6881).
>=20
> Given that young people already think contacting a local emergency =
call center (PSAP) can or should be achievable through SMS, IM, twitter =
and Facebook... just how long does anyone think it will be before =
calling 911/112/999 will be requested or mandated through WEBrtc/RTCweb?
>=20
> Waiting will only make it more painful to retrofit it into the future =
RFCs produced by RTCweb.

I knew that WebRTC is happening fast, including implementations coming =
out before standards. I don't think everyone have yet realised the full =
impact this technology will have.

I didn't know about the details of the emergency communications =
situation. But it is always difficult to balance getting something out =
early vs. complete. I know how much pressure there is on the working =
groups to keep up with things actually happening in the browsers and =
organisations setting up to use this technology. Do you think the =
retrofit will be problematic, and do you have a specific suggestion =
about what should be included today?

Jari


From adrian@olddog.co.uk  Sat May 25 03:20:14 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880D021F8FA9 for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 03:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.341
X-Spam-Level: 
X-Spam-Status: No, score=-2.341 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lAFbCjdWi389 for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 03:20:09 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 91CA121F9017 for <ietf@ietf.org>; Sat, 25 May 2013 03:20:08 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4PAK6oJ002255;  Sat, 25 May 2013 11:20:06 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4PAK5I5002247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 25 May 2013 11:20:05 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20130525012629.27814.9963.idtracker@ietfa.amsl.com>
In-Reply-To: <20130525012629.27814.9963.idtracker@ietfa.amsl.com>
Subject: RE: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>	(Requirements for	GMPLS applications of PCE) to Informational RFC
Date: Sat, 25 May 2013 11:20:04 +0100
Message-ID: <07b701ce5931$6c93acd0$45bb0670$@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: AQFqCM6wK8Jj72Y/bcq1okRvzWE3YZneULDA
Content-Language: en-gb
Cc: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 May 2013 10:20:14 -0000

Hi,

Here are my review comments as responsible AD. Because they are minor comments,
I am entering them as part of IETF last call rather than getting them fixed
before last call. That should expedite the publication a little.

Thanks,
Adrian

===

idnits shows a couple of issues with your references

  == Unused Reference: 'RFC3945' is defined on line 373, but no explicit
     reference was found in the text

  == Unused Reference: 'RFC4927' is defined on line 402, but no explicit
     reference was found in the text

These both seem like relevant references and I suggest that you find a 
place in the text to point to them.

---

Some work on acronyms, please.

PCE needs to be expanded on first use in the Abstract and the main text
(not on the second use :-)

OTOH, MPLS and GMPLS do not need to be expanded.

PCC shows up in section 2.1
PCReq and PCRep are in 2.1 (but expanded a little later)
P2MP is in section 2.2
ERO and XRO show in section 3.1
PCEP shows in section 3.2


---

Section 1 para 4 seems to say that SRLG is covered in RFC 3473. Are you
sure? Or do you need a different reference?

---

In Section 3.1 reqs (1), (2) and (3) you appear to be limiting the
supported values to only those listed or those in the referenced RFCs.

You may do better to say less. Just point at the base definition of the
signaling fields (in RFC 3473?) and then say "all current and future 
values".

---

Section 6

Julien Meuric not Meulic

> -----Original Message-----
> From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 25 May 2013 02:26
> To: IETF-Announce
> Cc: pce@ietf.org
> Subject: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt> (Requirements
for
> GMPLS applications of PCE) to Informational RFC
> 
> 
> The IESG has received a request from the Path Computation Element WG
> (pce) to consider the following document:
> - 'Requirements for GMPLS applications of PCE'
>   <draft-ietf-pce-gmpls-aps-req-07.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-07. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
>    The initial effort of the PCE WG is specifically focused on MPLS
>    (Multi-protocol label switching).  As a next step, this draft
>    describes functional requirements for GMPLS (Generalized MPLS)
>    application of PCE (Path computation element).
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/ballot/
> 
> 
> The following IPR Declarations may be related to this I-D:
> 
>    http://datatracker.ietf.org/ipr/1869/
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


From john-ietf@jck.com  Sat May 25 07:19:05 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8D8421F8AD1 for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 07:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.634
X-Spam-Level: 
X-Spam-Status: No, score=-102.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MCdM+X8WFTs for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 07:19:00 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA3B21F8763 for <ietf@ietf.org>; Sat, 25 May 2013 07:18:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UgFJB-000JNJ-1O; Sat, 25 May 2013 10:18:57 -0400
Date: Sat, 25 May 2013 10:18:51 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, James Polk <jmpolk@cisco.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South	America)
Message-ID: <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com>
In-Reply-To: <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "ietf@ietf.org 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, 25 May 2013 14:19:06 -0000

--On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

>...
> I didn't know about the details of the emergency
> communications situation. But it is always difficult to
> balance getting something out early vs. complete. I know how
> much pressure there is on the working groups to keep up with
> things actually happening in the browsers and organisations
> setting up to use this technology. Do you think the retrofit
> will be problematic, and do you have a specific suggestion
> about what should be included today?

Jari,

James will probably have a different answer and perspective, but
I suggest that retrofits of security-sensitive features are so
often problematic to make "always" not much of an exaggeration.  

I don't think there is any general solution to the "early vs.
complete" tradeoff [1], nor, as long as we keep trying to deal
with things as collections of disconnected pieces rather than
systems, to the issues created by WGs with significant overlaps
in either scope or technology.  What I think we can do is to be
particularly vigilant to be sure that the two WGs are tracking
and frequently reviewing each other's work.   At least RTCWEB
and ECRIT are in the same area, which should make that
coordination easier than it might be otherwise.

   john


[1] Watch for a note about this that I've been trying to
organize for about two weeks and hope to finish and post this
weekend.




From abdussalambaryun@gmail.com  Sat May 25 11:17:10 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A5D821F898B for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 11:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level: 
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsZDNaWXbr+x for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 11:17:05 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id 41FFE21F8519 for <ietf@ietf.org>; Sat, 25 May 2013 11:17:05 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id bv13so3416528pdb.12 for <ietf@ietf.org>; Sat, 25 May 2013 11:17:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=dkVMtYzGRQ7B+OON0laUNHtKaO5WcLLBYlBXiZZYrGo=; b=U2YRQzDV+Y8nDBk4GmQl+OaS5Lm1NL/mWfwOmDEX0/wtTIYEAx7EQ0rm52UkLfdam5 ZMF9oKlGEmc4pVHL7r6F54B67MjQOJ4BKPjxlg8czXJ9LN70mcmUNH1D+r69QsXVOHs5 QuU0wTJFOvgYyFEK+kMymVzeiAfdxxAQa9XgE7Y5VdSvoXfta0tbYRaZeeGuUG86tJV4 dEumxNqgJ1Lpg+OytB/M+W1FLdwFxDb2g8mu1clC8gMDHws8Yn/Hw1z7ACRoNGVPBke8 nGgpjY3QY5Xe8BghUO/oSSNuo7VXEIUEbyN7tl+tiheVEG+QhHD+dANGg27MhmA+BQ6w 7byg==
MIME-Version: 1.0
X-Received: by 10.68.113.101 with SMTP id ix5mr23089324pbb.142.1369505824905;  Sat, 25 May 2013 11:17:04 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sat, 25 May 2013 11:17:04 -0700 (PDT)
Date: Sat, 25 May 2013 20:17:04 +0200
Message-ID: <CADnDZ89DzhKwc2JWFhOMetL-cZqo71GjGiBZuiQMNBWZoxCLcQ@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 May 2013 18:17:10 -0000

> I don't think there is any general solution to the "early vs.
> complete" tradeoff [1],

IMHO, that general answer is; having good organisation or management
from all parts participants, discussion chairs and from directors.

> nor, as long as we keep trying to deal
> with things as collections of disconnected pieces rather than
> systems, to the issues created by WGs with significant overlaps
> in either scope or technology.

It is good to have systems that is why we need WGs with procedures,
and it is good to have collections-of-ideas (can be disconnected) that
is why we need diversed participants in each system/WG.

I am against the disconnection idea of pieces/work, we need both
connection and disconnection. The pieces SHOULD be always connected as
long it serves the same subject/issue/scope, but can disconnected when
we look into applications/projects.

>  What I think we can do is to be
> particularly vigilant to be sure that the two WGs are tracking
> and frequently reviewing each other's work.   At least RTCWEB
> and ECRIT are in the same area, which should make that
> coordination easier than it might be otherwise.

>From my new monitoring/experience of IETF, I don't think same area WGs
are coordinated in working related to their pieces. Management SHOULD
organise such coordination.

AB
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This message is not sent to private address, only sent to IETF.
My thoughts are writen in a message for the IETF not for other party,
if you want to comment on the thoughts, please comment on the message
idea/content not on the author or his/her thoughts/methods.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

>
>
> [1] Watch for a note about this that I've been trying to
> organize for about two weeks and hope to finish and post this
> weekend.
>

From abdussalambaryun@gmail.com  Sat May 25 11:32:40 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6962021F89A6 for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 11:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.167
X-Spam-Level: 
X-Spam-Status: No, score=-3.167 tagged_above=-999 required=5 tests=[AWL=0.432,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z2jdqo9FRRS0 for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 11:32:35 -0700 (PDT)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by ietfa.amsl.com (Postfix) with ESMTP id 5007221F898B for <ietf@ietf.org>; Sat, 25 May 2013 11:32:35 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kl12so2006192pab.6 for <ietf@ietf.org>; Sat, 25 May 2013 11:32:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DhB+agBYaLkQEvPt7Mep4cuJzYRMd3Sd/WmY7xaBKYE=; b=Ak/KcGDUtcMYMC1JnCiKhE7df1MHuaL1xPuYZR1DcDoib6t/dL6OB3keXat4msUldV d7gdDtXdoAZVVigG04qUVpmRxWKuhW3OWySSEqknsb4j+m/K54JSr33dyCMZyFgUiCaa Z5a5kFY0WJE5UFDsbRyeMab/YpJz5p6hHiOVunoPeio0SAU0ISPevjn2KliL4TPKwhZI jIlMJK9hHdE8UG+i24oVwPpNLh7iGk4bXD1ddLgijCBd4f7rPJccxZ0b+dLgtyJIA+ws o0rd7IwJjYOeAjm1sYLmgJfLGWSO1If9Avw+3UEbHX1GEl8AKHwzDlgiFca0HTkFprXx /ddA==
MIME-Version: 1.0
X-Received: by 10.68.103.194 with SMTP id fy2mr22810314pbb.158.1369506755100;  Sat, 25 May 2013 11:32:35 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sat, 25 May 2013 11:32:35 -0700 (PDT)
Date: Sat, 25 May 2013 20:32:35 +0200
Message-ID: <CADnDZ8_TpFa7sNvcvJef5FhD4ndRzvnYgr7cVuew8ccHoz+25g@mail.gmail.com>
Subject: General Comment on AD Review or IESG Review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 May 2013 18:32:40 -0000

Hi

Just small comment on the AD review, and to show my expectation. I
hope to know your expectations of reviews. If we know the expectations
of the community we will progress better.

I expect that the AD review overviews all I-D pieces and also all the
WG participants input within the WGLC. IMHO, I don't expect that the
AD just uses participants input without refering to such input/piece.
We need connected pieces, not disconnected because the review is for
one work I-D.

I expect that IESG review overviews all I-D pieces and also the IETF
participants input within the IETF Last Call. We need connected
pieces, not disconnected because the review is for one work I-D.

I like to make my review connected and disconnected to other people's
ideas other pieces of work.

AB
+++++++++++++++++++++++++++++++++++++++++++++++++++++
This message is not sent to private address, this is only sent to
IETF. However, the author accepts private or public replies as long it
is respectful.
+++++++++++++++++++++++++++++++++++++++++++++++++++++

From abdussalambaryun@gmail.com  Sat May 25 21:40:58 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA71021F8B45 for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 21:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3lGHAzEiLUV for <ietf@ietfa.amsl.com>; Sat, 25 May 2013 21:40:58 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7798C21F8F43 for <ietf@ietf.org>; Sat, 25 May 2013 21:40:50 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id xb12so5694303pbc.28 for <ietf@ietf.org>; Sat, 25 May 2013 21:40:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=CY0aRIvRipA+hlBvW1kGHwSd6L2P2x8mZGCd8x+wHxc=; b=hvSKnauWENB/4STE2HCbQdrLYNiOSvjt5CbGfC2D+FedOM8hWdtyZNpxgoRFY5DKDK Ujp9uUcKZyG+Ij7+lcyH2XYNVhGrtLQvZLvPG8ckmbVjdM0yTbQkyV6EVFEjbKu41tY3 dWwAGVRdiUEs+Q5yRgV3oqmm599mWwgTrmpubiSUeRz1QwgsdUmih6Ouz/6Rkngsqko1 YM7Umi6vmqTw8SaqSPEYfX3e9iB/HF2yOrx+FLwFy67+FHW6yF5iTiUeA7g1rWG+4LLD nZCkKQiSNKejfkXxI/sd7G7QwUM4rJg1FpDbZVGJPiLyTRUGyBNVZu6Bpk/9R7icHdbs rpaw==
MIME-Version: 1.0
X-Received: by 10.66.158.234 with SMTP id wx10mr24490329pab.43.1369543250242;  Sat, 25 May 2013 21:40:50 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sat, 25 May 2013 21:40:50 -0700 (PDT)
In-Reply-To: <CADnDZ8_TpFa7sNvcvJef5FhD4ndRzvnYgr7cVuew8ccHoz+25g@mail.gmail.com>
References: <CADnDZ8_TpFa7sNvcvJef5FhD4ndRzvnYgr7cVuew8ccHoz+25g@mail.gmail.com>
Date: Sun, 26 May 2013 06:40:50 +0200
Message-ID: <CADnDZ8_miwgsjxmLGi_M0DX5U_2d9XtqxM0bD_QQ9gqH7UPOtQ@mail.gmail.com>
Subject: Re: General Comment on AD Review or IESG Review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 May 2013 04:40:58 -0000

Connecting ideas related to the same I-D is not an easy task, usually
reviewers just do their own review without reading others. I try to
read all reviews (if time is available) or input related to I-D to
connect ideas to help in better my review results or quality.

 I recommend that such connection/coordination of reviews should be
done in the IETF-Area level for WGLC-reviews and AD-review, and then
done in the IESG level for ietf-reviews and editors-reply. This way
the final review for the Area and for the IESG will get better
results.

When we work as a team we will be connecting good ideas (may include
cross areas) to get to the best quality and final team work idea.

AB

From dhc@dcrocker.net  Sun May 26 09:42:50 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA48021F8D90 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 09:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eAHeNQyICNM1 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 09:42:46 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6F57021F8C40 for <ietf@ietf.org>; Sun, 26 May 2013 09:42:46 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4QGgeEp002247 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 26 May 2013 09:42:45 -0700
Message-ID: <51A23B7F.3050702@dcrocker.net>
Date: Sun, 26 May 2013 18:42:39 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com>
In-Reply-To: <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 26 May 2013 09:42:46 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2013 16:42:50 -0000

The IAOC has put forward two reasons for having an IETF meeting in South 
America:

> Encouraging growing participation will help strengthen the Internet,
> further encourage participation from those areas that will see the
> most growth in the coming years, and will help advance the IETF in
> political and international circles which is becoming more of an
> imperative.

That is:

1. Promoting regional participation from Latin America

    There certainly are under-represented constituencies that we should 
find ways to bring to the IETF in greater numbers.  Residents of Latin 
America certainly qualify.

    However a number of comments on the ietf list have observed that our 
conducting a single meeting in South America is unlikely to effect 
greater Latin participation in the IETF.  I agree, it won't, and frankly 
I think it shouldn't, because it's a expensive and possibly risky Grand 
Gesture rather than a substantive change.

    If we want great regional participation, let's look for ways to 
achieve that -- for /all/ under-represented constituencies.  I suspect 
that what's needed will be similar for all of them.


2. Counteracting some type of IETF 'deficiency' in political and 
international circles.

    As stated, that's a pretty vague concern, although yes, we sometimes 
hear criticisms around the IETF's regional choices. However the nature 
of exchanges like these are -- as correctly characterized by the IAOC -- 
political, and they are rarely assuaged by letting the critics dictate 
organizational decision-making, such as where to send 1200 participants 
for a mission-critical meeting.

    Put simply: we shouldn't let political critics set the agenda for 
IETF strategic planning.  They'll just find something else to hassle us 
about, since their political goal is criticizing the IETF, not improving 
it.  Again as others have noted, one meeting in the region won't be 
enough, and then there are the other regions we don't go to, and there 
will be something else, and something more after that.

    But wait. There's a bigger issue being missed: The basis of the 
criticism is fundamentally specious!  The /reality/ is that the IETF is 
dramatically /more/ open in its participation and its documents than 
nearly any other international standards group, most of whom have 
nation- or vendor-based membership fees and restrictions, with little or 
no participation via email or remote attendance.

    Again, don't let political exercises determine the IETF's public 
message. The solid reality of extreme IETF global inclusiveness is real 
and basic. Those who want to hear that message will.  Those who don't 
won't be quieted by a stray meeting in the southern half of South America.

     Of course we need to do more and better at being inclusive.  The 
nascent diversity effort speaks to the IETF's own concern about that.



As for some other points in the IAOC message...


On 5/23/2013 9:07 AM, Bob Hinden wrote:
> There has been a consistent level of IETF participation from South and Central
> America, and it has been growing since IETF82.  The data on this is posted at
>
>    http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.

 From the cited table, we see that Latin American meeting attendance 
grew from <1% to 2%, over a bit more than one year.  However note that 
it showed a marked /decrease/ in the preceding year.

As statistical analyses goes, making a business claim of increased 
attendance, based on percentages that small and with a pattern that 
contradictory, is extremely risky.

It also means 98% of attendees at the venue will /not/ be from the 
region, rather than the usual 1/3 - 2/3 for our usual meeting venues. 
That is, this meeting will be disproportionately out of the way for 
attendees.



>  IETF standards are also made more robust when all perspectives
> are represented during their development.

The IETF's primary working venue is mailing lists.  Are participants 
from that region having singular difficulties participating in mailing 
lists?

There were a few notes about this on the ietf list.

I'd summarize it as suggesting that we need more effort at making 
mailing list participation easier for non-native English speakers, for 
those new to IETF culture, and for those having an upbringing that is a 
poor match against the IETF's gruff, aggressive debating style.  But, of 
course, these are general issues about the IETF that also have come up 
before.  And these are what we need to address.


> Things to consider are that it will be a long trip for the majority of IETFers and the
> air fares are more expensive (about 10% to 20% higher than average), though
> restaurants are less expensive.  This would be a case where most IETFers would
> bear more travel pain and expense.

The cost appears to be significantly worse than that.  Presumably the 
referenced average is spread across current planned averages of 
within-region and 'distant' region meetings, with distant regions 
typically being more expensive and of course incurring longer travel 
times.

This one to South America will be distant for 98% of attendees. So more 
attendees than usual will be spending 'distant' travel money and time.

 From the table below, a rough guess is that the incremental per-person 
cost of this meeting's air travel is arguably around, US$700(!) 
Multiply that by 1175 attendees -- assuming an average total of 1200. 
That's an incremental community cost of roughly one million dollars.

And travel times to Buenos Aires are much longer than all but the most 
distant venues, probably adding 1/2 - 1 day each way.  So attendees are 
likely to be away from work and family for 1-2 days longer.

And for those who answer the questionnaire, saying that they are likely 
or very likely to go to a meeting in Buenos Aires, one issue to consider 
carefully is the likelihood of management approval for these extra 
costs, or at least the overall effect on your annual travel budget.

Adelaide was fun, but it was not justified in terms of either of the 
rationales put forward in the IAOC note.  It also was a long time ago -- 
the Internet has changed, the world's economies have changed, and 
companies allocation of funds have changed.

I like visiting South America.  But IETF meetings do not have tourism as 
a goal.  So yes, I'm sure those who go will "enjoy" the city; but again, 
that's not stated purpose of choosing venues.

Again, yes we want greater IETF participation of all regions around the 
globe, but this meeting venue won't change things.

If we are serious about wanting more participation from 
under-represented regions, then let's attack that issue seriously and 
substantively, rather than with an expensive marketing show.

For example, $1M/year could fund quite a lot of regional IETF outreach 
-- perhaps as an extension to the existing, excellent ISOC global effort 
-- and perhaps even better remote participation capabilities...


d/



  Orbitz coach prices for late October 2013, US$
  ==============================================

Origin        BUE   Frankfurt   Tokyo    Atlanta
---------    ----   ---------   -----    -------
SFO          1400     1200       1100       350
Amsterdam    1600      150        800      1100
Taipei       2100      900        400      1500
				



-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From juliao@braga.eti.br  Sun May 26 10:56:55 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC3521F8E8F for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 10:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XTJaeR4b8SLR for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 10:56:54 -0700 (PDT)
Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [IPv6:2607:f8b0:400c:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D607721F87FB for <ietf@ietf.org>; Sun, 26 May 2013 10:56:53 -0700 (PDT)
Received: by mail-vb0-f42.google.com with SMTP id w15so3835135vbf.15 for <ietf@ietf.org>; Sun, 26 May 2013 10:56:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=bLWWtTR9YObpO/S24b7oMk8K7hE+TaAk4+lmNzeHajE=; b=EGwnkEekVryeErV4ecmdTetUvp7IeOTzkVHs2/lk8dQpBbr5YSKo9YeGSnEkAKt2kg NHTBAVO2sUKGoW8VOzWu12ffNtnl1hEmFkJ+1kOJnlj525SoZbdMrvcwor/BOgfM4z87 EW2CQ3qV60MRyMBT6VQGKJEHBKJQfqT4Xo9AF069f8KmvZvfVYk5pEDUgEVD/paUKMyH e9fhsL0HrYZkCiv5DVQktBIjn6Hpt6yiYLN/9yP5X4XlywheNLmQkbdS7D6s7/kziZAq xTBTRTniTDgWBPjjYJh/AVfQ/yJ0qp+BcfDudy/59pc5EzA2YykWsYJuDFHWABD6OyFD 7LeQ==
X-Received: by 10.52.111.202 with SMTP id ik10mr11439595vdb.41.1369591013289;  Sun, 26 May 2013 10:56:53 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id u6sm17086694ven.3.2013.05.26.10.56.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 10:56:52 -0700 (PDT)
Message-ID: <51A24CE0.1040602@braga.eti.br>
Date: Sun, 26 May 2013 14:56:48 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net>
In-Reply-To: <51A23B7F.3050702@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQmBbsXK/XCJIaHVwO6vVVzkM0pmZ/X/p7/HSLFjSIGyNawcslQyya8pR4kKiJEdCuW95vbF
Cc: ericas@irtf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 May 2013 17:56:55 -0000

This is the main question with one pragmatic solution proposal in brief,
and well justified!

Juliao

Em 26/05/2013 13:42, Dave Crocker escreveu:
> If we are serious about wanting more participation from
> under-represented regions, then let's attack that issue seriously and
> substantively, rather than with an expensive marketing show.

From rlb@ipv.sx  Sun May 26 12:57:40 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D3221F9048 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 12:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.063
X-Spam-Level: 
X-Spam-Status: No, score=-1.063 tagged_above=-999 required=5 tests=[AWL=-0.638, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0uSOpHTB4GZ for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 12:57:36 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 9830421F84F5 for <ietf@ietf.org>; Sun, 26 May 2013 12:57:36 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id tb18so7332017obb.17 for <ietf@ietf.org>; Sun, 26 May 2013 12:57:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=toUOYybYb9Od9BMktmj7VJ7eZBr+gPkoU3TIO6OxqvU=; b=fj+b6sDHHVO7DhbsqE9xaEdwh4vc6wMnkEhHA3fWsL71IS0xHR0RBM9tcUhOaAVbJM aKnvll61T5vR30Fdh81P7zgxghKnctNhw8CtkONnda6xbysiTQeX4v7SnIovGeEAraeZ /YQR0tckuh+kTD+AFbLzLieU1ho8hYv/xine54X9d7oWibeFY4IvGIA8gcPKz993lMk5 3RNs1OL6iVsWjuSKwoU4FTZEoS64bacChloxaqxR2fj0ST0lGMxhKd9W5M8vEbTuYYZf xrxzOoPP/KFXTurhPkhstKywAqdLLgREqZt7f/+oAp/KIJluTvwR+JnsNUh7O0wAMeM4 /90w==
MIME-Version: 1.0
X-Received: by 10.60.102.230 with SMTP id fr6mr16587719oeb.141.1369598256177;  Sun, 26 May 2013 12:57:36 -0700 (PDT)
Received: by 10.60.102.146 with HTTP; Sun, 26 May 2013 12:57:36 -0700 (PDT)
X-Originating-IP: [128.89.255.67]
In-Reply-To: <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com>
Date: Sun, 26 May 2013 15:57:36 -0400
Message-ID: <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Richard Barnes <rlb@ipv.sx>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=089e011830d68b739804dda47145
X-Gm-Message-State: ALoCoQlmBYRXqlAnNfAMBJOutW+3FkBXrR0kXzL4ZvjwMtd+UL23z06kio0JzTeHCWDSkIQw+KFK
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2013 19:57:40 -0000

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

Indeed, there has already been some coordination between the groups, going
back about a year:
<http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf>
<http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt>

So my read of the situation is much less dire than James's.  As I
understand it, the upshot of the initial coordination discussions is that
there's not a single, clear "RTCWEB+ECRIT" story.  Instead, there are a few
ways you can put them together.  In the short run, without upgrading PSAPs,
RTCWEB VoIP services can bridge RTCWEB signaling to ECRIT-compliant SIP,
either at the server, or at the client using something like
SIP-over-WebSockets.  In the long run, PSAPs can just advertise an RTCWEB
service like they would advertise a SIP service today (in LoST).  Neither
of these is incompatible with RTCWEB or ECRIT as they're being specified
today.

I expect there are probably some ECRIT considerations that aren't naturally
supported in RTCWEB.  Things like real-time text come to mind.  However, it
doesn't seem to me that there's gross incompatibility.

--Richard




On Sat, May 25, 2013 at 10:18 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
> <jari.arkko@piuha.net> wrote:
>
> >...
> > I didn't know about the details of the emergency
> > communications situation. But it is always difficult to
> > balance getting something out early vs. complete. I know how
> > much pressure there is on the working groups to keep up with
> > things actually happening in the browsers and organisations
> > setting up to use this technology. Do you think the retrofit
> > will be problematic, and do you have a specific suggestion
> > about what should be included today?
>
> Jari,
>
> James will probably have a different answer and perspective, but
> I suggest that retrofits of security-sensitive features are so
> often problematic to make "always" not much of an exaggeration.
>
> I don't think there is any general solution to the "early vs.
> complete" tradeoff [1], nor, as long as we keep trying to deal
> with things as collections of disconnected pieces rather than
> systems, to the issues created by WGs with significant overlaps
> in either scope or technology.  What I think we can do is to be
> particularly vigilant to be sure that the two WGs are tracking
> and frequently reviewing each other's work.   At least RTCWEB
> and ECRIT are in the same area, which should make that
> coordination easier than it might be otherwise.
>
>    john
>
>
> [1] Watch for a note about this that I've been trying to
> organize for about two weeks and hope to finish and post this
> weekend.
>
>
>
>

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

<div dir=3D"ltr">Indeed, there has already been some coordination between t=
he groups, going back about a year:<div>&lt;<a href=3D"http://tools.ietf.or=
g/agenda/84/slides/slides-84-ecrit-0.pdf">http://tools.ietf.org/agenda/84/s=
lides/slides-84-ecrit-0.pdf</a>&gt;</div>
<div>&lt;<a href=3D"http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.tx=
t">http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt</a>&gt;</div><d=
iv><br></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">So my read of the situation is much less dire than James&#39;s. =A0As I =
understand it, the upshot of the initial coordination discussions is that t=
here&#39;s not a single, clear &quot;RTCWEB+ECRIT&quot; story. =A0Instead, =
there are a few ways you can put them together. =A0In the short run, withou=
t upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB signaling to ECRI=
T-compliant SIP, either at the server, or at the client using something lik=
e SIP-over-WebSockets. =A0In the long run, PSAPs can just advertise an RTCW=
EB service like they would advertise a SIP service today (in LoST). =A0Neit=
her of these is incompatible with RTCWEB or ECRIT as they&#39;re being spec=
ified today.</span><br>
</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">I expect there are probably some ECRIT considerations that aren&#39;t na=
turally supported in RTCWEB. =A0Things like real-time text come to mind. =
=A0However, it doesn&#39;t seem to me that there&#39;s gross incompatibilit=
y.</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">--R=
ichard</span></div><div><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px"><br>
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x"><br></span></div></div><div class=3D"gmail_extra"><br><br><div class=3D"=
gmail_quote">On Sat, May 25, 2013 at 10:18 AM, John C Klensin <span dir=3D"=
ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@j=
ck.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
--On Saturday, May 25, 2013 10:10 +0300 Jari Arkko<br>
&lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko@piuha.net</a>&gt; wr=
ote:<br>
<br>
&gt;...<br>
<div class=3D"im">&gt; I didn&#39;t know about the details of the emergency=
<br>
&gt; communications situation. But it is always difficult to<br>
&gt; balance getting something out early vs. complete. I know how<br>
&gt; much pressure there is on the working groups to keep up with<br>
&gt; things actually happening in the browsers and organisations<br>
&gt; setting up to use this technology. Do you think the retrofit<br>
&gt; will be problematic, and do you have a specific suggestion<br>
&gt; about what should be included today?<br>
<br>
</div>Jari,<br>
<br>
James will probably have a different answer and perspective, but<br>
I suggest that retrofits of security-sensitive features are so<br>
often problematic to make &quot;always&quot; not much of an exaggeration.<b=
r>
<br>
I don&#39;t think there is any general solution to the &quot;early vs.<br>
complete&quot; tradeoff [1], nor, as long as we keep trying to deal<br>
with things as collections of disconnected pieces rather than<br>
systems, to the issues created by WGs with significant overlaps<br>
in either scope or technology. =A0What I think we can do is to be<br>
particularly vigilant to be sure that the two WGs are tracking<br>
and frequently reviewing each other&#39;s work. =A0 At least RTCWEB<br>
and ECRIT are in the same area, which should make that<br>
coordination easier than it might be otherwise.<br>
<br>
=A0 =A0john<br>
<br>
<br>
[1] Watch for a note about this that I&#39;ve been trying to<br>
organize for about two weeks and hope to finish and post this<br>
weekend.<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--089e011830d68b739804dda47145--

From sm@resistor.net  Sun May 26 13:09:41 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AED921F93D4; Sun, 26 May 2013 13:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aA42oxqe+kRE; Sun, 26 May 2013 13:09:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D36BC21F92C5; Sun, 26 May 2013 13:09:24 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4QK9CGO004872; Sun, 26 May 2013 13:09:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369598957; bh=9x0lOfoVDDnmFoPJrjHbLbcju3wQQcS/y3gsn0x4ltI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aEoZnbP7rzUyBvDQYnIt4+HIoNsE44HZoDKF0NF3h8UaPOtaqZPXQK2Cwu+RTCLqO b06eweHhUi/pSsTeHJKizDA+k9YIOO09cUKh7iGRUw6OQbyOt3AiulGnk2anUwsO4o a7S1jOUHPbSt9hiAECKVY1QI2tNQf6TPMwuC5RzU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369598957; i=@resistor.net; bh=9x0lOfoVDDnmFoPJrjHbLbcju3wQQcS/y3gsn0x4ltI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DNu1/BYxKes9GGLhnYL8kL3P02D2+u8DDZ6PebVQiSniB0eve3e3hElIsQtzJ1Gyl gIM2uoZ9PLiXP7eb4uJ8oHEk7bHnLeerdxc7UEUxP/4cageN5AZot03HTakzj5NH+F JmmJgaPpTEO9OmudF2HBiVp9GPDaA1HDWfHJpJaA=
Message-Id: <6.2.5.6.2.20130526122352.0bc6e588@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 May 2013 13:08:43 -0700
To: ietf@ietf.org, iesg@ietf.org, iab@iab.org
From: SM <sm@resistor.net>
Subject: More participation from under-represented regions (was: IETF Meeting in South America)
In-Reply-To: <51A23B7F.3050702@dcrocker.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2013 20:09:41 -0000

At 09:42 26-05-2013, Dave Crocker wrote:
>I like visiting South America.  But IETF meetings do not have 
>tourism as a goal.  So yes, I'm sure those who go will "enjoy" the 
>city; but again, that's not stated purpose of choosing venues.

Over a year ago "the IAOC [was] pleased to announce the Return of the 
Nerds to Paradise!"

>If we are serious about wanting more participation from 
>under-represented regions, then let's attack that issue seriously 
>and substantively, rather than with an expensive marketing show.

Yes.

The meaning of "the elephant in the room" is "an important and 
obvious topic, which everyone present is aware of, but which isn't 
discussed, as such discussion is considered to be 
uncomfortable".  The elephant in the room is that there hasn't been 
any discussion about what has been done to get more participation 
from under-represented regions but nobody has mentioned that.

  (a) Was the IESG working on how to get more participation from
      under-represented regions?

  (b) Was the IAB working on how to get more participation from
      under-represented regions?

I am asking the above questions as it is not clear who in the IETF 
was doing that.

Regards,
-sm 


From melinda.shore@gmail.com  Sun May 26 13:43:55 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A3B21F9601 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 13:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.662
X-Spam-Level: 
X-Spam-Status: No, score=-2.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oDnwVGh6d7Fn for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 13:43:49 -0700 (PDT)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) by ietfa.amsl.com (Postfix) with ESMTP id 26A1B21F95D7 for <ietf@ietf.org>; Sun, 26 May 2013 13:43:49 -0700 (PDT)
Received: by mail-pd0-f179.google.com with SMTP id q11so5900108pdj.10 for <ietf@ietf.org>; Sun, 26 May 2013 13:43:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=AUMIte35YvrExLgD8vd16qKFbxv+QGtmOS6AmFGlUsU=; b=LuqIdVGs/96HJT0nUAOWR5iGCMucmz3CkpeII/fjxpu8YoWYI0q5dU6+vJQgrOWQBo QhsAbNapxriIiFoJWcOiMcxXpEeDZZSwT0jo2xvt/W88JNPmV4tXNZLk6A9EAQ3i9raM kLt9UOKq86NOdW6Kb0ALHax59+3HZvM09rKU76ObZ5Uq8q7OhqHA6qLVrlgK/RTSE1ag VBjQq1yB+TVvOEfh/4YlOSUXGGDk8hV0Rg+QLrqUC1fyB2TDKId5Ojx6ZSVbgmw4s3R7 a5m1Lv3wmRkqqxwIYvk2PRsZKpIuASuysgcYOmW8GtTiixmL7iQyU6QCi9wBbdQ2s/I8 3AKQ==
X-Received: by 10.66.191.40 with SMTP id gv8mr3050530pac.19.1369601027730; Sun, 26 May 2013 13:43:47 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id xl10sm27408397pac.15.2013.05.26.13.43.45 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 13:43:46 -0700 (PDT)
Message-ID: <51A273FF.6060109@gmail.com>
Date: Sun, 26 May 2013 12:43:43 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net>
In-Reply-To: <6.2.5.6.2.20130526122352.0bc6e588@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, 26 May 2013 20:43:55 -0000

On 5/26/13 12:08 PM, SM wrote:
> The elephant in the
> room is that there hasn't been any discussion about what has been done
> to get more participation from under-represented regions but nobody has
> mentioned that.

One of the things that's really popped out in the discussion
on the ericas list is that none of the people posting have
been from vendors/manufacturers, which right now is by far
the largest sector participating in the IETF.  The posters
have either been academics or from operators.  We can't even
get much participation from operators in North America and
Europe.  The industry sector bias in IETF participation is
possibly compounding the regional bias.

Melinda


From aeopare@gmail.com  Sun May 26 13:59:27 2013
Return-Path: <aeopare@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C08421F95E5 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 13:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-uILfgYSdQV for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 13:59:19 -0700 (PDT)
Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by ietfa.amsl.com (Postfix) with ESMTP id 8E40421F920B for <ietf@ietf.org>; Sun, 26 May 2013 13:59:19 -0700 (PDT)
Received: by mail-oa0-f46.google.com with SMTP id h2so8079347oag.5 for <ietf@ietf.org>; Sun, 26 May 2013 13:59:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f1l2jlNgPz/dqKcdOLsK/c4uBm9sVxBEI865Vyx2PZU=; b=sFk7AiFwkBAfejAILHO55BdaHbIEjoL+uZZhtK6Qkypl4EkuMMR+e9t88dwAfrOb8F DH4XDvl3VgfSCJ6RGFdPW5YqXQ8rjwSWjRah4Nr/y53nGV3NI3HLTMQEtvUYfOdXROrr NENH6dZVg/eHzGki+UsFjHX9GzICssNyRBWA5WajqiEm4T9MnMmX7dVQihHmo6fDuaEu sLJFbugBeHZnd5Y4U8mVMbbQpWFmS8mEpYk+yHgy+zgAEaCz2OSSXP1cjkzJS1fM3IKK 07QMuXzI/kGpZAc+e51Ul2TWvcMlUO7uhn+U0FCjcyiK4jsGIIbkl4qVpONw/K5PQZAd aQAw==
MIME-Version: 1.0
X-Received: by 10.182.65.100 with SMTP id w4mr14599751obs.70.1369601959125; Sun, 26 May 2013 13:59:19 -0700 (PDT)
Received: by 10.60.144.7 with HTTP; Sun, 26 May 2013 13:59:19 -0700 (PDT)
In-Reply-To: <51A273FF.6060109@gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com>
Date: Sun, 26 May 2013 20:59:19 +0000
Message-ID: <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com>
Subject: Re: More participation from under-represented regions
From: "Edwin A. Opare" <aeopare@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=089e0153894c41ecb104dda54e0e
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, 26 May 2013 20:59:27 -0000

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

>The elephant in the  room is that there hasn't been any discussion about
what has been done
> to get more participation from under-represented regions but nobody has
> mentioned that.

I believe there's the need for a lot more awareness creation about the IETF
in the under-represented regions. That is a sure way to get more
participation from there. In Ghana where I come from for instance not many
people know about the IETF, let alone the wonderful work they are doing to
ensure the continuous development and evolution of the Internet.

The awareness creation should start at the grassroots level : "The
Universities"!. Train the soon-to-graduate Computer Scientist/Engineer on
the values and essence of the IETF and it'll forever be with them even
after graduation.

To elicit participation from the under-represented regions, the
universities are a sure starting point, then a lot more industry-focused
awareness creation by the ISOC local Chapters.

--
Regards,

Edwin

On Sun, May 26, 2013 at 8:43 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 5/26/13 12:08 PM, SM wrote:
> > The elephant in the
> > room is that there hasn't been any discussion about what has been done
> > to get more participation from under-represented regions but nobody has
> > mentioned that.
>
> One of the things that's really popped out in the discussion
> on the ericas list is that none of the people posting have
> been from vendors/manufacturers, which right now is by far
> the largest sector participating in the IETF.  The posters
> have either been academics or from operators.  We can't even
> get much participation from operators in North America and
> Europe.  The industry sector bias in IETF participation is
> possibly compounding the regional bias.
>
> Melinda
>
>

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

<div dir=3D"ltr"><div>&gt;The elephant in the=A0=A0room is that there hasn&=
#39;t been any discussion about what has been done<br>&gt; to get more part=
icipation from under-represented regions but nobody has<br>&gt; mentioned t=
hat.<br>
</div><div><br></div>I believe there&#39;s the need for a lot more awarenes=
s creation about the IETF in the under-represented regions. That is a sure =
way to get more participation from there. In Ghana where I come from for in=
stance not many people know about the IETF, let alone the wonderful work th=
ey are doing to ensure the continuous development and evolution of the Inte=
rnet.<div>
<br></div><div>The awareness creation should start at the grassroots level =
: &quot;The Universities&quot;!. Train the soon-to-graduate Computer Scient=
ist/Engineer on the values and essence of the IETF and it&#39;ll forever be=
 with them even after graduation.=A0</div>
<div><br></div><div>To elicit participation from the under-represented regi=
ons, the universities are a sure starting point, then a lot more industry-f=
ocused awareness creation by the ISOC local Chapters.<br><div class=3D"gmai=
l_extra">
<br clear=3D"all"><div>--<br>Regards,<br><br>Edwin</div><br><div class=3D"g=
mail_quote">On Sun, May 26, 2013 at 8:43 PM, Melinda Shore <span dir=3D"ltr=
">&lt;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.=
shore@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">On 5/26/13 12:08 PM, SM wrote:<br>
&gt; The elephant in the<br>
&gt; room is that there hasn&#39;t been any discussion about what has been =
done<br>
&gt; to get more participation from under-represented regions but nobody ha=
s<br>
&gt; mentioned that.<br>
<br>
One of the things that&#39;s really popped out in the discussion<br>
on the ericas list is that none of the people posting have<br>
been from vendors/manufacturers, which right now is by far<br>
the largest sector participating in the IETF. =A0The posters<br>
have either been academics or from operators. =A0We can&#39;t even<br>
get much participation from operators in North America and<br>
Europe. =A0The industry sector bias in IETF participation is<br>
possibly compounding the regional bias.<br>
<span class=3D""><font color=3D"#888888"><br>
Melinda<br>
<br>
</font></span></blockquote></div><br></div></div></div>

--089e0153894c41ecb104dda54e0e--

From john-ietf@jck.com  Sun May 26 14:42:00 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 683C621F9193 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 14:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3b3X+M5X9iO for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 14:41:55 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9007821F9289 for <ietf@ietf.org>; Sun, 26 May 2013 14:41:52 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UgihK-000MD6-VO; Sun, 26 May 2013 17:41:51 -0400
X-Vipre-Scanned: 03CB347A002C3103CB35C7-TDI
Date: Sun, 26 May 2013 17:41:50 -0400
From: John C Klensin <john-ietf@jck.com>
To: Discussion IETF <ietf@ietf.org>
Subject: Re: [Recentattendees] IETF Meeting in South America
Message-ID: <35ED806EBF0D2E62A1027CF9@[192.168.1.128]>
In-Reply-To: <5FEB74E0-1DE6-432B-891C-B72352B8A727@isoc.org>
References: <5FEB74E0-1DE6-432B-891C-B72352B8A727@isoc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Bob Hinden <bob.hinden@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, 26 May 2013 21:42:00 -0000

--On Sunday, May 26, 2013 15:46 -0400 Ray Pelletier
<rpelletier@isoc.org> wrote:

> The venues are in Buenos Aires.  They meet our requirements
> for the meeting space, networking, nearby restaurants and
> bars, hotel room rates in the mid $200 dollar range, nearby
> alternate hotels at a broad range of prices, nice area in the
> city, safe, direct international flights, and accessible visas.

Ray,

I don't know the venues you are looking at, nor what the site
visit showed, nor what has happened in the decade or so since
I've attended a meeting in Buenos Aires.  But, based on my
outdated experience and the frequent rage in the IETF community
if their food requirements cannot be met, I'd encourage/caution
you to pay very careful attention to the food situation in your
considerations.  Argentina, especially the capital city, has
been one of the reasons I've avoided shifting to a complete
vegetarian (or at least non-meat) diet -- I've found there that
the alternatives were often either eating large quantities of
beef or both starving and insulting one's hosts.  The pressures
would presumably be less in an IETF context, but, again at least
in my experience, John Levine's "steak or pizza" summary for the
vast majority of eating places is pretty close to the mark, with
meat on most of the pizzas.

Note that isn't "don't go", just "watch out for this and be
ready for a lot of unpleasant pushback if the issues are
perceived of as unmanaged and/or indifferent or discriminatory
toward some groups".

best,
   john




From sm@resistor.net  Sun May 26 16:02:20 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC01021F94B1 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level: 
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uGdzHFqCEnfH for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:02:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F4B021F949F for <ietf@ietf.org>; Sun, 26 May 2013 16:02:20 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4QN2AXr017731; Sun, 26 May 2013 16:02:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369609335; bh=fIRAHhglyjMdH496VTiD53bjzvzrIZOXqA9U0I0j7Nk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Iy1BxnckItuJUvE5ZrCCjiHEClEUNJz5wmbEKYY4j4g7r0D2qXUvroEg7QqK583RX vWKh9ltXa0YGSS5DY+ouseME0ExXuEeXgcwvchW4/L9wFYhVhYmLg8wl5EkdjkpKdP VhKM+byBE75wwKdD2Dv4Coh0Rk7LPblj/0cj9zbg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369609335; i=@resistor.net; bh=fIRAHhglyjMdH496VTiD53bjzvzrIZOXqA9U0I0j7Nk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mGFG9sgcNiakrSgqc2TkaDCXru1tdD5kDFMigoULhVt5bJjNUzoei9zlfBjAXEKd7 VfW1mxY72P7Y3PxJS0Ej5O3Kn5y90lL2Ag/E3FZf8kL7/rvMf6CjquzEFW1DXJy0xm qlfn2GQ4W+pYpT6PJeE2RJRtlcunbL5oCKDIm+v4=
Message-Id: <6.2.5.6.2.20130526154034.0c284960@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 May 2013 16:01:30 -0700
To: "Edwin A. Opare" <aeopare@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: More participation from under-represented regions
In-Reply-To: <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.g mail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2013 23:02:21 -0000

Hi Edwin,
At 13:59 26-05-2013, Edwin A. Opare wrote:
>The awareness creation should start at the grassroots level : "The 
>Universities"!. Train the soon-to-graduate Computer 
>Scientist/Engineer on the values and essence of the IETF and it'll 
>forever be with them even after graduation.
>
>To elicit participation from the under-represented regions, the 
>universities are a sure starting point, then a lot more 
>industry-focused awareness creation by the ISOC local Chapters.

AfNOG has trained hundreds of people in Africa.  Those people do not 
participate on the mailing list.  There are some people from Africa 
who have attended IETF meetings.  They don't participate in the 
IETF.  Why is it that there are some participants from South America 
whereas there aren't any participants from Africa?

Regards,
-sm 


From randy_presuhn@mindspring.com  Sun May 26 16:28:30 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB4E21F9374 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.999
X-Spam-Level: 
X-Spam-Status: No, score=-99.999 tagged_above=-999 required=5 tests=[BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gg3UKWLKG0yI for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:28:23 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id CAA0221F91B1 for <ietf@ietf.org>; Sun, 26 May 2013 16:28:23 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=t/Lb9wZ2qU5ROSn1tPuRdb8dVkXzJB74TonCdvdD7eCkFhGZEXzeVcAVgQ4QtUhe; h=Message-ID:Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.39] (helo=elwamui-little.atl.sa.earthlink.net) by elasmtp-masked.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UgkMQ-0000mM-RN for ietf@ietf.org; Sun, 26 May 2013 19:28:22 -0400
Received: from 99.23.161.228 by webmail.earthlink.net with HTTP; Sun, 26 May 2013 19:28:22 -0400
Message-ID: <21899663.1369610902840.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Date: Sun, 26 May 2013 16:28:22 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: ietf@ietf.org
Subject: Re: More participation from under-represented regions
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88880ff2f3e23ebe946680bbd2c0922d73ec6256d737c0ee29e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.39
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 May 2013 23:28:30 -0000

Hi -

Watching this discussion scroll by on my screen, I'm amazed
how similar it is to discussions of evangelism in congregations.
Two things this religious institution might learn from other
religious institutions:

  (1) "need-based" evangelism.  Outreach efforts are more
      effective if they sincerely address specific needs of
      the target community.  Does face-to-face participation in
      the IETF offer things practitioners in under-represented
      regions feel they need?  As long as we focus on how it
      could help *us*, rather than what needs it would address
      for them, it'll be far less effective than it could be.

  (2) Watch out for "colonialist" attitudes, such as assuming
      that we know what the needs and priorities of the target
      communities are, rather than finding out.  This can require
      much more investment than just doing surveys, and may even
      reveal that certain models of "helping" might be culturally
      inappropriate, and consequently ineffective or counter-
      productive.

Randy


From abdussalambaryun@gmail.com  Sun May 26 16:38:14 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B6121F9195 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.734
X-Spam-Level: 
X-Spam-Status: No, score=-2.734 tagged_above=-999 required=5 tests=[AWL=-0.135, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U426vmQzLL6T for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:38:09 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0223521F911B for <ietf@ietf.org>; Sun, 26 May 2013 16:38:08 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so5879311pdj.15 for <ietf@ietf.org>; Sun, 26 May 2013 16:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/rhQiJpsV4+OKev00TAxnUz8Nvy4AHGX4ioMa+eOhkA=; b=SIfdPB4glexpeEhmLPA8wCE0rp99iOw1T/s0PDtIFR3vXIac1arfPTmL2sr6bGYO0K Xo53i5DZlu//aPye8B4UY9zuL1ZsAMkOIbJ3bCraHAgkGvvdhfKHU34d5XX/sp5I3iPO vjuXvsvJwaE9w4R7xWpRgAdBAEkMLOPpWIk1XPHzBoAY1xQGJjR9ir1el6iryiPahQPv 2trczmOhwhLNVS/upNr0WDDAgO9lh1DzYk7p1IAoUBchg94cvD39l4kxjSK+HlCa53hK fmY/asJqUNvfal+xQrXCqTsqHFjnaLDcPEqbJUK0CBeEfzBPysXFTVLM7eRPCWx7xsit 5KIg==
MIME-Version: 1.0
X-Received: by 10.66.122.8 with SMTP id lo8mr26728860pab.165.1369611488752; Sun, 26 May 2013 16:38:08 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sun, 26 May 2013 16:38:08 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130526122352.0bc6e588@resistor.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net>
Date: Mon, 27 May 2013 01:38:08 +0200
Message-ID: <CADnDZ889Wo_1fdF77W0yxnQAAKD=opr3ah4F-afzOfb5+MYQPg@mail.gmail.com>
Subject: Re: More participation from under-represented regions (was: IETF Meeting in South America)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, 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, 26 May 2013 23:38:14 -0000

I support to add the new region, hoping in future Africa gets its
chance. IMO, I thought about it from another point of view. After a
long time of having IETF meetings mostly in one region (as history of
North America region gaining most meetings), the result of that was
that IETF participants are majority from North America, so I think it
MAY be a result of meetings held in one region (some will argue it is
because experts individual-participants/company-participants come from
North America, while giving no value of IETF marketing),  However,
IETF claims it is for the WORLD as Internet is, not for only one
region's Internet. So giving now chance for other regions (or diverse
Internet communities) to gain meetings will help in the FUTURE more
participants from other regions as it happend to North America.

 For IETF it already gained many from North america, and they don't
increase so it SHOULD market elsewhere for future plans. My answers to
your questions below,

AB

On 5/26/13, SM <sm@resistor.net> wrote:
> At 09:42 26-05-2013, Dave Crocker wrote:
>>I like visiting South America.  But IETF meetings do not have
>>tourism as a goal.  So yes, I'm sure those who go will "enjoy" the
>>city; but again, that's not stated purpose of choosing venues.
>
> Over a year ago "the IAOC [was] pleased to announce the Return of the
> Nerds to Paradise!"
>
>>If we are serious about wanting more participation from
>>under-represented regions, then let's attack that issue seriously
>>and substantively, rather than with an expensive marketing show.
>
> Yes.
>
> The meaning of "the elephant in the room" is "an important and
> obvious topic, which everyone present is aware of, but which isn't
> discussed, as such discussion is considered to be
> uncomfortable".  The elephant in the room is that there hasn't been
> any discussion about what has been done to get more participation
> from under-represented regions but nobody has mentioned that.
>
>   (a) Was the IESG working on how to get more participation from
>       under-represented regions?

I think they SHOULD have, and all of us should do the same, because
IETF will expand and become stronger by increasing participants from
ALL Internet community regions. The answers also based on IETF vesion.
>
>   (b) Was the IAB working on how to get more participation from
>       under-represented regions?

I think they SHOULD have, and all of us should do the same, because
IETF will expand and become stronger by increasing participants from
ALL Internet community regions. The answers also based on IETF vesion.

>
> I am asking the above questions as it is not clear who in the IETF
> was doing that.

I am working on it my self, so I hope others think the same, I have
asked many students about the IETF, they don't know about it a thing,
so should n't we ask question why the community of Internet users in
South America not participating? One answer can be that the reason is
that IETF participants majority from North America and they don't want
to spend money on long journies that include many competing regions
(e.g. few regions or few long distance per year maybe fine).

>
> Regards,
> -sm
>
>

From abdussalambaryun@gmail.com  Sun May 26 16:51:17 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8CE21F944F for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:51:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.724
X-Spam-Level: 
X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZfas05eI6KT for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 16:51:12 -0700 (PDT)
Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by ietfa.amsl.com (Postfix) with ESMTP id DE3B121F9399 for <ietf@ietf.org>; Sun, 26 May 2013 16:51:11 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id z11so5982903pdj.2 for <ietf@ietf.org>; Sun, 26 May 2013 16:51:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=TdK+Ktxi1ituphjj0A6+QjJPFlswxQ91etKjt1u5/LA=; b=OXTVIAlKhQ5Ha+HrypR2EdfCbRWLTVwieBDE7ougWoOMoKLw5IC77gzYjMx2Gc7cex DY3cOqRMnFuDiesfUmC+IdbqRXNoxuXt/sPD0OxKSOkb5NWa8mwMNZvNQVtjebQlUFW4 O1vATcD57vvbCD5wW4JcjFcm4n7VKhDGRkPK9NCM7kqDcsWw7e/f+NO99zA15QcYh/IN MLxeJmwqHOSYaTYapReGNw+H/nTNLJcbu5C1/HgHcthB/Iop8Mc0+ln6TTuBseohCsb6 wXFRh0PkuPunlZnDgmS24GJse7W2I7+Z2zNMq2eI28QxEI8Wftl20tU+scg1hNMIcng8 Uv3A==
MIME-Version: 1.0
X-Received: by 10.68.103.194 with SMTP id fy2mr26829781pbb.158.1369612271679;  Sun, 26 May 2013 16:51:11 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sun, 26 May 2013 16:51:11 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130526154034.0c284960@resistor.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net>
Date: Mon, 27 May 2013 01:51:11 +0200
Message-ID: <CADnDZ8_XiL649=TVEUpWS1X7=TuXZrMxCa+EP7qv4A4412ca0w@mail.gmail.com>
Subject: Re: More participation from under-represented regions
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
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: Sun, 26 May 2013 23:51:17 -0000

Hi SM,

There are some from Africa trying to find the way in, but they may not
mention it, however, training is not important much to make people
participate but the type of training and its period inside
organisation not outside. For example, I notice that there was one
African participant (not me), trying to participate in writing one
draft for the community, so was he/she encouraged by the WGs,
Directors, or the Chairs, was the draft guided? was that participant
asked to market that draft in his/her community region to make
support. The IETF majority-culture may not be much welcoming from
others point of view, I try to market IETF but need help of the
responds others may get from discouragings.

AB

On 5/27/13, SM <sm@resistor.net> wrote:
> Hi Edwin,
> At 13:59 26-05-2013, Edwin A. Opare wrote:
>>The awareness creation should start at the grassroots level : "The
>>Universities"!. Train the soon-to-graduate Computer
>>Scientist/Engineer on the values and essence of the IETF and it'll
>>forever be with them even after graduation.
>>
>>To elicit participation from the under-represented regions, the
>>universities are a sure starting point, then a lot more
>>industry-focused awareness creation by the ISOC local Chapters.
>
> AfNOG has trained hundreds of people in Africa.  Those people do not
> participate on the mailing list.  There are some people from Africa
> who have attended IETF meetings.  They don't participate in the
> IETF.  Why is it that there are some participants from South America
> whereas there aren't any participants from Africa?
>
> Regards,
> -sm
>
>

From juliao@braga.eti.br  Sun May 26 17:02:37 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA4FF21F9446 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 17:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id srsDqChfJoeT for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 17:02:37 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2C92921F9377 for <ietf@ietf.org>; Sun, 26 May 2013 17:02:37 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id f64so577853yha.12 for <ietf@ietf.org>; Sun, 26 May 2013 17:02:36 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=1FnfmbLNeh8yKIUDc6kdVQfWPxmSReG7KYQGtrkpmEA=; b=O+P2mw/FZyLYx5eKrY3GoHVjlD983ngXJnRYsHv1UpBV35DeBiN6VwKrkGYZpOrCGz UIrOY8SKTMzFLzgcmE2qX7ov+WnmTwdnhED7uyS2pKzmcK+cpLOyJt6BHN8QRSUQ//hT 0Bk6etucB0Pr3mh24h7EMjInhFVSSH2jiJJ+kY/LDbLdLXRIkh9+KZlZvBbWNXLIgK9U 5zdmZt7kCHJ++8kfL8MVA0kYQYqPWXsBMJoqL8jFTVvfjQRtZPyb7p4dOvZjrjSFlH24 I7DA9tVGzwoTizyZYRG3fnL65Yj2weBQ9Ktcvc2ZzAwi65qv6jaQZ/+7jZWKnfv08cP5 V5ug==
X-Received: by 10.236.139.75 with SMTP id b51mr13792208yhj.6.1369612956607; Sun, 26 May 2013 17:02:36 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id v34sm37301440yhn.26.2013.05.26.17.02.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 17:02:35 -0700 (PDT)
Message-ID: <51A2A296.1010305@braga.eti.br>
Date: Sun, 26 May 2013 21:02:30 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net>
In-Reply-To: <6.2.5.6.2.20130526154034.0c284960@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQlmyy3bYKlHHLE98UBpaMVxRAEXzEyZIQxfr+Avp8Oe72OpfigefTo402gCDuegsw3Cmub9
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 00:02:38 -0000

SM, FYI:

Inscriptions at IETF 86 [1]:

ARIN	 RIPE	  APNIC	   AFRINIC	LACNIC
 671	  258	   237	      31	   26
  54.87%   21.10%   19.38%     2.53%	    2.13%

Inscriptions since IETF 72 to IETF 85. For Year, RIR and Country:
http://rfc.pegasus.com.br/ietf.php

I think the local of the meeting no change the numbers. For me the
apparent common sense prevails in the list and Dave Crocker pointed
(...let's attack that...): the issue is to establish a systematic and
effective process in under-represented regions (countries, I think).

Regards,

JuliÃ£o
1. http://rfc.pegasus.com.br/ietf86.php (including, year, RIR and Country)


Em 26/05/2013 20:01, SM escreveu:
> AfNOG has trained hundreds of people in Africa.  Those people do not
> participate on the mailing list.  There are some people from Africa who
> have attended IETF meetings.  They don't participate in the IETF.  Why
> is it that there are some participants from South America whereas there
> aren't any participants from Africa?

From abdussalambaryun@gmail.com  Sun May 26 18:11:57 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7C9121F9425 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 18:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.98
X-Spam-Level: 
X-Spam-Status: No, score=-1.98 tagged_above=-999 required=5 tests=[AWL=-0.620,  BAYES_00=-2.599, NO_RELAYS=-0.001, SARE_LWSHORTT=1.24]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rg3uF5MNRgs for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 18:11:56 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id C412021F9350 for <ietf@ietf.org>; Sun, 26 May 2013 18:11:56 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id ma3so6198457pbc.2 for <ietf@ietf.org>; Sun, 26 May 2013 18:11:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=KPsRqySJQ0Z0Gw85kf1eUJVe3KYE0SZGEbVHqwH0FyA=; b=QKtk/HKF/AMiJfbNixROb94WkwYzQlW0c6booMm7pIj4TYbVDtdSjhmzfWG5NnLnvU HjdSAyJdvnE7sYAC9zBHhBi3BS6L1XnC0GlpvwCliWNUWK2bk2aRtY1SehNySSIyRGOZ 1mSAPAF7oJ67QtVxqfxLoOLbKf/DFgNCOI9XHudqykjNVTGeTL17sL6PJctmZoEQgcqH d0pp0CoMrYcs3KoO2VOe/AFBN+l6Q3xgLnUMg7mT40se2+DCLj+vhZnhYD/kuNxZ6Ukg Wuo6XA4jWZ37sf0wyW4UVQjiOLuaJJ+p080ad1AB0fZRthbhZHIF4s4+CE/qYf5CNh8H 77mg==
MIME-Version: 1.0
X-Received: by 10.68.125.227 with SMTP id mt3mr4767100pbb.153.1369617116445; Sun, 26 May 2013 18:11:56 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Sun, 26 May 2013 18:11:56 -0700 (PDT)
In-Reply-To: <51A23B7F.3050702@dcrocker.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net>
Date: Mon, 27 May 2013 03:11:56 +0200
Message-ID: <CADnDZ89RJV6LVQotKD-ouowTU7k416a=-m7CMLtQiEqmTFanXQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Abdussalam Baryun <abdussalambaryun@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: Mon, 27 May 2013 01:11:58 -0000

I support the ietf-meeting in new regions, and reply as below,

On 5/26/13, Dave Crocker <dhc@dcrocker.net> wrote:
> The IAOC has put forward two reasons for having an IETF meeting in South
> America:
>
>> Encouraging growing participation will help strengthen the Internet,
>> further encourage participation from those areas that will see the
>> most growth in the coming years, and will help advance the IETF in
>> political and international circles which is becoming more of an
>> imperative.

Yes I agree, but think that managment SHOULD work with ALL
participants (usually majority from North America) to make this
successful. We will not do that only if we work together, otherwise
not possible if only management work alone.

>
> That is:
>
> 1. Promoting regional participation from Latin America
>
>     There certainly are under-represented constituencies that we should
> find ways to bring to the IETF in greater numbers.  Residents of Latin
> America certainly qualify.
>
>     However a number of comments on the ietf list have observed that our
> conducting a single meeting in South America is unlikely to effect
> greater Latin participation in the IETF.

If you analyse results for short term, you are right, but these things
are long term plans for future participants. We need to give South
America more time to see the result,

> I agree, it won't, and frankly
> I think it shouldn't, because it's a expensive and possibly risky Grand
> Gesture rather than a substantive change.

Not sure what is expensive, do you mean expensive for IETF or for the
participants. If it is for regular participants, then they may become
remote for some time, for the best of IETF, which they will gain as
will.
>
>     If we want great regional participation, let's look for ways to
> achieve that -- for /all/ under-represented constituencies.  I suspect
> that what's needed will be similar for all of them.

So you ask to other way other than reducing the majority of meetings
in North America. Do you mean that if we go for the way you are
disagreeing it will result to reduce number of majority participants?
I don't think so, as long as ALL have the IETF vesion.
>
>
> 2. Counteracting some type of IETF 'deficiency' in political and
> international circles.
>
>     As stated, that's a pretty vague concern, although yes, we sometimes
> hear criticisms around the IETF's regional choices. However the nature
> of exchanges like these are -- as correctly characterized by the IAOC --
> political, and they are rarely assuaged by letting the critics dictate
> organizational decision-making, such as where to send 1200 participants
> for a mission-critical meeting.

No one sending any participants, it is a volunteering meetings, and
can be remotely attended. New communities are still need more face to
face meetings than experts of IETF.
>
>     Put simply: we shouldn't let political critics set the agenda for
> IETF strategic planning.  They'll just find something else to hassle us
> about, since their political goal is criticizing the IETF, not improving
> it.  Again as others have noted, one meeting in the region won't be
> enough, and then there are the other regions we don't go to, and there
> will be something else, and something more after that.

Yes, that is the beauty of IETF, it always changes for the best, we
need to get use to change, many organisations face their staff
resistance of change. Usually memebrs of organisation like things to
go the way it was before.
>
>     But wait. There's a bigger issue being missed: The basis of the
> criticism is fundamentally specious!  The /reality/ is that the IETF is
> dramatically /more/ open in its participation and its documents than
> nearly any other international standards group, most of whom have
> nation- or vendor-based membership fees and restrictions, with little or
> no participation via email or remote attendance.

We will get more remote participants when the meetings are expensive
for majority of participants. However, the number of attendance will
increase, because we got remote attendance and face to face new
attendance with lower costs per individuals :)
>
>     Again, don't let political exercises determine the IETF's public
> message. The solid reality of extreme IETF global inclusiveness is real
> and basic. Those who want to hear that message will.  Those who don't
> won't be quieted by a stray meeting in the southern half of South America.
>
>      Of course we need to do more and better at being inclusive.  The
> nascent diversity effort speaks to the IETF's own concern about that.
>
>
>
> As for some other points in the IAOC message...
>
>
> On 5/23/2013 9:07 AM, Bob Hinden wrote:
>> There has been a consistent level of IETF participation from South and
>> Central
>> America, and it has been growing since IETF82.  The data on this is posted
>> at
>>
>>    http://iaoc.ietf.org/documents/IETF-Regional-Attendance-00.pdf.
>
>  From the cited table, we see that Latin American meeting attendance
> grew from <1% to 2%, over a bit more than one year.  However note that
> it showed a marked /decrease/ in the preceding year.
>
> As statistical analyses goes, making a business claim of increased
> attendance, based on percentages that small and with a pattern that
> contradictory, is extremely risky.
>
> It also means 98% of attendees at the venue will /not/ be from the
> region, rather than the usual 1/3 - 2/3 for our usual meeting venues.
> That is, this meeting will be disproportionately out of the way for
> attendees.

You assume that they all will attend not remotely. The usual meeting
venues has majority from same region, do you think that is a good
achievment, IMHO, it is better to have 50% attendance not from the
region and 50% remotely, than having 90% from same region. The 90%
attendance from same region sound like politics in my understandning,
I don't understand what you mean by *political excersies determining
IETF*.
>
>
>
>>  IETF standards are also made more robust when all perspectives
>> are represented during their development.
>
> The IETF's primary working venue is mailing lists.  Are participants
> from that region having singular difficulties participating in mailing
> lists?

That is good that ALL should get use to participate remotely,
including the 98% of IETF participants. For new regions they need to
start face to face, then after that they will be well trained to have
no difficultues on mailing lists. Please note that I am a remote
participant and attending meetings remotely, but still there are
difficulties facing me because of other issues (may be ietf politics)
you may never experienced.
>
> There were a few notes about this on the ietf list.
>
> I'd summarize it as suggesting that we need more effort at making
> mailing list participation easier for non-native English speakers, for
> those new to IETF culture, and for those having an upbringing that is a
> poor match against the IETF's gruff, aggressive debating style.  But, of
> course, these are general issues about the IETF that also have come up
> before.  And these are what we need to address.

I may understood that you define IETF culture as it is the North
America Culture, I disagree. The IETF culture is the world community
culture that are using the Internet standards. I know that 98%
participants from same region make a region-culture but that is not
the 98% IETF culture.
>
>
>> Things to consider are that it will be a long trip for the majority of
>> IETFers and the
>> air fares are more expensive (about 10% to 20% higher than average),
>> though
>> restaurants are less expensive.  This would be a case where most IETFers
>> would
>> bear more travel pain and expense.

I think that is reasonable, and that will help to increase remote
participants, and increase different industries to participate.
>
> The cost appears to be significantly worse than that.  Presumably the
> referenced average is spread across current planned averages of
> within-region and 'distant' region meetings, with distant regions
> typically being more expensive and of course incurring longer travel
> times.

that will help to increase attendance of remote participants, and
increase different industries to participate.

>
> This one to South America will be distant for 98% of attendees. So more
> attendees than usual will be spending 'distant' travel money and time.

We are not sure about that assumption, but I will say we need to give
chance to other regions to increase participation other wise this 98%
will be 100% in future, and we will never need to have other regions.
The result may be that communities decide to separate-work the IETF
into different regions that work separately, do we want that to
happen? Do you want each region to have its own IETF meetings that
have 100% of attendance (with 1% remote attendance) from same region
with lowest costs.
>
>  From the table below, a rough guess is that the incremental per-person
> cost of this meeting's air travel is arguably around, US$700(!)
> Multiply that by 1175 attendees -- assuming an average total of 1200.
> That's an incremental community cost of roughly one million dollars.

Not sure why you make it added to a million, they spend separately, so
we should not add them as if they go to one company. I don't think the
IETF is spending that one million. You will only add costs if ALL
participants from same region work together to pay one company for the
total costs, therefore, there is no dought that the costs per
individual will reduce and that company will still make money.
>
> And travel times to Buenos Aires are much longer than all but the most
> distant venues, probably adding 1/2 - 1 day each way.  So attendees are
> likely to be away from work and family for 1-2 days longer.
>
> And for those who answer the questionnaire, saying that they are likely
> or very likely to go to a meeting in Buenos Aires, one issue to consider
> carefully is the likelihood of management approval for these extra
> costs, or at least the overall effect on your annual travel budget.

The costs can be reduced if we work together not separately. However,
there is no excuse as long there is possibility of remote attendance.
As you mentioned we need to get use to mailing list remotely.
>
> Adelaide was fun, but it was not justified in terms of either of the
> rationales put forward in the IAOC note.  It also was a long time ago --
> the Internet has changed, the world's economies have changed, and
> companies allocation of funds have changed.

Yes, all changed so we also need to change, that may be the reason why
IETF should go to other regions that had not much economic impacts.

>
> I like visiting South America.  But IETF meetings do not have tourism as
> a goal.  So yes, I'm sure those who go will "enjoy" the city; but again,
> that's not stated purpose of choosing venues.

Yes tourist not a goal but IMO the goal is to meet with Internet
community and encourage its new technologies growth/use. IMO we need
to choose venues to meet with new regional
companies/vendors/users/individuals.
>
> Again, yes we want greater IETF participation of all regions around the
> globe, but this meeting venue won't change things.

Yes, It will not change only if we don't care or we don't work with
management. All 100% of participants should market the IETF standards
to the world and any/every where.
>
> If we are serious about wanting more participation from
> under-represented regions, then let's attack that issue seriously and
> substantively, rather than with an expensive marketing show.

It is not expensive marketing show for the IETF, it can be expensive
per participant, but still that is volunteering not expense, still
there is a choice to volunteer to attend remotely. However, even a
meeting with minimum of 500 present-attendance is a great/enough IETF
marketing per region which will give future results.
>
> For example, $1M/year could fund quite a lot of regional IETF outreach
> -- perhaps as an extension to the existing, excellent ISOC global effort
> -- and perhaps even better remote participation capabilities...

Dont forget globalisation, not a region is gaining the one million it
is companies, I suggested above a way to reduce the total amount of
1M/year (there are many ways) and dont agree to add them as the
payments are separate to separate companies,

AB

From dhc@dcrocker.net  Sun May 26 20:37:24 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A9B1F0D30 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 20:37:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6
X-Spam-Level: 
X-Spam-Status: No, score=-6 tagged_above=-999 required=5 tests=[GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x20MzhfkBMG8 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 20:37:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D6DE61F0D32 for <ietf@ietf.org>; Sun, 26 May 2013 20:37:19 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4R3bDCp015607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 26 May 2013 20:37:19 -0700
Message-ID: <51A2D4E8.5050605@dcrocker.net>
Date: Mon, 27 May 2013 05:37:12 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local>
In-Reply-To: <alpine.OSX.2.01.1305241253050.44324@rabdullah.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 26 May 2013 20:37:19 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 03:37:24 -0000

Just to make the topic a little more interesting...


    Google Unable To Keep Paying App Developers In Argentina

 
http://developers.slashdot.org/story/13/05/25/132232/google-unable-to-keep-paying-app-developers-in-argentina

    "Google has sent letters to app developers registered in Argentina 
saying they won't be able to accept payments on developers' behalf after 
June 27th. 'The change applies to both paid apps and apps that use 
in-app purchases. The move appears to be related to new, restrictive 
regulations the Argentine government has imposed on currency exchanges.' 
According to the Telegraph, 'The new regulations required anyone wanting 
to change Argentine pesos into another currency to submit an online 
request for permission to AFIP, the Argentine equivalent of HM Revenue & 
Customs. ..."


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From johnl@iecc.com  Sun May 26 21:15:41 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06BB21F930A for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 21:15:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.6
X-Spam-Level: 
X-Spam-Status: No, score=-108.6 tagged_above=-999 required=5 tests=[HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ug+mA1CVxOOc for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 21:15:37 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5FB21F92B2 for <ietf@ietf.org>; Sun, 26 May 2013 21:15:30 -0700 (PDT)
Received: (qmail 17990 invoked from network); 27 May 2013 04:15:32 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 May 2013 04:15:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51a2dde0.xn--9vv.k1305; i=johnl@user.iecc.com; bh=ihUl6PIThQCAiN6w4SwyLN4ykFNIQ9KXEtIS2zddNp4=; b=PxU4yWU2EEKB4CU10s/kQ9+Ck9k/vqxE7vm0Mp7djiz+AFm169NjV/t9rr7F1k/QmniKGTFFIZEj8wxELQ3wUQ+gwsXcFR8wVI5Zx+jsT6V2fHexIVJfHOu6OC5g/ICVKCHLer5MUFC2PimTlslA43o0bQtItDgQie/KyjbDDiA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=51a2dde0.xn--9vv.k1305; olt=johnl@user.iecc.com; bh=ihUl6PIThQCAiN6w4SwyLN4ykFNIQ9KXEtIS2zddNp4=; b=gF6laL7TM+oMliMRDIlcJzuTNxgKMVE5DQOB/Ut0AfAd6HPHXn7YVP6G1PRkbiO0f0smhjjQZK3m655zm65fEeRe1NLN5mNteAlzFuZbJC5hYEtNinKSP1gnVYb/gkp54AwPfWUdkBOrW58hMMvIRSbLg5LIyHhMs7+30aOH1MM=
Date: 27 May 2013 04:15:05 -0000
Message-ID: <20130527041505.7301.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: financial fun with an IETF Meeting in South America
In-Reply-To: <51A2D4E8.5050605@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 04:15:41 -0000

> The move appears to be related to new, restrictive 
> regulations the Argentine government has imposed on currency exchanges.' 
> According to the Telegraph, 'The new regulations required anyone wanting 
> to change Argentine pesos into another currency to submit an online 
> request for permission to AFIP, the Argentine equivalent of HM Revenue & 
> Customs. ..."

This isn't likely to change soon.

Back in 2001 the Argentine government defaulted on about $100 billion
of debt.  Since then they got 93% of the bondholders to agree to
restructure and accept partial payment, and had been making payments
to those and nothing to the other 7%.  But an outfit called Elliot
Management bought some of that 7%, took Argentina to court in New
York, where the bonds were issued. and earlier this year the New York
court decided that if Argentina pays anyone, they have to pay
everyone, including the 7% that still demand payment in full.
Argentina has tried a variety of gimmicks to try to pay the
restructured bonds and not the holdouts, mostly with the effect of
annoying the judge.  Since the payments are made through Bank of New
York, whose management has no interest in going to jail, nobody's
currently getting paid, leading to great gnashing of teeth but no
progress.

For this most part, this wouldn't affect foreigners going to Argentina
since we'd be changing hard currency into pesos, which the government
encourages, since their supply of hard currency is very limited.  (If
they had more, they could pay off the holdouts, but they don't.)
Except that the holdouts have done a lot of gimmicky things to try and
get their money, notably slapping a lien on the Argentine navy's
sailing training ship Libertad while it was in port in Ghana.  If they
slap a lien on an Argentine airplane, for example, things could be
somewhat chaotic.

These kinds of currency controls are quite common in the aftermath of
a currency crisis, e.g., in Iceland and Cyprus, but Argentina has had
a rolling crisis for decades.

R's,
John

From juliao@braga.eti.br  Sun May 26 22:31:35 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4062F21F8FA9 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 22:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1jQ47dTzmiii for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 22:31:29 -0700 (PDT)
Received: from mail-gh0-f181.google.com (mail-gh0-f181.google.com [209.85.160.181]) by ietfa.amsl.com (Postfix) with ESMTP id 1D30421F8B60 for <ietf@ietf.org>; Sun, 26 May 2013 22:31:29 -0700 (PDT)
Received: by mail-gh0-f181.google.com with SMTP id z12so1873937ghb.26 for <ietf@ietf.org>; Sun, 26 May 2013 22:31:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=pWLalC8EHaC9YCVEg5t/b+Gjggzj+HvwiP2xClFZkXQ=; b=dXfFee95e1Mg4YUoKfw0vaYmiTZwVKkysCpBIHOIhw3Lc3pEjGWXPO241Sqoq0TLfb +d7CQNYisZHIjiww0BoObbnuIv0fjl58hEYUKFznh8xlITjtoAkyEK1TKD04tqRFIYdX CLottvphinmV8FOHXr6mWwRovaL4rfC4x0aEfuvfehv0QvDsNPJdBxCbsEM19bPUXA+r MtXthc10bC6LZ2pmsCn/45yCORrMGtMRUijVoExjyV3Ibp7fwoMO8dl2klWYcr7o5Ezw ZGKuqZtJsN1+/g2nSThDR7aB/BPmJkM45gQ2gDfiHPLHF394mraVm0u4H385dlTe/rWF DyaA==
X-Received: by 10.236.229.193 with SMTP id h61mr14202287yhq.177.1369632688587;  Sun, 26 May 2013 22:31:28 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id u69sm38565133yhf.23.2013.05.26.22.31.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 22:31:27 -0700 (PDT)
Message-ID: <51A2EFAB.3010106@braga.eti.br>
Date: Mon, 27 May 2013 02:31:23 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan>
In-Reply-To: <20130527041505.7301.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnVEhjtTqgfvQ2M4Uo95Z3349fzOePTzHrPYef0YPuL5j4D/oq1dOSCaB1vZSNCnh/zURaM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 05:31:35 -0000

According to the news published for a long time in Brazilian newspapers
and magazines, Buenos Aires (a wonderful place!) would not be
recommended. But who should tell us about the true cenary would be our
Argentine friends.

Juliao

Em 27/05/2013 01:15, John Levine escreveu:
> These kinds of currency controls are quite common in the aftermath of
> a currency crisis, e.g., in Iceland and Cyprus, but Argentina has had
> a rolling crisis for decades.

From joelja@bogus.com  Sun May 26 22:45:49 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D874121F8FB3 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 22:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBYTS7U3VlQb for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 22:45:49 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 682FB21F8F2C for <ietf@ietf.org>; Sun, 26 May 2013 22:45:49 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4R5jjNq084196 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 27 May 2013 05:45:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A2F309.8010504@bogus.com>
Date: Sun, 26 May 2013 22:45:45 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: SM <sm@resistor.net>, "Edwin A. Opare" <aeopare@gmail.com>
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com>	<51A23B7F.3050702@dcrocker.net>	<6.2.5.6.2.20130526122352.0bc6e588@resistor.net>	<51A273FF.6060109@gmail.com>	<CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net>
In-Reply-To: <6.2.5.6.2.20130526154034.0c284960@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 27 May 2013 05:45:47 +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, 27 May 2013 05:45:50 -0000

On 5/26/13 4:01 PM, SM wrote:
> Hi Edwin,
> At 13:59 26-05-2013, Edwin A. Opare wrote:
>> The awareness creation should start at the grassroots level : "The 
>> Universities"!. Train the soon-to-graduate Computer 
>> Scientist/Engineer on the values and essence of the IETF and it'll 
>> forever be with them even after graduation.
>>
>> To elicit participation from the under-represented regions, the 
>> universities are a sure starting point, then a lot more 
>> industry-focused awareness creation by the ISOC local Chapters.
>
> AfNOG has trained hundreds of people in Africa.  Those people do not 
> participate on the mailing list.
They are network operators, system adminstrators, students and NGO 
participants bootstraping parts of the experience by participating in 
activities with their regional peers. A week-long series of workshops 
held once a year has some worthwhile goals and notable sucesses I don't 
think of it a fertile training ground for new IETF participants.
> There are some people from Africa who have attended IETF meetings.  
> They don't participate in the IETF.  Why is it that there are some 
> participants from South America whereas there aren't any participants 
> from Africa?
People come to the IETF with work because they have a problem which the 
work product of their contribution through the IETF activity addresses.  
That's fairly expensive, time consuming, and has uncertain results.

There are past and present contributors from various parts of the 
continent, I've had the privilege of working with some of them.
>
> Regards,
> -sm


From johnl@iecc.com  Sun May 26 22:53:25 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AEF321F9234 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 22:53:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.6
X-Spam-Level: 
X-Spam-Status: No, score=-108.6 tagged_above=-999 required=5 tests=[HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xc8DomEz9Gzm for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 22:53:21 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CDA3621F920B for <ietf@ietf.org>; Sun, 26 May 2013 22:53:20 -0700 (PDT)
Received: (qmail 29383 invoked from network); 27 May 2013 05:53:24 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 May 2013 05:53:24 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=51a2f4d0.xn--i8sz2z.k1305; i=johnl@user.iecc.com; bh=yzE7pf1ZPQkKg1Jw8y2c5x6tDXaO665+tEIi5ThvNMY=; b=epEMzE1o/w63LUw9P2g7c0u/rKy9vwJ6ghj9i5s6VFW70NIDQheb9kFrlP7X3jMndcNpJwzvGXNwuxSlZKVjaU5d74ruhQ17h1mLhZ6MYX1NpgGwrOaQ7hy8E4Rkq/nmF3InXVsUAoarkDgl3y4y3TMJYMMwJ1iSjsmwB5d/a5c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=51a2f4d0.xn--i8sz2z.k1305; olt=johnl@user.iecc.com; bh=yzE7pf1ZPQkKg1Jw8y2c5x6tDXaO665+tEIi5ThvNMY=; b=nCJ2lxKznX/WDjw4LGlKaEzCew5C0NFYaWjU2Fr7BJ7vGnpUcd9zGP4UFkBoTiVUG1mz5WaeQaL+EjQ3/dgbw+gxaCKzcdFwyDZGDC2CyWgRKzOhJwA1jjUXhG/ntZrdzR2DB++Sa9n0sRXyHpI1A8A+TfqQp40jThIixmp1/TI=
Date: 27 May 2013 05:52:57 -0000
Message-ID: <20130527055257.7635.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Issues in wider geographic participation
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 05:53:25 -0000

I think this is a summary of the issues people have mentioned that
discourage participation from LDCs, in rough order of importance.

* People aren't aware the IETF exists, or what it does, or that it has
an open participation model

* People don't read and write English well enough to be comfortable
participating

* People are unaccustomed to and perhaps uncomfortable expressing
overt disagreement

* People don't think they have anything to contribute to an organization
that is mostly people from rich countries

* People don't have adequate Internet access for mail, or to use the
remote participation tools

I have to say that I don't see one or two meetings in South America
addressing any of these.  Given that the incremental cost to the
participants, compared to meeting in North America, would likely be on
the order of a million dollars, it seems to me very likely that there
are better ways to spend the money.

For example, if language and net access is a problem, it might be
interesting to set up a remote participation center in B.A. during one
of the North American meetings (it's one time zone off from Toronto)
with screens and cameras, paid interpreters, and a few volunteers to
help explain what's going on.

R's,
John





From melinda.shore@gmail.com  Sun May 26 23:14:52 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B73BC21F9416 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:14:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[AWL=0.500, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e-qflpXagP3x for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:14:47 -0700 (PDT)
Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by ietfa.amsl.com (Postfix) with ESMTP id EF7DF21F93BB for <ietf@ietf.org>; Sun, 26 May 2013 23:14:46 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id tj12so1521005pac.32 for <ietf@ietf.org>; Sun, 26 May 2013 23:14:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=czmAP5Zd47F68sPCpsC0Lq+Ue+BhEW0h58OOLt7RHrk=; b=Hf1cfR+hQuW6onNV6hOi9NT6/pgbJl7Pa3qVbPClLJmZY6ZymklVY3wb9riFcYmcy6 iAgmAXlZL2Jw4qm1V+h9YADJxVngTgdKAwEFci/bx5LTCsRU3THlDF80mm8XU0rl+HIe p0kGvYkrC5zN1+CUkGN2AXQY3EA5/YN1llVXY4Ulbist6PF5WZIkN7ElwOFuGM/WMcfo nRc+VZpZI3vvtu69ljPFwSfSA5Vu0bV4nnEA0jMuOVL/G/q0Un3plv4E7eAl2C4oXUMw ZLYmOuTrJR80Mk6Z1zpKTW7HnO07fqH/od/2zSILQBcRDYdgMOCrh+f53qFXiNIL0OI5 5ulA==
X-Received: by 10.68.226.39 with SMTP id rp7mr27706612pbc.97.1369635286728; Sun, 26 May 2013 23:14:46 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id vb8sm27285478pbc.11.2013.05.26.23.14.44 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 23:14:45 -0700 (PDT)
Message-ID: <51A2F9D2.3090606@gmail.com>
Date: Sun, 26 May 2013 22:14:42 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan>
In-Reply-To: <20130527055257.7635.qmail@joyce.lan>
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: Mon, 27 May 2013 06:14:52 -0000

On 5/26/13 9:52 PM, John Levine wrote:
> I have to say that I don't see one or two meetings in South America
> addressing any of these. 

I don't, either.  However,

> Given that the incremental cost to the
> participants, compared to meeting in North America, would likely be on
> the order of a million dollars, it seems to me very likely that there
> are better ways to spend the money.

It also seems unlikely to me that that million dollars is otherwise
available.

I like the idea of setting up a remote participation center (doubly-
so if one or more very experienced IETFers who spoke the local language
could be on-site) but it seems very unlikely to me that, say, a Frobnitz
Networks employee would be able to convinced Frobnitz Networks to send
the $400 saved by not going to Buenos Aires to such an undertaking.

Melinda


From sm@resistor.net  Sun May 26 23:20:50 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F7D21F944F for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pix4qq0mBIWO for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:20:49 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8301421F940B for <ietf@ietf.org>; Sun, 26 May 2013 23:20:47 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4R6Kbmp027761; Sun, 26 May 2013 23:20:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369635641; bh=WyFz1KkLMzv1m1Gw70Hg1KK/XYMjsLAGG7blOZbGBEk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WZTNCykKUiulUvLCLMPH3LwmRW/A7vtZhKMu95Fu4kPOqmsiI5smZT+K7oMUDXv8H lZPcqSp0JTJAHnNeXAOk1yQ05ToMKq6aPYYPVyN3ktUuuXT0ErTWaNn8q2IJApD951 yA/T1Udj8IPsZXfPCYyxOLlwTdx7G5FNQdrLNGB8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369635641; i=@resistor.net; bh=WyFz1KkLMzv1m1Gw70Hg1KK/XYMjsLAGG7blOZbGBEk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EyMUGgq5GlCoHL8pjh4SICGbB/roogcDEdLPrxtkrgv1OOpJOog/Tdsd6iRE7JfN8 2JYfjSbjNibw18CnoHfMBXQJGFlfC0NkAeaPVbnZ7EC3Sjy3bnQV0DmFg6U6s1IJ4M f+Tkl0Y+2tEQLR6RREB6VQKHFfzu5gm8uIBLSOB0=
Message-Id: <6.2.5.6.2.20130526221950.0c51c658@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 May 2013 22:51:12 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: More participation from under-represented regions (was: IETF Meeting in South America)
In-Reply-To: <CADnDZ889Wo_1fdF77W0yxnQAAKD=opr3ah4F-afzOfb5+MYQPg@mail.g mail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <CADnDZ889Wo_1fdF77W0yxnQAAKD=opr3ah4F-afzOfb5+MYQPg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 06:20:50 -0000

Hi Abdussalam,
At 16:38 26-05-2013, Abdussalam Baryun wrote:
>I think they SHOULD have, and all of us should do the same, because
>IETF will expand and become stronger by increasing participants from
>ALL Internet community regions. The answers also based on IETF vesion.

The question was about what was done in the past.  It is not about 
what the IESG or IAB is doing or could do in future.

At 16:51 26-05-2013, Abdussalam Baryun wrote:
>There are some from Africa trying to find the way in, but they may not
>mention it, however, training is not important much to make people
>participate but the type of training and its period inside
>organisation not outside. For example, I notice that there was one
>African participant (not me), trying to participate in writing one
>draft for the community, so was he/she encouraged by the WGs,

Does that participant reside in Africa?  Will that participant 
implement the draft by writing code?

Regards,
-sm 


From sm@resistor.net  Sun May 26 23:20:50 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D529221F940B for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:20:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Dc+hNp09ZqT for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:20:49 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8329A21F9452 for <ietf@ietf.org>; Sun, 26 May 2013 23:20:47 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4R6Kbmr027761; Sun, 26 May 2013 23:20:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369635645; bh=ScH2kV7elFSoMmiFNhTB+WkEOW9YFHaQnrZkZ6yPTao=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iOe7P5dkRf6Z+eYJOKQEnzu2oSJrwW0sxrWf6mTHClwGt1OE5W9kWKMFmTIjQxCeU 9/LETWdrFtl2POsj9X/hUA68NLAltZRYCwMslSijNny2HVuIVAp4SkJFNfXJ0KS2SA iPyYuJLEgwSmYW5EdVoWpzRAIYkoqu8U1vJjqhbM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369635645; i=@resistor.net; bh=ScH2kV7elFSoMmiFNhTB+WkEOW9YFHaQnrZkZ6yPTao=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0ysP/qGy5OyayAjyI3evaGKEeis26K6Sn9t+wRlywl2qs7NHd8rt5b26dx7lvGhHH I/JAdBTWk3ZpG/XUf5GFbvWcksIZoQJDemj0/wBR9AvLWOPrtqmmimRX9QuTHKXXTL /ct53tE50u4OYltSTqh3mlEiUGnNPLmq4s6C9gMw=
Message-Id: <6.2.5.6.2.20130526225513.0b7cfd08@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 May 2013 23:07:30 -0700
To: joel jaeggli <joelja@bogus.com>
From: SM <sm@resistor.net>
Subject: Re: More participation from under-represented regions
In-Reply-To: <51A2F309.8010504@bogus.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2F309.8010504@bogus.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, 27 May 2013 06:20:50 -0000

Hi Joel,
At 22:45 26-05-2013, joel jaeggli wrote:
>notable sucesses I don't think of it a fertile training ground for 
>new IETF participants.

I agree that it is not fertile ground for new IETF participants.

>People come to the IETF with work because they have a problem which 
>the work product of their contribution through the IETF activity addresses.
>That's fairly expensive, time consuming, and has uncertain results.

Yes.

Regards,
-sm 


From jmamodio@gmail.com  Sun May 26 23:21:19 2013
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 CAEE821F95EC for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.82
X-Spam-Level: 
X-Spam-Status: No, score=0.82 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.819, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JsxVsxVictWi for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 23:21:15 -0700 (PDT)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by ietfa.amsl.com (Postfix) with ESMTP id E21F521F9601 for <ietf@ietf.org>; Sun, 26 May 2013 23:21:14 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id g12so8342193oah.26 for <ietf@ietf.org>; Sun, 26 May 2013 23:21:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=opmSW0R9TEBQye/Y+++5t+nuLqvdvXvSsBtkcLAIgv8=; b=CJq9WY73rvFr/aES9VFxzkcQ6Uc2UxuaIBbmiLj3qIudENO1dc2OSf84uRgQKHt5Xo K5kmuq+XPnqq9XMHNy16cUFFWXqvytPIheY3a8XYpqSvSaMQYtf4sDHol0YRIrGPbGfe 77TqzP0oTBQoDMWcknt0P/T/A5uKGHXXN8k0i/aecSceGtQSoewz/TRqAuUXfOHTq94i YEEOPbqCFztFNNsBiwByxDVKwDOZGPToOyGMyg7Nej2oe3B00nCufRi3gXU0LMX8iCU7 wYsZNEKIedt66MgHEPS6DBucOrL3BkOvE2Tp6tUKNM3A8AmXCRsYzXx0cl8w0pkiWt52 LnBA==
X-Received: by 10.182.113.169 with SMTP id iz9mr17311559obb.40.1369635669301;  Sun, 26 May 2013 23:21:09 -0700 (PDT)
Received: from [10.0.10.105] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id x5sm29888582oep.1.2013.05.26.23.21.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 May 2013 23:21:08 -0700 (PDT)
References: <20130527041505.7301.qmail@joyce.lan>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20130527041505.7301.qmail@joyce.lan>
Content-Type: multipart/alternative; boundary=Apple-Mail-6C0DFD2A-FD57-4E80-A190-230A841496BF
Content-Transfer-Encoding: 7bit
Message-Id: <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
Date: Mon, 27 May 2013 01:16:49 -0500
To: John Levine <johnl@taugh.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <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, 27 May 2013 06:21:20 -0000

--Apple-Mail-6C0DFD2A-FD57-4E80-A190-230A841496BF
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable


The financial and political current situation is more complex than just the m=
anipulation and restrictions on currency exchange and payment of obligations=
.

I feel that is totally OT but for example we have supporters of the current g=
overnment like this one, claiming to be a writer, that if you are able to re=
ad in Spanish or helped by a translator to read his article, you will learn t=
hat he is propagating a message that says "Internet is the secret weapon of t=
he imperialism."=20

http://sumateacristina.net/m/blogpost?id=3D6438092%3ABlogPost%3A524963

His view is shared by many, so in the event IETF gets to meet in Buenos Aire=
s, if the meeting becomes public, don't be surprised to see some coordinated=
 political manifestation.

Funny thing, does he realize what is he using to propagate his message ?

I'd really love to see folks from my country become more involved with IETF,=
 the opportunity for more outreach and engagement, and also visit my country=
, but as Dave said IETF is not in the tourism business and there could be mo=
re effective ways to develop some program with long term effects to drive mo=
re regional participation.

As I said before, just a meeting won't do.

Regards,

-Jorge


--Apple-Mail-6C0DFD2A-FD57-4E80-A190-230A841496BF
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br></div><div>The financial and polit=
ical current situation is more complex than just the manipulation and restri=
ctions on currency exchange and payment of obligations.</div><div><br></div>=
<div>I feel that is totally OT but for example we have supporters of the cur=
rent government like this one, claiming to be a writer, that if you are able=
 to read in Spanish or helped by a translator to read his article, you will l=
earn that he is propagating a message that says "Internet is the secret weap=
on of the imperialism."&nbsp;</div><div><br></div><div><span style=3D"font-f=
amily: '.HelveticaNeueUI'; font-size: 15px; line-height: 19px; white-space: n=
owrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-comp=
osition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame=
-color: rgba(77, 128, 180, 0.230469); -webkit-text-size-adjust: none; "><a h=
ref=3D"http://sumateacristina.net/m/blogpost?id=3D6438092%3ABlogPost%3A52496=
3">http://sumateacristina.net/m/blogpost?id=3D6438092%3ABlogPost%3A524963</a=
></span></div><div><br></div><div>His view is shared by many, so in the even=
t IETF gets to meet in Buenos Aires, if the meeting becomes public, don't be=
 surprised to see some coordinated political manifestation.</div><div><br></=
div><div>Funny thing, does he realize what is he using to propagate his mess=
age ?</div><div><br></div><div>I'd really love to see folks from my country b=
ecome more involved with IETF, the opportunity for more outreach and engagem=
ent, and also visit my country, but as Dave said IETF is not in the tourism b=
usiness and there could be more effective ways to develop some program with l=
ong term effects to drive more regional participation.</div><div><br></div><=
div>As I said before, just a meeting won't do.</div><div><br></div><div>Rega=
rds,<br><br>-Jorge</div><div><br></div></body></html>=

--Apple-Mail-6C0DFD2A-FD57-4E80-A190-230A841496BF--

From tjc@ecs.soton.ac.uk  Mon May 27 00:21:09 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3186821F911B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 00:21:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.202
X-Spam-Level: 
X-Spam-Status: No, score=-1.202 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sRLHmNayPUeX for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 00:21:08 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 452C721F90EF for <ietf@ietf.org>; Mon, 27 May 2013 00:21:07 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4R7KtxW013982;  Mon, 27 May 2013 08:20:55 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4R7KtxW013982
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369639255; bh=w0GPBiPIzq5tGx14L6TWgKMKEfo=; h=References:Mime-Version:In-Reply-To:Cc:From:Subject:Date:To; b=gdAAx2bPy/EkFjtbCLIHaPkVWYlhqD6FjZDpW8cVwq8Hx4y9DzAvgN/755vDm957T uRHQW8++El3bk1z6VupN0Id5JXsdYPXRLhIufuFTxx4r6a7hgBVjWp/DDo7RqS15Dq t4HvF7Kw/uUGt+SPkPcV2gH/kwOvBfp0MqkIYv68=
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 p4Q8Ky0430643887D3 ret-id none; Mon, 27 May 2013 08:20:55 +0100
Received: from [192.168.1.101] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4R7JZVD011185 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 27 May 2013 08:19:36 +0100
References: <20130527041505.7301.qmail@joyce.lan> <A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20130527041505.7301.qmail@joyce.lan>
Content-Type: multipart/alternative; boundary=Apple-Mail-7F6CDCE3-9977-4D2A-805B-044682AA32AD
Content-Transfer-Encoding: 7bit
Message-ID: <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk>
X-Mailer: iPad Mail (10B329)
From: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: financial fun with an IETF Meeting in South America
Date: Mon, 27 May 2013 08:19:35 +0100
To: John Levine <johnl@taugh.com>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4Q8Ky043064388700; tid=p4Q8Ky0430643887D3; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4R7KtxW013982
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <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, 27 May 2013 07:21:09 -0000

--Apple-Mail-7F6CDCE3-9977-4D2A-805B-044682AA32AD
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

On 27 May 2013, at 05:15, "John Levine" <johnl@taugh.com> wrote:

>> The move appears to be related to new, restrictive=20
>> regulations the Argentine government has imposed on currency exchanges.'=20=

>> According to the Telegraph, 'The new regulations required anyone wanting=20=

>> to change Argentine pesos into another currency to submit an online=20
>> request for permission to AFIP, the Argentine equivalent of HM Revenue &=20=

>> Customs. ..."
>=20
> This isn't likely to change soon.

Going into the country isn't the problem, more importantly it seems that if y=
ou don't spend all your pesos in Argentina, you can't change them back to yo=
ur own currency:

http://www.tripadvisor.co.uk/Travel-g294266-s601/Argentina:Banks.And.Money.h=
tml
(see last paragraph)

I just keep a pool of Euros and dollars (US and Canadian) which I never chan=
ge back to my own currency, as I visit these countries a fair bit, but it is=
 a concern to pick a venue where any cash I get in advance is lost if unspen=
t.

Is this above advice from Tripadvisor correct?

Tim

--Apple-Mail-7F6CDCE3-9977-4D2A-805B-044682AA32AD
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div style=3D"-webkit-text-size-adjust: aut=
o; ">On 27 May 2013, at 05:15, "John Levine" &lt;<a href=3D"mailto:johnl@tau=
gh.com">johnl@taugh.com</a>&gt; wrote:</div><div style=3D"-webkit-text-size-=
adjust: auto; "><br></div><blockquote type=3D"cite" style=3D"-webkit-text-si=
ze-adjust: auto; "><div><blockquote type=3D"cite"><span>The move appears to b=
e related to new, restrictive </span><br></blockquote><blockquote type=3D"ci=
te"><span>regulations the Argentine government has imposed on currency excha=
nges.' </span><br></blockquote><blockquote type=3D"cite"><span>According to t=
he Telegraph, 'The new regulations required anyone wanting </span><br></bloc=
kquote><blockquote type=3D"cite"><span>to change Argentine pesos into anothe=
r currency to submit an online </span><br></blockquote><blockquote type=3D"c=
ite"><span>request for permission to AFIP, the Argentine equivalent of HM Re=
venue &amp; </span><br></blockquote><blockquote type=3D"cite"><span>Customs.=
 ..."</span><br></blockquote><span></span><br><span>This isn't likely to cha=
nge soon.</span><br></div></blockquote><div style=3D"-webkit-text-size-adjus=
t: auto; "><br></div><span style=3D"-webkit-text-size-adjust: auto;">Going i=
nto the country isn't the problem, more importantly it seems that if you don=
't spend all your pesos in Argentina, you can't change them back to your own=
 currency:</span><div style=3D"-webkit-text-size-adjust: auto; "><br></div><=
div style=3D"-webkit-text-size-adjust: auto; "><span style=3D"font-family: '=
.HelveticaNeueUI'; font-size: 15px; line-height: 19px; white-space: nowrap; -=
webkit-tap-highlight-color: rgba(26, 26, 26, 0.296875); -webkit-composition-=
fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: r=
gba(77, 128, 180, 0.230469); -webkit-text-size-adjust: none; "><a href=3D"ht=
tp://www.tripadvisor.co.uk/Travel-g294266-s601/Argentina:Banks.And.Money.htm=
l">http://www.tripadvisor.co.uk/Travel-g294266-s601/Argentina:Banks.And.Mone=
y.html</a></span></div><div><span style=3D"font-size: 15px; line-height: 19p=
x; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.2929=
69); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-=
composition-frame-color: rgba(77, 128, 180, 0.230469);">(see last paragraph)=
</span></div><div><span style=3D"font-size: 15px; line-height: 19px; white-s=
pace: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webk=
it-composition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-compositio=
n-frame-color: rgba(77, 128, 180, 0.230469);"><br></span></div><div><span st=
yle=3D"font-size: 15px; line-height: 19px; white-space: nowrap; -webkit-tap-=
highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-fill-color:=
 rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: rgba(77, 12=
8, 180, 0.230469);">I just keep a pool of Euros and dollars (US and Canadian=
) which I never change back to my own currency, as I visit these countries a=
 fair bit, but it is a concern to pick a venue where any cash I get in advan=
ce is lost if unspent.</span></div><div><span style=3D"font-size: 15px; line=
-height: 19px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26=
, 26, 0.292969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.23046=
9); -webkit-composition-frame-color: rgba(77, 128, 180, 0.230469);"><br></sp=
an></div><div><span style=3D"font-size: 15px; line-height: 19px; white-space=
: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-c=
omposition-fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-fr=
ame-color: rgba(77, 128, 180, 0.230469);">Is this above advice from Tripadvi=
sor correct?</span></div><div><span style=3D"font-size: 15px; line-height: 1=
9px; white-space: nowrap; -webkit-tap-highlight-color: rgba(26, 26, 26, 0.29=
2969); -webkit-composition-fill-color: rgba(175, 192, 227, 0.230469); -webki=
t-composition-frame-color: rgba(77, 128, 180, 0.230469);"><br></span></div><=
div><span style=3D"font-size: 15px; line-height: 19px; white-space: nowrap; -=
webkit-tap-highlight-color: rgba(26, 26, 26, 0.292969); -webkit-composition-=
fill-color: rgba(175, 192, 227, 0.230469); -webkit-composition-frame-color: r=
gba(77, 128, 180, 0.230469);">Tim</span></div><div><blockquote type=3D"cite"=
 style=3D"-webkit-text-size-adjust: auto; "><div><span></span></div></blockq=
uote></div></body></html>=

--Apple-Mail-7F6CDCE3-9977-4D2A-805B-044682AA32AD--

From jari.arkko@piuha.net  Mon May 27 01:08:40 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5089721F8CA5 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 01:08:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7+OOCfC9tBU for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 01:08:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DDD4321F8B64 for <ietf@ietf.org>; Mon, 27 May 2013 01:08:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C7CBE2CC53 for <ietf@ietf.org>; Mon, 27 May 2013 11:08:32 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63M1ykhfCikl for <ietf@ietf.org>; Mon, 27 May 2013 11:08:32 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3FA7F2CC48 for <ietf@ietf.org>; Mon, 27 May 2013 11:08:32 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <51A2D4E8.5050605@dcrocker.net>
Date: Mon, 27 May 2013 11:08:32 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 08:08:40 -0000

I'm not quite sure the currency exchange issues are key for this =
discussion. FWIW, I think you can still budget in Euros for the Berlin =
meeting, but I'm only 97% sure :-)

Anyway, I wanted to highlight that, as has been pointed out by many, =
just meeting at some place makes little sense. But the question on the =
table is not just that. We're asking both about the meeting and about =
what other forms of getting additional participation from the region =
would be useful. My personal opinion is that we need to do multiple =
things to make an impact. And again IMO, meetings should be a part of =
that set. But definitely not alone. I know many of you have been very =
willing to help out in going out to new areas of the world to speak, =
gather input, and get familiar with more people. Thank you. I certainly =
plan to do that as well.

The other thing that was mentioned was political pressure to appear =
international. My opinion is that doing something purely based on that =
would be silly and potentially harmful. However, I think we have a =
situation where we simultaneously need wider involvement from different =
organisations & areas, are reaching out to new types of participants =
(including, shock! even regulators in cases like PAWS), and do face some =
pressures about how we are perceived. An IETF that is open, has broad =
participation that is based on actual technical substance is in a very =
good position to continue to be perceived as the authority it is. This =
is not to say we are not already about all those things; we are. But I =
think we definitely need to go even further.

A few other responses:

Randy wrote:

>  (1) "need-based" evangelism.  Outreach efforts are more
>      effective if they sincerely address specific needs of
>      the target community.  Does face-to-face participation in
>      the IETF offer things practitioners in under-represented
>      regions feel they need?  As long as we focus on how it
>      could help *us*, rather than what needs it would address
>      for them, it'll be far less effective than it could be.


Very true.

Melinda wrote:

> The industry sector bias in IETF participation is
> possibly compounding the regional bias.


Yes.

Jari


From aeopare@gmail.com  Mon May 27 03:01:09 2013
Return-Path: <aeopare@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 647E621F8F6D for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ofjgfBL65tFM for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:01:08 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 17F0221F8F41 for <ietf@ietf.org>; Mon, 27 May 2013 03:01:06 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id wo10so4317217obc.38 for <ietf@ietf.org>; Mon, 27 May 2013 03:01:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UT3kLSNGZ1HSXkFd8ykfzmi3dVRvf+NzS0QdZksg4SA=; b=YJ+368SMAmj5mySg5gttnEPiAazJqYcmfynFqVkbnhbilzrP3VkEgRWwBr0/k3OgK5 y6dY5P0qAyYLplcrMeTBG9eZOLNgeMR2YwjopLMJKG4S3u9G1r7ZcIvz8B35x4UR5Si5 six0swy5Sw6TfmQc8q2T3UpZ9QmE6tjSmqZQrgOhM3ORrB0KcvxxOuK+TPHjAF1WyxPK wR+1a8Rl9IfZmI+W6llvwD9lQLP9yiYGfihnvjbVDnomZt8O2O/5zir02wSlQKjswjsZ i/gfhcw22yRnMg3qPQ++ZZ5OSZsK/3f3McYli/ovENwjOgiVWtWw4b4hbTxhngt+N4uC lQ9Q==
MIME-Version: 1.0
X-Received: by 10.60.134.71 with SMTP id pi7mr5268099oeb.107.1369648865790; Mon, 27 May 2013 03:01:05 -0700 (PDT)
Received: by 10.60.144.7 with HTTP; Mon, 27 May 2013 03:01:05 -0700 (PDT)
In-Reply-To: <51A2A296.1010305@braga.eti.br>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br>
Date: Mon, 27 May 2013 10:01:05 +0000
Message-ID: <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com>
Subject: Re: More participation from under-represented regions
From: "Edwin A. Opare" <aeopare@gmail.com>
To: Juliao Braga <juliao@braga.eti.br>
Content-Type: multipart/alternative; boundary=047d7b4720761cd4a504ddb03aec
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, 27 May 2013 10:01:09 -0000

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

Juliao,

Thanks for the stats.

To borrow your words: > "the issue is to establish a systematic and effecti=
ve
process in under-represented regions", and that I believe should start at
the grassroots level & at the regional/national level .

Why does the numbers from the AfriNIC and LACNIC regions keep declining?
Don't these regions operate networks like everyone else? Which areas/WGs of
the IETF will they find particularly helpful/useful to subscribe to? Are
the AfNOG annual meetings enough to encourage participation from the
AfriNIC region? Could the IETF run "a day or two event" annually at the
AfNOG meetings as part of the "AfNOG Tutorials Workshop" to create a lot
more awareness and elicit participation? Could the institution of "IETF
Champions" in the under-rep regions where ISOC has presence influence
participation from these regions?

The ISOC Ghana Chapter for example runs a GhNOG workshop (4 day event)
annually in the month of July where workshop participants are trained in a
variety of areas relating to System Administration, Network Monitoring &
Management, CERTs and many more.

Going into the next workshop this July, the Chapter plans to dedicate a day
of the workshop to awareness creation about the IETF. Will this increase
participation from Ghana in any way? If the approach is done right with a
keen focus on the needs of participants it most definitely will.

At best we all agree there is the need for active participation and
inclusiveness from all the regions if the Internet is to develop and evolve
to its fullest potential. Let's work together to get EVERY ENGINEER on
board!!

Best,

EAO

On Mon, May 27, 2013 at 12:02 AM, Juliao Braga <juliao@braga.eti.br> wrote:

> SM, FYI:
>
> Inscriptions at IETF 86 [1]:
>
> ARIN     RIPE     APNIC    AFRINIC      LACNIC
>  671      258      237        31           26
>   54.87%   21.10%   19.38%     2.53%        2.13%
>
> Inscriptions since IETF 72 to IETF 85. For Year, RIR and Country:
> http://rfc.pegasus.com.br/ietf.php
>
> I think the local of the meeting no change the numbers. For me the
> apparent common sense prevails in the list and Dave Crocker pointed
> (...let's attack that...): the issue is to establish a systematic and
> effective process in under-represented regions (countries, I think).
>
> Regards,
>
> Juli=E3o
> 1. http://rfc.pegasus.com.br/ietf86.php (including, year, RIR and Country=
)
>
>
> Em 26/05/2013 20:01, SM escreveu:
> > AfNOG has trained hundreds of people in Africa.  Those people do not
> > participate on the mailing list.  There are some people from Africa who
> > have attended IETF meetings.  They don't participate in the IETF.  Why
> > is it that there are some participants from South America whereas there
> > aren't any participants from Africa?
>

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

<div dir=3D"ltr">Juliao,<div><br></div><div>Thanks for the stats.=A0</div><=
div><br></div><div>To borrow your words: &gt; &quot;<span style=3D"font-fam=
ily:arial,sans-serif;font-size:13px">the issue is to establish a systematic=
 and=A0</span><span style=3D"font-family:arial,sans-serif;font-size:13px">e=
ffective process in under-represented regions&quot;, and that I believe sho=
uld start at the grassroots level &amp; at the regional/national level .</s=
pan></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><div><font face=3D"arial, sans-serif">Why does the numbers from=
 the AfriNIC and LACNIC regions keep declining? Don&#39;t these regions ope=
rate networks like everyone else? Which areas/WGs of the IETF will they fin=
d particularly helpful/useful to subscribe to?=A0</font><span style=3D"font=
-family:arial,sans-serif">Are the AfNOG annual meetings enough to encourage=
 participation from the AfriNIC region? Could the IETF run &quot;a day or t=
wo event&quot; annually at the AfNOG meetings as part of the &quot;AfNOG Tu=
torials Workshop&quot; to create a lot more awareness and elicit participat=
ion? Could the institution of &quot;IETF Champions&quot; in the under-rep r=
egions where ISOC has presence influence participation from these regions?<=
/span></div>
</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">The ISOC Ghana Chapter for example runs a GhNOG workshop (4 day ev=
ent) annually in the month of July where workshop participants are trained =
in a variety of areas relating to System Administration, Network Monitoring=
 &amp; Management, CERTs and many more.</span></div>
<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Going into the next workshop this July, the Chapter plans to dedic=
ate a day of the workshop to awareness creation about the IETF. Will this i=
ncrease participation from Ghana in any way? If the approach is done right =
with a keen focus on the needs of participants it most definitely will.=A0<=
/span></div>
<div><br></div><div><font face=3D"arial, sans-serif">At best we all agree t=
here is the need for active participation and inclusiveness from all the re=
gions if the Internet is to develop and evolve to its fullest potential. Le=
t&#39;s work together to get EVERY ENGINEER on board!!<br>
</font><div class=3D"gmail_extra"><br clear=3D"all"><div style>Best,</div><=
div style><br></div><div style>EAO</div><br><div class=3D"gmail_quote">On M=
on, May 27, 2013 at 12:02 AM, Juliao Braga <span dir=3D"ltr">&lt;<a href=3D=
"mailto:juliao@braga.eti.br" target=3D"_blank">juliao@braga.eti.br</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">SM, FYI:<br>
<br>
Inscriptions at IETF 86 [1]:<br>
<br>
ARIN =A0 =A0 RIPE =A0 =A0 APNIC =A0 =A0AFRINIC =A0 =A0 =A0LACNIC<br>
=A0671 =A0 =A0 =A0258 =A0 =A0 =A0237 =A0 =A0 =A0 =A031 =A0 =A0 =A0 =A0 =A0 =
26<br>
=A0 54.87% =A0 21.10% =A0 19.38% =A0 =A0 2.53% =A0 =A0 =A0 =A02.13%<br>
<br>
Inscriptions since IETF 72 to IETF 85. For Year, RIR and Country:<br>
<a href=3D"http://rfc.pegasus.com.br/ietf.php" target=3D"_blank">http://rfc=
.pegasus.com.br/ietf.php</a><br>
<br>
I think the local of the meeting no change the numbers. For me the<br>
apparent common sense prevails in the list and Dave Crocker pointed<br>
(...let&#39;s attack that...): the issue is to establish a systematic and<b=
r>
effective process in under-represented regions (countries, I think).<br>
<br>
Regards,<br>
<br>
Juli=E3o<br>
1. <a href=3D"http://rfc.pegasus.com.br/ietf86.php" target=3D"_blank">http:=
//rfc.pegasus.com.br/ietf86.php</a> (including, year, RIR and Country)<br>
<br>
<br>
Em 26/05/2013 20:01, SM escreveu:<br>
<div class=3D""><div class=3D"h5">&gt; AfNOG has trained hundreds of people=
 in Africa. =A0Those people do not<br>
&gt; participate on the mailing list. =A0There are some people from Africa =
who<br>
&gt; have attended IETF meetings. =A0They don&#39;t participate in the IETF=
. =A0Why<br>
&gt; is it that there are some participants from South America whereas ther=
e<br>
&gt; aren&#39;t any participants from Africa?<br>
</div></div></blockquote></div><br></div></div></div>

--047d7b4720761cd4a504ddb03aec--

From lars@netapp.com  Mon May 27 03:06:12 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5056F21F8E12 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:06:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.146
X-Spam-Level: 
X-Spam-Status: No, score=-9.146 tagged_above=-999 required=5 tests=[AWL=0.054,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-8, SARE_SUB_RAND_LETTRS4=0.799]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7D-GH2GMzEZl for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:06:08 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA1621F8AEA for <ietf@ietf.org>; Mon, 27 May 2013 03:06:08 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,750,1363158000"; d="scan'208";a="58321727"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 27 May 2013 03:06:08 -0700
Received: from vmwexceht01-prd.hq.netapp.com (vmwexceht01-prd.hq.netapp.com [10.106.76.239]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4RA67pw024661 for <ietf@ietf.org>; Mon, 27 May 2013 03:06:08 -0700 (PDT)
Received: from VMWEXCEHT06-PRD.hq.netapp.com (10.106.77.104) by vmwexceht01-prd.hq.netapp.com (10.106.76.239) with Microsoft SMTP Server (TLS) id 14.3.123.3; Mon, 27 May 2013 03:06:07 -0700
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Mon, 27 May 2013 03:06:07 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: IETF list <ietf@ietf.org>
Subject: Fwd: [IRTF-Announce] Applied Networking Research Prize 2013 presentation		at IETF-87
Thread-Topic: [IRTF-Announce] Applied Networking Research Prize 2013 presentation		at IETF-87
Thread-Index: AQHOWsHNSewBXx8D8EatwTKw5Dyq0Q==
Date: Mon, 27 May 2013 10:06:06 +0000
Message-ID: <8551F5E9-A615-481B-B539-E2BC89C68F48@netapp.com>
References: <9B4B749D-239D-44AB-B9C4-F8D3095D9249@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="utf-8"
Content-ID: <777AA9B3EB0B6C4B8CC6B358CBB3C578@hq.netapp.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "anrp@irtf.org" <anrp@irtf.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, 27 May 2013 10:06:12 -0000

DQoNCkJlZ2luIGZvcndhcmRlZCBtZXNzYWdlOg0KDQo+IEZyb206ICJFZ2dlcnQsIExhcnMiIDxs
YXJzQG5ldGFwcC5jb20+DQo+IFN1YmplY3Q6IFtJUlRGLUFubm91bmNlXSBBcHBsaWVkIE5ldHdv
cmtpbmcgUmVzZWFyY2ggUHJpemUgMjAxMyBwcmVzZW50YXRpb24JIGF0IElFVEYtODcNCj4gRGF0
ZTogTWF5IDI3LCAyMDEzIDEyOjAxOjAxIEdNVCswMjowMA0KPiBUbzogImlydGYtYW5ub3VuY2VA
aXJ0Zi5vcmciIDxpcnRmLWFubm91bmNlQGlydGYub3JnPiwgImlydGYtZGlzY3Vzc0BpcnRmLm9y
ZyIgPGlydGYtZGlzY3Vzc0BpcnRmLm9yZz4NCj4gUmVwbHktVG86ICJhbnJwQGlydGYub3JnIiA8
YW5ycEBpcnRmLm9yZz4NCj4gDQo+IA0KPiBIaSwNCj4gDQo+IHdlIGFyZSBleHRyZW1lbHkgcGxl
YXNlZCB0byByZXBvcnQgdGhhdCBmb3IgdGhlIDIwMTMgYXdhcmQgcGVyaW9kIG9mDQo+IHRoZSBB
cHBsaWVkIE5ldHdvcmtpbmcgUmVzZWFyY2ggUHJpemUgKEFOUlApLCAzNiBlbGlnaWJsZSBub21p
bmF0aW9ucw0KPiB3ZXJlIHJlY2VpdmVkLiBFYWNoIHN1Ym1pc3Npb24gd2FzIHJldmlld2VkIGJ5
IGVpZ2h0IG1lbWJlcnMgb2YgdGhlDQo+IHNlbGVjdGlvbiBjb21taXR0ZWUgYWNjb3JkaW5nIHRv
IGEgZGl2ZXJzZSBzZXQgb2YgY3JpdGVyaWEsIGluY2x1ZGluZw0KPiBzY2llbnRpZmljIGV4Y2Vs
bGVuY2UgYW5kIHN1YnN0YW5jZSwgdGltZWxpbmVzcywgcmVsZXZhbmNlLCBhbmQNCj4gcG90ZW50
aWFsIGltcGFjdCBvbiB0aGUgSW50ZXJuZXQuDQo+IA0KPiBCYXNlZCBvbiB0aGlzIHJldmlldywg
Zm91ciBzdWJtaXNzaW9ucyB3ZXJlIGF3YXJkZWQgYW4gQU5SUCBpbiAyMDEzLA0KPiB0aGUgZmly
c3Qgb2Ygd2hpY2ggd2FzIGFscmVhZHkgcHJlc2VudGVkIGF0IElFVEYtODYuIA0KPiANCj4gVGhl
IHNlY29uZCBhbmQgdGhpcmQgYXdhcmRzIHdpbGwgaGFwcGVuIGF0IElFVEYtODcgaW4gQmVybGlu
LCBHZXJtYW55Lg0KPiBUaGV5IGdvIHRvOg0KPiANCj4gICoqKiBUZS1ZdWFuIEh1YW5nICoqKiBm
b3IgaW5zaWdodHMgaW50byB0aGUgZGlmZmljdWx0aWVzIG9mIHJhdGUNCj4gIGFkYXB0YXRpb24g
Zm9yIHN0cmVhbWluZyB2aWRlbzoNCj4gDQo+ICAgIFRlLVl1YW4gSHVhbmcsIE5pa2hpbCBIYW5k
aWdvbCwgQnJhbmRvbiBIZWxsZXIsIE5pY2sgTWNLZW93bg0KPiAgICBhbmQgUmFtZXNoIEpvaGFy
aS4gQ29uZnVzZWQsIFRpbWlkLCBhbmQgVW5zdGFibGU6IFBpY2tpbmcgYQ0KPiAgICBWaWRlbyBT
dHJlYW1pbmcgUmF0ZSBpcyBIYXJkLiBQcm9jLiBBQ00gSW50ZXJuZXQgTWVhc3VyZW1lbnQNCj4g
ICAgQ29uZmVyZW5jZSAoSU1DKSxOb3ZlbWJlciAyMDEyLCBCb3N0b24sIE1BLCBVU0EuDQo+IA0K
PiAgKioqIExhdXJlbnQgVmFuYmV2ZXIgKioqIGZvciBwcm9wb3NpbmcgYSBmcmFtZXdvcmsgdG8g
YWxsb3cgc2VhbWxlc3MNCj4gIEJHUCByZWNvbmZpZ3VyYXRpb25zOg0KPiANCj4gICAgU3RlZmFu
byBWaXNzaWNjaGlvLCBMYXVyZW50IFZhbmJldmVyLCBDcmlzdGVsIFBlbHNzZXIsIEx1Y2ENCj4g
ICAgQ2l0dGFkaW5pLCBQaWVycmUgRnJhbmNvaXMgYW5kIE9saXZpZXIgQm9uYXZlbnR1cmUuIElt
cHJvdmluZw0KPiAgICBOZXR3b3JrIEFnaWxpdHkgd2l0aCBTZWFtbGVzcyBCR1AgUmVjb27vrIFn
dXJhdGlvbnMuIFByb2MuIElFRUUvQUNNDQo+ICAgIFRyYW5zYWN0aW9ucyBvbiBOZXR3b3JraW5n
IChUT04pLCBUbyBBcHBlYXIuDQo+IA0KPiBUZS1ZdWFuIGFuZCBMYXVyZW50IGhhdmUgYmVlbiBp
bnZpdGVkIHRvIHByZXNlbnQgaGVyIGZpbmRpbmdzIGluIHRoZSBJUlRGDQo+IE9wZW4gTWVldGlu
ZyBkdXJpbmcgSUVURi04NywgSnVseSAyOCAtIEF1Z3VzdCAyLCAyMDEzIGluIEJlcmxpbiwgR2Vy
bWFueS4NCj4gSm9pbiB0aGVtIHRoZXJlIQ0KPiANCj4gVGhlIGNhbGwgZm9yIEFOUlAgbm9taW5h
dGlvbnMgZm9yIHRoZSAyMDE0IGF3YXJkcyBjeWNsZSB3aWxsIG9wZW4gaW4gdGhlDQo+IGZhbGwg
b2YgMjAxMy4gUmVhZCBtb3JlIGFib3V0IHRoZSBBTlJQIGF0IGh0dHA6Ly9pcnRmLm9yZy9hbnJw
Lg0KPiANCj4gUGxlYXNlIHN1YnNjcmliZSB0byB0aGUgSVJURi1Bbm5vdW5jZSBtYWlsaW5nIGxp
c3QgaW4gb3JkZXIgdG8gcmVjZWl2ZQ0KPiBmdXR1cmUgY2FsbHMgZm9yIEFOUlAgbm9taW5hdGlv
bnMgYW5kIGpvaW4gSVNPQyB0byBzdGF5IGluZm9ybWVkIG9mDQo+IG90aGVyIG5ldHdvcmtpbmcg
cmVzZWFyY2ggaW5pdGlhdGl2ZXM6DQo+IA0KPiAgaHR0cDovL2lydGYub3JnL21haWxtYW4vbGlz
dGluZm8vaXJ0Zi1hbm5vdW5jZQ0KPiAgaHR0cDovL2lzb2Mub3JnL2pvaW4NCj4gDQo+IFJlZ2Fy
ZHMsDQo+IA0KPiBMYXJzIEVnZ2VydCwgSVJURiBDaGFpciAgICAgICAgICAgIGh0dHA6Ly9pcnRm
Lm9yZy9hbnJwDQo+IE1hdCBGb3JkLCBJbnRlcm5ldCBTb2NpZXR5ICAgICAgICAgaHR0cDovL2lz
b2Mub3JnL3Jlc2VhcmNoDQo+IA0KPiAtLQ0KPiANCj4gMjAxMyBBTlJQIFNlbGVjdGlvbiBDb21t
aXR0ZWUNCj4gDQo+IE1hcmsgQWxsbWFuLCBJQ0lSDQo+IE1hcmNlbG8gQmFnbnVsbywgVUMzTQ0K
PiBMb3UgQmVyZ2VyLCBMYWJODQo+IE9saXZpZXIgQm9uYXZlbnR1cmUsIFVDTCBMb3V2YWluDQo+
IFJvc3MgQ2FsbG9uLCBKdW5pcGVyDQo+IExhcnMgRWdnZXJ0LCBOZXRBcHANCj4gT2xpdmllciBG
ZXN0b3IsIElOUklBDQo+IE1hdCBGb3JkLCBJU09DDQo+IExpc2FuZHJvIEdyYW52aWxsZSwgVUZS
R1MNCj4gVm9sa2VyIEhpbHQsIEJlbGwgTGFicw0KPiBTdXJlc2ggS3Jpc2huYW4sIEVyaWNzc29u
DQo+IERhbiBNYXNzZXksIENvbG9yYWRvIFN0YXRlDQo+IEFsIE1vcnRvbiwgQVQmVCBMYWJvcmF0
b3JpZXMNCj4gSsO2cmcgT3R0LCBBYWx0byBVbml2ZXJzaXR5DQo+IENvbGluIFBlcmtpbnMsIFVu
aXZlcnNpdHkgb2YgR2xhc2dvdw0KPiBTdGVmYW5vIFByZXZpZGksIENpc2NvDQo+IErDvHJnZW4g
U2Now7Zud8OkbGRlciwgSmFjb2JzIFVuaXZlcnNpdHkgQnJlbWVuDQo+IFlhbmcgUmljaGFyZCBZ
YW5nLCBZYWxlDQo+IExpeGlhIFpoYW5nLCBVQ0xBDQoNCg==

From abdussalambaryun@gmail.com  Mon May 27 03:10:43 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E92E21F8AEA for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:10:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2N9ICfPYq4uW for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:10:38 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 8499521F90F1 for <ietf@ietf.org>; Mon, 27 May 2013 03:10:38 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id g10so6449820pdj.13 for <ietf@ietf.org>; Mon, 27 May 2013 03:10:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=I8ETa8Pzs/LwyhnFwLbOXPQrRLaxW1ERwAZquPnhNNw=; b=qRTmgvpYt9jcgA8GU9wZ+ltWjV9pCN8/q1XC9+Ovr6F90bZ9ByXd5+o1j3WlA7lDn0 OjokfXq/qGIoFRk9U9XYYOgARoFLVVvVVTYSUspmvMt18XM+YVvbR+Smdx+S1o/vueu3 veRN1PHcD/MCrK43YQ0pthmMzOZ+cN4HquX5nFGx2qk8kTSuyZ5G07W3nVlRIs1j2Fxj nk/6zsAmZXusk6eKQeI5R6yhhQPPhVG5Alru5aFWUSEWXaf+q+BQtxPHgBweYxtLxLvy Bq7Agy6IC7WjZvUVoHcozU1uhKUDq8hHNgLzk9p2UFIhfFEZqYTC3rIsybK9+P+A3E+z pFwA==
MIME-Version: 1.0
X-Received: by 10.66.144.98 with SMTP id sl2mr29475945pab.92.1369649438319; Mon, 27 May 2013 03:10:38 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 27 May 2013 03:10:38 -0700 (PDT)
Date: Mon, 27 May 2013 12:10:38 +0200
Message-ID: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com>
Subject: Participation per Region of Authoring IETF documents vs Marketing
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 10:10:43 -0000

 Each IETF document mentions the authors place address (I may suggest
adding region, as a categorised by IETF), but not sure of history
statistics of how many IETF-documents produced by authors in South
America, Africa, or Asia, or others.

 I think it is a good marketing start for IETF to get more
Informational-RFCs input from regions by guiding their inputs.
Furthermore, if IETF helds a meeting in one region with very low
participation, then Why not that IETF encourages people to involve in
joining authors of interested documents to that region and interested
to IETF as well?

AB

From lars@netapp.com  Mon May 27 03:51:39 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C00B21F90F1 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.873
X-Spam-Level: 
X-Spam-Status: No, score=-9.873 tagged_above=-999 required=5 tests=[AWL=0.726,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pEKiiBJIZ8P1 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:51:34 -0700 (PDT)
Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by ietfa.amsl.com (Postfix) with ESMTP id A91A321F8EA5 for <ietf@ietf.org>; Mon, 27 May 2013 03:51:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,750,1363158000"; d="scan'208";a="260420092"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx1-out.netapp.com with ESMTP; 27 May 2013 03:51:35 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4RApYb5002741; Mon, 27 May 2013 03:51:34 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Mon, 27 May 2013 03:51:34 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
Thread-Topic: Participation per Region of Authoring IETF documents vs Marketing
Thread-Index: AQHOWsKHbBwvdk4+NEOdlrhOvSI/ZJkZUCGA
Date: Mon, 27 May 2013 10:51:34 +0000
Message-ID: <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com>
In-Reply-To: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B330A6BC91250443B631A4FCB541AE9A@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 27 May 2013 10:51:39 -0000

On May 27, 2013, at 12:10, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
> Each IETF document mentions the authors place address (I may suggest
> adding region, as a categorised by IETF), but not sure of history
> statistics of how many IETF-documents produced by authors in South
> America, Africa, or Asia, or others.

http://www.arkko.com/tools/stats/d-countrydistr.html and related pages

Lars=

From abdussalambaryun@gmail.com  Mon May 27 03:54:32 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9DE21F91A0 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G8CbwEs3QXQg for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 03:54:27 -0700 (PDT)
Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADAC21F9234 for <ietf@ietf.org>; Mon, 27 May 2013 03:54:23 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 14so4062207pdc.11 for <ietf@ietf.org>; Mon, 27 May 2013 03:54:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yd1r8004Czi/vbNxHk4ilqqRFnJ1b1q107QPJOIokBM=; b=LsgMSYZdwmxX4KZ/oTMj3QzGllVfHbQs+QrEEy2ScKFjk7fRlbR++dWh4oyE0a0Nj5 o+hvxhDTni4D+VhBsIxOHKrjFJfwVOnYNTya+MsgCogheIm4jTEXzoCL+/+/NwbQ1KaQ LPHOBq9uJzYvdLhRNW0pLZUcSGOeOmxolqzGp6wW7dBhkqqPU9A61wMINIhASwvp75+A njiO8G12s9EI2tnlGUV2DsgXCMXavE+4fByGCeFdKhxhrDfnreMsSy6ATfP8zFboZhux 0bdbc187ED21DSaMJE6pJ9sLSGUO1Pia5JpGnqIGF6oXO/29QArtIJZWFutn62YHpEF/ ENVg==
MIME-Version: 1.0
X-Received: by 10.66.20.3 with SMTP id j3mr29587095pae.142.1369652063373; Mon, 27 May 2013 03:54:23 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 27 May 2013 03:54:23 -0700 (PDT)
In-Reply-To: <20130527055257.7635.qmail@joyce.lan>
References: <20130527055257.7635.qmail@joyce.lan>
Date: Mon, 27 May 2013 12:54:23 +0200
Message-ID: <CADnDZ88mV=mfBC2+=PAO3c025kknHrkiyG67vxgVWG81j-TbFw@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John Levine <johnl@taugh.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: Mon, 27 May 2013 10:54:32 -0000

Hi John,

I agree and I will add, that What makes that participant continue to
volunteer, or even witness/read the ietf work process? Making someone
interested to do something freely is not an easy task. The difficulty
is how to make that individual participate with value, he/she may need
help to notice that *IETF needs* their regional-participation.

Example, I got once a response that IETF or WG chair's jobs are not to
educate others, but who said that IETF is better educated or that WG
chairs are better educated than others. It always depends on the
relativity of education with the region needs, not only eduaction
related to the Internet technology.

I think we *need* in IETF to gain all best educated people of
world-regions into IETF (volunteering), so that we make the Internet
better for the WORLD, because technology SHOULD follow the
community-regional *needs*. Not that we need to gain best
standard/technology experts to make all regions follow the
technology-product requirements, because will may never be *used* that
way :-)

Comments below,

AB

On 5/27/13, John Levine <johnl@taugh.com> wrote:
> I think this is a summary of the issues people have mentioned that
> discourage participation from LDCs, in rough order of importance.
>
> * People aren't aware the IETF exists, or what it does, or that it has
> an open participation model

Also IMHO, the IETF is not aware of existance of Internet
community-regional *needs* for their better Internet technology
future,

>
> * People don't read and write English well enough to be comfortable
> participating

That is not an issue, well educated people around the world know
english reasonably, but the problem is that many of current IETF
participants like to read correct english, hope they change to adapt
to the World's English.
>
> * People are unaccustomed to and perhaps uncomfortable expressing
> overt disagreement

That is true, but mostly Chairs and editors are responsible to make
that continue or stop.
>
> * People don't think they have anything to contribute to an organization
> that is mostly people from rich countries

This point is important, please read my addition above.
>
> * People don't have adequate Internet access for mail, or to use the
> remote participation tools

Yes that is true, but also we need people like old participants, or
98% of participants to get use to participating remotely at IETF
meetings. I don't want to see complains on journey expenses of money
but of spending-time is ok :Z
>
> I have to say that I don't see one or two meetings in South America
> addressing any of these.  Given that the incremental cost to the
> participants, compared to meeting in North America, would likely be on
> the order of a million dollars, it seems to me very likely that there
> are better ways to spend the money.

I don't care how much money spent, we SHOULD focus on how much time
gained by IETF and how much volunteer-time spent for IETF. Attendance
can spend the same time remotely, the World is well connected now,
>
> For example, if language and net access is a problem, it might be
> interesting to set up a remote participation center in B.A. during one
> of the North American meetings (it's one time zone off from Toronto)
> with screens and cameras, paid interpreters, and a few volunteers to
> help explain what's going on.

I think the problem is contribution access to IETF. We need centers to
increase access to documents-produced per regions, centers to increase
participants per region, centers to increase remote users per regions,
etc.

>
> R's,
> John
>
>
>
>
>

From aservin@lacnic.net  Mon May 27 04:52:54 2013
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 63CC921F9003 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 04:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mwmg-+4hzGj2 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 04:52:54 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id C262721F8B60 for <ietf@ietf.org>; Mon, 27 May 2013 04:52:53 -0700 (PDT)
Received: from [IPv6:2800:af:ba30:cc23:21e:52ff:fe76:b63] (unknown [IPv6:2800:af:ba30:cc23:21e:52ff:fe76:b63]) by mail.lacnic.net.uy (Postfix) with ESMTP id 59F6D308453; Mon, 27 May 2013 08:52:30 -0300 (UYT)
Subject: Re: Issues in wider geographic participation
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <20130527055257.7635.qmail@joyce.lan>
Date: Mon, 27 May 2013 08:52:42 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net>
References: <20130527055257.7635.qmail@joyce.lan>
To: "John Levine" <johnl@taugh.com>
X-Mailer: Apple Mail (2.1085)
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, 27 May 2013 11:52:54 -0000

John,

	Good summary.

	I would add a "steep learning-curve" to start participating. It =
takes time to get conformable in participating in mailing list and =
reviewing drafts for I think two reasons. One is to get know how the =
IETF works, and another to catch-up in knowing the topic in relation =
with other WG participants.

	About the remote hub I think it would be good to give it a try.

Regards,
as

On 27 May 2013, at 02:52, John Levine wrote:

> I think this is a summary of the issues people have mentioned that
> discourage participation from LDCs, in rough order of importance.
>=20
> * People aren't aware the IETF exists, or what it does, or that it has
> an open participation model
>=20
> * People don't read and write English well enough to be comfortable
> participating
>=20
> * People are unaccustomed to and perhaps uncomfortable expressing
> overt disagreement
>=20
> * People don't think they have anything to contribute to an =
organization
> that is mostly people from rich countries
>=20
> * People don't have adequate Internet access for mail, or to use the
> remote participation tools
>=20
> I have to say that I don't see one or two meetings in South America
> addressing any of these.  Given that the incremental cost to the
> participants, compared to meeting in North America, would likely be on
> the order of a million dollars, it seems to me very likely that there
> are better ways to spend the money.
>=20
> For example, if language and net access is a problem, it might be
> interesting to set up a remote participation center in B.A. during one
> of the North American meetings (it's one time zone off from Toronto)
> with screens and cameras, paid interpreters, and a few volunteers to
> help explain what's going on.
>=20
> R's,
> John
>=20
>=20
>=20


From dhc@dcrocker.net  Mon May 27 05:08:12 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE8A21F91A0 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.3
X-Spam-Level: 
X-Spam-Status: No, score=-6.3 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qDXCpc0b-g5m for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:08:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0DA9121F8AEA for <ietf@ietf.org>; Mon, 27 May 2013 05:08:07 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4RC7xn0022926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 May 2013 05:08:04 -0700
Message-ID: <51A34C9D.3020406@dcrocker.net>
Date: Mon, 27 May 2013 14:07:57 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net>
In-Reply-To: <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 27 May 2013 05:08:06 -0700 (PDT)
Cc: John Levine <johnl@taugh.com>, 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, 27 May 2013 12:08:12 -0000

On 5/27/2013 1:52 PM, Arturo Servin wrote:
> 	About the remote hub I think it would be good to give it a try.


I'm increasingly intrigued by this idea.  It could be interesting to try 
to formulate a serious proposal for this, with enough detail to qualify 
as a functional specification.  The easy part is specifying audio/video 
streams support.  More challenging is to get the personal and personnel 
support figured out.

And should it have some means of assisting discussions outside of the 
bof/wg/plenary sessions?

What else?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Mon May 27 05:15:12 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEC6F21F8C20 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMYDYU73lhsL for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:15:07 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 77C6821F8C4C for <ietf@ietf.org>; Mon, 27 May 2013 05:15:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C68FF2CC53; Mon, 27 May 2013 15:15:06 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lwsZyzIAHDvq; Mon, 27 May 2013 15:15:06 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 20DD92CC48; Mon, 27 May 2013 15:15:06 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Issues in wider geographic participation
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20130527055257.7635.qmail@joyce.lan>
Date: Mon, 27 May 2013 15:15:06 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1075CB6-E7BE-4C22-8C5D-1112785B4099@piuha.net>
References: <20130527055257.7635.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1503)
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, 27 May 2013 12:15:13 -0000

John,

> * People aren't aware the IETF exists, or what it does, or that it has
> an open participation model
>=20
> * People don't read and write English well enough to be comfortable
> participating
>=20
> * People are unaccustomed to and perhaps uncomfortable expressing
> overt disagreement
>=20
> * People don't think they have anything to contribute to an =
organization
> that is mostly people from rich countries
>=20
> * People don't have adequate Internet access for mail, or to use the
> remote participation tools

Thanks for sending out a list of potential issues.

I think there may be one issue missing from the list. At the end of the =
day, what tends to drive people actual, concrete benefit to themselves =
or their organisations. A drive that is so big that it forces you to =
cross language and other barriers and make at least a time investment in =
participation. As an example, the number of Chinese participants has =
increased rapidly in the IETF. Why? We probably didn't suddenly get much =
better at welcoming new people at the IETF, but the new participants =
felt that work on the Internet is important to them personally, and =
their organisations felt that they need to be part of making Internet =
standards. This isn't very surprising, given, for instance, the rise of =
the Chinese technology industry to a very visible role in the world.

So I feel that the issue in many cases is simpler than the ones in the =
list: "What's in it for me"? This obviously has to do with the role of =
vendors in the IETF and the distribution of tech industry in the world. =
It may also have something to do with doing things that are important. =
I'm sure we could be working on topics that are even better aligned to =
what the world needs=85 if the people who need them were here to tell us =
:-)

The IETF can't change the distribution of industries in the world, but =
we can, for instance, focus on the vendors that are there or work more =
on topics that are interesting for the operational folks. The latter =
would be a good idea for the IETF, anyway.=20

> For example, if language and net access is a problem, it might be
> interesting to set up a remote participation center in B.A. during one
> of the North American meetings (it's one time zone off from Toronto)

We've been looking at setting up something like that (not for BA =
specifically).

Jari


From aservin@lacnic.net  Mon May 27 05:17:56 2013
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 14D9121F8AF7 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyNu2Y1UsXSe for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:17:55 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 71CF721F8A6B for <ietf@ietf.org>; Mon, 27 May 2013 05:17:55 -0700 (PDT)
Received: from [IPv6:2800:af:ba30:cc23:21e:52ff:fe76:b63] (unknown [IPv6:2800:af:ba30:cc23:21e:52ff:fe76:b63]) by mail.lacnic.net.uy (Postfix) with ESMTP id 76F7E308455; Mon, 27 May 2013 09:17:34 -0300 (UYT)
Subject: Re: Issues in wider geographic participation
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Arturo Servin <aservin@lacnic.net>
In-Reply-To: <51A34C9D.3020406@dcrocker.net>
Date: Mon, 27 May 2013 09:17:47 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1085)
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: John Levine <johnl@taugh.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, 27 May 2013 12:17:56 -0000

	Translation?

	Also, it would be important that the "local" people/helpers =
could do an introduction to what it is the ietf, how to send comments in =
the remote participation, to the list, what's a WG etc. It may sound a =
bit bureaucratic, but if we want to have these remote people to start =
sending emails, comments, reviewing draft we need to break the "ice" =
somehow. It does not have to be extensive, a short intro could be =
enough.
=09
	About a serious proposal, are you thinking in an I+D, wg or =
something coming from the IESG, IAOC?

/as

On 27 May 2013, at 09:07, Dave Crocker wrote:

> On 5/27/2013 1:52 PM, Arturo Servin wrote:
>> 	About the remote hub I think it would be good to give it a try.
>=20
>=20
> I'm increasingly intrigued by this idea.  It could be interesting to =
try to formulate a serious proposal for this, with enough detail to =
qualify as a functional specification.  The easy part is specifying =
audio/video streams support.  More challenging is to get the personal =
and personnel support figured out.
>=20
> And should it have some means of assisting discussions outside of the =
bof/wg/plenary sessions?
>=20
> What else?
>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From scott.brim@gmail.com  Mon May 27 05:22:36 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EFB21F944F for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hp-I3VpXDn8m for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:22:35 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 2E22921F913E for <ietf@ietf.org>; Mon, 27 May 2013 05:22:35 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so1616579obb.5 for <ietf@ietf.org>; Mon, 27 May 2013 05:22:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+CRHZCcDylMeE/5ndb6XyxZNrGgdpv38U+gxy0ww67c=; b=NhBTxrjxFcd/55juaZRnb0NA3cybTwr8ht+c3krQiRyqpXCdjGMZAT2Z9wWkMdkux9 Zbvyhjowx5Adk7LWGGPo4rhhjFxSdwL8r4ykioiuUR3oa7rGLjhfQtonWiE9qsAuEKHm muQ8m0S1zQlgQ7tu3Ah6GV0aIT3gxlu73YZSOaEhlqsepDwCFWx8q0/AfZjxXytYr9IU 8F1ZQl9fPBovWbEEcM4vKXg61ArpEI3qhRbdamjsH+VUF0gPa+wjOe+y9TUjqO6Y2fhO XsgcPgdF0v/bXd5ZdoaibYCxCJpa9AUH+JhtBDF0+GCPOQCXjOA+OD2I2B+FjMQ/Ovqr 90gg==
MIME-Version: 1.0
X-Received: by 10.60.144.38 with SMTP id sj6mr16588889oeb.78.1369657354443; Mon, 27 May 2013 05:22:34 -0700 (PDT)
Received: by 10.182.114.193 with HTTP; Mon, 27 May 2013 05:22:34 -0700 (PDT)
Received: by 10.182.114.193 with HTTP; Mon, 27 May 2013 05:22:34 -0700 (PDT)
In-Reply-To: <20130527055257.7635.qmail@joyce.lan>
References: <20130527055257.7635.qmail@joyce.lan>
Date: Mon, 27 May 2013 08:22:34 -0400
Message-ID: <CAPv4CP8dvzpy-79NpZr-XEYCxYwVVAA-t=TgLphmotp3fY_=9w@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
From: Scott Brim <scott.brim@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=e89a8ff2560013616a04ddb234cf
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, 27 May 2013 12:22:36 -0000

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

Add: like many organizations around the world including the USA, they don't
think it's worth the huge effort to develop standards when they can rely on
others to do so well enough for their needs.

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

<p dir="ltr">Add: like many organizations around the world including the USA, they don&#39;t think it&#39;s worth the huge effort to develop standards when they can rely on others to do so well enough for their needs. </p>


--e89a8ff2560013616a04ddb234cf--

From npule@lca.org.ls  Mon May 27 05:33:52 2013
Return-Path: <npule@lca.org.ls>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA4E021F8F7B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0rFM0aKuF39F for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:33:52 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0F80E21F8F7A for <ietf@ietf.org>; Mon, 27 May 2013 05:33:51 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id l18so4305757wgh.25 for <ietf@ietf.org>; Mon, 27 May 2013 05:33:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=Rsq+4LVpNpINejtF+K6auBKaka0vlqPJsvuSUJWS43g=; b=Pf6rXtBqRvGrkD06HRZdxJIrP7Nn152XZ+7UtRFYdud9+Yo4MlR3lnAqd0CrI2YEwQ yxvXeBQxQtydhctp3lyXe/bdwXubsypykvNTRRccyG7z3iT0KPWlUqKtP0hYIN3bkAlm fScDfWqWIEPEdsJH7+1yFNgGJTd1/QMINY6ppJz1zJxDpO4ddT2IcDryiIUQUK6PQrQU bGCwu8HyUBnB8EdZVipHvyC2nVhwXGVXAjRE4PmY6I0kgbk5x48nqbfAWrlYEdKQiGAS QO5GwpD15qzapVKlPXg+dkgiNR9aevKSr+KUYVnDkKTGEFNk/ItnkGxK6v0bHaErLbbG 8dOg==
X-Received: by 10.194.216.105 with SMTP id op9mr4139058wjc.17.1369658030804; Mon, 27 May 2013 05:33:50 -0700 (PDT)
Received: from [10.17.2.218] ([41.203.180.22]) by mx.google.com with ESMTPSA id eq15sm17132435wic.4.2013.05.27.05.33.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 05:33:49 -0700 (PDT)
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls>
X-Mailer: iPad Mail (10B141)
From: Nthabiseng Pule <npule@lca.org.ls>
Subject: Re: Issues in wider geographic participation
Date: Mon, 27 May 2013 14:33:25 +0200
To: Arturo Servin <aservin@lacnic.net>
X-Gm-Message-State: ALoCoQkAEx0cz4cmVJsw7ZxeQLUaEKHIsJaGtBXJXWeAVq/5PvJX2DBJHHlZ2sDC9SUzUH5oABuS
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 12:33:53 -0000

as,

I am new to the IETF.  I would like to contribute any way I can, but the lea=
rning curve seems steep indeed. I am from an LCD country.  I have the necess=
ary resources but I just don't know where to start.

Some guidance would be welcome. I am reading on stuff and hope that one day I=
 will be able to make some meaningful contribution.


Nthabiseng Pule



On 27 May 2013, at 1:52 PM, Arturo Servin <aservin@lacnic.net> wrote:

> John,
>=20
>    Good summary.
>=20
>    I would add a "steep learning-curve" to start participating. It takes t=
ime to get conformable in participating in mailing list and reviewing drafts=
 for I think two reasons. One is to get know how the IETF works, and another=
 to catch-up in knowing the topic in relation with other WG participants.
>=20
>    About the remote hub I think it would be good to give it a try.
>=20
> Regards,
> as
>=20
> On 27 May 2013, at 02:52, John Levine wrote:
>=20
>> I think this is a summary of the issues people have mentioned that
>> discourage participation from LDCs, in rough order of importance.
>>=20
>> * People aren't aware the IETF exists, or what it does, or that it has
>> an open participation model
>>=20
>> * People don't read and write English well enough to be comfortable
>> participating
>>=20
>> * People are unaccustomed to and perhaps uncomfortable expressing
>> overt disagreement
>>=20
>> * People don't think they have anything to contribute to an organization
>> that is mostly people from rich countries
>>=20
>> * People don't have adequate Internet access for mail, or to use the
>> remote participation tools
>>=20
>> I have to say that I don't see one or two meetings in South America
>> addressing any of these.  Given that the incremental cost to the
>> participants, compared to meeting in North America, would likely be on
>> the order of a million dollars, it seems to me very likely that there
>> are better ways to spend the money.
>>=20
>> For example, if language and net access is a problem, it might be
>> interesting to set up a remote participation center in B.A. during one
>> of the North American meetings (it's one time zone off from Toronto)
>> with screens and cameras, paid interpreters, and a few volunteers to
>> help explain what's going on.
>>=20
>> R's,
>> John
>=20

From rumbiles@gmail.com  Mon May 27 05:55:50 2013
Return-Path: <rumbiles@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B41121F8EEA for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:55:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YFKI1eu6eNF for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 05:55:50 -0700 (PDT)
Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id D1D5321F8B45 for <ietf@ietf.org>; Mon, 27 May 2013 05:55:49 -0700 (PDT)
Received: by mail-ie0-f179.google.com with SMTP id c13so17878908ieb.24 for <ietf@ietf.org>; Mon, 27 May 2013 05:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/aLI7OjNw+G/3gYpzq1GRdqRKb5dCOqVXixQt4/w+ow=; b=TDTl6MCkvdkbQ0krGW7rh2AA7MxWQBmfjsiIaXaAbl4yx9o4NyDjFNVZzT3DLcy6OV pogFXJaH6Kcyv24krou8m1dsxvESK7zfbJcdy9p8gxO7CSn9+WWQrfdrAa7u40x5LJmJ p2DbQcuyEKEClGjoLuMUPbdUQKhy4QK77FzPrB7gi1v4swnii+xftsDcTCZ3UV0UExdI AmETwueBYH/jadJZsTV268O6h9Hoqargb3xxxedjFFEbqWkObm3bCi0GXGjDadSdfwYr VYi6TPdZlMute31h953rpMAQZff1jj0FqN20ZafB3ECh7Hzcicl8xnny5rmwK6O1dplT c5uw==
MIME-Version: 1.0
X-Received: by 10.42.64.69 with SMTP id f5mr17296569ici.29.1369659349308; Mon, 27 May 2013 05:55:49 -0700 (PDT)
Received: by 10.50.101.198 with HTTP; Mon, 27 May 2013 05:55:49 -0700 (PDT)
In-Reply-To: <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls>
Date: Mon, 27 May 2013 14:55:49 +0200
Message-ID: <CAOnoajwzBVozSnO4q-OBO+TWTHUSb=7664f7qa5JYFCHsrRMuA@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
From: Rumbidzayi Gadhula <rumbiles@gmail.com>
To: Nthabiseng Pule <npule@lca.org.ls>
Content-Type: multipart/alternative; boundary=90e6ba5bca8ffadd3404ddb2aa4c
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 12:55:50 -0000

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

Ditto.

On 27 May 2013 14:33, Nthabiseng Pule <npule@lca.org.ls> wrote:

> as,
>
> I am new to the IETF.  I would like to contribute any way I can, but the
> learning curve seems steep indeed. I am from an LCD country.  I have the
> necessary resources but I just don't know where to start.
>
> Some guidance would be welcome. I am reading on stuff and hope that one
> day I will be able to make some meaningful contribution.
>
>
> Nthabiseng Pule
>
>
>
> On 27 May 2013, at 1:52 PM, Arturo Servin <aservin@lacnic.net> wrote:
>
> > John,
> >
> >    Good summary.
> >
> >    I would add a "steep learning-curve" to start participating. It takes
> time to get conformable in participating in mailing list and reviewing
> drafts for I think two reasons. One is to get know how the IETF works, and
> another to catch-up in knowing the topic in relation with other WG
> participants.
> >
> >    About the remote hub I think it would be good to give it a try.
> >
> > Regards,
> > as
> >
> > On 27 May 2013, at 02:52, John Levine wrote:
> >
> >> I think this is a summary of the issues people have mentioned that
> >> discourage participation from LDCs, in rough order of importance.
> >>
> >> * People aren't aware the IETF exists, or what it does, or that it has
> >> an open participation model
> >>
> >> * People don't read and write English well enough to be comfortable
> >> participating
> >>
> >> * People are unaccustomed to and perhaps uncomfortable expressing
> >> overt disagreement
> >>
> >> * People don't think they have anything to contribute to an organization
> >> that is mostly people from rich countries
> >>
> >> * People don't have adequate Internet access for mail, or to use the
> >> remote participation tools
> >>
> >> I have to say that I don't see one or two meetings in South America
> >> addressing any of these.  Given that the incremental cost to the
> >> participants, compared to meeting in North America, would likely be on
> >> the order of a million dollars, it seems to me very likely that there
> >> are better ways to spend the money.
> >>
> >> For example, if language and net access is a problem, it might be
> >> interesting to set up a remote participation center in B.A. during one
> >> of the North American meetings (it's one time zone off from Toronto)
> >> with screens and cameras, paid interpreters, and a few volunteers to
> >> help explain what's going on.
> >>
> >> R's,
> >> John
> >
>

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

Ditto.<br><br><div class=3D"gmail_quote">On 27 May 2013 14:33, Nthabiseng P=
ule <span dir=3D"ltr">&lt;<a href=3D"mailto:npule@lca.org.ls" target=3D"_bl=
ank">npule@lca.org.ls</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
as,<br>
<br>
I am new to the IETF. =A0I would like to contribute any way I can, but the =
learning curve seems steep indeed. I am from an LCD country. =A0I have the =
necessary resources but I just don&#39;t know where to start.<br>
<br>
Some guidance would be welcome. I am reading on stuff and hope that one day=
 I will be able to make some meaningful contribution.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Nthabiseng Pule<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On 27 May 2013, at 1:52 PM, Arturo Servin &lt;<a href=3D"mailto:aservin@lac=
nic.net">aservin@lacnic.net</a>&gt; wrote:<br>
<br>
&gt; John,<br>
&gt;<br>
&gt; =A0 =A0Good summary.<br>
&gt;<br>
&gt; =A0 =A0I would add a &quot;steep learning-curve&quot; to start partici=
pating. It takes time to get conformable in participating in mailing list a=
nd reviewing drafts for I think two reasons. One is to get know how the IET=
F works, and another to catch-up in knowing the topic in relation with othe=
r WG participants.<br>

&gt;<br>
&gt; =A0 =A0About the remote hub I think it would be good to give it a try.=
<br>
&gt;<br>
&gt; Regards,<br>
&gt; as<br>
&gt;<br>
&gt; On 27 May 2013, at 02:52, John Levine wrote:<br>
&gt;<br>
&gt;&gt; I think this is a summary of the issues people have mentioned that=
<br>
&gt;&gt; discourage participation from LDCs, in rough order of importance.<=
br>
&gt;&gt;<br>
&gt;&gt; * People aren&#39;t aware the IETF exists, or what it does, or tha=
t it has<br>
&gt;&gt; an open participation model<br>
&gt;&gt;<br>
&gt;&gt; * People don&#39;t read and write English well enough to be comfor=
table<br>
&gt;&gt; participating<br>
&gt;&gt;<br>
&gt;&gt; * People are unaccustomed to and perhaps uncomfortable expressing<=
br>
&gt;&gt; overt disagreement<br>
&gt;&gt;<br>
&gt;&gt; * People don&#39;t think they have anything to contribute to an or=
ganization<br>
&gt;&gt; that is mostly people from rich countries<br>
&gt;&gt;<br>
&gt;&gt; * People don&#39;t have adequate Internet access for mail, or to u=
se the<br>
&gt;&gt; remote participation tools<br>
&gt;&gt;<br>
&gt;&gt; I have to say that I don&#39;t see one or two meetings in South Am=
erica<br>
&gt;&gt; addressing any of these. =A0Given that the incremental cost to the=
<br>
&gt;&gt; participants, compared to meeting in North America, would likely b=
e on<br>
&gt;&gt; the order of a million dollars, it seems to me very likely that th=
ere<br>
&gt;&gt; are better ways to spend the money.<br>
&gt;&gt;<br>
&gt;&gt; For example, if language and net access is a problem, it might be<=
br>
&gt;&gt; interesting to set up a remote participation center in B.A. during=
 one<br>
&gt;&gt; of the North American meetings (it&#39;s one time zone off from To=
ronto)<br>
&gt;&gt; with screens and cameras, paid interpreters, and a few volunteers =
to<br>
&gt;&gt; help explain what&#39;s going on.<br>
&gt;&gt;<br>
&gt;&gt; R&#39;s,<br>
&gt;&gt; John<br>
&gt;<br>
</div></div></blockquote></div><br>

--90e6ba5bca8ffadd3404ddb2aa4c--

From abdussalambaryun@gmail.com  Mon May 27 06:31:21 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E46B821F960F for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 06:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5hCJyF1-WEWP for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 06:31:20 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 125D821F9601 for <ietf@ietf.org>; Mon, 27 May 2013 06:31:19 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so6775440pbb.38 for <ietf@ietf.org>; Mon, 27 May 2013 06:31:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WM9Kpwvne/bgY1unqaZYXGszTMNlwpLLX1nOfMS/TLY=; b=TWqQovbKWl/zUSJcZGqIEvwJ5ZoGxXkzarspyEPO8+05qvRep2FlCb02MJjbsMdOd+ /i0Lxw9GU1DQekypViYFEkU9R5MBXQse7DYwog1wUrG06SyKM084w9DBHL48W9M1Ck0x jlxmDffGnf3fmrgRac5p36JGZgFyVYH9ikYzW03hN3mhhsp6s12ojQ0Vwrt8LdL3foMP FMURtKiZFg5WQUncKj+S6yjG+pqzD+ElITaKc26FqXh7Fza+ESwttoSRhD0eLrzshvbu ZlX32+yOpCiRjmKzEyTDMMVWMHZjNz4DWiiQBtbCrzkFNC0Fz9L+8QmNBYfEaUxII0gU WBHQ==
MIME-Version: 1.0
X-Received: by 10.66.122.8 with SMTP id lo8mr29184801pab.165.1369661479726; Mon, 27 May 2013 06:31:19 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 27 May 2013 06:31:19 -0700 (PDT)
In-Reply-To: <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com>
Date: Mon, 27 May 2013 15:31:19 +0200
Message-ID: <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 13:31:21 -0000

On 5/27/13, Eggert, Lars <lars@netapp.com> wrote:
> On May 27, 2013, at 12:10, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
>> Each IETF document mentions the authors place address (I may suggest
>> adding region, as a categorised by IETF), but not sure of history
>> statistics of how many IETF-documents produced by authors in South
>> America, Africa, or Asia, or others.
>
> http://www.arkko.com/tools/stats/d-countrydistr.html and related pages

I read that before, but does not show documents/RFCs per region. It
shows drafts per countries. For example, does not show the drafts from
South America. Does not show all regions in sequence of the most
participated region.

AB

From ynir@checkpoint.com  Mon May 27 07:13:29 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E24A21F8FCB for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 07:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lkGfMabx3EKn for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 07:13:24 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C83ED21F8F44 for <ietf@ietf.org>; Mon, 27 May 2013 07:13:23 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4REDEAk018751; Mon, 27 May 2013 17:13:14 +0300
X-CheckPoint: {51A3676B-27-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Mon, 27 May 2013 17:13:14 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Nthabiseng Pule <npule@lca.org.ls>
Subject: Re: Issues in wider geographic participation
Thread-Topic: Issues in wider geographic participation
Thread-Index: AQHOWp6MSRYfNsyh+USypHvVtoKe/ZkYudsAgAALYICAABvjgA==
Date: Mon, 27 May 2013 14:13:13 +0000
Message-ID: <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls>
In-Reply-To: <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <32E18F8DDD323443A50C102A57B09D0E@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 14:13:29 -0000

LCD?

Anyway, What I found most useful when I was starting out 9 years ago, was t=
o look over the list of areas and working groups ( http://tools.ietf.org/ar=
ea/ ) and find out which of them are working on something that is of intere=
st to me. In my case it was mostly the security area, and the IPsec working=
 group, since that is what I was working on in my day job. I subscribed to =
that list and some others that were also related to what I was working on (=
TLS, PKIX).

So the best thing is to subscribe to the mailing lists, both those that int=
erest you personally and those that are of interest to your employer (if th=
ere are such groups).=20

Step 2 is to lurk for a couple of weeks at least, and just read what others=
 are posting. If they're talking about a particular draft, it's easy to fin=
d on one of the IETF sites and read it. So you read the drafts, and read wh=
at people are saying about the drafts. This teaches you both about what the=
 group is working on, and the (for lack of a better term) "political" part =
- who are the participants and what are they like.  You might also want to =
read the Tao document, although different groups have varying dynamics.=20

After a while, you've read the drafts, you've read what some people are say=
ing, and you may have formed an opinion, either about the draft itself, or =
about one of the comments. That's a good time to speak up by sending a mess=
age to the list. Maybe the draft got something wrong. Maybe the comment is =
only correct in certain contexts, but doesn't describe some situation you'r=
e familiar with. Maybe in reading the draft you find it hard to figure out =
what an implementation should do in a certain case, and you present the cas=
e, and ask that it be clarified. Maybe the proposed protocol would require =
clients, servers, or middleboxes to allocate more memory than implementatio=
ns that you know can afford. Such comments, and even better, proposed fixes=
 are how you build a reputation in the IETF for knowing your stuff. You can=
 also volunteer to review a whole document, or volunteer to write a missing=
 section. That is how you build a reputation for being useful. Both are nec=
essary for success in the IETF.

Step 4 is when you have an idea of your own, or you read someone else's ide=
a and you want to participate. In that case you either write your own draft=
 or join someone else in writing one. It's often not enough to just write i=
t. You also have to get people to read it, post about it to the correct lis=
ts, and in general "sell" it and gather support. It is at about that time t=
hat you start to feel the need to attend meetings, but you can get some thi=
ngs done even without it.

Hope this helps

Yoav

On May 27, 2013, at 3:33 PM, Nthabiseng Pule <npule@lca.org.ls>
 wrote:

> as,
>=20
> I am new to the IETF.  I would like to contribute any way I can, but the =
learning curve seems steep indeed. I am from an LCD country.  I have the ne=
cessary resources but I just don't know where to start.
>=20
> Some guidance would be welcome. I am reading on stuff and hope that one d=
ay I will be able to make some meaningful contribution.
>=20
>=20
> Nthabiseng Pule
>=20
>=20
>=20
> On 27 May 2013, at 1:52 PM, Arturo Servin <aservin@lacnic.net> wrote:
>=20
>> John,
>>=20
>>   Good summary.
>>=20
>>   I would add a "steep learning-curve" to start participating. It takes =
time to get conformable in participating in mailing list and reviewing draf=
ts for I think two reasons. One is to get know how the IETF works, and anot=
her to catch-up in knowing the topic in relation with other WG participants=
.
>>=20
>>   About the remote hub I think it would be good to give it a try.
>>=20
>> Regards,
>> as
>>=20
>> On 27 May 2013, at 02:52, John Levine wrote:
>>=20
>>> I think this is a summary of the issues people have mentioned that
>>> discourage participation from LDCs, in rough order of importance.
>>>=20
>>> * People aren't aware the IETF exists, or what it does, or that it has
>>> an open participation model
>>>=20
>>> * People don't read and write English well enough to be comfortable
>>> participating
>>>=20
>>> * People are unaccustomed to and perhaps uncomfortable expressing
>>> overt disagreement
>>>=20
>>> * People don't think they have anything to contribute to an organizatio=
n
>>> that is mostly people from rich countries
>>>=20
>>> * People don't have adequate Internet access for mail, or to use the
>>> remote participation tools
>>>=20
>>> I have to say that I don't see one or two meetings in South America
>>> addressing any of these.  Given that the incremental cost to the
>>> participants, compared to meeting in North America, would likely be on
>>> the order of a million dollars, it seems to me very likely that there
>>> are better ways to spend the money.
>>>=20
>>> For example, if language and net access is a problem, it might be
>>> interesting to set up a remote participation center in B.A. during one
>>> of the North American meetings (it's one time zone off from Toronto)
>>> with screens and cameras, paid interpreters, and a few volunteers to
>>> help explain what's going on.
>>>=20
>>> R's,
>>> John
>>=20


From abdussalambaryun@gmail.com  Mon May 27 07:14:14 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2BB621F9616; Mon, 27 May 2013 07:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trHQ8OXWEqPc; Mon, 27 May 2013 07:14:14 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3A41321F93EB; Mon, 27 May 2013 07:14:14 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id un4so6775392pbc.40 for <multiple recipients>; Mon, 27 May 2013 07:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jwrVFgg4okOndHEm4VVkN1+9xMhcHxNHnnhHc9Ho2Y8=; b=Yus+Lo5dDwRak+d9nNVoYkk3/y9tVSA1O4b4GVAX3+G+Iz++UM2G+ScEF8yohDmJ6F 7dZFtoEaPL6m/M2ouecoeSjpZz+mEowYa1uWJYfcg8eAnI2lqNx9KSN9HdsmSeEcBn9m uMYIlTzV17/ibkFpMnPLerbA2vfTFLseBv6WMya4l6pJ8zzJQtMFtCJyZMq1xGZt+HlN L+8Y1XVaWFkyq8Wneo868Ta0K9nIWRqma7Nc5Xrw1kBxB3qnB/BiTGcukt5Jk1kVtAsS u3cG4v7GtUOlyAPV646if6T4sQt8cmNaab1O7Rfn8DDX1Kel+0+qA+hUhSNzl024rxf9 F6ew==
MIME-Version: 1.0
X-Received: by 10.68.12.98 with SMTP id x2mr29899785pbb.92.1369664053992; Mon, 27 May 2013 07:14:13 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 27 May 2013 07:14:13 -0700 (PDT)
In-Reply-To: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com>
Date: Mon, 27 May 2013 16:14:13 +0200
Message-ID: <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 14:14:14 -0000

Reply to your request dated 24/05/2013

Draft Reviewed By: Abdussalam Baryun (AB)    Dated:27/05/2013
Reviewer Comment A1: Previous comments in WGLC
+++++++++++++++++++++++++++++++++++++++

Related to your request below please read my previous review comments
[1] and I will continue with additional messages/comments.

[1] http://www.ietf.org/mail-archive/web/manet/current/msg15254.html

Regards
AB

On 5/24/13, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Mobile Ad-hoc Networks WG
> (manet) to consider the following document:
> - 'Security Threats for NHDP'
>   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-06. 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 analyses common security threats of the Neighborhood
>    Discovery Protocol (NHDP), and describes their potential impacts on
>    MANET routing protocols using NHDP.
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

From dhc@dcrocker.net  Mon May 27 07:24:06 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D62021F92EB for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 07:24:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QZFlTd-2rkMk for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 07:23:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3AC21F8E93 for <ietf@ietf.org>; Mon, 27 May 2013 07:23:46 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4RENWIS024637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 May 2013 07:23:37 -0700
Message-ID: <51A36C61.5030900@dcrocker.net>
Date: Mon, 27 May 2013 16:23:29 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls> <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
In-Reply-To: <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 27 May 2013 07:23:38 -0700 (PDT)
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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, 27 May 2013 14:24:07 -0000

On 5/27/2013 4:13 PM, Yoav Nir wrote:
> Anyway, What I found most useful when I was starting out 9 years ago,


One might wish for a document that gives such guidance to folk who are 
new to the IETF.

And indeed...

      The Tao of IETF: A Novice's Guide to the Internet Engineering
      Task Force

      http://www.ietf.org/tao.html

If the content needs to be improved, let's do it!

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From sm@resistor.net  Mon May 27 07:26:34 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB62721F91A0 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 07:26:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ClwCfoIJABLR for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 07:26:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0171421F901A for <ietf@ietf.org>; Mon, 27 May 2013 07:26:33 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4REQQEL022478; Mon, 27 May 2013 07:26:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369664791; bh=627UIFhWnsASHiubi1+Y6oobsROs8r/pzVRH61ftRio=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BJA42A8KANclsArk9uy7zivaT0cAAz2OTecTcVhaFKCkBzZAT+PXxOfaFUnEzyPAH Da0382aB5qplOXcxZtNXRDuj4VDQHRcUMr2R1vTsTjclwu55jFk4w9WoTvJ1SEDnAE +gWzF6iH1/R7WfOiU5nDG6nxz2SXmxn9vv7E3BqM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369664791; i=@resistor.net; bh=627UIFhWnsASHiubi1+Y6oobsROs8r/pzVRH61ftRio=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TT8FoGZUCCjVZx3ztzNjzS337tcNsCDRg7/L/j+evdqjqVHjtndjCu7NOGedtnkwB ltEnseGiHAoi3UdprHvpQtacaARQZ9qWPi4yRVTx689cuTaV1LryuNHzBPCSwKlIYm QVQl1Fuxi7DY7D+YdAWH7GWnEjJtosESSDQFza0k=
Message-Id: <6.2.5.6.2.20130527063900.06d1a498@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 27 May 2013 07:15:17 -0700
To: Arturo Servin <aservin@lacnic.net>
From: SM <sm@resistor.net>
Subject: Re: Issues in wider geographic participation
In-Reply-To: <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.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, 27 May 2013 14:26:34 -0000

Hola Arturo,
At 05:17 27-05-2013, Arturo Servin wrote:
>         Also, it would be important that the "local" people/helpers 
> could do an introduction to what it is the ietf, how to send 
> comments in the remote participation, to the list, what's a WG etc. 
> It may sound a bit bureaucratic, but if we want to have these 
> remote people to start sending emails, comments, reviewing draft we 
> need to break the "ice" somehow. It does not have to be extensive, 
> a short intro could be enough.

I like what you said about breaking the ice.  As mentioned above, 
having local people would help.  There is a Newcomers tutorial which 
explains what is a working group, what is the IETF, etc.

Joel Jaeggli mentioned that a regional NOG is not fertile ground for 
new IETF participants.  Is LACNOG fertile ground for new IETF participants?

The "sending email, comments, reviewing draft" is the really 
difficult part.  My uneducated guess is that it would takes months of 
work.  It's not as negative as it sounds if you consider that 
overcoming the barrier of entry might usually take over a year.

Could you ask the people who attended the talk ( 
http://www.youtube.com/watch?v=L_zacX9DcZA ) to provide some feedback 
about it to edu-discuss mailing list?

Regards,
-sm 


From michal@krsek.cz  Mon May 27 08:15:05 2013
Return-Path: <michal@krsek.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B10921F968E for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:15:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.239
X-Spam-Level: 
X-Spam-Status: No, score=0.239 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_CZ=0.445, HOST_EQ_CZ=0.904]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cNbHOSClxdH0 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:14:59 -0700 (PDT)
Received: from io.pinknet.cz (io.pinknet.cz [217.31.57.96]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9A421F96B5 for <ietf@ietf.org>; Mon, 27 May 2013 08:14:57 -0700 (PDT)
Received: from [195.113.228.228] (unknown [195.113.228.228]) by io.pinknet.cz (Postfix) with ESMTP id 8C4C223B051 for <ietf@ietf.org>; Mon, 27 May 2013 17:27:29 +0200 (CEST)
Message-ID: <51A3786F.9090103@krsek.cz>
Date: Mon, 27 May 2013 17:14:55 +0200
From: Michal Krsek <michal@krsek.cz>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net>
In-Reply-To: <51A34C9D.3020406@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 15:15:05 -0000

Hi,

>>     About the remote hub I think it would be good to give it a try.
>
>
> I'm increasingly intrigued by this idea.  It could be interesting to 
> try to formulate a serious proposal for this, with enough detail to 
> qualify as a functional specification.  The easy part is specifying 
> audio/video streams support.  More challenging is to get the personal 
> and personnel support figured out.

I think most of research/university networks are facing same challenge. 
Remote class setup is exactly what we need (with support of back a/v 
channel). Not a rocket science, but can be expensive in case of support 
in number of parallel tracks.

There is also a question if IETF wants to cover only room-to-room setup 
or want to cover room-to-desktop scenario.

>
> And should it have some means of assisting discussions outside of the 
> bof/wg/plenary sessions?

Having a mechanism for "voting" has also some value.

my $0.02

             Regards
                 Michal

From ynir@checkpoint.com  Mon May 27 08:15:08 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84E8221F96C3 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:15:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id td5UhpO99fBp for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:15:03 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0545021F9695 for <ietf@ietf.org>; Mon, 27 May 2013 08:15:02 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4RFEt6k000618; Mon, 27 May 2013 18:14:56 +0300
X-CheckPoint: {51A375E0-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Mon, 27 May 2013 18:14:56 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: Issues in wider geographic participation
Thread-Topic: Issues in wider geographic participation
Thread-Index: AQHOWp6MSRYfNsyh+USypHvVtoKe/ZkYudsAgAALYICAABvjgIAAAt6AgAAOXIA=
Date: Mon, 27 May 2013 15:14:54 +0000
Message-ID: <ABEB2A06-39D1-4378-BE5E-CF3195485EF0@checkpoint.com>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls> <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com> <51A36C61.5030900@dcrocker.net>
In-Reply-To: <51A36C61.5030900@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <22EAFBEE2D9F0E45AAA13785527AF221@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 15:15:08 -0000

On May 27, 2013, at 5:23 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 5/27/2013 4:13 PM, Yoav Nir wrote:
>> Anyway, What I found most useful when I was starting out 9 years ago,
>=20
>=20
> One might wish for a document that gives such guidance to folk who are ne=
w to the IETF.
>=20
> And indeed...
>=20
>     The Tao of IETF: A Novice's Guide to the Internet Engineering
>     Task Force
>=20
>     http://www.ietf.org/tao.html
>=20
> If the content needs to be improved, let's do it!

Yes, and for extra credit you can read RFC 4144.

I find it hard to improve on the Tao, but I think that its target audience =
are people who are ready to plunge - review documents, attend meetings, wri=
te drafts. It took me over a year of mostly lurking and little discussion t=
o get there. Others may be quicker.=20

I've also found that it's hard to make generalizations about working groups=
 and their associated mailing lists. Some are low-traffic, some have 50 mes=
sages a day. Some discuss protocols in abstract terms, while others take th=
e "running code" part seriously. Some have dominant chairs that moderate th=
e discussion such that all threads become dialogs with the chairs, while in=
 others the chairs move out of the way to let the discussion flow. Some hav=
e dominant experts and everyone waits for their (final?) word on the subjec=
t, while at others not only everyone may speak, but almost everyone is list=
ened to.

Regardless of what we would like groups to be like, I think it's important =
- particularly for a newcomer - to lurk for a while and get a "feel" for th=
e working group. Otherwise you get into arguments with the local crank that=
 everyone else knows to ignore (I've done this lots and lots of times).

Another think I've learned is that you don't necessarily end up being invol=
ved in the things you came into the IETF for. I came to the IETF to follow =
things that were important to my part of the company: IPsec, TLS, PKIX. I e=
nded up contributing in MSec, and finally chairing the WebSec group, which =
is really far away from my day job. Interestingly, a lot of the same people=
 show up in different working groups, so it works very well to do work in o=
ne group, while still following the groups that you came in for. IOW my abi=
lity to follow the groups that are related to my day job is enhanced by bei=
ng active in other working groups. That was kind of surprising to me at fir=
st.

So like the Tao says, take the plunge. The more you're involved in somethin=
g, the more you can do in other things. Much of being effective in the IETF=
 is about knowing people and making yourself useful to them.

Yoav


From johnl@taugh.com  Mon May 27 08:37:02 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 805A621F9675 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAewx8mVu2Z1 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:37:02 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2B921F9671 for <ietf@ietf.org>; Mon, 27 May 2013 08:37:01 -0700 (PDT)
Received: (qmail 51796 invoked from network); 27 May 2013 15:37:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=ca52.51a37da0.k1305; bh=LdTDn6qD3nQX9lDcvYxqnCn/eA07cvJZGCB/F9KSup0=; b=oA3L+SXcnpZHWJHMRrm0UYKWvYWqv/t70vpzjrTtNZQ40INnJPRLysbRt8ZeETdbDlQMlxd6DHecpP+BgZYto2vzhe8F4Y5j8UGcvJ5gsnwZnmAT0DKX/GoTIpg+UEbLz1DXlZN3MXNtABWHBniJ/DuSL91cD54ZW8aHjuJUaOM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=ca52.51a37da0.k1305; bh=LdTDn6qD3nQX9lDcvYxqnCn/eA07cvJZGCB/F9KSup0=; b=sCdQMnvYSkZdkJVofHgPv2E70+KpaTz7Br6TzUcDLTnj4kUWsiD+jK3P/deHUzEoXyIiRGCUbx+qy/xkERxTdRLDa2nU2nEMNJPBJHLnCs9k3TcAgdjYVqZ/7joNpRE91LtdT6TYz3mZTwg6/YbFs1ddtJRi+m1MxlE98tIUCXk=
Received: (ofmipd 127.0.0.1); 27 May 2013 15:36:42 -0000
Date: 27 May 2013 11:37:00 -0400
Message-ID: <alpine.BSF.2.00.1305271133490.7155@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Tim Chown" <tjc@ecs.soton.ac.uk>
Subject: Re: financial fun with an IETF Meeting in South America
In-Reply-To: <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk>
References: <20130527041505.7301.qmail@joyce.lan> <A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk> <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 15:37:02 -0000

> Is this above advice from Tripadvisor correct?

I believe so, but when I was there a few years ago for the ICANN meeting, 
excess cash was not a problem.  It wasn't hard to estimate how much cash 
I'd need, and whatever was left I spent at the airport.  The wine they 
drink in Argentina is often better than the stuff they send to the UK 
(which isn't bad) and much cheaper.  Take some home in your suitcase, even 
if you have to pay duty it's a bargain.

This still doesn't mean I think a meeting in South America is a good idea, 
though.  See other messages.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From joelja@bogus.com  Mon May 27 08:41:02 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28A6621F9675 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:41:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2697YNpJUQL for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:41:01 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 078C821F9671 for <ietf@ietf.org>; Mon, 27 May 2013 08:41:00 -0700 (PDT)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4RFewrk090163 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 27 May 2013 15:40:58 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A37E8A.9010506@bogus.com>
Date: Mon, 27 May 2013 08:40:58 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>
In-Reply-To: <20130520134442.30045.33596.idtracker@ietfa.amsl.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, 27 May 2013 15:40:58 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 15:41:02 -0000

On 5/20/13 6:44 AM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Resource Records for EUI-48 and EUI-64 Addresses in the DNS'
>    <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> as Proposed Standard

I would direct the attention of the commentors to draft 04

http://www.ietf.org/internet-drafts/draft-jabley-dnsext-eui48-eui64-rrtypes-04.txt

Which addresses concerns expressed in IETF last call over the intended 
status.

It also incorporates edits proposed by John Klensin in his review.

Notes: from the author:

  - changed intended status to informational

  - incorporation of John's suggestions in the Terminology section, to indicate that we're using 2119 keywords even though this is not a standards track document

  - added a couple of sentences to the security considerations sections to underscore the fact that this document specifies optional mechanisms that people might well not use if privacy considerations dictate otherwise

>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-06-17. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     48-bit Extended Unique Identifiers (EUI-48) and 64-bit Extended
>     Unique Identifiers (EUI-64) are address formats specified by the IEEE
>     for use in various layer-2 networks, e.g. ethernet.
>
>     This document defines two new DNS resource record types, EUI48 and
>     EUI64, for encoding ethernet addresses in the DNS.
>


>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-jabley-dnsext-eui48-eui64-rrtypes/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


From jmamodio@gmail.com  Mon May 27 08:42:04 2013
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 291FD21F9675 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:42:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.692
X-Spam-Level: 
X-Spam-Status: No, score=-0.692 tagged_above=-999 required=5 tests=[AWL=1.511,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5c1gpzkLFXYX for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:41:59 -0700 (PDT)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id 297D121F968E for <ietf@ietf.org>; Mon, 27 May 2013 08:41:59 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i10so8951170oag.1 for <ietf@ietf.org>; Mon, 27 May 2013 08:41:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=Jw1XWnm/Qlp7HaIqH9vEl70oBD5i7CMcnUsoBOyvb8s=; b=j6WosDqW00nUEbGCq0AsfwLDsfeFgI0LM3wEYjES9EAm/udkeHdmnSKLeYucfGth1T ciwwxO13ynBWsEUnPduNnab7M5Du8RTl9wfN/bkEtll0U0XUdJqpJTBB0UavtC9J7qOy /uF5Ubzz0x0vGZKomoplLjl4Vk9Z+iMVHzGtQ5BKqjoo7dlcx76SJycRLzklwz63edmG yuTGy+n3zg4m//vI80ldITFQv9LSdEkWpvpMr8Qh108+bTVgnBFGoMZ+LYFhEpcV+VxW oOtRyWPBzuwsFAqESbI0A2nA6E0/ZcTawgbEZDGwNiCDxOIc3l4uml2crKNNG34D941Z DmiQ==
X-Received: by 10.60.146.227 with SMTP id tf3mr18810444oeb.50.1369669318710; Mon, 27 May 2013 08:41:58 -0700 (PDT)
Received: from [10.0.10.101] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id h4sm31298891oel.2.2013.05.27.08.41.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 08:41:58 -0700 (PDT)
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE47309F-C7C1-4E82-9A14-68B2A2B7EBBB@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Issues in wider geographic participation
Date: Mon, 27 May 2013 10:41:56 -0500
To: Arturo Servin <aservin@lacnic.net>
Cc: John Levine <johnl@taugh.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 15:42:04 -0000

Translation ?? This a very old discussion and moot point, people that have i=
nterest to participate in this type of international forums and processes SH=
OULD learn English.

-Jorge

On May 27, 2013, at 7:17 AM, Arturo Servin <aservin@lacnic.net> wrote:

>=20
>    Translation?
>=20
>    Also, it would be important that the "local" people/helpers could do an=
 introduction to what it is the ietf, how to send comments in the remote par=
ticipation, to the list, what's a WG etc. It may sound a bit bureaucratic, b=
ut if we want to have these remote people to start sending emails, comments,=
 reviewing draft we need to break the "ice" somehow. It does not have to be e=
xtensive, a short intro could be enough.
>   =20
>    About a serious proposal, are you thinking in an I+D, wg or something c=
oming from the IESG, IAOC?
>=20
> /as
>=20
> On 27 May 2013, at 09:07, Dave Crocker wrote:
>=20
>> On 5/27/2013 1:52 PM, Arturo Servin wrote:
>>>    About the remote hub I think it would be good to give it a try.
>>=20
>>=20
>> I'm increasingly intrigued by this idea.  It could be interesting to try t=
o formulate a serious proposal for this, with enough detail to qualify as a f=
unctional specification.  The easy part is specifying audio/video streams su=
pport.  More challenging is to get the personal and personnel support figure=
d out.
>>=20
>> And should it have some means of assisting discussions outside of the bof=
/wg/plenary sessions?
>>=20
>> What else?
>>=20
>> d/
>>=20
>> --=20
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net
>=20

From lars@netapp.com  Mon May 27 08:46:40 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C1821F920B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.186
X-Spam-Level: 
X-Spam-Status: No, score=-10.186 tagged_above=-999 required=5 tests=[AWL=0.413, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I98XZanu+ajL for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:46:36 -0700 (PDT)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 0639621F8F87 for <ietf@ietf.org>; Mon, 27 May 2013 08:46:36 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,751,1363158000"; d="scan'208";a="58415803"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 27 May 2013 08:46:35 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4RFkZ1w021270; Mon, 27 May 2013 08:46:35 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.03.0123.003; Mon, 27 May 2013 08:46:35 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
Thread-Topic: Participation per Region of Authoring IETF documents vs Marketing
Thread-Index: AQHOWsKHbBwvdk4+NEOdlrhOvSI/ZJkZUCGAgAAso4CAACXKAA==
Date: Mon, 27 May 2013 15:46:35 +0000
Message-ID: <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com>
In-Reply-To: <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C869A53A7C541C41ACC3EEA130C64408@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 27 May 2013 15:46:40 -0000

On May 27, 2013, at 15:31, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
> On 5/27/13, Eggert, Lars <lars@netapp.com> wrote:
>> On May 27, 2013, at 12:10, Abdussalam Baryun <abdussalambaryun@gmail.com=
>
>> wrote:
>>> Each IETF document mentions the authors place address (I may suggest
>>> adding region, as a categorised by IETF), but not sure of history
>>> statistics of how many IETF-documents produced by authors in South
>>> America, Africa, or Asia, or others.
>>=20
>> http://www.arkko.com/tools/stats/d-countrydistr.html and related pages
>=20
> I read that before, but does not show documents/RFCs per region. It
> shows drafts per countries. For example, does not show the drafts from
> South America. Does not show all regions in sequence of the most
> participated region.

That's why I wrote *and related pages*.

Clicking around Jari's pages, you will easily find http://www.arkko.com/too=
ls/rfcstats/d-contdistr.html as well as many more stats.

As for "most participated region", look at the reports from the IAOC: http:=
//iaoc.ietf.org/reports.html

Lars=

From johnl@taugh.com  Mon May 27 08:48:26 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E036D21F96B8 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pY0dFD6FI64m for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:48:25 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CABBF21F96B7 for <ietf@ietf.org>; Mon, 27 May 2013 08:48:24 -0700 (PDT)
Received: (qmail 54032 invoked from network); 27 May 2013 15:48:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d30e.51a3804c.k1305; bh=pslFJYKhjRd2Y0RXwz+MtEJaRxA4umCvVAEjbsJjPB0=; b=UWyCIzZwl4gAg0saxSOdOb4Wrh8VatPnk+aros2jxuAQsQC8AV/wmCxPQwbg6fxu7ESLVFTzvrotPBo3JyIgryXNA8JRP9iTTeafhH81PdqaRVf4CvO1r36K7LmV4ztOShRvNnErH4ytyiZL6Iy6NU7sVWd25D173wN+LOTB9k0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d30e.51a3804c.k1305; bh=pslFJYKhjRd2Y0RXwz+MtEJaRxA4umCvVAEjbsJjPB0=; b=EBpM9By/XAEyZeEkSNGqxQlVzf6mlOMbzxmBFwsM1OkoIkRNB3k3PKI1pm9hAkqkQxJtmVu8bBsxKezO8kH9hd5hl/g+ABEc9+QG4h58z3vpeaqms9gcxM0lzWWlnQ4nAqazv4pBhvewItN+QaJcrOgDqLseaHYeLxjtW1pFMyw=
Received: (ofmipd 127.0.0.1); 27 May 2013 15:48:06 -0000
Date: 27 May 2013 11:48:24 -0400
Message-ID: <alpine.BSF.2.00.1305271147270.7155@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Yoav Nir" <ynir@checkpoint.com>
Subject: Re: Issues in wider geographic participation
In-Reply-To: <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls> <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1220248199-1369669704=:7155"
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, 27 May 2013 15:48:26 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1220248199-1369669704=:7155
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Mon, 27 May 2013, Yoav Nir wrote:

> LCD?

LDC, Less Developed Country, what used to be called the third world, now 
that the second has been bought by the first.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
--3825401791-1220248199-1369669704=:7155
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJCQYJKoZIhvcNAQcCoIII+jCCCPYCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBjowggY2MIIFHqADAgECAgMGLywwDQYJKoZIhvcNAQEFBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMzAzMTYxOTQ0MDdaFw0xNDAzMTgxMjI4MzVaMFUxGTAX
BgNVBA0TEHFaMXRuOTBuMkdVODZzemYxGDAWBgNVBAMMD2pvaG5sQHRhdWdo
LmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2guY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAve/4NFMbuvtD6QSuXAoYQ0SkaO9s
DiNHA4saJNV0OIXd6dtM87w7OETKWWVq24Ab6vQaYh218oCF1GDdLv6EiRB8
oL1k9sK2v70iAVT83vEnmaj6/hQVcBI6mZJH6LXyCgYSP2e5yBQqJu+hgLte
bdg7kOKW2tb937jDn9KYRVFIlEU0/iu/b/Buwq3ahg2BsG3vg92Zk+Dv5VON
QDLE8x8wdi1cor7qBY/RERw4O3LXo3644OU0t6KS3aQxLrXEvWZHHvLhsAu1
BjYbC+qdSddDT1t+adEnZq9/wMhNGhPWCd/uFDZanSpyM913b7eI1Q2aNgA0
cccjEgBsp8IipwIDAQABo4IC1TCCAtEwCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSL
djRDW8NpGZJjlhjZ0SLge0hCvjAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6W
NU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0YXVnaC5jb20wggFMBgNVHSAE
ggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIw
geowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqB
vlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhl
IENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0
Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVk
IHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBv
YmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5Bggr
BgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv
Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNv
bS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYY
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQCM
pgcOpxRJazPzEBYnhGENuQqzXeLyA3a8XL7YaxaAJwV7ucDVkyQHu35PUEkh
vVgIKnxq6N9WxHiO6GK/imdwS3LrUBbs+0v+95m6YhJv6ZfvAHTyTLqrozXU
ohR5NRFeL0p1OfK1llnl/I71Fe/JNgxJHDn1puzsFoJD3zYCKgNdST3FPNIb
2v/xIiubuB85tiJSWUlc56OkCdBK3ZgBnwYV8LxFmpOlwedaHC6sxIk1rsuX
BHbRIJwLFy2LqVtNm0M5NzBVyPQf72lPn/aaJLbqY5DDm4/lSy94R+CKXabE
6lWan7xmbqdDDlMxGbpMRWV2Cxi5ONp4uNgNcwI6MYIClzCCApMCAQEwgZQw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDBi8sMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNTI3MTU0ODI0WjAjBgkqhkiG
9w0BCQQxFgQU0AHM7cormchjbLMev5PFRsp5HYoweQYJKoZIhvcNAQkPMWww
ajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4D
AgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAPnqpp9Pf2dr2
WfD7Uv2+v1F2cYdlr/n8yHb0zAYofk48xh0aYLY/6DzbVpIZlhhz61giXIUu
qOdtgKs0pChHWFSA6a3kqfiE1NRtsJA4G4w2KZCUYM0puxQWQ2jKhcH9Lli4
tkS2uwy0KnKqhS05PTzZ0PoOY8iVkumhZnIwvRj+X/DRN7rdRhAf6QzDRdBe
D9PBClm3twOIPU0m3FUiUm2VK81oliGxQ0UBd2MfPOKbwZAAT3X6B9CpN16Y
yqcttfTH9Ai38p4qi8X6G3gseuvNRD9OpER+zR/2Et/23LqtmeOrcB2qfDm0
P9O4hl6bZxNwlbkbkAEdqzQQ8XP4SA==

--3825401791-1220248199-1369669704=:7155--

From andy@yumaworks.com  Mon May 27 09:10:12 2013
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6960521F96E0 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:10:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBPTZvznTUt5 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:10:11 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 904FD21F93EE for <ietf@ietf.org>; Mon, 27 May 2013 09:10:11 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so6923661pbb.34 for <ietf@ietf.org>; Mon, 27 May 2013 09:10:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=kDKHN/kPw/w5nHbMJHdEua+zLTFmxN1UrlEYLepVLMY=; b=ewHULh9YsGrfV4a5sHiWO24eLwqCSeJzrpcsiDdKYvj/jOSP4P3xyWpcrki14oF+rz ED4+UjS8LGAb7X39K5FjhGDGYOZjXVCP2qezWffymbpXG8MN6vRXxlDA6E2cLnZ/zSRb zTOOht7e37NIQGhklmix90a9DxMb3PONq9hy6UK9S+UGIQfrlHqT1J8+83jNQv0FMtc1 Y0/SyL5OakauIgRhouxdbW/cqQIDQtLBu+bSLhyz14jPoB8IfkCDArK04S7qZAA4c05T io5HvZZME6oaSfI4+RqX43nikLUBRGnNytaiVdHjq3LICePBItDsfLA9uUfwev3sDO33 lX4A==
MIME-Version: 1.0
X-Received: by 10.66.149.5 with SMTP id tw5mr30748316pab.87.1369671011103; Mon, 27 May 2013 09:10:11 -0700 (PDT)
Received: by 10.70.50.164 with HTTP; Mon, 27 May 2013 09:10:11 -0700 (PDT)
In-Reply-To: <B1075CB6-E7BE-4C22-8C5D-1112785B4099@piuha.net>
References: <20130527055257.7635.qmail@joyce.lan> <B1075CB6-E7BE-4C22-8C5D-1112785B4099@piuha.net>
Date: Mon, 27 May 2013 09:10:11 -0700
Message-ID: <CABCOCHQecg0uLVPM245iV8UAjOYYinwiW_wxhgqvCa=yu4j3QQ@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
From: Andy Bierman <andy@yumaworks.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=047d7b6dcdd214c7be04ddb56237
X-Gm-Message-State: ALoCoQlRemJyZKhZCgH+w1h7b5x+veDtcmDSLCsRY0ah27tOJ4XSagE8wN8SSRMd+3Gipo/Toqc4
Cc: John Levine <johnl@taugh.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, 27 May 2013 16:10:12 -0000

--047d7b6dcdd214c7be04ddb56237
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Jari,

On Mon, May 27, 2013 at 5:15 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> John,
>
> > * People aren't aware the IETF exists, or what it does, or that it has
> > an open participation model
> >
> > * People don't read and write English well enough to be comfortable
> > participating
> >
> > * People are unaccustomed to and perhaps uncomfortable expressing
> > overt disagreement
> >
> > * People don't think they have anything to contribute to an organizatio=
n
> > that is mostly people from rich countries
> >
> > * People don't have adequate Internet access for mail, or to use the
> > remote participation tools
>
> Thanks for sending out a list of potential issues.
>
> I think there may be one issue missing from the list. At the end of the
> day, what tends to drive people actual, concrete benefit to themselves or
> their organisations. A drive that is so big that it forces you to cross
> language and other barriers and make at least a time investment in
> participation. As an example, the number of Chinese participants has
> increased rapidly in the IETF. Why? We probably didn't suddenly get much
> better at welcoming new people at the IETF, but the new participants felt
> that work on the Internet is important to them personally, and their
> organisations felt that they need to be part of making Internet standards=
.
> This isn't very surprising, given, for instance, the rise of the Chinese
> technology industry to a very visible role in the world.
>
> So I feel that the issue in many cases is simpler than the ones in the
> list: "What's in it for me"? This obviously has to do with the role of
> vendors in the IETF and the distribution of tech industry in the world. I=
t
> may also have something to do with doing things that are important. I'm
> sure we could be working on topics that are even better aligned to what t=
he
> world needs=85 if the people who need them were here to tell us :-)
>
>

This is the most important factor and trumps all other combined.
If the standards work is relevant to your business or research then
the probability that you will participate in the IETF goes way up.

I think many people on this list forget how different doing engineering
in the IETF is from engineering for a private enterprise. Tasks that take
1 or 2 months in a private enterprise often take 1 or 2 years (or more!).
Competitors working on a standard have a completely different set
of incentives than employees working on a product, so agreement
on standards is much harder to achieve.

Newbies can have a hard time adjusting to these differences.




> The IETF can't change the distribution of industries in the world, but we
> can, for instance, focus on the vendors that are there or work more on
> topics that are interesting for the operational folks. The latter would b=
e
> a good idea for the IETF, anyway.
>
> > For example, if language and net access is a problem, it might be
> > interesting to set up a remote participation center in B.A. during one
> > of the North American meetings (it's one time zone off from Toronto)
>
> We've been looking at setting up something like that (not for BA
> specifically).
>
> Jari
>
>

Andy

--047d7b6dcdd214c7be04ddb56237
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi Jari,<br><br><div class=3D"gmail_quote">On Mon, May 27, 2013 at 5:15 AM,=
 Jari Arkko <span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" t=
arget=3D"_blank">jari.arkko@piuha.net</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">
John,<br>
<br>
&gt; * People aren&#39;t aware the IETF exists, or what it does, or that it=
 has<br>
&gt; an open participation model<br>
&gt;<br>
&gt; * People don&#39;t read and write English well enough to be comfortabl=
e<br>
&gt; participating<br>
&gt;<br>
&gt; * People are unaccustomed to and perhaps uncomfortable expressing<br>
&gt; overt disagreement<br>
&gt;<br>
&gt; * People don&#39;t think they have anything to contribute to an organi=
zation<br>
&gt; that is mostly people from rich countries<br>
&gt;<br>
&gt; * People don&#39;t have adequate Internet access for mail, or to use t=
he<br>
&gt; remote participation tools<br>
<br>
Thanks for sending out a list of potential issues.<br>
<br>
I think there may be one issue missing from the list. At the end of the day=
, what tends to drive people actual, concrete benefit to themselves or thei=
r organisations. A drive that is so big that it forces you to cross languag=
e and other barriers and make at least a time investment in participation. =
As an example, the number of Chinese participants has increased rapidly in =
the IETF. Why? We probably didn&#39;t suddenly get much better at welcoming=
 new people at the IETF, but the new participants felt that work on the Int=
ernet is important to them personally, and their organisations felt that th=
ey need to be part of making Internet standards. This isn&#39;t very surpri=
sing, given, for instance, the rise of the Chinese technology industry to a=
 very visible role in the world.<br>

<br>
So I feel that the issue in many cases is simpler than the ones in the list=
: &quot;What&#39;s in it for me&quot;? This obviously has to do with the ro=
le of vendors in the IETF and the distribution of tech industry in the worl=
d. It may also have something to do with doing things that are important. I=
&#39;m sure we could be working on topics that are even better aligned to w=
hat the world needs=85 if the people who need them were here to tell us :-)=
<br>

<br></blockquote><div><br></div><div><br></div><div>This is the most import=
ant factor and trumps all other combined.</div><div>If the standards work i=
s relevant to your business or research then</div><div>the probability that=
 you will participate in the IETF goes way up.</div>
<div><br></div><div>I think many people on this list forget how different d=
oing engineering</div><div>in the IETF is from engineering for a private en=
terprise. Tasks that take</div><div>1 or 2 months in a private enterprise o=
ften take 1 or 2 years (or more!).</div>
<div>Competitors working on a standard have a completely different set</div=
><div>of incentives than employees working on a product, so agreement</div>=
<div>on standards is much harder to achieve.</div><div><br></div><div>Newbi=
es can have a hard time adjusting to these differences.</div>
<div><br></div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The IETF can&#39;t change the distribution of industries in the world, but =
we can, for instance, focus on the vendors that are there or work more on t=
opics that are interesting for the operational folks. The latter would be a=
 good idea for the IETF, anyway.<br>

<br>
&gt; For example, if language and net access is a problem, it might be<br>
&gt; interesting to set up a remote participation center in B.A. during one=
<br>
&gt; of the North American meetings (it&#39;s one time zone off from Toront=
o)<br>
<br>
We&#39;ve been looking at setting up something like that (not for BA specif=
ically).<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br><div><br></div><div>Andy</div><div><br=
></div>

--047d7b6dcdd214c7be04ddb56237--

From aservin@lacnic.net  Mon May 27 09:12:19 2013
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 A2D1121F9675 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YzNQhkmL5zkY for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:12:18 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9B17D21F9692 for <ietf@ietf.org>; Mon, 27 May 2013 09:12:15 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2001:13c7:7001:7000:ddfb:e8e9:7667:3711]) by mail.lacnic.net.uy (Postfix) with ESMTP id 9B062308424 for <ietf@ietf.org>; Mon, 27 May 2013 13:11:59 -0300 (UYT)
Message-ID: <51A385DF.1050206@lacnic.net>
Date: Mon, 27 May 2013 13:12:15 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com>
In-Reply-To: <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com>
X-Enigmail-Version: 1.5.1
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 16:12:19 -0000

	But also remember, writing I+D is just part of the equation. We also
need reviewers and comments.

Regards,
as

On 5/27/13 7:51 AM, Eggert, Lars wrote:
> On May 27, 2013, at 12:10, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
>> Each IETF document mentions the authors place address (I may suggest
>> adding region, as a categorised by IETF), but not sure of history
>> statistics of how many IETF-documents produced by authors in South
>> America, Africa, or Asia, or others.
> 
> http://www.arkko.com/tools/stats/d-countrydistr.html and related pages
> 
> Lars
> 

From arturo.servin@gmail.com  Mon May 27 09:18:27 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAF3221F8EA4 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iEDbdo3kCWS3 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:18:27 -0700 (PDT)
Received: from mail-qc0-x232.google.com (mail-qc0-x232.google.com [IPv6:2607:f8b0:400d:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2585921F8E9A for <ietf@ietf.org>; Mon, 27 May 2013 09:18:27 -0700 (PDT)
Received: by mail-qc0-f178.google.com with SMTP id l11so3533707qcy.23 for <ietf@ietf.org>; Mon, 27 May 2013 09:18:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=VKTEugv9Ume975rq1TXKfY1kEBDI6ncHbYZdY/F+EdU=; b=U0/wPDiAV11O8VoJFvJet+HhmC/jUESUOmltHoKs0x8kPjxFY6aXZXPaTGt4cSb7Y3 PnATdX5E5jDpjGRVc75Fh27AgB5sPYtyY8XD83JslXfwzcEcFhI79+lIDm19RHOQczkC QBlhA1Mpx+p2oHPB/TtiO4viL4/gPEAtM4U7bkY+W4/NDMbj2vV4EMyoFUyN0A6DlxDs cYaTnFIJsJHv0eHfZkyLRJKokKhZcK8j7qXNKvZX/0maKyCFP5Jb1HXMGy7nD6r/+xq8 tzE5VtK/2eMrIDFOz7ownO2HGviOwQr4RXp+3VvoCw36VZQfE12ybJfmvg0yARS2eXCh Pl5g==
X-Received: by 10.49.84.42 with SMTP id v10mr32817677qey.60.1369671506635; Mon, 27 May 2013 09:18:26 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2001:13c7:7001:7000:ddfb:e8e9:7667:3711]) by mx.google.com with ESMTPSA id w7sm24077824qej.7.2013.05.27.09.18.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 09:18:25 -0700 (PDT)
Message-ID: <51A38750.8060805@gmail.com>
Date: Mon, 27 May 2013 13:18:24 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net> <6.2.5.6.2.20130527063900.06d1a498@resistor.net>
In-Reply-To: <6.2.5.6.2.20130527063900.06d1a498@resistor.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, 27 May 2013 16:18:28 -0000

On 5/27/13 11:15 AM, SM wrote:
> 
> Joel Jaeggli mentioned that a regional NOG is not fertile ground for new
> IETF participants.  Is LACNOG fertile ground for new IETF participants?

	I guess so.

	We have doing some efforts in the past and we are planning to do more.
You will see some recurrent participants to both places (ietf and lacnog).

> 
> The "sending email, comments, reviewing draft" is the really difficult
> part.  My uneducated guess is that it would takes months of work.  It's
> not as negative as it sounds if you consider that overcoming the barrier
> of entry might usually take over a year.

	It is no negative in deed. It is just plain hard.

> 
> Could you ask the people who attended the talk (
> http://www.youtube.com/watch?v=L_zacX9DcZA ) to provide some feedback
> about it to edu-discuss mailing list?

	Sure, I will do that.

Regards,
as

From hgs@cs.columbia.edu  Mon May 27 09:19:24 2013
Return-Path: <hgs@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 9715821F920B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cG+BapQ3HlAz for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:19:19 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9C45321F8EAD for <ietf@ietf.org>; Mon, 27 May 2013 09:19:17 -0700 (PDT)
Received: from new-host-2.home (pool-96-242-116-6.nwrknj.fios.verizon.net [96.242.116.6]) (user=hgs10 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r4RGJEfk004139 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 27 May 2013 12:19:15 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_11D2007A-119A-4148-814A-41D3CF9989DE"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com>
Date: Mon, 27 May 2013 12:19:14 -0400
Message-Id: <94B83A14-1FFE-450C-BAFF-0EC03E425641@cs.columbia.edu>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com> <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1503)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 16:19:24 -0000

--Apple-Mail=_11D2007A-119A-4148-814A-41D3CF9989DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

The most difficult part for any emergency calling system is location =
delivery. WebRTC probably doesn't have much impact on emergency calls if =
all the calls traverse a server of some kind and if the caller location =
can be looked up based on caller IP addresses, but once you have the end =
system involved in location determination (e.g., for mobile devices or =
for DHCP-delivered location), it has to know when a call is an emergency =
call as you otherwise end up providing location for every call, which is =
non-ideal from a privacy and battery perspective.

At least in the US, many of the WebRTC services would be considered =
"interconnected VoIP", so they are indeed subject to 911 obligations.

Henning

On May 26, 2013, at 3:57 PM, Richard Barnes <rlb@ipv.sx> wrote:

> Indeed, there has already been some coordination between the groups, =
going back about a year:
> <http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf>
> <http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt>
>=20
> So my read of the situation is much less dire than James's.  As I =
understand it, the upshot of the initial coordination discussions is =
that there's not a single, clear "RTCWEB+ECRIT" story.  Instead, there =
are a few ways you can put them together.  In the short run, without =
upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB signaling to =
ECRIT-compliant SIP, either at the server, or at the client using =
something like SIP-over-WebSockets.  In the long run, PSAPs can just =
advertise an RTCWEB service like they would advertise a SIP service =
today (in LoST).  Neither of these is incompatible with RTCWEB or ECRIT =
as they're being specified today.
>=20
> I expect there are probably some ECRIT considerations that aren't =
naturally supported in RTCWEB.  Things like real-time text come to mind. =
 However, it doesn't seem to me that there's gross incompatibility.
>=20
> --Richard
>=20
>=20
>=20
>=20
> On Sat, May 25, 2013 at 10:18 AM, John C Klensin <john-ietf@jck.com> =
wrote:
>=20
>=20
> --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
> <jari.arkko@piuha.net> wrote:
>=20
> >...
> > I didn't know about the details of the emergency
> > communications situation. But it is always difficult to
> > balance getting something out early vs. complete. I know how
> > much pressure there is on the working groups to keep up with
> > things actually happening in the browsers and organisations
> > setting up to use this technology. Do you think the retrofit
> > will be problematic, and do you have a specific suggestion
> > about what should be included today?
>=20
> Jari,
>=20
> James will probably have a different answer and perspective, but
> I suggest that retrofits of security-sensitive features are so
> often problematic to make "always" not much of an exaggeration.
>=20
> I don't think there is any general solution to the "early vs.
> complete" tradeoff [1], nor, as long as we keep trying to deal
> with things as collections of disconnected pieces rather than
> systems, to the issues created by WGs with significant overlaps
> in either scope or technology.  What I think we can do is to be
> particularly vigilant to be sure that the two WGs are tracking
> and frequently reviewing each other's work.   At least RTCWEB
> and ECRIT are in the same area, which should make that
> coordination easier than it might be otherwise.
>=20
>    john
>=20
>=20
> [1] Watch for a note about this that I've been trying to
> organize for about two weeks and hope to finish and post this
> weekend.
>=20
>=20
>=20
>=20


--Apple-Mail=_11D2007A-119A-4148-814A-41D3CF9989DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>The most difficult part for any emergency calling system is =
location delivery. WebRTC probably doesn't have much impact on emergency =
calls if all the calls traverse a server of some kind and if the caller =
location can be looked up based on caller IP addresses, but once you =
have the end system involved in location determination (e.g., for mobile =
devices or for DHCP-delivered location), it has to know when a call is =
an emergency call as you otherwise end up providing location for every =
call, which is non-ideal from a privacy and battery =
perspective.</div><div><br></div><div>At least in the US, many of the =
WebRTC services would be considered "interconnected VoIP", so they are =
indeed subject to 911 =
obligations.</div><div><br></div><div>Henning</div><br><div><div>On May =
26, 2013, at 3:57 PM, Richard Barnes &lt;<a =
href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
dir=3D"ltr">Indeed, there has already been some coordination between the =
groups, going back about a year:<div>&lt;<a =
href=3D"http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf">http=
://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf</a>&gt;</div>
<div>&lt;<a =
href=3D"http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt">http://t=
ools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt</a>&gt;</div><div><br></d=
iv><div><span style=3D"font-family:arial,sans-serif;font-size:13px">So =
my read of the situation is much less dire than James's. &nbsp;As I =
understand it, the upshot of the initial coordination discussions is =
that there's not a single, clear "RTCWEB+ECRIT" story. &nbsp;Instead, =
there are a few ways you can put them together. &nbsp;In the short run, =
without upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB =
signaling to ECRIT-compliant SIP, either at the server, or at the client =
using something like SIP-over-WebSockets. &nbsp;In the long run, PSAPs =
can just advertise an RTCWEB service like they would advertise a SIP =
service today (in LoST). &nbsp;Neither of these is incompatible with =
RTCWEB or ECRIT as they're being specified today.</span><br>
</div><div><span =
style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></div><di=
v><span style=3D"font-family:arial,sans-serif;font-size:13px">I expect =
there are probably some ECRIT considerations that aren't naturally =
supported in RTCWEB. &nbsp;Things like real-time text come to mind. =
&nbsp;However, it doesn't seem to me that there's gross =
incompatibility.</span></div>
<div><span =
style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></div><di=
v><span =
style=3D"font-family:arial,sans-serif;font-size:13px">--Richard</span></di=
v><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div><span =
style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></div></d=
iv><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, =
May 25, 2013 at 10:18 AM, John C Klensin <span dir=3D"ltr">&lt;<a =
href=3D"mailto:john-ietf@jck.com" =
target=3D"_blank">john-ietf@jck.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
--On Saturday, May 25, 2013 10:10 +0300 Jari Arkko<br>
&lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko@piuha.net</a>&gt; =
wrote:<br>
<br>
&gt;...<br>
<div class=3D"im">&gt; I didn't know about the details of the =
emergency<br>
&gt; communications situation. But it is always difficult to<br>
&gt; balance getting something out early vs. complete. I know how<br>
&gt; much pressure there is on the working groups to keep up with<br>
&gt; things actually happening in the browsers and organisations<br>
&gt; setting up to use this technology. Do you think the retrofit<br>
&gt; will be problematic, and do you have a specific suggestion<br>
&gt; about what should be included today?<br>
<br>
</div>Jari,<br>
<br>
James will probably have a different answer and perspective, but<br>
I suggest that retrofits of security-sensitive features are so<br>
often problematic to make "always" not much of an exaggeration.<br>
<br>
I don't think there is any general solution to the "early vs.<br>
complete" tradeoff [1], nor, as long as we keep trying to deal<br>
with things as collections of disconnected pieces rather than<br>
systems, to the issues created by WGs with significant overlaps<br>
in either scope or technology. &nbsp;What I think we can do is to be<br>
particularly vigilant to be sure that the two WGs are tracking<br>
and frequently reviewing each other's work. &nbsp; At least RTCWEB<br>
and ECRIT are in the same area, which should make that<br>
coordination easier than it might be otherwise.<br>
<br>
&nbsp; &nbsp;john<br>
<br>
<br>
[1] Watch for a note about this that I've been trying to<br>
organize for about two weeks and hope to finish and post this<br>
weekend.<br>
<br>
<br>
<br>
</blockquote></div><br></div>
</blockquote></div><br></body></html>=

--Apple-Mail=_11D2007A-119A-4148-814A-41D3CF9989DE--

From aservin@lacnic.net  Mon May 27 09:24:14 2013
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 3F1D621F9677 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:24:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KOIi9lsiga6P for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:24:13 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1B03121F89D5 for <ietf@ietf.org>; Mon, 27 May 2013 09:24:13 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2001:13c7:7001:7000:ddfb:e8e9:7667:3711]) by mail.lacnic.net.uy (Postfix) with ESMTP id 4B5E130844E; Mon, 27 May 2013 13:23:53 -0300 (UYT)
Message-ID: <51A388A9.6080206@lacnic.net>
Date: Mon, 27 May 2013 13:24:09 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net> <AE47309F-C7C1-4E82-9A14-68B2A2B7EBBB@gmail.com>
In-Reply-To: <AE47309F-C7C1-4E82-9A14-68B2A2B7EBBB@gmail.com>
X-Enigmail-Version: 1.5.1
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: John Levine <johnl@taugh.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 16:24:15 -0000

On 5/27/13 12:41 PM, Jorge Amodio wrote:
> 
> Translation ?? This a very old discussion and moot point, people that have interest to participate in this type of international forums and processes SHOULD learn English.
> 
> -Jorge
> 

	Another barrier.

	Anyway we are talking about remote participation only.

.as

From jmamodio@gmail.com  Mon May 27 09:27:54 2013
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 8C0F021F966B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:27:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eg6mCB-hijyX for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:27:50 -0700 (PDT)
Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) by ietfa.amsl.com (Postfix) with ESMTP id 73E9621F9660 for <ietf@ietf.org>; Mon, 27 May 2013 09:27:50 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id hv10so4759776vcb.6 for <ietf@ietf.org>; Mon, 27 May 2013 09:27:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9OmuMdZy54EI5Zy5hcGIZuLeUhjXqmj6TU++RNraa1w=; b=DHqKBPfQqGkCIK6shaVBqR+dE61Ons0KN+klBKQz/55oMcVsPxu1szfA5n7tfL6KhJ B2cCkA5uY8zB6PVX4HrYIQ/E4lWQk9d+E48/4xwaWBmhAPs5UzUpbCwGyi3e8LZgp5fl RRElx3IBfwwgqTVJDQI2EguxjEb9hb6jlX0FUzpSzkTf4SamAQDEUBCQ2ubGpPrQq2YN H9mRHoN7mPetfycwnLrNUoujkXdloZAzdM/GZ/k0F4RarLivn6cUztkd9oXK9bNI/fbs cECE99gOLsRMUZFwrcRzme1VnS1GkGFAAZH+j5ncCHDsVppLMF6UUTgRz5rhBWBKF+IV nd9A==
MIME-Version: 1.0
X-Received: by 10.52.156.65 with SMTP id wc1mr10414162vdb.10.1369672069873; Mon, 27 May 2013 09:27:49 -0700 (PDT)
Received: by 10.58.54.115 with HTTP; Mon, 27 May 2013 09:27:49 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1305271133490.7155@joyce.lan>
References: <20130527041505.7301.qmail@joyce.lan> <A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk> <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk> <alpine.BSF.2.00.1305271133490.7155@joyce.lan>
Date: Mon, 27 May 2013 11:27:49 -0500
Message-ID: <CAMzo+1av-hXe2gz=LmrxJQwJTzPkTYRr831igYw4ns8Qf57G5g@mail.gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
From: Jorge Amodio <jmamodio@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=bcaec53aecea2f094204ddb5a190
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "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, 27 May 2013 16:27:54 -0000

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

You should double check, regulations about currency markets are changing
very often, custom/immigration officials will almost for sure ask you how
much currency you are bringing and for what, and as the trip advisor page
says don't expect to be able to convert back leftover pesos to foreign
currency.

There are several sites and news media pages where you can check the
current exchange rates, and expect some volatility on the prices

http://www.lanacion.com.ar/1585934-sin-cambios-el-dolar-blue-comienza-la-semana-en-895

-J



On Mon, May 27, 2013 at 10:37 AM, John R Levine <johnl@taugh.com> wrote:

> Is this above advice from Tripadvisor correct?
>>
>
> I believe so, but when I was there a few years ago for the ICANN meeting,
> excess cash was not a problem.  It wasn't hard to estimate how much cash
> I'd need, and whatever was left I spent at the airport.  The wine they
> drink in Argentina is often better than the stuff they send to the UK
> (which isn't bad) and much cheaper.  Take some home in your suitcase, even
> if you have to pay duty it's a bargain.
>
> This still doesn't mean I think a meeting in South America is a good idea,
> though.  See other messages.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.
>

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

<div dir=3D"ltr"><br><div style>You should double check, regulations about =
currency markets are changing very often, custom/immigration officials will=
 almost for sure ask you how much currency you are bringing and for what, a=
nd as the trip advisor page says don&#39;t expect to be able to convert bac=
k leftover pesos to foreign currency.</div>
<div style><br></div><div style>There are several sites and news media page=
s where you can check the current exchange rates, and expect some volatilit=
y on the prices</div><div style><br></div><div style><a href=3D"http://www.=
lanacion.com.ar/1585934-sin-cambios-el-dolar-blue-comienza-la-semana-en-895=
">http://www.lanacion.com.ar/1585934-sin-cambios-el-dolar-blue-comienza-la-=
semana-en-895</a><br>
</div><div style><br></div><div style>-J</div><div style><br></div></div><d=
iv class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, May 27,=
 2013 at 10:37 AM, John R Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:jo=
hnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
Is this above advice from Tripadvisor correct?<br>
</blockquote>
<br></div>
I believe so, but when I was there a few years ago for the ICANN meeting, e=
xcess cash was not a problem. =A0It wasn&#39;t hard to estimate how much ca=
sh I&#39;d need, and whatever was left I spent at the airport. =A0The wine =
they drink in Argentina is often better than the stuff they send to the UK =
(which isn&#39;t bad) and much cheaper. =A0Take some home in your suitcase,=
 even if you have to pay duty it&#39;s a bargain.<br>

<br>
This still doesn&#39;t mean I think a meeting in South America is a good id=
ea, though. =A0See other messages.<br>
<br>
Regards,<br>
John Levine, <a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@tau=
gh.com</a>, Taughannock Networks, Trumansburg NY<br>
&quot;I dropped the toothpaste&quot;, said Tom, crestfallenly.<br>
</blockquote></div><br></div>

--bcaec53aecea2f094204ddb5a190--

From johnl@taugh.com  Mon May 27 09:31:04 2013
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3797921F8E34 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:31:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkLwc8JSp8R4 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:31:03 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 58A3B21F8EA4 for <ietf@ietf.org>; Mon, 27 May 2013 09:31:03 -0700 (PDT)
Received: (qmail 62215 invoked from network); 27 May 2013 16:31:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=f306.51a38a4a.k1305; bh=0/GuAKlVb4nS+MsT7yHqAA2Vks5masusAG4p/GgI/Lc=; b=Ox+DIHBadlXsh2fHt8O5uZ/dEuhqkkHpKc1lgyAUJzw+UMIfWL01pcfyqz+7Vl4WVwm2x08z0skuiEUFPmzSGeKWi5uLQ2EnyX2xUXRzeQ0tbRm6Az6Eqx/Ln1wmjvje1ACWWN8sh6frfVZ355OOekbD7esmM5QhqxpRFGGphlo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=f306.51a38a4a.k1305; bh=0/GuAKlVb4nS+MsT7yHqAA2Vks5masusAG4p/GgI/Lc=; b=FShN+vkK4YC4j9l1+R+mClTJ9ISi7OonQ1xjHuFPeEq5Q6pO4tCGD5TtT4cDBp+xEa5WAmSjXlgEn3yHMcF0qmqEuDDLnXDIpEb+TGFdlGdVCcsrU9HB4G4z1sIZsrpoFKuTZkUcPnDL4xDTI7q+jE7hV9EVHaXSp9gwQ//bzj8=
Received: (ofmipd 127.0.0.1); 27 May 2013 16:30:44 -0000
Date: 27 May 2013 12:30:24 -0400
Message-ID: <alpine.BSF.2.00.1305271229010.7155@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Arturo Servin" <aservin@lacnic.net>
Subject: Re: Issues in wider geographic participation
In-Reply-To: <51A388A9.6080206@lacnic.net>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net> <AE47309F-C7C1-4E82-9A14-68B2A2B7EBBB@gmail.com> <51A388A9.6080206@lacnic.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-475837478-1369672262=:7155"
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, 27 May 2013 16:31:04 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-475837478-1369672262=:7155
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

>> Translation ?? This a very old discussion and moot point, people that 
>> have interest to participate in this type of international forums and 
>> processes SHOULD learn English.

> 	Another barrier.
>
> 	Anyway we are talking about remote participation only.

You guys would know better than us gringos, but how likely is it that 
having translation available for live sessions would encourage people to 
use their limited English to work through drafts and try some e-mail?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.
--3825401791-475837478-1369672262=:7155
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJCQYJKoZIhvcNAQcCoIII+jCCCPYCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBjowggY2MIIFHqADAgECAgMGLywwDQYJKoZIhvcNAQEFBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMzAzMTYxOTQ0MDdaFw0xNDAzMTgxMjI4MzVaMFUxGTAX
BgNVBA0TEHFaMXRuOTBuMkdVODZzemYxGDAWBgNVBAMMD2pvaG5sQHRhdWdo
LmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxAdGF1Z2guY29tMIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAve/4NFMbuvtD6QSuXAoYQ0SkaO9s
DiNHA4saJNV0OIXd6dtM87w7OETKWWVq24Ab6vQaYh218oCF1GDdLv6EiRB8
oL1k9sK2v70iAVT83vEnmaj6/hQVcBI6mZJH6LXyCgYSP2e5yBQqJu+hgLte
bdg7kOKW2tb937jDn9KYRVFIlEU0/iu/b/Buwq3ahg2BsG3vg92Zk+Dv5VON
QDLE8x8wdi1cor7qBY/RERw4O3LXo3644OU0t6KS3aQxLrXEvWZHHvLhsAu1
BjYbC+qdSddDT1t+adEnZq9/wMhNGhPWCd/uFDZanSpyM913b7eI1Q2aNgA0
cccjEgBsp8IipwIDAQABo4IC1TCCAtEwCQYDVR0TBAIwADALBgNVHQ8EBAMC
BLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSL
djRDW8NpGZJjlhjZ0SLge0hCvjAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6W
NU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0YXVnaC5jb20wggFMBgNVHSAE
ggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIw
geowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqB
vlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhl
IENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0
Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVk
IHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBv
YmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFy
dHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5Bggr
BgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv
Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNv
bS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYY
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQCM
pgcOpxRJazPzEBYnhGENuQqzXeLyA3a8XL7YaxaAJwV7ucDVkyQHu35PUEkh
vVgIKnxq6N9WxHiO6GK/imdwS3LrUBbs+0v+95m6YhJv6ZfvAHTyTLqrozXU
ohR5NRFeL0p1OfK1llnl/I71Fe/JNgxJHDn1puzsFoJD3zYCKgNdST3FPNIb
2v/xIiubuB85tiJSWUlc56OkCdBK3ZgBnwYV8LxFmpOlwedaHC6sxIk1rsuX
BHbRIJwLFy2LqVtNm0M5NzBVyPQf72lPn/aaJLbqY5DDm4/lSy94R+CKXabE
6lWan7xmbqdDDlMxGbpMRWV2Cxi5ONp4uNgNcwI6MYIClzCCApMCAQEwgZQw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQQIDBi8sMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqG
SIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMwNTI3MTYzMTAyWjAjBgkqhkiG
9w0BCQQxFgQU7KtUGuNomBNTDVit4d0E721/0TAweQYJKoZIhvcNAQkPMWww
ajALBglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAKBggq
hkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4D
AgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEASzAMuwGLlIL1
p5o6054Eu2M4xTSW1qJuhQsM/P+txnzrnOXhM6GB4BNqi11uRvVEtnPLXfud
qSaCPFrNPcz628gVW2QtBsqJhjMtPoeR/CTziVdoQoRUrdpo0dF04zdRK/Sv
pCW5/IL2ZxDm80b7dqialwHT/9+VX65+xbPvD1CENbhvkHEcW6uTxcR05j4p
wlsaDlf/BtGUMQddeQoqw3eYo1PWoPxvkSEJYzje2xC5qHNMfyPLUTsUzxBT
VBjjrj95LbDdB3jQoqwfH+iAr5heaW0n8AeNzex1k1ltEaMBFNwb3jy8r4Iv
ah/4WzTg7x10TzaWRRw1KHd7/1iJCw==

--3825401791-475837478-1369672262=:7155--

From arturo.servin@gmail.com  Mon May 27 09:37:26 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFA2F21F968F for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:37:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pwjNAgWwZb5o for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:37:26 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 45A8821F968E for <ietf@ietf.org>; Mon, 27 May 2013 09:37:26 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n1so3637722qcw.27 for <ietf@ietf.org>; Mon, 27 May 2013 09:37:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=K+NxAy3zeUOCPX8Jcb6KtXq6fsKfu+RV2G3yJl+QOU4=; b=HBAEp+V8yU9sX2HRDZFJcXbJfB3YUq1usY7tGGk/OkI9BDQSoKPF+fiKN8YkDmz4sh MwEJ87j1Hh72ubdslhG81G67yOqRy01B5bbY0upxkoeq/4SHe8tC8vl5clpXU0AV07tk C+tvFhaNMDn1qbPzmqhnfo+agaUBhw6zauRFbCJr8O25GU5OPeCh1L7IYGgCxwTKhIGT P1xugZcGE4cRSsaW46favZiHizhvMmgjApga4LWkRRLzJRLgiFghc1Bu+1eyoLlkEQDq xmiIXJBoXaaNKin0c4tISVXjCGEQ0M07s73z+d5eH/l7oYJ34ky2cbbkEeyssWoQSu6L qCRw==
X-Received: by 10.49.49.167 with SMTP id v7mr33240791qen.10.1369672645743; Mon, 27 May 2013 09:37:25 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([200.7.87.33]) by mx.google.com with ESMTPSA id u5sm24115741qeu.6.2013.05.27.09.37.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 09:37:24 -0700 (PDT)
Message-ID: <51A38BC3.9060002@gmail.com>
Date: Mon, 27 May 2013 13:37:23 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: Issues in wider geographic participation
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net> <AE47309F-C7C1-4E82-9A14-68B2A2B7EBBB@gmail.com> <51A388A9.6080206@lacnic.net> <alpine.BSF.2.00.1305271229010.7155@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1305271229010.7155@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1
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, 27 May 2013 16:37:26 -0000

	The idea that I had for this remote participation hub was to "break the
ice". I saw no problem to provide some facilities to newcomers are more
comfortable. Perhaps, later that would encourage them to improve their
English and participate.

	But these are just ideas.

.as

On 5/27/13 1:30 PM, John R Levine wrote:
>>> Translation ?? This a very old discussion and moot point, people that
>>> have interest to participate in this type of international forums and
>>> processes SHOULD learn English.
> 
>>     Another barrier.
>>
>>     Anyway we are talking about remote participation only.
> 
> You guys would know better than us gringos, but how likely is it that
> having translation available for live sessions would encourage people to
> use their limited English to work through drafts and try some e-mail?
> 
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.

From juliao@braga.eti.br  Mon May 27 09:41:28 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B6521F96B2 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov3IYW3r4Q5H for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 09:41:27 -0700 (PDT)
Received: from mail-gg0-x22d.google.com (mail-gg0-x22d.google.com [IPv6:2607:f8b0:4002:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 929B921F96AD for <ietf@ietf.org>; Mon, 27 May 2013 09:41:27 -0700 (PDT)
Received: by mail-gg0-f173.google.com with SMTP id l4so1907214ggn.32 for <ietf@ietf.org>; Mon, 27 May 2013 09:41:27 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=/bLxSoGIz733KBeCfG01EArl7hX51dddswyFO37ny8Q=; b=cVItAYPjbavzpUx5XpiYpDmmCMPEQo7Ki9U6qNJX3VwfsJgs6K8htzwqczY0LmWO/r o2gxyG0w5JOeAE+qnhP2iVgqsPHGEcWtzndh0xeJCxPq6fMj0sqnPA2J7r+1xdAEIl9D b1mJguVT6i+AbauicTzB+emgIUO2d/hnN/rWRGOtCVQFVirHX44kaBE3wMZOlPfgaJua 2MA5+LTy6Uugo/+ahYAwMa3yqin/jdfzmOogHRtyegbcyVmXtMorM9b2I+cc2x+GCkzO 6s0IkZZYlEkY1AxGn36/hUxM524R5IcW7nEgzYX0v9wa2Vj2V0nvplZ3C+xTHa2w7o3O ew7Q==
X-Received: by 10.236.127.243 with SMTP id d79mr2549355yhi.4.1369672887093; Mon, 27 May 2013 09:41:27 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id m74sm41144450yhm.0.2013.05.27.09.41.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 09:41:26 -0700 (PDT)
Message-ID: <51A38CB2.6030102@braga.eti.br>
Date: Mon, 27 May 2013 13:41:22 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br> <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com>
In-Reply-To: <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQnYAKuFuErNGAUmtcZD44REGdFxbmMTu0DEbLQZMeHy7ToCbnNlaCft1x/da0Va+qOwxUO4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 16:41:28 -0000

Hi Edwin,

I don't know about AfriNIC. I know the reality of Brazil and a little
about Lacnic. My answers and additional comments follow.

1. When you appended: "...and that I believe should start at the
grassroots leve & at the regional/national level." you touch a very very
significant point!

2. Our people know RFCs, but are far from knowing about the IETF. So I
thing the process of participation in local events must be systematic,
e.g. one WG that need to do some pre-meeting before an annual meeting of
IETF. I think the *absence of the IETF* is the reason for the decline in
participation.

3. ISOC chapters can help immensely. If can not happen WGs meetings, so
the chapter can do a meeting about IETF at events happening
traditionally: Lacnic, Nic.br, SBC, etc. This is the systematic and
continuous ways, in my view. That such movements may become, time will
tell.

4. I do not believe that language is a problem in local events, but
Lacnic, Nic.br and others events traditionally have simultaneous
translation from English to Spanish and Portuguese and vice versa.

5. I think stimuli help, certainly. But it is not essential. What is
important is the *participation of the IETF* locally. Perhaps an
interesting step is to link the ISOC Fellowships with local
participation. That is, give significant value to local participation
when  happen the selection process.

6. Also, you must remember that in Brazil the infratestrutura the
Internet is very good. I don't know about the Africa countries. But I
think that we can abstract about this.

7. Given the structure of the IETF (very complex) I would recommend that
there were regional and local liaison peoples  helping ISOC chapters in
th plans of participations.

Let me see if your questions have been answered, please.

Regards,

Julião


Em 27/05/2013 07:01, Edwin A. Opare escreveu:
> To borrow your words: > "the issue is to establish a systematic
> and effective process in under-represented regions", and that I believe
> should start at the grassroots level & at the regional/national level .
>
> Why does the numbers from the AfriNIC and LACNIC regions keep declining?
> Don't these regions operate networks like everyone else? Which areas/WGs
> of the IETF will they find particularly helpful/useful to subscribe
> to? Are the AfNOG annual meetings enough to encourage participation from
> the AfriNIC region? Could the IETF run "a day or two event" annually at
> the AfNOG meetings as part of the "AfNOG Tutorials Workshop" to create a
> lot more awareness and elicit participation? Could the institution of
> "IETF Champions" in the under-rep regions where ISOC has presence
> influence participation from these regions?
> 
> The ISOC Ghana Chapter for example runs a GhNOG workshop (4 day event)
> annually in the month of July where workshop participants are trained in
> a variety of areas relating to System Administration, Network Monitoring
> & Management, CERTs and many more.
> 
> Going into the next workshop this July, the Chapter plans to dedicate a
> day of the workshop to awareness creation about the IETF. Will this
> increase participation from Ghana in any way? If the approach is done
> right with a keen focus on the needs of participants it most definitely
> will. 
> 
> At best we all agree there is the need for active participation and
> inclusiveness from all the regions if the Internet is to develop and
> evolve to its fullest potential. Let's work together to get EVERY
> ENGINEER on board!!

From rlb@ipv.sx  Mon May 27 10:51:30 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B81D21F940B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 10:51:29 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuh7ygL7954u for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 10:51:24 -0700 (PDT)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id CBC4121F962A for <ietf@ietf.org>; Mon, 27 May 2013 10:51:21 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i10so9071425oag.15 for <ietf@ietf.org>; Mon, 27 May 2013 10:51:20 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=mCibWt0WZkSgpHVGdlDgpEqAgap8+9lJI7QyL+UqXvI=; b=KBArLyCXqPYPexDu3t6CAYy6A/8LhPpLSNEXawZ5OzKvmJyscW+nPfzJ21CRkHJJWx zs47s4pTZD7q+G2QDuvczT9mZIBX8QQJr5bON6KE38VTIW9Kxqr1A4labmdJRdJoR850 9LQaxak68VLgtlLmFru+5nyFC50mnrlk5W01owm6ELlbx89mp1TVS3G+/ncRyb97Pn12 vlddN9vVIHfNWul4iQHBLfLYoQcos7FExNbXoX4TMzPkTo6PAVyu2GcfvMLLCBrC7bNs aXRluOgdDujts1vJq8XHBmJAjBMePMiHl95d290Wox2TADcrmKNCyGHbata80Jw2Eqt6 Vcvw==
MIME-Version: 1.0
X-Received: by 10.60.42.104 with SMTP id n8mr19015558oel.94.1369677080492; Mon, 27 May 2013 10:51:20 -0700 (PDT)
Received: by 10.60.102.146 with HTTP; Mon, 27 May 2013 10:51:20 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <94B83A14-1FFE-450C-BAFF-0EC03E425641@cs.columbia.edu>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com> <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com> <94B83A14-1FFE-450C-BAFF-0EC03E425641@cs.columbia.edu>
Date: Mon, 27 May 2013 13:51:20 -0400
Message-ID: <CAL02cgQHCyPM-movR8MTNYYFe8utGP8PU8YSa8VtWYh8MDFR1A@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Richard Barnes <rlb@ipv.sx>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Content-Type: multipart/alternative; boundary=089e0149ca5cd712a604ddb6cb2f
X-Gm-Message-State: ALoCoQlg2FbDlmQZL7UwxNc7TPWTHdi7n/3GRbmRf99OEreor7SUdT5fA+Q6+EjfHmI22AgeOffA
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 17:51:30 -0000

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

Even for location delivery, there's not that much to say at the standards
layer.

For *delivery*, the story is the same as with signaling.  Either the RTCWeb
VoIP service can translate the location information to comply with RFC
6442, or the PSAP can just build a web app that collects it however it
likes.

For *determination*, it's about the browser.  You can do browser-based
geolocation today, to "OK" quality.  Or the browser could implement the
GEOPRIV protocols to benefit from network-provided location.

All that's about implementation/deployment though.  I don't really see any
new standards there.

--Richard



On Mon, May 27, 2013 at 12:19 PM, Henning Schulzrinne
<hgs@cs.columbia.edu>wrote:

> The most difficult part for any emergency calling system is location
> delivery. WebRTC probably doesn't have much impact on emergency calls if
> all the calls traverse a server of some kind and if the caller location can
> be looked up based on caller IP addresses, but once you have the end system
> involved in location determination (e.g., for mobile devices or for
> DHCP-delivered location), it has to know when a call is an emergency call
> as you otherwise end up providing location for every call, which is
> non-ideal from a privacy and battery perspective.
>
> At least in the US, many of the WebRTC services would be considered
> "interconnected VoIP", so they are indeed subject to 911 obligations.
>
> Henning
>
> On May 26, 2013, at 3:57 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
> Indeed, there has already been some coordination between the groups, going
> back about a year:
> <http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf>
> <http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt>
>
> So my read of the situation is much less dire than James's.  As I
> understand it, the upshot of the initial coordination discussions is that
> there's not a single, clear "RTCWEB+ECRIT" story.  Instead, there are a few
> ways you can put them together.  In the short run, without upgrading PSAPs,
> RTCWEB VoIP services can bridge RTCWEB signaling to ECRIT-compliant SIP,
> either at the server, or at the client using something like
> SIP-over-WebSockets.  In the long run, PSAPs can just advertise an RTCWEB
> service like they would advertise a SIP service today (in LoST).  Neither
> of these is incompatible with RTCWEB or ECRIT as they're being specified
> today.
>
> I expect there are probably some ECRIT considerations that aren't
> naturally supported in RTCWEB.  Things like real-time text come to mind.
>  However, it doesn't seem to me that there's gross incompatibility.
>
> --Richard
>
>
>
>
> On Sat, May 25, 2013 at 10:18 AM, John C Klensin <john-ietf@jck.com>wrote:
>
>>
>>
>> --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
>> <jari.arkko@piuha.net> wrote:
>>
>> >...
>> > I didn't know about the details of the emergency
>> > communications situation. But it is always difficult to
>> > balance getting something out early vs. complete. I know how
>> > much pressure there is on the working groups to keep up with
>> > things actually happening in the browsers and organisations
>> > setting up to use this technology. Do you think the retrofit
>> > will be problematic, and do you have a specific suggestion
>> > about what should be included today?
>>
>> Jari,
>>
>> James will probably have a different answer and perspective, but
>> I suggest that retrofits of security-sensitive features are so
>> often problematic to make "always" not much of an exaggeration.
>>
>> I don't think there is any general solution to the "early vs.
>> complete" tradeoff [1], nor, as long as we keep trying to deal
>> with things as collections of disconnected pieces rather than
>> systems, to the issues created by WGs with significant overlaps
>> in either scope or technology.  What I think we can do is to be
>> particularly vigilant to be sure that the two WGs are tracking
>> and frequently reviewing each other's work.   At least RTCWEB
>> and ECRIT are in the same area, which should make that
>> coordination easier than it might be otherwise.
>>
>>    john
>>
>>
>> [1] Watch for a note about this that I've been trying to
>> organize for about two weeks and hope to finish and post this
>> weekend.
>>
>>
>>
>>
>
>

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

<div dir=3D"ltr">Even for location delivery, there&#39;s not that much to s=
ay at the standards layer.<div><br></div><div>For *delivery*, the story is =
the same as with signaling. =A0Either the RTCWeb VoIP service can translate=
 the location information to comply with RFC 6442, or the PSAP can just bui=
ld a web app that collects it however it likes.</div>
<div><br></div><div>For *determination*, it&#39;s about the browser. =A0You=
 can do browser-based geolocation today, to &quot;OK&quot; quality. =A0Or t=
he browser could implement the GEOPRIV protocols to benefit from network-pr=
ovided location.</div>
<div><br></div><div>All that&#39;s about implementation/deployment though. =
=A0I don&#39;t really see any new standards there.</div><div><br></div><div=
>--Richard</div>
<div><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On M=
on, May 27, 2013 at 12:19 PM, Henning Schulzrinne <span dir=3D"ltr">&lt;<a =
href=3D"mailto:hgs@cs.columbia.edu" target=3D"_blank">hgs@cs.columbia.edu</=
a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div>The=
 most difficult part for any emergency calling system is location delivery.=
 WebRTC probably doesn&#39;t have much impact on emergency calls if all the=
 calls traverse a server of some kind and if the caller location can be loo=
ked up based on caller IP addresses, but once you have the end system invol=
ved in location determination (e.g., for mobile devices or for DHCP-deliver=
ed location), it has to know when a call is an emergency call as you otherw=
ise end up providing location for every call, which is non-ideal from a pri=
vacy and battery perspective.</div>

<div><br></div><div>At least in the US, many of the WebRTC services would b=
e considered &quot;interconnected VoIP&quot;, so they are indeed subject to=
 911 obligations.</div><span><font color=3D"#888888"><div>
<br></div><div>Henning</div></font></span><div><div><br><div><div>On May 26=
, 2013, at 3:57 PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" target=
=3D"_blank">rlb@ipv.sx</a>&gt; wrote:</div><br><blockquote type=3D"cite">
<div dir=3D"ltr">Indeed, there has already been some coordination between t=
he groups, going back about a year:<div>&lt;<a href=3D"http://tools.ietf.or=
g/agenda/84/slides/slides-84-ecrit-0.pdf" target=3D"_blank">http://tools.ie=
tf.org/agenda/84/slides/slides-84-ecrit-0.pdf</a>&gt;</div>


<div>&lt;<a href=3D"http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.tx=
t" target=3D"_blank">http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.t=
xt</a>&gt;</div><div><br></div><div><span style=3D"font-family:arial,sans-s=
erif;font-size:13px">So my read of the situation is much less dire than Jam=
es&#39;s. =A0As I understand it, the upshot of the initial coordination dis=
cussions is that there&#39;s not a single, clear &quot;RTCWEB+ECRIT&quot; s=
tory. =A0Instead, there are a few ways you can put them together. =A0In the=
 short run, without upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB=
 signaling to ECRIT-compliant SIP, either at the server, or at the client u=
sing something like SIP-over-WebSockets. =A0In the long run, PSAPs can just=
 advertise an RTCWEB service like they would advertise a SIP service today =
(in LoST). =A0Neither of these is incompatible with RTCWEB or ECRIT as they=
&#39;re being specified today.</span><br>


</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">I expect there are probably some ECRIT considerations that aren&#39;t na=
turally supported in RTCWEB. =A0Things like real-time text come to mind. =
=A0However, it doesn&#39;t seem to me that there&#39;s gross incompatibilit=
y.</span></div>


<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">--R=
ichard</span></div><div><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px"><br>


</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x"><br></span></div></div><div class=3D"gmail_extra"><br><br><div class=3D"=
gmail_quote">On Sat, May 25, 2013 at 10:18 AM, John C Klensin <span dir=3D"=
ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@j=
ck.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<br>
--On Saturday, May 25, 2013 10:10 +0300 Jari Arkko<br>
&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@pi=
uha.net</a>&gt; wrote:<br>
<br>
&gt;...<br>
<div>&gt; I didn&#39;t know about the details of the emergency<br>
&gt; communications situation. But it is always difficult to<br>
&gt; balance getting something out early vs. complete. I know how<br>
&gt; much pressure there is on the working groups to keep up with<br>
&gt; things actually happening in the browsers and organisations<br>
&gt; setting up to use this technology. Do you think the retrofit<br>
&gt; will be problematic, and do you have a specific suggestion<br>
&gt; about what should be included today?<br>
<br>
</div>Jari,<br>
<br>
James will probably have a different answer and perspective, but<br>
I suggest that retrofits of security-sensitive features are so<br>
often problematic to make &quot;always&quot; not much of an exaggeration.<b=
r>
<br>
I don&#39;t think there is any general solution to the &quot;early vs.<br>
complete&quot; tradeoff [1], nor, as long as we keep trying to deal<br>
with things as collections of disconnected pieces rather than<br>
systems, to the issues created by WGs with significant overlaps<br>
in either scope or technology. =A0What I think we can do is to be<br>
particularly vigilant to be sure that the two WGs are tracking<br>
and frequently reviewing each other&#39;s work. =A0 At least RTCWEB<br>
and ECRIT are in the same area, which should make that<br>
coordination easier than it might be otherwise.<br>
<br>
=A0 =A0john<br>
<br>
<br>
[1] Watch for a note about this that I&#39;ve been trying to<br>
organize for about two weeks and hope to finish and post this<br>
weekend.<br>
<br>
<br>
<br>
</blockquote></div><br></div>
</blockquote></div><br></div></div></div></blockquote></div><br></div></div=
></div>

--089e0149ca5cd712a604ddb6cb2f--

From hgs@cs.columbia.edu  Mon May 27 10:56:04 2013
Return-Path: <hgs@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 6569421F8D94 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 10:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDo8fzUH8WVa for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 10:55:59 -0700 (PDT)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id 603B921F8EA4 for <ietf@ietf.org>; Mon, 27 May 2013 10:55:57 -0700 (PDT)
Received: from new-host-2.home (pool-96-242-116-6.nwrknj.fios.verizon.net [96.242.116.6]) (user=hgs10 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r4RHtp9D007941 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 27 May 2013 13:55:52 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_88DEBCE7-F6B7-46EC-ABE8-C722E46CBF99"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <CAL02cgQHCyPM-movR8MTNYYFe8utGP8PU8YSa8VtWYh8MDFR1A@mail.gmail.com>
Date: Mon, 27 May 2013 13:55:51 -0400
Message-Id: <ADAA4A8A-E5BD-4DF1-B9E1-270A1780998C@cs.columbia.edu>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com> <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com> <94B83A14-1FFE-450C-BAFF-0EC03E425641@cs.columbia.edu> <CAL02cgQHCyPM-movR8MTNYYFe8utGP8PU8YSa8VtWYh8MDFR1A@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1503)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 17:56:04 -0000

--Apple-Mail=_88DEBCE7-F6B7-46EC-ABE8-C722E46CBF99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Agreed - this is not so much about standards, but developer awareness. =
If we write any "how to" or similar informational documents, they should =
probably contain that type of discussion.

There is a browser aspect, however: Right now, users only have a binary =
choice about location disclosure, even though I suspect many users would =
be fine with "location disclosure for 911 only", not "disclose my =
fine-grained location for any purpose you like".

On May 27, 2013, at 1:51 PM, Richard Barnes <rlb@ipv.sx> wrote:

> Even for location delivery, there's not that much to say at the =
standards layer.
>=20
> For *delivery*, the story is the same as with signaling.  Either the =
RTCWeb VoIP service can translate the location information to comply =
with RFC 6442, or the PSAP can just build a web app that collects it =
however it likes.
>=20
> For *determination*, it's about the browser.  You can do browser-based =
geolocation today, to "OK" quality.  Or the browser could implement the =
GEOPRIV protocols to benefit from network-provided location.
>=20
> All that's about implementation/deployment though.  I don't really see =
any new standards there.
>=20
> --Richard
>=20
>=20
>=20
> On Mon, May 27, 2013 at 12:19 PM, Henning Schulzrinne =
<hgs@cs.columbia.edu> wrote:
> The most difficult part for any emergency calling system is location =
delivery. WebRTC probably doesn't have much impact on emergency calls if =
all the calls traverse a server of some kind and if the caller location =
can be looked up based on caller IP addresses, but once you have the end =
system involved in location determination (e.g., for mobile devices or =
for DHCP-delivered location), it has to know when a call is an emergency =
call as you otherwise end up providing location for every call, which is =
non-ideal from a privacy and battery perspective.
>=20
> At least in the US, many of the WebRTC services would be considered =
"interconnected VoIP", so they are indeed subject to 911 obligations.
>=20
> Henning
>=20
> On May 26, 2013, at 3:57 PM, Richard Barnes <rlb@ipv.sx> wrote:
>=20
>> Indeed, there has already been some coordination between the groups, =
going back about a year:
>> <http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf>
>> <http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt>
>>=20
>> So my read of the situation is much less dire than James's.  As I =
understand it, the upshot of the initial coordination discussions is =
that there's not a single, clear "RTCWEB+ECRIT" story.  Instead, there =
are a few ways you can put them together.  In the short run, without =
upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB signaling to =
ECRIT-compliant SIP, either at the server, or at the client using =
something like SIP-over-WebSockets.  In the long run, PSAPs can just =
advertise an RTCWEB service like they would advertise a SIP service =
today (in LoST).  Neither of these is incompatible with RTCWEB or ECRIT =
as they're being specified today.
>>=20
>> I expect there are probably some ECRIT considerations that aren't =
naturally supported in RTCWEB.  Things like real-time text come to mind. =
 However, it doesn't seem to me that there's gross incompatibility.
>>=20
>> --Richard
>>=20
>>=20
>>=20
>>=20
>> On Sat, May 25, 2013 at 10:18 AM, John C Klensin <john-ietf@jck.com> =
wrote:
>>=20
>>=20
>> --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
>> <jari.arkko@piuha.net> wrote:
>>=20
>> >...
>> > I didn't know about the details of the emergency
>> > communications situation. But it is always difficult to
>> > balance getting something out early vs. complete. I know how
>> > much pressure there is on the working groups to keep up with
>> > things actually happening in the browsers and organisations
>> > setting up to use this technology. Do you think the retrofit
>> > will be problematic, and do you have a specific suggestion
>> > about what should be included today?
>>=20
>> Jari,
>>=20
>> James will probably have a different answer and perspective, but
>> I suggest that retrofits of security-sensitive features are so
>> often problematic to make "always" not much of an exaggeration.
>>=20
>> I don't think there is any general solution to the "early vs.
>> complete" tradeoff [1], nor, as long as we keep trying to deal
>> with things as collections of disconnected pieces rather than
>> systems, to the issues created by WGs with significant overlaps
>> in either scope or technology.  What I think we can do is to be
>> particularly vigilant to be sure that the two WGs are tracking
>> and frequently reviewing each other's work.   At least RTCWEB
>> and ECRIT are in the same area, which should make that
>> coordination easier than it might be otherwise.
>>=20
>>    john
>>=20
>>=20
>> [1] Watch for a note about this that I've been trying to
>> organize for about two weeks and hope to finish and post this
>> weekend.
>>=20
>>=20
>>=20
>>=20
>=20
>=20


--Apple-Mail=_88DEBCE7-F6B7-46EC-ABE8-C722E46CBF99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>Agreed - this is not so much about standards, but developer =
awareness. If we write any "how to" or similar informational documents, =
they should probably contain that type of =
discussion.</div><div><br></div><div>There is a browser aspect, however: =
Right now, users only have a binary choice about location disclosure, =
even though I suspect many users would be fine with "location disclosure =
for 911 only", not "disclose my fine-grained location for any purpose =
you like".</div><br><div><div>On May 27, 2013, at 1:51 PM, Richard =
Barnes &lt;<a href=3D"mailto:rlb@ipv.sx">rlb@ipv.sx</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">Even for location delivery, there's not =
that much to say at the standards layer.<div><br></div><div>For =
*delivery*, the story is the same as with signaling. &nbsp;Either the =
RTCWeb VoIP service can translate the location information to comply =
with RFC 6442, or the PSAP can just build a web app that collects it =
however it likes.</div>
<div><br></div><div>For *determination*, it's about the browser. =
&nbsp;You can do browser-based geolocation today, to "OK" quality. =
&nbsp;Or the browser could implement the GEOPRIV protocols to benefit =
from network-provided location.</div>
<div><br></div><div>All that's about implementation/deployment though. =
&nbsp;I don't really see any new standards =
there.</div><div><br></div><div>--Richard</div>
<div><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On =
Mon, May 27, 2013 at 12:19 PM, Henning Schulzrinne <span =
dir=3D"ltr">&lt;<a href=3D"mailto:hgs@cs.columbia.edu" =
target=3D"_blank">hgs@cs.columbia.edu</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word"><div>The most difficult part for any =
emergency calling system is location delivery. WebRTC probably doesn't =
have much impact on emergency calls if all the calls traverse a server =
of some kind and if the caller location can be looked up based on caller =
IP addresses, but once you have the end system involved in location =
determination (e.g., for mobile devices or for DHCP-delivered location), =
it has to know when a call is an emergency call as you otherwise end up =
providing location for every call, which is non-ideal from a privacy and =
battery perspective.</div>

<div><br></div><div>At least in the US, many of the WebRTC services =
would be considered "interconnected VoIP", so they are indeed subject to =
911 obligations.</div><span><font color=3D"#888888"><div>
<br></div><div>Henning</div></font></span><div><br><div><div>On May 26, =
2013, at 3:57 PM, Richard Barnes &lt;<a href=3D"mailto:rlb@ipv.sx" =
target=3D"_blank">rlb@ipv.sx</a>&gt; wrote:</div><br><blockquote =
type=3D"cite">
<div dir=3D"ltr">Indeed, there has already been some coordination =
between the groups, going back about a year:<div>&lt;<a =
href=3D"http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf" =
target=3D"_blank">http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0=
.pdf</a>&gt;</div>


<div>&lt;<a =
href=3D"http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt" =
target=3D"_blank">http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt=
</a>&gt;</div><div><br></div><div><span =
style=3D"font-family:arial,sans-serif;font-size:13px">So my read of the =
situation is much less dire than James's. &nbsp;As I understand it, the =
upshot of the initial coordination discussions is that there's not a =
single, clear "RTCWEB+ECRIT" story. &nbsp;Instead, there are a few ways =
you can put them together. &nbsp;In the short run, without upgrading =
PSAPs, RTCWEB VoIP services can bridge RTCWEB signaling to =
ECRIT-compliant SIP, either at the server, or at the client using =
something like SIP-over-WebSockets. &nbsp;In the long run, PSAPs can =
just advertise an RTCWEB service like they would advertise a SIP service =
today (in LoST). &nbsp;Neither of these is incompatible with RTCWEB or =
ECRIT as they're being specified today.</span><br>


</div><div><span =
style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></div><di=
v><span style=3D"font-family:arial,sans-serif;font-size:13px">I expect =
there are probably some ECRIT considerations that aren't naturally =
supported in RTCWEB. &nbsp;Things like real-time text come to mind. =
&nbsp;However, it doesn't seem to me that there's gross =
incompatibility.</span></div>


<div><span =
style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></div><di=
v><span =
style=3D"font-family:arial,sans-serif;font-size:13px">--Richard</span></di=
v><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>


</span></div><div><span =
style=3D"font-family:arial,sans-serif;font-size:13px"><br></span></div></d=
iv><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, =
May 25, 2013 at 10:18 AM, John C Klensin <span dir=3D"ltr">&lt;<a =
href=3D"mailto:john-ietf@jck.com" =
target=3D"_blank">john-ietf@jck.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
--On Saturday, May 25, 2013 10:10 +0300 Jari Arkko<br>
&lt;<a href=3D"mailto:jari.arkko@piuha.net" =
target=3D"_blank">jari.arkko@piuha.net</a>&gt; wrote:<br>
<br>
&gt;...<br>
<div>&gt; I didn't know about the details of the emergency<br>
&gt; communications situation. But it is always difficult to<br>
&gt; balance getting something out early vs. complete. I know how<br>
&gt; much pressure there is on the working groups to keep up with<br>
&gt; things actually happening in the browsers and organisations<br>
&gt; setting up to use this technology. Do you think the retrofit<br>
&gt; will be problematic, and do you have a specific suggestion<br>
&gt; about what should be included today?<br>
<br>
</div>Jari,<br>
<br>
James will probably have a different answer and perspective, but<br>
I suggest that retrofits of security-sensitive features are so<br>
often problematic to make "always" not much of an exaggeration.<br>
<br>
I don't think there is any general solution to the "early vs.<br>
complete" tradeoff [1], nor, as long as we keep trying to deal<br>
with things as collections of disconnected pieces rather than<br>
systems, to the issues created by WGs with significant overlaps<br>
in either scope or technology. &nbsp;What I think we can do is to be<br>
particularly vigilant to be sure that the two WGs are tracking<br>
and frequently reviewing each other's work. &nbsp; At least RTCWEB<br>
and ECRIT are in the same area, which should make that<br>
coordination easier than it might be otherwise.<br>
<br>
&nbsp; &nbsp;john<br>
<br>
<br>
[1] Watch for a note about this that I've been trying to<br>
organize for about two weeks and hope to finish and post this<br>
weekend.<br>
<br>
<br>
<br>
</blockquote></div><br></div>
=
</blockquote></div><br></div></div></blockquote></div><br></div></div></di=
v>
</blockquote></div><br></body></html>=

--Apple-Mail=_88DEBCE7-F6B7-46EC-ABE8-C722E46CBF99--

From abdussalambaryun@gmail.com  Mon May 27 11:20:37 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D664521F8AD8 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 11:20:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0WlULAqCQHsJ for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 11:20:37 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 546C321F8A68 for <ietf@ietf.org>; Mon, 27 May 2013 11:20:33 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so6968747pbb.5 for <ietf@ietf.org>; Mon, 27 May 2013 11:20:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=c9M3JPzwAND7KPcb8Q4qhkP+bfUhzlOIS0mxYxqygU4=; b=YcqiamJG9rKrTxlxR32lEwIgaPahicuzvBMAvhk4QIxlcXIa4w2TvLrytaN3GnFwrd J04SYA6VK2zjutZYi5eZ+33MM+xyt5YOVgs0phLZFt5XNUpO0bulM2Yjrc9cw0bFCOEa 6ikdmtED9lzZC3kQjM/t6YXmJ8UK5zgPjF89CIU5SscOQC2WwbVEUBUK/Mf0frfJdR6P aY/tV5LylJsc14wImmbQTcQvgOnGhXVp8YxO5yMjzeOSJRSiliWiVvlLcwT7WdEDmFUs fTJk/DRnCJeE2PRCMP+2Nn8+EMHWObymPv/lJ5mElcWrmuhmwdPghHHoHfaaZ4aj/Tgn jlWQ==
MIME-Version: 1.0
X-Received: by 10.66.158.234 with SMTP id wx10mr30772787pab.43.1369678829831;  Mon, 27 May 2013 11:20:29 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 27 May 2013 11:20:29 -0700 (PDT)
In-Reply-To: <CAN1bDFw3p5MoUiRDNdo-_Eo7xxueg1rdQ_k+DRdUFLRSZSN2cg@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CAN1bDFw3p5MoUiRDNdo-_Eo7xxueg1rdQ_k+DRdUFLRSZSN2cg@mail.gmail.com>
Date: Mon, 27 May 2013 20:20:29 +0200
Message-ID: <CADnDZ89OGoh7YbKNMwY4fqocDS9UJT_BohTMB=ne=X+kZXCk+Q@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jiazi YI <yi.jiazi@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 18:20:38 -0000

Hi,
Reviews at this stage don't need supports from WG when it is in the
IETF Last Call, the comments are sent as per request of iesg.

AB

On 5/27/13, Jiazi YI <yi.jiazi@gmail.com> wrote:
> Hi,
>
> I think those comments have been addressed/answered in my previous reply
>
>   http://www.ietf.org/mail-archive/web/manet/current/msg15274.html
>
> I didn't see the support of your comments from other WG participants.
>
> best
>
> Jiazi
>
>
> 2013/5/27 Abdussalam Baryun <abdussalambaryun@gmail.com>
>
>> Reply to your request dated 24/05/2013
>>
>> Draft Reviewed By: Abdussalam Baryun (AB)    Dated:27/05/2013
>> Reviewer Comment A1: Previous comments in WGLC
>> +++++++++++++++++++++++++++++++++++++++
>>
>> Related to your request below please read my previous review comments
>> [1] and I will continue with additional messages/comments.
>>
>> [1] http://www.ietf.org/mail-archive/web/manet/current/msg15254.html
>>
>> Regards
>> AB
>>
>> On 5/24/13, The IESG <iesg-secretary@ietf.org> wrote:
>> >
>> > The IESG has received a request from the Mobile Ad-hoc Networks WG
>> > (manet) to consider the following document:
>> > - 'Security Threats for NHDP'
>> >   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
>> >
>> > The IESG plans to make a decision in the next few weeks, and solicits
>> > final comments on this action. Please send substantive comments to the
>> > ietf@ietf.org mailing lists by 2013-06-06. 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 analyses common security threats of the Neighborhood
>> >    Discovery Protocol (NHDP), and describes their potential impacts on
>> >    MANET routing protocols using NHDP.
>> >
>> > The file can be obtained via
>> > http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/
>> >
>> > IESG discussion can be tracked via
>> >
>> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/ballot/
>> >
>> >
>> > No IPR declarations have been submitted directly on this I-D.
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www.ietf.org/mailman/listinfo/manet
>> >
>>
>

From abdussalambaryun@gmail.com  Mon May 27 11:39:08 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87A7121F9672; Mon, 27 May 2013 11:39:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRBGfhkzBrvw; Mon, 27 May 2013 11:39:04 -0700 (PDT)
Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by ietfa.amsl.com (Postfix) with ESMTP id 736DD21F95EC; Mon, 27 May 2013 11:39:04 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id kp6so7051549pab.7 for <multiple recipients>; Mon, 27 May 2013 11:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lFTSGQlKi5B3iXSScjgUJYfrzmmwS7jymwB/V7Vc/ig=; b=QHXadR9Tl+6m5IA2Is4lLiuPupQYJP6nCRf2GP2t0saEcVV0u8HHoIAfGkaQictTRV 8dG00LdiZhWMm6AcPRxHs8z91OQOWtG/Blwul6+fOJ/q8o5Xr74kVIBbAXMjlUh6NIo9 78EoY+lep2GebeHPVsXe+Xb7Mw2UO+DmyAHPnRU8fLl6asslUEon14fIONFxYpcUIzZ1 uZDZL2b0RtOI0Pry79avp7jKFvjQ25WdtSyiO7WLw4AZbq+gKMQeJPkLx8ozgJk9VhHk QQdejiomNsB4o3HMr4IqYfw8gkuevNdIzW5WKE5IXHfLLwXRhCAz7eZEe5HccQsjrXXS xBGQ==
MIME-Version: 1.0
X-Received: by 10.66.145.98 with SMTP id st2mr31386943pab.24.1369679944218; Mon, 27 May 2013 11:39:04 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Mon, 27 May 2013 11:39:04 -0700 (PDT)
In-Reply-To: <CAN1bDFw3p5MoUiRDNdo-_Eo7xxueg1rdQ_k+DRdUFLRSZSN2cg@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CAN1bDFw3p5MoUiRDNdo-_Eo7xxueg1rdQ_k+DRdUFLRSZSN2cg@mail.gmail.com>
Date: Mon, 27 May 2013 20:39:04 +0200
Message-ID: <CADnDZ88tHdd9jJ11E4OoU+of7a=HsA+mBnxVG2_J_o5aSSzO6A@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jiazi YI <yi.jiazi@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 18:39:08 -0000

On 5/27/13, Jiazi YI <yi.jiazi@gmail.com> wrote:
> Hi,
>
> I think those comments have been addressed/answered in my previous reply
>
>   http://www.ietf.org/mail-archive/web/manet/current/msg15274.html
>
> I didn't see the support of your comments from other WG participants.

I also didn't see objection of my comments from the WG. I also didn't
see support of your reply from the WG.  (WG decisions are
WG-rough-consensus, not the editors opinion). If there was WG
objection then I will report that in my reviews to IESG as
information.

AB

From d3e3e3@gmail.com  Mon May 27 12:14:10 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 333D121F96E8 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 12:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pNF-XxbEVvl8 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 12:14:09 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 730AD21F96E5 for <ietf@ietf.org>; Mon, 27 May 2013 12:14:09 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id tb18so8263495obb.17 for <ietf@ietf.org>; Mon, 27 May 2013 12:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RaIJ3tK9DOfFH2s6bscNjvZwvuHzb/RBeh5YfTFYrbA=; b=X4IzS+X+Ko+8i0z+kupZ1DCeeO6v4eoKtDbA3PegsXLRA0eAMkOtQDvrvyq6Pcecp+ 0oDHKRq8/b7g1T6sq+zPyntz1EwCuc3YEqmhoGYQaHfTMGnFQrDYQODMQPnBDacg8QAM HvGD7uI9tXcZvJENYoGdBObMEl5XfL/qWAlyO3brFo952OK1eLW2vlNOtIt8SC9nwUgK vXTq6dML6SA0qSv4h3TD/qHFTMY7xodO2mH8rJ+Y3CcRoXRr3z/7FinQqQvt18DjG3hu qam8bfdzTCgEmEUkZbAaIa4zGJKA5QHdeyVijU8jL9uvoltbWemcoPzBFHiIpyj/vVcR x00w==
X-Received: by 10.182.130.138 with SMTP id oe10mr18677089obb.90.1369682049029;  Mon, 27 May 2013 12:14:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.100.231 with HTTP; Mon, 27 May 2013 12:13:48 -0700 (PDT)
In-Reply-To: <20130507110739.12847.4273.idtracker@ietfa.amsl.com>
References: <20130507110739.12847.4273.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 27 May 2013 15:13:48 -0400
Message-ID: <CAF4+nEG17915KyBM_5KSEZSD7Lc43pifRLY4S9hVMBhVz1PT2A@mail.gmail.com>
Subject: Re: Last Call: <draft-eastlake-rfc5342bis-02.txt> (IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters) 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: Mon, 27 May 2013 19:14:10 -0000

The first part of Section 2.1 should have a sentence added like "An
RRTYPE code has been assigned so 48-bit MAC addresses can be stored
using the DNS protocol." with an appropriate reference. A similar
sentence for 64-bit MAC addresses should be added to the first part of
Section 2.2.

The lists of Ethertypes in Appendix B should be brought up to date.

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


On Tue, May 7, 2013 at 7:07 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'IANA Considerations and IETF Protocol and Documentation Usage for IEEE
>    802 Parameters'
>   <draft-eastlake-rfc5342bis-02.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-06-04. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    Some IETF protocols make use of Ethernet frame formats and IEEE 802
>    parameters.  This document discusses some use of such parameters in
>    IETF protocols, specifies IANA considerations for assignment of
>    points under the IANA OUI (Organizationally Unique Identifier),
>    provides some values for use in documentation, and obsoletes RFC
>    5342.
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-eastlake-rfc5342bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-eastlake-rfc5342bis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>

From melinda.shore@gmail.com  Mon May 27 12:19:59 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C86A21F9626 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 12:19:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.05
X-Spam-Level: 
X-Spam-Status: No, score=-2.05 tagged_above=-999 required=5 tests=[AWL=1.550,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71EVzn9D4EHo for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 12:19:53 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id D01E221F8F12 for <ietf@ietf.org>; Mon, 27 May 2013 12:19:53 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id wp1so4523028pac.31 for <ietf@ietf.org>; Mon, 27 May 2013 12:19:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ij0MXv/bA6QI2indgCgUAZbewRP9pjIZo5MWu7UKjx4=; b=ycsk08wQMM5cn8FA/YdFngRAfQyG14QU55kbCknyibVcqiTjWovL06PmvNLcj/fsTr DubKFiT9dJI6X0fDtVz/Yeu1b8nzacPcpstoLqFmod9tTJvbElNUug5H2TBCYMs1/I4e f0RBfs6eVnBKldW0I/+2kRvZbk39yAym+TiqbTCeTtIgTseFoAegpWZoxHchGLs/RmSC fICvsGphs5tLPVeX/wf5G8/Ez/6RmclBymYwXZ2xf+hOmRvTg/1w2YGVglGn+ObbSHQJ HX6aQJkstXE6HZuapBF919DLwF8hA6qd8PSgXxFxlOo1F1M8JvwG2mlJxwuGvdCyDehE vYjg==
X-Received: by 10.66.87.5 with SMTP id t5mr31807946paz.169.1369682393441; Mon, 27 May 2013 12:19:53 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id yj2sm29563790pbb.40.2013.05.27.12.19.51 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 12:19:52 -0700 (PDT)
Message-ID: <51A3B1D5.3010604@gmail.com>
Date: Mon, 27 May 2013 11:19:49 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com> <CAN1bDFw3p5MoUiRDNdo-_Eo7xxueg1rdQ_k+DRdUFLRSZSN2cg@mail.gmail.com> <CADnDZ88tHdd9jJ11E4OoU+of7a=HsA+mBnxVG2_J_o5aSSzO6A@mail.gmail.com>
In-Reply-To: <CADnDZ88tHdd9jJ11E4OoU+of7a=HsA+mBnxVG2_J_o5aSSzO6A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 19:19:59 -0000

On 5/27/13 10:39 AM, Abdussalam Baryun wrote:
> I also didn't see objection of my comments from the WG. I also didn't
> see support of your reply from the WG.  (WG decisions are
> WG-rough-consensus, not the editors opinion).

Chairs call consensus.



From cb.list6@gmail.com  Mon May 27 12:29:22 2013
Return-Path: <cb.list6@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A541621F96FE for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 12:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tHYc1abU1UvD for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 12:29:21 -0700 (PDT)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E87C621F96FD for <ietf@ietf.org>; Mon, 27 May 2013 12:29:20 -0700 (PDT)
Received: by mail-we0-f175.google.com with SMTP id p60so4670394wes.6 for <ietf@ietf.org>; Mon, 27 May 2013 12:29:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DYINxVrZZkpzzHusttsTbzoL6hrJREvzbbXfwIiztbo=; b=eUmp9+J+jQjHnfBOPoH5avCIoyKYYN7P45BPf4PrxSNqJLaXVMaNQpPoCDRZnwA3o5 Is+2g+g801b/N6aUvKhzVBQt8JQFx0sE2q9csCPYnsnG1wp1PkrMOCqICNUU8LDJRVNe VP9pkDziQboJuN7myY9y4nsSDMzkXpWk0ES/XYpCKXn/OIWTFjJI/4luH29JgcCafYIf 1ihZEV4tOeN1SFwsafmVDkcQqgXVUn373Pbl2qBftn0SNa9wzd4oZVhvatpEax7myRiw asMAWyhXKwTJy9AwZ8mFYbG7zpS6bHRd8Lj88OJdjpqRRHiTXL4p+mPxfq+TQsTO7Mmz 7FMw==
MIME-Version: 1.0
X-Received: by 10.194.58.180 with SMTP id s20mr9968675wjq.58.1369682959367; Mon, 27 May 2013 12:29:19 -0700 (PDT)
Received: by 10.194.56.231 with HTTP; Mon, 27 May 2013 12:29:19 -0700 (PDT)
Received: by 10.194.56.231 with HTTP; Mon, 27 May 2013 12:29:19 -0700 (PDT)
In-Reply-To: <ADAA4A8A-E5BD-4DF1-B9E1-270A1780998C@cs.columbia.edu>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com> <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com> <94B83A14-1FFE-450C-BAFF-0EC03E425641@cs.columbia.edu> <CAL02cgQHCyPM-movR8MTNYYFe8utGP8PU8YSa8VtWYh8MDFR1A@mail.gmail.com> <ADAA4A8A-E5BD-4DF1-B9E1-270A1780998C@cs.columbia.edu>
Date: Mon, 27 May 2013 12:29:19 -0700
Message-ID: <CAD6AjGT7VTUGVQf8ZpM9_UD672uASf1rooFBCfvtoNP2QzpW-w@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: "cb.list6" <cb.list6@gmail.com>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Content-Type: multipart/alternative; boundary=047d7b86cb683f878404ddb82a1d
Cc: John C Klensin <john-ietf@jck.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, 27 May 2013 19:29:22 -0000

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

On May 27, 2013 10:56 AM, "Henning Schulzrinne" <hgs@cs.columbia.edu> wrote:
>
> Agreed - this is not so much about standards, but developer awareness. If
we write any "how to" or similar informational documents, they should
probably contain that type of discussion.
>
> There is a browser aspect, however: Right now, users only have a binary
choice about location disclosure, even though I suspect many users would be
fine with "location disclosure for 911 only", not "disclose my fine-grained
location for any purpose you like".
>

WebRTC is just a website in many respects.

I would like to see telcos get out of this starngely engineered and
regulated world and just be a "dumb pipe" for smart emergency services

And, in its place, the relevant emergergency response stakeholders
deblvelop 911.gov and when i need help i go to 911.gov and have a webrtc
call to my relevant emergency agency, or sip://help@911.gov .

And like  root CA certs, the location disclosure is already approved by the
browser vendors (giving user choices is not advised in emergencies)

CB
> On May 27, 2013, at 1:51 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
>> Even for location delivery, there's not that much to say at the
standards layer.
>>
>> For *delivery*, the story is the same as with signaling.  Either the
RTCWeb VoIP service can translate the location information to comply with
RFC 6442, or the PSAP can just build a web app that collects it however it
likes.
>>
>> For *determination*, it's about the browser.  You can do browser-based
geolocation today, to "OK" quality.  Or the browser could implement the
GEOPRIV protocols to benefit from network-provided location.
>>
>> All that's about implementation/deployment though.  I don't really see
any new standards there.
>>
>> --Richard
>>
>>
>>
>> On Mon, May 27, 2013 at 12:19 PM, Henning Schulzrinne <
hgs@cs.columbia.edu> wrote:
>>>
>>> The most difficult part for any emergency calling system is location
delivery. WebRTC probably doesn't have much impact on emergency calls if
all the calls traverse a server of some kind and if the caller location can
be looked up based on caller IP addresses, but once you have the end system
involved in location determination (e.g., for mobile devices or for
DHCP-delivered location), it has to know when a call is an emergency call
as you otherwise end up providing location for every call, which is
non-ideal from a privacy and battery perspective.
>>>
>>> At least in the US, many of the WebRTC services would be considered
"interconnected VoIP", so they are indeed subject to 911 obligations.
>>>
>>> Henning
>>>
>>> On May 26, 2013, at 3:57 PM, Richard Barnes <rlb@ipv.sx> wrote:
>>>
>>>> Indeed, there has already been some coordination between the groups,
going back about a year:
>>>> <http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf>
>>>> <http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt>
>>>>
>>>> So my read of the situation is much less dire than James's.  As I
understand it, the upshot of the initial coordination discussions is that
there's not a single, clear "RTCWEB+ECRIT" story.  Instead, there are a few
ways you can put them together.  In the short run, without upgrading PSAPs,
RTCWEB VoIP services can bridge RTCWEB signaling to ECRIT-compliant SIP,
either at the server, or at the client using something like
SIP-over-WebSockets.  In the long run, PSAPs can just advertise an RTCWEB
service like they would advertise a SIP service today (in LoST).  Neither
of these is incompatible with RTCWEB or ECRIT as they're being specified
today.
>>>>
>>>> I expect there are probably some ECRIT considerations that aren't
naturally supported in RTCWEB.  Things like real-time text come to mind.
 However, it doesn't seem to me that there's gross incompatibility.
>>>>
>>>> --Richard
>>>>
>>>>
>>>>
>>>>
>>>> On Sat, May 25, 2013 at 10:18 AM, John C Klensin <john-ietf@jck.com>
wrote:
>>>>>
>>>>>
>>>>>
>>>>> --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
>>>>> <jari.arkko@piuha.net> wrote:
>>>>>
>>>>> >...
>>>>> > I didn't know about the details of the emergency
>>>>> > communications situation. But it is always difficult to
>>>>> > balance getting something out early vs. complete. I know how
>>>>> > much pressure there is on the working groups to keep up with
>>>>> > things actually happening in the browsers and organisations
>>>>> > setting up to use this technology. Do you think the retrofit
>>>>> > will be problematic, and do you have a specific suggestion
>>>>> > about what should be included today?
>>>>>
>>>>> Jari,
>>>>>
>>>>> James will probably have a different answer and perspective, but
>>>>> I suggest that retrofits of security-sensitive features are so
>>>>> often problematic to make "always" not much of an exaggeration.
>>>>>
>>>>> I don't think there is any general solution to the "early vs.
>>>>> complete" tradeoff [1], nor, as long as we keep trying to deal
>>>>> with things as collections of disconnected pieces rather than
>>>>> systems, to the issues created by WGs with significant overlaps
>>>>> in either scope or technology.  What I think we can do is to be
>>>>> particularly vigilant to be sure that the two WGs are tracking
>>>>> and frequently reviewing each other's work.   At least RTCWEB
>>>>> and ECRIT are in the same area, which should make that
>>>>> coordination easier than it might be otherwise.
>>>>>
>>>>>    john
>>>>>
>>>>>
>>>>> [1] Watch for a note about this that I've been trying to
>>>>> organize for about two weeks and hope to finish and post this
>>>>> weekend.
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>

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

<p dir=3D"ltr"><br>
On May 27, 2013 10:56 AM, &quot;Henning Schulzrinne&quot; &lt;<a href=3D"ma=
ilto:hgs@cs.columbia.edu">hgs@cs.columbia.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; Agreed - this is not so much about standards, but developer awareness.=
 If we write any &quot;how to&quot; or similar informational documents, the=
y should probably contain that type of discussion.<br>
&gt;<br>
&gt; There is a browser aspect, however: Right now, users only have a binar=
y choice about location disclosure, even though I suspect many users would =
be fine with &quot;location disclosure for 911 only&quot;, not &quot;disclo=
se my fine-grained location for any purpose you like&quot;.<br>

&gt;<br></p>
<p dir=3D"ltr">WebRTC is just a website in many respects.=A0 </p>
<p dir=3D"ltr">I would like to see telcos get out of this starngely enginee=
red and regulated world and just be a &quot;dumb pipe&quot; for smart emerg=
ency services</p>
<p dir=3D"ltr">And, in its place, the relevant emergergency response stakeh=
olders deblvelop <a href=3D"http://911.gov">911.gov</a> and when i need hel=
p i go to <a href=3D"http://911.gov">911.gov</a> and have a webrtc call to =
my relevant emergency agency, or sip://<a href=3D"mailto:help@911.gov">help=
@911.gov</a> . </p>

<p dir=3D"ltr">And like=A0 root CA certs, the location disclosure is alread=
y approved by the browser vendors (giving user choices is not advised in em=
ergencies)</p>
<p dir=3D"ltr">CB<br>
&gt; On May 27, 2013, at 1:51 PM, Richard Barnes &lt;rlb@ipv.sx&gt; wrote:<=
br>
&gt;<br>
&gt;&gt; Even for location delivery, there&#39;s not that much to say at th=
e standards layer.<br>
&gt;&gt;<br>
&gt;&gt; For *delivery*, the story is the same as with signaling. =A0Either=
 the RTCWeb VoIP service can translate the location information to comply w=
ith RFC 6442, or the PSAP can just build a web app that collects it however=
 it likes.<br>

&gt;&gt;<br>
&gt;&gt; For *determination*, it&#39;s about the browser. =A0You can do bro=
wser-based geolocation today, to &quot;OK&quot; quality. =A0Or the browser =
could implement the GEOPRIV protocols to benefit from network-provided loca=
tion.<br>

&gt;&gt;<br>
&gt;&gt; All that&#39;s about implementation/deployment though. =A0I don&#3=
9;t really see any new standards there.<br>
&gt;&gt;<br>
&gt;&gt; --Richard<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Mon, May 27, 2013 at 12:19 PM, Henning Schulzrinne &lt;<a href=
=3D"mailto:hgs@cs.columbia.edu">hgs@cs.columbia.edu</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The most difficult part for any emergency calling system is lo=
cation delivery. WebRTC probably doesn&#39;t have much impact on emergency =
calls if all the calls traverse a server of some kind and if the caller loc=
ation can be looked up based on caller IP addresses, but once you have the =
end system involved in location determination (e.g., for mobile devices or =
for DHCP-delivered location), it has to know when a call is an emergency ca=
ll as you otherwise end up providing location for every call, which is non-=
ideal from a privacy and battery perspective.<br>

&gt;&gt;&gt;<br>
&gt;&gt;&gt; At least in the US, many of the WebRTC services would be consi=
dered &quot;interconnected VoIP&quot;, so they are indeed subject to 911 ob=
ligations.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Henning<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On May 26, 2013, at 3:57 PM, Richard Barnes &lt;rlb@ipv.sx&gt;=
 wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Indeed, there has already been some coordination between t=
he groups, going back about a year:<br>
&gt;&gt;&gt;&gt; &lt;<a href=3D"http://tools.ietf.org/agenda/84/slides/slid=
es-84-ecrit-0.pdf">http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0=
.pdf</a>&gt;<br>
&gt;&gt;&gt;&gt; &lt;<a href=3D"http://tools.ietf.org/id/draft-aboba-rtcweb=
-ecrit-00.txt">http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt</a>=
&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; So my read of the situation is much less dire than James&#=
39;s. =A0As I understand it, the upshot of the initial coordination discuss=
ions is that there&#39;s not a single, clear &quot;RTCWEB+ECRIT&quot; story=
. =A0Instead, there are a few ways you can put them together. =A0In the sho=
rt run, without upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB sig=
naling to ECRIT-compliant SIP, either at the server, or at the client using=
 something like SIP-over-WebSockets. =A0In the long run, PSAPs can just adv=
ertise an RTCWEB service like they would advertise a SIP service today (in =
LoST). =A0Neither of these is incompatible with RTCWEB or ECRIT as they&#39=
;re being specified today.<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I expect there are probably some ECRIT considerations that=
 aren&#39;t naturally supported in RTCWEB. =A0Things like real-time text co=
me to mind. =A0However, it doesn&#39;t seem to me that there&#39;s gross in=
compatibility.<br>

&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; --Richard<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, May 25, 2013 at 10:18 AM, John C Klensin &lt;<a hr=
ef=3D"mailto:john-ietf@jck.com">john-ietf@jck.com</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko<br>
&gt;&gt;&gt;&gt;&gt; &lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko=
@piuha.net</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &gt;...<br>
&gt;&gt;&gt;&gt;&gt; &gt; I didn&#39;t know about the details of the emerge=
ncy<br>
&gt;&gt;&gt;&gt;&gt; &gt; communications situation. But it is always diffic=
ult to<br>
&gt;&gt;&gt;&gt;&gt; &gt; balance getting something out early vs. complete.=
 I know how<br>
&gt;&gt;&gt;&gt;&gt; &gt; much pressure there is on the working groups to k=
eep up with<br>
&gt;&gt;&gt;&gt;&gt; &gt; things actually happening in the browsers and org=
anisations<br>
&gt;&gt;&gt;&gt;&gt; &gt; setting up to use this technology. Do you think t=
he retrofit<br>
&gt;&gt;&gt;&gt;&gt; &gt; will be problematic, and do you have a specific s=
uggestion<br>
&gt;&gt;&gt;&gt;&gt; &gt; about what should be included today?<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Jari,<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; James will probably have a different answer and perspe=
ctive, but<br>
&gt;&gt;&gt;&gt;&gt; I suggest that retrofits of security-sensitive feature=
s are so<br>
&gt;&gt;&gt;&gt;&gt; often problematic to make &quot;always&quot; not much =
of an exaggeration.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; I don&#39;t think there is any general solution to the=
 &quot;early vs.<br>
&gt;&gt;&gt;&gt;&gt; complete&quot; tradeoff [1], nor, as long as we keep t=
rying to deal<br>
&gt;&gt;&gt;&gt;&gt; with things as collections of disconnected pieces rath=
er than<br>
&gt;&gt;&gt;&gt;&gt; systems, to the issues created by WGs with significant=
 overlaps<br>
&gt;&gt;&gt;&gt;&gt; in either scope or technology. =A0What I think we can =
do is to be<br>
&gt;&gt;&gt;&gt;&gt; particularly vigilant to be sure that the two WGs are =
tracking<br>
&gt;&gt;&gt;&gt;&gt; and frequently reviewing each other&#39;s work. =A0 At=
 least RTCWEB<br>
&gt;&gt;&gt;&gt;&gt; and ECRIT are in the same area, which should make that=
<br>
&gt;&gt;&gt;&gt;&gt; coordination easier than it might be otherwise.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; =A0 =A0john<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; [1] Watch for a note about this that I&#39;ve been try=
ing to<br>
&gt;&gt;&gt;&gt;&gt; organize for about two weeks and hope to finish and po=
st this<br>
&gt;&gt;&gt;&gt;&gt; weekend.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;<br>
</p>

--047d7b86cb683f878404ddb82a1d--

From tjc@ecs.soton.ac.uk  Mon May 27 14:13:37 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9738D21F8904 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=0.699,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBxcZPRhZInM for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:13:37 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id BBC0C21F8900 for <ietf@ietf.org>; Mon, 27 May 2013 14:13:36 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4RLDXkM029994; Mon, 27 May 2013 22:13:33 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r4RLDXkM029994
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1369689213; bh=C7yGpmC9quQIOAI2riEhqL03Yuw=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=CGRF9dsJPj0PYm2w/MKIE/+vCSyl97bJuGmNetT+69CjwNmvTyspgeuL3hTCyumLV nHQpnMbciNLwLJgGFKZ5vn9dg/TAoofbmSnQ8mO59OC0KoY1aU6N3qGU0f8th+XdYv V5Pb8Kz20Mm33ei6pC/VddSPxJLHjJPAmNdlPEv0=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p4QMDX0430649863VA ret-id none; Mon, 27 May 2013 22:13:33 +0100
Received: from [192.168.1.110] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r4RLDO9j020385 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 27 May 2013 22:13:29 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: financial fun with an IETF Meeting in South America
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <alpine.BSF.2.00.1305271133490.7155@joyce.lan>
Date: Mon, 27 May 2013 22:13:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|fb52c9a027e15d45ff2873f7fd4b88bcp4QMDX03tjc|ecs.soton.ac.uk|7B19A70E-556C-4473-9686-C3501F20F6E5@ecs.soton.ac.uk>
References: <20130527041505.7301.qmail@joyce.lan> <A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk> <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk> <alpine.BSF.2.00.1305271133490.7155@joyce.lan> <7B19A70E-556C-4473-9686-C3501F20F6E5@ecs.soton.ac.uk>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1503)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p4QMDW043064986300; tid=p4QMDX0430649863VA; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r4RLDXkM029994
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 27 May 2013 21:13:37 -0000

On 27 May 2013, at 16:37, John R Levine <johnl@taugh.com> wrote:

>> Is this above advice from Tripadvisor correct?
>=20
> I believe so, but when I was there a few years ago for the ICANN =
meeting, excess cash was not a problem.  It wasn't hard to estimate how =
much cash I'd need, and whatever was left I spent at the airport.  The =
wine they drink in Argentina is often better than the stuff they send to =
the UK (which isn't bad) and much cheaper.  Take some home in your =
suitcase, even if you have to pay duty it's a bargain.

It's not necessarily so easy over the course of seven days. But I guess =
we could also just give all our leftover cash to a deserving Argentinian =
IETF attendee.  Fernando may like that approach :)

> This still doesn't mean I think a meeting in South America is a good =
idea, though.  See other messages.

I think Jari's views are spot on. There's a bigger picture question to =
address, regardless of the meeting venues, and not just for that region.=20=


Tim



From dwm@xpasc.com  Mon May 27 14:24:27 2013
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3974421F8EAE for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CMPiLEOJg8Fi for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:24:21 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8CF21F8EC2 for <ietf@ietf.org>; Mon, 27 May 2013 14:24:21 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id BA3D33F75C for <ietf@ietf.org>; Mon, 27 May 2013 21:24:20 +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 r4RLOKmO028773 for <ietf@ietf.org>; Mon, 27 May 2013 14:24:20 -0700
Date: Mon, 27 May 2013 14:24:20 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Issues in wider geographic participation
In-Reply-To: <51A2F9D2.3090606@gmail.com>
Message-ID: <alpine.LRH.2.01.1305271422030.26867@egate.xpasc.com>
References: <20130527055257.7635.qmail@joyce.lan> <51A2F9D2.3090606@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.87-g7939dec
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 21:24:27 -0000

On Sun, 26 May 2013, Melinda Shore wrote:

> It also seems unlikely to me that that million dollars is otherwise
> available.
> 
> I like the idea of setting up a remote participation center (doubly-
> so if one or more very experienced IETFers who spoke the local language
> could be on-site) but it seems very unlikely to me that, say, a Frobnitz
> Networks employee would be able to convinced Frobnitz Networks to send
> the $400 saved by not going to Buenos Aires to such an undertaking.

Your are likely right, but the discussion hasn't included the negative
impression on Frobnitz management re. the added expense.

Just because the money can't be 'recovered' for other use, doesn't
make it rational to spend it.

From scott.brim@gmail.com  Mon May 27 14:26:30 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3C121F8609 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:26:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.499, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wAPR7KHd7dTJ for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:26:25 -0700 (PDT)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5D53321F85E6 for <ietf@ietf.org>; Mon, 27 May 2013 14:26:25 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j6so9300262oag.32 for <ietf@ietf.org>; Mon, 27 May 2013 14:26:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=arP+WepfdTd5A928GKV7HYp5agjrJN2qdMgrsOKcYcc=; b=SAsRNeEVf0eUPvwIWHWYhsfqLEBbx4QofxmDV7M2OpUvJkTFGm3Pf1XyNtIs5RujB3 8fN/a5Y5ywLUp4xsjZjqr/FfBmCwgSeIGIpJJ+fPwydY7/KESdPu5vO+1zbllLPtaSj3 8T3gijfgcMih9Ivw4SKWZSDwJgq8wgC0OytJ9NYIOm1YFwfpmwwgVIkDJf/cu3Qb1jZL MaFwDkxKBsz/5ze6DGxcqYsFpao3hR/SvI6BLiqaLEHXIxbMFfCAIeRjMi+Lv5uhUgn2 w7FcZW7wSeRMqfId2uPuuRIdOW9HtUcyJ6R/Mkzw1x7HDhBVCroCT2R/XSi/3bkjKeQi +1DA==
X-Received: by 10.60.79.231 with SMTP id m7mr19701824oex.105.1369689984772; Mon, 27 May 2013 14:26:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.114.193 with HTTP; Mon, 27 May 2013 14:26:03 -0700 (PDT)
In-Reply-To: <51A38BC3.9060002@gmail.com>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <51A34C9D.3020406@dcrocker.net> <7BBE0F33-9113-4F1C-81CC-F932876FF913@lacnic.net> <AE47309F-C7C1-4E82-9A14-68B2A2B7EBBB@gmail.com> <51A388A9.6080206@lacnic.net> <alpine.BSF.2.00.1305271229010.7155@joyce.lan> <51A38BC3.9060002@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 27 May 2013 17:26:03 -0400
Message-ID: <CAPv4CP9=eS+ORmvrF6LioLFQcJspnSoa-sjSnQWwBHv3HkecNg@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e01184b0efebce804ddb9ccc0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 21:26:30 -0000

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

I would prefer that people come to the IETF because they have a problem and
they are looking for ways to solve it ... as opposed to wanting to work
with the IETF for some reason and looking for something "the IETF" wants
them to work on.  The former feels like engineering, the latter like
professional standards going.  Therefore, if someone says they are looking
for a problem to work on, I ask them to bring a problem with them.

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

I would prefer that people come to the IETF because they have a problem and=
 they are looking for ways to solve it ... as opposed to wanting to work wi=
th the IETF for some reason and looking for something &quot;the IETF&quot; =
wants them to work on. =A0The former feels like engineering, the latter lik=
e professional standards going. =A0Therefore, if someone says they are look=
ing for a problem to work on, I ask them to bring a problem with them.

--089e01184b0efebce804ddb9ccc0--

From scott.brim@gmail.com  Mon May 27 14:31:41 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A30E221F8F12 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:31:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIkN4yokOK+P for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:31:41 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 3588221F8EE8 for <ietf@ietf.org>; Mon, 27 May 2013 14:31:41 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id up14so1853350obb.14 for <ietf@ietf.org>; Mon, 27 May 2013 14:31:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OQX/V/VNo2SEpM4ro9rlB0WUW16vVLdAUh0aCmWKQRk=; b=FDswpOET916EvYDPNFIRUwLKNCVVGm1rXH9BLOXTLwBAe9NooXh/HzmpYiBRUP4JIs ifQZ8NBxLolfrlE8cntds6RPCajU8vyEidMHA4D3JFLtWWu/MLJ2Gt2foBhhp9bs+twR HgspXnezpHSSDdFylbkjAsh0G8yZQZEz16u+yDBZvC5BDCxG1JCojztihD2nDKuSNyWB ZYXGRhgwXH614T1c8iyZ9lLqyeISYgDr6VapwrnwwM15mlt2yHvzb8/JH5EGkEttHyOW AWlzR7bZxRHxqJc88tC48iy7qA8PHVJghok0lCoeWbnlydEWJH4W4/9NBmKdkaZtqdiq ZKoA==
X-Received: by 10.182.134.231 with SMTP id pn7mr18807408obb.11.1369690300783;  Mon, 27 May 2013 14:31:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.114.193 with HTTP; Mon, 27 May 2013 14:31:19 -0700 (PDT)
In-Reply-To: <51A38CB2.6030102@braga.eti.br>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br> <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com> <51A38CB2.6030102@braga.eti.br>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 27 May 2013 17:31:19 -0400
Message-ID: <CAPv4CP_f=O6Q0st4vEexpRSZ4T7zZuW2AZWZPCy91+h3+70G3g@mail.gmail.com>
Subject: Re: More participation from under-represented regions
To: Juliao Braga <juliao@braga.eti.br>
Content-Type: multipart/alternative; boundary=001a11c2c396d4a19b04ddb9dfa6
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, 27 May 2013 21:31:41 -0000

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

On Mon, May 27, 2013 at 12:41 PM, Juliao Braga <juliao@braga.eti.br> wrote:

> 2. Our people know RFCs, but are far from knowing about the IETF.


Juliao, you say they know RFCs. Do they have problems with the RFCs? Do
they see gaps in what they can do, or problems with what the RFCs
recommend?

If they do not, then there is no reason for them to be involved in the
IETF.  If they do, then you can point them to specific working groups that
are working in that area.

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

On Mon, May 27, 2013 at 12:41 PM, Juliao Braga <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:juliao@braga.eti.br" target=3D"_blank">juliao@braga.eti.br</a>&=
gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">

2. Our people know RFCs, but are far from knowing about the IETF. </blockqu=
ote><div><br></div><div>Juliao, you say they know RFCs. Do they have proble=
ms with the RFCs? Do they see gaps in what they can do, or problems with wh=
at the RFCs recommend?=A0</div>

<div><br></div><div>If they do not, then there is no reason for them to be =
involved in the IETF. =A0If they do, then you can point them to specific wo=
rking groups that are working in that area. =A0</div></div>

--001a11c2c396d4a19b04ddb9dfa6--

From christian.oflaherty@gmail.com  Mon May 27 14:38:59 2013
Return-Path: <christian.oflaherty@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3199B21F8A7B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EVAtOiA3YZmG for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 14:38:58 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 953EB21F8A74 for <ietf@ietf.org>; Mon, 27 May 2013 14:38:58 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id b11so5186118iee.39 for <ietf@ietf.org>; Mon, 27 May 2013 14:38:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4JMD2uAL68xUAsCCSKUhNSr1Ke3Vqi8j8s5ZHlayoQw=; b=lF4pYxWM56EFLjj+lOqemCq2V+1ey+ZReRbejr3tdHtmilpbuwVnYNKvQCCeH4+fmC I5NP1HWWv9r8P+SJlb914xFKHGGrzQVM7inXOkyQ/dPWvy2BTUlh8v+0Qtuj6k8ZKnJ8 Io0WKa/r8ZKAGPftAYuonom9s5V3AXp+BhtRK9GeuHddlyv6Uegmn4M+Y5Ao2hEcy3Tf xuyghs5bgTvLt3/w6C/bPcZEJwMfEAcJ+czF0LrguzizFywOZEWr4bMlxYNKXAX4h29x p8q/TBPFj11xN8zDhSlQrdxexy9+HoOu7sbgdrZQVRIbDGzQRwPXHPwzu43LK3EVo9dc DokQ==
MIME-Version: 1.0
X-Received: by 10.50.30.2 with SMTP id o2mr5685975igh.12.1369690738020; Mon, 27 May 2013 14:38:58 -0700 (PDT)
Received: by 10.64.136.18 with HTTP; Mon, 27 May 2013 14:38:57 -0700 (PDT)
In-Reply-To: <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net>
Date: Mon, 27 May 2013 18:38:57 -0300
Message-ID: <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 21:38:59 -0000

Hi,

On Mon, May 27, 2013 at 5:08 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
> I'm not quite sure the currency exchange issues are key for this discussion. FWIW, I think you can still budget in Euros for the Berlin meeting,
> but I'm only 97% sure :-)
>
> Anyway, I wanted to highlight that, as has been pointed out by many, just meeting at some place makes little sense. But the question on the
> table is not just that. We're asking both about the meeting and about what other forms of getting additional participation from the region would
> be useful. My personal opinion is that we need to do multiple things to make an impact. And again IMO, meetings should be a part of that set.
> But definitely not alone. I know many of you have been very willing to help out in going out to new areas of the world to speak, gather input,
> and get familiar with more people. Thank you. I certainly plan to do that as well.
>

I would like to follow up on this proposal. Having a meeting in South
America scheduled two or three years in advance will let us engage
local organisations and individuals on a "project". We did several
activities in the region trying to encourage IETF participation, but
we're going to be much more effective if they're part of a plan with a
strong commitment (and effort) from the IETF community.

Since this opportunity was announced, there were several contacts and
proposals from different groups asking for additional information,
suggesting things to do, asking for details, etc. We now have a much
more fertile ground to do multiple things.

> The other thing that was mentioned was political pressure to appear international. My opinion is that doing something purely based on that
> would be silly and potentially harmful. However, I think we have a situation where we simultaneously need wider involvement from different
> organisations & areas, are reaching out to new types of participants (including, shock! even regulators in cases like PAWS), and do face
> some pressures about how we are perceived. An IETF that is open, has broad participation that is based on actual technical substance is in a
> very good position to continue to be perceived as the authority it is. This is not to say we are not already about all those things; we are. But I
> think we definitely need to go even further.

Going further will also enrich the IETF work and community (making it
more international becomes a side effect). In this region there are
many engineers, software developers, people at Universities, etc. that
could provide new ideas and energy to the IETF.

Christian

> A few other responses:
>
> Randy wrote:
>
>>  (1) "need-based" evangelism.  Outreach efforts are more
>>      effective if they sincerely address specific needs of
>>      the target community.  Does face-to-face participation in
>>      the IETF offer things practitioners in under-represented
>>      regions feel they need?  As long as we focus on how it
>>      could help *us*, rather than what needs it would address
>>      for them, it'll be far less effective than it could be.
>
>
> Very true.
>
> Melinda wrote:
>
>> The industry sector bias in IETF participation is
>> possibly compounding the regional bias.
>
>
> Yes.
>
> Jari
>

From juliao@braga.eti.br  Mon May 27 15:28:01 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F2A21F8FF3 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 15:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VpNJc73Pgx1p for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 15:27:56 -0700 (PDT)
Received: from mail-gh0-f171.google.com (mail-gh0-f171.google.com [209.85.160.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3604A21F8E4E for <ietf@ietf.org>; Mon, 27 May 2013 15:27:56 -0700 (PDT)
Received: by mail-gh0-f171.google.com with SMTP id f15so2048399ghb.30 for <ietf@ietf.org>; Mon, 27 May 2013 15:27:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=SyxYKuoxF8aPjJPlM7ln2L641VafAD/Xd7Giiv/i2Tg=; b=YUfKipt0Ygji91mfzJLhvEq/KI+NQAPh6ji3RnzK1yj/UZp4yi1xCswUJM1L4vWFGz gqO1qKJzvuSPfEWb4ENmgVBp8PBM6iE2+GFcXBXuQVQWlE0kf0GGkRWtVYQwv3BVTKAQ kpXbhtbBX29ccm3WJzs3v/MsOb00ENCLetcCGHsUysk5/d92HlMlTYvD2ejY5GXWyJaB gPCEv44X4lowwRH3dlmVyXpHtU5cD+UOFvwc0UaAid8dE4PFMJ+zdMNuEjLih6NGoiz+ SwKYwCbzNgf8iEfV6gQo5RbXy3AhTTkFQ5jkCCFP6ImC/llim39Cks1RCVDvRx48r1gO STxQ==
X-Received: by 10.236.146.137 with SMTP id r9mr15007964yhj.42.1369693675675; Mon, 27 May 2013 15:27:55 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id j64sm42811271yhj.25.2013.05.27.15.27.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 15:27:54 -0700 (PDT)
Message-ID: <51A3DDE6.7020107@braga.eti.br>
Date: Mon, 27 May 2013 19:27:50 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br> <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com> <51A38CB2.6030102@braga.eti.br> <CAPv4CP_f=O6Q0st4vEexpRSZ4T7zZuW2AZWZPCy91+h3+70G3g@mail.gmail.com>
In-Reply-To: <CAPv4CP_f=O6Q0st4vEexpRSZ4T7zZuW2AZWZPCy91+h3+70G3g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQmgKeMJanNgy0kDc1CWjRLV4JmSzkgxlT8Xh3bG2m2QRYu8vSpT7o1vCPTsnPO9K5OPY6pZ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 22:28:01 -0000

Hi Scott,

They know RFCs => they read, learn and understand.

If they have problems, have any restrictions or see any gap on the
content of the RFCs, I don't know, unfortunately.

What I said is that they do not know the processes involved in the
production of what they read. In other words, they do not know the IETF.

But this is not a general rule! Occurs with much people. I don't have
the slightest idea how many would.

Best Regards,

Julião

Em 27/05/2013 18:31, Scott Brim escreveu:
> On Mon, May 27, 2013 at 12:41 PM, Juliao Braga <juliao@braga.eti.br
> <mailto:juliao@braga.eti.br>> wrote:
> 
>     2. Our people know RFCs, but are far from knowing about the IETF. 
> 
> 
> Juliao, you say they know RFCs. Do they have problems with the RFCs? 
> Do they see gaps in what they can do, or problems with what the RFCs
> recommend? 
> 
> If they do not, then there is no reason for them to be involved in the
> IETF.  If they do, then you can point them to specific working groups
> that are working in that area.  

From randy@psg.com  Mon May 27 16:54:24 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B8221F87D1 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 16:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6ezWgbSIf8V for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 16:54:24 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8474C21F8681 for <ietf@ietf.org>; Mon, 27 May 2013 16:54:24 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Uh7F8-0002eK-M2; Mon, 27 May 2013 23:54:23 +0000
Date: Tue, 28 May 2013 08:54:21 +0900
Message-ID: <m2sj18dln6.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
In-Reply-To: <51A37E8A.9010506@bogus.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@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: 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, 27 May 2013 23:54:25 -0000

while i appreciate joe's listening to my other comments on the draft, i
still strongly object to publication of this draft as an rfc for the
reasons made very clear in the sec cons.  please read the summary
section of rfc 2804.

randy

From jmamodio@gmail.com  Mon May 27 17:58:40 2013
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 7CCDF21F8FED for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 17:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level: 
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[AWL=0.953,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8KwZK-ZcQ35l for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 17:58:40 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0EFDF21F8F0F for <ietf@ietf.org>; Mon, 27 May 2013 17:58:40 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id wd20so2190021obb.5 for <ietf@ietf.org>; Mon, 27 May 2013 17:58:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=xUhcoXmPOmC6iwx+1mHbUpm3l4md6khBdZmpNlQOvKo=; b=jZfFCH7v8kFe5ney/ldOlBIO9YqBB0exeOU4irSPqL5Cp+sv5f0MgVqIIjiIQkUsAy hFdnJuOr2vmBNjGpF9tLBxjw+17JiPRxeL7bIuXzAgHD38dSrQhJBWi98R9p46lY/H/U yv9CwZ3zsauIdvaM0LJEkGlYyCDwY425tV+fbcoFtYF0xVYULUtVDTCGxg/CQ7R1wGMX vV0LAmuBEkzYkC8EXopp7lLaTo0ySPExwmWBURI0f5P2EzkET5/ZaaneWRSVA//LKE7z /B7p9UVCpx8ygqU0r9KjWpQUCd1dlpFyuAWtFx0EJ1XDTigaLke8ZelA83/rKNdzrOIO WSPQ==
X-Received: by 10.60.85.74 with SMTP id f10mr19642402oez.32.1369702719573; Mon, 27 May 2013 17:58:39 -0700 (PDT)
Received: from [10.0.10.101] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id w7sm32499764obx.9.2013.05.27.17.58.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 17:58:38 -0700 (PDT)
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br> <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com> <51A38CB2.6030102@braga.eti.br> <CAPv4CP_f=O6Q0st4vEexpRSZ4T7zZuW2AZWZPCy91+h3+70G3g@mail.gmail.com> <51A3DDE6.7020107@braga.eti.br>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51A3DDE6.7020107@braga.eti.br>
Content-Type: multipart/alternative; boundary=Apple-Mail-258BF503-121B-4FE5-A40F-9E78DDA9DD78
Content-Transfer-Encoding: 7bit
Message-Id: <41BB58E8-66A4-4C98-A7C8-024AF75BB63D@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: More participation from under-represented regions
Date: Mon, 27 May 2013 19:58:37 -0500
To: Juliao Braga <juliao@braga.eti.br>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 00:58:40 -0000

--Apple-Mail-258BF503-121B-4FE5-A40F-9E78DDA9DD78
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: 7bit


Tell them to start at http://www.ietf.org/tao.html

It is available in few languages 

-Jorge

> What I said is that they do not know the processes involved in the
> production of what they read. In other words, they do not know the IETF.
> 

--Apple-Mail-258BF503-121B-4FE5-A40F-9E78DDA9DD78
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>Tell them to start at&nbsp;<a href="http://www.ietf.org/tao.html">http://www.ietf.org/tao.html</a></div><div><br></div><div>It is available in few languages&nbsp;</div><div><br>-Jorge</div><div><br></div><blockquote type="cite"><div><span>What I said is that they do not know the processes involved in the</span><br><span>production of what they read. In other words, they do not know the IETF.</span><br><br></div></blockquote></body></html>
--Apple-Mail-258BF503-121B-4FE5-A40F-9E78DDA9DD78--

From juliao@braga.eti.br  Mon May 27 18:34:31 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3F6A21F9113 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 18:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XcfuZFqz77N6 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 18:34:31 -0700 (PDT)
Received: from mail-vb0-x229.google.com (mail-vb0-x229.google.com [IPv6:2607:f8b0:400c:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 10C1621F8F43 for <ietf@ietf.org>; Mon, 27 May 2013 18:34:30 -0700 (PDT)
Received: by mail-vb0-f41.google.com with SMTP id p14so5106221vbm.0 for <ietf@ietf.org>; Mon, 27 May 2013 18:34:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=ES1pmZTLErlgOl2J9DvpWMPupCsHRZGTQd/dcLl+OFY=; b=h/l6iHjDn8R8Pf6xj8Lkj3/tUjRcugaHqE2T1AvgBdFFhJTCu2oXXsOjDKp50OlBNt 7UT6F3iXbTK8DklydxFHfBlBJaxmJWc0PkGPXWn50vU4pq7SUUgFnQEEP5/IfmfUl+8J tAN2N6sc/xcRH4zGBMM4VvCmVvbaOeRIZMBTKXylX2V/JCe+//p1JOtiQK/Tl2Ny36mS m+ZNMREar4d3vMyKNUkzIZs//e7cOWMfW2ES9x1bX00TWpbFk7TUO9YD18nbv9gH5ofP M0AoAacZb0tHpJgAxg1qPCCl7IOLa0XVkWDzh14KHA3o/glRzZw+O1BAyHK8d9FYqqe2 rpIQ==
X-Received: by 10.220.158.209 with SMTP id g17mr16321846vcx.22.1369704870247;  Mon, 27 May 2013 18:34:30 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id ho10sm22522189vdb.7.2013.05.27.18.34.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 18:34:29 -0700 (PDT)
Message-ID: <51A409A0.6080306@braga.eti.br>
Date: Mon, 27 May 2013 22:34:24 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br> <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com> <51A38CB2.6030102@braga.eti.br> <CAPv4CP_f=O6Q0st4vEexpRSZ4T7zZuW2AZWZPCy91+h3+70G3g@mail.gmail.com> <51A3DDE6.7020107@braga.eti.br> <41BB58E8-66A4-4C98-A7C8-024AF75BB63D@gmail.com>
In-Reply-To: <41BB58E8-66A4-4C98-A7C8-024AF75BB63D@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQmNWCo92QWeQOyivYA3637cOUvPh4Q8sCW9nBW9F/8ALKHaYudS4AzigJcsxxtIWElJdhE1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 01:34:31 -0000

Thank you, Jorge.

I did this when I wrote a article about IETF, in Portuguese, named "The
ISOC, the IETF and the Internet Infrastructure:
http://ii.blog.br/2013/01/03/a-isoc-o-ietf-e-a-infraestrutura-da-infraestrutura-da-internet/

and, also in Portuguese, "Understanding RFCs:
http://ii.blog.br/2013/02/03/entendendo-rfcs/

Julião

Em 27/05/2013 21:58, Jorge Amodio escreveu:
> 
> Tell them to start at http://www.ietf.org/tao.html
> 
> It is available in few languages 
> 
> -Jorge
> 
>> What I said is that they do not know the processes involved in the
>> production of what they read. In other words, they do not know the IETF.
>>

From rlb@ipv.sx  Mon May 27 18:35:35 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D09121F926E for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 18:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.81
X-Spam-Level: 
X-Spam-Status: No, score=-0.81 tagged_above=-999 required=5 tests=[AWL=-2.167,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qGGmg5Lzx8vb for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 18:35:24 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id CAFC521F8F43 for <ietf@ietf.org>; Mon, 27 May 2013 18:35:23 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id dn14so8536407obc.12 for <ietf@ietf.org>; Mon, 27 May 2013 18:35:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=6aCCwk3VlgEaoY6ORTNSP7VRBcIwytfD5Tbu4jNxX64=; b=d+jGaBSeO18gtsMTvotr5yQesy5vE6dKzk1JdL5V1ipNgu3azWkNDnmFpzUVxCq13f AMg/eC19jjvT6EcD0X1NUO/0Pk6JXjzHRPRBBJ5IqT2x1DxOeUuReXQwEQrmclshHVBt zYLfriVN45EOcPxzx4AWu6NuaqgMdlPtPxd5adj+yhrFQZCQsedsw6ECpL8wEul8R3VX eH/vU2kM6wc03aN1TcQ6P828W9OKA8dXbxmyzl3yzx9o6qTlH+VJV+fSj779Vf0eyiLC bOhqA4FewEGyqedr/wzHEGM0B6hcxuo7kg10COsNtl3Qk9FF22C/lpvY/YE+RcuVJvrB giww==
MIME-Version: 1.0
X-Received: by 10.60.42.104 with SMTP id n8mr19733692oel.94.1369704923289; Mon, 27 May 2013 18:35:23 -0700 (PDT)
Received: by 10.60.102.146 with HTTP; Mon, 27 May 2013 18:35:23 -0700 (PDT)
X-Originating-IP: [108.18.40.68]
In-Reply-To: <ADAA4A8A-E5BD-4DF1-B9E1-270A1780998C@cs.columbia.edu>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <D7C3108CB0A00C3C13DBD928@JcK-HP8200.jck.com> <CAL02cgToqRu-otpgUQXSnyMLFQOc_-FtZgMjXq5kK+iQ_+zZPQ@mail.gmail.com> <94B83A14-1FFE-450C-BAFF-0EC03E425641@cs.columbia.edu> <CAL02cgQHCyPM-movR8MTNYYFe8utGP8PU8YSa8VtWYh8MDFR1A@mail.gmail.com> <ADAA4A8A-E5BD-4DF1-B9E1-270A1780998C@cs.columbia.edu>
Date: Mon, 27 May 2013 21:35:23 -0400
Message-ID: <CAL02cgQJFucbgGLB+gs9R1_vzN4yt1nKkqwxc22ufhwN7JZiYQ@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Richard Barnes <rlb@ipv.sx>
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Content-Type: multipart/alternative; boundary=089e0149ca5c666c4d04ddbd4778
X-Gm-Message-State: ALoCoQllPDwiBpHPF1LWK8zBWSmYwrDodcQEAQo+i0pRXZOyacKTgSZIK9zuJxooWKYzkiOXDPoX
Cc: John C Klensin <john-ietf@jck.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 01:35:35 -0000

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

Keep in mind, though, that the binary decision is usually per site.  So if
the PSAP is web-enabled, the user can provide location to 911.gov, and not
anyone else.

That seems like a solution that's more likely to deploy than something that
requires the browser to distinguish emergency from non-emergency web apps.

--Richard


On Monday, May 27, 2013, Henning Schulzrinne wrote:

> Agreed - this is not so much about standards, but developer awareness. If
> we write any "how to" or similar informational documents, they should
> probably contain that type of discussion.
>
> There is a browser aspect, however: Right now, users only have a binary
> choice about location disclosure, even though I suspect many users would be
> fine with "location disclosure for 911 only", not "disclose my fine-grained
> location for any purpose you like".
>
> On May 27, 2013, at 1:51 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
> Even for location delivery, there's not that much to say at the standards
> layer.
>
> For *delivery*, the story is the same as with signaling.  Either the
> RTCWeb VoIP service can translate the location information to comply with
> RFC 6442, or the PSAP can just build a web app that collects it however it
> likes.
>
> For *determination*, it's about the browser.  You can do browser-based
> geolocation today, to "OK" quality.  Or the browser could implement the
> GEOPRIV protocols to benefit from network-provided location.
>
> All that's about implementation/deployment though.  I don't really see any
> new standards there.
>
> --Richard
>
>
>
> On Mon, May 27, 2013 at 12:19 PM, Henning Schulzrinne <hgs@cs.columbia.edu
> > wrote:
>
> The most difficult part for any emergency calling system is location
> delivery. WebRTC probably doesn't have much impact on emergency calls if
> all the calls traverse a server of some kind and if the caller location can
> be looked up based on caller IP addresses, but once you have the end system
> involved in location determination (e.g., for mobile devices or for
> DHCP-delivered location), it has to know when a call is an emergency call
> as you otherwise end up providing location for every call, which is
> non-ideal from a privacy and battery perspective.
>
> At least in the US, many of the WebRTC services would be considered
> "interconnected VoIP", so they are indeed subject to 911 obligations.
>
> Henning
>
> On May 26, 2013, at 3:57 PM, Richard Barnes <rlb@ipv.sx> wrote:
>
> Indeed, there has already been some coordination between the groups, going
> back about a year:
> <http://tools.ietf.org/agenda/84/slides/slides-84-ecrit-0.pdf>
> <http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.txt>
>
> So my read of the situation is much less dire than James's.  As I
> understand it, the upshot of the initial coordination discussions is that
> there's not a single, clear "RTCWEB+ECRIT" story.  Instead, there are a few
> ways you can put them together.  In the short run, without upgrading PSAPs,
> RTCWEB VoIP services can bridge RTCWEB signaling to ECRIT-compliant SIP,
> either at the server, or at the client using something like
> SIP-over-WebSockets.  In the long run, PSAPs can just advertise an RTCWEB
> service like they would advertise a SIP service today (in LoST).  Neither
> of these is incompatible with RTCWEB or ECRIT as they're being specified
> today.
>
> I expect there are probably some ECRIT considerations that aren't
> naturally supported in RTCWEB.  Things like real-time text come to mind.
>  However, it doesn't seem to me that there's gross incompatibility.
>
> --Richard
>
>
>
>
> On Sat, May 25, 2013 at 10:18 AM, John C Klensin <john-ietf@jck.com>wrote:
>
>
>
> --On Saturday, May 25, 2013 10:10 +0300 Jari Arkko
> <jari.arkko@piuha.net> wrote:
>
> >...
> > I didn't know about the details of the emergency
> > communications situation. But it is always difficult to
> > balance getting something out early vs. compl
>
>

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

Keep in mind, though, that the binary decision is usually per site. =A0So i=
f the PSAP is web-enabled, the user can provide location to <a href=3D"http=
://911.gov">911.gov</a>, and not anyone else.<div><br></div><div>That seems=
 like a solution that&#39;s more likely to deploy than something that requi=
res the browser to distinguish emergency from non-emergency web apps.=A0</d=
iv>
<div><br></div><div>--Richard<span></span></div><div><br><br>On Monday, May=
 27, 2013, Henning Schulzrinne  wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv style=3D"word-wrap:break-word">
<div>Agreed - this is not so much about standards, but developer awareness.=
 If we write any &quot;how to&quot; or similar informational documents, the=
y should probably contain that type of discussion.</div><div><br></div>
<div>There is a browser aspect, however: Right now, users only have a binar=
y choice about location disclosure, even though I suspect many users would =
be fine with &quot;location disclosure for 911 only&quot;, not &quot;disclo=
se my fine-grained location for any purpose you like&quot;.</div>
<br><div><div>On May 27, 2013, at 1:51 PM, Richard Barnes &lt;<a>rlb@ipv.sx=
</a>&gt; wrote:</div><br><blockquote type=3D"cite"><div dir=3D"ltr">Even fo=
r location delivery, there&#39;s not that much to say at the standards laye=
r.<div>
<br></div><div>For *delivery*, the story is the same as with signaling. =A0=
Either the RTCWeb VoIP service can translate the location information to co=
mply with RFC 6442, or the PSAP can just build a web app that collects it h=
owever it likes.</div>

<div><br></div><div>For *determination*, it&#39;s about the browser. =A0You=
 can do browser-based geolocation today, to &quot;OK&quot; quality. =A0Or t=
he browser could implement the GEOPRIV protocols to benefit from network-pr=
ovided location.</div>

<div><br></div><div>All that&#39;s about implementation/deployment though. =
=A0I don&#39;t really see any new standards there.</div><div><br></div><div=
>--Richard</div>
<div><br><div><br><br><div>On Mon, May 27, 2013 at 12:19 PM, Henning Schulz=
rinne <span dir=3D"ltr">&lt;<a>hgs@cs.columbia.edu</a>&gt;</span> wrote:<br=
>

<blockquote style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><div style=3D"word-wrap:break-word"><div>The most difficult part f=
or any emergency calling system is location delivery. WebRTC probably doesn=
&#39;t have much impact on emergency calls if all the calls traverse a serv=
er of some kind and if the caller location can be looked up based on caller=
 IP addresses, but once you have the end system involved in location determ=
ination (e.g., for mobile devices or for DHCP-delivered location), it has t=
o know when a call is an emergency call as you otherwise end up providing l=
ocation for every call, which is non-ideal from a privacy and battery persp=
ective.</div>


<div><br></div><div>At least in the US, many of the WebRTC services would b=
e considered &quot;interconnected VoIP&quot;, so they are indeed subject to=
 911 obligations.</div><span><font color=3D"#888888"><div>
<br></div><div>Henning</div></font></span><div><br><div><div>On May 26, 201=
3, at 3:57 PM, Richard Barnes &lt;<a>rlb@ipv.sx</a>&gt; wrote:</div><br><bl=
ockquote type=3D"cite">
<div dir=3D"ltr">Indeed, there has already been some coordination between t=
he groups, going back about a year:<div>&lt;<a href=3D"http://tools.ietf.or=
g/agenda/84/slides/slides-84-ecrit-0.pdf" target=3D"_blank">http://tools.ie=
tf.org/agenda/84/slides/slides-84-ecrit-0.pdf</a>&gt;</div>



<div>&lt;<a href=3D"http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.tx=
t" target=3D"_blank">http://tools.ietf.org/id/draft-aboba-rtcweb-ecrit-00.t=
xt</a>&gt;</div><div><br></div><div><span style=3D"font-family:arial,sans-s=
erif;font-size:13px">So my read of the situation is much less dire than Jam=
es&#39;s. =A0As I understand it, the upshot of the initial coordination dis=
cussions is that there&#39;s not a single, clear &quot;RTCWEB+ECRIT&quot; s=
tory. =A0Instead, there are a few ways you can put them together. =A0In the=
 short run, without upgrading PSAPs, RTCWEB VoIP services can bridge RTCWEB=
 signaling to ECRIT-compliant SIP, either at the server, or at the client u=
sing something like SIP-over-WebSockets. =A0In the long run, PSAPs can just=
 advertise an RTCWEB service like they would advertise a SIP service today =
(in LoST). =A0Neither of these is incompatible with RTCWEB or ECRIT as they=
&#39;re being specified today.</span><br>



</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">I expect there are probably some ECRIT considerations that aren&#39;t na=
turally supported in RTCWEB. =A0Things like real-time text come to mind. =
=A0However, it doesn&#39;t seem to me that there&#39;s gross incompatibilit=
y.</span></div>



<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">--R=
ichard</span></div><div><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px"><br>



</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x"><br></span></div></div><div><br><br><div>On Sat, May 25, 2013 at 10:18 A=
M, John C Klensin <span dir=3D"ltr">&lt;<a>john-ietf@jck.com</a>&gt;</span>=
 wrote:<br>



<blockquote style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex"><br>
<br>
--On Saturday, May 25, 2013 10:10 +0300 Jari Arkko<br>
&lt;<a>jari.arkko@piuha.net</a>&gt; wrote:<br>
<br>
&gt;...<br>
<div>&gt; I didn&#39;t know about the details of the emergency<br>
&gt; communications situation. But it is always difficult to<br>
&gt; balance getting something out early vs. compl</div></blockquote></div>=
</div></blockquote></div></div></div></blockquote></div></div></div></div><=
/blockquote></div></div></blockquote></div>

--089e0149ca5c666c4d04ddbd4778--

From jmamodio@gmail.com  Mon May 27 19:08:14 2013
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 489A921F90E0 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 19:08:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.265
X-Spam-Level: 
X-Spam-Status: No, score=-1.265 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FpsHh+11+ttd for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 19:08:13 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF6721F8F62 for <ietf@ietf.org>; Mon, 27 May 2013 19:08:12 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id ef5so8491936obb.16 for <ietf@ietf.org>; Mon, 27 May 2013 19:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=EVZHp8wO6eqYaJTo30KZTb6/wR0hRWa85jWrl5M6c9U=; b=HcYDHPnyEnevtOAUIEesDpq7wg4QTStdFpawytv35uTontFdM2btaOVRwJP4UE/gEU iTcaAqILWUevDVRol/3KPpNbOWgE+1iPVib7nnYKc4iCtDs+cszElLpCqdSl8Y1alpJV 9qmbZXk0YbuCui3V6CppTeUouQqrvMJ0mfbRc6jIiAUOiIQrq9Xe6mhJr7Y9fU4jnINl OZxexGv0gOk5igObyZbwC9YmEl12yfxIsr2iqMITD8DYHuxI5rmX1+lfvryvXifWohVK Y8VekFPFLL/YYWCehdf778HjR+1vk8tre01vJo5uWYjr7/2XmbFUKGUzpvCZY6NPgfj9 ftbw==
X-Received: by 10.182.44.129 with SMTP id e1mr19721047obm.57.1369706889639; Mon, 27 May 2013 19:08:09 -0700 (PDT)
Received: from [10.0.10.101] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id pm16sm33616146oeb.3.2013.05.27.19.08.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 May 2013 19:08:08 -0700 (PDT)
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <6.2.5.6.2.20130526154034.0c284960@resistor.net> <51A2A296.1010305@braga.eti.br> <CANeGSFnPZ2-kUxOx1279r1qgPEOetcJ=xq2281B8S4UYyFKesA@mail.gmail.com> <51A38CB2.6030102@braga.eti.br> <CAPv4CP_f=O6Q0st4vEexpRSZ4T7zZuW2AZWZPCy91+h3+70G3g@mail.gmail.com> <51A3DDE6.7020107@braga.eti.br> <41BB58E8-66A4-4C98-A7C8-024AF75BB63D@gmail.com> <51A409A0.6080306@braga.eti.br>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51A409A0.6080306@braga.eti.br>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <E69B8181-B5BC-46B0-9750-428E80E61068@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: More participation from under-represented regions
Date: Mon, 27 May 2013 21:08:07 -0500
To: Juliao Braga <juliao@braga.eti.br>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 02:08:14 -0000

Great job Juli=C3=A3o, thanks for sharing.=20

-Jorge

On May 27, 2013, at 8:34 PM, Juliao Braga <juliao@braga.eti.br> wrote:

> Thank you, Jorge.
>=20
> I did this when I wrote a article about IETF, in Portuguese, named "The
> ISOC, the IETF and the Internet Infrastructure:
> http://ii.blog.br/2013/01/03/a-isoc-o-ietf-e-a-infraestrutura-da-infraestr=
utura-da-internet/
>=20
> and, also in Portuguese, "Understanding RFCs:
> http://ii.blog.br/2013/02/03/entendendo-rfcs/
>=20
> Juli=C3=A3o
>=20
> Em 27/05/2013 21:58, Jorge Amodio escreveu:
>>=20
>> Tell them to start at http://www.ietf.org/tao.html
>>=20
>> It is available in few languages=20
>>=20
>> -Jorge
>>=20
>>> What I said is that they do not know the processes involved in the
>>> production of what they read. In other words, they do not know the IETF.=

>>>=20

From d3e3e3@gmail.com  Mon May 27 21:10:02 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 019E121F9434 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 21:10:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GIiEBAD903At for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 21:09:56 -0700 (PDT)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id AE78521F941D for <ietf@ietf.org>; Mon, 27 May 2013 21:09:56 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id n9so9388902oag.28 for <ietf@ietf.org>; Mon, 27 May 2013 21:09:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=GfkfDqnjQIKktxZ29/UQ/7jxewZU577Hk77mklKrDZE=; b=nm0H83oPJcmgwFTxovLB4GV5ribZAEtk8bjSHvlcHK4VMvff7jm1gEWDH4ZN8NrgVv HQ75ZPkC80SgaZuXudWRFk0OxRamX2rB4nBrIXotxxt9a1suDfQgf1nLqk5r2cd1bWE2 QL8/uxeACF5jcpAWwdZGFeYEG0nILYGn9pTtkR4335AkgIvpElUfwu3+t2JJn7Dd54Wt QEn5z00M+oOm5KpOVVWbwMkx7e2yfc7itNHMmqJQWiKwZ2CjBKWruLKjf/5OVScrkRIE 78xGvO+riutCnlrAdVAoHksbu8KSB1R0rC0i58sdhFklVKTE2TqREdN9toCiaEIGHZ9u LAKg==
X-Received: by 10.60.131.243 with SMTP id op19mr19284972oeb.132.1369714196294;  Mon, 27 May 2013 21:09:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.100.231 with HTTP; Mon, 27 May 2013 21:09:36 -0700 (PDT)
In-Reply-To: <m2sj18dln6.wl%randy@psg.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 28 May 2013 00:09:36 -0400
Message-ID: <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
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: Tue, 28 May 2013 04:10:02 -0000

On Mon, May 27, 2013 at 7:54 PM, Randy Bush <randy@psg.com> wrote:
> while i appreciate joe's listening to my other comments on the draft, i
> still strongly object to publication of this draft as an rfc for the
> reasons made very clear in the sec cons.  please read the summary
> section of rfc 2804.

While the RFC should not be materially misleading, I don't think there
is a requirement for Informational RFCs to guarantee any particular
level or security or privacy.

RFC 2804 is about the security of communications content, not the
security of statically stored address information. I'm not denying the
applicability of some security considerations, I'm just saying that
RFC 2804 doesn't seem to me to be particularly applicable. In any
case, the final part of the summary section of RFC 2804 calls for the
publication of specifications that might affect security.

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

> randy

From dhc@dcrocker.net  Mon May 27 23:29:49 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6314521F93A6 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 23:29:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kFu4FyQ31NUS for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 23:29:44 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9C64021F93E9 for <ietf@ietf.org>; Mon, 27 May 2013 23:29:39 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4S6TWM1005346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 May 2013 23:29:37 -0700
Message-ID: <51A44EC9.7080100@dcrocker.net>
Date: Tue, 28 May 2013 08:29:29 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com>
In-Reply-To: <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 27 May 2013 23:29:38 -0700 (PDT)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 06:29:49 -0000

On 5/27/2013 11:38 PM, Christian O'Flaherty wrote:
> I would like to follow up on this proposal. Having a meeting in South
> America scheduled two or three years in advance will let us engage
> local organisations and individuals on a "project". We did several
> activities in the region trying to encourage IETF participation, but
> we're going to be much more effective if they're part of a plan with a
> strong commitment (and effort) from the IETF community.


Such a project sounds like an excellent idea and it could be interesting 
to pursue it with coordination from the IETF community.

One point worth noting is that the primary work of the IETF is conducted 
over email.  Consequently, the project does not require an in-person 
meeting with the IETF community.  In fact, relying on an in-person 
meeting for the effort is counter-productive training for being 
effective in the IETF.  I don't mean that such meetings aren't useful, 
but that I believe they are secondary to the work that is done over the 
rest of the time.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From randy@psg.com  Mon May 27 23:42:25 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152CD21F8F33 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 23:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NXNEthJ3tG4 for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 23:42:24 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBA721F8F06 for <ietf@ietf.org>; Mon, 27 May 2013 23:42:24 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UhDbx-0004bi-Gs; Tue, 28 May 2013 06:42:21 +0000
Date: Tue, 28 May 2013 15:42:37 +0900
Message-ID: <m27gij61wi.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed Standard
In-Reply-To: <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 06:42:25 -0000

>> while i appreciate joe's listening to my other comments on the draft, i
>> still strongly object to publication of this draft as an rfc for the
>> reasons made very clear in the sec cons.  please read the summary
>> section of rfc 2804.
> 
> While the RFC should not be materially misleading, I don't think there
> is a requirement for Informational RFCs to guarantee any particular
> level or security or privacy.

that the draft now tries to slide by as info does not change that it
specified protocol elements and how they are to be used.  and the draft
makes very clear that this is juristiction specific and a serious
privacy problem.

> RFC 2804 is about

i am very well aware what 2804 contains

> RFC 2804 doesn't seem to me to be particularly applicable.

i disagree.  i believe the first two bullets in section one are very
applicable to joe's draft.

   - The IETF, an international standards body, believes itself to be
     the wrong forum for designing protocol or equipment features that
     address needs arising from the laws of individual countries,
     because these laws vary widely across the areas that IETF standards
     are deployed in.  Bodies whose scope of authority correspond to a
     single regime of jurisdiction are more appropriate for this task.

   - The IETF sets standards for communications that pass across
     networks that may be owned, operated and maintained by people from
     numerous jurisdictions with numerous requirements for privacy.  In
     light of these potentially divergent requirements, the IETF
     believes that the operation of the Internet and the needs of its
     users are best served by making sure the security properties of
     connections across the Internet are as well known as possible.  At
     the present stage of our ignorance this means making them as free
     from security loopholes as possible.

randy

From sm@resistor.net  Tue May 28 00:38:06 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 182FF21F8F33 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 00:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.079
X-Spam-Level: 
X-Spam-Status: No, score=-102.079 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wslKOXTazwIg for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 00:38:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5060321F8EB1 for <ietf@ietf.org>; Tue, 28 May 2013 00:38:04 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4S7btqr011551; Tue, 28 May 2013 00:37:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369726680; bh=d7uLRPIvb7v0YIxFPXVHXM2ySh8+odHn9b65AUzt/Eo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RtEXYXjeBBoQzMCTYQqdOX2UZddSF/NMvCXqgwSLr2Xmoeen4HrJA7YuN1w0aLFlK x7zp8pI8WJayPXn/Qh8yAGQcJUWuqJe0glsTbDCCIbhhN6PTUXy+rQ/+7vurmyqsbD NWrACBuOdN0qYadJquqYcNymAVFDqlrwz5EV79E0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369726680; i=@resistor.net; bh=d7uLRPIvb7v0YIxFPXVHXM2ySh8+odHn9b65AUzt/Eo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=w4Fg85QXl0LLDQABuxMDdHBCCC8sx+2T5ZNkkC1T2U1eq8V4x5nWCeSFHHZnxvjMt wldiikrQU6b6YNEV3+DzW2Z01YqPKDG5g0ow2rORSTEQJESOXGEqbURxXw9fRu2+Xd Dqj0DUJE98sl8lB2L51Kp7mmoZsVlszXGG7VAJl8=
Message-Id: <6.2.5.6.2.20130527232315.0c2c56b8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 28 May 2013 00:30:24 -0700
To: Donald Eastlake <d3e3e3@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-Reply-To: <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.g mail.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 07:38:06 -0000

Hi Donald,
At 21:09 27-05-2013, Donald Eastlake wrote:
>While the RFC should not be materially misleading, I don't think there
>is a requirement for Informational RFCs to guarantee any particular
>level or security or privacy.

Yes.  In my opinion a best effort is preferable or else the Security 
Considerations section in RFCs is useless.

In theory the IETF does not publish RFCs to suit the regulations of 
one country (see use-case in 
draft-jabley-dnsext-eui48-eui64-rrtypes-04).  In practice, the IETF 
has published a RFC to suit the requirements (it was a voluntary 
measure instead of a formal requirement) of one country.

draft-jabley-dnsext-eui48-eui64-rrtypes-04 is an odd case.  My guess 
is that the requirements were set because of a problem of 
monopoly.  I have not looked into whether the transfer of data 
violates the expectations of the user.  I understand that the draft 
is about standardizing [1] a data format and not the transfer of 
data.  Section 8 of the draft says everything correctly except that 
it doesn't provide adequate security guidance.

I believe that Joe tried to do the "right thing".  I am not 
comfortable objecting to publication as I don't know the "path 
forward".  I personally would not support publication.  That can 
easily be overcome and I won't do anything about it.

Regards,
-sm

1. I did read Section 2 carefully.  


From rumbiles@gmail.com  Tue May 28 01:26:10 2013
Return-Path: <rumbiles@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 737DA21F87C5 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 01:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Niw41PxJejCn for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 01:26:04 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id BEB7221F8B98 for <ietf@ietf.org>; Tue, 28 May 2013 01:26:02 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id at1so20405416iec.35 for <ietf@ietf.org>; Tue, 28 May 2013 01:26:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rcpemjgtk95DQ/yZIRxzJkn8WG6eBuCaBw23v0pd58Y=; b=BahG1ZdKgiaXDW6AiyQTa7jZpH1dw/gZN2EcyBEp7g08AC5d37/v21DTw42q+LAMaq z5XkruoET2kgv+bhD+VipmzGU0JW4nZyLawAyaHb7jPrzWlJ1Kc+B+ix1yCktwQ/rGj1 sZhhu30r24OrTC3yuCzzzYYmEpTUtv2s+ezjppcxpP3U12uBw4a41cJQlLJYSknXmOyX Nd3AVst53SHHclKWzNrDVG8Kg9kcK2XSqCUhM2BvbTcNyi9RbflXvgnGqyXedvCNDacP g76h3/1ixjIVSuBibeTEvQfeL9/B6xA63KQlQU31EGVDqsFyy2Bp3yIQQErSKbGeD0RU PZxQ==
MIME-Version: 1.0
X-Received: by 10.50.118.69 with SMTP id kk5mr6266876igb.36.1369729561999; Tue, 28 May 2013 01:26:01 -0700 (PDT)
Received: by 10.50.176.225 with HTTP; Tue, 28 May 2013 01:26:01 -0700 (PDT)
In-Reply-To: <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls> <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com>
Date: Tue, 28 May 2013 10:26:01 +0200
Message-ID: <CAOnoajysqS0tNwBh=uchLxQsOoT0HwEKFyhNdkOVAx_eXTa=Bw@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
From: Rumbidzayi Gadhula <rumbiles@gmail.com>
To: Yoav Nir <ynir@checkpoint.com>
Content-Type: multipart/alternative; boundary=e89a8f643382fb42c004ddc30348
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 08:26:11 -0000

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

Your experience and ideas on how to start-out are useful.

On 27 May 2013 16:13, Yoav Nir <ynir@checkpoint.com> wrote:

> LCD?
>
> Anyway, What I found most useful when I was starting out 9 years ago, was
> to look over the list of areas and working groups (
> http://tools.ietf.org/area/ ) and find out which of them are working on
> something that is of interest to me. In my case it was mostly the security
> area, and the IPsec working group, since that is what I was working on in
> my day job. I subscribed to that list and some others that were also
> related to what I was working on (TLS, PKIX).
>
> So the best thing is to subscribe to the mailing lists, both those that
> interest you personally and those that are of interest to your employer (if
> there are such groups).
>
> Step 2 is to lurk for a couple of weeks at least, and just read what
> others are posting. If they're talking about a particular draft, it's easy
> to find on one of the IETF sites and read it. So you read the drafts, and
> read what people are saying about the drafts. This teaches you both about
> what the group is working on, and the (for lack of a better term)
> "political" part - who are the participants and what are they like.  You
> might also want to read the Tao document, although different groups have
> varying dynamics.
>
> After a while, you've read the drafts, you've read what some people are
> saying, and you may have formed an opinion, either about the draft itself,
> or about one of the comments. That's a good time to speak up by sending a
> message to the list. Maybe the draft got something wrong. Maybe the comment
> is only correct in certain contexts, but doesn't describe some situation
> you're familiar with. Maybe in reading the draft you find it hard to figure
> out what an implementation should do in a certain case, and you present the
> case, and ask that it be clarified. Maybe the proposed protocol would
> require clients, servers, or middleboxes to allocate more memory than
> implementations that you know can afford. Such comments, and even better,
> proposed fixes are how you build a reputation in the IETF for knowing your
> stuff. You can also volunteer to review a whole document, or volunteer to
> write a missing section. That is how you build a reputation for being
> useful. Both are necessary for success in the IETF.
>
> Step 4 is when you have an idea of your own, or you read someone else's
> idea and you want to participate. In that case you either write your own
> draft or join someone else in writing one. It's often not enough to just
> write it. You also have to get people to read it, post about it to the
> correct lists, and in general "sell" it and gather support. It is at about
> that time that you start to feel the need to attend meetings, but you can
> get some things done even without it.
>
> Hope this helps
>
> Yoav
>
> On May 27, 2013, at 3:33 PM, Nthabiseng Pule <npule@lca.org.ls>
>  wrote:
>
> > as,
> >
> > I am new to the IETF.  I would like to contribute any way I can, but the
> learning curve seems steep indeed. I am from an LCD country.  I have the
> necessary resources but I just don't know where to start.
> >
> > Some guidance would be welcome. I am reading on stuff and hope that one
> day I will be able to make some meaningful contribution.
> >
> >
> > Nthabiseng Pule
> >
> >
> >
> > On 27 May 2013, at 1:52 PM, Arturo Servin <aservin@lacnic.net> wrote:
> >
> >> John,
> >>
> >>   Good summary.
> >>
> >>   I would add a "steep learning-curve" to start participating. It takes
> time to get conformable in participating in mailing list and reviewing
> drafts for I think two reasons. One is to get know how the IETF works, and
> another to catch-up in knowing the topic in relation with other WG
> participants.
> >>
> >>   About the remote hub I think it would be good to give it a try.
> >>
> >> Regards,
> >> as
> >>
> >> On 27 May 2013, at 02:52, John Levine wrote:
> >>
> >>> I think this is a summary of the issues people have mentioned that
> >>> discourage participation from LDCs, in rough order of importance.
> >>>
> >>> * People aren't aware the IETF exists, or what it does, or that it has
> >>> an open participation model
> >>>
> >>> * People don't read and write English well enough to be comfortable
> >>> participating
> >>>
> >>> * People are unaccustomed to and perhaps uncomfortable expressing
> >>> overt disagreement
> >>>
> >>> * People don't think they have anything to contribute to an
> organization
> >>> that is mostly people from rich countries
> >>>
> >>> * People don't have adequate Internet access for mail, or to use the
> >>> remote participation tools
> >>>
> >>> I have to say that I don't see one or two meetings in South America
> >>> addressing any of these.  Given that the incremental cost to the
> >>> participants, compared to meeting in North America, would likely be on
> >>> the order of a million dollars, it seems to me very likely that there
> >>> are better ways to spend the money.
> >>>
> >>> For example, if language and net access is a problem, it might be
> >>> interesting to set up a remote participation center in B.A. during one
> >>> of the North American meetings (it's one time zone off from Toronto)
> >>> with screens and cameras, paid interpreters, and a few volunteers to
> >>> help explain what's going on.
> >>>
> >>> R's,
> >>> John
> >>
>
>

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

Your experience and ideas on how to start-out are useful.=A0<br><br><div cl=
ass=3D"gmail_quote">On 27 May 2013 16:13, Yoav Nir <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:ynir@checkpoint.com" target=3D"_blank">ynir@checkpoint.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">LCD?<br>
<br>
Anyway, What I found most useful when I was starting out 9 years ago, was t=
o look over the list of areas and working groups ( <a href=3D"http://tools.=
ietf.org/area/" target=3D"_blank">http://tools.ietf.org/area/</a> ) and fin=
d out which of them are working on something that is of interest to me. In =
my case it was mostly the security area, and the IPsec working group, since=
 that is what I was working on in my day job. I subscribed to that list and=
 some others that were also related to what I was working on (TLS, PKIX).<b=
r>

<br>
So the best thing is to subscribe to the mailing lists, both those that int=
erest you personally and those that are of interest to your employer (if th=
ere are such groups).<br>
<br>
Step 2 is to lurk for a couple of weeks at least, and just read what others=
 are posting. If they&#39;re talking about a particular draft, it&#39;s eas=
y to find on one of the IETF sites and read it. So you read the drafts, and=
 read what people are saying about the drafts. This teaches you both about =
what the group is working on, and the (for lack of a better term) &quot;pol=
itical&quot; part - who are the participants and what are they like. =A0You=
 might also want to read the Tao document, although different groups have v=
arying dynamics.<br>

<br>
After a while, you&#39;ve read the drafts, you&#39;ve read what some people=
 are saying, and you may have formed an opinion, either about the draft its=
elf, or about one of the comments. That&#39;s a good time to speak up by se=
nding a message to the list. Maybe the draft got something wrong. Maybe the=
 comment is only correct in certain contexts, but doesn&#39;t describe some=
 situation you&#39;re familiar with. Maybe in reading the draft you find it=
 hard to figure out what an implementation should do in a certain case, and=
 you present the case, and ask that it be clarified. Maybe the proposed pro=
tocol would require clients, servers, or middleboxes to allocate more memor=
y than implementations that you know can afford. Such comments, and even be=
tter, proposed fixes are how you build a reputation in the IETF for knowing=
 your stuff. You can also volunteer to review a whole document, or voluntee=
r to write a missing section. That is how you build a reputation for being =
useful. Both are necessary for success in the IETF.<br>

<br>
Step 4 is when you have an idea of your own, or you read someone else&#39;s=
 idea and you want to participate. In that case you either write your own d=
raft or join someone else in writing one. It&#39;s often not enough to just=
 write it. You also have to get people to read it, post about it to the cor=
rect lists, and in general &quot;sell&quot; it and gather support. It is at=
 about that time that you start to feel the need to attend meetings, but yo=
u can get some things done even without it.<br>

<br>
Hope this helps<br>
<br>
Yoav<br>
<br>
On May 27, 2013, at 3:33 PM, Nthabiseng Pule &lt;<a href=3D"mailto:npule@lc=
a.org.ls">npule@lca.org.ls</a>&gt;<br>
<div class=3D"HOEnZb"><div class=3D"h5">=A0wrote:<br>
<br>
&gt; as,<br>
&gt;<br>
&gt; I am new to the IETF. =A0I would like to contribute any way I can, but=
 the learning curve seems steep indeed. I am from an LCD country. =A0I have=
 the necessary resources but I just don&#39;t know where to start.<br>
&gt;<br>
&gt; Some guidance would be welcome. I am reading on stuff and hope that on=
e day I will be able to make some meaningful contribution.<br>
&gt;<br>
&gt;<br>
&gt; Nthabiseng Pule<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; On 27 May 2013, at 1:52 PM, Arturo Servin &lt;<a href=3D"mailto:aservi=
n@lacnic.net">aservin@lacnic.net</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; John,<br>
&gt;&gt;<br>
&gt;&gt; =A0 Good summary.<br>
&gt;&gt;<br>
&gt;&gt; =A0 I would add a &quot;steep learning-curve&quot; to start partic=
ipating. It takes time to get conformable in participating in mailing list =
and reviewing drafts for I think two reasons. One is to get know how the IE=
TF works, and another to catch-up in knowing the topic in relation with oth=
er WG participants.<br>

&gt;&gt;<br>
&gt;&gt; =A0 About the remote hub I think it would be good to give it a try=
.<br>
&gt;&gt;<br>
&gt;&gt; Regards,<br>
&gt;&gt; as<br>
&gt;&gt;<br>
&gt;&gt; On 27 May 2013, at 02:52, John Levine wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; I think this is a summary of the issues people have mentioned =
that<br>
&gt;&gt;&gt; discourage participation from LDCs, in rough order of importan=
ce.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; * People aren&#39;t aware the IETF exists, or what it does, or=
 that it has<br>
&gt;&gt;&gt; an open participation model<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; * People don&#39;t read and write English well enough to be co=
mfortable<br>
&gt;&gt;&gt; participating<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; * People are unaccustomed to and perhaps uncomfortable express=
ing<br>
&gt;&gt;&gt; overt disagreement<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; * People don&#39;t think they have anything to contribute to a=
n organization<br>
&gt;&gt;&gt; that is mostly people from rich countries<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; * People don&#39;t have adequate Internet access for mail, or =
to use the<br>
&gt;&gt;&gt; remote participation tools<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I have to say that I don&#39;t see one or two meetings in Sout=
h America<br>
&gt;&gt;&gt; addressing any of these. =A0Given that the incremental cost to=
 the<br>
&gt;&gt;&gt; participants, compared to meeting in North America, would like=
ly be on<br>
&gt;&gt;&gt; the order of a million dollars, it seems to me very likely tha=
t there<br>
&gt;&gt;&gt; are better ways to spend the money.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; For example, if language and net access is a problem, it might=
 be<br>
&gt;&gt;&gt; interesting to set up a remote participation center in B.A. du=
ring one<br>
&gt;&gt;&gt; of the North American meetings (it&#39;s one time zone off fro=
m Toronto)<br>
&gt;&gt;&gt; with screens and cameras, paid interpreters, and a few volunte=
ers to<br>
&gt;&gt;&gt; help explain what&#39;s going on.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; R&#39;s,<br>
&gt;&gt;&gt; John<br>
&gt;&gt;<br>
<br>
</div></div></blockquote></div><br>

--e89a8f643382fb42c004ddc30348--

From adrian@olddog.co.uk  Tue May 28 02:33:05 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4430521F8E8F for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 02:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.485
X-Spam-Level: 
X-Spam-Status: No, score=-1.485 tagged_above=-999 required=5 tests=[AWL=0.495,  BAYES_00=-2.599, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ffzBQlGVFKIq for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 02:32:59 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5854B21F8CEC for <ietf@ietf.org>; Tue, 28 May 2013 02:32:59 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4S9Wvsx027518 for <ietf@ietf.org>; Tue, 28 May 2013 10:32:57 +0100
Received: from 950129200 ([220.109.211.58]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4S9Ws0x027422 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 28 May 2013 10:32:56 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: When to adopt a WG I-D
Date: Tue, 28 May 2013 10:32:50 +0100
Message-ID: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5bhk7NZ1bJ2lzKSk+IVhI2yJUoXQ==
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: Tue, 28 May 2013 09:33:05 -0000

Hi,

Dave Crocker and I have this little draft [1] discussing the process and =
considerations for creating formal working group drafts that are =
targeted for publication.

We believe that this may help clarify some of the issues and concerns =
associated with this part of the process. We are targeting this as =
Informational (i.e. commentary on existing process, not new normative =
definition of process) and would like your input.

What is not clear?
What have we got wrong?
How should we resolve the remaining editor notes?

Thanks,
Adrian
(per pro Dave)

[1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt



From npule@lca.org.ls  Tue May 28 02:46:23 2013
Return-Path: <npule@lca.org.ls>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D86C821F90E0 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 02:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vMO1TjziD-XE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 02:46:23 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 13E8C21F8651 for <ietf@ietf.org>; Tue, 28 May 2013 02:46:22 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id k13so5253278wgh.5 for <ietf@ietf.org>; Tue, 28 May 2013 02:46:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=r0AYh3cR5aC8OIMiMqc73aSNlIEQD46+lE6IFPvdLwA=; b=YGVWaukQdnMnOBaHHsMLUZY1uy4mBJgkFS13Njpo2Az1jT34vMEQsWmh6v30H7JpO3 p0Hr7lxdsLiu7AI4MIC2uUM9Vv+lP3rxVcsajs6EfN2FlGHxDCVWnPbm9hgkLzTH5yY3 Oc5UxGfZpDx2VCY1h9hCEWe6YX6scCLSbE32inkCAjaNRdLcpSStL3c4SJ4Uv7YJv9Aq 9xmwJ6Y/2619I3FdmyMTKlmhk+39o543cKs491sxMagCYeSeyqLAnGTLS+Ih9rucd8Ix DY3ikjZsAzC4P28rf8wjliFDClWZiTzA+YqoT4J4NZ7hzwurVn3U5Jop1SZYHUzZS5Kt +NZw==
X-Received: by 10.180.185.244 with SMTP id ff20mr11542328wic.0.1369734382041;  Tue, 28 May 2013 02:46:22 -0700 (PDT)
Received: from [10.17.2.218] ([41.203.180.22]) by mx.google.com with ESMTPSA id fv11sm23032232wic.11.2013.05.28.02.46.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 02:46:20 -0700 (PDT)
References: <20130527055257.7635.qmail@joyce.lan> <53F65557-BBF2-4EEE-B9B7-EA228278E289@lacnic.net> <58C856D9-B7F8-455E-9F7E-91E9BEDAAA7E@lca.org.ls> <165383C2-E198-463B-87AE-F2BCE3250914@checkpoint.com> <alpine.BSF.2.00.1305271147270.7155@joyce.lan>
Mime-Version: 1.0 (1.0)
In-Reply-To: <alpine.BSF.2.00.1305271147270.7155@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF8E5A08-9FCE-47D1-BF08-1E092C76E367@lca.org.ls>
X-Mailer: iPad Mail (10B141)
From: Nthabiseng Pule <npule@lca.org.ls>
Subject: Re: Issues in wider geographic participation
Date: Tue, 28 May 2013 11:46:12 +0200
To: John R Levine <johnl@taugh.com>
X-Gm-Message-State: ALoCoQlVoRLSd51r4fGPBEYqsaRBUM0im7+MDEYE9y48LQ3IHHgmctbUHo42ofVyJfME30VQHACV
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 09:46:23 -0000

Sorry, I meant LCD.



Nthabiseng Pule




On 27 May 2013, at 5:48 PM, "John R Levine" <johnl@taugh.com> wrote:

> On Mon, 27 May 2013, Yoav Nir wrote:
>=20
>> LCD?
>=20
> LDC, Less Developed Country, what used to be called the third world, now t=
hat the second has been bought by the first.
>=20
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> "I dropped the toothpaste", said Tom, crestfallenly.

From jabley@hopcount.ca  Tue May 28 03:12:10 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD9F21F91CA for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 03:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HnqVMSmznEd3 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 03:12:10 -0700 (PDT)
Received: from mail-qa0-x230.google.com (mail-qa0-x230.google.com [IPv6:2607:f8b0:400d:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id DA29821F9374 for <ietf@ietf.org>; Tue, 28 May 2013 03:12:09 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id o13so1393908qaj.14 for <ietf@ietf.org>; Tue, 28 May 2013 03:12:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=references:from:mime-version:in-reply-to:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=aYGguuvop68xjZf1l+ZAok4z84rZI/O8e+zEOpmIw4o=; b=PgCBOAH9grLK5jV3ByHCnD7w++eYPkxFfP5PnqLSprqdRwbinxG5bSLa6p1mZzto31 5sXOabm6RY5RsncYAdzz1MNLc/TCm75c7O86nCHNNaUcGfyUpqNqRnfYiWr0UAyGNlGy nudQl15/EwWe2Rarp8T+K/BZRJZfT18UlrB7c=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:from:mime-version:in-reply-to:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=aYGguuvop68xjZf1l+ZAok4z84rZI/O8e+zEOpmIw4o=; b=GSbRr6zJXLq+acSbsr//sCF8CLPDH3ZgSI+y3hauMLVeue28nJKtz3/WE5DzXNzIi3 SohhiDx14Snx607MuM/mF7kP30N2YU2crE1dWfdjcLOVFuX+AUFEudyum73o1NyGnLZv I6/6bvic6qM92J4smlCKcARZzFKNnkx4bi8mf1XcJDKEV4KDe4gC0oT/uFdjj9DIS8vi 396uOvLwqnUkAFz7kvBlvIf+m91Fn5tR6sTPIQhKSb+qjOoO2tOaTwUrTQVb77CBjMS6 ckaAHXJcfOQyoZXLum0vBBl8FxxRSJ1E3RhUOb94MJJoesecL86kbjOT9zKtnX4TSLxY /oyw==
X-Received: by 10.229.76.137 with SMTP id c9mr11598302qck.98.1369735928214; Tue, 28 May 2013 03:12:08 -0700 (PDT)
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <6.2.5.6.2.20130527232315.0c2c56b8@resistor.net>
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
In-Reply-To: <6.2.5.6.2.20130527232315.0c2c56b8@resistor.net>
Date: Tue, 28 May 2013 06:12:08 -0400
Message-ID: <5807146640630736649@unknownmsgid>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQn5cyQtEGiBb0Ik8vvIn+TCLBSddWWUHuaXatZjpWxwxUyKj6uh9Lz/RisL2OgHJ1sWJ6WQ
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 10:12:10 -0000

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

> In theory the IETF does not publish RFCs to suit the regulations of one c=
ountry (see use-case in draft-jabley-dnsext-eui48-eui64-rrtypes-04).  In pr=
actice, the IETF has published a RFC to suit the requirements (it was a vol=
untary measure instead of a formal requirement) of one country.

Note that there's no suggestion that these RRTypes are required by the
CRTC. The example given was for a situation where Interop would have
been beneficial (so that cable resellers have an obvious, stable and
supported way of encoding this kind of information.

> draft-jabley-dnsext-eui48-eui64-rrtypes-04 is an odd case.  My guess is t=
hat the requirements were set because of a problem of monopoly.

The opposite actually: cable operators are required to provide access
to subscribers on behalf of third parties in order to promote
competition. There are multiple such cable providers and multiple such
resellers.

(TekSavvy is one such reseller of multiple cable companies' access networks=
.)

> I have not looked into whether the transfer of data violates the expectat=
ions of the user.

The CRTC's decisions are public, and one might hope they would show
their working. The Canadian courts have been pretty protective of user
privacy in general, I would say.

> I understand that the draft is about standardizing [1] a data format and =
not the transfer of data.  Section 8 of the draft says everything correctly=
 except that it doesn't provide adequate security guidance.

Feel free to point out the gaps, and/or to suggest text.

> I believe that Joe tried to do the "right thing".  I am not comfortable o=
bjecting to publication as I don't know the "path forward".  I personally w=
ould not support publication.  That can easily be overcome and I won't do a=
nything about it.

Thanks for the thoughtful review.


Joe

From dromasca@avaya.com  Tue May 28 04:09:59 2013
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 986D721F96A6 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:09:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.349
X-Spam-Level: 
X-Spam-Status: No, score=-103.349 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iT56qqfLXCJX for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:09:54 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCB821F96A3 for <ietf@ietf.org>; Tue, 28 May 2013 04:09:53 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAAH/ZlHGmAcF/2dsb2JhbABQgmUhNoMuvhoNehZ0gh8BAQEBAxIREVEEAgEIDQQEAQEDAgYdAwICAjAUAQgIAQEEARIIARIHh3IBC6A8iieCQJAlF4EjjUIWEBIGgigyYQOdKYpogwuCKA
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="13114896"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 May 2013 07:09:53 -0400
Received: from unknown (HELO AZ-FFEXHC02.global.avaya.com) ([135.64.58.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 28 May 2013 07:04:20 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0328.009; Tue, 28 May 2013 13:09:51 +0200
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: When to adopt a WG I-D
Thread-Topic: When to adopt a WG I-D
Thread-Index: Ac5bhk7NZ1bJ2lzKSk+IVhI2yJUoXQAC+BaQ
Date: Tue, 28 May 2013 11:09:50 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA179779@AZ-FFEXMB04.global.avaya.com>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 11:09:59 -0000

SGksDQoNCkdvb2Qgd29yay4gSGVyZSBhcmUgYSBmZXcgdGhvdWdodHMgYWZ0ZXIgYSBmaXJzdCBy
ZWFkaW5nLg0KDQotIFdlIHNlZW0gbm90IHRvIGhhdmUgYSBkZWZpbml0aW9uIG9mIHdoYXQgYSBX
RyBJLUQgaXMsIGFsdGhvdWdoIHdlIGtub3cgaG93IHRvIHJlY29nbml6ZSBhIFdHIEktRCBiZWNh
dXNlIG9mIHRoZSBuYW1pbmcgY29udmVudGlvbi4gU28sIGlmIEkgYW0gbm90IG1pc3Rha2VuIHRo
ZSBwaHJhc2UgDQoNCldvcmtpbmcgR3JvdXAgZHJhZnRzIGFyZSBkb2N1bWVudHMgdGhhdCBhcmUg
c3ViamVjdCB0byBJRVRGIFdvcmtpbmcNCiAgIEdyb3VwIHJldmlzaW9uIGNvbnRyb2wuDQoNCmlu
IHNlY3Rpb24gMS4xIGludHJvZHVjZXMgc3VjaCBhIGRlZmluaXRpb24uIElzIGV2ZXJ5Ym9keSBo
YXBweSB3aXRoIHRoaXM/IA0KDQotIEkgYW0gbGFja2luZyBmcm9tIHRoZSBjcml0ZXJpYSBpbiAy
LjIgdGhlIHN0YWJpbGl0eSBvZiB0aGUgdGVjaG5pY2FsIHNvbHV0aW9uIChhcyBwZXIgV0cgY29u
c2Vuc3VzKS4gSW4gbXkgbWluZCB0aGlzIGlzIGluIGN1cnJlbnQgcHJhY3RpY2UgdGhlIHByaW5j
aXBhbCBzcGVjaWZpYyBkaWZmZXJlbmNlIGJldHdlZW4gaW5kaXZpZHVhbCBzdWJtaXNzaW9uIEkt
RHMgYW5kIFdHIEktRHMgLSB0aGUgZmFjdCB0aGF0IHRoZSBJLUQgbWFrZXMgYSBjbGVhciAoaXQg
bWF5IGJlIGRyYWZ0eSBidXQgeWV0IGNsZWFyKSBzdGF0ZW1lbnQgYWJvdXQgd2hhdCB0aGUgdGVj
aG5pY2FsIHNvbHV0aW9uIGlzLiANCg0KLSBJIGxlc3MgbGlrZSB0aGUgZm9sbG93aW5nOiANCg0K
ICAgICAgKiAgSWYgbm90IGFscmVhZHkgaW4gc2NvcGUsIGlzIGEgc2ltcGxlIG1vZGlmaWNhdGlv
biB0byB0aGUNCiAgICAgICAgIGNoYXJ0ZXIgZmVhc2libGUgYW5kIHdhcnJhbnRlZD8NCg0KV2l0
aG91dCBiZWluZyBleHRyZW1lbHkgc3RyaWN0IG9uIHRoZSBwcm9jZXNzIGFzcGVjdCwgSSBiZWxp
ZXZlIHRoYXQgV0dzIHNob3VsZCBub3Qgd29yayBvbiBpdGVtcyB0aGF0IGFyZSBub3QgY2hhcnRl
cmVkLCBhbmQgZXZlbiBsZXNzIGFkb3B0IFdHIEktRHMgb24gbm9uLWNoYXJ0ZXJlZCBpdGVtcy4g
SWYgdGhleSBmZWVsIHRoYXQgc29tZXRoaW5nIGlzIG1pc3NpbmcgZnJvbSB0aGUgY2hhcnRlciB0
aGV5IGNhbiBhc2sgdGhlIEFEcyBmb3IgYSBjaGFydGVyIHVwZGF0ZSwgb3IgZm9yIGFkZGluZyBt
aWxlc3RvbmVzLCB3ZSBoYXZlIHRvZGF5IGF0IGhhbmQgbGlnaHQgcHJvY2Vzc2VzIHdoaWNoIGNh
biBsZWFkIHRvIGZhc3QgaW5jcmVtZW50YWwgYWRkaXRpb25zIHRvIGNoYXJ0ZXJzLCBhbmQgaWYg
dGhlIGFkZGl0aW9uIGlzIG1vcmUgdGhhbiBpbmNyZW1lbnRhbCB0aGFuIGl0IHNob3VsZCBnbyB0
aHJvdWdoIGEgcHJvcGVyIHJlY2hhcnRlcmluZyBwcm9jZXNzLiANCg0KLSAgICAgICogIFdoYXQg
aXMgdGhlIHBvc2l0aW9uIG9mIHRoZSB3b3JraW5nIGdyb3VwIGNoYWlycywgY29uY2VybmluZw0K
ICAgICAgICAgdGhlIGRyYWZ0Pw0KDQogICAgICAgICAgICBbW2VkaXRvciBub3RlOiBJIGFtIG5v
dCBzdXJlIHRoaXMgaXMgcmVsZXZhbnQuICBJbmRlZWQgaXMNCiAgICAgICAgICAgIG1pZ2h0IGJl
IHNwZWNpZmljYWxseSBub3QgcmVsZXZhbnQuICAvYV1dDQoNCk5vdCByZWxldmFudCBJTU8uIA0K
DQpSZWdhcmRzLA0KDQpEYW4NCg0KDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4g
RnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3Jn
XSBPbiBCZWhhbGYgT2YNCj4gQWRyaWFuIEZhcnJlbA0KPiBTZW50OiBUdWVzZGF5LCBNYXkgMjgs
IDIwMTMgMTI6MzMgUE0NCj4gVG86IGlldGZAaWV0Zi5vcmcNCj4gU3ViamVjdDogV2hlbiB0byBh
ZG9wdCBhIFdHIEktRA0KPiANCj4gSGksDQo+IA0KPiBEYXZlIENyb2NrZXIgYW5kIEkgaGF2ZSB0
aGlzIGxpdHRsZSBkcmFmdCBbMV0gZGlzY3Vzc2luZyB0aGUgcHJvY2VzcyBhbmQNCj4gY29uc2lk
ZXJhdGlvbnMgZm9yIGNyZWF0aW5nIGZvcm1hbCB3b3JraW5nIGdyb3VwIGRyYWZ0cyB0aGF0IGFy
ZQ0KPiB0YXJnZXRlZCBmb3IgcHVibGljYXRpb24uDQo+IA0KPiBXZSBiZWxpZXZlIHRoYXQgdGhp
cyBtYXkgaGVscCBjbGFyaWZ5IHNvbWUgb2YgdGhlIGlzc3VlcyBhbmQgY29uY2VybnMNCj4gYXNz
b2NpYXRlZCB3aXRoIHRoaXMgcGFydCBvZiB0aGUgcHJvY2Vzcy4gV2UgYXJlIHRhcmdldGluZyB0
aGlzIGFzDQo+IEluZm9ybWF0aW9uYWwgKGkuZS4gY29tbWVudGFyeSBvbiBleGlzdGluZyBwcm9j
ZXNzLCBub3QgbmV3IG5vcm1hdGl2ZQ0KPiBkZWZpbml0aW9uIG9mIHByb2Nlc3MpIGFuZCB3b3Vs
ZCBsaWtlIHlvdXIgaW5wdXQuDQo+IA0KPiBXaGF0IGlzIG5vdCBjbGVhcj8NCj4gV2hhdCBoYXZl
IHdlIGdvdCB3cm9uZz8NCj4gSG93IHNob3VsZCB3ZSByZXNvbHZlIHRoZSByZW1haW5pbmcgZWRp
dG9yIG5vdGVzPw0KPiANCj4gVGhhbmtzLA0KPiBBZHJpYW4NCj4gKHBlciBwcm8gRGF2ZSkNCj4g
DQo+IFsxXSBodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1jcm9ja2Vy
LWlkLWFkb3B0aW9uLTAyLnR4dA0KPiANCg0K

From tnadeau@lucidvision.com  Tue May 28 04:34:44 2013
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC5821F96CB for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIFdBRWrJjF0 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:34:39 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8B20321F94F5 for <ietf@ietf.org>; Tue, 28 May 2013 04:34:39 -0700 (PDT)
Received: from bartimaeus.thenadeaufarm.com (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 2F09424A8149; Tue, 28 May 2013 07:34:36 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: When to adopt a WG I-D
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
Date: Tue, 28 May 2013 07:34:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDBAB644-4A70-4B25-A44C-0B32CB6814A2@lucidvision.com>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1503)
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, 28 May 2013 11:34:44 -0000

	Nicely written, largely stating what might be obvious for many, =
but still nice to see it in black and white. =20

	A few comments/suggestions:

	1) Section 3.  Authors/Editors


	I suggest that you suggest that WG (co)chair(s) add an editor =
that is unrelated to the draft, but that they trust who has good editing =
skills. As we all well know, that is half the battle for getting a draft =
successfully across the finish line and to the IESG. How many times has =
the IESG seen drafts that are not up to snuff in some =
(editorially-related) manner?  This person might also keep the draft's =
trajectory motivated in the forward progress direction.  Finally, in =
cases where a draft is controversial, this //might// aid in diffusing =
any electric situations.=20

	2) Section 5.2.  Competing Drafts  states:

   Engineering for interesting topics often produces competing,
   interesting proposals.

	I suggest replacing "interesting proposals" with just "competing =
proposals"

	I'd also put a reference here to the point I made above.

	3) A little further in this section, I suggesting amending the =
text a bit from:

	Sometimes,
   multiple versions are formally published, absent consensus among the
   alternatives.

	to something like:

	Sometimes, multiple versions are formally published, absent =
consensus among the
   alternatives. In this way, marketplace economics and preferences are =
allowed to weigh-in on the relevancy of one approach versus the =
other(s).   In these cases, the working group should be prepared to =
revisit the drafts later once a clear preference in the marketplace =
exists. At this time the working group should be prepared to amend, =
narrow or delete the competing approaches as necessary, in order to =
clarify the multiple approaches to as narrow a selection of options as =
possible once the approaches are ready for Proposed Standard status.

	4) There is also no mention of functioning and interoperability =
of implementations, and hence no reference to the "working code" part of =
the mantra. I think it is important to provide some guidance in this =
regard during all phases of the document's states.  For example, two =
competing approaches, but one with running and demonstrable =
interoperating code might cause a WG to err in that direction rather =
than having competing approaches just because a second one was dreamt up =
at the last minute for political reasons.

	--Tom


> Hi,
>=20
> Dave Crocker and I have this little draft [1] discussing the process =
and considerations for creating formal working group drafts that are =
targeted for publication.
>=20
> We believe that this may help clarify some of the issues and concerns =
associated with this part of the process. We are targeting this as =
Informational (i.e. commentary on existing process, not new normative =
definition of process) and would like your input.
>=20
> What is not clear?
> What have we got wrong?
> How should we resolve the remaining editor notes?
>=20
> Thanks,
> Adrian
> (per pro Dave)
>=20
> [1] =
http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>=20
>=20
>=20


From john-ietf@jck.com  Tue May 28 04:56:54 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B0221F8CA5 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gqqh+Dboeg8V for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:56:48 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D484A21F9680 for <ietf@ietf.org>; Tue, 28 May 2013 04:56:48 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UhIWE-0000Ce-NM; Tue, 28 May 2013 07:56:46 -0400
Date: Tue, 28 May 2013 07:56:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
Message-ID: <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com>
In-Reply-To: <m27gij61wi.wl%randy@psg.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.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 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, 28 May 2013 11:56:54 -0000

--On Tuesday, May 28, 2013 15:42 +0900 Randy Bush
<randy@psg.com> wrote:

>... 
>> While the RFC should not be materially misleading, I don't
>> think there is a requirement for Informational RFCs to
>> guarantee any particular level or security or privacy.
> 
> that the draft now tries to slide by as info does not change
> that it specified protocol elements and how they are to be
> used.  and the draft makes very clear that this is
> juristiction specific and a serious privacy problem.

Hmm.   I'm not happy with several aspects of the content of the
draft, including the privacy issue.  I'm also not happy with it
as an apparent example of "if one has a piece of information
that needs to be accessible sometimes, put it in the DNS whether
the characteristics of the DNS are a good match for the
information and retrieval requirements or not".   For those
reasons, and because of the principles expressed in RFC2804, I
believe it was completely unacceptable as a Standards Track
document.

Perhaps these RRTYPEs should never have been created and
registered.  If so, the balance between community review and
maximizing the number of things that are registered (and the
resulting avoidance of conflicts) is wrong for RRTYPEs.  That
would imply a need to revisit the registration policy, but it
wouldn't change the status of these two RRTYPEs.

But it seems to me that none of that is at issue at this stage.  

What is at issue, IMO, is whether the Internet is better off
having a couple of RRTYPEs around with no documentation or
having them documented.  Put differently, are these RRTYPEs
sufficiently reprehensible that we would hope to make them
non-interoperable in practice by not telling people how to make
them work.  I believe that would be a bad plan and would violate
principles far more basic than the 2804 ones -- the IETF should
not be setting itself up as the arbiter of what can be deployed
on the Internet if only because we would certainly fail.

If people find these RRTYPEs (or the document) reprehensible,
then let me suggest that they generate an I-D in Applicability
Statement form that identifies them as "Not Recommended" and
generally obscene and to do so and show sufficient consensus
quickly enough to convince the IESG to force a normative
reference to it into this document so they can be published
together.

I also don't see "slide by as info" in this.  Like you, I
opposed making this standards track and saw serious issues with
2804 in that context.  Tuning aside, only two changes have been
made to the document between -03 and -04 and both are intended
to make it clear that the _description_ of these RRTYPEs does
not constitute a recommendation to use them and that, if one has
serious security concerns that outweigh other considerations,
one should not use them (or put EUI-* information into the DNS
in any other way).   That makes the document about as close to
being information about how these RRTYPEs work without
recommending their use as I can figure out how to get it (others
can probably do better, but apparently haven't stepped forward
with text).  It also contains a pretty strong caution about
their use.  I think that is appropriate too.  It stops short of
saying "not recommended" because the latter would imply
standards track (and Joe might not agree).

>> RFC 2804 is about
> 
> i am very well aware what 2804 contains
> 
>> RFC 2804 doesn't seem to me to be particularly applicable.
> 
> i disagree.  i believe the first two bullets in section one
> are very applicable to joe's draft.
 
>    - The IETF, an international standards body, believes
> itself to be      the wrong forum for designing protocol or
>...

In authorizing the publication of an Informational document that
describes how something works for the information of the
community, the IETF is not acting as an "international standards
body" even though it is being consistent with its goal of making
the Internet better by providing documentation that facilitates
interoperability.  The idea of providing registrations for
non-standardized objects has the same goal.  If we were willing
to register only those objects that met our standards-track
criteria, then we would encourage both code point squatting
(seen in many other cases) or kludges that overload existing
code points (as we have seen with TXT RRs) and damaging
interoperability in both cases.  I don't see the issues in
simply documenting things as different and we certainly have a
long tradition of encouraging the RFC Editor to publish that
type of documentation.

best,
   john


From randy@psg.com  Tue May 28 04:58:45 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 348AA21F96EC for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:58:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9cSl980WPNoE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 04:58:44 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id D90FE21F96EA for <ietf@ietf.org>; Tue, 28 May 2013 04:58:44 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UhIY7-0005bI-5y; Tue, 28 May 2013 11:58:43 +0000
Date: Tue, 28 May 2013 20:58:41 +0900
Message-ID: <m2ehcr48pa.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource	R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
In-Reply-To: <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@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 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, 28 May 2013 11:58:45 -0000

> What is at issue, IMO, is whether the Internet is better off
> having a couple of RRTYPEs around with no documentation or
> having them documented.

there are two solutions to this

randy

From lear@cisco.com  Tue May 28 05:02:43 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 107AE21F9118 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 05:02:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qaxrGKmRHHxH for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 05:02:38 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id C174A21F8F87 for <ietf@ietf.org>; Tue, 28 May 2013 05:02:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=275; q=dns/txt; s=iport; t=1369742557; x=1370952157; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=JHpZleAgG80CtZ2bKK4e30ELzD9IW1GXr3v272P2NLA=; b=KoNEMZzlbI8unOgn2map8hGUJnoMDnrheHGBxVDz25yv6L0mCRWTIS1/ 4GzJa6o8zR7bepI5i9eFvJFIzH8ZPopc3ckSRPPn60ZZbIdlRnCY8IAA7 mRx10KsPoIyzaWpgGd6UGSWlMLin/ZDaBd5nD22FWuluDbmObS1CXObLO c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFACacpFGQ/khN/2dsb2JhbABZgwiDa4hctXyBBBZ0giMBAQEEI1UBEAsYAgIFFgsCAgkDAgECASsaBg0BBwEBiAmqdZEBgSaNdweCQYETA5c7kUCDETo
X-IronPort-AV: E=Sophos;i="4.87,758,1363132800"; d="scan'208";a="154634327"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 28 May 2013 12:02:32 +0000
Received: from mctiny.local ([10.61.201.43]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r4SC2Uwk030405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 May 2013 12:02:31 GMT
Message-ID: <51A49CD6.1060405@cisco.com>
Date: Tue, 28 May 2013 14:02:30 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net>
In-Reply-To: <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 12:02:43 -0000

Hi,

Actually it's not industry that I hear complaining, but individuals.

Eliot

On 5/27/13 10:08 AM, Jari Arkko wrote:
> Melinda wrote:
>> The industry sector bias in IETF participation is
>> possibly compounding the regional bias.
>
> Yes.
>
> Jari
>
>
>


From eburger@standardstrack.com  Tue May 28 05:46:45 2013
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9CBF21F96B8 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 05:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AHUA1bpLAi0 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 05:46:40 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 07B6321F96A3 for <ietf@ietf.org>; Tue, 28 May 2013 05:46:40 -0700 (PDT)
Received: from [141.161.133.241] (port=56626 helo=[10.129.126.122]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger@standardstrack.com>) id 1UhJIO-0002Hc-KN; Tue, 28 May 2013 05:46:37 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_FFE1BF95-DB27-4A0A-9310-16CF202AB2A0"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <51A44EC9.7080100@dcrocker.net>
Date: Tue, 28 May 2013 08:46:36 -0400
Message-Id: <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net>
To: Crocker Dave <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1503)
X-OutGoing-Spam-Status: No, score=1.5
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz104.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 12:46:45 -0000

--Apple-Mail=_FFE1BF95-DB27-4A0A-9310-16CF202AB2A0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Riiight. That is why one never has to attend an IETF meeting in person =
to serve on NOMCOM, one does not need travel support from one's employer =
to be on the IESG, and why people who never come to IETF meetings are =
the rule and not the exception with respect to getting documents adopted =
and published.

Oops - I got my sense wrong there=85.

On May 28, 2013, at 2:29 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 5/27/2013 11:38 PM, Christian O'Flaherty wrote:
>> I would like to follow up on this proposal. Having a meeting in South
>> America scheduled two or three years in advance will let us engage
>> local organisations and individuals on a "project". We did several
>> activities in the region trying to encourage IETF participation, but
>> we're going to be much more effective if they're part of a plan with =
a
>> strong commitment (and effort) from the IETF community.
>=20
>=20
> Such a project sounds like an excellent idea and it could be =
interesting to pursue it with coordination from the IETF community.
>=20
> One point worth noting is that the primary work of the IETF is =
conducted over email.  Consequently, the project does not require an =
in-person meeting with the IETF community.  In fact, relying on an =
in-person meeting for the effort is counter-productive training for =
being effective in the IETF.  I don't mean that such meetings aren't =
useful, but that I believe they are secondary to the work that is done =
over the rest of the time.
>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


--Apple-Mail=_FFE1BF95-DB27-4A0A-9310-16CF202AB2A0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)

iQIcBAEBAgAGBQJRpKcsAAoJEDY/T2tCIPW3elYP/RjI6pwqLRKsBq8y79tcrTru
fBkj5pb790vJOtoM+kUKUdf9+PorsTtUj59wAYRh2H7hNU0sIMchaaXUOehA0trC
VwWQaftaOiR2Q78osfvIAvb+4JOfkzh/bxlvDNoGwfP3XPT19F5VL5c+n2Hvk8kN
VU84eTcaaArYzn4S/VvB+vF41h8yKSPAUnAf8Yb4FzLyjycSmAv0lY9PQNht9tDz
VDpqDbz6MZQNQxP8ZqT06Ani/EGyIBvfuhmPn+ZAOqqoumB6pkU6C+rKBMLXfVT+
wNR8UymzneHEaC0os0unZJP3IDbaLUhRkCJxBAgTXRih2xdsXgMCIeoFufbGazPb
zCixfTT0U/zpNEQiojSug7Vd+xp1MARaiL2aJvQcTjbjHKmFIl3HPa2kLX9KEoqY
mJPB2htTlAeYJzuFzY8+LMG0MNFyWfTQPWxOD8rPc0ORwHKgMvd5ukBe1E6uhP1s
DB8HrXByYEjutZd8skx58sQQl5ZiAX8dCLpKrbetWaEFZVgtP2WlgwmXgAhFBjB8
m/2LZdO8O/UCAm50n3kamdpfhYAj9c5kKsBrrPHxPdbePU9BJQ8mxb008Zyr51zi
lM7dCapFgq0j8c21fiR4cPxNmgK9UHy6WY7YKKvMXyBTkMKno9HOjJFgJtWgkcPg
dRztvIQ3KmqEW8Heoh72
=nk+g
-----END PGP SIGNATURE-----

--Apple-Mail=_FFE1BF95-DB27-4A0A-9310-16CF202AB2A0--

From Ted.Lemon@nominum.com  Tue May 28 06:01:37 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CCDA21F970F for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 06:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.394
X-Spam-Level: 
X-Spam-Status: No, score=-106.394 tagged_above=-999 required=5 tests=[AWL=0.205, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i8QfUFBvTm4H for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 06:01:30 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 7112321F96F9 for <ietf@ietf.org>; Tue, 28 May 2013 06:01:30 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUaSqqoX5b5H2X6AKlf3DHd5Ty9G6uL5a@postini.com; Tue, 28 May 2013 06:01:30 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 09AC91B8053 for <ietf@ietf.org>; Tue, 28 May 2013 06:01:30 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id F2A81190052; Tue, 28 May 2013 06:01:29 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Tue, 28 May 2013 06:01:23 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Eric Burger <eburger@standardstrack.com>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV84TSGHm8o4FqkygKNhv1BO4YZkVEhMAgAAFlwCAAAC7gIAABGOAgAAA3ACAAAF0AIAAAjmAgAAOsICAAAo3gIADonYAgABL0ACAAOJtgIAAlDuAgABpXQCAAAQhAA==
Date: Tue, 28 May 2013 13:01:22 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com>
In-Reply-To: <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <56BE2286F944144097994D560DE2644E@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Crocker Dave <dcrocker@bbiw.net>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 13:01:37 -0000

On May 28, 2013, at 8:46 AM, Eric Burger <eburger@standardstrack.com> wrote=
:
> Riiight. That is why one never has to attend an IETF meeting in person to=
 serve on NOMCOM, one does not need travel support from one's employer to b=
e on the IESG, and why people who never come to IETF meetings are the rule =
and not the exception with respect to getting documents adopted and publish=
ed.

The IETF has a big problem, IMHO, in that effective participation really do=
es currently seem to require meeting attendance.   There's a reason that no=
mcom members have to show up=97if they didn't, they wouldn't be part of the=
 actual culture of IETF, because so much IETF culture is bound up in the ph=
ysical meetings.

The interaction we get in the physical meetings is really important.   I wo=
uld very much like to see the IETF try to discover new ways of using the te=
chnology our forebears (and some remaining senior participants) invented to=
 achieve the same effectiveness without requiring us to all burn tons of fu=
el getting to remote corners of the globe.

But "achieve the same effectiveness" is an important requirement for any su=
ch new solution.   And right now we don't have a solution like that, so we =
do what we do, and you are right that that means that effective participati=
on in the IETF is much easier for people who are able to attend at least a =
sufficiency of meetings on an ongoing basis.   We should see this as a star=
ting point, not as an end state.


From jgunn6@csc.com  Tue May 28 06:55:17 2013
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2FF21F8689; Tue, 28 May 2013 06:55:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ysTeWSyWRiMC; Tue, 28 May 2013 06:55:05 -0700 (PDT)
Received: from mail86.messagelabs.com (mail86.messagelabs.com [216.82.242.179]) by ietfa.amsl.com (Postfix) with ESMTP id 4086B21F8930; Tue, 28 May 2013 06:55:03 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-2.tower-86.messagelabs.com!1369749301!43117169!1
X-Originating-IP: [20.137.2.87]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6776 invoked from network); 28 May 2013 13:55:01 -0000
Received: from unknown (HELO amer-mta101.csc.com) (20.137.2.87) by server-2.tower-86.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 28 May 2013 13:55:01 -0000
Received: from amer-gw09.amer.csc.com (amer-gw09.amer.csc.com [20.6.39.245]) by amer-mta101.csc.com (8.13.8/8.13.8) with ESMTP id r4SDm3HE019872; Tue, 28 May 2013 09:48:11 -0400
In-Reply-To: <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
MIME-Version: 1.0
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
X-KeepSent: 0B0F6222:C5F7395B-85257B79:004C35B7; 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: <OF0B0F6222.C5F7395B-ON85257B79.004C35B7-85257B79.004C6E82@csc.com>
Date: Tue, 28 May 2013 09:54:48 -0400
X-MIMETrack: Serialize by Router on AMER-GW09/SRV/CSC(Release 8.5.2FP3 HF204|September 20, 2011) at 05/28/2013 09:48:49 AM, Serialize complete at 05/28/2013 09:48:49 AM
Content-Type: multipart/alternative; boundary="=_alternative 004C6E4E85257B79_="
Cc: ietf-bounces@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, 28 May 2013 13:55:17 -0000

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

Considering how long and painful the "retrofit" (RFC 4412) for SIP was, 
yes, I think it is important to plan for it early.

Janet

.

ietf-bounces@ietf.org wrote on 05/25/2013 03:10:07 AM:

> From: Jari Arkko <jari.arkko@piuha.net>
> To: James Polk <jmpolk@cisco.com>
> Cc: "ietf@ietf.org list" <ietf@ietf.org>
> Date: 05/25/2013 03:10 AM
> Subject: WebRTC and emergency communications (Was: Re: IETF Meeting 
> in South America)
> Sent by: ietf-bounces@ietf.org
> 
> James:
> 
> > did you know that you have a audio/video realtime interactive 
> communications WG churning out proposals and solutions that is 
> *actively* ignoring "emergency communications" in its entirety? No? 
> Look at RTCweb, which will become a dominant form of interactive 
> communications between humans in the near future. You have an 
> equally active WG in the same area that is addressing emergency 
> communications (ECRIT) that is further along/mature in its documents
> (i.e., they've already produced the bulk of their RFCs, specifically
> RFC 6443 and 6881).
> > 
> > Given that young people already think contacting a local emergency
> call center (PSAP) can or should be achievable through SMS, IM, 
> twitter and Facebook... just how long does anyone think it will be 
> before calling 911/112/999 will be requested or mandated through 
> WEBrtc/RTCweb?
> > 
> > Waiting will only make it more painful to retrofit it into the 
> future RFCs produced by RTCweb.
> 
> I knew that WebRTC is happening fast, including implementations 
> coming out before standards. I don't think everyone have yet 
> realised the full impact this technology will have.
> 
> I didn't know about the details of the emergency communications 
> situation. But it is always difficult to balance getting something 
> out early vs. complete. I know how much pressure there is on the 
> working groups to keep up with things actually happening in the 
> browsers and organisations setting up to use this technology. Do you
> think the retrofit will be problematic, and do you have a specific 
> suggestion about what should be included today?
> 
> Jari
> 

--=_alternative 004C6E4E85257B79_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Considering how long and painful the &quot;retrofit&quot;
(RFC 4412) for SIP was, yes, I think it is important to plan for it early.</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
<br>
.</font>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 05/25/2013 03:10:07
AM:<br>
<br>
&gt; From: Jari Arkko &lt;jari.arkko@piuha.net&gt;</font></tt>
<br><tt><font size=2>&gt; To: James Polk &lt;jmpolk@cisco.com&gt;</font></tt>
<br><tt><font size=2>&gt; Cc: &quot;ietf@ietf.org list&quot; &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 05/25/2013 03:10 AM</font></tt>
<br><tt><font size=2>&gt; Subject: WebRTC and emergency communications
(Was: Re: IETF Meeting <br>
&gt; in South America)</font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; James:<br>
&gt; <br>
&gt; &gt; did you know that you have a audio/video realtime interactive
<br>
&gt; communications WG churning out proposals and solutions that is <br>
&gt; *actively* ignoring &quot;emergency communications&quot; in its entirety?
No? <br>
&gt; Look at RTCweb, which will become a dominant form of interactive <br>
&gt; communications between humans in the near future. You have an <br>
&gt; equally active WG in the same area that is addressing emergency <br>
&gt; communications (ECRIT) that is further along/mature in its documents<br>
&gt; (i.e., they've already produced the bulk of their RFCs, specifically<br>
&gt; RFC 6443 and 6881).<br>
&gt; &gt; <br>
&gt; &gt; Given that young people already think contacting a local emergency<br>
&gt; call center (PSAP) can or should be achievable through SMS, IM, <br>
&gt; twitter and Facebook... just how long does anyone think it will be
<br>
&gt; before calling 911/112/999 will be requested or mandated through <br>
&gt; WEBrtc/RTCweb?<br>
&gt; &gt; <br>
&gt; &gt; Waiting will only make it more painful to retrofit it into the
<br>
&gt; future RFCs produced by RTCweb.<br>
&gt; <br>
&gt; I knew that WebRTC is happening fast, including implementations <br>
&gt; coming out before standards. I don't think everyone have yet <br>
&gt; realised the full impact this technology will have.<br>
&gt; <br>
&gt; I didn't know about the details of the emergency communications <br>
&gt; situation. But it is always difficult to balance getting something
<br>
&gt; out early vs. complete. I know how much pressure there is on the <br>
&gt; working groups to keep up with things actually happening in the <br>
&gt; browsers and organisations setting up to use this technology. Do you<br>
&gt; think the retrofit will be problematic, and do you have a specific
<br>
&gt; suggestion about what should be included today?<br>
&gt; <br>
&gt; Jari<br>
&gt; <br>
</font></tt>
--=_alternative 004C6E4E85257B79_=--

From rsouza.rjo@gmail.com  Fri May 24 10:28:43 2013
Return-Path: <rsouza.rjo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21C1C21F90FD for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.469
X-Spam-Level: 
X-Spam-Status: No, score=-1.469 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_LWOILCO=1.13]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvuWG6Qi+4JS for <ietf@ietfa.amsl.com>; Fri, 24 May 2013 10:28:42 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9AF21F8F27 for <ietf@ietf.org>; Fri, 24 May 2013 10:28:42 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id at1so12974727iec.35 for <ietf@ietf.org>; Fri, 24 May 2013 10:28:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2+PV5kQtgU+OGtXWhLpt/1SPyuEuyv+wQ1vlRD1kn5w=; b=tpWmZb5zYjXL5eK1QmwM7JDQVmXYeNt1w/4tOC0PCRMVtoA402pluEmJDISKinde71 MZpr+4ep5pry6rWuSBICpDAw0/MUeVvCZZvgAKHnHlBo0v0RqD5+snvDDqsvNYwvDQiN 6tOkjM0H2h6zJLdSoZ/C6J8LiygEXPrEvHC11nI8q7oRxK6DcKzzdN5ImF6XDp1lA1m+ nr4gwlk/4YBvWzs+wuQlORtx4ShfXYSI93V4c90+RfKiZmYLnkSdk3eSJ16f428aqWBj wVwC7HuMlAfVYbjDKOoda0joAlQY9a93qiFCOMzuYcvlsxN2beWecgB+VQcQnwfekbtR v58g==
MIME-Version: 1.0
X-Received: by 10.50.114.131 with SMTP id jg3mr80598igb.75.1369416522011; Fri, 24 May 2013 10:28:42 -0700 (PDT)
Received: by 10.50.125.6 with HTTP; Fri, 24 May 2013 10:28:41 -0700 (PDT)
Date: Fri, 24 May 2013 14:28:41 -0300
Message-ID: <CAOBNHyeQ9uVn8E=heSf_+JQbp=Zd9K49wpct7gDB0bK5rV8bww@mail.gmail.com>
Subject: [Isoc-br] IETF Meeting in South America
From: Rogerio Mariano <rsouza.rjo@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e0122ac4c58670504dd7a2114
X-Mailman-Approved-At: Tue, 28 May 2013 06:58:11 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 May 2013 17:32:23 -0000

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

Dear IETF Managers,

My name is Rog=E9rio Mariano and I`m a member of the Internet Society (Glob=
al
Member # 339380) and a student of Internet Governance Programme (IGCBP)
DiploFoundation and Consultant for the definition and operation of the
Service Provider direction related to the technical architecture of Routing
Protocols and Core Infrastructure components in the Petrobras Oil company
(largest company in Brazil).  Over 14 years of management experience
working and leading a group of engineers engaged in a variety of projects
and operations spanning areas such as MPLS, routing, Internet and services.
Active participant in standards bodies and industry forums such as ISOC,
IETF, NIC.br and GTER.

About IETF in LATAM

We feel really miss the action of engineers and professionals in Latin
America within the IETF to improve the quality of the Internet in Latin
America and spread its use, with special attention to its technical and
infrastructure. For these issues is very important to have a performance of
the IETF in Latin America, since we already have strong groups like LACNIC,
the ISOC.br the NIC.br and meetings as well as the products GTER the LACNOG
events and chapters ISOC. I think there are people in Latin America who can
encourage and contribute in various aspects such as: infrastructure and
standardization / standardization and standards for various segments mainly
as a BOF or WG in the IETF.

Regards,

Rog=E9rio Mariano de Souza
+ 55 21 8314-9647

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

<div dir=3D"ltr"><div>Dear IETF Managers,<br><br>My name is Rog=E9rio Maria=
no and I`m a member of the Internet Society (Global Member # 339380) and a =
student of Internet Governance Programme (IGCBP) DiploFoundation and Consul=
tant for the definition and operation of the Service Provider direction rel=
ated to the technical architecture of Routing Protocols and Core Infrastruc=
ture components in the Petrobras Oil company (largest company in Brazil).=
=A0 Over 14 years of management experience working and leading a group of e=
ngineers engaged in a variety of projects and operations spanning areas suc=
h as MPLS, routing, Internet and services. Active participant in standards =
bodies and industry forums such as ISOC, IETF, NIC.br and GTER. <br>
<br></div>About IETF in LATAM<br><div><br>We feel really miss the action of=
 engineers and professionals in Latin America within the IETF to improve th=
e quality of the Internet in Latin America and spread its use, with special=
 attention to its technical and infrastructure. For these issues is very im=
portant to have a performance of the IETF in Latin America, since we alread=
y have strong groups like LACNIC, the ISOC.br the NIC.br and meetings as we=
ll as the products GTER the LACNOG events and chapters ISOC. I think there =
are people in Latin America who can encourage and contribute in various asp=
ects such as: infrastructure and standardization / standardization and stan=
dards for various segments mainly as a BOF or WG in the IETF.<br>
<br></div><div>Regards,<br><br></div><div>Rog=E9rio Mariano de Souza<br>+ 5=
5 21 8314-9647<br></div></div>

--089e0122ac4c58670504dd7a2114--

From yaojk@cnnic.cn  Sun May 26 18:49:47 2013
Return-Path: <yaojk@cnnic.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F56921F95E5 for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 18:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.294
X-Spam-Level: 
X-Spam-Status: No, score=-99.294 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dsb+wj25xOMm for <ietf@ietfa.amsl.com>; Sun, 26 May 2013 18:49:42 -0700 (PDT)
Received: from cnnic.cn (unknown [218.241.105.202]) by ietfa.amsl.com (Postfix) with SMTP id 3DDD221F937A for <ietf@ietf.org>; Sun, 26 May 2013 18:49:40 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: yaojk@cnnic.cn
Received: from unknown127.0.0.1 (HELO healthyao-think) (127.0.0.1) by 127.0.0.1 with SMTP; Mon, 27 May 2013 09:49:33 +0800
Date: Mon, 27 May 2013 09:49:32 +0800
From: "Jiankang Yao" <yaojk@cnnic.cn>
To: "Abdussalam Baryun" <abdussalambaryun@gmail.com>,  SM <sm@resistor.net>
Subject: Re: Re: More participation from under-represented regions (was: IETF Meeting in South America)
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net>,  <CADnDZ889Wo_1fdF77W0yxnQAAKD=opr3ah4F-afzOfb5+MYQPg@mail.gmail.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2013052709492539008318@cnnic.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart412582500516_=----"
X-Mailman-Approved-At: Tue, 28 May 2013 06:58:11 -0700
Cc: ietf <ietf@ietf.org>, dcrocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: yaojk <yaojk@cnnic.cn>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 01:49:47 -0000

This is a multi-part message in MIME format.

------=_001_NextPart412582500516_=----
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: base64

DQpJIHN1cHBvcnQgdG8gdHJ5IHRoZSBuZXcgbWVldGluZyBzaXRlcyBzdWNoIGFzIFNvdXRoIEFt
ZXJpY2Egb3IgQWZyaWNhLg0KDQoNCg0KDQpKaWFua2FuZyBZYW8NCg0KRnJvbTogQWJkdXNzYWxh
bSBCYXJ5dW4NCkRhdGU6IDIwMTMtMDUtMjcgMDc6MzgNClRvOiBTTQ0KQ0M6IGlldGY7IGRjcm9j
a2VyDQpTdWJqZWN0OiBSZTogTW9yZSBwYXJ0aWNpcGF0aW9uIGZyb20gdW5kZXItcmVwcmVzZW50
ZWQgcmVnaW9ucyAod2FzOiBJRVRGIE1lZXRpbmcgaW4gU291dGggQW1lcmljYSkNCkkgc3VwcG9y
dCB0byBhZGQgdGhlIG5ldyByZWdpb24sIGhvcGluZyBpbiBmdXR1cmUgQWZyaWNhIGdldHMgaXRz
DQpjaGFuY2UuIElNTywgSSB0aG91Z2h0IGFib3V0IGl0IGZyb20gYW5vdGhlciBwb2ludCBvZiB2
aWV3LiBBZnRlciBhDQpsb25nIHRpbWUgb2YgaGF2aW5nIElFVEYgbWVldGluZ3MgbW9zdGx5IGlu
IG9uZSByZWdpb24gKGFzIGhpc3Rvcnkgb2YNCk5vcnRoIEFtZXJpY2EgcmVnaW9uIGdhaW5pbmcg
bW9zdCBtZWV0aW5ncyksIHRoZSByZXN1bHQgb2YgdGhhdCB3YXMNCnRoYXQgSUVURiBwYXJ0aWNp
cGFudHMgYXJlIG1ham9yaXR5IGZyb20gTm9ydGggQW1lcmljYSwgc28gSSB0aGluayBpdA0KTUFZ
IGJlIGEgcmVzdWx0IG9mIG1lZXRpbmdzIGhlbGQgaW4gb25lIHJlZ2lvbiAoc29tZSB3aWxsIGFy
Z3VlIGl0IGlzDQpiZWNhdXNlIGV4cGVydHMgaW5kaXZpZHVhbC1wYXJ0aWNpcGFudHMvY29tcGFu
eS1wYXJ0aWNpcGFudHMgY29tZSBmcm9tDQpOb3J0aCBBbWVyaWNhLCB3aGlsZSBnaXZpbmcgbm8g
dmFsdWUgb2YgSUVURiBtYXJrZXRpbmcpLCAgSG93ZXZlciwNCklFVEYgY2xhaW1zIGl0IGlzIGZv
ciB0aGUgV09STEQgYXMgSW50ZXJuZXQgaXMsIG5vdCBmb3Igb25seSBvbmUNCnJlZ2lvbidzIElu
dGVybmV0LiBTbyBnaXZpbmcgbm93IGNoYW5jZSBmb3Igb3RoZXIgcmVnaW9ucyAob3IgZGl2ZXJz
ZQ0KSW50ZXJuZXQgY29tbXVuaXRpZXMpIHRvIGdhaW4gbWVldGluZ3Mgd2lsbCBoZWxwIGluIHRo
ZSBGVVRVUkUgbW9yZQ0KcGFydGljaXBhbnRzIGZyb20gb3RoZXIgcmVnaW9ucyBhcyBpdCBoYXBw
ZW5kIHRvIE5vcnRoIEFtZXJpY2EuDQoNCiBGb3IgSUVURiBpdCBhbHJlYWR5IGdhaW5lZCBtYW55
IGZyb20gTm9ydGggYW1lcmljYSwgYW5kIHRoZXkgZG9uJ3QNCmluY3JlYXNlIHNvIGl0IFNIT1VM
RCBtYXJrZXQgZWxzZXdoZXJlIGZvciBmdXR1cmUgcGxhbnMuIE15IGFuc3dlcnMgdG8NCnlvdXIg
cXVlc3Rpb25zIGJlbG93LA0KDQpBQg0KDQpPbiA1LzI2LzEzLCBTTSA8c21AcmVzaXN0b3IubmV0
PiB3cm90ZToNCj4gQXQgMDk6NDIgMjYtMDUtMjAxMywgRGF2ZSBDcm9ja2VyIHdyb3RlOg0KPj5J
IGxpa2UgdmlzaXRpbmcgU291dGggQW1lcmljYS4gIEJ1dCBJRVRGIG1lZXRpbmdzIGRvIG5vdCBo
YXZlDQo+PnRvdXJpc20gYXMgYSBnb2FsLiAgU28geWVzLCBJJ20gc3VyZSB0aG9zZSB3aG8gZ28g
d2lsbCAiZW5qb3kiIHRoZQ0KPj5jaXR5OyBidXQgYWdhaW4sIHRoYXQncyBub3Qgc3RhdGVkIHB1
cnBvc2Ugb2YgY2hvb3NpbmcgdmVudWVzLg0KPg0KPiBPdmVyIGEgeWVhciBhZ28gInRoZSBJQU9D
IFt3YXNdIHBsZWFzZWQgdG8gYW5ub3VuY2UgdGhlIFJldHVybiBvZiB0aGUNCj4gTmVyZHMgdG8g
UGFyYWRpc2UhIg0KPg0KPj5JZiB3ZSBhcmUgc2VyaW91cyBhYm91dCB3YW50aW5nIG1vcmUgcGFy
dGljaXBhdGlvbiBmcm9tDQo+PnVuZGVyLXJlcHJlc2VudGVkIHJlZ2lvbnMsIHRoZW4gbGV0J3Mg
YXR0YWNrIHRoYXQgaXNzdWUgc2VyaW91c2x5DQo+PmFuZCBzdWJzdGFudGl2ZWx5LCByYXRoZXIg
dGhhbiB3aXRoIGFuIGV4cGVuc2l2ZSBtYXJrZXRpbmcgc2hvdy4NCj4NCj4gWWVzLg0KPg0KPiBU
aGUgbWVhbmluZyBvZiAidGhlIGVsZXBoYW50IGluIHRoZSByb29tIiBpcyAiYW4gaW1wb3J0YW50
IGFuZA0KPiBvYnZpb3VzIHRvcGljLCB3aGljaCBldmVyeW9uZSBwcmVzZW50IGlzIGF3YXJlIG9m
LCBidXQgd2hpY2ggaXNuJ3QNCj4gZGlzY3Vzc2VkLCBhcyBzdWNoIGRpc2N1c3Npb24gaXMgY29u
c2lkZXJlZCB0byBiZQ0KPiB1bmNvbWZvcnRhYmxlIi4gIFRoZSBlbGVwaGFudCBpbiB0aGUgcm9v
bSBpcyB0aGF0IHRoZXJlIGhhc24ndCBiZWVuDQo+IGFueSBkaXNjdXNzaW9uIGFib3V0IHdoYXQg
aGFzIGJlZW4gZG9uZSB0byBnZXQgbW9yZSBwYXJ0aWNpcGF0aW9uDQo+IGZyb20gdW5kZXItcmVw
cmVzZW50ZWQgcmVnaW9ucyBidXQgbm9ib2R5IGhhcyBtZW50aW9uZWQgdGhhdC4NCj4NCj4gICAo
YSkgV2FzIHRoZSBJRVNHIHdvcmtpbmcgb24gaG93IHRvIGdldCBtb3JlIHBhcnRpY2lwYXRpb24g
ZnJvbQ0KPiAgICAgICB1bmRlci1yZXByZXNlbnRlZCByZWdpb25zPw0KDQpJIHRoaW5rIHRoZXkg
U0hPVUxEIGhhdmUsIGFuZCBhbGwgb2YgdXMgc2hvdWxkIGRvIHRoZSBzYW1lLCBiZWNhdXNlDQpJ
RVRGIHdpbGwgZXhwYW5kIGFuZCBiZWNvbWUgc3Ryb25nZXIgYnkgaW5jcmVhc2luZyBwYXJ0aWNp
cGFudHMgZnJvbQ0KQUxMIEludGVybmV0IGNvbW11bml0eSByZWdpb25zLiBUaGUgYW5zd2VycyBh
bHNvIGJhc2VkIG9uIElFVEYgdmVzaW9uLg0KPg0KPiAgIChiKSBXYXMgdGhlIElBQiB3b3JraW5n
IG9uIGhvdyB0byBnZXQgbW9yZSBwYXJ0aWNpcGF0aW9uIGZyb20NCj4gICAgICAgdW5kZXItcmVw
cmVzZW50ZWQgcmVnaW9ucz8NCg0KSSB0aGluayB0aGV5IFNIT1VMRCBoYXZlLCBhbmQgYWxsIG9m
IHVzIHNob3VsZCBkbyB0aGUgc2FtZSwgYmVjYXVzZQ0KSUVURiB3aWxsIGV4cGFuZCBhbmQgYmVj
b21lIHN0cm9uZ2VyIGJ5IGluY3JlYXNpbmcgcGFydGljaXBhbnRzIGZyb20NCkFMTCBJbnRlcm5l
dCBjb21tdW5pdHkgcmVnaW9ucy4gVGhlIGFuc3dlcnMgYWxzbyBiYXNlZCBvbiBJRVRGIHZlc2lv
bi4NCg0KPg0KPiBJIGFtIGFza2luZyB0aGUgYWJvdmUgcXVlc3Rpb25zIGFzIGl0IGlzIG5vdCBj
bGVhciB3aG8gaW4gdGhlIElFVEYNCj4gd2FzIGRvaW5nIHRoYXQuDQoNCkkgYW0gd29ya2luZyBv
biBpdCBteSBzZWxmLCBzbyBJIGhvcGUgb3RoZXJzIHRoaW5rIHRoZSBzYW1lLCBJIGhhdmUNCmFz
a2VkIG1hbnkgc3R1ZGVudHMgYWJvdXQgdGhlIElFVEYsIHRoZXkgZG9uJ3Qga25vdyBhYm91dCBp
dCBhIHRoaW5nLA0Kc28gc2hvdWxkIG4ndCB3ZSBhc2sgcXVlc3Rpb24gd2h5IHRoZSBjb21tdW5p
dHkgb2YgSW50ZXJuZXQgdXNlcnMgaW4NClNvdXRoIEFtZXJpY2Egbm90IHBhcnRpY2lwYXRpbmc/
IE9uZSBhbnN3ZXIgY2FuIGJlIHRoYXQgdGhlIHJlYXNvbiBpcw0KdGhhdCBJRVRGIHBhcnRpY2lw
YW50cyBtYWpvcml0eSBmcm9tIE5vcnRoIEFtZXJpY2EgYW5kIHRoZXkgZG9uJ3Qgd2FudA0KdG8g
c3BlbmQgbW9uZXkgb24gbG9uZyBqb3VybmllcyB0aGF0IGluY2x1ZGUgbWFueSBjb21wZXRpbmcg
cmVnaW9ucw0KKGUuZy4gZmV3IHJlZ2lvbnMgb3IgZmV3IGxvbmcgZGlzdGFuY2UgcGVyIHllYXIg
bWF5YmUgZmluZSkuDQoNCj4NCj4gUmVnYXJkcywNCj4gLXNtDQo+DQo+

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Typ=
e>
<STYLE>
BLOCKQUOTE {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
BODY {
	LINE-HEIGHT: 1.5; FONT-FAMILY: verdana; COLOR: #000000; FONT-SIZE: 10pt
}
P {
	MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>

<META name=3DGENERATOR content=3D"MSHTML 8.00.7601.18129"></HEAD>
<BODY style=3D"MARGIN: 10px">
<DIV style=3D"FONT-FAMILY: Verdana">&nbsp;</DIV>
<DIV style=3D"FONT-FAMILY: Verdana">I support to try the new meeting sites=
 such as=20
South America or Africa.</DIV>
<DIV style=3D"FONT-FAMILY: Verdana">&nbsp;</DIV>
<HR style=3D"WIDTH: 210px; HEIGHT: 1px" align=3Dleft color=3D#b5c4df SIZE=
=3D1>

<DIV style=3D"FONT-FAMILY: Verdana"><SPAN>Jiankang Yao</SPAN></DIV>
<DIV>&nbsp;</DIV>
<DIV=20
style=3D"BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOT=
TOM: 0cm; PADDING-LEFT: 0cm; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt s=
olid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<DIV=20
style=3D"PADDING-BOTTOM: 8px; PADDING-LEFT: 8px; PADDING-RIGHT: 8px; BACKG=
ROUND: #efefef; COLOR: #000000; FONT-SIZE: 12px; PADDING-TOP: 8px">
<DIV><B>From:</B>&nbsp;<A href=3D"mailto:abdussalambaryun@gmail.com">Abdus=
salam=20
Baryun</A></DIV>
<DIV><B>Date:</B>&nbsp;2013-05-27&nbsp;07:38</DIV>
<DIV><B>To:</B>&nbsp;<A href=3D"mailto:sm@resistor.net">SM</A></DIV>
<DIV><B>CC:</B>&nbsp;<A href=3D"mailto:ietf@ietf.org">ietf</A>; <A=20
href=3D"mailto:dcrocker@bbiw.net">dcrocker</A></DIV>
<DIV><B>Subject:</B>&nbsp;Re: More participation from under-represented re=
gions=20
(was: IETF Meeting in South America)</DIV></DIV></DIV>
<DIV>
<DIV>I&nbsp;support&nbsp;to&nbsp;add&nbsp;the&nbsp;new&nbsp;region,&nbsp;h=
oping&nbsp;in&nbsp;future&nbsp;Africa&nbsp;gets&nbsp;its</DIV>
<DIV>chance.&nbsp;IMO,&nbsp;I&nbsp;thought&nbsp;about&nbsp;it&nbsp;from&nb=
sp;another&nbsp;point&nbsp;of&nbsp;view.&nbsp;After&nbsp;a</DIV>
<DIV>long&nbsp;time&nbsp;of&nbsp;having&nbsp;IETF&nbsp;meetings&nbsp;mostl=
y&nbsp;in&nbsp;one&nbsp;region&nbsp;(as&nbsp;history&nbsp;of</DIV>
<DIV>North&nbsp;America&nbsp;region&nbsp;gaining&nbsp;most&nbsp;meetings),=
&nbsp;the&nbsp;result&nbsp;of&nbsp;that&nbsp;was</DIV>
<DIV>that&nbsp;IETF&nbsp;participants&nbsp;are&nbsp;majority&nbsp;from&nbs=
p;North&nbsp;America,&nbsp;so&nbsp;I&nbsp;think&nbsp;it</DIV>
<DIV>MAY&nbsp;be&nbsp;a&nbsp;result&nbsp;of&nbsp;meetings&nbsp;held&nbsp;i=
n&nbsp;one&nbsp;region&nbsp;(some&nbsp;will&nbsp;argue&nbsp;it&nbsp;is</DI=
V>
<DIV>because&nbsp;experts&nbsp;individual-participants/company-participant=
s&nbsp;come&nbsp;from</DIV>
<DIV>North&nbsp;America,&nbsp;while&nbsp;giving&nbsp;no&nbsp;value&nbsp;of=
&nbsp;IETF&nbsp;marketing),&nbsp;&nbsp;However,</DIV>
<DIV>IETF&nbsp;claims&nbsp;it&nbsp;is&nbsp;for&nbsp;the&nbsp;WORLD&nbsp;as=
&nbsp;Internet&nbsp;is,&nbsp;not&nbsp;for&nbsp;only&nbsp;one</DIV>
<DIV>region's&nbsp;Internet.&nbsp;So&nbsp;giving&nbsp;now&nbsp;chance&nbsp=
;for&nbsp;other&nbsp;regions&nbsp;(or&nbsp;diverse</DIV>
<DIV>Internet&nbsp;communities)&nbsp;to&nbsp;gain&nbsp;meetings&nbsp;will&=
nbsp;help&nbsp;in&nbsp;the&nbsp;FUTURE&nbsp;more</DIV>
<DIV>participants&nbsp;from&nbsp;other&nbsp;regions&nbsp;as&nbsp;it&nbsp;h=
append&nbsp;to&nbsp;North&nbsp;America.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;For&nbsp;IETF&nbsp;it&nbsp;already&nbsp;gained&nbsp;many&nbsp;f=
rom&nbsp;North&nbsp;america,&nbsp;and&nbsp;they&nbsp;don't</DIV>
<DIV>increase&nbsp;so&nbsp;it&nbsp;SHOULD&nbsp;market&nbsp;elsewhere&nbsp;=
for&nbsp;future&nbsp;plans.&nbsp;My&nbsp;answers&nbsp;to</DIV>
<DIV>your&nbsp;questions&nbsp;below,</DIV>
<DIV>&nbsp;</DIV>
<DIV>AB</DIV>
<DIV>&nbsp;</DIV>
<DIV>On&nbsp;5/26/13,&nbsp;SM&nbsp;&lt;sm@resistor.net&gt;&nbsp;wrote:</DI=
V>
<DIV>&gt;&nbsp;At&nbsp;09:42&nbsp;26-05-2013,&nbsp;Dave&nbsp;Crocker&nbsp;=
wrote:</DIV>
<DIV>&gt;&gt;I&nbsp;like&nbsp;visiting&nbsp;South&nbsp;America.&nbsp;&nbsp=
;But&nbsp;IETF&nbsp;meetings&nbsp;do&nbsp;not&nbsp;have</DIV>
<DIV>&gt;&gt;tourism&nbsp;as&nbsp;a&nbsp;goal.&nbsp;&nbsp;So&nbsp;yes,&nbs=
p;I'm&nbsp;sure&nbsp;those&nbsp;who&nbsp;go&nbsp;will&nbsp;"enjoy"&nbsp;th=
e</DIV>
<DIV>&gt;&gt;city;&nbsp;but&nbsp;again,&nbsp;that's&nbsp;not&nbsp;stated&n=
bsp;purpose&nbsp;of&nbsp;choosing&nbsp;venues.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;Over&nbsp;a&nbsp;year&nbsp;ago&nbsp;"the&nbsp;IAOC&nbsp;[wa=
s]&nbsp;pleased&nbsp;to&nbsp;announce&nbsp;the&nbsp;Return&nbsp;of&nbsp;th=
e</DIV>
<DIV>&gt;&nbsp;Nerds&nbsp;to&nbsp;Paradise!"</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&gt;If&nbsp;we&nbsp;are&nbsp;serious&nbsp;about&nbsp;wanting&nbsp=
;more&nbsp;participation&nbsp;from</DIV>
<DIV>&gt;&gt;under-represented&nbsp;regions,&nbsp;then&nbsp;let's&nbsp;att=
ack&nbsp;that&nbsp;issue&nbsp;seriously</DIV>
<DIV>&gt;&gt;and&nbsp;substantively,&nbsp;rather&nbsp;than&nbsp;with&nbsp;=
an&nbsp;expensive&nbsp;marketing&nbsp;show.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;Yes.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;The&nbsp;meaning&nbsp;of&nbsp;"the&nbsp;elephant&nbsp;in&nb=
sp;the&nbsp;room"&nbsp;is&nbsp;"an&nbsp;important&nbsp;and</DIV>
<DIV>&gt;&nbsp;obvious&nbsp;topic,&nbsp;which&nbsp;everyone&nbsp;present&n=
bsp;is&nbsp;aware&nbsp;of,&nbsp;but&nbsp;which&nbsp;isn't</DIV>
<DIV>&gt;&nbsp;discussed,&nbsp;as&nbsp;such&nbsp;discussion&nbsp;is&nbsp;c=
onsidered&nbsp;to&nbsp;be</DIV>
<DIV>&gt;&nbsp;uncomfortable".&nbsp;&nbsp;The&nbsp;elephant&nbsp;in&nbsp;t=
he&nbsp;room&nbsp;is&nbsp;that&nbsp;there&nbsp;hasn't&nbsp;been</DIV>
<DIV>&gt;&nbsp;any&nbsp;discussion&nbsp;about&nbsp;what&nbsp;has&nbsp;been=
&nbsp;done&nbsp;to&nbsp;get&nbsp;more&nbsp;participation</DIV>
<DIV>&gt;&nbsp;from&nbsp;under-represented&nbsp;regions&nbsp;but&nbsp;nobo=
dy&nbsp;has&nbsp;mentioned&nbsp;that.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;(a)&nbsp;Was&nbsp;the&nbsp;IESG&nbsp;working&nb=
sp;on&nbsp;how&nbsp;to&nbsp;get&nbsp;more&nbsp;participation&nbsp;from</DI=
V>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;under-represented&nbsp;=
regions?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;think&nbsp;they&nbsp;SHOULD&nbsp;have,&nbsp;and&nbsp;all&nbsp;=
of&nbsp;us&nbsp;should&nbsp;do&nbsp;the&nbsp;same,&nbsp;because</DIV>
<DIV>IETF&nbsp;will&nbsp;expand&nbsp;and&nbsp;become&nbsp;stronger&nbsp;by=
&nbsp;increasing&nbsp;participants&nbsp;from</DIV>
<DIV>ALL&nbsp;Internet&nbsp;community&nbsp;regions.&nbsp;The&nbsp;answers&=
nbsp;also&nbsp;based&nbsp;on&nbsp;IETF&nbsp;vesion.</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;&nbsp;&nbsp;(b)&nbsp;Was&nbsp;the&nbsp;IAB&nbsp;working&nbs=
p;on&nbsp;how&nbsp;to&nbsp;get&nbsp;more&nbsp;participation&nbsp;from</DIV=
>
<DIV>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;under-represented&nbsp;=
regions?</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;think&nbsp;they&nbsp;SHOULD&nbsp;have,&nbsp;and&nbsp;all&nbsp;=
of&nbsp;us&nbsp;should&nbsp;do&nbsp;the&nbsp;same,&nbsp;because</DIV>
<DIV>IETF&nbsp;will&nbsp;expand&nbsp;and&nbsp;become&nbsp;stronger&nbsp;by=
&nbsp;increasing&nbsp;participants&nbsp;from</DIV>
<DIV>ALL&nbsp;Internet&nbsp;community&nbsp;regions.&nbsp;The&nbsp;answers&=
nbsp;also&nbsp;based&nbsp;on&nbsp;IETF&nbsp;vesion.</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;I&nbsp;am&nbsp;asking&nbsp;the&nbsp;above&nbsp;questions&nb=
sp;as&nbsp;it&nbsp;is&nbsp;not&nbsp;clear&nbsp;who&nbsp;in&nbsp;the&nbsp;I=
ETF</DIV>
<DIV>&gt;&nbsp;was&nbsp;doing&nbsp;that.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I&nbsp;am&nbsp;working&nbsp;on&nbsp;it&nbsp;my&nbsp;self,&nbsp;so&nbs=
p;I&nbsp;hope&nbsp;others&nbsp;think&nbsp;the&nbsp;same,&nbsp;I&nbsp;have<=
/DIV>
<DIV>asked&nbsp;many&nbsp;students&nbsp;about&nbsp;the&nbsp;IETF,&nbsp;the=
y&nbsp;don't&nbsp;know&nbsp;about&nbsp;it&nbsp;a&nbsp;thing,</DIV>
<DIV>so&nbsp;should&nbsp;n't&nbsp;we&nbsp;ask&nbsp;question&nbsp;why&nbsp;=
the&nbsp;community&nbsp;of&nbsp;Internet&nbsp;users&nbsp;in</DIV>
<DIV>South&nbsp;America&nbsp;not&nbsp;participating?&nbsp;One&nbsp;answer&=
nbsp;can&nbsp;be&nbsp;that&nbsp;the&nbsp;reason&nbsp;is</DIV>
<DIV>that&nbsp;IETF&nbsp;participants&nbsp;majority&nbsp;from&nbsp;North&n=
bsp;America&nbsp;and&nbsp;they&nbsp;don't&nbsp;want</DIV>
<DIV>to&nbsp;spend&nbsp;money&nbsp;on&nbsp;long&nbsp;journies&nbsp;that&nb=
sp;include&nbsp;many&nbsp;competing&nbsp;regions</DIV>
<DIV>(e.g.&nbsp;few&nbsp;regions&nbsp;or&nbsp;few&nbsp;long&nbsp;distance&=
nbsp;per&nbsp;year&nbsp;maybe&nbsp;fine).</DIV>
<DIV>&nbsp;</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;&nbsp;Regards,</DIV>
<DIV>&gt;&nbsp;-sm</DIV>
<DIV>&gt;</DIV>
<DIV>&gt;</DIV></DIV></BODY></HTML>

------=_001_NextPart412582500516_=------


From yi.jiazi@gmail.com  Mon May 27 07:27:26 2013
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968DB21F9375; Mon, 27 May 2013 07:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ba-YGto0r7-8; Mon, 27 May 2013 07:27:26 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5737221F9260; Mon, 27 May 2013 07:27:25 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id q56so4335891wes.23 for <multiple recipients>; Mon, 27 May 2013 07:27:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XU7DtgjtUCQ0DAmLZB2pcxth+ShjklV0WLD2tNxTemA=; b=EA3UDZ6dHtUO+j7BfA96gozaRz+QT6Oa5Qj+lUvr7q8wnqsKjHkmsQfCQzo0VWGJk4 VJv3RTou3JRyo2xof+g7NDQ7+Pq0kZr3CBg+SSdtFi9Qkf7McGJNxXebSxZxEK2DptmT B/XFQkbK54Yr8xx31bgctwS2E8FhyCessP0ILgBjbEU8VeSW5znYbV2y9HvEIx7O74IJ r62hqFsSS841aSQGii+4mjiuCaiUhqr6hZqaUJa9ORPU5eN1w1qkEgUvP4MRWeTKIhot IyDhaSqzI3oJMrdWlz1uzaWuyX+VclDTqyaP2QViXRzArclQUen0ablch7xXmZ0m4E+u w3vA==
MIME-Version: 1.0
X-Received: by 10.181.13.112 with SMTP id ex16mr8671407wid.28.1369664844417; Mon, 27 May 2013 07:27:24 -0700 (PDT)
Received: by 10.194.216.167 with HTTP; Mon, 27 May 2013 07:27:24 -0700 (PDT)
In-Reply-To: <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
References: <20130523222242.3631.36122.idtracker@ietfa.amsl.com> <CADnDZ8-i=sNFHyrPhBehPFQy9gLHcZWp2tXvwfL_ieeBMVAiHA@mail.gmail.com>
Date: Mon, 27 May 2013 16:27:24 +0200
Message-ID: <CAN1bDFw3p5MoUiRDNdo-_Eo7xxueg1rdQ_k+DRdUFLRSZSN2cg@mail.gmail.com>
Subject: Re: [manet] Last Call: <draft-ietf-manet-nhdp-sec-threats-03.txt> (Security Threats for NHDP) to Informational RFC
From: Jiazi YI <yi.jiazi@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c06be83521704ddb3f2c2
X-Mailman-Approved-At: Tue, 28 May 2013 06:58:11 -0700
Cc: ietf@ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 May 2013 14:27:26 -0000

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

Hi,

I think those comments have been addressed/answered in my previous reply

  http://www.ietf.org/mail-archive/web/manet/current/msg15274.html

I didn't see the support of your comments from other WG participants.

best

Jiazi


2013/5/27 Abdussalam Baryun <abdussalambaryun@gmail.com>

> Reply to your request dated 24/05/2013
>
> Draft Reviewed By: Abdussalam Baryun (AB)    Dated:27/05/2013
> Reviewer Comment A1: Previous comments in WGLC
> +++++++++++++++++++++++++++++++++++++++
>
> Related to your request below please read my previous review comments
> [1] and I will continue with additional messages/comments.
>
> [1] http://www.ietf.org/mail-archive/web/manet/current/msg15254.html
>
> Regards
> AB
>
> On 5/24/13, The IESG <iesg-secretary@ietf.org> wrote:
> >
> > The IESG has received a request from the Mobile Ad-hoc Networks WG
> > (manet) to consider the following document:
> > - 'Security Threats for NHDP'
> >   <draft-ietf-manet-nhdp-sec-threats-03.txt> as Informational RFC
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2013-06-06. 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 analyses common security threats of the Neighborhood
> >    Discovery Protocol (NHDP), and describes their potential impacts on
> >    MANET routing protocols using NHDP.
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/
> >
> > IESG discussion can be tracked via
> >
> http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-threats/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www.ietf.org/mailman/listinfo/manet
> >
>

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

<div dir=3D"ltr"><div><div><div>Hi, <br><br></div>I think those comments ha=
ve been addressed/answered in my previous reply <br><br>=A0 <a href=3D"http=
://www.ietf.org/mail-archive/web/manet/current/msg15274.html">http://www.ie=
tf.org/mail-archive/web/manet/current/msg15274.html</a><br>
<br></div>I didn&#39;t see the support of your comments from other WG parti=
cipants. <br><br></div>best<br><br>Jiazi<br></div><div class=3D"gmail_extra=
"><br><br><div class=3D"gmail_quote">2013/5/27 Abdussalam Baryun <span dir=
=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_blank=
">abdussalambaryun@gmail.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Reply to your request dated 24/05/2013<br>
<br>
Draft Reviewed By: Abdussalam Baryun (AB) =A0 =A0Dated:27/05/2013<br>
Reviewer Comment A1: Previous comments in WGLC<br>
+++++++++++++++++++++++++++++++++++++++<br>
<br>
Related to your request below please read my previous review comments<br>
[1] and I will continue with additional messages/comments.<br>
<br>
[1] <a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg15254.=
html" target=3D"_blank">http://www.ietf.org/mail-archive/web/manet/current/=
msg15254.html</a><br>
<br>
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">AB<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 5/24/13, The IESG &lt;<a href=3D"mailto:iesg-secretary@ietf.org">iesg-se=
cretary@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt; The IESG has received a request from the Mobile Ad-hoc Networks WG<br>
&gt; (manet) to consider the following document:<br>
&gt; - &#39;Security Threats for NHDP&#39;<br>
&gt; =A0 &lt;draft-ietf-manet-nhdp-sec-threats-03.txt&gt; as Informational =
RFC<br>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 20=
13-06-06. Exceptionally, comments may be<br>
&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In=
 either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt; =A0 =A0This document analyses common security threats of the Neighborh=
ood<br>
&gt; =A0 =A0Discovery Protocol (NHDP), and describes their potential impact=
s on<br>
&gt; =A0 =A0MANET routing protocols using NHDP.<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-t=
hreats/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-manet=
-nhdp-sec-threats/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-manet-nhdp-sec-t=
hreats/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-iet=
f-manet-nhdp-sec-threats/ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt; _______________________________________________<br>
&gt; manet mailing list<br>
&gt; <a href=3D"mailto:manet@ietf.org">manet@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/manet" target=3D"_bla=
nk">https://www.ietf.org/mailman/listinfo/manet</a><br>
&gt;<br>
</div></div></blockquote></div><br></div>

--f46d043c06be83521704ddb3f2c2--

From ajs@crankycanuck.ca  Mon May 27 08:38:36 2013
Return-Path: <ajs@crankycanuck.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 DDFBA21F967B for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.556
X-Spam-Level: 
X-Spam-Status: No, score=0.556 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rABKf5TtqIIa for <ietf@ietfa.amsl.com>; Mon, 27 May 2013 08:38:31 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id D7D0121F9675 for <ietf@ietf.org>; Mon, 27 May 2013 08:38:31 -0700 (PDT)
Received: from [25.138.119.253] (unknown [24.114.84.118]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 9CB018A031; Mon, 27 May 2013 15:38:29 +0000 (UTC)
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com>
In-Reply-To: <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B9EBA3D1-2189-4693-9A1D-E0CC383B4555@crankycanuck.ca>
X-Mailer: iPhone Mail (10B329)
From: Andrew Sullivan <ajs@crankycanuck.ca>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
Date: Mon, 27 May 2013 11:38:22 -0400
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailman-Approved-At: Tue, 28 May 2013 06:58:11 -0700
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, 27 May 2013 15:38:37 -0000

Rather than saying "someone should do this" on the list, you could, you know=
, do the work.=20

A

--=20
Andrew Sullivan=20
Please excuse my clumbsy thums.=20

On 2013-05-27, at 9:31, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote=
:

> On 5/27/13, Eggert, Lars <lars@netapp.com> wrote:
>> On May 27, 2013, at 12:10, Abdussalam Baryun <abdussalambaryun@gmail.com>=

>> wrote:
>>> Each IETF document mentions the authors place address (I may suggest
>>> adding region, as a categorised by IETF), but not sure of history
>>> statistics of how many IETF-documents produced by authors in South
>>> America, Africa, or Asia, or others.
>>=20
>> http://www.arkko.com/tools/stats/d-countrydistr.html and related pages
>=20
> I read that before, but does not show documents/RFCs per region. It
> shows drafts per countries. For example, does not show the drafts from
> South America. Does not show all regions in sequence of the most
> participated region.
>=20
> AB

From christian.oflaherty@gmail.com  Tue May 28 07:20:21 2013
Return-Path: <christian.oflaherty@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFCD721F9781 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MWG6ZA4zfNH8 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:20:21 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2F19621F973F for <ietf@ietf.org>; Tue, 28 May 2013 07:20:21 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id f4so5229899iea.23 for <ietf@ietf.org>; Tue, 28 May 2013 07:20:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=SQFhLR0pUWO5O/j/B3ItBX4J+e+0j0Nqc6DnSWbMuqU=; b=qF3pGgqBMahbBR0dTr84875tdKNnmVgo1WmSOBmkcF5qxLdCXS3zsrCLQTl9Qj+ycD Oso8pYUgTCuS3zB598pM4nmz4CoWiiRpFN43St4+vfn1Z+u7vHH9wam7u4J1qLlZwBoi lzhhLV+gn1PPD5uetGV7op5UQ63cTk3rqbBK6Zt52B8TiRSzJL5QkTssL9bw8JusM/0p tbA2hGrG5MRsf6NWdaG2o7MzhPfeVR+/RTjg2XNRw8BAjM3RiswfnVFqTNcY1PifqUyO DsHVtCalXfrgLQ4yJNDf1UaCaseTCjt0A6zGrTKhXnquSlo2TgT5uzWR6IE/J3nQWync 7Ifg==
MIME-Version: 1.0
X-Received: by 10.50.17.166 with SMTP id p6mr7089112igd.12.1369750820795; Tue, 28 May 2013 07:20:20 -0700 (PDT)
Received: by 10.64.136.18 with HTTP; Tue, 28 May 2013 07:20:20 -0700 (PDT)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com>
Date: Tue, 28 May 2013 11:20:20 -0300
Message-ID: <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: Crocker Dave <dcrocker@bbiw.net>, Eric Burger <eburger@standardstrack.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 14:20:21 -0000

>
> The IETF has a big problem, IMHO, in that effective participation really =
does currently seem to require meeting attendance.   There's a reason
> that nomcom members have to show up=97if they didn't, they wouldn't be pa=
rt of the actual culture of IETF, because so much IETF culture is
> bound up in the physical meetings.
>
> The interaction we get in the physical meetings is really important.

I think this is going to be difficult to change unless we let robots
do the work. The social part is an important component for cooperative
work.

Probably, this lack of social interaction in our region is one of the
main reasons for low participation. Most of latin american IETFers are
currently living outside the region and they engaged in the IETF when
living in the US or Europe. It's difficult to be involved when no one
else around is working in it or think it doesn't fit well in their
current work. A physical meeting will help to "demystify" the IETF,
making it "accesible" from a professional perspective.

Christian

>  I would very much like to see the IETF try to discover new ways of using=
 the technology our forebears (and some remaining senior
> participants) invented to achieve the same effectiveness without requirin=
g us to all burn tons of fuel getting to remote corners of the globe.
>
> But "achieve the same effectiveness" is an important requirement for any =
such new solution.   And right now we don't have a solution like that, so w=
e do what we do, and you are right that that means that effective participa=
tion in the IETF is much easier for people who are able to attend at least =
a sufficiency of meetings on an ongoing basis.   We should see this as a st=
arting point, not as an end state.
>

From loa@pi.nu  Tue May 28 07:24:49 2013
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 3F8A421F8F43 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eX1dmr3ZYOHZ for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:24:38 -0700 (PDT)
Received: from pipi.pi.nu (unknown [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 562A621F8E76 for <ietf@ietf.org>; Tue, 28 May 2013 07:24:37 -0700 (PDT)
Received: from [192.168.1.133] (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) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 776561800272; Tue, 28 May 2013 16:24:35 +0200 (CEST)
Message-ID: <51A4BE23.5000307@pi.nu>
Date: Tue, 28 May 2013 16:24:35 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <9904FB1B0159DA42B0B887B7FA8119CA179779@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA179779@AZ-FFEXMB04.global.avaya.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 14:24:49 -0000

On 2013-05-28 13:09, Romascanu, Dan (Dan) wrote:
> Hi,
>
> Good work. Here are a few thoughts after a first reading.
>
> - We seem not to have a definition of what a WG I-D is,
> although we know how to recognize a WG I-D because of the naming
 > convention. So, if I am not mistaken the phrase
>
> Working Group drafts are documents that are subject to IETF Working
>     Group revision control.
>
> in section 1.1 introduces such a definition. Is everybody happy with this?

No not really - first it is not a definition - it is something that
follow from that the document is a wg document.

I guess the following is closer to a definition:

   "A working group document is any document that the working group
    chairs says is a working group document."

The revision control follows from that, but is nevertheless necessary.

/Loa
>
> - I am lacking from the criteria in 2.2 the stability of the technical solution (as per WG consensus). In my mind this is in current practice the principal specific difference between individual submission I-Ds and WG I-Ds - the fact that the I-D makes a clear (it may be drafty but yet clear) statement about what the technical solution is.
>
> - I less like the following:
>
>        *  If not already in scope, is a simple modification to the
>           charter feasible and warranted?
>
> Without being extremely strict on the process aspect, I believe that WGs should not work on items that are not chartered, and even less adopt WG I-Ds on non-chartered items. If they feel that something is missing from the charter they can ask the ADs for a charter update, or for adding milestones, we have today at hand light processes which can lead to fast incremental additions to charters, and if the addition is more than incremental than it should go through a proper rechartering process.
>
> -      *  What is the position of the working group chairs, concerning
>           the draft?
>
>              [[editor note: I am not sure this is relevant.  Indeed is
>              might be specifically not relevant.  /a]]
>
> Not relevant IMO.
>
> Regards,
>
> Dan
>
>
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>> Adrian Farrel
>> Sent: Tuesday, May 28, 2013 12:33 PM
>> To: ietf@ietf.org
>> Subject: When to adopt a WG I-D
>>
>> Hi,
>>
>> Dave Crocker and I have this little draft [1] discussing the process and
>> considerations for creating formal working group drafts that are
>> targeted for publication.
>>
>> We believe that this may help clarify some of the issues and concerns
>> associated with this part of the process. We are targeting this as
>> Informational (i.e. commentary on existing process, not new normative
>> definition of process) and would like your input.
>>
>> What is not clear?
>> What have we got wrong?
>> How should we resolve the remaining editor notes?
>>
>> Thanks,
>> Adrian
>> (per pro Dave)
>>
>> [1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From abdussalambaryun@gmail.com  Tue May 28 07:36:01 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3ED821F941D for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k8hcf7QmlzAY for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:36:01 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 21A1721F93F1 for <ietf@ietf.org>; Tue, 28 May 2013 07:36:01 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md12so7938808pbc.35 for <ietf@ietf.org>; Tue, 28 May 2013 07:36:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jWb0hb/nsO6HdG0Jnls26Dbf3Hhozj6UnQouuPp+aWE=; b=1FoGT32S8GzzbTtpVQ8BbJdb/Z/z1hoxyDqPSZE+N3kyaGdMkGHe3FyszN3X5LnKff Q08VhfTUT3MM6/9JV6Rjwkn3/NTPSli/0uXaiaPgs6zexG7WEzcGK/wIyDL/S3aJIP+/ 6MP7u1oP1TMfkPx2VKgGcLSRk5A6RFGJ8OetKy0yf8XEVCszi9pdPzKaf4pdyUusJFPv 6CZutBpF5mt036P9C/LgztvwhmwFGOxdaFgncZnOqWBhX0qchj+mH+5dXwaWhmK1lQPb 7NPIVb1hOa+Y2/xshwgFPLfbx6awvzcwi228tpe5AhctCmAWs7xbh38lanM8gG013k+C UNEg==
MIME-Version: 1.0
X-Received: by 10.68.219.42 with SMTP id pl10mr34625716pbc.24.1369751760864; Tue, 28 May 2013 07:36:00 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Tue, 28 May 2013 07:36:00 -0700 (PDT)
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
Date: Tue, 28 May 2013 15:36:00 +0100
Message-ID: <CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com>
Subject: Re: When to adopt a WG I-D
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: adrian <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=047d7b10caa3230bab04ddc82f83
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, 28 May 2013 14:36:01 -0000

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

It is difficult to read, because I am expecting a process and find
something else,

I started to read, but got confused (stoped reading), why you are titling
it as creating WG-draft and mentioning the adoption into the document. I
understand that the creating first is *individual-draft* not *WG-draft*,
the adoption happens after the creation of individual draft. If creating is
WG creation, then it is already adopted as *idea* not *draft*, and then
draft-00 is the WG-draft.

I don't see the process clear at all, I maybe missing something,

AB


On Tue, May 28, 2013 at 10:32 AM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Hi,
>
> Dave Crocker and I have this little draft [1] discussing the process and
> considerations for creating formal working group drafts that are targeted
> for publication.
>
> We believe that this may help clarify some of the issues and concerns
> associated with this part of the process. We are targeting this as
> Informational (i.e. commentary on existing process, not new normative
> definition of process) and would like your input.
>
> What is not clear?
> What have we got wrong?
> How should we resolve the remaining editor notes?
>
> Thanks,
> Adrian
> (per pro Dave)
>
> [1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>
>
>

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

<div dir=3D"ltr"><div>It is difficult to read, because I am expecting a pro=
cess and find something else,</div><div>=A0</div><div>I started to read, bu=
t got confused (stoped reading), why you are titling it as creating WG-draf=
t=A0and mentioning the adoption into the document. I understand that the cr=
eating first is *individual-draft* not *WG-draft*, the adoption happens aft=
er the creation of individual draft. If creating is WG creation, then it is=
 already adopted as *idea* not *draft*, and then draft-00 is the WG-draft.<=
/div>
<div>=A0</div><div>I don&#39;t see the process clear at all, I maybe missin=
g something,</div><div>=A0</div><div>AB</div></div><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Tue, May 28, 2013 at 10:32 AM, Adr=
ian Farrel <span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" tar=
get=3D"_blank">adrian@olddog.co.uk</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<br>
Dave Crocker and I have this little draft [1] discussing the process and co=
nsiderations for creating formal working group drafts that are targeted for=
 publication.<br>
<br>
We believe that this may help clarify some of the issues and concerns assoc=
iated with this part of the process. We are targeting this as Informational=
 (i.e. commentary on existing process, not new normative definition of proc=
ess) and would like your input.<br>

<br>
What is not clear?<br>
What have we got wrong?<br>
How should we resolve the remaining editor notes?<br>
<br>
Thanks,<br>
Adrian<br>
(per pro Dave)<br>
<br>
[1] <a href=3D"http://www.ietf.org/internet-drafts/draft-crocker-id-adoptio=
n-02.txt" target=3D"_blank">http://www.ietf.org/internet-drafts/draft-crock=
er-id-adoption-02.txt</a><br>
<br>
<br>
</blockquote></div><br></div>

--047d7b10caa3230bab04ddc82f83--

From stbryant@cisco.com  Tue May 28 07:52:23 2013
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 1698421F9725 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T3-iblb4md3Y for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:52:18 -0700 (PDT)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id B2F6121F971B for <ietf@ietf.org>; Tue, 28 May 2013 07:52:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6050; q=dns/txt; s=iport; t=1369752737; x=1370962337; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=LcR7PYjBhtG8yj5eXX4Srous19+T18UnttjMEshGpFs=; b=lQRjoKcC+d9DEKos0WtWoxq7CHdiN9DTByVX+ZM4FIvoN+ei+m/uxgzX VN5WtCky6N1dWVChk7T1/LIUpuWCaYNg16h80FfhWXle/oASAV6PRPBDj tegijVpa02czvVNM+MF3VSgffN9RJ+b4q6zF5S1IczRftHbugc3VS5Bxd o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai4HAE7DpFGQ/khR/2dsb2JhbABZgwgwiRm4d4EEFnSCIwEBAQMBeAEFCwsYCRYIBwkDAgECATQRBg0BBQIBAQWHfgYMvCSPHQeDVAOXO5FAgxA
X-IronPort-AV: E=Sophos;i="4.87,758,1363132800"; d="scan'208,217";a="13788407"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 28 May 2013 14:52:16 +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 r4SEqEAB030037 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 May 2013 14:52:14 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r4SEqD8Z024149; Tue, 28 May 2013 15:52:13 +0100 (BST)
Message-ID: <51A4C49D.4080806@cisco.com>
Date: Tue, 28 May 2013 15:52:13 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com>
In-Reply-To: <CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060706030206070606000800"
Cc: adrian <adrian@olddog.co.uk>, ietf <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: Tue, 28 May 2013 14:52:23 -0000

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

On 28/05/2013 15:36, Abdussalam Baryun wrote:
> It is difficult to read, because I am expecting a process and find 
> something else,
> I started to read, but got confused (stoped reading), why you are 
> titling it as creating WG-draft and mentioning the adoption into the 
> document. I understand that the creating first is *individual-draft* 
> not *WG-draft*,

Incorrect, the first incarnation of a draft can be a WG draft. The only 
requirement is that the chairs conclude that the existence such a draft 
has WG consensus.

> the adoption happens after the creation of individual draft. If 
> creating is WG creation, then it is already adopted as *idea* not 
> *draft*, and then draft-00 is the WG-draft.
> I don't see the process clear at all, I maybe missing something,
Yes you are.

Stewart
> AB
>
>
> On Tue, May 28, 2013 at 10:32 AM, Adrian Farrel <adrian@olddog.co.uk 
> <mailto:adrian@olddog.co.uk>> wrote:
>
>     Hi,
>
>     Dave Crocker and I have this little draft [1] discussing the
>     process and considerations for creating formal working group
>     drafts that are targeted for publication.
>
>     We believe that this may help clarify some of the issues and
>     concerns associated with this part of the process. We are
>     targeting this as Informational (i.e. commentary on existing
>     process, not new normative definition of process) and would like
>     your input.
>
>     What is not clear?
>     What have we got wrong?
>     How should we resolve the remaining editor notes?
>
>     Thanks,
>     Adrian
>     (per pro Dave)
>
>     [1]
>     http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------060706030206070606000800
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 28/05/2013 15:36, Abdussalam Baryun
      wrote:<br>
    </div>
    <blockquote
cite="mid:CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr">
        <div>It is difficult to read, because I am expecting a process
          and find something else,</div>
        <div>&nbsp;</div>
        <div>I started to read, but got confused (stoped reading), why
          you are titling it as creating WG-draft&nbsp;and mentioning the
          adoption into the document. I understand that the creating
          first is *individual-draft* not *WG-draft*, </div>
      </div>
    </blockquote>
    <br>
    Incorrect, the first incarnation of a draft can be a WG draft. The
    only requirement is that the chairs conclude that the existence such
    a draft has WG consensus.<br>
    <br>
    <blockquote
cite="mid:CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>the adoption happens after the creation of individual
          draft. If creating is WG creation, then it is already adopted
          as *idea* not *draft*, and then draft-00 is the WG-draft.</div>
        <div>&nbsp;</div>
        <div>I don't see the process clear at all, I maybe missing
          something,</div>
      </div>
    </blockquote>
    Yes you are.<br>
    <br>
    Stewart<br>
    <blockquote
cite="mid:CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>&nbsp;</div>
        <div>AB</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Tue, May 28, 2013 at 10:32 AM,
          Adrian Farrel <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:adrian@olddog.co.uk" target="_blank">adrian@olddog.co.uk</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
            <br>
            Dave Crocker and I have this little draft [1] discussing the
            process and considerations for creating formal working group
            drafts that are targeted for publication.<br>
            <br>
            We believe that this may help clarify some of the issues and
            concerns associated with this part of the process. We are
            targeting this as Informational (i.e. commentary on existing
            process, not new normative definition of process) and would
            like your input.<br>
            <br>
            What is not clear?<br>
            What have we got wrong?<br>
            How should we resolve the remaining editor notes?<br>
            <br>
            Thanks,<br>
            Adrian<br>
            (per pro Dave)<br>
            <br>
            [1] <a moz-do-not-send="true"
href="http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt"
              target="_blank">http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt</a><br>
            <br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------060706030206070606000800--

From loa@pi.nu  Tue May 28 07:59:52 2013
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 F12C621F9790 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.048
X-Spam-Level: 
X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RtQpTKKk+zq5 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 07:59:47 -0700 (PDT)
Received: from pipi.pi.nu (unknown [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 97BD921F9007 for <ietf@ietf.org>; Tue, 28 May 2013 07:59:46 -0700 (PDT)
Received: from [192.168.1.133] (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) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id CF1511800272; Tue, 28 May 2013 16:59:43 +0200 (CEST)
Message-ID: <51A4C65E.1010606@pi.nu>
Date: Tue, 28 May 2013 16:59:42 +0200
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
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: Tue, 28 May 2013 14:59:52 -0000

Adrian,

I'm fine with this draft as long as it stays informational and is
viewed as a commentary on how what we are doing in the border land
between individual and formal working group documents, i.e. this is
not an IETF process text.

Names of ID file are a bit trickier than what I get from this draft

It is true that a document with a file name as:

draft-<wgname>-ietf-... uniquely is a working group document; you need
the approval of the wg chair(s) to have a draft with that file name
posted.

However, a draft with the file name:

draft-<individual>-ietf... may or may not be wg document, and it is
actually so when the the working group chairs states on the wg mailing
list that it is.

Admittedly this is often followed by a request to re-post it with
the common format of file names for wg documents, but it is not the
posting with the wg name format that makes it a wg document, it is the
announcement from wg chairs.

It is nowhere required to change the file name just because the
document has become a working group document. Stupid not to do it,
but not required. For example the appsawg does have two parked
*wg documents* that does not follow the naming convention above.

Now in section 5.1. you talk about a special case "documents supported
by a working", but that remains an individual draft but progress
according to the wg processes. I think that what is now RFC 3468 was
such a case; even though we at that did not talk about in those terms.

I think it would be clearer if you in section 5.1. just said that there
might be individual documents that is supported by a working group, and
that follows the naming conventions for individual documents.

/Loa

On 2013-05-28 11:32, Adrian Farrel wrote:
> Hi,
>
> Dave Crocker and I have this little draft [1] discussing the process and considerations for creating formal working group drafts that are targeted for publication.
>
> We believe that this may help clarify some of the issues and concerns associated with this part of the process. We are targeting this as Informational (i.e. commentary on existing process, not new normative definition of process) and would like your input.
>
> What is not clear?
> What have we got wrong?
> How should we resolve the remaining editor notes?
>
> Thanks,
> Adrian
> (per pro Dave)
>
> [1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From fernando@gont.com.ar  Tue May 28 08:00:03 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA4F21F97DE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:00:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saQxY0fqP-As for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:00:02 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3774C21F97DD for <ietf@ietf.org>; Tue, 28 May 2013 08:00:02 -0700 (PDT)
Received: from [2001:5c0:1400:a::7cf] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UhLNX-0003t5-Px; Tue, 28 May 2013 17:00:00 +0200
Message-ID: <51A4B2C6.3050706@gont.com.ar>
Date: Tue, 28 May 2013 15:36:06 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Juliao Braga <juliao@braga.eti.br>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br>
In-Reply-To: <51A2EFAB.3010106@braga.eti.br>
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: Tue, 28 May 2013 15:00:03 -0000

On 05/27/2013 07:31 AM, Juliao Braga wrote:
> According to the news published for a long time in Brazilian newspapers
> and magazines, Buenos Aires (a wonderful place!) would not be
> recommended.

Recommended for what? And on what basis?

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fernando@gont.com.ar  Tue May 28 08:00:09 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1F821F97ED for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:00:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdR1errTJRBP for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:00:08 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id E9F5921F97E4 for <ietf@ietf.org>; Tue, 28 May 2013 08:00:07 -0700 (PDT)
Received: from [2001:5c0:1400:a::7cf] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UhLNc-0003v3-21; Tue, 28 May 2013 17:00:04 +0200
Message-ID: <51A4C661.4030302@gont.com.ar>
Date: Tue, 28 May 2013 16:59:45 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com>
In-Reply-To: <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <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: Tue, 28 May 2013 15:00:09 -0000

Jorge,

On 05/27/2013 08:16 AM, Jorge Amodio wrote:
> 
> I feel that is totally OT but for example we have supporters of the
> current government like this one, claiming to be a writer, that if you
> are able to read in Spanish or helped by a translator to read his
> article, you will learn that he is propagating a message that says
> "Internet is the secret weapon of the imperialism." 
> 
> http://sumateacristina.net/m/blogpost?id=6438092%3ABlogPost%3A524963

I'm currently off-line at the moment, and hence cannot read the
aforementioned article. I would just say that lots of crap gets posted
on the Internet.

I'd also say that I've never heard anyone making that sort of statement.
For instance, the argentinan government itself has a program to increase
Internet connectivity throughout the country -- which should be more of
a datapoint that the aforementioned article should be taken as "a post
by some random idiot" (assuming he says what you say he is saying).


> His view is shared by many, so in the event IETF gets to meet in Buenos
> Aires, if the meeting becomes public, don't be surprised to see some
> coordinated political manifestation.

I live in Buenos Aires, and have never ever heard about such message
about "the internet being a weapon of imperialism". For instance,
left-wing parties (which are the ones usually talking about
imperialism) tend to use the Internet a lot, since it provides a cheap
way of communication when compared to other means (printed media, or
whatever). So, me, I couldn't even imagine such a manifestation.

Besides, I doubt anyone considers us (IETF) as important to be the
target of a manifestation.

I don't think it's productive to alarm people this way. Particularly
without any concrete data.

Note: I'm not not even touching the issue of whether having a meeting in
Buenos Aires is a great idea or not.. but just trying to keep the
discussion objective.

Un abrazo,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From fernando@gont.com.ar  Tue May 28 08:00:14 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4579521F97ED for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tx0iVFhl0PV for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:00:13 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3021621F97EF for <ietf@ietf.org>; Tue, 28 May 2013 08:00:11 -0700 (PDT)
Received: from [2001:5c0:1400:a::7cf] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UhLNa-0003tg-PV; Tue, 28 May 2013 17:00:02 +0200
Message-ID: <51A4B549.7010706@gont.com.ar>
Date: Tue, 28 May 2013 15:46:49 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk> <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|97e823e22bce4bde60b7222ce5eb9581p4Q8Ky03tjc|ecs.soton.ac.uk|A349D0AF-E19C-4937-A3E5-9554CDF1CCA3@ecs.soton.ac.uk>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <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: Tue, 28 May 2013 15:00:14 -0000

Hi, Tim,

On 05/27/2013 09:19 AM, Tim Chown wrote:
>>> The move appears to be related to new, restrictive
>>> regulations the Argentine government has imposed on currency exchanges.'
>>> According to the Telegraph, 'The new regulations required anyone wanting
>>> to change Argentine pesos into another currency to submit an online
>>> request for permission to AFIP, the Argentine equivalent of HM Revenue &
>>> Customs. ..."
>>
>> This isn't likely to change soon.
> 
> Going into the country isn't the problem, more importantly it seems that
> if you don't spend all your pesos in Argentina, you can't change them
> back to your own currency:
> 
> http://www.tripadvisor.co.uk/Travel-g294266-s601/Argentina:Banks.And.Money.html
> (see last paragraph)

I'm currently off-line, and hance cannot read the article right now. But
I should say that the last time that I checked, it was possible to
change the excess pesos back to your original currency, provided you
kept the original receipt that proved that those excess pesos correspond
to money you had in your original currency. But I could double-check if
interested.

That said, man shops accept dollars and euros (not pounds, though :-( ).
So I guess that for the most part you could just have some small amount
of money in pesos (mostly to pay cabs, I'd say), and move around the
city using your credit card (or, if needed, USD or Euros)

Cheers,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From john-ietf@jck.com  Tue May 28 08:17:41 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91AA21F97A1 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIEvpv3ociNk for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:17:35 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B29C321F97A5 for <ietf@ietf.org>; Tue, 28 May 2013 08:17:34 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UhLeX-0000Qp-Ur; Tue, 28 May 2013 11:17:33 -0400
Date: Tue, 28 May 2013 11:17:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
Message-ID: <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com>
In-Reply-To: <m2ehcr48pa.wl%randy@psg.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com>	<m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.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 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, 28 May 2013 15:17:41 -0000

--On Tuesday, May 28, 2013 20:58 +0900 Randy Bush
<randy@psg.com> wrote:

>> What is at issue, IMO, is whether the Internet is better off
>> having a couple of RRTYPEs around with no documentation or
>> having them documented.
> 
> there are two solutions to this

Probably more than two if your comment indicates that you agree
that having registered RRTYPEs documented is, on balance, better
than not having them documented:

(1) We can continue along the path of Informational RFC
publication in the IETF Stream

(2) Joe could have submitted the document to the ISE and
requested Informational RFC publication in the Independent
stream.

(3) Joe could post the definitional document on a web site
somewhere that could provide a stable reference and then ask
IANA to incorporate that reference, presumably in URL form,
rather than the name of an I-D in the registry.  If this is a
Canadian initiative, perhaps the Canadian government would like
to provide that location and reference but, clearly, there are
other alternatives.

Did you have something else in mind?

I think the advantage of the first over the other two is that it
promotes a level of review in the community that, a least IMO,
had improved the document and, if we need revisit how RRTYPEs
are allocated, to provide a concrete basis for that discussion.
Once an RFC is published, the broader community is unlikely to
be able to tell the difference between the first and second
although, if we think the second would be better, it suggests
another option for the longer term:

(4) Create an IANA Stream for the RFC Editor through which we
can publish documents that describe protocol parameters that are
registered through lightweight methods and assure stable
references for them, with no approval beyond that required to
accomplish the registration.  If such a stream retained the
requirement to post as an I-D (and conformance to the IETF's IPR
rules), there would still be as much or more opportunity for
community pre-publication review and feedback to the author and
expert reviewers than the independent stream affords.  I have no
idea whether that would be a good idea or not and it would
certainly be too long-term to affect this document, but it is
possible.

Of course, (5), we could retroactively change the registration
procedure and retroactively deprecate these types.  That might
avoid the need to write the Applicability Statement I-D that I
mentioned but, if my reading of trends in the IESG is correct, I
have my doubts.

What, actually, would you propose other than continuing to
complain about the RRTYPEs themselves and what they are intended
to support (which, in case it hasn't been clear, I largely agree
with you about).

best,
    john





From randy@psg.com  Tue May 28 08:18:42 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D153B21F97D1 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5z9HI8J7APL for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:18:42 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 20A3121F979A for <ietf@ietf.org>; Tue, 28 May 2013 08:18:42 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UhLfd-0006Ih-89; Tue, 28 May 2013 15:18:41 +0000
Date: Wed, 29 May 2013 00:18:40 +0900
Message-ID: <m2ppwb2kvj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
In-Reply-To: <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@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 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, 28 May 2013 15:18:43 -0000

>>> What is at issue, IMO, is whether the Internet is better off
>>> having a couple of RRTYPEs around with no documentation or
>>> having them documented.
>> 
>> there are two solutions to this
> 
> Probably more than two if your comment indicates that you agree
> that having registered RRTYPEs documented is, on balance, better
> than not having them documented:
> 
> (1) We can continue along the path of Informational RFC
> publication in the IETF Stream
> 
> (2) Joe could have submitted the document to the ISE and
> requested Informational RFC publication in the Independent
> stream.
> 
> (3) Joe could post the definitional document on a web site
> somewhere that could provide a stable reference and then ask
> IANA to incorporate that reference, presumably in URL form,
> rather than the name of an I-D in the registry.  If this is a
> Canadian initiative, perhaps the Canadian government would like
> to provide that location and reference but, clearly, there are
> other alternatives.
> 
> Did you have something else in mind?

remove the rrtypes from the registry

From juliao@braga.eti.br  Tue May 28 08:19:53 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5848E21F9816 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:19:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6ZaJs4a8vJ7 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:19:48 -0700 (PDT)
Received: from mail-gh0-f171.google.com (mail-gh0-f171.google.com [209.85.160.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3A06A21F979A for <ietf@ietf.org>; Tue, 28 May 2013 08:19:48 -0700 (PDT)
Received: by mail-gh0-f171.google.com with SMTP id f15so2180683ghb.30 for <ietf@ietf.org>; Tue, 28 May 2013 08:19:47 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=EqHsvNGiLZB1ZrwTxJC3UGK80cld5k/cgFNiea5S3m0=; b=Hu17D1hhTFdVrJ/dmMnMBFV3hZmpzYWCIWx9zqBwELLbr9NLFtxAQ6XtGT74R9nvum zmpvMpCXvAufRDChqGiz6WhP0HPlVvPuiywPa1Hpd/BFlceMv62WdF2f/XPTcJZT4sN3 IALWc/Gpzm8XmXwhRgqhLVWuRrlW7iNDTbVXaTATCim/jBddLtjJFByx50sImZ1Fj6Zt 43F3MaZic5h6/pFQ1chgxQQAIX8txmgN/nddPrxwq2+4wYdd6tS1LX0u0gYqy9hF+qXh vNt69HdOpd431j3Hfare4i+R9SA2AQvDfRX5LHmfS5yUZHyxCmlvFj+tMn0yG1HeBrjS aJyw==
X-Received: by 10.236.59.164 with SMTP id s24mr16301458yhc.110.1369754387773;  Tue, 28 May 2013 08:19:47 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id n15sm46752047yhi.2.2013.05.28.08.19.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 08:19:47 -0700 (PDT)
Message-ID: <51A4CB0D.9010001@braga.eti.br>
Date: Tue, 28 May 2013 12:19:41 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar>
In-Reply-To: <51A4B2C6.3050706@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQmEDSqnnOpRqRPBco8bBXeETyQtYfg1M+XvPmEqoyFfCrnnBGbSqauWGU0A6MnMTqZtvcSH
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 15:19:53 -0000

Hi Fernando,

Please, read my sentence complementary to comment:

"...But who should tell us about the true cenary would be our
Argentine friends."

Regards,

Julião
Em 28/05/2013 10:36, Fernando Gont escreveu:
> On 05/27/2013 07:31 AM, Juliao Braga wrote:
>> According to the news published for a long time in Brazilian newspapers
>> and magazines, Buenos Aires (a wonderful place!) would not be
>> recommended.
> 
> Recommended for what? And on what basis?
> 
> Cheers,
> 

From lberger@labn.net  Tue May 28 08:21:18 2013
Return-Path: <lberger@labn.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 6EAF421F90CC for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:21:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jk6ZD0bNVxec for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:21:12 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id A03AA21F918F for <ietf@ietf.org>; Tue, 28 May 2013 08:21:12 -0700 (PDT)
Received: (qmail 24566 invoked by uid 0); 28 May 2013 15:20:45 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy6.bluehost.com with SMTP; 28 May 2013 15:20:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=28rU35QwW2C072GSKp67yh0qwdLVuwM6sr6o7G+hoYU=;  b=a5ziLi9kkBQ3g1z52DUvNveuHtyq/lNX5JMglw92dIAxmA45VmFVJhLZ4cFZr1k/ZM9PEgqC2/efIt+nzlx23UEXLMh6Y/3abjRMI/PnuTUpmPMLoC7CMspjJbNtDctW;
Received: from box313.bluehost.com ([69.89.31.113]:38616 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1UhLhd-0005o6-AY; Tue, 28 May 2013 09:20:45 -0600
Message-ID: <51A4CB4B.5090707@labn.net>
Date: Tue, 28 May 2013 11:20:43 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <CADnDZ89Q9zFOqUDuapw4TKW-wJb-QLkaVEaz_Tg+QKVM=vcrDg@mail.gmail.com> <51A4C49D.4080806@cisco.com>
In-Reply-To: <51A4C49D.4080806@cisco.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: adrian <adrian@olddog.co.uk>, 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, 28 May 2013 15:21:18 -0000

On 5/28/2013 10:52 AM, Stewart Bryant wrote:
> ... The only
> requirement is that the chairs conclude that the existence such a draft
> has WG consensus.
> ...

Strictly speaking, I believe the only requirement for a document to be
published as a WG document is that a WG chair approves it.

I do agree/think there are many practical restrictions, notably charter
& WG support.

WRT to the I-D: the text in section 2.4 that says "the chairs need
to..." can mislead some to believe that this is the required process.  I
think the "the chairs typically..." would be more accurate.

Lou

From jmh@joelhalpern.com  Tue May 28 08:22:16 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB9121F89FF for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:22:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJf+cCbkEAM7 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:22:11 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 52DBE21F900C for <ietf@ietf.org>; Tue, 28 May 2013 08:22:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id E14941D2633; Tue, 28 May 2013 08:22:10 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.1.21] (pool-108-2-221-176.phlapa.fios.verizon.net [108.2.221.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 2A7AE1C065B; Tue, 28 May 2013 08:22:10 -0700 (PDT)
Message-ID: <51A4CB9E.6020103@joelhalpern.com>
Date: Tue, 28 May 2013 11:22:06 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
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: Tue, 28 May 2013 15:22:17 -0000

In reading through the draft, particularly the section on questions for 
WG adoption of a draft, I did not see the questions I consider most 
pertinent:
Does the WG think this is a reasonable (preferably good) basis for 
starting to work collectively on the deliverable?

(Apologies if it was there and I missed it.)

Another question many WGs have found useful is:
Are there enough people interested and willing to write and / or review 
the document?
This is not the same as WG support for the document.

Yours,
Joel

PS: The chairs opinion on the technical content of the document ought to 
be irrelevant as far as I can tell.  On the other hand, detecting and 
raising concerns if the document is badly written is probably part of 
the chair's job.

On 5/28/2013 5:32 AM, Adrian Farrel wrote:
> Hi,
>
> Dave Crocker and I have this little draft [1] discussing the process
> and considerations for creating formal working group drafts that are
> targeted for publication.
>
> We believe that this may help clarify some of the issues and concerns
> associated with this part of the process. We are targeting this as
> Informational (i.e. commentary on existing process, not new normative
> definition of process) and would like your input.
>
> What is not clear? What have we got wrong? How should we resolve the
> remaining editor notes?
>
> Thanks, Adrian (per pro Dave)
>
> [1]
> http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>
>
>

From bmanning@isi.edu  Tue May 28 08:39:20 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07BD621F9808 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:39:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Mq3VPsvYFvh for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:39:15 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 4F03021F97A7 for <ietf@ietf.org>; Tue, 28 May 2013 08:39:15 -0700 (PDT)
Received: from [128.9.184.107] ([128.9.184.107]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4SFcMgg018829 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 28 May 2013 08:38:39 -0700 (PDT)
Subject: Re: When to adopt a WG I-D
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <51A4C65E.1010606@pi.nu>
Date: Tue, 28 May 2013 08:38:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <22B474AE-1D6C-4D0C-892D-65857CADEFCA@isi.edu>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A4C65E.1010606@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
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: Tue, 28 May 2013 15:39:20 -0000

there is also the not uncommon event where an idea starts as an =
individual idea,
moves into a WG, is rejected by the WG, becomes an individual idea, is =
picked up
by another WG, rejected,  (lather, rinse, repeat), and then the -right- =
WG is formed=20
and it is processed that way.  In the current state of affairs, at each =
name-change, the
document counter is reset, particularly for IP challenges.

and there is also Mr. Bush's dispensation to use neither WG or name in =
his drafts=85
he gets to use  "YMBK"

Naming of IDs, while important, is not an accurate reflection of the =
growth and evolution of=20
an idea in the IETF context.


/bill


On 28May2013Tuesday, at 7:59, Loa Andersson wrote:

>=20
> Adrian,
>=20
> I'm fine with this draft as long as it stays informational and is
> viewed as a commentary on how what we are doing in the border land
> between individual and formal working group documents, i.e. this is
> not an IETF process text.
>=20
> Names of ID file are a bit trickier than what I get from this draft
>=20
> It is true that a document with a file name as:
>=20
> draft-<wgname>-ietf-... uniquely is a working group document; you need
> the approval of the wg chair(s) to have a draft with that file name
> posted.
>=20
> However, a draft with the file name:
>=20
> draft-<individual>-ietf... may or may not be wg document, and it is
> actually so when the the working group chairs states on the wg mailing
> list that it is.
>=20
> Admittedly this is often followed by a request to re-post it with
> the common format of file names for wg documents, but it is not the
> posting with the wg name format that makes it a wg document, it is the
> announcement from wg chairs.
>=20
> It is nowhere required to change the file name just because the
> document has become a working group document. Stupid not to do it,
> but not required. For example the appsawg does have two parked
> *wg documents* that does not follow the naming convention above.
>=20
> Now in section 5.1. you talk about a special case "documents supported
> by a working", but that remains an individual draft but progress
> according to the wg processes. I think that what is now RFC 3468 was
> such a case; even though we at that did not talk about in those terms.
>=20
> I think it would be clearer if you in section 5.1. just said that =
there
> might be individual documents that is supported by a working group, =
and
> that follows the naming conventions for individual documents.
>=20
> /Loa
>=20
> On 2013-05-28 11:32, Adrian Farrel wrote:
>> Hi,
>>=20
>> Dave Crocker and I have this little draft [1] discussing the process =
and considerations for creating formal working group drafts that are =
targeted for publication.
>>=20
>> We believe that this may help clarify some of the issues and concerns =
associated with this part of the process. We are targeting this as =
Informational (i.e. commentary on existing process, not new normative =
definition of process) and would like your input.
>>=20
>> What is not clear?
>> What have we got wrong?
>> How should we resolve the remaining editor notes?
>>=20
>> Thanks,
>> Adrian
>> (per pro Dave)
>>=20
>> [1] =
http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>>=20
>>=20
>=20
> --=20
>=20
>=20
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64


From joelja@bogus.com  Tue May 28 08:52:31 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5031721F9670 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:52:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yy-Ocj+SCi5p for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 08:52:30 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8761221F9180 for <ietf@ietf.org>; Tue, 28 May 2013 08:52:30 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4SFqTQ8005305 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 28 May 2013 15:52:30 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A4D2B9.7000205@bogus.com>
Date: Tue, 28 May 2013 08:52:25 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com>	<CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com>	<m27gij61wi.wl%randy@psg.com>	<DFE3023D474039B828B19D6D@JcK-HP8200.jck.com>	<m2ehcr48pa.wl%randy@psg.com>	<AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com>
In-Reply-To: <m2ppwb2kvj.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]); Tue, 28 May 2013 15:52:30 +0000 (UTC)
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, 28 May 2013 15:52:31 -0000

On 5/28/13 8:18 AM, Randy Bush wrote:
>>>> What is at issue, IMO, is whether the Internet is better off
>>>> having a couple of RRTYPEs around with no documentation or
>>>> having them documented.
>>> there are two solutions to this
>> Probably more than two if your comment indicates that you agree
>> that having registered RRTYPEs documented is, on balance, better
>> than not having them documented:
>>
>> (1) We can continue along the path of Informational RFC
>> publication in the IETF Stream
>>
>> (2) Joe could have submitted the document to the ISE and
>> requested Informational RFC publication in the Independent
>> stream.
>>
>> (3) Joe could post the definitional document on a web site
>> somewhere that could provide a stable reference and then ask
>> IANA to incorporate that reference, presumably in URL form,
>> rather than the name of an I-D in the registry.  If this is a
>> Canadian initiative, perhaps the Canadian government would like
>> to provide that location and reference but, clearly, there are
>> other alternatives.
>>
>> Did you have something else in mind?
> remove the rrtypes from the registry
>
Unless you're proposing that we change the operation of the registry 
that seems a bit out of scope.

From ajs@anvilwalrusden.com  Tue May 28 09:07:46 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12D6021F977A for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 09:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vsqWRhXYI6TG for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 09:07:38 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id DD2DD21F9775 for <ietf@ietf.org>; Tue, 28 May 2013 09:07:35 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 7A1EB8A031 for <ietf@ietf.org>; Tue, 28 May 2013 16:07:34 +0000 (UTC)
Date: Tue, 28 May 2013 12:08:03 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
Message-ID: <20130528160803.GC28387@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m2ppwb2kvj.wl%randy@psg.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 16:07:46 -0000

On Wed, May 29, 2013 at 12:18:40AM +0900, Randy Bush wrote:

> remove the rrtypes from the registry

While it's good to see that the Internet Exemplary Taste-enForcers are
alive and well, I would have an extremely strong objection to that
approach.  The DNS Extensions Working Group published an IANA
Considerations document that was explicitly designed to permit
registrations, and this is an example of that procedure working.  If
people had objections to that permissiveness, they didn't express them
when the then-to-be-RFC6895 was last called.  We have shipping
implementations of DNS software that are using those code points.

Removing the types from the registry does absolutely nothing for
interoperation, doesn't actually help any of the privacy concerns that
are being raised, doesn't solve anyone's problem, and sets up the
registry as a crypto-normative repository -- a state of affairs that
several people objected to when we tried to do this explicitly (I
still bear the scars from that lashing).

I am tired of the self-appointed Internet Cops attempting to regulate
the taste of people wanting to use the DNS.  If people don't like the
allocation policy for DNS RRTYPEs, then they are free to spin up a new
DNSTASTE WG and get the policy changed.  I will attend the BoF and
blow raspberries.  But I look forward to the bright future in which
the DNS contains only TXT records, which we retrieve via port 80 or
(if lucky) port 443.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ted.ietf@gmail.com  Tue May 28 09:58:40 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A554711E80A2 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 09:58:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShIMsDm0W2Mu for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 09:58:38 -0700 (PDT)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 3058921F9918 for <ietf@ietf.org>; Tue, 28 May 2013 09:58:37 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 17so1336258iea.31 for <ietf@ietf.org>; Tue, 28 May 2013 09:58:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zbzV9sRAvy7nMVewzT49nJpi5fnsKAauQBGCkWbXUTI=; b=rZDH9vWdM85Y40XaivFZrXEkK9a0lf043c5CQpIKHBKrjLoM+7E/Z8If4AK3LmawhO wulT6J4mSdRbttXlzcP6tcZKWJ13GCk8FW1T1QcXjiEnU9BicsGAui/eqwL4kYNLenMg NEF+zvsdNAGjsUZg3GPKfrXpEQSHI5ynPT7MpJlViFUz7B6qn7mwrEkbMgtS5lyxW64p CNhhI2TYuzZ/0FwYrfXIphOicA/5oZK9NwTtFPhO28YnADLHF/BwzDvjKFVy42vscprN JFutN+VSM4TF3rOV0bur9KevDr7zp9LI2ZkD5seNnHB/QLATHlQXs/KDYMb5rPQTI9oM 1P8Q==
MIME-Version: 1.0
X-Received: by 10.42.131.73 with SMTP id y9mr19676980ics.22.1369760317618; Tue, 28 May 2013 09:58:37 -0700 (PDT)
Received: by 10.42.177.2 with HTTP; Tue, 28 May 2013 09:58:37 -0700 (PDT)
In-Reply-To: <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net>
Date: Tue, 28 May 2013 09:58:37 -0700
Message-ID: <CA+9kkMBLGQFBk+nqBQQMeWw4OoJ26pvfB99HECN=oKkAc+Qzsw@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Ted Hardie <ted.ietf@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=90e6ba6e901c28c33f04ddca2d01
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 16:58:40 -0000

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

On Sat, May 25, 2013 at 12:10 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> James:
>
> > did you know that you have a audio/video realtime interactive
> communications WG churning out proposals and solutions that is *actively*
> ignoring "emergency communications" in its entirety? No? Look at RTCweb,
> which will become a dominant form of interactive communications between
> humans in the near future. You have an equally active WG in the same area
> that is addressing emergency communications (ECRIT) that is further
> along/mature in its documents (i.e., they've already produced the bulk of
> their RFCs, specifically RFC 6443 and 6881).
> >
> > Given that young people already think contacting a local emergency call
> center (PSAP) can or should be achievable through SMS, IM, twitter and
> Facebook... just how long does anyone think it will be before calling
> 911/112/999 will be requested or mandated through WEBrtc/RTCweb?
> >
> > Waiting will only make it more painful to retrofit it into the future
> RFCs produced by RTCweb.
>
> I knew that WebRTC is happening fast, including implementations coming out
> before standards. I don't think everyone have yet realised the full impact
> this technology will have.
>
> I didn't know about the details of the emergency communications situation.
> But it is always difficult to balance getting something out early vs.
> complete. I know how much pressure there is on the working groups to keep
> up with things actually happening in the browsers and organisations setting
> up to use this technology. Do you think the retrofit will be problematic,
> and do you have a specific suggestion about what should be included today?
>
> Jari
>
>
I'm replying here, rather than down thread, because I believe it's
important to tackle two different statements here:  one James' and one
Jari's.

The first is James' that RTCWEB is ignoring Emergency Services.  Perhaps by
"actively ignoring" James means that the working group considered emergency
services and made a decision he did not agree with, which is that the
baseline capabilities already allows a PSAP or other emergency service to
provide a WebRTC application that would work to connect you to its
emergency responders, and that this was enough.

As context, it's very important to recognize that the WebRTC efforts in the
IETF and W3C *are not building a telephone into a browser*.  We could have
done that in a few weeks.   The groups *are* creating building blocks that
allow a javascript application within a browser or mobile context to add
peer-to-peer audio, video, or data channels to whatever *its* application
happens to be.  That application can be a game (we often use a poker game
as an example here), a puzzle (there's an example where you compete with a
peer in unscrambling a tiled video feed), or a pure data exchange (where
neither audio or video are passed).

In that context, the group considered two questions:

can you use the WebRTC building blocks to create an application to talk to
emergency responders?

should every application be required to have the ability to talk to
emergency responders?

It gave the answer to the first one as "yes", and I am convinced that any
emergency responder that wished to create such an application could do so
with the existing building blocks.  A set of emergency responders could
even create and distribute one that was highly generalized and took
advantage of  LoST's facilities to be useful in many locations.

To the second question, the working group answered "no".  There are
applications of WebRTC which are not general-purpose communications,
including some applications where there will be no audio or video at all.
Requiring that a puzzle should provide you 911 service because it happens
to provide have live video is not really sensible.  Fundamentally, making
every application also be a generalized telephony application with ECRIT
support makes no more sense here than it would for desktop applications;
you could equally require a text processor connected to the network to
support texting emergency responders--after all, it has the UI facilities
and the user's attention, right?

The second statement is Jari's, which seems to imply that the
implementations coming out before standards is a problem in the WebRTC
case.  The implementers in this case are also very active contributors to
both the IETF and W3C efforts, and they are feeding implementation
experience into the process.  That's a good thing, since it is coming along
with a willingness to change implementations to match group consensus.
That won't last forever, obviously, but we have that now and should
continue to take advantage of it while we do.

That's my personal take, in any case, as someone who has been actively
involved in both efforts.

regards,

Ted Hardie

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

On Sat, May 25, 2013 at 12:10 AM, Jari Arkko <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@piuha.net</a>=
&gt;</span> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
James:<br>
<br>
&gt; did you know that you have a audio/video realtime interactive communic=
ations WG churning out proposals and solutions that is *actively* ignoring =
&quot;emergency communications&quot; in its entirety? No? Look at RTCweb, w=
hich will become a dominant form of interactive communications between huma=
ns in the near future. You have an equally active WG in the same area that =
is addressing emergency communications (ECRIT) that is further along/mature=
 in its documents (i.e., they&#39;ve already produced the bulk of their RFC=
s, specifically RFC 6443 and 6881).<br>

&gt;<br>
&gt; Given that young people already think contacting a local emergency cal=
l center (PSAP) can or should be achievable through SMS, IM, twitter and Fa=
cebook... just how long does anyone think it will be before calling 911/112=
/999 will be requested or mandated through WEBrtc/RTCweb?<br>

&gt;<br>
&gt; Waiting will only make it more painful to retrofit it into the future =
RFCs produced by RTCweb.<br>
<br>
I knew that WebRTC is happening fast, including implementations coming out =
before standards. I don&#39;t think everyone have yet realised the full imp=
act this technology will have.<br>
<br>
I didn&#39;t know about the details of the emergency communications situati=
on. But it is always difficult to balance getting something out early vs. c=
omplete. I know how much pressure there is on the working groups to keep up=
 with things actually happening in the browsers and organisations setting u=
p to use this technology. Do you think the retrofit will be problematic, an=
d do you have a specific suggestion about what should be included today?<br=
>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br>I&#39;m replying here, rather than dow=
n thread, because I believe it&#39;s important to tackle two different stat=
ements here:=A0 one James&#39; and one Jari&#39;s.<br><br>The first is Jame=
s&#39; that RTCWEB is ignoring Emergency Services.=A0 Perhaps by &quot;acti=
vely ignoring&quot; James means that the working group considered emergency=
 services and made a decision he did not agree with, which is that the base=
line capabilities already allows a PSAP or other emergency service to provi=
de a WebRTC application that would work to connect you to its emergency res=
ponders, and that this was enough.=A0 <br>
<br>As context, it&#39;s very important to recognize that the WebRTC effort=
s in the IETF and W3C *are not building a telephone into a browser*.=A0 We =
could have done that in a few weeks.=A0=A0 The groups *are* creating buildi=
ng blocks that allow a javascript application within a browser or mobile co=
ntext to add peer-to-peer audio, video, or data channels to whatever *its* =
application happens to be.=A0 That application can be a game (we often use =
a poker game as an example here), a puzzle (there&#39;s an example where yo=
u compete with a peer in unscrambling a tiled video feed), or a pure data e=
xchange (where neither audio or video are passed). <br>
<br>In that context, the group considered two questions:=A0 <br><br>can you=
 use the WebRTC building blocks to create an application to talk to emergen=
cy responders? <br><br>should every application be required to have the abi=
lity to talk to emergency responders?<br>
<br>It gave the answer to the first one as &quot;yes&quot;, and I am convin=
ced that any emergency responder that wished to create such an application =
could do so with the existing building blocks.=A0 A set of emergency respon=
ders could even create and distribute one that was highly generalized and t=
ook advantage of=A0 LoST&#39;s facilities to be useful in many locations. <=
br>
<br>To the second question, the working group answered &quot;no&quot;.=A0 T=
here are applications of WebRTC which are not general-purpose communication=
s, including some applications where there will be no audio or video at all=
.=A0 Requiring that a puzzle should provide you 911 service because it happ=
ens to provide have live video is not really sensible.=A0 Fundamentally, ma=
king every application also be a generalized telephony application with ECR=
IT support makes no more sense here than it would for desktop applications;=
 you could equally require a text processor connected to the network to sup=
port texting emergency responders--after all, it has the UI facilities and =
the user&#39;s attention, right?=A0 <br>
<br>The second statement is Jari&#39;s, which seems to imply that the imple=
mentations coming out before standards is a problem in the WebRTC case.=A0 =
The implementers in this case are also very active contributors to both the=
 IETF and W3C efforts, and they are feeding implementation experience into =
the process.=A0 That&#39;s a good thing, since it is coming along with a wi=
llingness to change implementations to match group consensus.=A0 That won&#=
39;t last forever, obviously, but we have that now and should continue to t=
ake advantage of it while we do.<br>
<br>That&#39;s my personal take, in any case, as someone who has been activ=
ely involved in both efforts.<br><br>regards,<br><br>Ted Hardie<br><br><br>

--90e6ba6e901c28c33f04ddca2d01--

From melinda.shore@gmail.com  Tue May 28 10:15:27 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7F321F96B0 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.066
X-Spam-Level: 
X-Spam-Status: No, score=-2.066 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXfVTkyC1Zq2 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:15:21 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id C536321F9590 for <ietf@ietf.org>; Tue, 28 May 2013 10:15:21 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id bv13so5987927pdb.26 for <ietf@ietf.org>; Tue, 28 May 2013 10:15:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ct+FWIjpVU3F2E5Qdl/gp/SCQOfORifKUvnh79lH+b4=; b=sTSunGJzDMnvPyULE5GxxbQzbmoKhHTOCtV9WX8wFaTUkSNsLVDbRc6JMeTscF9DWz DZUqt3bSjYxLQ8bciGJwdzleuQem7p5uaYjeyLUwNaIfVQc2enNmyutawAPFSlq7Ewxp rrWholhm4dxnHFckWhi+5EuPxgwxRst3Zv8OEWnG3S4DAeq+/fngnZO91tNnlVkJqIeP eT34z+4I27FJteZ5Mupo1lS/Gp9NN3IeXT6qlgsGnkw0jdmcD/S6rPTLxe8n8wCp1MZu PPGdUBf3c2i1RQM1fKGxJ2KqE7V2Mv86u7UgdyluDzh/QwwjfJ8CGY3VpEeUtk5LFaRe FNkw==
X-Received: by 10.68.164.226 with SMTP id yt2mr34960106pbb.203.1369761321330;  Tue, 28 May 2013 10:15:21 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id wi6sm33620252pbc.22.2013.05.28.10.15.18 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 10:15:19 -0700 (PDT)
Message-ID: <51A4E625.3020406@gmail.com>
Date: Tue, 28 May 2013 09:15:17 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>
In-Reply-To: <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 17:15:28 -0000

On 5/28/13 6:20 AM, Christian O'Flaherty wrote:
> Probably, this lack of social interaction in our region is one of
> the main reasons for low participation. Most of latin american
> IETFers are currently living outside the region and they engaged in
> the IETF when living in the US or Europe. It's difficult to be
> involved when no one else around is working in it or think it doesn't
> fit well in their current work. A physical meeting will help to
> "demystify" the IETF, making it "accesible" from a professional
> perspective.

Any sense of why that didn't happen with Australians after
the Adelaide meeting?

I'm not opposed to meeting in South America but there have
been an awful lot of assertions about this or that happening
if we do, without a lot of supporting evidence.  History,
unfortunately, doesn't support many of these assertions, and
I think beating the meeting location question to death is
at least some small distraction from trying to get at the core
issues.

For whatever it's worth, I was participating on IETF mailing lists
well before attending a meeting.  Granted, I'm a native English
speaker and wasn't dealing with that as an issue but probably
more to the point was that there was work going on in the IETF
that directly impacted work I was doing myself.

Melinda

From joelja@bogus.com  Tue May 28 10:16:00 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 555E011E80AE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:16:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sn1kzvndJVUi for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:15:59 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1B421F9080 for <ietf@ietf.org>; Tue, 28 May 2013 10:15:52 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4SHFnEp006278 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 28 May 2013 17:15:50 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A4E640.9050707@bogus.com>
Date: Tue, 28 May 2013 10:15:44 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>	<CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com>	<CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>	<519E7E83.9000809@gmail.com>	<CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com>	<519E94AC.3060500@gmail.com>	<8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com>	<193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>	<519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com>	<519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>
In-Reply-To: <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 28 May 2013 17:15:50 +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, 28 May 2013 17:16:00 -0000

On 5/23/13 8:02 PM, David Conrad wrote:
> On May 23, 2013, at 7:44 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
>> So the question is why we aren't seeing more drafts, reviews, and
>> discussions from people in Central and South America,
> Language?
It would seem likely when the participation is heaviliy biased towards 
equipment vendors and software tooling that the participants would be 
more representative of where the concentration of the development sideo 
of that work occurs. Comparative advantage isn't just the domain of 
agricultural products, extractive industries, and low-cost 
manufacturing. That seems likely to be part and parcel of the diversity 
discussion.

From sm@resistor.net  Tue May 28 10:16:31 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E02C11E80E9 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.166
X-Spam-Level: 
X-Spam-Status: No, score=-102.166 tagged_above=-999 required=5 tests=[AWL=0.433, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kB4u6e2iJuOU for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:16:29 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D21F511E80E6 for <ietf@ietf.org>; Tue, 28 May 2013 10:16:29 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4SHGITS001815; Tue, 28 May 2013 10:16:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369761384; bh=7ZZ5PiosvKiqQcEo2B1WwHR2YWccFX+tgEHhuxPLfHI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OqPkhqybsEpUVczzAgFF26h0pfwJhncCCyKqbWxHjeSjWEmOadIK+TCxrT901xZqk TC0flfFPD1WbencE/PGnnVD86AdheJiIPPaZqL0mO2pUkoD942R/l8XesYINkInKYo vyykpf/Op27gbdOOGgDTvl511ImOp92OI4a68gxw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369761384; i=@resistor.net; bh=7ZZ5PiosvKiqQcEo2B1WwHR2YWccFX+tgEHhuxPLfHI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=N5qKPK+hnkEm7NOkz18s9bM4fvKWYZ6cD+dvqCkLVPL88YBbWoA6ZrpYYmUkBkaPp 6nYg394Ioem3YmLhAbH9En0DCQp1YrZ8fBnVZ8D7qtUXUVICif2guNxSR2htlvnuEg 1GYzLItpvYQ7NxHWeukxrCgfhGSZ8Mh6qqonilw8=
Message-Id: <6.2.5.6.2.20130528075648.0e42c420@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 28 May 2013 09:41:01 -0700
To: Joe Abley <jabley@hopcount.ca>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-Reply-To: <5807146640630736649@unknownmsgid>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <6.2.5.6.2.20130527232315.0c2c56b8@resistor.net> <5807146640630736649@unknownmsgid>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 17:16:31 -0000

Hi Joe,
At 03:12 28-05-2013, Joe Abley wrote:
>Note that there's no suggestion that these RRTypes are required by the
>CRTC. The example given was for a situation where Interop would have
>been beneficial (so that cable resellers have an obvious, stable and
>supported way of encoding this kind of information.

Ok.

>The opposite actually: cable operators are required to provide access
>to subscribers on behalf of third parties in order to promote
>competition. There are multiple such cable providers and multiple such
>resellers.

Yes.

>(TekSavvy is one such reseller of multiple cable companies' access networks.)

Ok.

>Feel free to point out the gaps, and/or to suggest text.

I'll give it a try.  I suggest talking to the Area Director to see 
what's workable.

I would drop Section 6 of the draft as I no longer need a use case to 
get an RRTYPE assignment.  There is a typo for "RRTPES" in Section 
7.  I would start Section 9 with "There are privacy concerns ...".  I 
would replace the third paragraph with:

   The user should be provided with a disclosure statement that clearly
   mentions:

   - How the EUI addresses published in DNS will be used and protected

   - What privacy policies are applicable

   The disclosure statement is to enable the user to make an informed decision
   about whether the disclosure of the information is acceptable considering
   local laws and customs.

I would rename Section 9 as "Privacy Considerations".  I don't know 
what to put in the new Security Considerations section.  Maybe 
"Publishing EUI addresses in DNS lowers the security of the Internet".

Regards,
-sm 


From fernando@gont.com.ar  Tue May 28 10:31:55 2013
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 952D621F9711 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:31:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jveYiz1NUpBP for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:31:55 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 07FB821F96CC for <ietf@ietf.org>; Tue, 28 May 2013 10:31:53 -0700 (PDT)
Received: from [2001:5c0:1400:a::719] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fernando@gont.com.ar>) id 1UhNkV-0007QZ-8K; Tue, 28 May 2013 19:31:51 +0200
Message-ID: <51A4E5B5.3020109@gont.com.ar>
Date: Tue, 28 May 2013 19:13:25 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Juliao Braga <juliao@braga.eti.br>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br>
In-Reply-To: <51A4CB0D.9010001@braga.eti.br>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 17:31:56 -0000

Julio,

I'm worried about people making statements on a random basis.

I assume that many people (IAOC and many others) have made a lot of
effort before getting to the point of formally proposing/suggesting to
have an IETF meeting in Buenos Aires. I bet much of that effort had to
do with making an informed decision on the subject.

However, so far I've read a number of rather uninformed claims about how
bad/not_recommended having an IETF meeting in Buenos Aires would be
(besides the usual discussion of whether meeting should be held where
most of the participants come from, which is a different issue).

IMO, throwing out random comments (arbitrary, or based on what one
"heard", etc.) tends to bias the discussion in an inappropriate way.

Thanks,
Fernando




On 05/28/2013 05:19 PM, Juliao Braga wrote:
> Hi Fernando,
> 
> Please, read my sentence complementary to comment:
> 
> "...But who should tell us about the true cenary would be our
> Argentine friends."
> 
> Regards,
> 
> Julião
> Em 28/05/2013 10:36, Fernando Gont escreveu:
>> On 05/27/2013 07:31 AM, Juliao Braga wrote:
>>> According to the news published for a long time in Brazilian newspapers
>>> and magazines, Buenos Aires (a wonderful place!) would not be
>>> recommended.
>>
>> Recommended for what? And on what basis?
>>
>> Cheers,
>>
> 


-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From joelja@bogus.com  Tue May 28 10:35:21 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 594C921F9735 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:35:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jab4pnKmtdPp for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:35:20 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 794FC21F9738 for <ietf@ietf.org>; Tue, 28 May 2013 10:35:20 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4SHZFfo006624 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 28 May 2013 17:35:16 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A4EACE.60109@bogus.com>
Date: Tue, 28 May 2013 10:35:10 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: SM <sm@resistor.net>, Joe Abley <jabley@hopcount.ca>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource Records for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com>	<51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com>	<CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com>	<6.2.5.6.2.20130527232315.0c2c56b8@resistor.net>	<5807146640630736649@unknownmsgid> <6.2.5.6.2.20130528075648.0e42c420@resistor.net>
In-Reply-To: <6.2.5.6.2.20130528075648.0e42c420@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 28 May 2013 17:35:16 +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, 28 May 2013 17:35:21 -0000

On 5/28/13 9:41 AM, SM wrote:
> Hi Joe,
> At 03:12 28-05-2013, Joe Abley wrote:
>> Note that there's no suggestion that these RRTypes are required by the
>> CRTC. The example given was for a situation where Interop would have
>> been beneficial (so that cable resellers have an obvious, stable and
>> supported way of encoding this kind of information.
>
> Ok.
>
>> The opposite actually: cable operators are required to provide access
>> to subscribers on behalf of third parties in order to promote
>> competition. There are multiple such cable providers and multiple such
>> resellers.
>
> Yes.
>
>> (TekSavvy is one such reseller of multiple cable companies' access 
>> networks.)
>
> Ok.
>
>> Feel free to point out the gaps, and/or to suggest text.
>
> I'll give it a try.  I suggest talking to the Area Director to see 
> what's workable.
>
> I would drop Section 6 of the draft as I no longer need a use case to 
> get an RRTYPE assignment.  There is a typo for "RRTPES" in Section 7.  
> I would start Section 9 with "There are privacy concerns ...".  I 
> would replace the third paragraph with:
>
For some background. The usecase facilitates discussion and 
justification of the draft. It is not about justifying the RRtype (which 
was assigned under the rules of that registry).

It's in there because the sponsoring AD requested it after feedback 
during the dnsext dicussion.
>   The user should be provided with a disclosure statement that clearly
>   mentions:
>
>   - How the EUI addresses published in DNS will be used and protected
>
>   - What privacy policies are applicable
>
>   The disclosure statement is to enable the user to make an informed 
> decision
>   about whether the disclosure of the information is acceptable 
> considering
>   local laws and customs.
>
> I would rename Section 9 as "Privacy Considerations".  I don't know 
> what to put in the new Security Considerations section. Maybe 
> "Publishing EUI addresses in DNS lowers the security of the Internet".
>
> Regards,
> -sm


From carlosm3011@gmail.com  Tue May 28 10:37:17 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7AE21F91B1 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sdxi1s39M+pn for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:37:17 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACEE21F9285 for <ietf@ietf.org>; Tue, 28 May 2013 10:37:11 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id f64so971368yha.40 for <ietf@ietf.org>; Tue, 28 May 2013 10:37:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=WmIT2wfBFqdG0oC2lVorAdZ8btZStASR5c6selwTzW8=; b=fI3hmSqvToOZUWGczPbCq0lARY1EFCC2LcvvBvOPkSQTVC85RZMQADHFnvQ1eocbVg YhZYgcUEqSrKcskWT45S+IpnugjRqK1HVNZWFDqGVMUY5kql7Bq1Xio85lR42slz/zFj ttKoEUZKlUNcRvUT7hL1s8thQ6GVZODR0VKXo1Pm91jnIJUVxNoMDeyzmE/UC9lphkK6 qeLaSchXG0rK1Dn5SqaYeLybCSqVjbp7Zop8bVdMFImBPcwAKT2Ujpu4WWl6X2IkTasg LdAA3OFyQ/khfQZkxfgCpy1i+vWTM37B9M52H9ZR+7m6qm2S7Hk26T8A1XO9jHkC2JXl 1ciw==
X-Received: by 10.236.88.228 with SMTP id a64mr16007292yhf.85.1369762630468; Tue, 28 May 2013 10:37:10 -0700 (PDT)
Received: from europa.local ([200.20.164.185]) by mx.google.com with ESMTPSA id a24sm47371218yho.24.2013.05.28.10.37.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 10:37:09 -0700 (PDT)
Message-ID: <51A4EB42.1000501@gmail.com>
Date: Tue, 28 May 2013 14:37:06 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar>
In-Reply-To: <51A4B2C6.3050706@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 17:37:17 -0000

The bad things that happen in Argentina financially affect only
Argentinians. I'm not saying this is a good thing overall, just saying
that this isn't a problem for tourists and certainly won't be a problem
for IETFers.

Probably these financial 'issues' will even affect positively the
conference's bottom line, as everything is very cheap when priced in
dollars.

If you take a stroll through downtown Buenos Aires today, you'll listen
to many different languages. The place is packed with foreigners, as the
food is great, the city is very nice and everything appears very cheap.

cheers!

~Carlos


On 5/28/13 10:36 AM, Fernando Gont wrote:
> On 05/27/2013 07:31 AM, Juliao Braga wrote:
>> According to the news published for a long time in Brazilian newspapers
>> and magazines, Buenos Aires (a wonderful place!) would not be
>> recommended.
> 
> Recommended for what? And on what basis?
> 
> Cheers,
> 

From spencer@wonderhamster.org  Tue May 28 10:43:27 2013
Return-Path: <spencer@wonderhamster.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 3D43A21E8083 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:43:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.543
X-Spam-Level: 
X-Spam-Status: No, score=-101.543 tagged_above=-999 required=5 tests=[AWL=1.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Hnonc3NHne2 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:43:21 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 3703221E805E for <ietf@ietf.org>; Tue, 28 May 2013 10:43:21 -0700 (PDT)
Received: from [192.168.1.74] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MPDRo-1UlnmJ2Z2O-005Bnw; Tue, 28 May 2013 13:43:15 -0400
Message-ID: <51A4ECB5.3040708@wonderhamster.org>
Date: Tue, 28 May 2013 12:43:17 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A4CB9E.6020103@joelhalpern.com>
In-Reply-To: <51A4CB9E.6020103@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:OKcajlpSx7Va+co4ZfjrYPOhyAtVP+q8wlLzoaf8NV2 zbyl1zQp29IBPNo2hxDzK18gf40qbz5Zsnd/qKCf5afuqMsfwR 8i1zwSBzCd99nuLwiRIPM+XbxSqvO978o851gooLSpnFUyzeg9 Mfr4pK3H7UM21pH3mOkCTo7RXaDXeYhwyxtMQlM+6EO9qpEJ+z 5dGCfG5886nxqx88XU3gRofNr/MNt1emng6kSkQolm8/eELGpX O3vkiha23sVZfBBuVlbGwUmhbwe/ysiFaTi+fc2qOyc6llDc36 3c284wvQTmrEDwaS6b4bhuRY3P+7ZcHBKxOEQHUzwf4pzneYK3 BM1ZLc+++0G2s7LjW4kjMznnxjCXFJ+bCBo5m9zMN
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: Tue, 28 May 2013 17:43:27 -0000

On 5/28/2013 10:22 AM, Joel M. Halpern wrote:
> In reading through the draft, particularly the section on questions for
> WG adoption of a draft, I did not see the questions I consider most
> pertinent:

I appreciate Dave and Adrian for producing this helpful start, and I'm 
mostly comfortable with where this conversation has gone since Adrian 
asked for feedback on this list.

I wanted specifically to echo Joel's suggestions for additional questions.

> Does the WG think this is a reasonable (preferably good) basis for
> starting to work collectively on the deliverable?

I read this as "is this stable enough for a working group to work on it, 
or might we still want to tell some small number of people to go off in 
a corner and try again to produce something that IS a reasonable basis?"

I agree. To the extent that a working group really does control the 
contents of a working group draft, if the working group doesn't agree 
that the draft is a reasonable basis, making consensus calls about 
massive rewrites seems more painful than we are hoping for.

> Another question many WGs have found useful is:
> Are there enough people interested and willing to write and / or review
> the document?

Exactly. We should work on working group drafts. If a working group 
doesn't have the resources and willingness to work on the document, I'm 
not sure how much sense it makes to adopt it as a draft that's being 
officially ignored by the working group :-)

Spencer

From abdussalambaryun@gmail.com  Tue May 28 10:46:45 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2DDD21F94E1 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.765
X-Spam-Level: 
X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=-0.167, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfHEvCSYVjCJ for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 10:46:41 -0700 (PDT)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by ietfa.amsl.com (Postfix) with ESMTP id DDBAE11E80F8 for <ietf@ietf.org>; Tue, 28 May 2013 10:46:41 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y11so7946652pdj.14 for <ietf@ietf.org>; Tue, 28 May 2013 10:46:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8P3kw4R4i1VQ2a48hDnF0ep+pScMaReDhMoo5zjldAE=; b=tudQBv7EbEBluij7RV0qB/xhu1aMkR3MDgDreUTqLhzso0lnSY9gRpJuQ17Z0JUgun yJzS17oMvOrznFrQGXqAO5ylzjeiKJymPIvQ41vr8z9r5kTytkCAsVe1wH8X980XQF50 jQuBrMVUhJYSZx5d8VeaXmfhBcBlL+z2/qUzLxho01vOaMlQidULB/EGszsMW0PrA+pI WKYbW17yyaNuH9ADoVuQY9ZIx8FNp2M/J1I9jofNoGJ1Kk5uvumz3PUlf2JwATG+LBZb uYx6k2DD4HXzXpRGyOsQm6mN+JCuUhXOLybeStOKk8KS/SKA1XkXvkX+Rz2RBHLs2oTF d+7g==
MIME-Version: 1.0
X-Received: by 10.66.144.98 with SMTP id sl2mr35790367pab.92.1369763201609; Tue, 28 May 2013 10:46:41 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Tue, 28 May 2013 10:46:41 -0700 (PDT)
In-Reply-To: <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com>
Date: Tue, 28 May 2013 18:46:41 +0100
Message-ID: <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=047d7b6dbe640ef9f604ddcad969
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, 28 May 2013 17:46:46 -0000

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

by looking into the statistics of I-Ds and RFCs, it is strange that we get
sometimes high rate in the I-D going in IETF from some regions but the
success rate of I-Ds to become RFCs is very low (5- 50). So the only region
that is producing RFCs with high rate (about 200 per year) is North America
even though there is a high rate of I-Ds created. No sure Why is that
result, or waste of efforts, or maybe I misunderstood the figures,

How many I-Ds per year of Asia-region are adopted by IETF WGs?
How many I-Ds per year of Europe-region are adopted by IETF WGs?

AB



On Mon, May 27, 2013 at 4:46 PM, Eggert, Lars <lars@netapp.com> wrote:

> On May 27, 2013, at 15:31, Abdussalam Baryun <abdussalambaryun@gmail.com>
> wrote:
> > On 5/27/13, Eggert, Lars <lars@netapp.com> wrote:
> >> On May 27, 2013, at 12:10, Abdussalam Baryun <
> abdussalambaryun@gmail.com>
> >> wrote:
> >>> Each IETF document mentions the authors place address (I may suggest
> >>> adding region, as a categorised by IETF), but not sure of history
> >>> statistics of how many IETF-documents produced by authors in South
> >>> America, Africa, or Asia, or others.
> >>
> >> http://www.arkko.com/tools/stats/d-countrydistr.html and related pages
> >
> > I read that before, but does not show documents/RFCs per region. It
> > shows drafts per countries. For example, does not show the drafts from
> > South America. Does not show all regions in sequence of the most
> > participated region.
>
> That's why I wrote *and related pages*.
>
> Clicking around Jari's pages, you will easily find
> http://www.arkko.com/tools/rfcstats/d-contdistr.html as well as many more
> stats.
>
> As for "most participated region", look at the reports from the IAOC:
> http://iaoc.ietf.org/reports.html
>
> Lars

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

<div dir=3D"ltr"><div>by looking into the statistics of I-Ds and RFCs, it i=
s strange that we get sometimes high rate in the I-D going in IETF from som=
e regions but the success rate of I-Ds to become RFCs is very low (5- 50). =
So the only region that is producing RFCs with high rate (about 200 per yea=
r)=A0is North America even though there is a high rate of I-Ds created. No =
sure Why is that result, or waste of efforts, or maybe I misunderstood the =
figures,</div>
<div>=A0</div><div>How many I-Ds per year of Asia-region are adopted by IET=
F=A0WGs?</div><div>How many I-Ds per year of=A0Europe-region are adopted by=
 IETF WGs?</div><div>=A0</div><div>AB</div><div>=A0</div></div><div class=
=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Mon, May 27, 2013 at 4:46 PM, Eggert,=
 Lars <span dir=3D"ltr">&lt;<a href=3D"mailto:lars@netapp.com" target=3D"_b=
lank">lars@netapp.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<div class=3D"HOEnZb"><div class=3D"h5">On May 27, 2013, at 15:31, Abdussal=
am Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalambaryu=
n@gmail.com</a>&gt; wrote:<br>
&gt; On 5/27/13, Eggert, Lars &lt;<a href=3D"mailto:lars@netapp.com">lars@n=
etapp.com</a>&gt; wrote:<br>
&gt;&gt; On May 27, 2013, at 12:10, Abdussalam Baryun &lt;<a href=3D"mailto=
:abdussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt;<br>
&gt;&gt; wrote:<br>
&gt;&gt;&gt; Each IETF document mentions the authors place address (I may s=
uggest<br>
&gt;&gt;&gt; adding region, as a categorised by IETF), but not sure of hist=
ory<br>
&gt;&gt;&gt; statistics of how many IETF-documents produced by authors in S=
outh<br>
&gt;&gt;&gt; America, Africa, or Asia, or others.<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"http://www.arkko.com/tools/stats/d-countrydistr.html" t=
arget=3D"_blank">http://www.arkko.com/tools/stats/d-countrydistr.html</a> a=
nd related pages<br>
&gt;<br>
&gt; I read that before, but does not show documents/RFCs per region. It<br=
>
&gt; shows drafts per countries. For example, does not show the drafts from=
<br>
&gt; South America. Does not show all regions in sequence of the most<br>
&gt; participated region.<br>
<br>
</div></div>That&#39;s why I wrote *and related pages*.<br>
<br>
Clicking around Jari&#39;s pages, you will easily find <a href=3D"http://ww=
w.arkko.com/tools/rfcstats/d-contdistr.html" target=3D"_blank">http://www.a=
rkko.com/tools/rfcstats/d-contdistr.html</a> as well as many more stats.<br=
>

<br>
As for &quot;most participated region&quot;, look at the reports from the I=
AOC: <a href=3D"http://iaoc.ietf.org/reports.html" target=3D"_blank">http:/=
/iaoc.ietf.org/reports.html</a><br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Lars</font></span></blockquote></div><br></div>

--047d7b6dbe640ef9f604ddcad969--

From jmpolk@cisco.com  Tue May 28 11:20:51 2013
Return-Path: <jmpolk@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 25E1121F9434 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HakcJ0tMwC7X for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:20:46 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB4421F93EC for <ietf@ietf.org>; Tue, 28 May 2013 11:20:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6406; q=dns/txt; s=iport; t=1369765236; x=1370974836; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=RFA1XQhKGj3Vd00fVGxPNKYUItmFhs9bk9iVhy1wbbo=; b=mOF7FAiOZxBjoWhZSevnfPUbiVk3py3TWaWFU63MfSAOBJfX9KdcYJv5 pkWLErvx+1AKkCdJZyQI04eXVUtkAn5RUcFQluPpNmKmRxlR1r1G3n/Sz ecmSK+KZHlxGx5akVJEn/j6p6/nVpPAN8ziP0ai3JJdJ8rGvORNZm8Qpm A=;
X-IronPort-AV: E=Sophos;i="4.87,759,1363132800"; d="scan'208";a="215825905"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 28 May 2013 18:20:34 +0000
Received: from jmpolk-WS.cisco.com ([10.89.10.72]) (authenticated bits=0) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r4SIKXMS029096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 May 2013 18:20:33 GMT
Message-Id: <201305281820.r4SIKXMS029096@rcdn-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 28 May 2013 13:20:34 -0500
To: Ted Hardie <ted.ietf@gmail.com>, Jari Arkko <jari.arkko@piuha.net>
From: James Polk <jmpolk@cisco.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
In-Reply-To: <CA+9kkMBLGQFBk+nqBQQMeWw4OoJ26pvfB99HECN=oKkAc+Qzsw@mail.g mail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <CA+9kkMBLGQFBk+nqBQQMeWw4OoJ26pvfB99HECN=oKkAc+Qzsw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:20:51 -0000

At 11:58 AM 5/28/2013, Ted Hardie wrote:
>On Sat, May 25, 2013 at 12:10 AM, Jari Arkko 
><<mailto:jari.arkko@piuha.net>jari.arkko@piuha.net> wrote:
>James:
>
> > did you know that you have a audio/video realtime interactive 
> communications WG churning out proposals and solutions that is 
> *actively* ignoring "emergency communications" in its entirety? No? 
> Look at RTCweb, which will become a dominant form of interactive 
> communications between humans in the near future. You have an 
> equally active WG in the same area that is addressing emergency 
> communications (ECRIT) that is further along/mature in its 
> documents (i.e., they've already produced the bulk of their RFCs, 
> specifically RFC 6443 and 6881).
> >
> > Given that young people already think contacting a local 
> emergency call center (PSAP) can or should be achievable through 
> SMS, IM, twitter and Facebook... just how long does anyone think it 
> will be before calling 911/112/999 will be requested or mandated 
> through WEBrtc/RTCweb?
> >
> > Waiting will only make it more painful to retrofit it into the 
> future RFCs produced by RTCweb.
>
>I knew that WebRTC is happening fast, including implementations 
>coming out before standards. I don't think everyone have yet 
>realised the full impact this technology will have.
>
>I didn't know about the details of the emergency communications 
>situation. But it is always difficult to balance getting something 
>out early vs. complete. I know how much pressure there is on the 
>working groups to keep up with things actually happening in the 
>browsers and organisations setting up to use this technology. Do you 
>think the retrofit will be problematic, and do you have a specific 
>suggestion about what should be included today?
>
>Jari
>
>
>I'm replying here, rather than down thread, because I believe it's 
>important to tackle two different statements here:  one James' and one Jari's.
>
>The first is James' that RTCWEB is ignoring Emergency 
>Services.  Perhaps by "actively ignoring" James means that the 
>working group considered emergency services and made a decision he 
>did not agree with, which is that the baseline capabilities already 
>allows a PSAP or other emergency service to provide a WebRTC 
>application that would work to connect you to its emergency 
>responders, and that this was enough.
>
>As context, it's very important to recognize that the WebRTC efforts 
>in the IETF and W3C *are not building a telephone into a 
>browser*.  We could have done that in a few weeks.   The groups 
>*are* creating building blocks that allow a javascript application 
>within a browser or mobile context to add peer-to-peer audio, video, 
>or data channels to whatever *its* application happens to be.  That 
>application can be a game (we often use a poker game as an example 
>here), a puzzle (there's an example where you compete with a peer in 
>unscrambling a tiled video feed), or a pure data exchange (where 
>neither audio or video are passed).
>
>In that context, the group considered two questions:
>
>can you use the WebRTC building blocks to create an application to 
>talk to emergency responders?
>
>should every application be required to have the ability to talk to 
>emergency responders?
>
>It gave the answer to the first one as "yes", and I am convinced 
>that any emergency responder that wished to create such an 
>application could do so with the existing building blocks.  A set of 
>emergency responders could even create and distribute one that was 
>highly generalized and took advantage of  LoST's facilities to be 
>useful in many locations.
>
>To the second question, the working group answered "no".  There are 
>applications of WebRTC which are not general-purpose communications, 
>including some applications where there will be no audio or video at 
>all.  Requiring that a puzzle should provide you 911 service because 
>it happens to provide have live video is not really 
>sensible.  Fundamentally, making every application also be a 
>generalized telephony application with ECRIT support makes no more 
>sense here than it would for desktop applications; you could equally 
>require a text processor connected to the network to support texting 
>emergency responders--after all, it has the UI facilities and the 
>user's attention, right?
>
>The second statement is Jari's, which seems to imply that the 
>implementations coming out before standards is a problem in the 
>WebRTC case.  The implementers in this case are also very active 
>contributors to both the IETF and W3C efforts, and they are feeding 
>implementation experience into the process.  That's a good thing, 
>since it is coming along with a willingness to change 
>implementations to match group consensus.  That won't last forever, 
>obviously, but we have that now and should continue to take 
>advantage of it while we do.
>
>That's my personal take, in any case, as someone who has been 
>actively involved in both efforts.

Ted - this view (I believe) doesn't reconcile with the view stated by 
Henning's yesterday.

(truth be told, it's hard to separate Henning's stated views from his 
official title and his official organization, given that he writes 
the types of regulations the IETF community merely reads (about)...

"The most difficult part for any emergency calling system is location 
delivery. WebRTC probably doesn't have much impact on emergency calls 
if all the calls traverse a server of some kind and if the caller 
location can be looked up based on caller IP addresses, but once you 
have the end system involved in location determination (e.g., for 
mobile devices or for DHCP-delivered location), it has to know when a 
call is an emergency call as you otherwise end up providing location 
for every call, which is non-ideal from a privacy and battery perspective.

At least in the US, many of the WebRTC services would be considered 
"interconnected VoIP", so they are indeed subject to 911 obligations."

James

BTW- yeah, I know I'm picking a fight - but Jari singled this topic 
out as an example of how various regions of the world differ on how 
they handle certain applications, emergency services being one of a 
very short list he mentioned.


>regards,
>
>Ted Hardie
>


From juliao@braga.eti.br  Tue May 28 11:21:04 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EAB421F88FB for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ci3G4EeBSMIQ for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:21:03 -0700 (PDT)
Received: from mail-gg0-x231.google.com (mail-gg0-x231.google.com [IPv6:2607:f8b0:4002:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4F46321F87BB for <ietf@ietf.org>; Tue, 28 May 2013 11:20:54 -0700 (PDT)
Received: by mail-gg0-f177.google.com with SMTP id r4so2179697ggn.36 for <ietf@ietf.org>; Tue, 28 May 2013 11:20:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=G7l3/fwwBYNPnbjSoMDsD7ceacdJkLggp70gRvqfsgM=; b=LyOdy/uy8idtn9p5LpODPW6zJOdDOws0z3hYCLjuMMk7Bquv6Cb94tzwhkDyr1XRPv vlhBXNqgjQ5xvROeJUOgx1CaJbUMnuXd8tTqOtcto7hCyThoV3h3q4XGnyrYiz/76p9j rzxVjiy3bmqg3df0uajaKty8jBsUPw68/87d5g4bWI78Izg3m2/FifBIvxUAavSkc5Kn vw0auw2OYvOjFnE0VJGARy/+Y8PQ8sHiHXUhTGpxDPjhv7Rhw8B+NOoMoGjCyAgc1/Tv 3y2IRBRDYgr6ZQQ5TFY6rShWnTzLF3Nyrq1QLZvCLx1sPhCZI+Q267/POAs4UENe+OG0 QEHw==
X-Received: by 10.236.230.40 with SMTP id i38mr17233655yhq.170.1369765253236;  Tue, 28 May 2013 11:20:53 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id j20sm68265yhi.1.2013.05.28.11.20.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 11:20:52 -0700 (PDT)
Message-ID: <51A4F57C.8000902@braga.eti.br>
Date: Tue, 28 May 2013 15:20:44 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar>
In-Reply-To: <51A4E5B5.3020109@gont.com.ar>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Gm-Message-State: ALoCoQmg22uEbAYx3R6pw8/sYmlEAxAhZVL2yRvJeyC3Rx2WufJacPuXc3dckOFCoBjk49ZRJPB7
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:21:04 -0000

Dear Fernando,

If I have to decide about a meeting in Buenos Aires based in the
information that I read in the Brazilian newspapers and magazines I
decide to no. By this reason I need to listen from Argentine people, as
you. I believe this is the right way to decide.

The choice of Buenos Aires is a definitive fact, and I have no decision
concerns this selection. My approach was to reinforce the fact that only
you, in Argentina can really guide us, if the decision were to be
revoked. Buenos Aires was a beatiful choice!

It was not an arbitrary comment. It was real and oriented so that any
queries related to media reports, our people of Argentina should be heard.

Therefore, you should have no doubt that I'm hoping to have a meeting of
the IETF in Buenos Aires.

Best regards,

Julião

Em 28/05/2013 14:13, Fernando Gont escreveu:
> Julio,
> 
> I'm worried about people making statements on a random basis.
> 
> I assume that many people (IAOC and many others) have made a lot of
> effort before getting to the point of formally proposing/suggesting to
> have an IETF meeting in Buenos Aires. I bet much of that effort had to
> do with making an informed decision on the subject.
> 
> However, so far I've read a number of rather uninformed claims about how
> bad/not_recommended having an IETF meeting in Buenos Aires would be
> (besides the usual discussion of whether meeting should be held where
> most of the participants come from, which is a different issue).
> 
> IMO, throwing out random comments (arbitrary, or based on what one
> "heard", etc.) tends to bias the discussion in an inappropriate way.
> 
> Thanks,
> Fernando

From rlb@ipv.sx  Tue May 28 11:25:26 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4552D21F8F00 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:25:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.009
X-Spam-Level: 
X-Spam-Status: No, score=-0.009 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-Bi3sQfb5rR for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:25:16 -0700 (PDT)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A92C711E80A6 for <ietf@ietf.org>; Tue, 28 May 2013 11:25:16 -0700 (PDT)
Received: by mail-ob0-f170.google.com with SMTP id er7so9570594obc.29 for <ietf@ietf.org>; Tue, 28 May 2013 11:25:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=vOVNN8ZdFkeb/J50t5mjKVKlof99uvgAHbnzZdJV0SI=; b=JjwzYbEoRFu4mr0pIeCP5z8oYQYNIAyHxptO36G2NXRfPpq2U2Yivajx0MGVImAHIN n+uPL+Pl/1mUe3eLEJrsXRDRR6jVJjjreeBTD6I6xaQUj4sXVsQK5WfD1ARd3U4W3IGX YngBMW5uA/jWimomsg13oUZD0TUokUebn7vN27Ucysj/20kClRHCVLDcaRW3AQx0B71m jdnfUqr9PfsULOTqwsvlc1WqzGEn4ZXoQ1BzYt8vmUNi8IbYhyFlvwxLuBKZykME311q 8UB0o0S9wLgmcIQhJQN/IyqE6uBVp8fVe53eqf5RUPH8E6wPKXdwMxNM+HTawhVBK/6B hBfw==
MIME-Version: 1.0
X-Received: by 10.60.34.135 with SMTP id z7mr21672516oei.68.1369765516030; Tue, 28 May 2013 11:25:16 -0700 (PDT)
Received: by 10.60.17.9 with HTTP; Tue, 28 May 2013 11:25:15 -0700 (PDT)
X-Originating-IP: [192.1.51.101]
In-Reply-To: <201305281820.r4SIKXMS029096@rcdn-core-2.cisco.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <CA+9kkMBLGQFBk+nqBQQMeWw4OoJ26pvfB99HECN=oKkAc+Qzsw@mail.gmail.com> <201305281820.r4SIKXMS029096@rcdn-core-2.cisco.com>
Date: Tue, 28 May 2013 14:25:15 -0400
Message-ID: <CAL02cgTyCv80qH4cu=-O686VsuDuK46aedmKxJ9GxEBTres++w@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Richard Barnes <rlb@ipv.sx>
To: James Polk <jmpolk@cisco.com>
Content-Type: multipart/alternative; boundary=089e0122acb402443804ddcb630d
X-Gm-Message-State: ALoCoQkiy5SnmKs1F8Q6uPKei6Yfb5qnpXlxtAjzrVOald57bxwUi+Qt9TUawmg/RyBU5Xahiiqs
Cc: Ted Hardie <ted.ietf@gmail.com>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:25:26 -0000

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

I would suggest we not try to sort out on this list which sorts of Internet
services are subject to American regulations.


On Tue, May 28, 2013 at 2:20 PM, James Polk <jmpolk@cisco.com> wrote:

> At 11:58 AM 5/28/2013, Ted Hardie wrote:
>
>  On Sat, May 25, 2013 at 12:10 AM, Jari Arkko <<mailto:
>> jari.arkko@piuha.net>**jari.arkko@piuha.net <jari.arkko@piuha.net>>
>> wrote:
>> James:
>>
>> > did you know that you have a audio/video realtime interactive
>> communications WG churning out proposals and solutions that is *actively*
>> ignoring "emergency communications" in its entirety? No? Look at RTCweb,
>> which will become a dominant form of interactive communications between
>> humans in the near future. You have an equally active WG in the same area
>> that is addressing emergency communications (ECRIT) that is further
>> along/mature in its documents (i.e., they've already produced the bulk of
>> their RFCs, specifically RFC 6443 and 6881).
>> >
>> > Given that young people already think contacting a local emergency call
>> center (PSAP) can or should be achievable through SMS, IM, twitter and
>> Facebook... just how long does anyone think it will be before calling
>> 911/112/999 will be requested or mandated through WEBrtc/RTCweb?
>> >
>> > Waiting will only make it more painful to retrofit it into the future
>> RFCs produced by RTCweb.
>>
>> I knew that WebRTC is happening fast, including implementations coming
>> out before standards. I don't think everyone have yet realised the full
>> impact this technology will have.
>>
>> I didn't know about the details of the emergency communications
>> situation. But it is always difficult to balance getting something out
>> early vs. complete. I know how much pressure there is on the working groups
>> to keep up with things actually happening in the browsers and organisations
>> setting up to use this technology. Do you think the retrofit will be
>> problematic, and do you have a specific suggestion about what should be
>> included today?
>>
>> Jari
>>
>>
>> I'm replying here, rather than down thread, because I believe it's
>> important to tackle two different statements here:  one James' and one
>> Jari's.
>>
>> The first is James' that RTCWEB is ignoring Emergency Services.  Perhaps
>> by "actively ignoring" James means that the working group considered
>> emergency services and made a decision he did not agree with, which is that
>> the baseline capabilities already allows a PSAP or other emergency service
>> to provide a WebRTC application that would work to connect you to its
>> emergency responders, and that this was enough.
>>
>> As context, it's very important to recognize that the WebRTC efforts in
>> the IETF and W3C *are not building a telephone into a browser*.  We could
>> have done that in a few weeks.   The groups *are* creating building blocks
>> that allow a javascript application within a browser or mobile context to
>> add peer-to-peer audio, video, or data channels to whatever *its*
>> application happens to be.  That application can be a game (we often use a
>> poker game as an example here), a puzzle (there's an example where you
>> compete with a peer in unscrambling a tiled video feed), or a pure data
>> exchange (where neither audio or video are passed).
>>
>> In that context, the group considered two questions:
>>
>> can you use the WebRTC building blocks to create an application to talk
>> to emergency responders?
>>
>> should every application be required to have the ability to talk to
>> emergency responders?
>>
>> It gave the answer to the first one as "yes", and I am convinced that any
>> emergency responder that wished to create such an application could do so
>> with the existing building blocks.  A set of emergency responders could
>> even create and distribute one that was highly generalized and took
>> advantage of  LoST's facilities to be useful in many locations.
>>
>> To the second question, the working group answered "no".  There are
>> applications of WebRTC which are not general-purpose communications,
>> including some applications where there will be no audio or video at all.
>>  Requiring that a puzzle should provide you 911 service because it happens
>> to provide have live video is not really sensible.  Fundamentally, making
>> every application also be a generalized telephony application with ECRIT
>> support makes no more sense here than it would for desktop applications;
>> you could equally require a text processor connected to the network to
>> support texting emergency responders--after all, it has the UI facilities
>> and the user's attention, right?
>>
>> The second statement is Jari's, which seems to imply that the
>> implementations coming out before standards is a problem in the WebRTC
>> case.  The implementers in this case are also very active contributors to
>> both the IETF and W3C efforts, and they are feeding implementation
>> experience into the process.  That's a good thing, since it is coming along
>> with a willingness to change implementations to match group consensus.
>>  That won't last forever, obviously, but we have that now and should
>> continue to take advantage of it while we do.
>>
>> That's my personal take, in any case, as someone who has been actively
>> involved in both efforts.
>>
>
> Ted - this view (I believe) doesn't reconcile with the view stated by
> Henning's yesterday.
>
> (truth be told, it's hard to separate Henning's stated views from his
> official title and his official organization, given that he writes the
> types of regulations the IETF community merely reads (about)...
>
>
> "The most difficult part for any emergency calling system is location
> delivery. WebRTC probably doesn't have much impact on emergency calls if
> all the calls traverse a server of some kind and if the caller location can
> be looked up based on caller IP addresses, but once you have the end system
> involved in location determination (e.g., for mobile devices or for
> DHCP-delivered location), it has to know when a call is an emergency call
> as you otherwise end up providing location for every call, which is
> non-ideal from a privacy and battery perspective.
>
> At least in the US, many of the WebRTC services would be considered
> "interconnected VoIP", so they are indeed subject to 911 obligations."
>
> James
>
> BTW- yeah, I know I'm picking a fight - but Jari singled this topic out as
> an example of how various regions of the world differ on how they handle
> certain applications, emergency services being one of a very short list he
> mentioned.
>
>
>  regards,
>>
>> Ted Hardie
>>
>>
>

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

<div dir=3D"ltr">I would suggest we not try to sort out on this list which =
sorts of Internet services are subject to American regulations.</div><div c=
lass=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, May 28, 201=
3 at 2:20 PM, James Polk <span dir=3D"ltr">&lt;<a href=3D"mailto:jmpolk@cis=
co.com" target=3D"_blank">jmpolk@cisco.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">At 11:58 AM 5/28/2013, Ted Hardie wrote:<div=
><div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On Sat, May 25, 2013 at 12:10 AM, Jari Arkko &lt;&lt;mailto:<a href=3D"mail=
to:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@piuha.net</a>&gt;<a h=
ref=3D"mailto:jari.arkko@piuha.net" target=3D"_blank"><u></u>jari.arkko@piu=
ha.net</a>&gt; wrote:<br>

James:<br>
<br>
&gt; did you know that you have a audio/video realtime interactive communic=
ations WG churning out proposals and solutions that is *actively* ignoring =
&quot;emergency communications&quot; in its entirety? No? Look at RTCweb, w=
hich will become a dominant form of interactive communications between huma=
ns in the near future. You have an equally active WG in the same area that =
is addressing emergency communications (ECRIT) that is further along/mature=
 in its documents (i.e., they&#39;ve already produced the bulk of their RFC=
s, specifically RFC 6443 and 6881).<br>

&gt;<br>
&gt; Given that young people already think contacting a local emergency cal=
l center (PSAP) can or should be achievable through SMS, IM, twitter and Fa=
cebook... just how long does anyone think it will be before calling 911/112=
/999 will be requested or mandated through WEBrtc/RTCweb?<br>

&gt;<br>
&gt; Waiting will only make it more painful to retrofit it into the future =
RFCs produced by RTCweb.<br>
<br>
I knew that WebRTC is happening fast, including implementations coming out =
before standards. I don&#39;t think everyone have yet realised the full imp=
act this technology will have.<br>
<br>
I didn&#39;t know about the details of the emergency communications situati=
on. But it is always difficult to balance getting something out early vs. c=
omplete. I know how much pressure there is on the working groups to keep up=
 with things actually happening in the browsers and organisations setting u=
p to use this technology. Do you think the retrofit will be problematic, an=
d do you have a specific suggestion about what should be included today?<br=
>

<br>
Jari<br>
<br>
<br>
I&#39;m replying here, rather than down thread, because I believe it&#39;s =
important to tackle two different statements here: =A0one James&#39; and on=
e Jari&#39;s.<br>
<br>
The first is James&#39; that RTCWEB is ignoring Emergency Services. =A0Perh=
aps by &quot;actively ignoring&quot; James means that the working group con=
sidered emergency services and made a decision he did not agree with, which=
 is that the baseline capabilities already allows a PSAP or other emergency=
 service to provide a WebRTC application that would work to connect you to =
its emergency responders, and that this was enough.<br>

<br>
As context, it&#39;s very important to recognize that the WebRTC efforts in=
 the IETF and W3C *are not building a telephone into a browser*. =A0We coul=
d have done that in a few weeks. =A0 The groups *are* creating building blo=
cks that allow a javascript application within a browser or mobile context =
to add peer-to-peer audio, video, or data channels to whatever *its* applic=
ation happens to be. =A0That application can be a game (we often use a poke=
r game as an example here), a puzzle (there&#39;s an example where you comp=
ete with a peer in unscrambling a tiled video feed), or a pure data exchang=
e (where neither audio or video are passed).<br>

<br>
In that context, the group considered two questions:<br>
<br>
can you use the WebRTC building blocks to create an application to talk to =
emergency responders?<br>
<br>
should every application be required to have the ability to talk to emergen=
cy responders?<br>
<br>
It gave the answer to the first one as &quot;yes&quot;, and I am convinced =
that any emergency responder that wished to create such an application coul=
d do so with the existing building blocks. =A0A set of emergency responders=
 could even create and distribute one that was highly generalized and took =
advantage of =A0LoST&#39;s facilities to be useful in many locations.<br>

<br>
To the second question, the working group answered &quot;no&quot;. =A0There=
 are applications of WebRTC which are not general-purpose communications, i=
ncluding some applications where there will be no audio or video at all. =
=A0Requiring that a puzzle should provide you 911 service because it happen=
s to provide have live video is not really sensible. =A0Fundamentally, maki=
ng every application also be a generalized telephony application with ECRIT=
 support makes no more sense here than it would for desktop applications; y=
ou could equally require a text processor connected to the network to suppo=
rt texting emergency responders--after all, it has the UI facilities and th=
e user&#39;s attention, right?<br>

<br>
The second statement is Jari&#39;s, which seems to imply that the implement=
ations coming out before standards is a problem in the WebRTC case. =A0The =
implementers in this case are also very active contributors to both the IET=
F and W3C efforts, and they are feeding implementation experience into the =
process. =A0That&#39;s a good thing, since it is coming along with a willin=
gness to change implementations to match group consensus. =A0That won&#39;t=
 last forever, obviously, but we have that now and should continue to take =
advantage of it while we do.<br>

<br>
That&#39;s my personal take, in any case, as someone who has been actively =
involved in both efforts.<br>
</blockquote>
<br></div></div>
Ted - this view (I believe) doesn&#39;t reconcile with the view stated by H=
enning&#39;s yesterday.<br>
<br>
(truth be told, it&#39;s hard to separate Henning&#39;s stated views from h=
is official title and his official organization, given that he writes the t=
ypes of regulations the IETF community merely reads (about)...<div class=3D=
"im">
<br>
<br>
&quot;The most difficult part for any emergency calling system is location =
delivery. WebRTC probably doesn&#39;t have much impact on emergency calls i=
f all the calls traverse a server of some kind and if the caller location c=
an be looked up based on caller IP addresses, but once you have the end sys=
tem involved in location determination (e.g., for mobile devices or for DHC=
P-delivered location), it has to know when a call is an emergency call as y=
ou otherwise end up providing location for every call, which is non-ideal f=
rom a privacy and battery perspective.<br>

<br>
At least in the US, many of the WebRTC services would be considered &quot;i=
nterconnected VoIP&quot;, so they are indeed subject to 911 obligations.&qu=
ot;<br>
<br></div>
James<br>
<br>
BTW- yeah, I know I&#39;m picking a fight - but Jari singled this topic out=
 as an example of how various regions of the world differ on how they handl=
e certain applications, emergency services being one of a very short list h=
e mentioned.<br>

<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
regards,<br>
<br>
Ted Hardie<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div>

--089e0122acb402443804ddcb630d--

From scott.brim@gmail.com  Tue May 28 11:32:52 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFCB711E80EC for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQ09NeWjHF4R for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:32:52 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 48E2011E80EA for <ietf@ietf.org>; Tue, 28 May 2013 11:32:51 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id ef5so9458230obb.16 for <ietf@ietf.org>; Tue, 28 May 2013 11:32:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5TP1El5SbSui0MVBOCUnXpbZlFkvnoZsYnp3blxMOms=; b=AvU1aby6zqG6pZv6/tYk96FPoFhdZas8+kOOQ0VF/ypYe1CLku/EmmpH0gsHbP/DOt GPMAqAipqbQ8VKSF2L/lCL5W+7xWI5tbCIL86H2SLCWV8+igH4b2Y6K79gZ3+3bU1XSY iXAuZfCQnjWPGQ3FPClni5/XsBYYSir9xql6gH8wAqDjdA0b3OM5mp5qJA7FW+ddIfF3 dojfoHB85089bgb9SrBSyUvEKrVzJA5dYQ2fuZA0tVYYBck1mWGxDzfvS+ZEYQG7ro7N UohAmECUlXgJkiCJAQDOV8+5jy3hMdQskAwtUA68Hxa+IbveJRt2I55he+t5ldmsLO6+ uhDQ==
X-Received: by 10.182.204.105 with SMTP id kx9mr21176859obc.81.1369765971617;  Tue, 28 May 2013 11:32:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.114.193 with HTTP; Tue, 28 May 2013 11:32:31 -0700 (PDT)
In-Reply-To: <CAOBNHyeQ9uVn8E=heSf_+JQbp=Zd9K49wpct7gDB0bK5rV8bww@mail.gmail.com>
References: <CAOBNHyeQ9uVn8E=heSf_+JQbp=Zd9K49wpct7gDB0bK5rV8bww@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 28 May 2013 14:32:31 -0400
Message-ID: <CAPv4CP937=b_Fq6LgZfYix_d--+b+JrXgvs=SesEJCOCHzxXqA@mail.gmail.com>
Subject: Re: [Isoc-br] IETF Meeting in South America
To: Rogerio Mariano <rsouza.rjo@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8ff1cf2629ef3b04ddcb7e33
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, 28 May 2013 18:32:52 -0000

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

Dear Rog=E9rio Mariano,

You have a great deal of experience.  Since the mission of the IETF is to
make the Internet better, could you point out specific problems that you
would like to work on in the IETF?  When you say "infrastructure and
standardization", that is very general.  If there were an IETF meeting in
your city, why would you come to the meeting?  Can you give a specific
example of a problem that would you like to work on?

Thank you.

Scott Brim

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

Dear Rog=E9rio Mariano,<div><br></div><div>You have a great deal of experie=
nce. =A0Since the mission of the IETF is to make the Internet better, could=
 you point out specific problems that you would like to work on in the IETF=
? =A0When you say &quot;infrastructure and standardization&quot;, that is v=
ery general. =A0If there were an IETF meeting in your city, why would you c=
ome to the meeting? =A0Can you give a specific example of a problem that wo=
uld you like to work on? =A0</div>

<div><br></div><div>Thank you.</div><div><br></div><div>Scott Brim</div>

--e89a8ff1cf2629ef3b04ddcb7e33--

From paul.hoffman@vpnc.org  Tue May 28 11:34:17 2013
Return-Path: <paul.hoffman@vpnc.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 7822611E80F4 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCIsKTtC5D2h for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:34:17 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9A80211E80A2 for <ietf@ietf.org>; Tue, 28 May 2013 11:34:15 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4SIYEg4027415 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 28 May 2013 11:34:15 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAL02cgTyCv80qH4cu=-O686VsuDuK46aedmKxJ9GxEBTres++w@mail.gmail.com>
Date: Tue, 28 May 2013 11:34:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDDF44F8-EF15-4FAC-B806-234DDCB9101D@vpnc.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <CA+9kkMBLGQFBk+nqBQQMeWw4OoJ26pvfB99HECN=oKkAc+Qzsw@mail.gmail.com> <201305281820.r4SIKXMS029096@rcdn-core-2.cisco.com> <CAL02cgTyCv80qH4cu=-O686VsuDuK46aedmKxJ9GxEBTres++w@mail.gmail.com>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:34:17 -0000

On May 28, 2013, at 11:25 AM, Richard Barnes <rlb@ipv.sx> wrote:

> I would suggest we not try to sort out on this list which sorts of =
Internet services are subject to American regulations.

Or those of any other jurisdiction. If jurisdiction Z comes to the IETF =
and says "we have declared protocol A to be a service of type B", and we =
can think of harmless ways of making B more obvious in an extended =
version of A, that seems like potential work, possibly even for a WG but =
certainly for individual submission. But it should be done after A is =
done (assuming that A is extensible) and after Z has looked at A.

--Paul Hoffman=

From christian.oflaherty@gmail.com  Tue May 28 11:38:53 2013
Return-Path: <christian.oflaherty@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26DB421F949A for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mi3ISx6Prlwm for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:38:52 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 654B221F9497 for <ietf@ietf.org>; Tue, 28 May 2013 11:38:52 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id 9so22387720iec.36 for <ietf@ietf.org>; Tue, 28 May 2013 11:38:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rDRcJ9lbbdChQnL47Eef1m5PknHZWkPR3Vp4OD2Wg08=; b=nmiVMCnOWbng9WD3nWrXauz5kYgfpTatxGorVoOsZdxV9rFWOTtsJXAQcfLMSRijTr Kr5niJOsnQ06Y4ovxmDXIUIZGYJcOZW/ahOay4iDn68zjOkSt229OKfdJBl6VCmIrXFU qMChKM8Y1KUCz39WvS/KgtuiP8DYBQth5xvbTmFpIIxKJUwv3Jgmq3/B+D3inWSoP+EL 8pzMwbOIDUTXtaHzWhR77dFrBl3ADtzfLX9morDxmdRaYF2jySXwaMCNB0d7HoO8NPrZ EUnBMVI1R/hyjynVP6uLxm+ejFb8xAfIGd9W9j4Jy/3CKj8Egnc5UV6BUrFf7/dK/7gb XDJg==
MIME-Version: 1.0
X-Received: by 10.42.27.208 with SMTP id k16mr19659179icc.43.1369766332008; Tue, 28 May 2013 11:38:52 -0700 (PDT)
Received: by 10.64.136.18 with HTTP; Tue, 28 May 2013 11:38:51 -0700 (PDT)
In-Reply-To: <51A4E625.3020406@gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com>
Date: Tue, 28 May 2013 15:38:51 -0300
Message-ID: <CAKfZcEtD6nFKNtc1xGPHKKydctWmcCGsZgDKhxoLRTCCg7gR1Q@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:38:53 -0000

On Tue, May 28, 2013 at 2:15 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> On 5/28/13 6:20 AM, Christian O'Flaherty wrote:
>> Probably, this lack of social interaction in our region is one of
>> the main reasons for low participation. Most of latin american
>> IETFers are currently living outside the region and they engaged in
>> the IETF when living in the US or Europe. It's difficult to be
>> involved when no one else around is working in it or think it doesn't
>> fit well in their current work. A physical meeting will help to
>> "demystify" the IETF, making it "accesible" from a professional
>> perspective.
>
> Any sense of why that didn't happen with Australians after
> the Adelaide meeting?

If we're able to get a "proportional growth" similar to what happened
in Australia it will be a success :-)
Latam is a region with 600 million inhabitants compared to 23 million
in Australia.

But I agree with you and I'm not saying a meeting is going to be
enough. In the past it was probably not combined with other activities
planned two or three years in advance. We can do something serious
here and we know the potential available in the region to empower the
IETF even more.

Christian

>
> I'm not opposed to meeting in South America but there have
> been an awful lot of assertions about this or that happening
> if we do, without a lot of supporting evidence.  History,
> unfortunately, doesn't support many of these assertions, and
> I think beating the meeting location question to death is
> at least some small distraction from trying to get at the core
> issues.
>
> For whatever it's worth, I was participating on IETF mailing lists
> well before attending a meeting.  Granted, I'm a native English
> speaker and wasn't dealing with that as an issue but probably
> more to the point was that there was work going on in the IETF
> that directly impacted work I was doing myself.
>
> Melinda

From christian.oflaherty@gmail.com  Tue May 28 11:56:36 2013
Return-Path: <christian.oflaherty@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11B4F21F962A for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z-eEpLcSIvXx for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:56:35 -0700 (PDT)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 56E5921F94B1 for <ietf@ietf.org>; Tue, 28 May 2013 11:56:32 -0700 (PDT)
Received: by mail-ie0-f178.google.com with SMTP id f4so6513920iea.9 for <ietf@ietf.org>; Tue, 28 May 2013 11:56:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H6Fa3YMeIDBkPLWWr0Zh4zvXKchGvIne6DV8oG/9oDE=; b=ANeai2ogdGMQVhx1ZIKMK8sUYK3dH7+DN1BkXRz6QU1KC/Z4nvESWMKy7DI94uPD7j u69Dxx7EIsPZNkf/9xm7IMWsUIWDLX4IGlBC5TdgZ470UqqqX1vnHyU/GBw237fHt3oW q+j9TO+P6xm5o/h/Z45wqnBy/9DPrHGY7h994P04oAAY9nPQB7K1r5mvFyyvXE5CEuwX zS1Tx8+xGwd+vNclgFvyei4aqkj32Ygd/0jONpE9bY95pFqLp2uXnEENT72Nxy+Sv1IY NIj7qJB+n1lRQ/wNtGp9rEh8wL9h+3Voe6B7hJorbzfwGy0Lynv16j/VezfhoCUlSO0y 2PpQ==
MIME-Version: 1.0
X-Received: by 10.50.50.195 with SMTP id e3mr7643736igo.109.1369767391315; Tue, 28 May 2013 11:56:31 -0700 (PDT)
Received: by 10.64.136.18 with HTTP; Tue, 28 May 2013 11:56:30 -0700 (PDT)
In-Reply-To: <51A4E640.9050707@bogus.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com> <CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com> <CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com> <519E7E83.9000809@gmail.com> <CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com> <519E94AC.3060500@gmail.com> <8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com> <193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net> <519EC3BA.9010908@braga.eti.br> <519EC664.5050806@gmail.com> <519ED27D.9050709@braga.eti.br> <519ED3F0.40300@gmail.com> <F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org> <51A4E640.9050707@bogus.com>
Date: Tue, 28 May 2013 15:56:30 -0300
Message-ID: <CAKfZcEvszxAeBycOdQ5DbYYpTRcvhO_6nND4CJRYLwaMx5eCZg@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:56:36 -0000

> It would seem likely when the participation is heaviliy biased towards
> equipment vendors and software tooling that the participants would be more
> representative of where the concentration of the development sideo of that
> work occurs.

This is true, but this is also something where active participants can
help. Many of those companies also have R&D groups in Latam but
unfortunately they're not yet active in the IETF. This is probably for
historical reasons but it's feasible to change. If you know in your
companies, groups or individuals valuable enough to work in the IETF
please reach them and help them (or let me know and I'll do it).

> Comparative advantage isn't just the domain of agricultural
> products, extractive industries, and low-cost manufacturing. That seems
> likely to be part and parcel of the diversity discussion.

Latam is not just agriculture and cows :-)

From ted.ietf@gmail.com  Tue May 28 11:59:13 2013
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9083521F91C4 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54R+MHzP0Iwr for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 11:59:12 -0700 (PDT)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com [IPv6:2607:f8b0:4001:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4C18921E8094 for <ietf@ietf.org>; Tue, 28 May 2013 11:59:10 -0700 (PDT)
Received: by mail-ie0-f180.google.com with SMTP id b11so8251314iee.11 for <ietf@ietf.org>; Tue, 28 May 2013 11:59:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DXJqKOxCvkBJgGrapVgK7XaTNmW+881lkvqydE5jkLw=; b=zaCLiBoVo/xcYoDOKCxy9DsySKAaR2nmGpjiTSp3nFhXMe8c7SNnR3OYxH9Kbuakkk ftuaUEtbJbmC5QIzKtBeT6RflVmvQpzlbhdNVSHbMaoEew0HO+WVqu1UdlNdAnnej3xk vHesTT9uSl0caH7DP1oISg9tS7A2YZwowJhiZRe8Grzf8PY/tzNMg8Ao76WXSztIKcVq E55RVBiwKVxsx1BNcRBdIRayccbF88pzaF7IXDhyThVBH1appNn9iiWpQEYLDq8uxIuq MWcGRluDIQqWJuKhuJM5jXgezEpxo7mpzaV8B4iu/idWHgE9ZYmX4hlzsZ0UZ+jBjAXV oX8A==
MIME-Version: 1.0
X-Received: by 10.50.17.166 with SMTP id p6mr7694731igd.12.1369767548827; Tue, 28 May 2013 11:59:08 -0700 (PDT)
Received: by 10.42.177.2 with HTTP; Tue, 28 May 2013 11:59:08 -0700 (PDT)
In-Reply-To: <201305281820.r4SIKXMS029096@rcdn-core-2.cisco.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <B44FB2FE-AA90-4108-B9F1-7E5D5A773C0A@piuha.net> <201305241821.r4OIL33S031511@rcdn-core2-6.cisco.com> <2B32AA85-3D44-40C5-9FF3-C406B54590ED@piuha.net> <CA+9kkMBLGQFBk+nqBQQMeWw4OoJ26pvfB99HECN=oKkAc+Qzsw@mail.gmail.com> <201305281820.r4SIKXMS029096@rcdn-core-2.cisco.com>
Date: Tue, 28 May 2013 11:59:08 -0700
Message-ID: <CA+9kkMDf1x2EQ5tEWK3BT8jFZ16kmjQMoN=+3gjeN6rXXyYtvw@mail.gmail.com>
Subject: Re: WebRTC and emergency communications (Was: Re: IETF Meeting in South America)
From: Ted Hardie <ted.ietf@gmail.com>
To: James Polk <jmpolk@cisco.com>
Content-Type: multipart/alternative; boundary=14dae9340cc92c93c504ddcbdc62
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 18:59:13 -0000

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

On Tue, May 28, 2013 at 11:20 AM, James Polk <jmpolk@cisco.com> wrote:

> Quoting Henning:
> "At least in the US, many of the WebRTC services would be considered
> "interconnected VoIP", so they are indeed subject to 911 obligations."
>
> James
>
> BTW- yeah, I know I'm picking a fight - but Jari singled this topic out as
> an example of how various regions of the world differ on how they handle
> certain applications, emergency services being one of a very short list he
> mentioned.
>

I will agree with Richard that we shouldn't focus discussion on this list
on the regulatory environment.  But I think there's a piece of this that
goes to the heart of what WebRTC can be, and that is whether the point is
to create a new infrastructure that becomes part of "interconnected VoIP"
or to create a set of building blocks that allows real-time communications
without that infrastructure.

I personally believe that is the latter, rather than the former, that is
the promise of WebRTC.  If I can make peer-to-peer, real time
communications a part of any javascript application downloaded into a
browser, I can create imbue those applications with a far richer
environment.  They can be social in ways that they are not now; they can be
interactive in ways which they are not now; they can be creative in ways
that they are not now (at least not without limiting the experience to
those with specific plugins).

Can you use that interactivity to create a telephone, which you then hook
up to SIP islands or the PSTN via gateways?  Sure, if that's what you want
to do.

But I don't think that's the major goal, and I have argued against a focus
on that interoperability as a major driver of work in WebRTC.  It looks
shiny, as a way to get early users and quick deployment.  But there's a lot
of hooks attached to that lure, and I'd personally advise anyone developing
for WebRTC to focus on native WebRTC apps.  Those will be the ones that wow
users and drive us forward.

Again, just my personal view,

Ted Hardie

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

On Tue, May 28, 2013 at 11:20 AM, James Polk <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jmpolk@cisco.com" target=3D"_blank">jmpolk@cisco.com</a>&gt;</sp=
an> wrote:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Quoting Henning:<br><div class=3D"im">
&quot;At least in the US, many of the WebRTC services would be considered &=
quot;interconnected VoIP&quot;, so they are indeed subject to 911 obligatio=
ns.&quot;<br>
<br></div>
James<br>
<br>
BTW- yeah, I know I&#39;m picking a fight - but Jari singled this topic out=
 as an example of how various regions of the world differ on how they handl=
e certain applications, emergency services being one of a very short list h=
e mentioned.<br>
</blockquote><div><br>I will agree with Richard that we shouldn&#39;t focus=
 discussion on this list on the regulatory environment.=A0 But I think ther=
e&#39;s a piece of this that goes to the heart of what WebRTC can be, and t=
hat is whether the point is to create a new infrastructure that becomes par=
t of &quot;interconnected VoIP&quot; or to create a set of building blocks =
that allows real-time communications without that infrastructure.=A0 <br>
<br>I personally believe that is the latter, rather than the former, that i=
s the promise of WebRTC.=A0 If I can make peer-to-peer, real time communica=
tions a part of any javascript application downloaded into a browser, I can=
 create imbue those applications with a far richer environment.=A0 They can=
 be social in ways that they are not now; they can be interactive in ways w=
hich they are not now; they can be creative in ways that they are not now (=
at least not without limiting the experience to those with specific plugins=
).=A0 <br>
<br>Can you use that interactivity to create a telephone, which you then ho=
ok up to SIP islands or the PSTN via gateways?=A0 Sure, if that&#39;s what =
you want to do. <br><br>But I don&#39;t think that&#39;s the major goal, an=
d I have argued against a focus on that interoperability as a major driver =
of work in WebRTC.=A0 It looks shiny, as a way to get early users and quick=
 deployment.=A0 But there&#39;s a lot of hooks attached to that lure, and I=
&#39;d personally advise anyone developing for WebRTC to focus on native We=
bRTC apps.=A0 Those will be the ones that wow users and drive us forward.=
=A0 <br>
<br>Again, just my personal view,<br><br>Ted Hardie<br><br></div></div>

--14dae9340cc92c93c504ddcbdc62--

From brian.e.carpenter@gmail.com  Tue May 28 13:26:21 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8677321F8FAF for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 13:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=1.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ysV77qO14sbg for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 13:26:16 -0700 (PDT)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id A6D5C21F8EF7 for <ietf@ietf.org>; Tue, 28 May 2013 13:26:16 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx1so8408357pab.13 for <ietf@ietf.org>; Tue, 28 May 2013 13:26:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=auhiKDpL0bcMQ9t42kdCqWTq9TpvfDzEki/MQPAird4=; b=tp2eM2cCuTuIv+ATIGR8zPTFhsWGJjde4rOg5muqEsLxw+aw3E+vuFjlVFEMmjmES9 tdyRLOBl0jncBNw7qW0M5jlckQltYktxopoKEQoja99ee3dynsUYMWnq30KnaAfuzCb7 2Qy8Q9vbij86rEPi5L6Klbj94DkF+LRZNqJholxBcAiaeGhzdhxv+Ta4PNFW6W4/TBW4 z9R10yCB9NWotce7UMT2wdAx0L+0gvamdgQj45fAM0t9QSaJVxJ2XFqO1JVBK/np6/wI Qr4o1n21YjkaAaW0jASKddLONFsu+6jz2ZmGRwMjx7f37y+sAXlnwNDJ4xcgjOkf/i9i b3aA==
X-Received: by 10.66.248.40 with SMTP id yj8mr122516pac.95.1369772776358; Tue, 28 May 2013 13:26:16 -0700 (PDT)
Received: from [192.168.1.2] (253.150.252.27.dyn.cust.vf.net.nz. [27.252.150.253]) by mx.google.com with ESMTPSA id fr1sm34135588pbb.26.2013.05.28.13.26.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 13:26:15 -0700 (PDT)
Message-ID: <51A512E8.6000801@gmail.com>
Date: Wed, 29 May 2013 08:26:16 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
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, 28 May 2013 20:26:21 -0000

On 28/05/2013 21:32, Adrian Farrel wrote:
> Hi,
> 
> Dave Crocker and I have this little draft [1] discussing the process and considerations for creating formal working group drafts that are targeted for publication.
> 
> We believe that this may help clarify some of the issues and concerns associated with this part of the process. We are targeting this as Informational (i.e. commentary on existing process, not new normative definition of process) and would like your input.
> 
> What is not clear?
> What have we got wrong?

I haven't read the draft yet, and *before* I do so, I'd like to express
some doubt whether we should even informally describe this using the
word "process". It seems to me that it's each WG's prerogative how it
does this; it has no impact on the standards process as a whole. The
word "adopt" doesn't even occur in RFC 2418, and it is not used in
the context of WG adoption in RFC 2026.

In other words, I don't think this action is part of the standards process.
It's WG folklore.

   Brian

> How should we resolve the remaining editor notes?
> 
> Thanks,
> Adrian
> (per pro Dave)
> 
> [1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
> 
> 
> .
> 

From fgont@si6networks.com  Tue May 28 14:19:33 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CAD821F881C for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 14:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R9IlUp1y76Tr for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 14:19:32 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id DF65721F92FB for <ietf@ietf.org>; Tue, 28 May 2013 14:19:31 -0700 (PDT)
Received: from [2001:5c0:1400:a::431] by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UhRIn-0004BU-2m; Tue, 28 May 2013 23:19:29 +0200
Message-ID: <51A5004E.60706@si6networks.com>
Date: Tue, 28 May 2013 21:06:54 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Juliao Braga <juliao@braga.eti.br>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br>
In-Reply-To: <51A4F57C.8000902@braga.eti.br>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=ISO-8859-1
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: Tue, 28 May 2013 21:19:33 -0000

Julio,

On 05/28/2013 08:20 PM, Juliao Braga wrote:
> 
> If I have to decide about a meeting in Buenos Aires based in the
> information that I read in the Brazilian newspapers and magazines I
> decide to no. 

Could you please provide pointers to such articles? Additionally, could
you please summarize what are your concerns, or what are the concerns
expressed in the articles you've read?



> By this reason I need to listen from Argentine people, as
> you. I believe this is the right way to decide.

The problem is that when comments are thrown out to a mailing-list
without checking what's the information that is being spread, that ends
up polluting and biasing the discussion unfairly and inappropriately.

As a datapoint, Buenos Aires is *full* of brazillians these days -- I
guess both because we're geographically near, but also because the
exchange rate benefits brazillians (I haven't checked lately, but I'd
bet that you can get most stuff for about 50% or 70% of the price of
what you pay in Brazil).

And I know of quite a few brazillians myself that have recently traveled
to Argentina to attend meetings, and others that are planning to do so
to attend meetings or conferences (Internet and/or security related)
held in Buenos Aires.

As noted in some other emails, I'm not even weighing in regarding the
pro's and con's of having a meeting in Argentina, but rather pointing
out that making public statements regarding based on what has been
"heard", "rumors", or what some idiot posted on a blog pollutes and
biases the discussion unfairly and inappropriately.

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From arturo.servin@gmail.com  Tue May 28 14:31:56 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 986F911E80E0 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 14:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rc7G01jUDkgh for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 14:31:56 -0700 (PDT)
Received: from mail-vb0-x22c.google.com (mail-vb0-x22c.google.com [IPv6:2607:f8b0:400c:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id EF42C11E80A5 for <ietf@ietf.org>; Tue, 28 May 2013 14:31:55 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id i3so3958235vbh.31 for <ietf@ietf.org>; Tue, 28 May 2013 14:31:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+h8SYfHngL9kvcg+IQTevUcj4iQkKkNFD+XJQxmbn5c=; b=SDenshJ0uF58gXp+kmeY16sWmIIRkYuZ2RrJIP66JP30V2xCB/0Wd2gw4VJDKUwZN1 19OCYC5lL+kye7sFmJAGyAwKxV0cetM5aj6Qbkg3pj1zvrCQRfLGa9cMqaPYnUBE+0nj HNvbg3igYeO8vSLYGgXe8whGPUrBwwPAbBECIKVAYSlLhxn8zrVKT0RrRTS/DNWHBIvY eC2i/1kOGUEKVn+L0a5dAHcgzCUtJ/OW0AviCxiPxAGnIoBTT8F6ob6b05GaRg3pRxfg wwWA1mPrnZldRQl5UOosYcH4F7vD7kI/IijdA6o0XNGhbnumSR5ZVp031+IE3ohWSu2S +24A==
X-Received: by 10.52.76.103 with SMTP id j7mr16504080vdw.90.1369776715021; Tue, 28 May 2013 14:31:55 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba31:739:501a:b0ca:146e:a8f3]) by mx.google.com with ESMTPSA id wl4sm25809522vdb.3.2013.05.28.14.31.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 14:31:54 -0700 (PDT)
Message-ID: <51A52246.6090000@gmail.com>
Date: Tue, 28 May 2013 18:31:50 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
In-Reply-To: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk>
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, 28 May 2013 21:31:56 -0000

Hi,

	I have never been a wg chair but I think that this document may be very
useful and helpful (at least it clarifies many things to me).

	I have some comments:

- To me Section 2.1 (Formal Steps) looks better after 2.2 (Criteria of
Adoption).

- Section 2.2 does not set up a criteria. It just ask questions, it
would be good to set basic criteria at least.

- Section 2.2, The paragraph under "REMINDER" it is very important but I
am not convinced 100% how you raised the attention to it (by using
"reminder") But I think that it is very important to point out this.

- Section 3. Also not convinced about the "NOTE", it would be better to
me to include it as part of the text (similar to my comment of
"reminder" of section 2.2.

- There are some questions in different parts of the document, for
example "Shall it be adopted and entirely replace the current working
group draft?  Shall the new ideas be incorporated into the work of the
working group through the normal editorial process? ..." I am not sure
the purpose of those, I imagine that they are helpful questions to ask,
if so I suggest to add something like this to clarify "Important
questions that WG chairs should ask or consider are 'Shall it be adopted
and entirely replace the current working group draft?'..."

Best regards,
as


On 5/28/13 6:32 AM, Adrian Farrel wrote:
> Hi,
> 
> Dave Crocker and I have this little draft [1] discussing the process and considerations for creating formal working group drafts that are targeted for publication.
> 
> We believe that this may help clarify some of the issues and concerns associated with this part of the process. We are targeting this as Informational (i.e. commentary on existing process, not new normative definition of process) and would like your input.
> 
> What is not clear?
> What have we got wrong?
> How should we resolve the remaining editor notes?
> 
> Thanks,
> Adrian
> (per pro Dave)
> 
> [1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
> 

From juliao@braga.eti.br  Tue May 28 15:13:40 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75B8121F9052 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 15:13:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYYZdr7gKAvE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 15:13:39 -0700 (PDT)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBED21F901F for <ietf@ietf.org>; Tue, 28 May 2013 15:13:39 -0700 (PDT)
Received: by mail-yh0-f54.google.com with SMTP id b12so1179649yha.27 for <ietf@ietf.org>; Tue, 28 May 2013 15:13:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=15Ffyepr4E2Fs6E+N2Pi36psB0qrXkHz6PsaLUJ3EOE=; b=gGkmHdT/6uUaaDOb+gJ7txJNBotiW8bYfffXj74ZbuLwZsACYSb0U/jV1AI32bOK+n gzhOxvnWN8/lK2//KmlmVJs3E6RldeFyvlxaqGobLC3MZLyBuXmQpDHheVt9xiyEzl1a GeCpKQIBu3I4OphyUL2YMj8SBIQps2jtcyWxWzNi4UgVOY0wBPgIdKc6IP4W89L/HmaD QjIM8WQwO1djk/qWj3B+wnow+CdwX0+Kh6ECKcefnu5Ai/n3V+9b85XCowX1Z9Y2V4Zv ybK0nSv7Qx2wibJ1JO07SRO0JUWIRuTZ1qbH3xkWrDlc4pp4BI5Dt0OUFMtqFEqU1WZw yc0Q==
X-Received: by 10.236.137.204 with SMTP id y52mr9663015yhi.103.1369779218789;  Tue, 28 May 2013 15:13:38 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id z65sm48891034yhc.9.2013.05.28.15.13.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 15:13:37 -0700 (PDT)
Message-ID: <51A52C0A.7000805@braga.eti.br>
Date: Tue, 28 May 2013 19:13:30 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br> <51A5004E.60706@si6networks.com>
In-Reply-To: <51A5004E.60706@si6networks.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnBRh1aF660RFSDQrSHjfkiobmHa58Rj0OpSdOzvPXBx/vyVHxrx5wGn656IKfaKYhKZE+u
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 22:13:40 -0000

Fernando,

Please, read the Brazilian newspapers and magazines.

I'm not looking for news from Argentina. I see them and / or read just
the same way that I see or read others news, always "an passant".

This type of issue is not exactly my specialty or interest. But you can
see a handful of recents news in the following locations, among others:

http://www.veja.com.br
http://revistaepoca.globo.com/
http://www.globo.com
http://uol.com.br
http://www.estadao.com.br

or you can use Google, searching for Brazil or other contries news about
Argentina.

As I said to you, but it seems you do not understand, this is not a
relevant question. For me and for many others the relevant question is
your opinion.

Carlos Martinez was precise and clear in your last post. Let us return
to the subject that interests us, please.

Although I do not have much time for this kind of debate, if you feel
comfortable, send me email in private.

Juliao

Em 28/05/2013 16:06, Fernando Gont escreveu:
> Could you please provide pointers to such articles? Additionally, could
> you please summarize what are your concerns, or what are the concerns
> expressed in the articles you've read?

From l.wood@surrey.ac.uk  Tue May 28 16:06:26 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00AE821F8B04 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sA+-WMD1Nwv3 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:06:21 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.165]) by ietfa.amsl.com (Postfix) with ESMTP id 8926021F85C0 for <ietf@ietf.org>; Tue, 28 May 2013 16:06:19 -0700 (PDT)
Received: from [195.245.230.131:34372] by server-5.bemta-3.messagelabs.com id 59/77-29713-A6835A15; Tue, 28 May 2013 23:06:18 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-78.messagelabs.com!1369782377!30221387!2
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 12452 invoked from network); 28 May 2013 23:06:18 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-12.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 28 May 2013 23:06:18 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Wed, 29 May 2013 00:06:17 +0100
From: <l.wood@surrey.ac.uk>
To: <melinda.shore@gmail.com>, <ietf@ietf.org>
Date: Wed, 29 May 2013 00:06:16 +0100
Subject: RE: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: Ac5bxwcC8EeJauj3QFOQ3xeWRcx4UgAL/Oco
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com>
In-Reply-To: <51A4E625.3020406@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:06:26 -0000

> Any sense of why that didn't happen with Australians after
> the Adelaide meeting?

The centres for networking industry in Australia are Melbourne and Sydney, =
in that order.

It's a bit like IETF 51 being held in Grimsby, not London or Cambridge.

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

From arturo.servin@gmail.com  Tue May 28 16:09:51 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D12811E80A4 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:09:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6vIxpXf5klas for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:09:49 -0700 (PDT)
Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BB93311E80A5 for <ietf@ietf.org>; Tue, 28 May 2013 16:09:44 -0700 (PDT)
Received: by mail-ve0-f170.google.com with SMTP id 15so6417882vea.1 for <ietf@ietf.org>; Tue, 28 May 2013 16:09:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=tHogo6+Oeg3IAQo314FJFdOJ2428SmDbbtPOu40BcxE=; b=GoymnPfolc8ZKutxyr6PiIWcZ3xPZbaTDcq1kzU/Gkqi/y3Qbn31SGU9b6KlYsSe// kNX+5k9srFM+fAahSI4NPZ7S18pbxZY/vaANfaosQe5Ep/JW/3XS4ZcY+T+muUqOqc7D S4Ia6tcDy6qbDL7Ghxw1MjatbQ+BzFPlapPqBCErByf/BSNn+tmkYe2eoNWqhVqmze8V MRF/+NciKHddOIiLJ7ZB0z5MEXTXhrws3cef2glMbmduSvGYhv3oPTaLvNhJ/J0S8ndC usQZTgj1s6WiU3knsO3cxEqaFLRK+kJFAyl1mA/wvGzFpBc/26XMCYeGyNEiSlELIBM6 zjkg==
X-Received: by 10.220.3.144 with SMTP id 16mr70628vcn.6.1369782582826; Tue, 28 May 2013 16:09:42 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (r186-49-7-57.dialup.adsl.anteldata.net.uy. [186.49.7.57]) by mx.google.com with ESMTPSA id ho10sm26174033vdb.7.2013.05.28.16.09.40 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 16:09:41 -0700 (PDT)
Message-ID: <51A53930.4030201@gmail.com>
Date: Tue, 28 May 2013 20:09:36 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br> <51A5004E.60706@si6networks.com> <51A52C0A.7000805@braga.eti.br>
In-Reply-To: <51A52C0A.7000805@braga.eti.br>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:09:51 -0000

Juliao,

	I went to all this sites (besides BBC Brazil) and searched for
Argentina. There were some news about economy, the lady President, some
about the senate, commercial balance but none saying "huu, scary
Argentina, do not go there".


Regards,
as

On 5/28/13 7:13 PM, Juliao Braga wrote:
> Fernando,
> 
> Please, read the Brazilian newspapers and magazines.
> 
> I'm not looking for news from Argentina. I see them and / or read just
> the same way that I see or read others news, always "an passant".
> 
> This type of issue is not exactly my specialty or interest. But you can
> see a handful of recents news in the following locations, among others:
> 
> http://www.veja.com.br
> http://revistaepoca.globo.com/
> http://www.globo.com
> http://uol.com.br
> http://www.estadao.com.br
> 
> or you can use Google, searching for Brazil or other contries news about
> Argentina.
> 
> As I said to you, but it seems you do not understand, this is not a
> relevant question. For me and for many others the relevant question is
> your opinion.
> 
> Carlos Martinez was precise and clear in your last post. Let us return
> to the subject that interests us, please.
> 
> Although I do not have much time for this kind of debate, if you feel
> comfortable, send me email in private.
> 
> Juliao
> 
> Em 28/05/2013 16:06, Fernando Gont escreveu:
>> Could you please provide pointers to such articles? Additionally, could
>> you please summarize what are your concerns, or what are the concerns
>> expressed in the articles you've read?

From joelja@bogus.com  Tue May 28 16:15:29 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC31A21E8054 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vOc68uaRfgtD for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:15:29 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 71C2421E8053 for <ietf@ietf.org>; Tue, 28 May 2013 16:15:29 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4SNFQpJ010332 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 28 May 2013 23:15:26 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A53A89.4020100@bogus.com>
Date: Tue, 28 May 2013 16:15:21 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: "Christian O'Flaherty" <christian.oflaherty@gmail.com>
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com>	<CAA=duU3JFUaNhOX9s31VPdpAyycNX6hhFHB4dM4rH0yHmsevpw@mail.gmail.com>	<CAHiKxWh1W981TnKqeFcXwmq5awLb1HVddL=VKe0ZPLjt9PT5kg@mail.gmail.com>	<CAG4d1rckh251BY6NRxsJLfybgTJifp2i7OXYv0o0yGHjtUkFFQ@mail.gmail.com>	<519E7E83.9000809@gmail.com>	<CAF4+nEGrZmMv+=U4+p85Dq0=jcNRGD7XGCwR0G+oNJq6_AUECA@mail.gmail.com>	<519E94AC.3060500@gmail.com>	<8C48B86A895913448548E6D15DA7553B8F50B9@xmb-rcd-x09.cisco.com>	<193787A8-C237-4FDA-82B1-E0CE4B22744D@mnot.net>	<519EC3BA.9010908@braga.eti.br>	<519EC664.5050806@gmail.com>	<519ED27D.9050709@braga.eti.br>	<519ED3F0.40300@gmail.com>	<F2C0DCEA-DFA5-460D-B233-25B8366780BA@virtualized.org>	<51A4E640.9050707@bogus.com> <CAKfZcEvszxAeBycOdQ5DbYYpTRcvhO_6nND4CJRYLwaMx5eCZg@mail.gmail.com>
In-Reply-To: <CAKfZcEvszxAeBycOdQ5DbYYpTRcvhO_6nND4CJRYLwaMx5eCZg@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.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 28 May 2013 23:15:26 +0000 (UTC)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:15:30 -0000

On 5/28/13 11:56 AM, Christian O'Flaherty wrote:
>> It would seem likely when the participation is heaviliy biased towards
>> equipment vendors and software tooling that the participants would be more
>> representative of where the concentration of the development sideo of that
>> work occurs.
> This is true, but this is also something where active participants can
> help. Many of those companies also have R&D groups in Latam but
> unfortunately they're not yet active in the IETF. This is probably for
> historical reasons but it's feasible to change. If you know in your
> companies, groups or individuals valuable enough to work in the IETF
> please reach them and help them (or let me know and I'll do it).
$former_dayjob had a R&D office in manaus. We have active kernel/gtk/qt 
development going on there with real contributors. It is however an 
isolated kind of strange tax haven in the middle of the amazon  and it's 
kind of hard to get to.
>> Comparative advantage isn't just the domain of agricultural
>> products, extractive industries, and low-cost manufacturing. That seems
>> likely to be part and parcel of the diversity discussion.
> Latam is not just agriculture and cows :-)
I am within about 10 minutes driving distance of maybe 1/3 the world's 
ethernet switch asic design capacity, so to ignore the fact that 
concetration and specialization does occur is a little short sighted, it 
also changes over time when the basis for advantage no longer applies, 
or erodes).



From juliao@braga.eti.br  Tue May 28 16:30:31 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD71D21E8090 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:30:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.166
X-Spam-Level: 
X-Spam-Status: No, score=-3.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TTTS67JQtW8A for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:30:26 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9BBC121F8A68 for <ietf@ietf.org>; Tue, 28 May 2013 16:30:26 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id hf12so5934701vcb.17 for <ietf@ietf.org>; Tue, 28 May 2013 16:30:26 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=ER1JiFHAUTmh21ngbD4wVmjGPn2NPqlYKoEdQuMffsM=; b=Aqu2uAaayDD9mkfeBYgXKmEWXhjldf2YXi2I1cOizhnqKsRHeBkcciwkH+wg08GpyJ gOGPP5OnKxqdyxSp1ugnEU6KBIvol5tj1l7fjcFdTQIRI8Rg96G47Tzzc2h1njUNbvNW wrNBpgoFkiAOGMWaR3zYxgzTJoBHP47MDEK6oX18s5KaqI9ycuRYT/u6X6MTqHhYbf8q 0lXvv7osZTDih4BELE05yB/Iq+TCKvurABWbY+01xcWAlJkMsUSb1xXSZNzXpA0/oxt7 dRLDL7RNVa3QwO5rrN7tlxzCkmA1UqwDItsQYhIoP4hwvJD8/0yrZ9uj8oUzv3Np5Wnj 1bNQ==
X-Received: by 10.52.65.38 with SMTP id u6mr57362vds.59.1369783825937; Tue, 28 May 2013 16:30:25 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id mw6sm25969180vec.7.2013.05.28.16.30.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 16:30:25 -0700 (PDT)
Message-ID: <51A53E0B.7080300@braga.eti.br>
Date: Tue, 28 May 2013 20:30:19 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br> <51A5004E.60706@si6networks.com> <51A52C0A.7000805@braga.eti.br> <51A53930.4030201@gmail.com>
In-Reply-To: <51A53930.4030201@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQkLtDfotKZgnVhSRfbz50ZdxtB/BpZB1XG1aQgGkW+SgpbHMueY+hByN8f56zDv+ZM+lG+W
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:30:32 -0000

Arturo,

Who said "...huu, scary Argentina, do not go there"? Where? In this list?


Em 28/05/2013 20:09, Arturo Servin escreveu:
> Juliao,
> 
> 	I went to all this sites (besides BBC Brazil) and searched for
> Argentina. There were some news about economy, the lady President, some
> about the senate, commercial balance but none saying "huu, scary
> Argentina, do not go there".
> 

From aservin@lacnic.net  Tue May 28 16:36:31 2013
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 D02B121F86CE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8l+k2gj3rfL6 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:36:31 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id D87FE21F8619 for <ietf@ietf.org>; Tue, 28 May 2013 16:36:30 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2800:af:ba31:739:501a:b0ca:146e:a8f3]) by mail.lacnic.net.uy (Postfix) with ESMTP id AC83E308437 for <ietf@ietf.org>; Tue, 28 May 2013 20:36:02 -0300 (UYT)
Message-ID: <51A53F70.7060103@lacnic.net>
Date: Tue, 28 May 2013 20:36:16 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br> <51A5004E.60706@si6networks.com> <51A52C0A.7000805@braga.eti.br> <51A53930.4030201@gmail.com> <51A53E0B.7080300@braga.eti.br>
In-Reply-To: <51A53E0B.7080300@braga.eti.br>
X-Enigmail-Version: 1.5.1
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:36:31 -0000

	"not be recommended" sounds to me it sounded like "huu, scary, do not
go there".

	
/as

On 5/27/13 2:31 AM, Juliao Braga wrote:> According to the news
>published for a long time in Brazilian newspapers
> and magazines, Buenos Aires (a wonderful place!) would not be
> recommended. But who should tell us about the true cenary would be our
> Argentine friends.
>
> Juliao



On 5/28/13 8:30 PM, Juliao Braga wrote:
> Arturo,
> 
> Who said "...huu, scary Argentina, do not go there"? Where? In this list?
> 
> 
> Em 28/05/2013 20:09, Arturo Servin escreveu:
>> Juliao,
>>
>> 	I went to all this sites (besides BBC Brazil) and searched for
>> Argentina. There were some news about economy, the lady President, some
>> about the senate, commercial balance but none saying "huu, scary
>> Argentina, do not go there".
>>

From randy@psg.com  Tue May 28 16:44:12 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF1B11E80A6 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:44:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ItGHCT7d6int for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:44:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEDD21E8090 for <ietf@ietf.org>; Tue, 28 May 2013 16:44:12 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UhTYo-0007n4-0d; Tue, 28 May 2013 23:44:10 +0000
Date: Wed, 29 May 2013 08:44:08 +0900
Message-ID: <m27gii3c1j.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
In-Reply-To: <20130528160803.GC28387@mx1.yitter.info>
References: <20130520134442.30045.33596.idtracker@ietfa.amsl.com> <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info>
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: Tue, 28 May 2013 23:44:12 -0000

>> remove the rrtypes from the registry
> While it's good to see that the Internet Exemplary Taste-enForcers are
> alive and well, I would have an extremely strong objection to that
> approach.

jck was trying to enumerate alternatives.  he omitted one.  i am not a
particular advocate of any of them, including the above.

but i think the draft in question has very serious privacy issues, and
would like to focus on that, not characterization of the messengers.

randy

From juliao@braga.eti.br  Tue May 28 16:45:28 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28FB11E80BA for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.274
X-Spam-Level: 
X-Spam-Status: No, score=-3.274 tagged_above=-999 required=5 tests=[AWL=0.325,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydpjOzVOuVMD for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:45:23 -0700 (PDT)
Received: from mail-gh0-f170.google.com (mail-gh0-f170.google.com [209.85.160.170]) by ietfa.amsl.com (Postfix) with ESMTP id 5CC0311E80A6 for <ietf@ietf.org>; Tue, 28 May 2013 16:45:23 -0700 (PDT)
Received: by mail-gh0-f170.google.com with SMTP id z10so2352280ghb.15 for <ietf@ietf.org>; Tue, 28 May 2013 16:45:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=UjmLCBtw0xd6P8nre/BnTtZrsrLDTrCnt/t90UVoKUE=; b=kNnNj23aHOhaxnIQ7jBXsJnVkVH9dcOKeFtcoifWIEINT1urkLy44y9/534cdygJSk vWnBp+FQD2eCkO23Rmo6i2IEztkzd5m6n+tSblRKZG8rCNNX5j6VEOvRwQMeiu27Erkh VMJwKRLNIP+4I8rcmCGaZubk4FBgYrES1WQjWtZOfmsSEnFioBLLQrY/xNYyR6LJOvCE R58GwXeNS3qJ12u/vszI3kjTVuN4/oucby0CimRKAJp6XOyMTQuJIfM4l+oGFu7lQih8 3nhagGXy6PMv3nCsoh6LcFdE57vEbn3C/SsG/8rI8/b8RaucPXvddct8Qz87XXaltX5E pWng==
X-Received: by 10.236.127.243 with SMTP id d79mr95507yhi.4.1369784719495; Tue, 28 May 2013 16:45:19 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id y24sm49303817yhn.20.2013.05.28.16.45.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 16:45:18 -0700 (PDT)
Message-ID: <51A54188.60206@braga.eti.br>
Date: Tue, 28 May 2013 20:45:12 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br> <51A5004E.60706@si6networks.com> <51A52C0A.7000805@braga.eti.br> <51A53930.4030201@gmail.com> <51A53E0B.7080300@braga.eti.br> <51A53F70.7060103@lacnic.net>
In-Reply-To: <51A53F70.7060103@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnzrv7uE+YcHA6IoEarDEBiMjRog5Fu1lW3XEMKybkBJVAscCgilL+OmgTOlqyhRM5H0OEE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:45:28 -0000

Arturo,

I'm sorry that you interpret this way. But absolutely, I do not mean to
offend. Only expressed a point of view and said that our Argentine
friends could clarify. You can not trust the press, totally.

Anyway, I apologize if there was offense.

Best Regards,

Juliao

Em 28/05/2013 20:36, Arturo Servin escreveu:
> 
> 	"not be recommended" sounds to me it sounded like "huu, scary, do not
> go there".
> 
> 	
> /as

From arturo.servin@gmail.com  Tue May 28 16:59:29 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F52911E80DE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:59:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NCaEG0weBKD for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 16:59:24 -0700 (PDT)
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by ietfa.amsl.com (Postfix) with ESMTP id 75AEA21F8EC2 for <ietf@ietf.org>; Tue, 28 May 2013 16:59:24 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id ha11so5947367vcb.35 for <ietf@ietf.org>; Tue, 28 May 2013 16:59:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=HN6U38ImKIEf5GJYc1hVMldozGclTVgDwe1FqnjmpAI=; b=ATq0ZJL2EtVpNamoBQS/BRYLBh38j+CvBvwEHHi4yWAyJvOhGQqdoAECDQj7dsdQ+W +VxbRSbL4RTRtl6Q7jMfCYs7uWdKtLBQYH0dz17Lpw5y4Kjh1qOdqOxFdFS8+dzBkcJ5 XBbBIEv4LVvI5rDsmsafiGIE4XplZWRjD7cbF1iBesC0w3K73Fjj7VLhx52VHUnxfyf7 UKGZ27G267NWjCRQvc7LEtbcry15rplMQvOef0MzDSzneqX8PFdg555kgeuIhDfJumK0 RdJvLLpCKbA9mBAFRdJh1JdA6pc7mV1af+Jt2sbnJ5Vi6IootLlOIVNa2gHjNTwkxZjF sV6g==
X-Received: by 10.220.252.10 with SMTP id mu10mr159019vcb.4.1369785563909; Tue, 28 May 2013 16:59:23 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba31:739:501a:b0ca:146e:a8f3]) by mx.google.com with ESMTPSA id aq10sm25964873ved.2.2013.05.28.16.59.20 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 16:59:22 -0700 (PDT)
Message-ID: <51A544D5.5080805@gmail.com>
Date: Tue, 28 May 2013 20:59:17 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <51A2EFAB.3010106@braga.eti.br> <51A4B2C6.3050706@gont.com.ar> <51A4CB0D.9010001@braga.eti.br> <51A4E5B5.3020109@gont.com.ar> <51A4F57C.8000902@braga.eti.br> <51A5004E.60706@si6networks.com> <51A52C0A.7000805@braga.eti.br> <51A53930.4030201@gmail.com> <51A53E0B.7080300@braga.eti.br> <51A53F70.7060103@lacnic.net> <51A54188.60206@braga.eti.br>
In-Reply-To: <51A54188.60206@braga.eti.br>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 23:59:29 -0000

	Not taken. It was estrange to me that it were many news about how bad
Argentina is in the Brazilian press. I read frequently BBC-Brazil and
other newspapers of latin america and I haven't read such things, that
is why.

	
/as

On 5/28/13 8:45 PM, Juliao Braga wrote:
> Arturo,
> 
> I'm sorry that you interpret this way. But absolutely, I do not mean to
> offend. Only expressed a point of view and said that our Argentine
> friends could clarify. You can not trust the press, totally.
> 
> Anyway, I apologize if there was offense.
> 
> Best Regards,
> 
> Juliao
> 
> Em 28/05/2013 20:36, Arturo Servin escreveu:
>>
>> 	"not be recommended" sounds to me it sounded like "huu, scary, do not
>> go there".
>>
>> 	
>> /as

From alejandroacostaalamo@gmail.com  Tue May 28 18:15:18 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27FCD21F8CE9 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 18:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yqf4rx+cUZfD for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 18:15:17 -0700 (PDT)
Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 8805C21F842B for <ietf@ietf.org>; Tue, 28 May 2013 18:15:17 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id q13so3632984vbe.36 for <ietf@ietf.org>; Tue, 28 May 2013 18:15:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Z1/7yNyyn3Fk32ZQ+0q5bV/5b7iGKJbCs1NTDWMgZwI=; b=winuyaf9JXl35dY8htdXZCeDCVV7X+uyDN1A2C1lQ9hKbqochTNMol04EIprrH/Bdt ksHuyoYv0z5HgQLoq5QW2Quq68iAfc2Pkfc5qHRAwrvIrNsnU3kjVmNtGxzLOHkEtm1S 0CHFmEM/prIXeh373Ft+7RQ2uQKLh0TNgOtpYsVN2QrHi9FA45+TIoVz7lEumg740SF0 e+JoUTcKEb23IDnG8R0q/bDQaCbo6iMO8qNLFJWAWyLS0oYliHa9ErAUb2YW5oHVCu5z bJnR5siqx3CFSCzYNX61WdINC0EW7eTHxeG2EBe1eG9QAlPohyFH3iDbRhm/hGERZS/9 pg9A==
MIME-Version: 1.0
X-Received: by 10.52.170.19 with SMTP id ai19mr222659vdc.25.1369790116930; Tue, 28 May 2013 18:15:16 -0700 (PDT)
Received: by 10.52.243.162 with HTTP; Tue, 28 May 2013 18:15:16 -0700 (PDT)
In-Reply-To: <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com>
Date: Tue, 28 May 2013 20:45:16 -0430
Message-ID: <CAOmxzdzcVeu4H_vG=c=Aws7e2pq0G3GaYQSdExxUFV3uhtLg1Q@mail.gmail.com>
Subject: Re: More participation from under-represented regions
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: "Edwin A. Opare" <aeopare@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 01:15:18 -0000

Hi Edwin,

On 5/26/13, Edwin A. Opare <aeopare@gmail.com> wrote:
{...}

>
> To elicit participation from the under-represented regions, the
> universities are a sure starting point, then a lot more industry-focused
> awareness creation by the ISOC local Chapters.

  I fully agree with you that universities might be an excellent starting point.
  I wonder if you have some ideas to shares in how to do this.

Thanks,

>
> --
> Regards,
>
> Edwin

Alejandro Acosta,

>
> On Sun, May 26, 2013 at 8:43 PM, Melinda Shore
> <melinda.shore@gmail.com>wrote:
>
>> On 5/26/13 12:08 PM, SM wrote:
>> > The elephant in the
>> > room is that there hasn't been any discussion about what has been done
>> > to get more participation from under-represented regions but nobody has
>> > mentioned that.
>>
>> One of the things that's really popped out in the discussion
>> on the ericas list is that none of the people posting have
>> been from vendors/manufacturers, which right now is by far
>> the largest sector participating in the IETF.  The posters
>> have either been academics or from operators.  We can't even
>> get much participation from operators in North America and
>> Europe.  The industry sector bias in IETF participation is
>> possibly compounding the regional bias.
>>
>> Melinda
>>
>>
>


-- 
=====
^A.......o$

From juliao@braga.eti.br  Tue May 28 18:50:43 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7385421F8F29 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 18:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhQIeIioqT+3 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 18:50:43 -0700 (PDT)
Received: from mail-gg0-x234.google.com (mail-gg0-x234.google.com [IPv6:2607:f8b0:4002:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id CDD2921F8F20 for <ietf@ietf.org>; Tue, 28 May 2013 18:50:42 -0700 (PDT)
Received: by mail-gg0-f180.google.com with SMTP id q4so2279100ggn.11 for <ietf@ietf.org>; Tue, 28 May 2013 18:50:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=6+Vxu5P8qx+Zzl8VKjVFwM2rOKn94qcUtN2IyKTBt0c=; b=ObcwpKvZntWpFYWsxh01cRxoe/+DqiblKBLtIKQzjzidFnDy/k8lauamTkNy+Hk00p pPvVpL/dC0w5g+3+QdqhN2Ob9k3WtW1S7TGkS7hMfBXrf6DssLLakg4anXpvHShXTdZ4 bvxLlRtiTUvrcnK8NLqnEQ7t3RMSOb689yj3u2hkqKl+sxESysmsL86NjaSu631+h6c6 WgTsd6vdwzhxagYDrkO72a3+nedT6P38CG5qzGPYUWAcThKmrmW5a9W9jdVHFhPhidBr 5/HvA+xiVv+U6NyHQCVOAmdOmEC7RHm0zDMaRkXXWIQ+Ga8hWUSkun1UZ4ZmYLmDc0GV T57A==
X-Received: by 10.236.113.134 with SMTP id a6mr187506yhh.150.1369792242297; Tue, 28 May 2013 18:50:42 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id g40sm30802502yhj.15.2013.05.28.18.50.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 18:50:41 -0700 (PDT)
Message-ID: <51A55EEC.5020108@braga.eti.br>
Date: Tue, 28 May 2013 22:50:36 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org, j@braga.net.br
Subject: Re: More participation from under-represented regions
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <51A273FF.6060109@gmail.com> <CANeGSFm7QFHDwF9Rxpf9LQb=sLyaO6viz47jrPrHEjpWHWO0ow@mail.gmail.com> <CAOmxzdzcVeu4H_vG=c=Aws7e2pq0G3GaYQSdExxUFV3uhtLg1Q@mail.gmail.com>
In-Reply-To: <CAOmxzdzcVeu4H_vG=c=Aws7e2pq0G3GaYQSdExxUFV3uhtLg1Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnfQPmfT8Q75zFTPq2wjh0JVU00b0jwvke0iCY/yGqZaZ/sBQ9Qr4+d4kROiNyXhtaxjtW6
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 01:50:43 -0000

Just one, Alejandro, here in Brazil:

Next July, 23-26 in Maceio, Brazil will be held the 13o. CSBC (the main
annual meeting of SBC - Brazilian Computer Society. A big meeting!).

I sent an e-mail to coordinators, requesting a BoF to talk about the
IETF and ISOC Fellowships.

If they approve a space, I'll inform the ISOC-BR about it. I'll be there
and I can provide the necessary information. But can be others.

Also, the Vice-President of the SBC (Lisandro Granville Zambenedetti -
granville@inf.ufrgs.br) was at IETF 86 in Orlando, and therefore knows
the IETF. Additionally the IETF could talk with Lisandro to joint
actions in universities and research centers in Brazil. I think the
ISOC-BR could do this contact, if necessary.

Juliao

Em 28/05/2013 22:15, Alejandro Acosta escreveu:
> I fully agree with you that universities might be an excellent starting point.
>   I wonder if you have some ideas to shares in how to do this.

From melinda.shore@gmail.com  Tue May 28 19:09:20 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C43D11E80DF for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level: 
X-Spam-Status: No, score=-2.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3HtJbVQcN1S for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:09:19 -0700 (PDT)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8194011E80AD for <ietf@ietf.org>; Tue, 28 May 2013 19:09:19 -0700 (PDT)
Received: by mail-pb0-f51.google.com with SMTP id jt11so8560980pbb.38 for <ietf@ietf.org>; Tue, 28 May 2013 19:09:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=YksEsuBVqP81GKuofPN+HwTZY+39Vg/9kuHV+kKw55s=; b=LFPrtMgEa1YaNtxkmq1GbR06ZCUc9f2HO34mvzpu61RauHXNHiL9DemMjuciHxPPSG vzkHyxqvuTv8E5FPNZcanBNvaPdNU1OlGnlKVgJEXu6wB9vcITEpSPDzsDlgBVrQVTHE 2V0Bbehvkxpr8OjgCis3623XrT24smj7B0J1td6F1zkrOPt59XXB5i0Z/k6VDJjH2Apt 9vJB2neb2NM/Km2jL55ixlWvI8NT9GMRsEOhUAI3YxMhibTMbfYq4zB7SfDUaIVZNjDu ld7f1lPxkRjERZqhDCG5v5c11zbWP1mk0t/pA06uwja90mBM5Qc4CHuYdVAKfvmIRFkA ZhtQ==
X-Received: by 10.68.28.164 with SMTP id c4mr565979pbh.105.1369793359221; Tue, 28 May 2013 19:09:19 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id ra4sm37590957pab.9.2013.05.28.19.09.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 19:09:18 -0700 (PDT)
Message-ID: <51A5634B.4000707@gmail.com>
Date: Tue, 28 May 2013 18:09:15 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 02:09:20 -0000

On 5/28/13 3:06 PM, l.wood@surrey.ac.uk wrote:
> The centres for networking industry in Australia are Melbourne and Sydney, in that order. 
> It's a bit like IETF 51 being held in Grimsby, not London or Cambridge.

Okay.  So, should we be extrapolating from this to what
we can expect from Brazilians if we meet in Buenos
Aires?

Melinda


From aservin@lacnic.net  Tue May 28 19:27:45 2013
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 86BAF11E80AD for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:27:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1dFPrlUMbf5b for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:27:44 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 52FAA11E80A2 for <ietf@ietf.org>; Tue, 28 May 2013 19:27:43 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2800:af:ba30:c08c:ac6b:5931:111f:5a42]) by mail.lacnic.net.uy (Postfix) with ESMTP id 59FCA308432 for <ietf@ietf.org>; Tue, 28 May 2013 23:27:20 -0300 (UYT)
Message-ID: <51A56797.2050208@lacnic.net>
Date: Tue, 28 May 2013 23:27:35 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com>
In-Reply-To: <51A5634B.4000707@gmail.com>
X-Enigmail-Version: 1.5.1
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 02:27:46 -0000

	Perhaps not. Buenos Aires is also a big hub of technology in Latin
America. In addition as it was mentioned it relatively close from Sao
Paulo, Montevideo and Santiago. Also there are direct flights from other
major cities in Peru and Colombia.

	Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will always
split audiences as these are the major tech hubs in the region (also add
Bogota, Lima, San Jose and other cities). So, I think it is not
comparable with Australia.

as

	

On 5/28/13 11:09 PM, Melinda Shore wrote:
> On 5/28/13 3:06 PM, l.wood@surrey.ac.uk wrote:
>> The centres for networking industry in Australia are Melbourne and Sydney, in that order. 
>> It's a bit like IETF 51 being held in Grimsby, not London or Cambridge.
> 
> Okay.  So, should we be extrapolating from this to what
> we can expect from Brazilians if we meet in Buenos
> Aires?
> 
> Melinda
> 

From juliao@braga.eti.br  Tue May 28 19:39:04 2013
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A8F611E80D3 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:39:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SFz8xh1wQDYp for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:39:03 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 7DF3811E80D2 for <ietf@ietf.org>; Tue, 28 May 2013 19:39:03 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id z20so461651yhz.25 for <ietf@ietf.org>; Tue, 28 May 2013 19:39:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=f8B6Oy8bYG0Ccbvg5GCr9h9n+WTUegEIYC2HwIiT4hE=; b=JlYZUMRFniCHAh9uJ0G4ak1P7yDi+eiZFBnjgtPckSuHt+cDaHywDPDaDhLet/rHdx eD5MddxtQB22uZDKN+u83ztnX1ZpNViHd1VN5E73C0rqlZwZkgWT+PTfpjJlmQycYsS3 Hp2hRsLJgSOr+Jp+r/4Y8PLKFER/2TmfObXoN4vIwQInyiBPsZ1XXWXdPPhlPmCep6z/ K9bF0sDVOyhL3AZa0Lg2I/CYE13GhlvnuI5XF16iU2Cgn1oOvgvcIhGOr5FraaK8EfD8 IOuqcO0z1P7YnqaANLdtBIRxSu9Lga5MtH/kGfkglJhU6DTyahce3LWBwL5AcC71mohr l9ug==
X-Received: by 10.236.112.234 with SMTP id y70mr228469yhg.154.1369795143051; Tue, 28 May 2013 19:39:03 -0700 (PDT)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id m47sm3076422yhb.11.2013.05.28.19.39.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 19:39:02 -0700 (PDT)
Message-ID: <51A56A42.8020603@braga.eti.br>
Date: Tue, 28 May 2013 23:38:58 -0300
From: Juliao Braga <juliao@braga.eti.br>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com>
In-Reply-To: <51A5634B.4000707@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnZNhgnZyDgQW5o4vxQ1mI02agA4EGqqUs2+yoE91z+C7p2eRA33Wy+vi6Q4RvsG3jgLKZ2
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 02:39:04 -0000

I think we can expect a lot of Brazilians people in Buenos Aires.

Juliao

Em 28/05/2013 23:09, Melinda Shore escreveu:
> Okay.  So, should we be extrapolating from this to what
> we can expect from Brazilians if we meet in Buenos
> Aires?

From melinda.shore@gmail.com  Tue May 28 19:47:57 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22B3111E80D2 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.279
X-Spam-Level: 
X-Spam-Status: No, score=-2.279 tagged_above=-999 required=5 tests=[AWL=0.320,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wif0zhg-tm2l for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:47:51 -0700 (PDT)
Received: from mail-pd0-f180.google.com (mail-pd0-f180.google.com [209.85.192.180]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA9721F8B27 for <ietf@ietf.org>; Tue, 28 May 2013 19:47:51 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id 14so5888527pdc.25 for <ietf@ietf.org>; Tue, 28 May 2013 19:47:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=TmL2O69edgsji+ivrINZfqyvAox918L1W4OJT2DG64w=; b=tm2DKYFB8EVqhrsf7YSeGrqaAKbVuR34zFV4HbZ8785p/ajzMVBoF4r/usuoyQ6D3v iA/x1nw56oRsmRaCE1PCnmoi8/+gzC2nNypQzriPzT0b77149/ZUVNr7OWI9YBEEfDXO 0OcEAbGWFhZJmlfD5qNHZ0u8HQ3giPyihyWXtQwYsL8nZ9dZWG4eYlbkoT9UIljt47k9 ja32qR128wosshCzTkA7beazHxItiITCuDgNSGf5A5LQrlK52rkVAgDssKghfAz0rHtu 6q5tAtgxiME2jEviJRGMEqTKVB879w7nsdK7WvoEOM9Gq0CsUVfjjJwPYm2OwcfhrPT0 OB+Q==
X-Received: by 10.66.216.170 with SMTP id or10mr1276815pac.31.1369795670957; Tue, 28 May 2013 19:47:50 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id ya4sm35268907pbb.24.2013.05.28.19.47.49 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 19:47:49 -0700 (PDT)
Message-ID: <51A56C53.7070709@gmail.com>
Date: Tue, 28 May 2013 18:47:47 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net>
In-Reply-To: <51A56797.2050208@lacnic.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: Wed, 29 May 2013 02:47:57 -0000

On 5/28/13 6:27 PM, Arturo Servin wrote:
> 	Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will always
> split audiences as these are the major tech hubs in the region (also add
> Bogota, Lima, San Jose and other cities). So, I think it is not
> comparable with Australia.

I actually don't agree with Lloyd that the reason that the Australian
meeting didn't lead to increased Australian participation was that it
was because it was in Adelaide.  I don't expect a South American
meeting in any South American city to lead to an increase in Latin
American participation, either.

Melinda



From marka@isc.org  Tue May 28 19:52:16 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC5C21F8B27 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:52:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id un2I647a3FJP for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 19:52:15 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB4321F8A6B for <ietf@ietf.org>; Tue, 28 May 2013 19:52:14 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 3ABBF5F983B; Wed, 29 May 2013 02:52:04 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1369795933; bh=56hukKy2zER4f60/IyjOe/TAddI4vSBCXXTW4RgQjhM=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=iStEq/rpbHTs0ZR8xKGpF42ef33C10MJLFGNzR0wzk07n+ECGt0ogtGlpNZUowxan JaPOuA5gBoOtLvdnb49sn0QoNjoJ782CQJ66ipvNmWWD/lL7PDH0Oc4tmzQ9jWbDjl ZaqpEw7KCRZKTsJ+u0uCauMY8X+SJbnQ4ER1z9TA=
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 3F6A7216C40; Wed, 29 May 2013 02:52:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [IPv6:::1]) by drugs.dv.isc.org (Postfix) with ESMTP id 564CD34C50C1; Wed, 29 May 2013 12:51:59 +1000 (EST)
To: Melinda Shore <melinda.shore@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com>
Subject: Re: IETF Meeting in South America
In-reply-to: Your message of "Tue, 28 May 2013 09:15:17 -0800." <51A4E625.3020406@gmail.com>
Date: Wed, 29 May 2013 12:51:59 +1000
Message-Id: <20130529025159.564CD34C50C1@drugs.dv.isc.org>
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, 29 May 2013 02:52:16 -0000

In message <51A4E625.3020406@gmail.com>, Melinda Shore writes:
> On 5/28/13 6:20 AM, Christian O'Flaherty wrote:
> > Probably, this lack of social interaction in our region is one of
> > the main reasons for low participation. Most of latin american
> > IETFers are currently living outside the region and they engaged in
> > the IETF when living in the US or Europe. It's difficult to be
> > involved when no one else around is working in it or think it doesn't
> > fit well in their current work. A physical meeting will help to
> > "demystify" the IETF, making it "accesible" from a professional
> > perspective.
> 
> Any sense of why that didn't happen with Australians after
> the Adelaide meeting?

Adelaide is a small city.  If you were picking Australian cities
to promote local interaction Adelaide would be the 4th-6th city
you would choose.  Melboure, Sydney and Brisbane are the top 3
with some debate about the order.
 
> I'm not opposed to meeting in South America but there have
> been an awful lot of assertions about this or that happening
> if we do, without a lot of supporting evidence.  History,
> unfortunately, doesn't support many of these assertions, and
> I think beating the meeting location question to death is
> at least some small distraction from trying to get at the core
> issues.
> 
> For whatever it's worth, I was participating on IETF mailing lists
> well before attending a meeting.  Granted, I'm a native English
> speaker and wasn't dealing with that as an issue but probably
> more to the point was that there was work going on in the IETF
> that directly impacted work I was doing myself.
> 
> Melinda
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From arturo.servin@gmail.com  Tue May 28 20:09:18 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BAAE21E805E for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 20:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AcemUtmt7E+M for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 20:09:12 -0700 (PDT)
Received: from mail-qe0-f43.google.com (mail-qe0-f43.google.com [209.85.128.43]) by ietfa.amsl.com (Postfix) with ESMTP id D39F111E80D2 for <ietf@ietf.org>; Tue, 28 May 2013 20:09:11 -0700 (PDT)
Received: by mail-qe0-f43.google.com with SMTP id k5so4776663qej.16 for <ietf@ietf.org>; Tue, 28 May 2013 20:09:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=yKqICF1shudg+4UPrfkJjWKcAXg1c2UhsYm4yUJfZ/Y=; b=Ba1OPAn8wEzOuDWWKaNLv5avyuq9wcBdm1S8Kl1XaRZBPpCPyok5PZTcSU1/qixEAz nB1xHiPH+MYtiisUZjpGba9BvyMmxoRvjri3iPEEGS3GJuawoxnwyxg6K1/2C4Cyrd+K r+pxWx+k+IkUEHQ7p/ExcwXLGL8p7TLD3Zsir/5esLRjUt/RaZbO6HgX1TNkaBFbHi6D n2yiquA7gs4nkShyVeNZWGFLuMI3aXwSqtOnyvQGPA53iFlU7eUu5RK6lsAvbA7ZZxnj PjoXF0y3OCeqveKgwmOS33vDQxC7rpy8XElqU/VRRhXXMIL8NgTp2FhwYrWtWpgAbPs4 Qm2w==
X-Received: by 10.229.13.165 with SMTP id c37mr271708qca.34.1369796951314; Tue, 28 May 2013 20:09:11 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([2800:af:ba30:c08c:ac6b:5931:111f:5a42]) by mx.google.com with ESMTPSA id j10sm29373978qeh.0.2013.05.28.20.09.09 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 20:09:10 -0700 (PDT)
Message-ID: <51A57153.9010009@gmail.com>
Date: Wed, 29 May 2013 00:09:07 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <51A56C53.7070709@gmail.com>
In-Reply-To: <51A56C53.7070709@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: Wed, 29 May 2013 03:09:18 -0000

On 5/28/13 11:47 PM, Melinda Shore wrote:
> On 5/28/13 6:27 PM, Arturo Servin wrote:
>> 	Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will always
>> split audiences as these are the major tech hubs in the region (also add
>> Bogota, Lima, San Jose and other cities). So, I think it is not
>> comparable with Australia.
> 
> I actually don't agree with Lloyd that the reason that the Australian
> meeting didn't lead to increased Australian participation was that it
> was because it was in Adelaide.  I don't expect a South American
> meeting in any South American city to lead to an increase in Latin
> American participation, either.
> 
> Melinda
> 

	If we just do a meeting probably it won't. But as Christian said it
before, that is not the plan. I think that the meeting would be a
catalyst to do more thing, but not a solution by it self.

.as

From l.wood@surrey.ac.uk  Tue May 28 20:20:49 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A5E21E804B for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 20:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.848
X-Spam-Level: 
X-Spam-Status: No, score=-5.848 tagged_above=-999 required=5 tests=[AWL=0.750,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBDz1y-KIr1M for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 20:20:43 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.116]) by ietfa.amsl.com (Postfix) with ESMTP id C143921F8EAD for <ietf@ietf.org>; Tue, 28 May 2013 20:20:42 -0700 (PDT)
Received: from [193.109.255.147:19944] by server-12.bemta-14.messagelabs.com id 25/46-15557-90475A15; Wed, 29 May 2013 03:20:41 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-72.messagelabs.com!1369797641!11913352!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 15686 invoked from network); 29 May 2013 03:20:41 -0000
Received: from unknown (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-2.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 29 May 2013 03:20:41 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 29 May 2013 04:20:40 +0100
From: <l.wood@surrey.ac.uk>
To: <melinda.shore@gmail.com>, <ietf@ietf.org>
Date: Wed, 29 May 2013 04:19:47 +0100
Subject: RE: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: Ac5cFv5KiTLC3mvTR1iCvrlSaseLPwABGDxO
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net>,<51A56C53.7070709@gmail.com>
In-Reply-To: <51A56C53.7070709@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 03:20:49 -0000

Melinda,

can you confine yourself to disagreeing with something I actually said?

Thanks so much!

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Melinda Sh=
ore [melinda.shore@gmail.com]
Sent: 29 May 2013 03:47
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America

On 5/28/13 6:27 PM, Arturo Servin wrote:
>       Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will alwa=
ys
> split audiences as these are the major tech hubs in the region (also add
> Bogota, Lima, San Jose and other cities). So, I think it is not
> comparable with Australia.

I actually don't agree with Lloyd that the reason that the Australian
meeting didn't lead to increased Australian participation was that it
was because it was in Adelaide.  I don't expect a South American
meeting in any South American city to lead to an increase in Latin
American participation, either.

Melinda



From sistopefuni@gmail.com  Tue May 28 21:17:00 2013
Return-Path: <sistopefuni@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F125521E804D for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 21:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kU6Otp5lFSqP for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 21:17:00 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB9421E804B for <ietf@ietf.org>; Tue, 28 May 2013 21:17:00 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id xn12so6639906obc.6 for <ietf@ietf.org>; Tue, 28 May 2013 21:16:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3B2UkAk03v7OCSZiMjYpTWWsazzmN+U23ErONgd5FNE=; b=hS5ABB9EtJHpp9J7qZG72WGpoUIG6X573XyD9v2ipewPIH8Pfg7066ZCZ9KPvkyM0S nwLLIg6bSQyRd+/38f8jWIr8kpJ15+hpPkMkbWdOEJxTfjzQQOfCH+JkQHgx7/bOkhlG KUU+JVTm8Y3J6W6uOMb2ALGJtWDDY3jxlP67LS9KuG7bTk0ejzjn7tPCBik83FlhRAoc O9Ad4as5AegSTjNi9ljkI3rcTEgsX8YcCxqMEUSMQyxKbVc3bbkCQO35wf0ZprZPXJpQ FIPataOzTJ8kBpz/Y55S1Es3OEaozdqSpUVvDI4PsnkPXZNxaIY9eacFD+1FAK6dF5s7 un3A==
MIME-Version: 1.0
X-Received: by 10.182.214.105 with SMTP id nz9mr516145obc.66.1369801019133; Tue, 28 May 2013 21:16:59 -0700 (PDT)
Received: by 10.182.154.37 with HTTP; Tue, 28 May 2013 21:16:59 -0700 (PDT)
In-Reply-To: <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com>
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com> <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com>
Date: Wed, 29 May 2013 01:16:59 -0300
Message-ID: <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com>
Subject: IETF Meeting in South America
From: I rob <sistopefuni@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=e89a8ff1cd4a28940604ddd3a721
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 04:17:01 -0000

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

Hello,

I agree with the Idea of a IETF meeting in South America.

I think it is a way to let the people know about IETF (of course there are
other ways, but this is a good one), to give the possibility to
students/engineers with very good skills to get into the IETF, thinking
that it is going to be published in universities in advance, to give time
to students to enroll to a mailing list and read the drafts to be presented.

Talking about my personal experience, I am pretty new in the IETF, but
since I have been involved, I teach my students (from Argentina)  about it,
I tell them, that they can participate, that is open, and I realize that
they didn't know it.

I understand that usually the place is chosen based on the most of
participant origin, but I think a meeting in Latin America is a
good opportunity to give the possibility to people from that region to know
about the IETF.

Kind Regards,

Ines Robles.

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

I would like to follow up on this proposal. Having a meeting in South
America scheduled two or three years in advance will let us engage
local organisations and individuals on a "project". We did several
activities in the region trying to encourage IETF participation, but
we're going to be much more effective if they're part of a plan with a
strong commitment (and effort) from the IETF community.

Since this opportunity was announced, there were several contacts and
proposals from different groups asking for additional information,
suggesting things to do, asking for details, etc. We now have a much
more fertile ground to do multiple things.

 Going further will also enrich the IETF work and community (making it
more international becomes a side effect). In this region there are
many engineers, software developers, people at Universities, etc. that
could provide new ideas and energy to the IETF.

Christian

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

<div class=3D"gmail_quote"><div class=3D"gmail_quote">Hello,<div><br></div>=
<div>I agree with the Idea of a IETF meeting in South America.</div><div><b=
r>
</div><div>I think it is a way to let the people know about IETF (of course=
 there are other ways, but this is a good one), to give the possibility to =
students/engineers with very good skills to get into the IETF, thinking tha=
t it is going to be published in universities in advance, to give time to s=
tudents to enroll to a mailing list and read the drafts to be presented.</d=
iv>


<div><br></div><div>Talking about my personal experience,=A0I am pretty new=
 in the IETF, but since I have been involved, I teach my students (from Arg=
entina) =A0about it, I tell them, that they can participate, that is open, =
and I realize that they=A0didn&#39;t know it.=A0=A0=A0</div>


<div><br></div><div>I understand that usually the place is=A0chosen=A0based=
 on the=A0most=A0of participant=A0origin, but I think a meeting in Latin Am=
erica is a good=A0opportunity=A0to give the possibility to people from that=
 region to know about the IETF.=A0</div>


<div><br></div><div>Kind Regards,</div><div><br></div><div>Ines Robles.</di=
v><div><br></div><div><div class=3D"gmail_quote">
------------------------------<br><br>
I would like to follow up on this proposal. Having a meeting in South<br>
America scheduled two or three years in advance will let us engage<br>
local organisations and individuals on a &quot;project&quot;. We did severa=
l<br>
activities in the region trying to encourage IETF participation, but<br>
we&#39;re going to be much more effective if they&#39;re part of a plan wit=
h a<br>
strong commitment (and effort) from the IETF community.<br>
<br>
Since this opportunity was announced, there were several contacts and<br>
proposals from different groups asking for additional information,<br>
suggesting things to do, asking for details, etc. We now have a much<br>
more fertile ground to do multiple things.<br>
<br>
=A0Going further will also enrich the IETF work and community (making it<br=
>
more international becomes a side effect). In this region there are<br>
many engineers, software developers, people at Universities, etc. that<br>
could provide new ideas and energy to the IETF.<br>
<br>
Christian<br><br></div></div>
</div><br>
</div><br>

--e89a8ff1cd4a28940604ddd3a721--

From sistopefuni@gmail.com  Tue May 28 21:25:52 2013
Return-Path: <sistopefuni@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10D7B21E804B for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 21:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.499,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OiiLiE8ROJSE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 21:25:47 -0700 (PDT)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by ietfa.amsl.com (Postfix) with ESMTP id 719C221F89FF for <ietf@ietf.org>; Tue, 28 May 2013 21:25:47 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id g12so10964350oah.26 for <ietf@ietf.org>; Tue, 28 May 2013 21:25:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VroxDJeGYDhd6SfzFAWD3bfgjDmJV2UHCciD/nGH5i4=; b=KroiSyfBsbjhT2X2v+4aQM4IplQrObGjLDvnfAiOWqlMKKVdrxUeidfEhi78VbNYhR nJsuXsaZQ7Bqiqah0Nzb3Pq2Vx2a07R/aPYidNbYj4wxkkhEvtg4KgS2NGhATAMTtMw/ 3ydI49UmyM5LyMnST7Z1MUPO5eQRPmRaorsbrpx8W+Cr3MnnnEmqx/v26WNKGJJX1cje eto+yBbKZyqKMn3qiRHd/UFSOLQ9zCQvUAOf0/Ggwr2E3jAUOlnNBeiB4KLTb6FR8sIG yp0W0ASB2Kg/3cdTGcnBjrgGBOjxmdSxoTwKwAIaU9elEbIzkhMne5vUGCRPw9343m8V Rb+w==
MIME-Version: 1.0
X-Received: by 10.60.84.35 with SMTP id v3mr548081oey.36.1369801547010; Tue, 28 May 2013 21:25:47 -0700 (PDT)
Received: by 10.182.154.37 with HTTP; Tue, 28 May 2013 21:25:46 -0700 (PDT)
In-Reply-To: <CAP+sJUccj9we_zRA4r9dHM8Zbq=UH9Hc9WEjgUtVOJXLue3QDA@mail.gmail.com>
References: <CAP+sJUdmDEm36vNNbFW4mOjJq=Bh0C_rVFaDo8ZUib+n2BPm-A@mail.gmail.com> <CAP+sJUccj9we_zRA4r9dHM8Zbq=UH9Hc9WEjgUtVOJXLue3QDA@mail.gmail.com>
Date: Wed, 29 May 2013 01:25:46 -0300
Message-ID: <CAKaL0mCBU0_=R4ZMWTdSFEdour=EAhgMSt9ek9RQLtAk-zMeuA@mail.gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
From: I rob <sistopefuni@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e0111b9289f55a804ddd3c615
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 04:25:52 -0000

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

Hello,



> I'd also say that I've never heard anyone making that sort of statement.
> For instance, the argentinan government itself has a program to increase
> Internet connectivity throughout the country --
>

 That is the web page of the program that Fernando mentions,
http://www.conectarigualdad.gob.ar/  (spanish ) - netbooks with windows and
Linux :)  for the kids -

>
> > His view is shared by many, so in the event IETF gets to meet in Buenos
> > Aires, if the meeting becomes public, don't be surprised to see some
> > coordinated political manifestation.
>
> I live in Argentina too, and people don't make political manifestation
about Internet topics. In opposite. In Mendoza (Arg.) we did a lot of
events (conferences, hands-on) open to the people (no technical) about IPv6
and they were very interested on it and the concurrence was high (200
people :-))

Argentina is a beautiful place to know :-), have a lot of things to do, and
is always full of tourist during all the seasons.

Kind Regards,

Ines Robles.

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

<div class=3D"gmail_quote"><div class=3D"gmail_quote"><div class=3D"gmail_q=
uote"><div>Hello,</div><div><br></div><div>=A0</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
I&#39;d also say that I&#39;ve never heard anyone making that sort of state=
ment.<br>
For instance, the argentinan government itself has a program to increase<br=
>
Internet connectivity throughout the country --=A0<br></blockquote><div>=A0=
</div><div>=A0That is the web page of the program that Fernando mentions,=
=A0<a href=3D"http://www.conectarigualdad.gob.ar/" target=3D"_blank">http:/=
/www.conectarigualdad.gob.ar/</a>=A0 (spanish ) - netbooks with windows and=
 Linux :) =A0for the kids -</div>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&gt; His view is shared by many, so in the event IETF gets to meet in Bueno=
s<br>
&gt; Aires, if the meeting becomes public, don&#39;t be surprised to see so=
me<br>
&gt; coordinated political manifestation.<br><br></blockquote><div>I live i=
n Argentina too, and people don&#39;t make political manifestation about In=
ternet topics. In opposite. In Mendoza (Arg.) we did a lot of events (confe=
rences, hands-on) open to the people (no technical) about IPv6 and they wer=
e very=A0interested=A0on it and the concurrence was high (200 people :-))</=
div>


<div><br></div><div>Argentina is a beautiful=A0place=A0to know :-), have a =
lot of things to do, and is always full of tourist during all the seasons.<=
/div><div><br></div><div>Kind Regards,</div><div><br></div><div>Ines Robles=
.</div>


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

--089e0111b9289f55a804ddd3c615--

From ggm@algebras.org  Tue May 28 21:50:55 2013
Return-Path: <ggm@algebras.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 59A6221F86C3 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 21:50:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uV74BxCpFMTE for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 21:50:54 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 137DF21F8681 for <ietf@ietf.org>; Tue, 28 May 2013 21:50:53 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id 9so22399506iec.8 for <ietf@ietf.org>; Tue, 28 May 2013 21:50:53 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=nh6DHgEczE8/p/2y7ERgsZR7tEdZFl8wF+xje1RR9TE=; b=I9HSY1Gf5GdQ78x+E/mIZjnNXTxjlpvxRdVTYgnWknhFEd9N+slhEaeFhA6otC+jJe qu06d8rAT1vBnjkUW7L0x/EkMAHiS4gP6I3m9N2ZQ2sPmhyrxHdynOweh6Xouzi2Aw77 ubtkHTrAe4KOktn4CcFMCBq5YxeoWQ2icez2FM1lbq4BoloBqUxdZB6gN0MyZI5hHkXm F8TKYHEioYwGpC4yBLH1cAD6BSIOYhA6aWMPjV6rVVXl45nEeR05zXzDlz03DHf75pMs W0BhFtpiydd3wObMGnI0yxoBP3iEecwUum4Hp9RNKNRqSs65vIFLZV1nbVcRgZgq2VB1 Oo0Q==
MIME-Version: 1.0
X-Received: by 10.50.141.230 with SMTP id rr6mr8536633igb.89.1369803053401; Tue, 28 May 2013 21:50:53 -0700 (PDT)
Received: by 10.64.170.236 with HTTP; Tue, 28 May 2013 21:50:53 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:c5b9:1425:b023:228f]
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <51A56C53.7070709@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk>
Date: Wed, 29 May 2013 14:50:53 +1000
Message-ID: <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: George Michaelson <ggm@algebras.org>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=089e010d9576691cab04ddd42003
X-Gm-Message-State: ALoCoQkoqYlELS4x5ffQfXNlX1m4ERG7SqSOcop8THb/hcLisnc8Wj6akf6kIZ0WHxDbPhqIeJu0
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, 29 May 2013 04:50:55 -0000

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

I went to Adelaide. it was my first IETF. I am now an IETF
regular-irregular, of 10+ years standing. So, proof by example, it
increased Australian participation by at least 1.

In fact, I think by scale, Australians punch above their weight. Especially
if you include americans who live in Australia, Australians who live in the
mainland of the USA.

I think IETF going to Adelaide had net positive effects on Australian
participation. Small. but real.

-G


On Wed, May 29, 2013 at 1:19 PM, <l.wood@surrey.ac.uk> wrote:

> Melinda,
>
> can you confine yourself to disagreeing with something I actually said?
>
> Thanks so much!
>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Melinda
> Shore [melinda.shore@gmail.com]
> Sent: 29 May 2013 03:47
> To: ietf@ietf.org
> Subject: Re: IETF Meeting in South America
>
> On 5/28/13 6:27 PM, Arturo Servin wrote:
> >       Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will
> always
> > split audiences as these are the major tech hubs in the region (also add
> > Bogota, Lima, San Jose and other cities). So, I think it is not
> > comparable with Australia.
>
> I actually don't agree with Lloyd that the reason that the Australian
> meeting didn't lead to increased Australian participation was that it
> was because it was in Adelaide.  I don't expect a South American
> meeting in any South American city to lead to an increase in Latin
> American participation, either.
>
> Melinda
>
>
>

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

<div dir=3D"ltr">I went to Adelaide. it was my first IETF. I am now an IETF=
 regular-irregular, of 10+ years standing. So, proof by example, it increas=
ed Australian participation by at least 1.<div><br></div><div style>In fact=
, I think by scale, Australians punch above their weight. Especially if you=
 include americans who live in Australia, Australians who live in the mainl=
and of the USA.</div>
<div style><br></div><div style>I think IETF going to Adelaide had net posi=
tive effects on Australian participation. Small. but real.</div><div style>=
<br></div><div style>-G</div></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">
On Wed, May 29, 2013 at 1:19 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:l=
.wood@surrey.ac.uk" target=3D"_blank">l.wood@surrey.ac.uk</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
Melinda,<br>
<br>
can you confine yourself to disagreeing with something I actually said?<br>
<br>
Thanks so much!<br>
<br>
Lloyd Wood<br>
<a href=3D"http://sat-net.com/L.Wood/" target=3D"_blank">http://sat-net.com=
/L.Wood/</a><br>
<br>
<br>
________________________________________<br>
From: <a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a> [<=
a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>] On Behal=
f Of Melinda Shore [<a href=3D"mailto:melinda.shore@gmail.com">melinda.shor=
e@gmail.com</a>]<br>

Sent: 29 May 2013 03:47<br>
To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: IETF Meeting in South America<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On 5/28/13 6:27 PM, Arturo Servin wrote:<br>
&gt; =A0 =A0 =A0 Going to Buenos Aires, Sao Paulo, Mexico City or Santiago =
will always<br>
&gt; split audiences as these are the major tech hubs in the region (also a=
dd<br>
&gt; Bogota, Lima, San Jose and other cities). So, I think it is not<br>
&gt; comparable with Australia.<br>
<br>
I actually don&#39;t agree with Lloyd that the reason that the Australian<b=
r>
meeting didn&#39;t lead to increased Australian participation was that it<b=
r>
was because it was in Adelaide. =A0I don&#39;t expect a South American<br>
meeting in any South American city to lead to an increase in Latin<br>
American participation, either.<br>
<br>
Melinda<br>
<br>
<br>
</div></div></blockquote></div><br></div>

--089e010d9576691cab04ddd42003--

From medel@globetel.com.ph  Tue May 28 22:10:30 2013
Return-Path: <medel@globetel.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B151521F8EEC for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 22:10:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.604
X-Spam-Level: 
X-Spam-Status: No, score=-1.604 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6cW-jJQRYBS for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 22:10:25 -0700 (PDT)
Received: from smtp02.globetel.com.ph (smtp02.globetel.com.ph [203.177.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id F0F7621F8ED8 for <ietf@ietf.org>; Tue, 28 May 2013 22:10:24 -0700 (PDT)
Received: from exgtbh02.globetel.com ([10.225.208.154]) by smtp02.globetel.com.ph (8.14.4/8.14.4) with ESMTP id r4T5A4n4014482 for <ietf@ietf.org>; Wed, 29 May 2013 13:10:22 +0800
Received: from EXVSGT02.globetel.com ([10.225.208.146]) by exgtbh02.globetel.com with Microsoft SMTPSVC(6.0.3790.3959);  Wed, 29 May 2013 13:18:01 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CE5C2B.E361A8C4"
Subject: RE: IETF Meeting in South America
Date: Wed, 29 May 2013 13:18:00 +0800
Message-ID: <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel.com>
In-Reply-To: <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: IETF Meeting in South America
Thread-Index: Ac5cJIpASzlEZtYLTPGLWdADRim8vQABryvw
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com><CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com> <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com>
From: "GT RAMIREZ, Medel G." <medel@globetel.com.ph>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 29 May 2013 05:18:01.0155 (UTC) FILETIME=[E3903130:01CE5C2B]
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626, 1.0.431, 0.0.0000 definitions=2013-05-29_02:2013-05-28, 2013-05-29, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1211240000 definitions=main-1305280383
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 05:10:30 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CE5C2B.E361A8C4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

How about in the Philippines? I can show my homeland...

I can help facilitate the event, why don't you give it a try!

=20

Regards

Medel

=20

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
I rob
Sent: Wednesday, May 29, 2013 12:17 PM
To: ietf@ietf.org
Subject: IETF Meeting in South America

=20

Hello,

=20

I agree with the Idea of a IETF meeting in South America.

=20

I think it is a way to let the people know about IETF (of course there
are other ways, but this is a good one), to give the possibility to
students/engineers with very good skills to get into the IETF, thinking
that it is going to be published in universities in advance, to give
time to students to enroll to a mailing list and read the drafts to be
presented.

=20

Talking about my personal experience, I am pretty new in the IETF, but
since I have been involved, I teach my students (from Argentina)  about
it, I tell them, that they can participate, that is open, and I realize
that they didn't know it.=20=20=20

=20

I understand that usually the place is chosen based on the most of
participant origin, but I think a meeting in Latin America is a good
opportunity to give the possibility to people from that region to know
about the IETF.=20

=20

Kind Regards,

=20

Ines Robles.

=20

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

I would like to follow up on this proposal. Having a meeting in South
America scheduled two or three years in advance will let us engage
local organisations and individuals on a "project". We did several
activities in the region trying to encourage IETF participation, but
we're going to be much more effective if they're part of a plan with a
strong commitment (and effort) from the IETF community.

Since this opportunity was announced, there were several contacts and
proposals from different groups asking for additional information,
suggesting things to do, asking for details, etc. We now have a much
more fertile ground to do multiple things.

 Going further will also enrich the IETF work and community (making it
more international becomes a side effect). In this region there are
many engineers, software developers, people at Universities, etc. that
could provide new ideas and energy to the IETF.

Christian

=20

=20

This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.

------_=_NextPart_001_01CE5C2B.E361A8C4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV=3D"Content-Type" CONTENT=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi,<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:"Calibri","sans-serif";color:#1F497D'>How about in the Philippines? I=
 can show my homeland&#8230;<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>I can help facilitate the event, why don&#8217;t you give it a try!<o:p>=
</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-=
family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","s=
ans-serif";color:#1F497D'>Regards<o:p></o:p></span></p><p class=3DMsoNormal=
><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#=
1F497D'>Medel<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;fon=
t-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-size:10=
.0pt;font-family:"Tahoma","sans-serif"'> ietf-bounces@ietf.org [mailto:ietf=
-bounces@ietf.org] <b>On Behalf Of </b>I rob<br><b>Sent:</b> Wednesday, May=
 29, 2013 12:17 PM<br><b>To:</b> ietf@ietf.org<br><b>Subject:</b> IETF Meet=
ing in South America<o:p></o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><div><div><p class=3DMsoNormal>Hello,<o:p></o:p></p><div><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I agree w=
ith the Idea of a IETF meeting in South America.<o:p></o:p></p></div><div><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
think it is a way to let the people know about IETF (of course there are ot=
her ways, but this is a good one), to give the possibility to students/engi=
neers with very good skills to get into the IETF, thinking that it is going=
 to be published in universities in advance, to give time to students to en=
roll to a mailing list and read the drafts to be presented.<o:p></o:p></p><=
/div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DM=
soNormal>Talking about my personal experience,&nbsp;I am pretty new in the =
IETF, but since I have been involved, I teach my students (from Argentina) =
&nbsp;about it, I tell them, that they can participate, that is open, and I=
 realize that they&nbsp;didn't know it.&nbsp;&nbsp;&nbsp;<o:p></o:p></p></d=
iv><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMso=
Normal>I understand that usually the place is&nbsp;chosen&nbsp;based on the=
&nbsp;most&nbsp;of participant&nbsp;origin, but I think a meeting in Latin =
America is a good&nbsp;opportunity&nbsp;to give the possibility to people f=
rom that region to know about the IETF.&nbsp;<o:p></o:p></p></div><div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>Kind =
Regards,<o:p></o:p></p></div><div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
></div><div><p class=3DMsoNormal>Ines Robles.<o:p></o:p></p></div><div><p c=
lass=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>------------------------------<br><br>I woul=
d like to follow up on this proposal. Having a meeting in South<br>America =
scheduled two or three years in advance will let us engage<br>local organis=
ations and individuals on a &quot;project&quot;. We did several<br>activiti=
es in the region trying to encourage IETF participation, but<br>we're going=
 to be much more effective if they're part of a plan with a<br>strong commi=
tment (and effort) from the IETF community.<br><br>Since this opportunity w=
as announced, there were several contacts and<br>proposals from different g=
roups asking for additional information,<br>suggesting things to do, asking=
 for details, etc. We now have a much<br>more fertile ground to do multiple=
 things.<br><br>&nbsp;Going further will also enrich the IETF work and comm=
unity (making it<br>more international becomes a side effect). In this regi=
on there are<br>many engineers, software developers, people at Universities=
, etc. that<br>could provide new ideas and energy to the IETF.<br><br>Chris=
tian<o:p></o:p></p></div></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p>=
</p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div>
<DIV>
This e-mail message (including attachments, if any) is intended for the use=
 of the individual or the entity to whom it is addressed and may contain in=
formation that is privileged, proprietary, confidential and exempt from dis=
closure. If you are not the intended recipient, you are notified that any d=
issemination, distribution or copying of this communication is strictly pro=
hibited. If you have received this communication in error, please notify th=
e sender and delete this E-mail message immediately.<BR>
</DIV></body></html>

------_=_NextPart_001_01CE5C2B.E361A8C4--

From jmamodio@gmail.com  Tue May 28 22:28:32 2013
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 9F7AA21F8EF7 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 22:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=0.453,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQetXdklTdjP for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 22:28:26 -0700 (PDT)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id C58B221F89FD for <ietf@ietf.org>; Tue, 28 May 2013 22:28:26 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id j6so11227232oag.32 for <ietf@ietf.org>; Tue, 28 May 2013 22:28:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=mPncx7aYpEjXrVcLg0kTiTFzyylnHcOkjs4x1HfVEEQ=; b=OVirhtJOVBViSOrzzrVGaY9FAWJBcO+gqPn1ZB9i0UtHf9zxt+eNAwJcMe7l7GPWH7 R8SJdI+PYOkFDqKuA5XrN51c7pO7Np0HLim9ROkZ0vRk0y7UiJdMLyzg8PNp1wYYL6uS pvcz9+MABmJ5ilT7xCois19hgnZN0ea1LuoUsRuRbqBffcR1Xr4ihwymPpw9tk+HXgt/ 8d2/aoIwY1Vl26o9NRQNuyuj6hQ1d8cAPdHreANHsmQSFu7p14VFsEmWhnmUztQ4kSgm uFmqTwQvyZgyHJhZkf/6i6imKGtn6ngrH6A7YAzZVW6C24bAQGQ4LiCSSadEoRfDBDRn PL0w==
X-Received: by 10.60.36.136 with SMTP id q8mr632030oej.90.1369805306292; Tue, 28 May 2013 22:28:26 -0700 (PDT)
Received: from [10.0.10.101] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id x10sm39525783oes.6.2013.05.28.22.28.25 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 May 2013 22:28:25 -0700 (PDT)
Subject: Re: IETF Meeting in South America
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com> <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com> <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com> <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel.com>
From: Jorge Amodio <jmamodio@gmail.com>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (10B329)
In-Reply-To: <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel.com>
Message-Id: <E3247277-B256-49E4-90C8-6843610357C0@gmail.com>
Date: Wed, 29 May 2013 00:28:23 -0500
To: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 05:28:32 -0000

Just wondering if some folks realize that IETF meetings are not missionary t=
rips, conferences, conventions or industry trade shows ...

-Jorge


From ynir@checkpoint.com  Tue May 28 23:27:11 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19BFA21F8FDC for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 23:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qqF9FwmuUXZZ for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 23:27:05 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DF10321F8FCB for <ietf@ietf.org>; Tue, 28 May 2013 23:27:04 -0700 (PDT)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r4T6QwPE031063; Wed, 29 May 2013 09:26:58 +0300
X-CheckPoint: {51A59D0D-E-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.48]) with mapi id 14.02.0342.003; Wed, 29 May 2013 09:26:58 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: IETF Meeting in South America
Thread-Topic: IETF Meeting in South America
Thread-Index: AQHOV831D4tngZxCqkCGgr/monvqF5kUanAAgAAFlwCAAAC7gIAABGOAgAAA3ACAAAF0AIAAAjmAgAAOsICAAAo3gIADonYAgABL0ACAAOJtgIAAlDuAgABpXQCAAAQgAIAAFhEAgAAw4YCAAGIQAIAAMyCAgABH/QA=
Date: Wed, 29 May 2013 06:26:57 +0000
Message-ID: <797371F0-F20C-4C1C-841E-893F08F04B85@checkpoint.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com>
In-Reply-To: <51A5634B.4000707@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.172]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
x-cpdlp: 11a431933ae712d659ae68c8e14b15f3d111c604cf
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <395B2E5AD243B04C839F66291DB32545@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 06:27:11 -0000

On May 29, 2013, at 5:09 AM, Melinda Shore <melinda.shore@gmail.com> wrote:

> On 5/28/13 3:06 PM, l.wood@surrey.ac.uk wrote:
>> The centres for networking industry in Australia are Melbourne and Sydne=
y, in that order.=20
>> It's a bit like IETF 51 being held in Grimsby, not London or Cambridge.
>=20
> Okay.  So, should we be extrapolating from this to what
> we can expect from Brazilians if we meet in Buenos
> Aires?

We should extrapolate to Americans and expect that all North American meeti=
ngs should be in Silicone Valley, otherwise American engineers won't partic=
ipate.

Unless Americans have some unique ability to travel that South Americans an=
d Australians don't.

Yoav


From paf@frobbit.se  Tue May 28 23:36:56 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7163D21F8FB3 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 23:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JKltPGs9W+AA for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 23:36:56 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id EA59221F8E34 for <ietf@ietf.org>; Tue, 28 May 2013 23:36:55 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::d14c:f600:646d:49bb] (unknown [IPv6:2a02:80:3ffc:0:d14c:f600:646d:49bb]) by mail.frobbit.se (Postfix) with ESMTPSA id 8987421C9A; Wed, 29 May 2013 08:36:54 +0200 (CEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <51A56797.2050208@lacnic.net>
Date: Wed, 29 May 2013 08:34:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <985F3F2E-8BDF-4BCC-9D18-C8BADB0DDDB8@frobbit.se>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com>, <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1503)
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, 29 May 2013 06:36:56 -0000

ICANN 48 is to be held in Buenos Aires, Argentina, 17-21 November 2013, =
and I am looking forward to it!

   Patrik

On 29 maj 2013, at 04:27, Arturo Servin <aservin@lacnic.net> wrote:

> 	Perhaps not. Buenos Aires is also a big hub of technology in =
Latin
> America. In addition as it was mentioned it relatively close from Sao
> Paulo, Montevideo and Santiago. Also there are direct flights from =
other
> major cities in Peru and Colombia.
>=20
> 	Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will =
always
> split audiences as these are the major tech hubs in the region (also =
add
> Bogota, Lima, San Jose and other cities). So, I think it is not
> comparable with Australia.
>=20
> as
>=20
> On 5/28/13 11:09 PM, Melinda Shore wrote:
>> On 5/28/13 3:06 PM, l.wood@surrey.ac.uk wrote:
>>> The centres for networking industry in Australia are Melbourne and =
Sydney, in that order.=20
>>> It's a bit like IETF 51 being held in Grimsby, not London or =
Cambridge.
>>=20
>> Okay.  So, should we be extrapolating from this to what
>> we can expect from Brazilians if we meet in Buenos
>> Aires?
>>=20
>> Melinda
>>=20


From sm@elandsys.com  Wed May 29 01:41:29 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE9D21F8700 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 01:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jd4YnUJJaiFv for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 01:41:28 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD2921F869F for <ietf@ietf.org>; Wed, 29 May 2013 01:41:24 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.129.170]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4T8cCdv007336 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 May 2013 01:38:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369816706; bh=OubnJn/UvvFiN0D8ZD/L3zw1I85oz4fHmkB6OvOM4sI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=f6Tdyn/+3OtHQ/1mBeWLg+a5I0NTWIV7tOge3E0kIKSEf1uZJRL05yt1DrDiZ7ZY1 NVmKeQVp1kH27NVxv83mH0FU993fQotRe2w2z+FcnToT7KMPKGbvQgSsNO6SD8G/JP D/xDNowYCxFZuXH/Q+QfIQNoTrTNRjs92dJuMYSw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1369816706; i=@elandsys.com; bh=OubnJn/UvvFiN0D8ZD/L3zw1I85oz4fHmkB6OvOM4sI=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aO6kOaeZL3weXw4HtDh8hFgVjQADYhRvD8PA1FJE9sCSnnkmN4l7GcV/GOJ3MDFsJ WebEt/j+35OwkAoGzB8L9Anio0swqO693UpZUOdU+CKBc2XOQKMl/CkMHOaLFcFvl4 LXz/biYZKBVJ/P6Q5MqMQRWXAwqdimVGDVKoDrlM=
Message-Id: <6.2.5.6.2.20130528232137.0c9d2818@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 May 2013 01:09:14 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: IETF Meeting in South America
In-Reply-To: <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel .com>
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com> <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com> <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com> <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: sistopefuni@gmail.com, Eric Burger <eburger@standardstrack.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, 29 May 2013 08:41:29 -0000

At 22:18 28-05-2013, GT RAMIREZ, Medel G. wrote:
>How about in the Philippines? I can show my homeland=85
>I can help facilitate the event, why don=92t you give it a try!

In the message that was quoted the person mentioned that:

   "I understand that usually the place is chosen based on the most of
    participant origin"

The person also mentioned explaining to students=20
that the IETF is open to them and that they can=20
participate.  I believe that the person will not=20
be explaining that incorrectly.

At 05:46 28-05-2013, Eric Burger wrote:
>Riiight. That is why one never has to attend an=20
>IETF meeting in person to serve on NOMCOM, one=20
>does not need travel support from one's employer=20
>to be on the IESG, and why people who never come=20
>to IETF meetings are the rule and not the=20
>exception with respect to getting documents adopted and published.

I wasn't unable to attend an IETF meeting some=20
time ago due to an administrative issue.  The=20
proposal I intended to discuss about (it was=20
discussed during a session) was not=20
adopted.  With hindsight I'll say that the=20
proposal would not have been adopted as I would=20
have made the mistake of not following IETF "culture".

Regards,
S. Moonesamy=20


From abdussalambaryun@gmail.com  Wed May 29 01:49:13 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5D2D21F9121 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 01:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DZDw8xlt+STq for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 01:49:13 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 2D46E21F911B for <ietf@ietf.org>; Wed, 29 May 2013 01:49:13 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id ma3so8927345pbc.2 for <ietf@ietf.org>; Wed, 29 May 2013 01:49:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rrlRQxXEBShGQtuDVio4rdmSMe3T5EZ3V5wekSSRfio=; b=wVBdYvSUjH5tCzkNxKhYo9dzDQwXgoQctu3sHeYUhu/BNYa69rlS02kzcMvvmSOtOY q/wluw2znT9NC/9ahxagfLFm4BvhYXX8fEHa89DYZPlrXT6L5eDuc5d2Skyk1qssli5s o3M+NCxW/QyEuKlYV2JGYuPtSuu0hBu7MJ8E6L8oi0GhBcXzZQneIJVqIesJFFsoqszd /NKW2dc++DNkUooqYwVhpbGF63VArWQCEmG40PlOC+H5BW2KfLdFEhrkgigkFzvMnnWt 5uQmVjS2YvuebaPZJKgng1YkrCojKXr0/1L0dR4XO/Lxtk/m/MRBbv3mVN6R4uZKx3ys VEnA==
MIME-Version: 1.0
X-Received: by 10.66.20.3 with SMTP id j3mr2359026pae.142.1369817352809; Wed, 29 May 2013 01:49:12 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 29 May 2013 01:49:12 -0700 (PDT)
In-Reply-To: <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com>
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com> <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com> <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com>
Date: Wed, 29 May 2013 10:49:12 +0200
Message-ID: <CADnDZ88=XPgdYES+DiFTKeTsghyDSBDNY0gZ5AZ1Dfr9_byBtQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: I rob <sistopefuni@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 08:49:13 -0000

Hello,

Thanks alot, we need people like you that tell others about IETF and
its real culture, or what they can do by using IETF. If
people/community can know what they can do, they will participate. Are
the IETF management contacting Internet Societies in South America
about participation, and what was the response? That information is
important to know if the meeting will make difference or not.

The IETF management need to do effort as well to encourage people like
you are doing. We need experts from South America to be involved and
we hope that IETF management contact the region's experts to encourage
participation. The experts then will reply to IETF management and tell
them their needs and ask to solve their problems of using IETF or
problems of participation. Most probably they have already tried but
left as I was always thinking to do but did not.

AB

On 5/29/13, I rob <sistopefuni@gmail.com> wrote:
> Hello,
>
> I agree with the Idea of a IETF meeting in South America.
>
> I think it is a way to let the people know about IETF (of course there are
> other ways, but this is a good one), to give the possibility to
> students/engineers with very good skills to get into the IETF, thinking
> that it is going to be published in universities in advance, to give time
> to students to enroll to a mailing list and read the drafts to be
> presented.
>
> Talking about my personal experience, I am pretty new in the IETF, but
> since I have been involved, I teach my students (from Argentina)  about it,
> I tell them, that they can participate, that is open, and I realize that
> they didn't know it.
>
> I understand that usually the place is chosen based on the most of
> participant origin, but I think a meeting in Latin America is a
> good opportunity to give the possibility to people from that region to know
> about the IETF.
>
> Kind Regards,
>
> Ines Robles.
>
> ------------------------------
>
> I would like to follow up on this proposal. Having a meeting in South
> America scheduled two or three years in advance will let us engage
> local organisations and individuals on a "project". We did several
> activities in the region trying to encourage IETF participation, but
> we're going to be much more effective if they're part of a plan with a
> strong commitment (and effort) from the IETF community.
>
> Since this opportunity was announced, there were several contacts and
> proposals from different groups asking for additional information,
> suggesting things to do, asking for details, etc. We now have a much
> more fertile ground to do multiple things.
>
>  Going further will also enrich the IETF work and community (making it
> more international becomes a side effect). In this region there are
> many engineers, software developers, people at Universities, etc. that
> could provide new ideas and energy to the IETF.
>
> Christian
>

From abdussalambaryun@gmail.com  Wed May 29 02:00:34 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A588721F9195 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 02:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mBA3X8+XvzaI for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 02:00:34 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9BD21F9180 for <ietf@ietf.org>; Wed, 29 May 2013 02:00:33 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id rr4so8956557pbb.20 for <ietf@ietf.org>; Wed, 29 May 2013 02:00:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gPkMFFfHCohRL1r3Rjr7Qj4fjqdn+zrSOvXEn+SLyxk=; b=ozrE5SJoLhNXxkmbCLXMmZg3ZDdSBquuok2B8LIEMdig9YB69HBZb1PEn2wTbmeyST UC+OxgJdXlS4VJvy+4oDUwollbawkPX8AQitkEISJGARDmQu0b8EFCRad17H1EWs/oai ZBEKNMhbrDKLY1bTFr0Y2kv2iefX7gRpCaQQGQ0AgQl6RAfqlrsjVRNZVML2TMQdfh+1 VsJbaTmyW/x+0g/Joyf6kvLd0m46GMYRhm/BmPi/uPg5XZGhm1SVxpbDFgOhSnv3ms1n /uJ1/AnRhiJfNUq+Rq7u/g5x0ALE2Q2c2ZKft0aMfXu8y3yfw6vZk67bQ6SLGRWrY7U3 2Uqw==
MIME-Version: 1.0
X-Received: by 10.68.176.197 with SMTP id ck5mr1769301pbc.165.1369818033807; Wed, 29 May 2013 02:00:33 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 29 May 2013 02:00:33 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130526221950.0c51c658@resistor.net>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <737D9439-A200-47C3-BE8B-6E6074CBD1F5@gmail.com> <51A23B7F.3050702@dcrocker.net> <6.2.5.6.2.20130526122352.0bc6e588@resistor.net> <CADnDZ889Wo_1fdF77W0yxnQAAKD=opr3ah4F-afzOfb5+MYQPg@mail.gmail.com> <6.2.5.6.2.20130526221950.0c51c658@resistor.net>
Date: Wed, 29 May 2013 11:00:33 +0200
Message-ID: <CADnDZ8-k10w8CdP0DNB4q_uOPnE5o6GufzcYogsKkbsnX3yXVg@mail.gmail.com>
Subject: Re: More participation from under-represented regions (was: IETF Meeting in South America)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 09:00:34 -0000

Hi SM

my answer to your reply,

On 5/27/13, SM <sm@resistor.net> wrote:
> Hi Abdussalam,
> At 16:38 26-05-2013, Abdussalam Baryun wrote:
>>I think they SHOULD have, and all of us should do the same, because
>>IETF will expand and become stronger by increasing participants from
>>ALL Internet community regions. The answers also based on IETF vesion.
>
> The question was about what was done in the past.  It is not about
> what the IESG or IAB is doing or could do in future.

Any done in past may need to change in future to cope with
Internet-world change. I can answer only for the present and future.
>
> At 16:51 26-05-2013, Abdussalam Baryun wrote:
>>There are some from Africa trying to find the way in, but they may not
>>mention it, however, training is not important much to make people
>>participate but the type of training and its period inside
>>organisation not outside. For example, I notice that there was one
>>African participant (not me), trying to participate in writing one
>>draft for the community, so was he/she encouraged by the WGs,
>
> Does that participant reside in Africa?  Will that participant
> implement the draft by writing code?

I think the draft was Informational, not for coding. The link below,
but I hope you are not the same author because is similar S.M. :-)

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

Regards
AB

From abdussalambaryun@gmail.com  Wed May 29 02:19:33 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E60121F922A for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 02:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id su8T2Gv1a5HT for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 02:19:32 -0700 (PDT)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id A459A21F9223 for <ietf@ietf.org>; Wed, 29 May 2013 02:19:32 -0700 (PDT)
Received: by mail-pb0-f41.google.com with SMTP id xb12so8967853pbc.0 for <ietf@ietf.org>; Wed, 29 May 2013 02:19:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fSuVgq+CkXg5Okzgci50fZCFoo/ZG7kFI8r8JS+snVg=; b=rUV22FXymxpoloz/IcL4qXKfNWtawhst1uPR2hYVRtMF6uyKnPbSd1klpe/dGIxnve PWfruC6dDS7t3EfSTitMQwkbH+8f55snJWpXTsJ2y6ZYEu49jb75AT5EV9Jbr+EQtxKN g/M+JPrchUDKtw0eGgEcTL6VX0AG6oknZNhRQtsQmocCeFkMH55QHExCA1hMcNFGLlzH T7FKOqgElt9U1O4CcMKxCF0+liUuyrhaVPvUQwnYEUAiiK4F0pRp9IcunX39ekmzAffZ 6G3PaMZWdk3g7g9UbLnRk1E+2vwH9PhBRjlhRoczN+F6E4UEvYK0WB/Ozlv2zlhv+MRh l/kw==
MIME-Version: 1.0
X-Received: by 10.66.20.3 with SMTP id j3mr2463872pae.142.1369819172324; Wed, 29 May 2013 02:19:32 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 29 May 2013 02:19:32 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20130528232137.0c9d2818@resistor.net>
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com> <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com> <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com> <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel.com> <6.2.5.6.2.20130528232137.0c9d2818@resistor.net>
Date: Wed, 29 May 2013 11:19:32 +0200
Message-ID: <CADnDZ88uAGOi_Vq2=sM8+j32iXnWSp5kZqcNeY1ZumiebHpm8Q@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 09:19:33 -0000

On 5/29/13, S Moonesamy <sm+ietf@elandsys.com> wrote:
> I wasn't unable to attend an IETF meeting some
> time ago due to an administrative issue.  The
> proposal I intended to discuss about (it was
> discussed during a session) was not
> adopted.  With hindsight I'll say that the
> proposal would not have been adopted as I would
> have made the mistake of not following IETF "culture".

I don't think I should follow the IETF culture to make my I-D adopted
by WG, but I may follow the good/technical reasons the WG provide. We
need to follow the technology/region/users needs for the Internet
purposes. The Internet is a global network that is present in all
regions, each region may have different needs and similar needs. So if
my document was not adopted by WGs, then there SHOULD be a good
technical reason (not that I did not follow cultures). I think that
IETF follows up with the Internet developers, users and participants
(within South America and others).

AB

From lars@netapp.com  Wed May 29 02:53:56 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 830F921F85BF for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 02:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.343
X-Spam-Level: 
X-Spam-Status: No, score=-10.343 tagged_above=-999 required=5 tests=[AWL=0.256, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1g8IluJw7t+2 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 02:53:51 -0700 (PDT)
Received: from mx1.netapp.com (mx1.netapp.com [216.240.18.38]) by ietfa.amsl.com (Postfix) with ESMTP id 78BC521F8FAF for <ietf@ietf.org>; Wed, 29 May 2013 02:53:51 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.87,763,1363158000"; d="scan'208";a="260732843"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx1-out.netapp.com with ESMTP; 29 May 2013 02:53:51 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r4T9rpTb011994; Wed, 29 May 2013 02:53:51 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.208]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Wed, 29 May 2013 02:53:50 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
Thread-Topic: Participation per Region of Authoring IETF documents vs Marketing
Thread-Index: AQHOWsKHbBwvdk4+NEOdlrhOvSI/ZJkZUCGAgAAso4CAACXKAIABs+SAgAEOOAA=
Date: Wed, 29 May 2013 09:53:50 +0000
Message-ID: <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com>
In-Reply-To: <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <6FB1A06ABD09FC499B79C9E76CC00E14@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 29 May 2013 09:53:56 -0000

Hi,

On May 28, 2013, at 19:46, Abdussalam Baryun <abdussalambaryun@gmail.com> w=
rote:
> by looking into the statistics of I-Ds and RFCs, it is strange that we ge=
t
> sometimes high rate in the I-D going in IETF from some regions but the
> success rate of I-Ds to become RFCs is very low (5- 50).

which IDs and RFCs are you basing this statement on?

Thanks,
Lars=

From jmamodio@gmail.com  Wed May 29 03:52:40 2013
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 1FEB221F9385 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 03:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SLB8Sr3QO2X for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 03:52:39 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 56D1321F909A for <ietf@ietf.org>; Wed, 29 May 2013 03:52:39 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id cz10so2044035veb.36 for <ietf@ietf.org>; Wed, 29 May 2013 03:52:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IFszceNYeOiupSUQxBd7IPnPuKOLACQ2TWVDJOW4/WE=; b=qCO4gdhrwMFyIfX769DpeHMxJ3pdo8LO+nEKG1h/RRrn0QMskxhq8eNIMXRum7ofQC 2iOszDrXH0rTnbqzG34UiIbDuka92VTM2IusAa2BvODkyGA3vY1HFazrcUO3Nxp3Oui7 cMmWoHnvV/x9kXxwHEYE2ZUIfSNUfoePfXKXEWWXkOeSMx6TeYzbtI/Xy1sOIpypwUpk vBRrh27uAWSPomaWX80Sw6niG5yMem8HAiX7k0Lhpc3fIIP6gR9IBK8JIaxYB7kK6ZYj 4l7kS1IFNs3UFHCJ7am/9tQBYJPDL+xJF35fJIVySA02PJ3fYZhT17VDVmx/GGxUG9Qa 9Z9Q==
MIME-Version: 1.0
X-Received: by 10.220.167.69 with SMTP id p5mr1097182vcy.57.1369824758314; Wed, 29 May 2013 03:52:38 -0700 (PDT)
Received: by 10.58.234.230 with HTTP; Wed, 29 May 2013 03:52:38 -0700 (PDT)
In-Reply-To: <985F3F2E-8BDF-4BCC-9D18-C8BADB0DDDB8@frobbit.se>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <985F3F2E-8BDF-4BCC-9D18-C8BADB0DDDB8@frobbit.se>
Date: Wed, 29 May 2013 05:52:38 -0500
Message-ID: <CAMzo+1aoHiswxs2o-e_B35qVtd2Kh_eWRRANTN-7aAM3L5hGHg@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Jorge Amodio <jmamodio@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=089e0149cf361fbda604ddd92e9f
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: Wed, 29 May 2013 10:52:40 -0000

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

ICANN constituencies, mission and participants are way different than IETF
and an important number of folks receive financial support to participate.

I believe the discussion is not really about if Buenos Aires is the right
location or not but if by meeting in a particular region that will drive
more engagement and participation from the people from that region.

-J



On Wed, May 29, 2013 at 1:34 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:

> ICANN 48 is to be held in Buenos Aires, Argentina, 17-21 November 2013,
> and I am looking forward to it!
>
>    Patrik
>
> On 29 maj 2013, at 04:27, Arturo Servin <aservin@lacnic.net> wrote:
>
> >       Perhaps not. Buenos Aires is also a big hub of technology in Lati=
n
> > America. In addition as it was mentioned it relatively close from Sao
> > Paulo, Montevideo and Santiago. Also there are direct flights from othe=
r
> > major cities in Peru and Colombia.
> >
> >       Going to Buenos Aires, Sao Paulo, Mexico City or Santiago will
> always
> > split audiences as these are the major tech hubs in the region (also ad=
d
> > Bogota, Lima, San Jose and other cities). So, I think it is not
> > comparable with Australia.
> >
> > as
> >
> > On 5/28/13 11:09 PM, Melinda Shore wrote:
> >> On 5/28/13 3:06 PM, l.wood@surrey.ac.uk wrote:
> >>> The centres for networking industry in Australia are Melbourne and
> Sydney, in that order.
> >>> It's a bit like IETF 51 being held in Grimsby, not London or Cambridg=
e.
> >>
> >> Okay.  So, should we be extrapolating from this to what
> >> we can expect from Brazilians if we meet in Buenos
> >> Aires?
> >>
> >> Melinda
> >>
>
>

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

<div dir=3D"ltr"><br><div style>ICANN constituencies, mission and participa=
nts are way different than IETF and an important number of folks receive fi=
nancial support to participate.</div><div style><br></div><div style>I beli=
eve the discussion is not really about if Buenos Aires is the right locatio=
n or not but if by meeting in a particular region that will drive more enga=
gement and participation from the people from that region.</div>
<div style><br></div><div style>-J</div><div style><br></div></div><div cla=
ss=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, May 29, 2013 =
at 1:34 AM, Patrik F=E4ltstr=F6m <span dir=3D"ltr">&lt;<a href=3D"mailto:pa=
f@frobbit.se" target=3D"_blank">paf@frobbit.se</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">ICANN 48 is to be held in Buenos Aires, Arge=
ntina, 17-21 November 2013, and I am looking forward to it!<br>
<br>
=A0 =A0Patrik<br>
<br>
On 29 maj 2013, at 04:27, Arturo Servin &lt;<a href=3D"mailto:aservin@lacni=
c.net">aservin@lacnic.net</a>&gt; wrote:<br>
<br>
&gt; =A0 =A0 =A0 Perhaps not. Buenos Aires is also a big hub of technology =
in Latin<br>
&gt; America. In addition as it was mentioned it relatively close from Sao<=
br>
&gt; Paulo, Montevideo and Santiago. Also there are direct flights from oth=
er<br>
&gt; major cities in Peru and Colombia.<br>
<div class=3D"im">&gt;<br>
&gt; =A0 =A0 =A0 Going to Buenos Aires, Sao Paulo, Mexico City or Santiago =
will always<br>
&gt; split audiences as these are the major tech hubs in the region (also a=
dd<br>
&gt; Bogota, Lima, San Jose and other cities). So, I think it is not<br>
&gt; comparable with Australia.<br>
&gt;<br>
</div>&gt; as<br>
<div class=3D"im">&gt;<br>
&gt; On 5/28/13 11:09 PM, Melinda Shore wrote:<br>
&gt;&gt; On 5/28/13 3:06 PM, <a href=3D"mailto:l.wood@surrey.ac.uk">l.wood@=
surrey.ac.uk</a> wrote:<br>
&gt;&gt;&gt; The centres for networking industry in Australia are Melbourne=
 and Sydney, in that order.<br>
&gt;&gt;&gt; It&#39;s a bit like IETF 51 being held in Grimsby, not London =
or Cambridge.<br>
&gt;&gt;<br>
&gt;&gt; Okay. =A0So, should we be extrapolating from this to what<br>
&gt;&gt; we can expect from Brazilians if we meet in Buenos<br>
&gt;&gt; Aires?<br>
&gt;&gt;<br>
</div>&gt;&gt; Melinda<br>
&gt;&gt;<br>
<br>
</blockquote></div><br></div>

--089e0149cf361fbda604ddd92e9f--

From john-ietf@jck.com  Wed May 29 04:19:26 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B88121F9298 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 04:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b+o2rTbFbkLF for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 04:19:20 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6482E21F928C for <ietf@ietf.org>; Wed, 29 May 2013 04:19:20 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UhePV-00024N-LR; Wed, 29 May 2013 07:19:17 -0400
Date: Wed, 29 May 2013 07:19:09 -0400
From: John C Klensin <john-ietf@jck.com>
To: George Michaelson <ggm@algebras.org>, l.wood@surrey.ac.uk
Subject: Re: IETF Meeting in South America
Message-ID: <08CA5DA78C79446B431AC8B6@JcK-HP8200.jck.com>
In-Reply-To: <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us>	<519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us>	<519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net>	<51A56C53.7070709@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk> <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@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@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 11:19:26 -0000

--On Wednesday, May 29, 2013 14:50 +1000 George Michaelson
<ggm@algebras.org> wrote:

> I went to Adelaide. it was my first IETF. I am now an IETF
> regular-irregular, of 10+ years standing. So, proof by
> example, it increased Australian participation by at least 1.
>...

I think that increasing IETF participation by you has certainly
been worthwhile for the IETF.  

We went to Australia in part because there was already a
significant base of Australian participation (as you point out).
Certainly the organization for which you work had others who
participated on a regular basis, so there should have been
significant support structure for your participation both before
and after your first meeting.  As I've said before, I think we
would be more than justified in going back to Australia and I
would try attend such a meeting.

Even those other factors were not relevant in your continued
participation, if one calculates the aggregate marginal cost to
other participants --in either money out of pocket or in
justifying additional travel expenses against tight budgets-- if
the key accomplishment directly associated with your meeting
there is adding you as a participant, you are a rather expensive
guy for the rest of us.

best,
    john


From john-ietf@jck.com  Wed May 29 04:31:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE9121F9374 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 04:31:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zvIKUGo83dQ0 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 04:31:40 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A07B521F9362 for <ietf@ietf.org>; Wed, 29 May 2013 04:31:40 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UhebT-00025A-SJ; Wed, 29 May 2013 07:31:39 -0400
Date: Wed, 29 May 2013 07:31:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
Subject: Re: IETF Meeting in South America
Message-ID: <1828658D04480D34F71BC801@JcK-HP8200.jck.com>
In-Reply-To: <985F3F2E-8BDF-4BCC-9D18-C8BADB0DDDB8@frobbit.se>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us>	<519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us>	<519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> ,	<51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <985F3F2E-8BDF-4BCC-9D18-C8BADB0DDDB8@frobbit.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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, 29 May 2013 11:31:46 -0000

--On Wednesday, May 29, 2013 08:34 +0200 Patrik =
F=C3=A4ltstr=C3=B6m
<paf@frobbit.se> wrote:

> ICANN 48 is to be held in Buenos Aires, Argentina, 17-21
> November 2013, and I am looking forward to it!

Patrik,

ICANN has taken on a formal obligation to meet regularly in
Latin America, sees significant obligation to "show the flag" in
precisely those places from which there is no participation,
maintains a professional staff for promotion of the
organization, and underwrites the costs of meeting attendance by
a rather large number of people as well as the costs of the
meetings themselves.   While I have no reason to expect any
problems in Buenos Aires, ICANN empirically cares less about
effective remote participation and working global Internet
connections from the meeting location than the IETF.   IIR,
ICANN met twice in Argentina while I was actively involved and
may have done so again since (in addition to meeting in other
parts of Latin America).  Most of those meetings worked out
well, a few were less satisfactory but, again, ICANN's goals,
constrains, and meeting success criteria are different from
those of the IETF.

Given the differences between ICANN and the IETF, this is
relevant how?  Perhaps we can use the ICANN meeting as a way to
promote remote and mailing list participation in the IETF of the
variety that would justify a meeting under our traditional
criteria for holding meetings in a country or region?

best,
    john


From paf@frobbit.se  Wed May 29 04:39:48 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E34321F93DA for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 04:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XE2OyBkIREYD for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 04:39:48 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 1196621F939E for <ietf@ietf.org>; Wed, 29 May 2013 04:39:48 -0700 (PDT)
Received: from [IPv6:2a02:80:3ffc::12] (unknown [IPv6:2a02:80:3ffc::12]) by mail.frobbit.se (Postfix) with ESMTPA id 0655821C94; Wed, 29 May 2013 13:39:47 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: IETF Meeting in South America
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <1828658D04480D34F71BC801@JcK-HP8200.jck.com>
Date: Wed, 29 May 2013 13:39:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FE979AB6-939B-4F40-81D1-4EFA60A609AA@frobbit.se>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us>	<519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us>	<519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> , <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <985F3F2E-8BDF-4BCC-9D18-C8BADB0DDDB8@frobbit.se> <1828 658D04480D34F71BC801@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
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, 29 May 2013 11:39:48 -0000

On 29 maj 2013, at 13:31, John C Klensin <john-ietf@jck.com> wrote:

> Given the differences between ICANN and the IETF, this is
> relevant how?

I was not clear enough on my response.

I see two things discussed:

1. Whether the organisation should "move around" and place meetings here =
and there.

There is, as many have said on the list and privately to me, many =
differences between the organisations on requirements on doing so.

2. Whether, given South America is chosen according to a proper =
selection according to (1), Buenos Aries was a good choice.

My comment was related to questions related to (2). That people felt =
uncomfortable traveling there.

I now understand my comment could be interpreted as if I felt it was =
important for IETF to go there. Sure, in general I think anything that =
can make IETF and other organisations do outreach is good. But for IETF, =
it is secondary. Quality of documents is much more important, and having =
local meetings might make documents less US/Western Europe centric in =
views related to various things. But of course not a primary goal as it =
is for ICANN (for example).

Btw, after not going to IETF for a while, I will come a few days to =
Berlin ;-)

   Patrik


From mariainesrobles@googlemail.com  Tue May 28 13:36:59 2013
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7994111E80D5 for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 13:36:59 -0700 (PDT)
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FhHMI3bhcbpy for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 13:36:55 -0700 (PDT)
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by ietfa.amsl.com (Postfix) with ESMTP id F18EF21F93E0 for <ietf@ietf.org>; Tue, 28 May 2013 13:36:54 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id hz10so5772360vcb.38 for <ietf@ietf.org>; Tue, 28 May 2013 13:36:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=uyeEyYmofCzdtoFQq+T9jUaEH3de8/jFPTHjqOyxW9U=; b=jP4P3am/trXgr+ZcVi8e2Ni0UtDagl8m5BB/jhPNZbZRfX3bbbPKz4xKv4pqXOpeXD WMR6kTZBQP2raIBAiexaZPSxgtBNYJv0JkmPnBnGD484i1x1tjsIMsQSL2aSMbs61S33 V3B+tHcRt+DshUimiB/HabP3v8Xu6twlgcSJsG963Hg9ztfD2PFeRO0nDv9FAVG+JTsj Hndx6KpMjnt3+rtUQH0NYAVc9FmhzpvXVvSqFwIvogflzY7DV2zRye/zrXDj9UUKNPiZ IK8KpmyJzs4DAqUWb1XXULpsQUHCzCIW057lo1KQnKYCwSO2pwiqQac1SCxO3ULWTYZv XJKg==
MIME-Version: 1.0
X-Received: by 10.220.223.14 with SMTP id ii14mr19161908vcb.50.1369773414157;  Tue, 28 May 2013 13:36:54 -0700 (PDT)
Received: by 10.220.177.135 with HTTP; Tue, 28 May 2013 13:36:53 -0700 (PDT)
Date: Tue, 28 May 2013 17:36:53 -0300
Message-ID: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com>
Subject: IETF Meeting in South America
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=14dae9cdc033c6155d04ddcd39b6
X-Mailman-Approved-At: Wed, 29 May 2013 08:01:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 20:36:59 -0000

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

Hello,

I agree with the Idea of a IETF meeting in South America.

I think it is a way to let the people know about IETF (of course there are
other ways, but this is a good one), to give the possibility to
students/engineers with very good skills to get into the IETF, thinking
that it is going to be published in universities in advance, to give time
to students to enroll to a mailing list and read the drafts to be presented.

Talking about my personal experience, I am pretty new in the IETF, but
since I have been involved, I teach my students (from Argentina)  about it,
I tell them, that they can participate, that is open, and I realize that
they didn't know it.

I understand that usually the place is chosen based on the most of
participant origin, but I think a meeting in Latin America is a
good opportunity to give the possibility to people from that region to know
about the IETF.

Kind Regards,

Ines Robles.

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

I would like to follow up on this proposal. Having a meeting in South
America scheduled two or three years in advance will let us engage
local organisations and individuals on a "project". We did several
activities in the region trying to encourage IETF participation, but
we're going to be much more effective if they're part of a plan with a
strong commitment (and effort) from the IETF community.

Since this opportunity was announced, there were several contacts and
proposals from different groups asking for additional information,
suggesting things to do, asking for details, etc. We now have a much
more fertile ground to do multiple things.

 Going further will also enrich the IETF work and community (making it
more international becomes a side effect). In this region there are
many engineers, software developers, people at Universities, etc. that
could provide new ideas and energy to the IETF.

Christian

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

Hello,<div><br></div><div>I agree with the Idea of a IETF meeting in South =
America.</div><div><br></div><div>I think it is a way to let the people kno=
w about IETF (of course there are other ways, but this is a good one), to g=
ive the possibility to students/engineers with very good skills to get into=
 the IETF, thinking that it is going to be published in universities in adv=
ance, to give time to students to enroll to a mailing list and read the dra=
fts to be presented.</div>
<div><br></div><div>Talking about my personal experience,=A0I am pretty new=
 in the IETF, but since I have been involved, I teach my students (from Arg=
entina) =A0about it, I tell them, that they can participate, that is open, =
and I realize that they=A0didn&#39;t know it.=A0=A0=A0</div>
<div><br></div><div>I understand that usually the place is=A0chosen=A0based=
 on the=A0most=A0of participant=A0origin, but I think a meeting in Latin Am=
erica is a good=A0opportunity=A0to give the possibility to people from that=
 region to know about the IETF.=A0</div>
<div><br></div><div>Kind Regards,</div><div><br></div><div>Ines Robles.</di=
v><div><br></div><div><div class=3D"gmail_quote">
------------------------------<br><br>
I would like to follow up on this proposal. Having a meeting in South<br>
America scheduled two or three years in advance will let us engage<br>
local organisations and individuals on a &quot;project&quot;. We did severa=
l<br>
activities in the region trying to encourage IETF participation, but<br>
we&#39;re going to be much more effective if they&#39;re part of a plan wit=
h a<br>
strong commitment (and effort) from the IETF community.<br>
<br>
Since this opportunity was announced, there were several contacts and<br>
proposals from different groups asking for additional information,<br>
suggesting things to do, asking for details, etc. We now have a much<br>
more fertile ground to do multiple things.<br>
<br>
=A0Going further will also enrich the IETF work and community (making it<br=
>
more international becomes a side effect). In this region there are<br>
many engineers, software developers, people at Universities, etc. that<br>
could provide new ideas and energy to the IETF.<br>
<br>
Christian<br><br></div></div>

--14dae9cdc033c6155d04ddcd39b6--

From mariainesrobles@googlemail.com  Tue May 28 14:17:45 2013
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF4421F92EC for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 14:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3e6IEDKvCSrM for <ietf@ietfa.amsl.com>; Tue, 28 May 2013 14:17:44 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 29A6121F881C for <ietf@ietf.org>; Tue, 28 May 2013 14:17:44 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id db10so4461867veb.40 for <ietf@ietf.org>; Tue, 28 May 2013 14:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=wFCtjjeQ4i0a4NlzL23sLENCbc3VUErypjdSKokpnyI=; b=kjjkdgCfHWMmDPiYLtjhwuA0x0HPJ2zREPrhsNnpYWb8BEp5Ygjjoutb7spAn2vQaz d3C2A/1zgyQrXsGX3ZY+puVv9ZKfQ+iiMWPgYiIQCjitlA0ydd7XJdxKM5JWE57Bew02 uPF2YXwKaxyexQa8UDRn+OmwH5yyh9Q66fPAPf/2p9laJGE/K56GD2bVHXfbmJ4eZKMb UufgxUgxSVS4bRnsXg86Lwn9a0re5Va/sZNK5hwbHttRh25O7DXEQ6KceZl3IU3rqfWa OVGny0diFgur9hmy2+G0aWGPHA/ZZqJbZ82uvPM5fsKD/WCndTqX9kEE6q9fN9RHulUk 1UNw==
MIME-Version: 1.0
X-Received: by 10.52.190.130 with SMTP id gq2mr16397504vdc.37.1369775863612; Tue, 28 May 2013 14:17:43 -0700 (PDT)
Received: by 10.220.177.135 with HTTP; Tue, 28 May 2013 14:17:43 -0700 (PDT)
Date: Tue, 28 May 2013 18:17:43 -0300
Message-ID: <CAP+sJUdmDEm36vNNbFW4mOjJq=Bh0C_rVFaDo8ZUib+n2BPm-A@mail.gmail.com>
Subject: financial fun with an IETF Meeting in South America
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e0122ee42c5cd3504ddcdcb05
X-Mailman-Approved-At: Wed, 29 May 2013 08:01:43 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 May 2013 21:17:45 -0000

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

Hello,



> I'd also say that I've never heard anyone making that sort of statement.
> For instance, the argentinan government itself has a program to increase
> Internet connectivity throughout the country --
>

 That is the web page of the program that Fernando mentions,
http://www.conectarigualdad.gob.ar/  (spanish ) - netbooks with windows and
Linux :)  for the kids -

>
> > His view is shared by many, so in the event IETF gets to meet in Buenos
> > Aires, if the meeting becomes public, don't be surprised to see some
> > coordinated political manifestation.
>
> I live in Argentina too, and people don't make political manifestation
about Internet topics. In opposite. In Mendoza (Arg.) we did a lot of
events (conferences, hands-on) for the people (no technical) about IPv6 and
they were very interested on it and the concurrence was high (200 people
:-))

Argentina is a beautiful place to know :-), have a lot of things to do, and
is always full of tourist during all the seasons.

Kind Regards,

Ines Robles.

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

<div class=3D"gmail_quote"><div>Hello,</div><div><br></div><div>=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
I&#39;d also say that I&#39;ve never heard anyone making that sort of state=
ment.<br>
For instance, the argentinan government itself has a program to increase<br=
>
Internet connectivity throughout the country --=A0<br></blockquote><div>=A0=
</div><div>=A0That is the web page of the program that Fernando mentions,=
=A0<a href=3D"http://www.conectarigualdad.gob.ar/">http://www.conectarigual=
dad.gob.ar/</a>=A0 (spanish ) - netbooks with windows and Linux :) =A0for t=
he kids -</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
&gt; His view is shared by many, so in the event IETF gets to meet in Bueno=
s<br>
&gt; Aires, if the meeting becomes public, don&#39;t be surprised to see so=
me<br>
&gt; coordinated political manifestation.<br><br></blockquote><div>I live i=
n Argentina too, and people don&#39;t make political manifestation about In=
ternet topics. In opposite. In Mendoza (Arg.) we did a lot of events (confe=
rences, hands-on) for the people (no technical) about IPv6 and they were ve=
ry=A0interested=A0on it and the concurrence was high (200 people :-))</div>
<div><br></div><div>Argentina is a beautiful=A0place=A0to know :-), have a =
lot of things to do, and is always full of tourist during all the seasons.<=
/div><div><br></div><div>Kind Regards,</div><div><br></div><div>Ines Robles=
.</div>
</div>

--089e0122ee42c5cd3504ddcdcb05--

From jari.arkko@piuha.net  Wed May 29 08:21:08 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3119C21F8233 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 08:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UzRXbySl2NiZ for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 08:21:03 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 758B321F8630 for <ietf@ietf.org>; Wed, 29 May 2013 08:20:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E4BFF2CC60; Wed, 29 May 2013 18:20:46 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gCJNuoVlvhlH; Wed, 29 May 2013 18:20:46 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E55452CC3C; Wed, 29 May 2013 18:20:45 +0300 (EEST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com>
Date: Wed, 29 May 2013 18:20:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4237401D-DBEE-4547-AB07-21B2D4BFA895@piuha.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
X-Mailer: Apple Mail (2.1503)
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, 29 May 2013 15:21:08 -0000

>> by looking into the statistics of I-Ds and RFCs, it is strange that =
we get
>> sometimes high rate in the I-D going in IETF from some regions but =
the
>> success rate of I-Ds to become RFCs is very low (5- 50).

There seems to be a general pattern where new participants first =
participate and/or produce IDs but it takes some time to produce RFCs. =
For instance, for a while it was the case that there was a growing =
number of proposals and participants from China, but it is only more =
recently that the RFC statistics reflect this (see the bright green line =
in http://www.arkko.com/tools/rfcstats/countrydistrhist.html). The =
hypothesis is that first of all, it takes a while to produce RFCs :-) =
and that new participants take a while before they get up to speed on =
the process, find enough other parties that share similar needs for the =
specific technical work, etc.

Jari


From john-ietf@jck.com  Wed May 29 08:35:37 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D2621F9234 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 08:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.562
X-Spam-Level: 
X-Spam-Status: No, score=-102.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydo5I24ZMYT9 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 08:35:32 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2F96321F8FDD for <ietf@ietf.org>; Wed, 29 May 2013 08:35:32 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UhiPO-0002NK-M6; Wed, 29 May 2013 11:35:26 -0400
Date: Wed, 29 May 2013 11:35:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
Message-ID: <BD3EC04B622B385D10DD2C3E@JcK-HP8200.jck.com>
In-Reply-To: <4237401D-DBEE-4547-AB07-21B2D4BFA895@piuha.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <4237401D-DBEE-4547-AB07-21B2D4BFA895@piuha.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 15:35:37 -0000

--On Wednesday, May 29, 2013 18:20 +0300 Jari Arkko
<jari.arkko@piuha.net> wrote:

> There seems to be a general pattern where new participants
> first participate and/or produce IDs but it takes some time to
> produce RFCs. For instance, for a while it was the case that
> there was a growing number of proposals and participants from
> China, but it is only more recently that the RFC statistics
> reflect this (see the bright green line in
> http://www.arkko.com/tools/rfcstats/countrydistrhist.html).
> The hypothesis is that first of all, it takes a while to
> produce RFCs :-) and that new participants take a while before
> they get up to speed on the process, find enough other parties
> that share similar needs for the specific technical work, etc.

I would add to that list the observation that, when complete
newcomers come to the IETF in order to propose some pet idea or
personal invention and get it standardized, the first I-Ds that
they submit often don't go anywhere because they propose a
networking model that is outside IETF scope, have serious
technical flaws the authors did not identify,  just are not of
interest to other members of the community, or are generally off
the wall for some other reason (such as requiring changes to
laws of physics or axiomatic definitions of mathematics).
Certainly not every proposal with which a newcomer arrives falls
into those categories -- some have been useful -- but it is
important to remember that there are substantive reasons why
I-Ds submitted within the first months of someone's
participation often have a lower acceptance rate as RFCs than
ones that come from more experienced participants.

I think there are important questions as to whether we handle
such proposals in a way that maximizes the odds of future
participation by those individuals and suspect we could do
better in that area.  But those are separate issues.

   john


From sm@elandsys.com  Wed May 29 09:07:58 2013
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 216B621F9590 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ySEsF7gkyKo for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:07:57 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F61721F9180 for <ietf@ietf.org>; Wed, 29 May 2013 09:07:55 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.155.215]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4TG7ZkE022173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 May 2013 09:07:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369843668; bh=HhiZsJwNGR3pATphXPX3+Kx+sv/IQX1Q9EnM0+wKlE8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bQsS2X7SP/YcG+q4d65Q6ge9zRfDz1sNySGMh5k7vcbMEFuIzMIf67vfOYvMaXZJL TvPcPhdr9PQY1tODBoTJvbx7KEr24Ltva3ce7LM6jkNiUwzz9nfwCCCmxMl6HwdlqU +FGGklTA8CvQ/Idm81KIVDO0BkxAKn4oBk1ro0cQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1369843668; i=@elandsys.com; bh=HhiZsJwNGR3pATphXPX3+Kx+sv/IQX1Q9EnM0+wKlE8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jBP39sFZ2nGMop/1gBww2aZBimgqYS1/xrH/4/CTtm4+p+tIjz6bWPHluEn4cgO/K 1FtLIry6oKZAUNkByhAN0nc482HvQnQ31IWlczY+ttziNCFaPTjnp9eWlFnMumk9AI ZAoB3J06af/sgSJNbahI8bCLNFcrQLm2wU152cVg=
Message-Id: <6.2.5.6.2.20130529083221.0efba520@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 May 2013 08:43:04 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF Meeting in South America (off-topic)
In-Reply-To: <CADnDZ88uAGOi_Vq2=sM8+j32iXnWSp5kZqcNeY1ZumiebHpm8Q@mail.g mail.com>
References: <CAP+sJUf6Jp+MvhuC0hzRLU4r+mX97JumbnKJo1ymi6vUFY-6Bg@mail.gmail.com> <CAP+sJUdc6UHLK+kQ8-L3FgUZ8+gSaA-sq2M2pUsvTPXjHhvELQ@mail.gmail.com> <CAKaL0mDoWUn9=RWG0Vwzz3pbEofECnXZ+8duMdjuoAV5G8u+7g@mail.gmail.com> <A5AD67DA1ACB9648831FD753485B2BFE21533A75@EXVSGT02.globetel.com> <6.2.5.6.2.20130528232137.0c9d2818@resistor.net> <CADnDZ88uAGOi_Vq2=sM8+j32iXnWSp5kZqcNeY1ZumiebHpm8Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 16:07:58 -0000

At 02:19 29-05-2013, Abdussalam Baryun wrote:
>I don't think I should follow the IETF culture to make my I-D adopted
>by WG, but I may follow the good/technical reasons the WG provide. We

If a working group does not show any interest in working on an I-D it 
is a good enough reason, in my opinion, for the I-D not to be adopted.

Regards,
S. Moonesamy 


From ajs@anvilwalrusden.com  Wed May 29 09:25:42 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A63F21F96C1 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ha0v19f5abrC for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:25:14 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E12E621F96B7 for <ietf@ietf.org>; Wed, 29 May 2013 09:25:13 -0700 (PDT)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 29D378A031 for <ietf@ietf.org>; Wed, 29 May 2013 16:25:07 +0000 (UTC)
Date: Wed, 29 May 2013 12:25:39 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to Proposed	Standard
Message-ID: <20130529162539.GJ34296@mx1.yitter.info>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m27gii3c1j.wl%randy@psg.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 16:25:42 -0000

On Wed, May 29, 2013 at 08:44:08AM +0900, Randy Bush wrote:

> but i think the draft in question has very serious privacy issues, and
> would like to focus on that, not characterization of the messengers.

The discussion in the security considerations of the -04 draft appears
to me to acknowledge there are potential privacy issues, and suggests
how to avoid them.  What more would you ask?

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From john-ietf@jck.com  Wed May 29 09:36:54 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D87921F9683 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:36:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWoFFkFSdadk for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:36:48 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C655B21F9545 for <ietf@ietf.org>; Wed, 29 May 2013 09:36:48 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UhjMj-0002SK-Pm; Wed, 29 May 2013 12:36:45 -0400
Date: Wed, 29 May 2013 12:36:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt>	(Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to	Proposed	Standard
Message-ID: <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com>
In-Reply-To: <20130529162539.GJ34296@mx1.yitter.info>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 16:36:54 -0000

--On Wednesday, May 29, 2013 12:25 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> On Wed, May 29, 2013 at 08:44:08AM +0900, Randy Bush wrote:
> 
>> but i think the draft in question has very serious privacy
>> issues, and would like to focus on that, not characterization
>> of the messengers.
> 
> The discussion in the security considerations of the -04 draft
> appears to me to acknowledge there are potential privacy
> issues, and suggests how to avoid them.  What more would you
> ask?

At the risk of saying that differently and partially channeling
Joe, would you care to propose specific text?  The sentences
added in -04 are partially mine. If I had been able to figure
out what else to say that would be stronger, constructive, and
not stray into Applicability Statement territory, I would have,
so I'm out of ideas and it is possible that Joe is too.

    john




From Ted.Lemon@nominum.com  Wed May 29 09:54:02 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E24D21F970A for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:54:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.504
X-Spam-Level: 
X-Spam-Status: No, score=-106.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXm4DzIqVzCG for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 09:53:49 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id C986A21F9704 for <ietf@ietf.org>; Wed, 29 May 2013 09:53:34 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUaYyiDavJDIh2FQALfxJP36nfCPL2WCH@postini.com; Wed, 29 May 2013 09:53:35 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 88CB51B81C7 for <ietf@ietf.org>; Wed, 29 May 2013 09:53:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 78B93190052; Wed, 29 May 2013 09:53:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 29 May 2013 09:53:28 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Thread-Topic: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Thread-Index: AQHOXIrBdwBO08II6EOxhnWJfQrk3Jkc1leA
Date: Wed, 29 May 2013 16:53:27 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com>
In-Reply-To: <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <CBDBC5BAF906A04185184CD9B158670B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 16:54:02 -0000

On May 29, 2013, at 12:36 PM, John C Klensin <john-ietf@jck.com> wrote:
> If I had been able to figure
> out what else to say that would be stronger, constructive, and
> not stray into Applicability Statement territory, I would have,
> so I'm out of ideas and it is possible that Joe is too.

Even if you don't have an applicability statement, I don't think it's inapp=
ropriate to talk about the context in which the documented protocol is inte=
nded to be useful, nor to talk about contexts in which it wouldn't be appro=
priate.   The document currently is far too restrained in this regard, IMHO=
.   I would add some text to the introduction, like this:

The DNS Resource Records described in this document have significant privac=
y implications (see section 8).   They were developed with the intention to=
 use them in [scenario a] or [scenario b] and are likely not to be appropri=
ate in other scenarios.   In particular, they are unlikely to be appropriat=
e for use in DNS zones hosted on globally-reachable servers that will answe=
r any query without any access control mechanism.

I realize this looks a lot like an applicability statement, but the problem=
 with putting an applicability statement in an Informational document is th=
at informational documents are never applicable in the sense of being the s=
tandard the IETF recommends to use in a specific case.   As long as you sta=
y away from _recommending_ the use of this specification, I think it's okay=
 to say where its use was envisioned.   Although of course if it was envisi=
oned to be used on the public internet, that wouldn't help.


From john-ietf@jck.com  Wed May 29 10:24:19 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D22A21F8E1C for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:24:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYWhZkWG74dG for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:24:02 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8698621F8F6D for <ietf@ietf.org>; Wed, 29 May 2013 10:24:01 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uhk6S-0002Vg-0P for ietf@ietf.org; Wed, 29 May 2013 13:24:00 -0400
Date: Wed, 29 May 2013 13:23:51 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: What do we mean when we standardize something?
Message-ID: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 17:24:20 -0000

Hi.  A number of recent discussions, specifically including the
Last Calls on DKIM and standardizing RRTYPEs and even to some
extent the meeting location ones, have started me thinking that
perhaps we need to review what business the IETF is actually in
and to be sure that we actually still agree about it.  The note
that follows is an attempt to take the isolated parts (and
symptoms) of that discussion up a level and discuss it as a
general issue.

The key issues go to the very nature of standardization.  While
there are many variations on each, there are two fundamentally
different models for what standards are about.  Each is
legitimate in its own way and each has its advocates, but they
are different.  One is a focus on quality: an engineering
consensus on the best technical solution given physics or
consensus goals and boundary conditions.  The other is
sometimes called "consensus of industry practice" in which a
standard reflects what is already deployed, possibly picking
among different implemented options in a few cases but mostly
requiring that a common model appears before standards are
issued.  

Two variations on the second theme were extremely common in the
earlier days of computer and telecommunciations standardization
but are less popular today (at least in theory) due to IPR and
antitrust concerns.  Both start with a single vendor (or closed
consortium) implementation.  That implementation might then be
offered for standardization (sometimes with a "no major
changes" restriction) and adopted more generally or endorsed by
traditional SDOs.  Or that single implementation might be
reverse-engineered by others and then the result treated as
common industry practice.

Despite the occasional claim that a strange (to me) idea called
"anticipatory standardization" is a variation on the second
model, that combination makes standards in the absence of, or
prior to, implementation and deployment an impossible
contradiction.  It is basically incompatible with innovation of
any type.

The IETF has traditionally chosen the first model and a great
deal of our thinking and public rhetoric are based on it. Even
when we have adopted proposals, sometimes implemented ones,
from elsewhere, we have insisted on change control and usually
taken that seriously.  One could claim that an adaptation of
the second model would make the Internet more uniform, but a
consensus of existing practice cannot aspire to "working
better" except in the narrow sense of substitutability of
conforming products.

It is interesting that the multi-stage model of RFC 2026
(particularly the original "Proposed Standard" definition), the
IEEE's "Trial-Use" standards (the current Section 5.7 of their
Standards Board Operations Manual,
http://standards.ieee.org/develop/policies/opman/sect5.html#5.7,
makes instructive reading), and ISO "Technical Specification"
all try to combine the two models by allowing a preliminary
specification --one that is intended for trial implementation
but not deployment-- to be designed on an engineering basis and
then standardized only when implementations exist and can be
compared (our original "Draft Standard").  In theory, only when
both an industry common practice and consensus about value
emerges does true standardization (including our original
definition for "Internet Standard") move forward.  We know how
well that has worked for us in practice.  While there have been
exceptions, I don't believe it has worked much better for other
SDOs.

If we are not going to move significantly in the direction of
"consensus of industry practice", then it seems to me that we
need to be careful about the arguments that are made (or at
least those that are considered legitimate) in support of
advancement into or on the standards track.  

For example, if we agree on a relaxed registration procedure
for some protocol parameters, it is not reasonable to later
turn around and ask that that those parameters be standardized,
unchanged, because they are already registered (and maybe
deployed).  For standardization, the IETF generally needs not
only change control but an opportunity to comment on and affect
the actual design and specification of whatever is being
standardized.  

Similarly, we sometimes hear it argued that we should accept a
specification for Proposed Standard unchanged because it has
been extensively developed and reviewed elsewhere.  That may be
reasonable in some cases although I'd hope we wouldn't make it
a common practice.  But, if a specification adopted for
Proposed Standard on that basis is then proposed for
advancement to Internet Standard, I think the review should be
comprehensive --perhaps even more comprehensive than the usual
such review-- because the Internet Standard is unambiguously an
IETF product and recommendation not that of the other body.  If
we allow a specification to advance to Proposed Standard
without an open and critical review because it was developed
and reviewed comprehensively by outside expert organizations
and then allow the Last Call review for Internet Standard to be
constrained by existing deployment, we would have gone into the
rubber stamping business that we regularly say is incompatible
with our standardization model.  That doesn't mean, of course,
that changes during review for Internet Standard are likely to
be a good idea.  Those who propose changes to the spec, and
especially to the protocol, should have to convince the
community that those changes are important enough to overcome
the costs, including those of incompatibility with deployed
versions.  But I don't think we can reasonably exclude them
from raising the issues and making those arguments.

thanks,
   john


From touch@isi.edu  Wed May 29 10:32:11 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDAFC21F8F27 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MF2DHemLaF7C for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:32:07 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 0362621F8E6E for <ietf@ietf.org>; Wed, 29 May 2013 10:32:06 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4THVSqd017428 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 10:31:28 -0700 (PDT)
Message-ID: <51A63B63.1090309@isi.edu>
Date: Wed, 29 May 2013 10:31:15 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com>
In-Reply-To: <51A512E8.6000801@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 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: Wed, 29 May 2013 17:32:12 -0000

This doc seems more useful as a section of an update to the TAO of the 
IETF. I agree with Brian that putting it forth as a separate document 
may give the unintended impression that this is the formal procedure.

Joe

On 5/28/2013 1:26 PM, Brian E Carpenter wrote:
> On 28/05/2013 21:32, Adrian Farrel wrote:
>> Hi,
>>
>> Dave Crocker and I have this little draft [1] discussing the process and considerations for creating formal working group drafts that are targeted for publication.
>>
>> We believe that this may help clarify some of the issues and concerns associated with this part of the process. We are targeting this as Informational (i.e. commentary on existing process, not new normative definition of process) and would like your input.
>>
>> What is not clear?
>> What have we got wrong?
>
> I haven't read the draft yet, and *before* I do so, I'd like to express
> some doubt whether we should even informally describe this using the
> word "process". It seems to me that it's each WG's prerogative how it
> does this; it has no impact on the standards process as a whole. The
> word "adopt" doesn't even occur in RFC 2418, and it is not used in
> the context of WG adoption in RFC 2026.
>
> In other words, I don't think this action is part of the standards process.
> It's WG folklore.
>
>     Brian
>
>> How should we resolve the remaining editor notes?
>>
>> Thanks,
>> Adrian
>> (per pro Dave)
>>
>> [1] http://www.ietf.org/internet-drafts/draft-crocker-id-adoption-02.txt
>>
>>
>> .
>>

From dhc@dcrocker.net  Wed May 29 10:36:24 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD5621F8F6E for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q+pI0nyWqMLU for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:36:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B8DBD21F8F4D for <ietf@ietf.org>; Wed, 29 May 2013 10:36:19 -0700 (PDT)
Received: from [173.255.178.233] (233.178.255.173.client.dyn.strong-mf8.as54203.net [173.255.178.233]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4THaAhP009823 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 10:36:16 -0700
Message-ID: <51A63C85.7000604@dcrocker.net>
Date: Wed, 29 May 2013 19:36:05 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu>
In-Reply-To: <51A63B63.1090309@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 29 May 2013 10:36:18 -0700 (PDT)
Cc: adrian@olddog.co.uk, 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, 29 May 2013 17:36:24 -0000

On 5/29/2013 7:31 PM, Joe Touch wrote:
> This doc seems more useful as a section of an update to the TAO of the
> IETF. I agree with Brian that putting it forth as a separate document
> may give the unintended impression that this is the formal procedure.


Nevermind that it isn't standards track or BCP and that it says quite 
explicitly that it isn't normative?

Just the mere fact that it's a "separate" document will somehow impart 
and implication of official normativeness?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From melinda.shore@gmail.com  Wed May 29 10:38:27 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C305421F8FEB for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.333
X-Spam-Level: 
X-Spam-Status: No, score=-2.333 tagged_above=-999 required=5 tests=[AWL=0.266,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PAABFd+JcLCP for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:38:21 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id D96F421F8F62 for <ietf@ietf.org>; Wed, 29 May 2013 10:38:19 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id u11so9186687pdi.36 for <ietf@ietf.org>; Wed, 29 May 2013 10:38:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ZKeX59p+hyMHTrl3SBv+6oVCaWnXDsvv3gZ8vu89y6g=; b=x8ErMWQy7GLumlHgxGiA7TscI5pJoRB9YCHP3IB0K0JbGdrWnx+a+2Yc8Xuy6NBkRD xo9jX+Uuf9zvgsnxdPvW7qudXwJjAReE4R2Hcoy2qJ9XX0M8Y1gKT0ecZrAH26ZBGMk0 bIXSRRSew6FwzHtwfzE2+CiBTHQxVELyyO6D8X8GmFCydW9aAhavFcLsCln2MJb1W0st eFnYuuY8X9Zr2lsfrRk4nnKN7Rbctsot+1AvKKfv/dneKtaFuVPj7cbkbEFdwGKOx7oO Oy7u6e6F3WlQ4IabTszBqwVwRGPxMOu8B52WduM2a9SxVRL7SLOyN8P8+uaGvzbwXWDh 9XYA==
X-Received: by 10.66.232.164 with SMTP id tp4mr4545063pac.39.1369849099646; Wed, 29 May 2013 10:38:19 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id bs2sm40704677pad.17.2013.05.29.10.38.17 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 10:38:18 -0700 (PDT)
Message-ID: <51A63D08.8080406@gmail.com>
Date: Wed, 29 May 2013 09:38:16 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: What do we mean when we standardize something?
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>
In-Reply-To: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 17:38:28 -0000

I think this is one of the best discussions of what we're
about that I've seen anywhere, and I'm grateful to John
for working this through.

One thing I'd like to take up further is this:

On 5/29/13 9:23 AM, John C Klensin wrote:
> Similarly, we sometimes hear it argued that we should accept a
> specification for Proposed Standard unchanged because it has
> been extensively developed and reviewed elsewhere.  That may be
> reasonable in some cases although I'd hope we wouldn't make it
> a common practice.  But, if a specification adopted for
> Proposed Standard on that basis is then proposed for
> advancement to Internet Standard, I think the review should be
> comprehensive --perhaps even more comprehensive than the usual
> such review-- because the Internet Standard is unambiguously an
> IETF product and recommendation not that of the other body. 

I'd actually much prefer to see these go to informational, if
they're to be published.  Otherwise I agree - if something's going
to be an IETF standard it needs to go through the IETF standards
development review and revision process, which is probably not
what the authors want.

Melinda


From stpeter@stpeter.im  Wed May 29 10:42:21 2013
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD0421F9234 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:42:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8AwKPxmQrFr for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:42:15 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 1331D21F93E9 for <ietf@ietf.org>; Wed, 29 May 2013 10:42:15 -0700 (PDT)
Received: from ergon.local (unknown [128.107.239.235]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 695114115C; Wed, 29 May 2013 11:55:00 -0600 (MDT)
Message-ID: <51A63DF1.90904@stpeter.im>
Date: Wed, 29 May 2013 11:42:09 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: What do we mean when we standardize something?
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com> <51A63D08.8080406@gmail.com>
In-Reply-To: <51A63D08.8080406@gmail.com>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 17:42:21 -0000

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

On 5/29/13 11:38 AM, Melinda Shore wrote:
> I think this is one of the best discussions of what we're about
> that I've seen anywhere, and I'm grateful to John for working this
> through.
> 
> One thing I'd like to take up further is this:
> 
> On 5/29/13 9:23 AM, John C Klensin wrote:
>> Similarly, we sometimes hear it argued that we should accept a 
>> specification for Proposed Standard unchanged because it has been
>> extensively developed and reviewed elsewhere.  That may be 
>> reasonable in some cases although I'd hope we wouldn't make it a
>> common practice.  But, if a specification adopted for Proposed
>> Standard on that basis is then proposed for advancement to
>> Internet Standard, I think the review should be comprehensive
>> --perhaps even more comprehensive than the usual such review--
>> because the Internet Standard is unambiguously an IETF product
>> and recommendation not that of the other body.
> 
> I'd actually much prefer to see these go to informational, if 
> they're to be published.  Otherwise I agree - if something's going 
> to be an IETF standard it needs to go through the IETF standards 
> development review and revision process, which is probably not what
> the authors want.

/me wonders if we need a separate series for informational documentation

Peter

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRpj3xAAoJEOoGpJErxa2pAiYP/jvIR0UI55/HBq4wUeGW4rWJ
LXJLvEpxuKZL056F6cNFajksDlOVyL3oknHacc7OKPt+3d8ClXyQTzisAsjzxYdT
XyQynTk0x0AmyFTvwDQ99HnPnpe+FJoBBdPvKM0KXvrGSDLQQviPvgBol/J/jBrz
fBGq/sf/qDRbuORDyK30Dr9g3iDPvuWtz8umVGKZVH0NU0SuWcBx+UqZlMxYDh62
T4X/HZXWEHcooGviiTLfpMRi+wzWJc16OlRW9Ncq1DwgITFXAuDchp5xmXoP20Q2
DU6K+pqCGZpO/AU2XBH72pno7cwi92nZPatAVhvNnwuC3IrtwcACH/mEvf6LJZ7q
B1ZmlMuhNA22Bu1lyLBzvJ/udwK84wtiCV64QGRnY5fzTxP3j8E00BjabjBMdkKM
ctwNaYI9JplVKUiW2NdOBVlsDwVYKpEBXNcZGPP4BmaaO9BFhUnK21heyD+TNf+o
gUC10MOkOLgByKN21EFMc8VTNettZLSM90MlOx06ToN/xaAL5Cgh0Qn18nvIisxg
IMCfEdTSdsxlBNgD01X/6MNBTzb6gFVS7nRm74UX4R+HA9eTrBhB1BYx6y4PhVhY
UOPVZkNuHngjth21TM3U62UZdIgT/AWZ/EvVFQFlTuB25vLXOV7tVfWbWa/FW4AT
6rgPVAQbyPvJZm4kSX7R
=sjcp
-----END PGP SIGNATURE-----

From paul.hoffman@vpnc.org  Wed May 29 10:44:42 2013
Return-Path: <paul.hoffman@vpnc.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 19F3021F941D for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8CyaiulR2i+c for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:44:41 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1E17A21F9410 for <ietf@ietf.org>; Wed, 29 May 2013 10:44:41 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4THiXf2023059 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 10:44:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: When to adopt a WG I-D
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51A63C85.7000604@dcrocker.net>
Date: Wed, 29 May 2013 10:44:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCFEC07C-78DA-478C-BCAE-BED12C3B019A@vpnc.org>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1503)
Cc: adrian@olddog.co.uk, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 17:44:42 -0000

On May 29, 2013, at 10:36 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 5/29/2013 7:31 PM, Joe Touch wrote:
>> This doc seems more useful as a section of an update to the TAO of =
the
>> IETF. I agree with Brian that putting it forth as a separate document
>> may give the unintended impression that this is the formal procedure.
>=20
>=20
> Nevermind that it isn't standards track or BCP and that it says quite =
explicitly that it isn't normative?
>=20
> Just the mere fact that it's a "separate" document will somehow impart =
and implication of official normativeness?

Yes. We even have that problem with the Tao itself.

--Paul Hoffman=

From touch@isi.edu  Wed May 29 10:45:13 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FACE21F9007 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFGYS+XZ9ZIz for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:45:06 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5241E21F947C for <ietf@ietf.org>; Wed, 29 May 2013 10:44:58 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4THgxtm021806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 10:42:59 -0700 (PDT)
Message-ID: <51A63E15.8070704@isi.edu>
Date: Wed, 29 May 2013 10:42:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net>
In-Reply-To: <51A63C85.7000604@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 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: Wed, 29 May 2013 17:45:13 -0000

On 5/29/2013 10:36 AM, Dave Crocker wrote:
> On 5/29/2013 7:31 PM, Joe Touch wrote:
>> This doc seems more useful as a section of an update to the TAO of the
>> IETF. I agree with Brian that putting it forth as a separate document
>> may give the unintended impression that this is the formal procedure.
>
> Nevermind that it isn't standards track or BCP and that it says quite
> explicitly that it isn't normative?

Yes, nevermind that. ;-)

> Just the mere fact that it's a "separate" document will somehow impart
> and implication of official normativeness?

Yes, to some - especially newbies who don't know the process. Except 
that's exactly whom you're trying to reach.

Consider yourself a newbie who has been told that the TAO gives all the 
informal information on how the IETF works. Then you find out about this 
doc. Wouldn't you wonder why it was treated separately? Was it that 
important? Was it not informal enough for the TAO?

There's a lot of nuance here, but overall, I said what I meant - it 
would give the *unintended* *impression* of something beyond what I 
think is the goal.

Joe

From dhc@dcrocker.net  Wed May 29 10:52:19 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2744321F871D for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oL4QYEjFK9Q8 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:52:14 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 74F0821F8FAF for <ietf@ietf.org>; Wed, 29 May 2013 10:52:13 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4THq5HQ010387 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 10:52:10 -0700
Message-ID: <51A6403F.8010206@dcrocker.net>
Date: Wed, 29 May 2013 19:51:59 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu>
In-Reply-To: <51A63E15.8070704@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 29 May 2013 10:52:12 -0700 (PDT)
Cc: adrian@olddog.co.uk, 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, 29 May 2013 17:52:19 -0000

On 5/29/2013 7:42 PM, Joe Touch wrote:
> Yes, to some - especially newbies who don't know the process. Except
> that's exactly whom you're trying to reach.
>
> Consider yourself a newbie who has been told that the TAO gives all the
> informal information on how the IETF works.

OK.  So your premise is that someone has been given seriously flawed 
guidance and based on that we need to fear their misunderstanding of things?

As a rule, the analytic template "somebody somewhere said something 
wrong or critical or otherwise problematic..." is a very, very poor 
basis for making policy.

For any interesting topic and any possible misstatement or criticism, 
there is certain to be someone, somewhere that suffers from having heard 
or said it.

Unless your view is that we must never do anything, let's instead try to 
look at the merits of what exists and how it is seen by reasonable 
people who are being reasonable, rather than make policy decisions on 
the hypothetical of a stray distortion.


> There's a lot of nuance here,

There is no nuance at all in this document.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From touch@isi.edu  Wed May 29 11:00:14 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B64021F8CA5 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGW7WvZlO2CD for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 10:59:31 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 3348621F8D31 for <ietf@ietf.org>; Wed, 29 May 2013 10:58:23 -0700 (PDT)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r4THvuFv027245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 10:57:56 -0700 (PDT)
Message-ID: <51A64196.4030100@isi.edu>
Date: Wed, 29 May 2013 10:57:42 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net>
In-Reply-To: <51A6403F.8010206@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 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: Wed, 29 May 2013 18:00:14 -0000

On 5/29/2013 10:51 AM, Dave Crocker wrote:
> On 5/29/2013 7:42 PM, Joe Touch wrote:
>> Yes, to some - especially newbies who don't know the process. Except
>> that's exactly whom you're trying to reach.
>>
>> Consider yourself a newbie who has been told that the TAO gives all the
>> informal information on how the IETF works.
>
> OK.  So your premise is that someone has been given seriously flawed
> guidance and based on that we need to fear their misunderstanding of
> things?

My premise is that when introducing people to a new game, it makes sense 
to keep things simple and in one place p the TAO.

You can continue to disagree with that if you prefer.

Joe

From ron.even.tlv@gmail.com  Wed May 29 11:14:13 2013
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 94EED21F9686; Wed, 29 May 2013 11:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQoO4XwlAqfj; Wed, 29 May 2013 11:14:08 -0700 (PDT)
Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) by ietfa.amsl.com (Postfix) with ESMTP id 3771821F95E9; Wed, 29 May 2013 11:14:08 -0700 (PDT)
Received: by mail-ee0-f42.google.com with SMTP id c50so5573387eek.1 for <multiple recipients>; Wed, 29 May 2013 11:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=3pPRFEuv6RRkhh3an83LeYSSpS7VOA92zVmLKiZR3hY=; b=iGjY3Lzz3/vdisLY/HX7hI3elTMRPG/dK0aAeBjFdI9+upsYq+Zg+DPyDwUjyKWsdV SkXBEyOSSYkM3RQDiBpWqyPLjSujMs89sCxOSxtQMr2VkQ/1blRoZZaW9Tp/70QtxS5O G6rqS+tXk9uBQfYCHjw70k9DjpQc/TZE+cUNp6lSq4ZKYogkpL1RgntWP+ZekkC+pFKv I7ud68O5ezvucY+tWvzU3lWD+Untwx94Aj6E8UJKMUjq88yD4e8V1YPhFsWEDTmj0JFk mAhY51c7mde3/si7LPeRxVwNOkFxnpV6aBONVh7SNjRZRXAhtb0MuHdsUU1YdCPN6n+Q kUuQ==
X-Received: by 10.15.43.203 with SMTP id x51mr4207577eev.144.1369851247195; Wed, 29 May 2013 11:14:07 -0700 (PDT)
Received: from RoniE (bzq-79-181-165-179.red.bezeqint.net. [79.181.165.179]) by mx.google.com with ESMTPSA id g7sm55758403eew.15.2013.05.29.11.14.04 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 29 May 2013 11:14:06 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Date: Wed, 29 May 2013 21:12:57 +0300
Message-ID: <000301ce5c98$278d0220$76a70660$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CE5CB1.4CDAFD70"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac5cmCWECo5bIU14RKqGyok1y70zYA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 18:14:13 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0004_01CE5CB1.4CDAFD70
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-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013-5-29

IETF LC End Date: 2013-6-4

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

1.       I can understand from the draft that when you have IP and PSTN
nettype it is requires that the ccap will be for the PSTN. What happens if
you want to have the ccap nettype as ATM to be used with IP in the c=

 

 

Nits/editorial comments:

 


------=_NextPart_000_0004_01CE5CB1.4CDAFD70
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:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 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;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New","serif"'>draft-ietf-mmusic-sdp-miscellaneous-caps-05</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:2013&#8211;5&#8211;29<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: 2013-6&#8211;4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as Standard track =
RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 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"'>I can =
understand from the draft that when you have IP and PSTN nettype it is =
requires that the ccap will be for the PSTN. What happens if you want to =
have the ccap nettype as ATM to be used with IP in the =
c=3D<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0004_01CE5CB1.4CDAFD70--


From aservin@lacnic.net  Wed May 29 11:40:25 2013
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 A761521F9263 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 11:40:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hIThuFwd0JLL for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 11:40:25 -0700 (PDT)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 0967021F8EC1 for <ietf@ietf.org>; Wed, 29 May 2013 11:40:24 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local (unknown [IPv6:2001:13c7:7001:7000:f8:4633:411a:bf]) by mail.lacnic.net.uy (Postfix) with ESMTP id 90E7630843C; Wed, 29 May 2013 15:40:08 -0300 (UYT)
Message-ID: <51A64B99.3010408@lacnic.net>
Date: Wed, 29 May 2013 15:40:25 -0300
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu>
In-Reply-To: <51A64196.4030100@isi.edu>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=UTF-8
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: adrian@olddog.co.uk, 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, 29 May 2013 18:40:25 -0000

	You can always include add some text from this document in the TAO and
add a reference so anybody wanting to know more could follow.

	Also, to me, this I+D also targets new and not so new WG chairs, not
just new comers.

	
.as


On 5/29/13 2:57 PM, Joe Touch wrote:
> 
> 
> On 5/29/2013 10:51 AM, Dave Crocker wrote:
>> On 5/29/2013 7:42 PM, Joe Touch wrote:
>>> Yes, to some - especially newbies who don't know the process. Except
>>> that's exactly whom you're trying to reach.
>>>
>>> Consider yourself a newbie who has been told that the TAO gives all the
>>> informal information on how the IETF works.
>>
>> OK.  So your premise is that someone has been given seriously flawed
>> guidance and based on that we need to fear their misunderstanding of
>> things?
> 
> My premise is that when introducing people to a new game, it makes sense
> to keep things simple and in one place p the TAO.
> 
> You can continue to disagree with that if you prefer.
> 
> Joe

From dhc@dcrocker.net  Wed May 29 11:57:03 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAF621F9223 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 11:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qKlCP2vpvkIM for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 11:56:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BAF8D21F9590 for <ietf@ietf.org>; Wed, 29 May 2013 11:56:54 -0700 (PDT)
Received: from [173.255.178.203] (203.178.255.173.client.dyn.strong-mf8.as54203.net [173.255.178.203]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4TIukRW012138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 11:56:51 -0700
Message-ID: <51A64F68.10401@dcrocker.net>
Date: Wed, 29 May 2013 20:56:40 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu>
In-Reply-To: <51A64196.4030100@isi.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 29 May 2013 11:56:53 -0700 (PDT)
Cc: adrian@olddog.co.uk, 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, 29 May 2013 18:57:03 -0000

On 5/29/2013 7:57 PM, Joe Touch wrote:
>
> My premise is that when introducing people to a new game, it makes sense
> to keep things simple and in one place p the TAO.
>
> You can continue to disagree with that if you prefer.


I haven't disagreed with doing that.  I disagreed with saying that that 
document contains everything they need to know.

Entirely different semantics to the two statements.

I think it's a dandy starting document.  But it's a really crappy 'last' 
document.

And by the way, the draft that's been put forward isn't just for 
beginners...

d/

ps.  The real consideration was whether to try to folk this draft into 
Working Group Guidelines and Procedures.  I think that idea actually has 
some reasonable logic to it; but it doesn't have enough benefit to be 
worth the effort of opening up WGG&P a third time, for now.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jabley@hopcount.ca  Wed May 29 12:34:50 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C045B21F9806 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 12:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTgUNp6LvjmT for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 12:34:50 -0700 (PDT)
Received: from mail-qc0-x236.google.com (mail-qc0-x236.google.com [IPv6:2607:f8b0:400d:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 11FB221F9805 for <ietf@ietf.org>; Wed, 29 May 2013 12:34:49 -0700 (PDT)
Received: by mail-qc0-f182.google.com with SMTP id n1so4905714qcw.41 for <ietf@ietf.org>; Wed, 29 May 2013 12:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=references:from:mime-version:in-reply-to:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=OtcpyABkLBwtjy2JFq8zFCYYSs6mRakcpfQVdQt32zY=; b=jE9AC5yZKIuTqW63YKmDF3BxlIcYkadGzLNOrFOYmDSUS7FcQ/A2S+RqZrtG/x5Fqg sWKQoCWz28Z15PaDIRNW2XFcvVwuHU5lOQW2bMAist7GDvsNZyMyz4WTXxUEnaWQm1wG oMJKB0rQ3f0DL05o4adTO50ig3oDj9Ilsz2wk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:from:mime-version:in-reply-to:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=OtcpyABkLBwtjy2JFq8zFCYYSs6mRakcpfQVdQt32zY=; b=HHmiKlc6J7+MSY7X+S38BYjGatlieuHnxGMlYv7Glm+hwbxkacqxWdvL1SZdBsrUDp C4JjfShubGPJuyLKlOECD25AwMFzr8PhgnRRxxO5dS/Jzs83XGn/O3+GtlTpS7tYV1xm 9J9Hh/swhCdl3ddBc6CuTbLbvD/2UaJxaKuQFYcMkhaLi/EULDaSviGeyNdFUd+Ddz+T pa+OtAEGVLsvqz00jxbjHPcYXac/Kx5sMuly3KTnf3M76ygmU52H7PIunD375Sw0hS6F +P2yGmRqkniRZ3lmgsAawzhnpxdRm/WAxL5qSyucchsVEAShSefnhzWDi/MGI6tlTGW/ e6rA==
X-Received: by 10.224.37.198 with SMTP id y6mr4477811qad.83.1369856089389; Wed, 29 May 2013 12:34:49 -0700 (PDT)
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com>
From: Joe Abley <jabley@hopcount.ca>
Mime-Version: 1.0 (1.0)
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com>
Date: Wed, 29 May 2013 12:34:51 -0700
Message-ID: <6651082245453285571@unknownmsgid>
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlW14HrqOp14fWHZYgtLF8enjKXXTGji9dysMfyWgsKGYsgFaq0xSt5h8PXvNhC7glwfL9/
Cc: John C Klensin <john-ietf@jck.com>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 19:34:50 -0000

Hi Ted,

On 2013-05-29, at 9:54, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On May 29, 2013, at 12:36 PM, John C Klensin <john-ietf@jck.com> wrote:
>> If I had been able to figure
>> out what else to say that would be stronger, constructive, and
>> not stray into Applicability Statement territory, I would have,
>> so I'm out of ideas and it is possible that Joe is too.
>
> Even if you don't have an applicability statement, I don't think it's ina=
ppropriate to talk about the context in which the documented protocol is in=
tended to be useful, nor to talk about contexts in which it wouldn't be app=
ropriate.   The document currently is far too restrained in this regard, IM=
HO.   I would add some text to the introduction, like this:
>
> The DNS Resource Records described in this document have significant priv=
acy implications (see section 8).   They were developed with the intention =
to use them in [scenario a] or [scenario b] and are likely not to be approp=
riate in other scenarios.   In particular, they are unlikely to be appropri=
ate for use in DNS zones hosted on globally-reachable servers that will ans=
wer any query without any access control mechanism.

I don't have an objection to adding text along those lines, and I
understand your reasoning.

Would this address the concerns of others who find the draft alarming?


Joe

From touch@isi.edu  Wed May 29 12:50:37 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D94721F8952 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 12:50:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.939
X-Spam-Level: 
X-Spam-Status: No, score=-102.939 tagged_above=-999 required=5 tests=[AWL=-0.340, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L+Cd9CK80H67 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 12:50:30 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id DF21E21F8EAD for <ietf@ietf.org>; Wed, 29 May 2013 12:50:28 -0700 (PDT)
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 r4TJo388024085 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 May 2013 12:50:03 -0700 (PDT)
Message-ID: <51A65BDD.8040304@isi.edu>
Date: Wed, 29 May 2013 12:49:49 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net>
In-Reply-To: <51A64F68.10401@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: 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: Wed, 29 May 2013 19:50:38 -0000

On 5/29/2013 11:56 AM, Dave Crocker wrote:
> On 5/29/2013 7:57 PM, Joe Touch wrote:
>>
>> My premise is that when introducing people to a new game, it makes sense
>> to keep things simple and in one place p the TAO.
>>
>> You can continue to disagree with that if you prefer.
>
> I haven't disagreed with doing that.  I disagreed with saying that that
> document contains everything they need to know.

Agreed, but if we have more to say, it would be useful to keep it in a 
single place - esp. given we have that vehicle for doing so.

> Entirely different semantics to the two statements.
>
> I think it's a dandy starting document.  But it's a really crappy 'last'
> document.

Good reason to make it better, rather than fracturing that sort of info, 
though.

> And by the way, the draft that's been put forward isn't just for
> beginners...

Nor is the TAO, AFAICT, either.

Joe


From dave@cridland.net  Wed May 29 13:05:09 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 889C221F967B for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 13:05:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.477
X-Spam-Level: 
X-Spam-Status: No, score=-2.477 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cGGToKmfxfXd for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 13:05:00 -0700 (PDT)
Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE6A21F9678 for <ietf@ietf.org>; Wed, 29 May 2013 13:04:59 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id t10so9540774lbi.18 for <ietf@ietf.org>; Wed, 29 May 2013 13:04:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pH2W48qmz2oT36sdnaQwTNe2rRONvmWnca7kXSlZdWE=; b=if02uWgcU0iAxx2yttIrtdKyDbpW52FxIQ8oFUe0jpsY9gcqY2HWJBBRT38VgtAslJ WZsLmwsKUNTpnCAF7obBLjaNod0zvzjUfIUXaxUso+e/IVLyVLdxYetK2eCGyAA6h3RJ nKCx2BEMXuW9aFoedUYascGRFA2p2V/e0smcg=
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=pH2W48qmz2oT36sdnaQwTNe2rRONvmWnca7kXSlZdWE=; b=SAOjVzux8VDDECRtvJh2pSMEO8fj/sE4rGOAKcsjpeyPqBQaP6rTKNPje7ittdzK58 JcezBvy6uPZnYNg4gEjSdTkuzJiBI3HGFEyQcyBKr1vEM2BJvWZDfJ12jhOLibogL59C 38XWOCaKScmlCmUNiT0wLLD5mh0C+wAMTxfv6rQaPh2jzJNsJiIaaMFOucIt6yvHK28t pJ8ZhhkNRhNd6R9SwFHEuelTFXWBvXd8jqsgpGyq4OB5vHo36krBZJtHy5C4+md67DLz AlFqVuxYwAfsd/2b3tis8WaImehtfCyRPYi2D5QeY5tsholeVCCx+l9DZAuH6+3kyZSp eTKA==
MIME-Version: 1.0
X-Received: by 10.112.18.164 with SMTP id x4mr2306726lbd.127.1369857897727; Wed, 29 May 2013 13:04:57 -0700 (PDT)
Received: by 10.114.160.199 with HTTP; Wed, 29 May 2013 13:04:57 -0700 (PDT)
Received: by 10.114.160.199 with HTTP; Wed, 29 May 2013 13:04:57 -0700 (PDT)
In-Reply-To: <51A63DF1.90904@stpeter.im>
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com> <51A63D08.8080406@gmail.com> <51A63DF1.90904@stpeter.im>
Date: Wed, 29 May 2013 21:04:57 +0100
Message-ID: <CAKHUCzx7GSL=ZR56f2fVVSCu7BZVyOK75YQD795D1jkUpwR6_A@mail.gmail.com>
Subject: Re: What do we mean when we standardize something?
From: Dave Cridland <dave@cridland.net>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: multipart/alternative; boundary=14dae94735dd631d4104dde0e5a7
X-Gm-Message-State: ALoCoQm0qRZxC5rC17gdf8bu1Jgc5wWDnoEq5XE4DTSFkC92WuagIW8ArhxH1VrEH5HkjG+icP6R
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 20:05:09 -0000

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

On 29 May 2013 18:42, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
> /me wonders if we need a separate series for informational documentation

Or maybe multiple paths, with multiple entry points.

Perhaps instead of Proposed Standard, we have a Engineering Proposal for an
engineering consensus, and a Submitted Proposal for an industry submission.
Both would move to Internet Standard from there, if appropriate.

I admit to picking names without the word standard in on purpose, but
that's because I think we should reclaim PS... I know I'm in the rough.

Dave.

--14dae94735dd631d4104dde0e5a7
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr"><br>
On 29 May 2013 18:42, &quot;Peter Saint-Andre&quot; &lt;<a href="mailto:stpeter@stpeter.im">stpeter@stpeter.im</a>&gt; wrote:<br>
&gt; /me wonders if we need a separate series for informational documentation</p>
<p dir="ltr">Or maybe multiple paths, with multiple entry points.</p>
<p dir="ltr">Perhaps instead of Proposed Standard, we have a Engineering Proposal for an engineering consensus, and a Submitted Proposal for an industry submission. Both would move to Internet Standard from there, if appropriate.</p>

<p dir="ltr">I admit to picking names without the word standard in on purpose, but that&#39;s because I think we should reclaim PS... I know I&#39;m in the rough.</p>
<p dir="ltr">Dave.</p>

--14dae94735dd631d4104dde0e5a7--

From brian.e.carpenter@gmail.com  Wed May 29 13:44:49 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C39321F9779 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 13:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.439
X-Spam-Level: 
X-Spam-Status: No, score=-102.439 tagged_above=-999 required=5 tests=[AWL=0.160, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kcHdPoEEF09o for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 13:44:41 -0700 (PDT)
Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) by ietfa.amsl.com (Postfix) with ESMTP id C6B4821F9776 for <ietf@ietf.org>; Wed, 29 May 2013 13:44:41 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id 10so9447636pdi.3 for <ietf@ietf.org>; Wed, 29 May 2013 13:44:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hUoC/W57kzZ+gtSwtvbaYRmNm2XBJUkh9oo2+02EZHs=; b=z4VmZ7w6nqF/OGceaTv/+t9d6sEHj2CyHN98L+/ejCpvndooidq4JKcLqKoTB6DaGj CtLDxEMuTPU3HKi11iXM4QEYwKoOA/TBpcVZsJeu2u/S8Tz7/QCdBUWDS+HAh1VUUPL7 fjt0yIXSLFG53wXfGzLLoeB0qlchNUG2Oc3RI3F311AM/pUrsZUnSSmVPCLP8QLm/67m zFEy4hTdNYbOzd9ajTtd8hFhM+30o9sUrdBcWK95AAErWXZfdeY3gCGGEaj8zJpu/25f BlYIQLKHhU4Mmb4twiL/D8q57/mrNBCjEmL3oG1iQ1IhUqbCMrWg4/z3OPPAVqtAWXNj 1y1A==
X-Received: by 10.66.67.11 with SMTP id j11mr5069131pat.220.1369860281502; Wed, 29 May 2013 13:44:41 -0700 (PDT)
Received: from [192.168.1.2] (51.191.252.27.dyn.cust.vf.net.nz. [27.252.191.51]) by mx.google.com with ESMTPSA id vb8sm38630906pbc.11.2013.05.29.13.44.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 13:44:40 -0700 (PDT)
Message-ID: <51A668BB.3040703@gmail.com>
Date: Thu, 30 May 2013 08:44:43 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: What do we mean when we standardize something?
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>	<51A63D08.8080406@gmail.com> <51A63DF1.90904@stpeter.im> <CAKHUCzx7GSL=ZR56f2fVVSCu7BZVyOK75YQD795D1jkUpwR6_A@mail.gmail.com>
In-Reply-To: <CAKHUCzx7GSL=ZR56f2fVVSCu7BZVyOK75YQD795D1jkUpwR6_A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 20:44:49 -0000

On 30/05/2013 08:04, Dave Cridland wrote:
> On 29 May 2013 18:42, "Peter Saint-Andre" <stpeter@stpeter.im> wrote:
>> /me wonders if we need a separate series for informational documentation
> 
> Or maybe multiple paths, with multiple entry points.

We already do have exactly that, and there are many instances
of proprietary or local protocols being documented, but not
standardised, as Informational RFCs in the Independent stream.
Sometimes they squeeze through as Informational RFCs in the
IETF stream.

We also have BCPs, when there is robust consensus on good
operational practice. Again, we have Informational RFCs when
somebody wants to document current practice without seeking
consensus.

I'm not sure what we need to change.

Where we get into trouble seems to be when people want a rubber
stamp for something that doesn't make the cut for IETF consensus.
We have a little trouble saying "No." But I think we have a duty
to say "No" when something works but is believed to be bad for
the Internet as a whole.

    Brian

> 
> Perhaps instead of Proposed Standard, we have a Engineering Proposal for an
> engineering consensus, and a Submitted Proposal for an industry submission.
> Both would move to Internet Standard from there, if appropriate.
> 
> I admit to picking names without the word standard in on purpose, but
> that's because I think we should reclaim PS... I know I'm in the rough.
> 
> Dave.
> 

From ben@nostrum.com  Wed May 29 13:45:52 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC9EF21F97AE; Wed, 29 May 2013 13:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtNbJGYzstq7; Wed, 29 May 2013 13:45:50 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE3221F97A0; Wed, 29 May 2013 13:45:50 -0700 (PDT)
Received: from [172.20.10.2] (mobile-166-147-070-236.mycingular.net [166.147.70.236]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r4TKjmT0011111 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 29 May 2013 15:45:49 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART Telechat Review of draft-ietf-forces-interop-08
Date: Wed, 29 May 2013 15:45:44 -0500
Message-Id: <ACB5DC05-5175-4ADD-91E8-830B35B70564@nostrum.com>
To: "<draft-ietf-forces-interop.all@tools.ietf.org>" <draft-ietf-forces-interop.all@tools.ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass (shaman.nostrum.com: 166.147.70.236 is authenticated by a trusted mechanism)
Cc: "<gen-art@ietf.org> Team" <gen-art@ietf.org>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 20:45:52 -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-forces-interop-08
Reviewer: Ben Campbell
Review Date: 2013-05-29
IETF LC End Date: 2013-05-30
IESG Telechat date: (if known)

Summary: This draft is mostly ready for publication as an informational =
RFC. All of the substantive comments from my earlier review have been =
addressed.  Some editorial issues remain. These are of the sort that the =
RFC editor can probably fix, but if there are further iterations of the =
draft prior to approval it might be worth addressing them.

Major issues:

None.

Minor issues:

None.

Nits/editorial comments:

-- I previously mentioned that the draft used inconsistent verb tenses =
to the point of being confusing. The authors improved this by changing =
occurances most to past tense. However, there were some places where the =
change was incorrect ( section 1 paragraph 1: "This document captures" =
was changed to "... captured".). Also in at least one section (3.3), the =
previously past tense verbs were changed to future tense.

-- There are a lot of missing articles, especially in text that is new =
to this version.

-- section 1, new paragraph 5: Up to date, the 'ForCES..."

I suggest changing "Up to date..." to "As of now..." or "As of the time =
of this writing...". Or even better, remove it completely.





From amankin@verisign.com  Wed May 29 14:05:03 2013
Return-Path: <amankin@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 8D43821F9298; Wed, 29 May 2013 14:05:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1rCLKxXSxHYE; Wed, 29 May 2013 14:04:57 -0700 (PDT)
Received: from exprod6og118.obsmtp.com (exprod6og118.obsmtp.com [64.18.1.233]) by ietfa.amsl.com (Postfix) with ESMTP id BCBD221F918F; Wed, 29 May 2013 14:04:55 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob118.postini.com ([64.18.5.12]) with SMTP ID DSNKUaZtd5fdAtXmSINLUXxEBAfjgCBu/Y0v@postini.com; Wed, 29 May 2013 14:04:55 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r4TL4qcC014913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 May 2013 17:04:54 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 29 May 2013 17:04:51 -0400
From: "Mankin, Allison" <amankin@verisign.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Subject: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Topic: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Index: AQHOXLAohg3/5/hJhka74OTHCGTCZQ==
Date: Wed, 29 May 2013 21:04:51 +0000
Message-ID: <D9F5D76C-1929-4C6B-B902-3A0854821FB7@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F4D60B42B10B6D438950D8D6DC648102@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 21:05:03 -0000

Hi, everyone,

Remember that I'm challenging the IETF to come up with 200 volunteers for=20
the upcoming nomcom.  You can volunteer just by hitting Reply to this email=
.

What are you waiting for??  The more volunteers we get, the better chance w=
e
have of choosing a random yet representative cross section of the IETF=20
population.  Respond to the 200-volunteer challenge and hit Reply right now=
.=20
(Well, much as I want you to do this, please look below at the posts being
filled and be sure you are willing to forgo trying for any of them this yea=
r).

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

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

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

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

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

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

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

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

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

You should expect an email response from me within 3 business days stating
whether or not you are qualified (and added to the list).  If you don't rec=
eive this
response, please re-send your email adding the tag "RESEND" to the subject =
line.

Participating in the IETF nomcom is a meaningful and fun way to contribute =
to the IETF. =20
Please help us meet the 200-volunteer challenge by hitting Reply to this me=
ssage today. =20

Allison=20

Allison Mankin
Nomcom Chair 2013-2014
 =

From amankin@verisign.com  Wed May 29 14:09:04 2013
Return-Path: <amankin@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 8B49C21F9263; Wed, 29 May 2013 14:09:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyxesYK4GZB3; Wed, 29 May 2013 14:08:58 -0700 (PDT)
Received: from exprod6og127.obsmtp.com (exprod6og127.obsmtp.com [64.18.1.78]) by ietfa.amsl.com (Postfix) with ESMTP id E702D21F856D; Wed, 29 May 2013 14:08:57 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob127.postini.com ([64.18.5.12]) with SMTP ID DSNKUaZuaSRoZGmiHTPtkEJqCWlP1+2palzH@postini.com; Wed, 29 May 2013 14:08:58 PDT
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01.vcorp.ad.vrsn.com [10.173.152.205]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r4TL8vRH015040 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 May 2013 17:08:57 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Wed, 29 May 2013 17:08:56 -0400
From: "Mankin, Allison" <amankin@verisign.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
Subject: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Topic: Oooops CORRECTION Reply to This - Re: Nomcom 2013-14 Volunteering - 2nd Call
Thread-Index: AQHOXLAohg3/5/hJhka74OTHCGTCZZkc6yMA
Date: Wed, 29 May 2013 21:08:56 +0000
Message-ID: <639CE511-1B0E-47D8-9D9D-1A48964467E2@verisign.com>
References: <D9F5D76C-1929-4C6B-B902-3A0854821FB7@verisign.com>
In-Reply-To: <D9F5D76C-1929-4C6B-B902-3A0854821FB7@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0553B016F069A34196A7AF0900A6EC62@verisign.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Mankin, Allison" <amankin@verisign.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 21:09:04 -0000

Sorry - my eye was on entering the reply-to field and then I forgot....apol=
ogies in advance for=20
pain that may result from this lapse.


On May 29, 2013, at 5:04 PM, "Mankin, Allison" <amankin@verisign.com> wrote=
:

> Hi, everyone,
>=20
> Remember that I'm challenging the IETF to come up with 200 volunteers for=
=20
> the upcoming nomcom.  You can volunteer just by hitting Reply to this ema=
il.
>=20
> What are you waiting for??  The more volunteers we get, the better chance=
 we
> have of choosing a random yet representative cross section of the IETF=20
> population.  Respond to the 200-volunteer challenge and hit Reply right n=
ow.=20
> (Well, much as I want you to do this, please look below at the posts bein=
g
> filled and be sure you are willing to forgo trying for any of them this y=
ear).
>=20
> The official information:
> The IETF nominating committee (nomcom) process for 2013-14 is under way. =
The=20
> IETF nomcom appoints folks to fill the open slots on the IAOC, the IAB,
> and the IESG. Ten voting members for the nomcom are selected in a verifia=
bly
> random way from a pool of volunteers.=20
>=20
> The details of the selection and operation of the nomcom can be found=20
> in RFCs 3777, 5078, 5633, 5680, and 6859.  Four of those RFCs  (3777, 563=
3,=20
> 5680 and 6859)  comprise BCP 10. We will also reference RFC 3797.
>=20
> Volunteers must have attended 3 of the past 5 IETF meetings.  As specifie=
d in
> RFC 3777, that means three out of the five past meetings up to the time t=
his
> email announcement goes out to start the solicitation of volunteers. The =
five
> meetings out of which you must have attended three are IETF 82, 83, 84, 8=
5, 86.
>=20
> If you qualify, reply to this email and volunteer. =20
>=20
> The list of people and posts whose terms end with the March 2014 IETF
> meeting, and thus the positions for which this nomcom is responsible, are
> IAOC:
> Chris Griffiths
>=20
> IAB:
> Bernard Aboba
> Marc Blanchet
> Ross Callon
> Eliot Lear
> Hannes Tschofenig
>=20
> IESG:
> Barry Leiba (Applications)
> Brian Haberman (Internet)
> Benoit Claise (Operations and Management)
> Gonzalo Camarillo (RAI)
> Stewart Bryant (Routing)
> Sean Turner (Security)
> Martin Stiemerling (Transport)
>=20
> The primary activity for this nomcom will begin in July 2013 and should b=
e
> completed in January 2014.  Being a nomcom member will require some time
> commitment - there will be interviews with candidates at meetings, regula=
rly
> scheduled conference calls to ensure progress, collection and review of=20
> requirements from the commitment, review of candidate questionnaires and
> of community feedback.  A more detailed timetable for the nomcom tasks
> will appear soon.
>=20
> Please respond to this email before 11:59 pm EDT (UTC -4 hours)=20
> June 16, 2013.  In the body include:=20
> 1. your Given Name as you enter it when you register for the IETF
> 2. your Family Name as you enter it when you register for the IETF
> 3. your current primary affilation (the information you enter into the Co=
mpany field)
> 4. any/all email addresses you've used to register for IETF meetings=20
> 5. which email address you prefer=20
> 6. your phone number (for our use in confirming you if selected).
>=20
> You should expect an email response from me within 3 business days statin=
g
> whether or not you are qualified (and added to the list).  If you don't r=
eceive this
> response, please re-send your email adding the tag "RESEND" to the subjec=
t line.
>=20
> Participating in the IETF nomcom is a meaningful and fun way to contribut=
e to the IETF. =20
> Please help us meet the 200-volunteer challenge by hitting Reply to this =
message today. =20
>=20
> Allison=20
>=20
> Allison Mankin
> Nomcom Chair 2013-2014


From sm@resistor.net  Wed May 29 14:56:09 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 019B521F9782 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 14:56:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.228
X-Spam-Level: 
X-Spam-Status: No, score=-102.228 tagged_above=-999 required=5 tests=[AWL=0.371, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bJ55QvfY6MBh for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 14:56:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D17321F9780 for <ietf@ietf.org>; Wed, 29 May 2013 14:56:08 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4TLu1a4005188; Wed, 29 May 2013 14:56:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369864567; bh=OWD4aljdO1iK+BeT1IglwXQQveG3aYlUPoI6JjCFyI4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=i9GxtDVzb5PibrKeLw2gs5zJBWqeQJ/Y1Yx4S8oiwwLv0ew6dmr//js3ZKdEW6Iff unookbDaVjkvxkiCVIskQSSuWesRHlLnbJFNvTlfHlN+723lwEosy0pOkRWCRlEYWc fPdLNAWYedBnqExmSOXk3pxqhQbz2wV2wqPfEKeo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369864567; i=@resistor.net; bh=OWD4aljdO1iK+BeT1IglwXQQveG3aYlUPoI6JjCFyI4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tl7hgSdKhCbmfpNBVdUpOq6WZmvm8wKfdoqtYg78j7ilVHstz0UI2grzrQRx4oAy1 FGiimSsUERDs/DvwY1Y18ngcQaCuQcMwzykmzIBRhIfFU2roELqngfcr1fhbBkWxYM IaFH/FtZI3bhdp9x82ihWFSNGc+Ek9ILIvpYUftQ=
Message-Id: <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 29 May 2013 14:51:51 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominu m.com>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.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: Wed, 29 May 2013 21:56:09 -0000

Hi Ted,
At 09:53 29-05-2013, Ted Lemon wrote:
>too restrained in this regard, IMHO.   I would add some text to the 
>introduction, like this:
>
>The DNS Resource Records described in this document have significant 
>privacy implications (see section 8).   They were developed with the 
>intention to use them in [scenario a] or [scenario b] and are likely 
>not to be appropriate in other scenarios.   In particular, they are 
>unlikely to be appropriate for use in DNS zones hosted on 
>globally-reachable servers that will answer any query without any 
>access control mechanism.

Here's what I would be told:  Scenario a and Scenario b do not have 
privacy implications as they have been reviewed by a respected 
organization in Canada.  I would also be told that there is an Office 
of the Privacy Commissioner of Canada which is diligent [1].  I will 
also be told that all this has been reviewed diligently by highly 
respected people in the Internet Engineering Task Force.

I still do not plan to raise any objection on the draft.

Regards,
-sm

1. Out of context quote: "One issue being contended with by several 
data protection authorities was whether or not Media Access Control 
("MAC") addresses (manufacturer-assigned codes that allow devices to 
speak to one another), either alone or in combination with other 
information, constitute personal information.  The OPC did not have 
to address this question since it found, as a matter of fact, clear 
examples of personal information collected among the payload data, 
including complete e-mails, user names and passwords, and even 
medical conditions of specified individuals.  However, as in the case 
of IP addresses, the question of whether or not MAC addresses 
constitute personal information is highly contextual and must be 
considered in conjunction with what other information is also 
available to different users in different circumstances. 


From Ted.Lemon@nominum.com  Wed May 29 15:21:57 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88D9A21F93DE for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 15:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.514
X-Spam-Level: 
X-Spam-Status: No, score=-106.514 tagged_above=-999 required=5 tests=[AWL=0.085, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4a6SegQFkUK for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 15:21:47 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 9116221F9121 for <ietf@ietf.org>; Wed, 29 May 2013 15:21:47 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUaZ/eytkYnFBuPbgVRGFZokHvX9zCyXt@postini.com; Wed, 29 May 2013 15:21:47 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 12BAC1B81B3 for <ietf@ietf.org>; Wed, 29 May 2013 15:21:47 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 058A2190052; Wed, 29 May 2013 15:21:47 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 29 May 2013 15:21:46 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: Last  Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Thread-Topic: Last  Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Thread-Index: AQHOXLdTJRdCGgULcEmtH1sPD4zIbZkdMbiA
Date: Wed, 29 May 2013 22:21:46 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BA3A0@mbx-01.win.nominum.com>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com> <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <81FE170B9DFA7E43AE5AA8C81B44B12B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 22:21:59 -0000

On May 29, 2013, at 5:51 PM, SM <sm@resistor.net> wrote:
> Here's what I would be told:  Scenario a and Scenario b do not have priva=
cy implications as they have been reviewed by a respected organization in C=
anada.  I would also be told that there is an Office of the Privacy Commiss=
ioner of Canada which is diligent [1].  I will also be told that all this h=
as been reviewed diligently by highly respected people in the Internet Engi=
neering Task Force.

I didn't say that I support the draft; just what I think could be done to s=
omewhat mitigate its scope.   My personal (non-hat) feeling about the draft=
 is that if there is something good that will result from documenting these=
 RRtypes, then the draft is worth doing, but if there is no good outcome ot=
her than "we documented it," then the document shouldn't be published.   I =
haven't been following the discussion closely enough to know what good outc=
ome is anticipated as a result of publishing this document.

I hope the responsible AD for this document will not count me as participat=
ing in the consensus on this document; it was not my intention in making th=
e suggestion I made to indicate that I favor publishing the document.   Bas=
ed on the extent to which I _have_ followed the discussion, my position on =
the document could best be characterized as "trepidatious semi-neutrality, =
leaning towards opposition."


From Ted.Lemon@nominum.com  Wed May 29 15:51:11 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 463F421F96B9 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 15:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.518
X-Spam-Level: 
X-Spam-Status: No, score=-106.518 tagged_above=-999 required=5 tests=[AWL=0.081, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NiqvEP8nLxUk for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 15:51:04 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA0921F96A3 for <ietf@ietf.org>; Wed, 29 May 2013 15:51:00 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUaaGU1RT64tf0SeuiWQyBheucbRCQT/C@postini.com; Wed, 29 May 2013 15:51:03 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A9E051B81A2 for <ietf@ietf.org>; Wed, 29 May 2013 15:50:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id A32F1190052; Wed, 29 May 2013 15:50:59 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Wed, 29 May 2013 15:50:54 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: SM <sm@resistor.net>
Subject: Re: Last  Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Thread-Topic: Last  Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
Thread-Index: AQHOXLdTJRdCGgULcEmtH1sPD4zIbQ==
Date: Wed, 29 May 2013 22:50:53 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BA488@mbx-01.win.nominum.com>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com> <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net> <62037E40-A130-41F0-A0D5-0B2A1B89AABA@nominum.com>
In-Reply-To: <62037E40-A130-41F0-A0D5-0B2A1B89AABA@nominum.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: <700080C5D6CE2E46B6149907BFBA62D2@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 22:51:11 -0000

On May 29, 2013, at 6:21 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:
> I hope the responsible AD for this document will not count me as particip=
ating in the consensus on this document; it was not my intention in making =
the suggestion I made to indicate that I favor publishing the document.   B=
ased on the extent to which I _have_ followed the discussion, my position o=
n the document could best be characterized as "trepidatious semi-neutrality=
, leaning towards opposition."

Okay, I felt a bit embarrassed about having said this, so I went back and r=
eviewed the justification for bringing this forth as an IETF document.   Th=
e stated reason for publishing the document as an IETF document is that the=
re is a regulatory requirement in Canada to implement something like this. =
  I think that's really thin, and I as an IETF participant, hat off, I oppo=
se the publication of this document.

I think Joe did the right thing in registering the RRtype, and I think Joe =
should by all means publish this on his personal web site so that people wh=
o need to implement this because of the weird requirements of various regul=
atory bodies can be satisfied in a clean way.   However, I think putting th=
is forward as an IETF consensus document, or as an IETF document at all, do=
es convey the wrong message.


From hsantos@isdg.net  Wed May 29 15:59:25 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FB021F96E7 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 15:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.677
X-Spam-Level: 
X-Spam-Status: No, score=-101.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNuuZTCY0XlS for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 15:59:20 -0700 (PDT)
Received: from mail.catinthebox.net (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0619121F9712 for <ietf@ietf.org>; Wed, 29 May 2013 15:59:19 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1453; t=1369868352; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=xTeLyvt MOzFZgKD8ZMVfX6tipV8=; b=K+7UQWTBA1gvrklv9fOScKK7OQkwZciyjOQX+Gz HltJW9E2Db7xcvzG23Ijr50Qws+Tg61t6QHhS3KHtRGo/zjDZgWPE7DgsSr+Fzop 44FDaB+mvHTEfgHo92P8Kg92e6laSNmALPzrfrgK1zvUGnyCgJ0cCBO4fWvxCg0O nNLs=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 29 May 2013 18:59:12 -0400
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 625918256.6977.3084; Wed, 29 May 2013 18:59:11 -0400
Message-ID: <51A687C3.5040909@isdg.net>
Date: Wed, 29 May 2013 18:57:07 -0400
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>,  "ietf-dkim@mipassoc.org" <ietf-dkim@mipassoc.org>, iesg@ietf.org
Subject: DKIM promotion to Internet Standard status
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, 29 May 2013 22:59:25 -0000

As a commercial implementer and acknowledged contributor to the DKIM 
protocol IETF project, with some reservation, I would like to add my 
support for the promotion of the DKIM protocol to Internet Standard (IS) 
status.

For the record, I would like to state that there still remains 
inconsistent reputation modeling of DKIM that has not paid off. DKIM 
processing has offered no value in message evaluations.  No persistent 
or consistent trust framework ("Batteries Required") has emerged for 
MTAs, MDAs, MSAs, MUAs or any other DKIM processor.  In fact, the higher 
potential model (Author Domain Policies) which was intentionally 
separated from DKIM continues to be the trend in currently explored 
augmented protocols to help protect the DKIM signature layer.  Author 
Domain Policies such as ADSP, and extensions ATPS, ASL and now DMARC has 
emerged to provide signature protection and handling guidelines for 
domains and receivers.   This Author Domain Policy framework is not 
depicted, by design, in the DKIM  proposed standard protocol. However, 
it is depicted in other RFC documents, such as the Threat Analysis 
(RFC4686), DKIM Deployment Guide (RFC5863) and the DKIM overview 
(RFC5585) informational publications. Perhaps some update in the future 
can correct this design and market inconsistency and explicitly provide 
knowledge of the alternative frameworks available for DKIM.

--
Hector Santos, CTO
Santronics Software, Inc.


From ggm@algebras.org  Wed May 29 16:29:34 2013
Return-Path: <ggm@algebras.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 3638E21F8976 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 16:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7LdSxWwQPxwg for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 16:29:28 -0700 (PDT)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 75B1C21F89EB for <ietf@ietf.org>; Wed, 29 May 2013 16:29:26 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id g10so9574145pdj.41 for <ietf@ietf.org>; Wed, 29 May 2013 16:29:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=afhbG6T2dy7YzpR7b8EVSmgXO6XXNCN833Jl5PaWRTQ=; b=dYHMTcxn8kkZ1tNS6nrXOqOLoBMUGREaXMyLG/63mpDWr4DPgWwbBIlUDymHMamrTl P0FWZB+H1f2N4SoDlaQipOwgfJWkSxm6AkxBJAp/Rj2deYAXMU5RVVocpCJxsE3cuo0x sfP2sfF9PTPOE6M/QTQX32DmrPSi8HpNA58SuGSnMHGbi7+r86jecmgpzvNrAtxEKKNr ZIFQa/eqF+E1fbtcpI0AlD6VuQKzUyRo1aUwROjcbH0BPR9WbaIgmwxQUYJlKV0nYPum rVij+5f/XUWHlMRw6YWVPTYPJJYAEcYAoDeb+1eA2DdtFC1VsHO8BTHw1vNWfGFLXuod C7vA==
MIME-Version: 1.0
X-Received: by 10.66.8.138 with SMTP id r10mr5723207paa.55.1369870164913; Wed, 29 May 2013 16:29:24 -0700 (PDT)
Received: by 10.70.25.195 with HTTP; Wed, 29 May 2013 16:29:24 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:b5c2:a4c8:ee5c:2816]
In-Reply-To: <08CA5DA78C79446B431AC8B6@JcK-HP8200.jck.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <51A56C53.7070709@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk> <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@mail.gmail.com> <08CA5DA78C79446B431AC8B6@JcK-HP8200.jck.com>
Date: Thu, 30 May 2013 09:29:24 +1000
Message-ID: <CAKr6gn1VhNpW9C49hkH1=-rxWU8YkK5wCXaHEiBG1Lp3yA8VLQ@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: George Michaelson <ggm@algebras.org>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=bcaec51dd3c791811304dde3c08b
X-Gm-Message-State: ALoCoQnFfLdxHyWg/yL2MtjY/bq0sBG5JpS/e8Hz8y4Fp9Dqr0c3xsd9I3NnKw/tUumgZZ4299BL
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 23:29:34 -0000

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

yes, I made a facetious posting because I sensed that we were discussing
outcomes on a basis of 'nothing happened' when in fact, I think by scale,
Australian participation reflects if not exceeds our numerical role in
standards development and Internet matters. There is reason to believe we
do accrete people by bringing a roadshow to town. Expensive way to accrete
matter. Australia is a G20 participant and a net donor into development of
standards worldwide, and ICT. So, its arguable "we didn't need the help" of
a local meeting.

At risk of alienating my comrades from locations seeking to attract an IETF
for local development/inclusiveness and the like reasons, I think John gets
to the nub of the matter: the wider community cost, borne by all attendees
as a 'silent tax' is really very high, for this outcome. We need to be
explicit this is what we're doing. The ISOC grants are probably a more cost
effective way of boosting participation from outlier economies right now.

So lets be explicit. This is a standards-setting body, which is discussing
outreach, inclusiveness, wider participation outcomes, and the cost
consequences on attendance where the core motivation is standards setting.
If the core motivations are changing, maybe that drives things in a
different way?

[I loved BA when I went there for a LacNIC meeting. I worry about becoming
a standards tourist.]

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

<div dir=3D"ltr">yes, I made a=A0facetious=A0posting because I sensed that =
we were discussing outcomes on a basis of &#39;nothing happened&#39; when i=
n fact, I think by scale, Australian participation reflects if not exceeds =
our numerical role in standards development and Internet matters. There is =
reason to believe we do accrete people by bringing a roadshow to town. Expe=
nsive way to accrete matter. Australia is a G20 participant and a net donor=
 into development of standards worldwide, and ICT. So, its arguable &quot;w=
e didn&#39;t need the help&quot; of a local meeting.<div class=3D"gmail_ext=
ra">
<br><div class=3D"gmail_quote"><div style>At risk of alienating my comrades=
 from locations seeking to attract an IETF for local development/inclusiven=
ess and the like reasons, I think John gets to the nub of the matter: the w=
ider community cost, borne by all attendees as a &#39;silent tax&#39; is re=
ally very high, for this outcome. We need to be explicit this is what we&#3=
9;re doing. The ISOC grants are probably a more cost effective way of boost=
ing participation from outlier economies right now.=A0</div>
<div style><br></div><div style>So lets be explicit. This is a standards-se=
tting body, which is discussing outreach, inclusiveness, wider participatio=
n outcomes, and the cost consequences on attendance where the core motivati=
on is standards setting. If the core motivations are changing, maybe that d=
rives things in a different way?</div>
<div style><br></div><div style>[I loved BA when I went there for a LacNIC =
meeting. I worry about becoming a standards tourist.]</div></div></div></di=
v>

--bcaec51dd3c791811304dde3c08b--

From abdussalambaryun@gmail.com  Wed May 29 17:39:45 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA9721F8CEC for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 17:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.724
X-Spam-Level: 
X-Spam-Status: No, score=-2.724 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wxDUiwJCZXJu for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 17:39:40 -0700 (PDT)
Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) by ietfa.amsl.com (Postfix) with ESMTP id BEF2621F939E for <ietf@ietf.org>; Wed, 29 May 2013 17:39:40 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id bv13so7801747pdb.40 for <ietf@ietf.org>; Wed, 29 May 2013 17:39:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=hWTqyJ4c2DeWSiJfp22p3xHNzfJhs+9zdCvtioXR6JA=; b=00iwlO/sNSplwJnIy2VdzXM82HSLEQrmw/5fYZMuU+78obQdBfFA3xO+Eyr6dwVuKR vrM0Jb8ybYPbIGLtYMoIsOOQrp0J5Vs4Vl2Ra45fH+bFDdu+btjnCiY91fDEMHXAJ4pa +c0qlqEJDSGgRWxWxsguItG2+WZw1atlXJa8VEmKQkdyQfSnPiMbGmNC2R4/HKmffk80 Rg29D48E52rdmOvCWI4fM7hnBasky7Yp/8Fz71dcsa/QC+AP2PvAZKWbBBqn3vfGF0Fr kaODJZ+eJRTGnwoOPKceOsZ9awNyTs6K/uOrjfpPrMBgJnxfvkBPpzThomITmfVb7kMT cIpQ==
MIME-Version: 1.0
X-Received: by 10.66.145.98 with SMTP id st2mr6007628pab.24.1369874380458; Wed, 29 May 2013 17:39:40 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 29 May 2013 17:39:39 -0700 (PDT)
In-Reply-To: <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com>
Date: Thu, 30 May 2013 02:39:39 +0200
Message-ID: <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
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: Thu, 30 May 2013 00:39:45 -0000

Hi Lars,

It was for Asia region, I thought its rate is between (5 - 50)
rfc/year for last 3 years. Basing on; The first figure of RFCs is the
Comparison of countries over the year [1], the second, is the
Distribution of number of RFCs per continent [2], the third is
publication rate per year [3]. For the I-Ds going in IETF is seen from
the distribution of drafts according to the countries of their authors
[4] and [5]. All figures make together the below conclusions, even
though some of them need more details for readers to understand.

=A0As from Figure [1] always one region (North America) is doing about
200 rfc/year and the each of others may do between 5 - 50 rfc/year or
50-100, but all together other regions do 150 rfc/year, so total
ietf-participation can be about 350 rfc/year. The Figure [2] is not
reasonable, not showing of years or period of such numbers.

So my understanding is that=A0for Europe-region and Asia-region, the
number of I-Ds rates are high compared to North America, but not the
rate of RFCs. I see that the total RFCs ietf-output=A0rate (RFC/year)=A0as
in Figure [3] for the last three years is about 350 rfc/year, so if
North America is having 200, the all others only will have about 150
rfc/year. The total RFCs produced per countries=A0is in Figure [6] is
reasonable but if compared with Figure [2] I get lost.

>From Figure=A0[5] (also [4]) the number of I-Ds (now currently 2013
outstanding) from Asia and Europe are about 600 and 1200 respectively
(let us add them up so =3D1800 ids), which I think only about 150 will
succeed (non-North America drafts). Furthermore, for North America the
I-Ds are 1500 ids and only 200 ids will succeed to become RFCs. I
think that Asia and Europe should have together about 250/year rfc=A0not
150 rfc/year. If we do more MARKETING effort we can make that rfc-rate
of other regions increase, but we already tried to increase North
America rate but it is stable for about 200 rfc/years.

[1] http://www.arkko.com/tools/rfcstats/countrydistrhist.html
[2] http://www.arkko.com/tools/recrfcstats/d-contdistr.html
[3] http://arkko.com/tools/rfcstats/pubdistr.html
[4] http://www.arkko.com/tools/stats/d-countrydistr.html
[5] http://www.arkko.com/tools/stats/d-countryeudistr.html
[6] http://www.arkko.com/tools/rfcstats/d-countrydistr.html

=A0This lower participation from regions like Asia will continue because
most meeting are in North America, or most participants from North
America prefer to have face-face meeting locally,=A0than to be remote to
other regions=A0(not reasonable because they are writers in English very
well). Also other regions participants prefer to participate in
meetings not remotely (but that is reasonable because they are not
good in English Language Writting). It is also important that some
IETF management visit the other region participants for the progress
of their I-Ds.

Please note that I don't claim that my analysis is all correct, but
trying to discuss it and get others to analyse as well or comment on
the figures/statistics. If you disagree or have any comment please
reply/advise. Thanking you,

AB


On Wed, May 29, 2013 at 10:53 AM, Eggert, Lars <lars@netapp.com> wrote:
>
> Hi,
>
> On May 28, 2013, at 19:46, Abdussalam Baryun <abdussalambaryun@gmail.com>=
 wrote:
> > by looking into the statistics of I-Ds and RFCs, it is strange that we =
get
> > sometimes high rate in the I-D going in IETF from some regions but the
> > success rate of I-Ds to become RFCs is very low (5- 50).
>
> which IDs and RFCs are you basing this statement on?
>
> Thanks,
> Lars

From mnot@mnot.net  Wed May 29 17:46:09 2013
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 E985521F8EB2 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 17:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.345
X-Spam-Level: 
X-Spam-Status: No, score=-105.345 tagged_above=-999 required=5 tests=[AWL=-2.746, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XIi4UmBZZ8RO for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 17:46:04 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 182E321F8EB1 for <ietf@ietf.org>; Wed, 29 May 2013 17:46:04 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.184.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4A12622E253; Wed, 29 May 2013 20:46:01 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com>
Date: Thu, 30 May 2013 10:45:55 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1503)
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: Thu, 30 May 2013 00:46:09 -0000

I would take those numbers with a HUGE grain of salt (as Jari =
documents).

For example, I've lived in Australia since 2006, and yet am only listed =
as producing RFCs in the USA.

Regards,


On 30/05/2013, at 10:39 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Hi Lars,
>=20
> It was for Asia region, I thought its rate is between (5 - 50)
> rfc/year for last 3 years. Basing on; The first figure of RFCs is the
> Comparison of countries over the year [1], the second, is the
> Distribution of number of RFCs per continent [2], the third is
> publication rate per year [3]. For the I-Ds going in IETF is seen from
> the distribution of drafts according to the countries of their authors
> [4] and [5]. All figures make together the below conclusions, even
> though some of them need more details for readers to understand.
>=20
>  As from Figure [1] always one region (North America) is doing about
> 200 rfc/year and the each of others may do between 5 - 50 rfc/year or
> 50-100, but all together other regions do 150 rfc/year, so total
> ietf-participation can be about 350 rfc/year. The Figure [2] is not
> reasonable, not showing of years or period of such numbers.
>=20
> So my understanding is that for Europe-region and Asia-region, the
> number of I-Ds rates are high compared to North America, but not the
> rate of RFCs. I see that the total RFCs ietf-output rate (RFC/year) as
> in Figure [3] for the last three years is about 350 rfc/year, so if
> North America is having 200, the all others only will have about 150
> rfc/year. The total RFCs produced per countries is in Figure [6] is
> reasonable but if compared with Figure [2] I get lost.
>=20
> =46rom Figure [5] (also [4]) the number of I-Ds (now currently 2013
> outstanding) from Asia and Europe are about 600 and 1200 respectively
> (let us add them up so =3D1800 ids), which I think only about 150 will
> succeed (non-North America drafts). Furthermore, for North America the
> I-Ds are 1500 ids and only 200 ids will succeed to become RFCs. I
> think that Asia and Europe should have together about 250/year rfc not
> 150 rfc/year. If we do more MARKETING effort we can make that rfc-rate
> of other regions increase, but we already tried to increase North
> America rate but it is stable for about 200 rfc/years.
>=20
> [1] http://www.arkko.com/tools/rfcstats/countrydistrhist.html
> [2] http://www.arkko.com/tools/recrfcstats/d-contdistr.html
> [3] http://arkko.com/tools/rfcstats/pubdistr.html
> [4] http://www.arkko.com/tools/stats/d-countrydistr.html
> [5] http://www.arkko.com/tools/stats/d-countryeudistr.html
> [6] http://www.arkko.com/tools/rfcstats/d-countrydistr.html
>=20
>  This lower participation from regions like Asia will continue because
> most meeting are in North America, or most participants from North
> America prefer to have face-face meeting locally, than to be remote to
> other regions (not reasonable because they are writers in English very
> well). Also other regions participants prefer to participate in
> meetings not remotely (but that is reasonable because they are not
> good in English Language Writting). It is also important that some
> IETF management visit the other region participants for the progress
> of their I-Ds.
>=20
> Please note that I don't claim that my analysis is all correct, but
> trying to discuss it and get others to analyse as well or comment on
> the figures/statistics. If you disagree or have any comment please
> reply/advise. Thanking you,
>=20
> AB
>=20
>=20
> On Wed, May 29, 2013 at 10:53 AM, Eggert, Lars <lars@netapp.com> =
wrote:
>>=20
>> Hi,
>>=20
>> On May 28, 2013, at 19:46, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
>>> by looking into the statistics of I-Ds and RFCs, it is strange that =
we get
>>> sometimes high rate in the I-D going in IETF from some regions but =
the
>>> success rate of I-Ds to become RFCs is very low (5- 50).
>>=20
>> which IDs and RFCs are you basing this statement on?
>>=20
>> Thanks,
>> Lars

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




From abdussalambaryun@gmail.com  Wed May 29 18:16:11 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F5021F93C4 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 18:16:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aij47MeoBcPp for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 18:16:06 -0700 (PDT)
Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA2121F939E for <ietf@ietf.org>; Wed, 29 May 2013 18:16:06 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id v14so8533031pde.4 for <ietf@ietf.org>; Wed, 29 May 2013 18:16:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1Y1hhcB8sMdAYuZbnF8lzEK+oa71ppePBMTpA0nDQnE=; b=C+Q+9yXZP0g3FQy5LharaFKrJ9X+yiDMP9X172B4KKcF+HE4L5NlsFrzwkeCdPhgaE FAq6EwJ0anOzuizWxh8+RUe+Pzisr1K5nDy0E38G4Or5y7u3TdCBucBptz5FU96RAf5x NdcswFnTPYd1cWKkDcstWQMGIqMKhSTnvOGYn/hZ/UYBsBDeHBh5Zj4HXjDpjD+aaelI JCcVpZ9k9kBBCTRxrzQjjXEUs40/r8NOauehPH0uW/+5XwuDciMKRuwrZSQkoPDEeXPk P/lpZXHlpbeZ3xONd+NdrYoht+BnNwEIoTvIOSo1lsDZImBgcguU4DKWLsPgyl9cz5RF T2cQ==
MIME-Version: 1.0
X-Received: by 10.66.158.234 with SMTP id wx10mr6003224pab.43.1369876566367; Wed, 29 May 2013 18:16:06 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Wed, 29 May 2013 18:16:06 -0700 (PDT)
In-Reply-To: <4237401D-DBEE-4547-AB07-21B2D4BFA895@piuha.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <4237401D-DBEE-4547-AB07-21B2D4BFA895@piuha.net>
Date: Thu, 30 May 2013 03:16:06 +0200
Message-ID: <CADnDZ89mfLWsbpnbFBGc7qNw_ci0opEcf4+tySB01cohr0zD9Q@mail.gmail.com>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
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: Thu, 30 May 2013 01:16:11 -0000

On 5/29/13, Jari Arkko <jari.arkko@piuha.net> wrote:
>
>>> by looking into the statistics of I-Ds and RFCs, it is strange that we
>>> get
>>> sometimes high rate in the I-D going in IETF from some regions but the
>>> success rate of I-Ds to become RFCs is very low (5- 50).
>
> There seems to be a general pattern where new participants first participate
> and/or produce IDs but it takes some time to produce RFCs.

Yes that is right, so I think we can encourage thoes new participants
to join and continue, of speed up by our guidance, and also the IETF
may be guided by thoes new comers. It is a two way new-participation,
and even IETF is new to participate in other new sub-regions or
sub-communities.

>For instance, for
> a while it was the case that there was a growing number of proposals and
> participants from China,

Yes IETF needs China's participation, so the question is why is China
(as sub-region) having low rate of rfc/year? How can the IETF do
marketing/help to improve that?

> but it is only more recently that the RFC
> statistics reflect this (see the bright green line in
> http://www.arkko.com/tools/rfcstats/countrydistrhist.html). The hypothesis
> is that first of all, it takes a while to produce RFCs :-) and that new
> participants take a while before they get up to speed on the process, find
> enough other parties that share similar needs for the specific technical
> work, etc.

So if you agree that they need to find other parties to speed up or
increase rate of rfc/year, that meens it will be a good idea to have
one meeting of IETF per year in Asia region (IETF marketing in Asia
for participation).

Furthermore, IETF can have one meeting per year for each region
equally (for equal marketing opportunities), because North America
region's rate of rfc/year for many years shown to be stable not much
improving (about 200 rfc/year), and all participants in North America
have excellent English and writting skill to explain remotely in
meetings.

Some inputs on this IETF list (sub: IETF meeting in South America) say
that IETF meeting in South America will not increase participation, as
no result of such marketing (I disagree, their argument may be correct
only if South America are well English writers that can easily
remotely communicate). On the other hand, from their argument I
understand that it means there is no affect of IETF meeting for all
regions to increase or decrease participation including North America
(no results of marketing or de-marketing). Therefore, if we reduce the
number of meeting in North America (as not de-marketing because at
least there is a meeting per year) we will not face any decrease of
the 200 rfc/year (so we can give more space to other regions), because
they are mostly not-new-participants (as compared to hypothesis you
explain for China's rate and new-participate speed) and they are well
english/known writers/remote-participants.

AB
My thoughts on the subject and on South America meeting subject.

From jabley@hopcount.ca  Wed May 29 18:34:39 2013
Return-Path: <jabley@hopcount.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B4E21F90CD for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 18:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MILESw22I9-w for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 18:34:34 -0700 (PDT)
Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0C45E21F8FA9 for <ietf@ietf.org>; Wed, 29 May 2013 18:34:34 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so9667895pdj.15 for <ietf@ietf.org>; Wed, 29 May 2013 18:34:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=WfkQUg9HJyHpjY1s+JnFrAr00BhkxCcJ5n0N9gIAGa8=; b=f5w7FgjbgrLF9LLqsp0JkJ/17/1vBrZVOPVI/nILrDRDJsw8yyULb3vbwsPRRIWoEy UJj+LRHHZtfIKBg0aL+9cvdZyKo+QYstjuIvezb5iv7rDH+m23XDNmyjlUaih3jmEwKK wMPQy7OFRLgGVRJ9AwRQnExuFSRgb3HcrtCBM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=WfkQUg9HJyHpjY1s+JnFrAr00BhkxCcJ5n0N9gIAGa8=; b=ajmcAqA8B3OrRQWz6BTHAAIVBu5d2RMEeDqe2OFwgG9h30ABUW7G2CsUz+i79b3Pq9 d3hWFLkMctu/f1Qw5lFIPiPCQdcQF5xG0x05YKHqEsuCkYufjoUiZ1kKW3vhc6PMe2mQ vXFAQCta/uXZPPN5yy8EwXetX3mI1Lj5X75XqNjed/LRuIiCE/o5SHS8WwoUxqr+kMuU Xz1fX0MYpzZTpHvUJxqTFhnHnIji1QdFMIwl/8Ph9Lx8Cr70t1uyxi0m2+3X9zVnkxg1 OZ5Sg+akG6I/hIhOL57X4n3wVDmokHHZJBynoRMU65n0FviMrTgOF309PnXkUB3vwp2E SvjQ==
X-Received: by 10.66.122.163 with SMTP id lt3mr5942619pab.219.1369877673779; Wed, 29 May 2013 18:34:33 -0700 (PDT)
Received: from ?IPv6:2620::2d0:111:d0b1:c473:fc0a:e0af? ([2620:0:2d0:111:d0b1:c473:fc0a:e0af]) by mx.google.com with ESMTPSA id ya4sm39436344pbb.24.2013.05.29.18.34.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 May 2013 18:34:32 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Last Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BA488@mbx-01.win.nominum.com>
Date: Wed, 29 May 2013 18:34:30 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9EF99F12-AD4D-4BDB-81A9-12D6E9DF3965@hopcount.ca>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com> <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net> <62037E40-A130-41F0-A0D5-0B2A1B89AABA@nominum.com> <8D23D4052ABE7A4490E77B1A012B6307751BA488@mbx-01.win.nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1503)
X-Gm-Message-State: ALoCoQljr4F7IiOJkVvQaVscBvFDl+ZL8VHUa5DfnqxIIUE9VuqEi2WHlLqyFFqI9QvmhNOp2gpx
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 01:34:39 -0000

Hi Ted,

On 2013-05-29, at 15:50, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> Okay, I felt a bit embarrassed about having said this, so I went back =
and reviewed the justification for bringing this forth as an IETF =
document.   The stated reason for publishing the document as an IETF =
document is that there is a regulatory requirement in Canada to =
implement something like this.

No, that's not right (and really, if that's how you read the document at =
hand then clearly I need to re-write it). Let's review.

The original motivation for requesting code-point assignments for new =
RRTypes which would facilitate a clean encoding of EUI-48 and EUI-64 =
addresses in the DNS resulted from my distaste for the evident lack of =
consistency in approach taken in response to the CRTC's general =
requirement that cable operators publish this kind of data in the DNS, =
for internal, authenticated access by resellers of their access networks =
in Canada.

It's not at all certain or even likely that the CRTC-mandated systems =
will ever use these RRTypes. That ship has surely sailed. The reason for =
requesting the code-points was to make future such situations less =
messy, and more likely to result in DNS schemas (if that's a phrase) =
that were consistent and parseable.

Code-points were assigned following the documented process, which relies =
upon expert review. To support that review, I wrote a specification for =
their use as an I-D (intended status: experimental). Note that by =
specification I mean a technical description of the encoding and =
protocol considerations associated with EUI48 and EUI64, and not any =
kind of applicability statement or guidance for how the RRTypes should =
be used.

I've had feedback from a small number of people who are already in the =
habit of publishing MAC addresses in the DNS as part of (as I understand =
it) inventory management and internal troubleshooting. I take no =
position here on whether that's a good idea, but I conclude that =
publishing such data in the DNS happens today, regardless of the =
availability of the EUI48 or EUI64 RRTypes.

The new RRTypes have since been implemented in the code base of BIND9, =
NSD, Knot DNS and PowerDNS based on that specification.

After some discussion in dnsext, directly with individual contributors =
and with Joel as Ops Area AD, the draft was revised. Text was added, =
including the general use case for storage of this data in the DNS =
mandated by the CRTC (requested by Joel). The intended status was =
changed to standards track, since I was told that made sense.

After last-call discussions on this list the intended status was changed =
to informational, and more textual changes were made.

The stated reason for publishing this draft in the RFC series (I'm =
stating it now!) is that the RFC series is the most obvious place for =
anybody to look for a specification about the implementation of these =
RRTypes. That's it.

So, in summary:

1. There is, I would suggest, a stable specification.

2. Code points are assigned.

3. There are multiple implementations.

4. There are multiple use-cases, and multiple examples of these data =
types being published in the DNS today (note, I am not suggesting that =
widespread use is likely or sensible.)

5. It would be useful (I would assert) that the specification can =
actually be found by people in the future who care about it.

In my mind, this suggests publication of the spec in the RFC series, =
where it can join other specifications for the encoding of IPv4, IPv6, =
NSAP, E.164, X.25, ISDN, ATM, NIMROD, HIP, and ILNP addresses. I may =
have missed some.


Joe=

From l.wood@surrey.ac.uk  Wed May 29 18:54:36 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA1C21F92E8 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 18:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UTnb4SN7-+l4 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 18:54:31 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.161]) by ietfa.amsl.com (Postfix) with ESMTP id 0952321F92E7 for <ietf@ietf.org>; Wed, 29 May 2013 18:54:30 -0700 (PDT)
Received: from [195.245.230.131:23109] by server-1.bemta-3.messagelabs.com id F9/C4-06847-551B6A15; Thu, 30 May 2013 01:54:29 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-78.messagelabs.com!1369878868!24122522!2
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29994 invoked from network); 30 May 2013 01:54:29 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-9.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 30 May 2013 01:54:29 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Thu, 30 May 2013 02:53:57 +0100
From: <l.wood@surrey.ac.uk>
To: <mnot@mnot.net>
Date: Thu, 30 May 2013 02:53:56 +0100
Subject: RE: Participation per Region of Authoring IETF documents vs Marketing
Thread-Topic: Participation per Region of Authoring IETF documents vs Marketing
Thread-Index: Ac5czyi36DKC601/QP2OzNyDwuWt0gAB56TI
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E93@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com>, <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
In-Reply-To: <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 01:54:36 -0000

http://www.arkko.com/tools/recrfcstats/d-contdistr.html
(Jari, what time period is that across? Oceania doesn't rate a mention...)
11 RFCs (0.73%) have authors from South America.

http://www.arkko.com/tools/allstats/fernandogont.html
This author is in Argentina (as of 2013)
Fernando has the following 12 RFCs

This suggests that itr would be efficient for the IETF to fund travel and s=
upport for Fernando, who I've met at IETF meetings, rather  than fund an IE=
TF meeting in Fernando's neighbourhood (consistently Haedo, Provincia de Bu=
enos Aires - address is a better guide than affiliation).

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mark Notti=
ngham [mnot@mnot.net]
Sent: 30 May 2013 01:45
To: Abdussalam Baryun
Cc: ietf
Subject: Re: Participation per Region of Authoring IETF documents vs Market=
ing

I would take those numbers with a HUGE grain of salt (as Jari documents).

For example, I've lived in Australia since 2006, and yet am only listed as =
producing RFCs in the USA.

Regards,


On 30/05/2013, at 10:39 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> =
wrote:

> Hi Lars,
>
> It was for Asia region, I thought its rate is between (5 - 50)
> rfc/year for last 3 years. Basing on; The first figure of RFCs is the
> Comparison of countries over the year [1], the second, is the
> Distribution of number of RFCs per continent [2], the third is
> publication rate per year [3]. For the I-Ds going in IETF is seen from
> the distribution of drafts according to the countries of their authors
> [4] and [5]. All figures make together the below conclusions, even
> though some of them need more details for readers to understand.
>
>  As from Figure [1] always one region (North America) is doing about
> 200 rfc/year and the each of others may do between 5 - 50 rfc/year or
> 50-100, but all together other regions do 150 rfc/year, so total
> ietf-participation can be about 350 rfc/year. The Figure [2] is not
> reasonable, not showing of years or period of such numbers.
>
> So my understanding is that for Europe-region and Asia-region, the
> number of I-Ds rates are high compared to North America, but not the
> rate of RFCs. I see that the total RFCs ietf-output rate (RFC/year) as
> in Figure [3] for the last three years is about 350 rfc/year, so if
> North America is having 200, the all others only will have about 150
> rfc/year. The total RFCs produced per countries is in Figure [6] is
> reasonable but if compared with Figure [2] I get lost.
>
> From Figure [5] (also [4]) the number of I-Ds (now currently 2013
> outstanding) from Asia and Europe are about 600 and 1200 respectively
> (let us add them up so =3D1800 ids), which I think only about 150 will
> succeed (non-North America drafts). Furthermore, for North America the
> I-Ds are 1500 ids and only 200 ids will succeed to become RFCs. I
> think that Asia and Europe should have together about 250/year rfc not
> 150 rfc/year. If we do more MARKETING effort we can make that rfc-rate
> of other regions increase, but we already tried to increase North
> America rate but it is stable for about 200 rfc/years.
>
> [1] http://www.arkko.com/tools/rfcstats/countrydistrhist.html
> [2] http://www.arkko.com/tools/recrfcstats/d-contdistr.html
> [3] http://arkko.com/tools/rfcstats/pubdistr.html
> [4] http://www.arkko.com/tools/stats/d-countrydistr.html
> [5] http://www.arkko.com/tools/stats/d-countryeudistr.html
> [6] http://www.arkko.com/tools/rfcstats/d-countrydistr.html
>
>  This lower participation from regions like Asia will continue because
> most meeting are in North America, or most participants from North
> America prefer to have face-face meeting locally, than to be remote to
> other regions (not reasonable because they are writers in English very
> well). Also other regions participants prefer to participate in
> meetings not remotely (but that is reasonable because they are not
> good in English Language Writting). It is also important that some
> IETF management visit the other region participants for the progress
> of their I-Ds.
>
> Please note that I don't claim that my analysis is all correct, but
> trying to discuss it and get others to analyse as well or comment on
> the figures/statistics. If you disagree or have any comment please
> reply/advise. Thanking you,
>
> AB
>
>
> On Wed, May 29, 2013 at 10:53 AM, Eggert, Lars <lars@netapp.com> wrote:
>>
>> Hi,
>>
>> On May 28, 2013, at 19:46, Abdussalam Baryun <abdussalambaryun@gmail.com=
> wrote:
>>> by looking into the statistics of I-Ds and RFCs, it is strange that we =
get
>>> sometimes high rate in the I-D going in IETF from some regions but the
>>> success rate of I-Ds to become RFCs is very low (5- 50).
>>
>> which IDs and RFCs are you basing this statement on?
>>
>> Thanks,
>> Lars

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




From john-ietf@jck.com  Wed May 29 22:10:31 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D359F21F9428 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 22:10:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c3T+stG6ucD1 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 22:10:26 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F082B21F9421 for <ietf@ietf.org>; Wed, 29 May 2013 22:10:25 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uhv81-0003FW-86; Thu, 30 May 2013 01:10:21 -0400
Date: Thu, 30 May 2013 01:10:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, Dave Cridland <dave@cridland.net>, Peter Saint-Andre <stpeter@stpeter.im>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: "Fixing: the standards track or RFC series (was: Re: What do we mean when we standardize something?)
Message-ID: <5420793214639E162E9EEC23@JcK-HP8200.jck.com>
In-Reply-To: <51A63D08.8080406@gmail.com>
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com> <51A63D08.8080406@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, 30 May 2013 05:10:31 -0000

Melinda, Peter, Dave, and Brian,

I wanted to try to describe some fundamental models and their
implications but avoid leaping head first into either the "fix
the standards process" or "change the categories or content of
the RFC Series" rat holes.    However...

--On Wednesday, May 29, 2013 09:38 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

>> Proposed Standard on that basis is then proposed for
>> advancement to Internet Standard, I think the review should be
>> comprehensive --perhaps even more comprehensive than the usual
>> such review-- because the Internet Standard is unambiguously
>> an IETF product and recommendation not that of the other
>> body. 
> 
> I'd actually much prefer to see these go to informational, if
> they're to be published.  Otherwise I agree - if something's
> going to be an IETF standard it needs to go through the IETF
> standards development review and revision process, which is
> probably not what the authors want.

While I agree with the preference, I didn't mention it because I
assumed, for the purpose of my analysis, that the choice of
"standards track" or not was outside my logical scope. I suggest
we've done it both ways, e.g., with NFS, we published Version 3
as Informational (RFC 1813) and then produced Version 4 on the
standards track (RFC 3010).   HTTP was pretty much the same: 1.0
was pretty much taken over from W3C and published as
Informational (RFC 1945); 1.1 was a Proposed Standards in RFC
2068.  DKIM, IIR, went directly to Proposed Standard (RFC
4871ff) based mostly on an external spec (RFC 4870 appears to
represent a somewhat different protocol).   There are probably
better examples of the latter.  My guess is that cases will
differ and trying to make a hard rule would just get us into
trouble.


--On Wednesday, May 29, 2013 11:42 -0600 Peter Saint-Andre
<stpeter@stpeter.im> wrote:

> /me wonders if we need a separate series for informational
> documentation

I'm not sure what you are suggesting.  If it is "time to get
informational documents out of the RFC Series", the community
has considered variations on that theme endless times and been
unable to reach consensus that it is a good idea (and has
sometimes reached consensus that it isn't).  In particular,
putting them in a separate series would complicate the model of
publishing externally-produced specifications as Informational
and then following up with Standards Track, IETF designed and
vetted, specs discussed above.

If it is time to rethink the categories of RFCs and/or those of
the standards track as Dave suggests...  well, I've tried
floating several of those proposals and gotten absolutely no
traction.  If you want to try, I promise to cheer supportively
from the sidelines.

--On Thursday, May 30, 2013 08:44 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Where we get into trouble seems to be when people want a rubber
> stamp for something that doesn't make the cut for IETF
> consensus. We have a little trouble saying "No." But I think
> we have a duty to say "No" when something works but is
> believed to be bad for the Internet as a whole.

Yes, and the latter is implicit in my long note.  The even more
difficult problems arise when someone comes to us with a spec
that might be ok but isn't how we would do it and tries to say
"you can have this and we will turn over change control as long
as you don't really want to make any changes".  When a statement
equivalent to that is justified on the basis of either being in
a hurry or not invalidating existing implementations, we find
ourselves in the middle of the contradiction between "consensus
of industry practice" and "best engineering solution" for
standardization.

  best,
     john


From john-ietf@jck.com  Wed May 29 23:05:15 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F418121F93DC for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 23:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EUhB21BinPkR for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 23:05:09 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E943D21F92BB for <ietf@ietf.org>; Wed, 29 May 2013 23:05:08 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uhvyy-0003It-7f; Thu, 30 May 2013 02:05:04 -0400
Date: Thu, 30 May 2013 02:04:54 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Issues in wider geographic participation
Message-ID: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 06:05:15 -0000

Jari,

Inspired by two of your recent notes and Dave Crocker's long
one last weekend (with which I almost completely agree should
that be notable), let me make a few observations:

(1) To the extent to which the IETF's focus is on protocols that
we hope vendors and others ("producers" in the vocabulary of
some other SDOs) will implement and try to get deployed, lines
of argument that start with "they use the Internet there,
therefore they should be participating in the IETF" may just be
irrelevant.  If there is a major vendor design presence in a
region, then we should be very concerned if we don't have
significant presence from that region in the IETF as well.  But,
if the vendor presence is limited to marketing, sales, and
perhaps implementation, then, if that is a problem, it is one
that doesn't lie easily within IETF scope... and probably
shouldn't.

(2) As far as I can tell, the operators in most regions are
generally well represented in, and collaborate using, the
various *NOGs.  If those groups aren't serving their needs, it
is probably not a problem for the IETF.  If they are, then the
IETF should no more be trying to invade that turf than a certain
Geneva-based organization should be invading ours.  We are not a
user group either.  To the extent to which there is a need for
more user groups or more effective ones, I hope that the ISOC
Chapter structure is at least making useful contributions in the
area.

(3) Our Operations and Management Area is mostly about protocols
and tools (just as the Applications area really isn't about
applications as user/purchasers normally understand that term)
and therefore those with the most skin in the game are, again,
producers, vendors, and designers, not users or even operators.
The latter are important for figuring out whether a particular
facility will meet identified needs, but that is typically more
of a review function than a design one.   If we need more input
about such specs, we might ask the various *NOGs or similar
groups to formally review proposed specifications rather than
depending on people to come to f2f IETF meetings or even to
follow our mailing lists.  So, while closer contact with
operator communities is always good (and not just for that
Area), we may need to adjust our expectations to the reality of
what we can do effectively, rather than forcing on broadening
participation for its own sake.

(4) There are some areas of work in the IETF in which very broad
geographic input --more accurately, broad cultural and
linguistic input-- are absolutely essential.  For example, the
more we move into internationalization or make decisions that
dictate or constrain user interfaces, the more danger we get
into of making really stupid decisions if we don't have broad
and diverse participation and input.  To a degree, the same
issue shows up in lower layers of the stack.  For example, the
vast majority of us spend our time using current-technology
hardware, fast and high-capacity connections to the public
Internet, and even faster LANs.  We often subconsciously design
for that sort of environment because we don't encounter the
other kinds on a regular basis. I contend that we have a
relatively poor history of protocol decisions when people are
affected whose day-to-day technology is a decade or two behind
our current experience.

(5) There are a lot of non-vendor participants in the IETF and
even ones whose days as producers of implementations are mostly
over, but it is still a relatively small minority (and, as far
as I can tell, getting smaller).  As a member of that group, I
wish it were larger, both for balance and because I think that
we may have an easier time maintaining focus on the overall
well-being of the Internet as a complete system than people
whose focus is getting the next product specified, implemented,
and into the hands of users (or marketing organizations).  But,
if we contribute usefully, it is mostly because we bring
considerable experience or perspective of one sort or another to
the table.  With rare (and occasionally very important)
exceptions that include people from the research side of the
community, a newly-minted engineer who has no producer
organization affiliation to provide context is unlikely to be
useful to us (and is reasonably likely to have a frustrating
experience no matter what we do about "newcomers" or recruiting).

(6) The IETF is (or has become) primarily an engineering and
protocol design and standardization organization, something that
was recognized over two decades ago when the community kept the
IRTF separate but got rid of all the other non-IETF task forces.
While we could try to "diversify" to include a much broader base
of experience and interests that do not focus directly on our
current range of activities, it is likely that doing so would
increase noise without adding much to the signal.

One thing that all of those observations have in common is that
none of them are likely to be affected by a single meeting in a
single location.  Probably holding a whole year or two of
meetings in the same general vicinity wouldn't make any
significant difference either, at least after we moved on.  

Borrowing from some of the discussions about mentoring during
and after IETF 86, I suggest that, if we really want to
encourage active participation from places where we now have
very little, we would:

(i) Try to increase awareness of the IETF and what it does in
those areas, via ISOC chapters, lectures, and other forms of
contact.  Variations on this have been suggested by others.
Note that doing this for a given location would require putting,
at most, one or two people on airplanes (possibly at IETF or
ISOC expense), not order 1000 of us at individual or company
expense.  (See George Michaelson's most recent note in the "IETF
Meeting in South America" thread.)

(ii) Try to assign a document process advisor to each newcomer
the first time that person posts an I-D (or earlier if we can
determine that an I-D is in progress or should be generated from
other discussions).  This is a little different from a mentor
(see Iiii)) in that the role would be to specifically advise on
the process of getting a document through the system, what
obstacles are likely to be encountered, etc., and could be
pretty aggressive if that were necessary.   The process advisor
could recommend that that author seek out other resources,
including a mentor or editorial help, when necessary.  The
IETF's curmudgeon component, many of whom would make lousy
mentors, might still be good document process advisors.

(iii) Allow new participants who intend to participate remotely
and by mailing list to request and be assigned mentors, ideally
mentors who speak the participant's primary language.  Focusing
our efforts only on people who show up at meetings means that we
leave the folks who could be among our more productive
participants in the cold and, for most regions where we have
little penetration and resources are a problem, pretty much
guarantees that it will stay that way.

(iv) Encourage ISOC to redesign the IETF Fellows program so that
people who were reasonable candidates for long-term
participation were tracked differently from the
observer-tourists.   In the potential participant track, the
assumption should be that Fellows might have participated
remotely (including by mailing list) already, that such
participation would give a candidate Fellow some extra priority
or points in the selection process, and that activities during
IETF should include explicit and focused discussions of optimal
ways to participate without attending meetings.  If we (or ISOC,
or other organizations) later get the Fellows to more meetings,
that would be great, but the goal should be to make a good
remote participant, not people who can be effective only if they
attend a lot of face to face meetings.

The above would not be easy.  It would require a large number of
experienced members of the community to make a major commitment
to working with new authors and non-attendee newcomers.  But it
would help significantly to bridge the gap between "interested
in the IETF and its work" and "contributing participant".
Flying a thousand person-weeks worth of folks into an area where
we have little participation and attracting a few local tourists
won't have the same effect --with or without a few hours of
"newcomer" sessions-- and will still leave people with the need
to make that transition if they are going to be effective.

best,
    john



From adrian@olddog.co.uk  Wed May 29 23:53:55 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A06A321F939E for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 23:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nManzVqOTyzI for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 23:53:47 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 479F521F94F5 for <ietf@ietf.org>; Wed, 29 May 2013 23:53:46 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4U6rVKp014944;  Thu, 30 May 2013 07:53:31 +0100
Received: from 950129200 (HKRnf12760.tokyo-ip.dti.ne.jp [27.120.235.10]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4U6rQUA014879 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 May 2013 07:53:29 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Joe Touch'" <touch@isi.edu>, <dcrocker@bbiw.net>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu>
In-Reply-To: <51A65BDD.8040304@isi.edu>
Subject: RE: When to adopt a WG I-D
Date: Thu, 30 May 2013 07:53:24 +0100
Message-ID: <034f01ce5d02$64068630$2c139290$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH8VFWFOMOF4T7j3iZi6HwvX6jttQHGZrOZAstJnqoBa2jBHQHGsb/BAxhMqLwB4mbI6AMFuGGZArMqGx2YLZ+X4A==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 06:53:55 -0000

OK, I think Dave and I are going to discuss this.

I see a wedge :-)
The problem is where to stop.

I completely agree that the current I-D does not cover everything and I =
can see that *some* things can usefully be added.=20

OTOH, if we don't draw lines, mission creep will lead us, step-by-step, =
to attempt to document everything about the IETF in one document. I =
don't want to go there :-)

So I can see this I-D *possibly* becoming a document lifecycle =
description.

I can also see potential for adding some info to the Tao, but the danger =
there is that document becomes too big and too detailed to be of use.

Cheers,
Adrian

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: 29 May 2013 20:50
> To: dcrocker@bbiw.net
> Cc: Dave Crocker; Brian E Carpenter; adrian@olddog.co.uk; =
ietf@ietf.org
> Subject: Re: When to adopt a WG I-D
>=20
>=20
>=20
> On 5/29/2013 11:56 AM, Dave Crocker wrote:
> > On 5/29/2013 7:57 PM, Joe Touch wrote:
> >>
> >> My premise is that when introducing people to a new game, it makes =
sense
> >> to keep things simple and in one place p the TAO.
> >>
> >> You can continue to disagree with that if you prefer.
> >
> > I haven't disagreed with doing that.  I disagreed with saying that =
that
> > document contains everything they need to know.
>=20
> Agreed, but if we have more to say, it would be useful to keep it in a
> single place - esp. given we have that vehicle for doing so.
>=20
> > Entirely different semantics to the two statements.
> >
> > I think it's a dandy starting document.  But it's a really crappy =
'last'
> > document.
>=20
> Good reason to make it better, rather than fracturing that sort of =
info,
> though.
>=20
> > And by the way, the draft that's been put forward isn't just for
> > beginners...
>=20
> Nor is the TAO, AFAICT, either.
>=20
> Joe


From jari.arkko@piuha.net  Wed May 29 23:56:01 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9349121F9679 for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 23:56:01 -0700 (PDT)
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.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIyqHfO6SkjA for <ietf@ietfa.amsl.com>; Wed, 29 May 2013 23:55:57 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id B6DCB21F939E for <ietf@ietf.org>; Wed, 29 May 2013 23:55:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D452B2CC48; Thu, 30 May 2013 09:55:49 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uk_Ub6F_lee4; Thu, 30 May 2013 09:55:47 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 989E02CC3C; Thu, 30 May 2013 09:55:47 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E93@EXMB01CMS.surrey.ac.uk>
Date: Thu, 30 May 2013 09:55:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC219569-6D6F-44EE-9C49-B1538EDA0286@piuha.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com>, <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E93@EXMB01CMS.surrey.ac.uk>
To: l.wood@surrey.ac.uk
X-Mailer: Apple Mail (2.1503)
Cc: mnot@mnot.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: Thu, 30 May 2013 06:56:01 -0000

Lloyd,

> http://www.arkko.com/tools/recrfcstats/d-contdistr.html
> (Jari, what time period is that across? Oceania doesn't rate a =
mention=85)

"Recent RFCs" is anything from RFC 5400 onwards. An arbitrary =
definition.

And Oceania is listed under "Australia" per =
http://en.wikipedia.org/wiki/Continent...

> 11 RFCs (0.73%) have authors from South America.
>=20
> http://www.arkko.com/tools/allstats/fernandogont.html
> This author is in Argentina (as of 2013)
> Fernando has the following 12 RFCs

I need to repeat the warning that someone gave - my statistics are very =
unreliable, particularly when it comes to small numbers. The tools parse =
natural language, and all I can say is that they sometimes guess right. =
But I also looked at this a while ago, and from what I could tell, =
Fernando is responsible for the RFCs from that continent :-) For now=85 =
see below.

> This suggests that itr would be efficient for the IETF to fund travel =
and support for Fernando, who I've met at IETF meetings, rather  than =
fund an IETF meeting in Fernando's neighbourhood (consistently Haedo, =
Provincia de Buenos Aires - address is a better guide than affiliation).

I think we need to look at this topic not with today's numbers but with =
what is possible within a few years. Today, I see several people who are =
making significant contributions to discussion, including some who =
clearly could/should be making RFCs. This will happen, and then there =
are all the other people who could be participating, but are not. Just =
as an anecdotal datapoint, some people at my day job at Ericsson have a =
very successful co-operation with a Brasilian university on IETF-like =
topics.

Jari


From jari.arkko@piuha.net  Thu May 30 00:06:08 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDCB21F96AB for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WtP0YBaDmDem for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:06:02 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id ADB7521F96AA for <ietf@ietf.org>; Thu, 30 May 2013 00:06:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 0CF432CC56; Thu, 30 May 2013 10:06:02 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eyydxAJ7SEZo; Thu, 30 May 2013 10:06:01 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 5B25A2CC48; Thu, 30 May 2013 10:06:01 +0300 (EEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
Date: Thu, 30 May 2013 10:06:01 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BF755FD-468D-47BD-A8FC-27FF3089EF32@piuha.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com> <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.1503)
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: Thu, 30 May 2013 07:06:08 -0000

Mark:

> I would take those numbers with a HUGE grain of salt (as Jari =
documents).

Indeed

> For example, I've lived in Australia since 2006, and yet am only =
listed as producing RFCs in the USA.

My apologies. I added a data item to recognise you=85

Jari


From melinda.shore@gmail.com  Thu May 30 00:06:45 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F77A21F8C40 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.371
X-Spam-Level: 
X-Spam-Status: No, score=-2.371 tagged_above=-999 required=5 tests=[AWL=0.228,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e73PMILj3baU for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:06:39 -0700 (PDT)
Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) by ietfa.amsl.com (Postfix) with ESMTP id 3892821F8CE9 for <ietf@ietf.org>; Thu, 30 May 2013 00:06:39 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id v14so8950358pde.4 for <ietf@ietf.org>; Thu, 30 May 2013 00:06:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3ssvNCmFl2sRwStfhBBpqBVIZucMcplQSP3GznjcA4Y=; b=nhAfMViMxWEjmL2GC/V+UsqsJb6lj+qnVJ47xs2KHsNz60CEOSc45sH5Mpa2UbV+kn vQ+wEeFhRAt+FZA8H76INiDprBvboIjo2IfyXm38ShsN+9/TQBKo4H4f086T/2s1LLBl 2WnJ+7x8/sWtN8V8G5KXXkT+JB44F0wekS3N6UtyoBYiLYYs/Pfwmn+F2F6tiQZ38QLa 5JzEqdrzVkFXxbrhzci1gki8KJR5iQJw6LMSEB1ho8cs38DT2Vcv8HYJdAkIfjw5VNln I7zbGnFM9oGDmRWuEi8moCSUcDOGcQxvsmOcO9+cg/Ob89F0TdbEpBZNFfHC6VFuiPMR O3ew==
X-Received: by 10.66.27.40 with SMTP id q8mr6986162pag.98.1369897598940; Thu, 30 May 2013 00:06:38 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id pm7sm1645366pbb.31.2013.05.30.00.06.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 00:06:38 -0700 (PDT)
Message-ID: <51A6FA7A.30100@gmail.com>
Date: Wed, 29 May 2013 23:06:34 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk>
In-Reply-To: <034f01ce5d02$64068630$2c139290$@olddog.co.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 30 May 2013 07:06:45 -0000

On 5/29/13 10:53 PM, Adrian Farrel wrote:
> I see a wedge :-)
> The problem is where to stop.

Well, I don't know.  Maybe the problem is where to
start.  That is to say, I don't know what problem
this document is trying to solve, or if there even
is a problem.  I know that we've had some major
document quality issues in opsawg and Benoit has
provided some needed guidance on document adoption,
but this doesn't seem to be dealing with that sort
of issue.  Is it that people are confused about when
to adopt a document (or not)?  Is this intended to
provide some sort of context to resolve complaints?
Is this a tutorial?

To be honest at this point I'm sort of reflexively
anti-process-documents, unless there's an actual problem
that needs actual solution.

Melinda


From mnot@mnot.net  Thu May 30 00:06:50 2013
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 5DF2C21F9413 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.246
X-Spam-Level: 
X-Spam-Status: No, score=-105.246 tagged_above=-999 required=5 tests=[AWL=-2.647, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rtjHF1e6ksJw for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:06:43 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF5021F8D31 for <ietf@ietf.org>; Thu, 30 May 2013 00:06:39 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.184.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9BD1D22E1F4; Thu, 30 May 2013 03:06:32 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <5BF755FD-468D-47BD-A8FC-27FF3089EF32@piuha.net>
Date: Thu, 30 May 2013 17:06:28 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <15D656E9-50B5-4333-949B-B31CF4C3B96E@mnot.net>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com> <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net> <5BF755FD-468D-47BD-A8FC-27FF3089EF32@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1503)
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: Thu, 30 May 2013 07:06:50 -0000

Thanks :)

On 30/05/2013, at 5:06 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

>=20
> Mark:
>=20
>> I would take those numbers with a HUGE grain of salt (as Jari =
documents).
>=20
> Indeed
>=20
>> For example, I've lived in Australia since 2006, and yet am only =
listed as producing RFCs in the USA.
>=20
> My apologies. I added a data item to recognise you=85
>=20
> Jari
>=20

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




From hannes.tschofenig@gmx.net  Thu May 30 00:11:49 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D59E21F89D5 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:11:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.189
X-Spam-Level: 
X-Spam-Status: No, score=-100.189 tagged_above=-999 required=5 tests=[AWL=0.952, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4U0kGi5wKiM5 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:11:44 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 8F49A21F8B45 for <ietf@ietf.org>; Thu, 30 May 2013 00:11:40 -0700 (PDT)
Received: from 3capp-gmx-bs39.server.lan ([172.19.170.91]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M52ci-1UV4Va1GF4-00zGyz; Thu, 30 May 2013 09:11:28 +0200
Received: from [194.251.119.196] by 3capp-gmx-bs39.server.lan with HTTP; Thu May 30 09:11:28 CEST 2013
MIME-Version: 1.0
Message-ID: <trinity-e2cf6141-70f9-4459-886d-2872dcfb8ae4-1369897887887@3capp-gmx-bs39>
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: "John C Klensin" <john-ietf@jck.com>
Subject: Aw: What do we mean when we standardize something?
Content-Type: text/html; charset=UTF-8
Date: Thu, 30 May 2013 09:11:27 +0200 (CEST)
Importance: normal
Sensitivity: Normal
In-Reply-To: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K0:b3UCaKW9KO/al3xY7s3QagjMjzFaYXY8HCUu4SsJIx7 T37q3TkZu7RqeS8Zcm86lAraC7N4UOprfQCNduN6gc2dC6oqzu w5Czi1gn7+VA717yKrRJlPCM07rdbbjMXgshFCrNuBFjEyykKe gOv2ye20BWtWGiYYjkuZPRT0w1GVuoubW6OfPDkfUi/kfsa+JG aYBJKdSyGs0XnC4w9CT+lvm+qdQi86IjyYBaq/E1f9YHMhYcKw OYfIC3B4BhBnpIKckMf5El1gc1gDftS0v50d5SxPcPoTPuAnTw sT9h4g=
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, 30 May 2013 07:11:49 -0000

<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Hi John,&nbsp;</div>

<div>&nbsp;</div>

<div>this is a great summary.&nbsp;</div>

<div>&nbsp;</div>

<div>Regarding the question about the type of standardization we want I would argue for a&nbsp;mixture of both si<span style="font-family: Verdana, sans-serif, Arial, &#39;Trebuchet MS&#39;; font-size: 13px; line-height: 1.6em;">nce in&nbsp;practice there are, of course,</span><span style="font-family: Verdana, sans-serif, Arial, &#39;Trebuchet MS&#39;; font-size: 13px; line-height: 1.6em;">&nbsp;a lot of grey areas. I suspect that setting the expectations right at the beginning of starting the work (in a group or on a specific document) are important. I guess it is just the &quot;surprises&quot; that folks get concerned about when they suddenly realize that the last call period isn&#39;t actually something were they can change a lot (even if they dislike something) because the technology is widely deployed already and any change in the spec is likely going to cause a disconnect with the deployment.&nbsp;</span></div>

<div>&nbsp;</div>

<div>Ciao<br/>
Hannes</div>

<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b>&nbsp;Mittwoch, 29. Mai 2013 um 19:23 Uhr<br/>
<b>Von:</b>&nbsp;&quot;John C Klensin&quot; &lt;john-ietf@jck.com&gt;<br/>
<b>An:</b>&nbsp;ietf@ietf.org<br/>
<b>Betreff:</b>&nbsp;What do we mean when we standardize something?</div>

<div name="quoted-content">Hi. A number of recent discussions, specifically including the<br/>
Last Calls on DKIM and standardizing RRTYPEs and even to some<br/>
extent the meeting location ones, have started me thinking that<br/>
perhaps we need to review what business the IETF is actually in<br/>
and to be sure that we actually still agree about it. The note<br/>
that follows is an attempt to take the isolated parts (and<br/>
symptoms) of that discussion up a level and discuss it as a<br/>
general issue.<br/>
<br/>
The key issues go to the very nature of standardization. While<br/>
there are many variations on each, there are two fundamentally<br/>
different models for what standards are about. Each is<br/>
legitimate in its own way and each has its advocates, but they<br/>
are different. One is a focus on quality: an engineering<br/>
consensus on the best technical solution given physics or<br/>
consensus goals and boundary conditions. The other is<br/>
sometimes called &quot;consensus of industry practice&quot; in which a<br/>
standard reflects what is already deployed, possibly picking<br/>
among different implemented options in a few cases but mostly<br/>
requiring that a common model appears before standards are<br/>
issued.<br/>
<br/>
Two variations on the second theme were extremely common in the<br/>
earlier days of computer and telecommunciations standardization<br/>
but are less popular today (at least in theory) due to IPR and<br/>
antitrust concerns. Both start with a single vendor (or closed<br/>
consortium) implementation. That implementation might then be<br/>
offered for standardization (sometimes with a &quot;no major<br/>
changes&quot; restriction) and adopted more generally or endorsed by<br/>
traditional SDOs. Or that single implementation might be<br/>
reverse-engineered by others and then the result treated as<br/>
common industry practice.<br/>
<br/>
Despite the occasional claim that a strange (to me) idea called<br/>
&quot;anticipatory standardization&quot; is a variation on the second<br/>
model, that combination makes standards in the absence of, or<br/>
prior to, implementation and deployment an impossible<br/>
contradiction. It is basically incompatible with innovation of<br/>
any type.<br/>
<br/>
The IETF has traditionally chosen the first model and a great<br/>
deal of our thinking and public rhetoric are based on it. Even<br/>
when we have adopted proposals, sometimes implemented ones,<br/>
from elsewhere, we have insisted on change control and usually<br/>
taken that seriously. One could claim that an adaptation of<br/>
the second model would make the Internet more uniform, but a<br/>
consensus of existing practice cannot aspire to &quot;working<br/>
better&quot; except in the narrow sense of substitutability of<br/>
conforming products.<br/>
<br/>
It is interesting that the multi-stage model of RFC 2026<br/>
(particularly the original &quot;Proposed Standard&quot; definition), the<br/>
IEEE&#39;s &quot;Trial-Use&quot; standards (the current Section 5.7 of their<br/>
Standards Board Operations Manual,<br/>
<a href="http://standards.ieee.org/develop/policies/opman/sect5.html#5.7" target="_blank">http://standards.ieee.org/develop/policies/opman/sect5.html#5.7</a>,<br/>
makes instructive reading), and ISO &quot;Technical Specification&quot;<br/>
all try to combine the two models by allowing a preliminary<br/>
specification --one that is intended for trial implementation<br/>
but not deployment-- to be designed on an engineering basis and<br/>
then standardized only when implementations exist and can be<br/>
compared (our original &quot;Draft Standard&quot;). In theory, only when<br/>
both an industry common practice and consensus about value<br/>
emerges does true standardization (including our original<br/>
definition for &quot;Internet Standard&quot;) move forward. We know how<br/>
well that has worked for us in practice. While there have been<br/>
exceptions, I don&#39;t believe it has worked much better for other<br/>
SDOs.<br/>
<br/>
If we are not going to move significantly in the direction of<br/>
&quot;consensus of industry practice&quot;, then it seems to me that we<br/>
need to be careful about the arguments that are made (or at<br/>
least those that are considered legitimate) in support of<br/>
advancement into or on the standards track.<br/>
<br/>
For example, if we agree on a relaxed registration procedure<br/>
for some protocol parameters, it is not reasonable to later<br/>
turn around and ask that that those parameters be standardized,<br/>
unchanged, because they are already registered (and maybe<br/>
deployed). For standardization, the IETF generally needs not<br/>
only change control but an opportunity to comment on and affect<br/>
the actual design and specification of whatever is being<br/>
standardized.<br/>
<br/>
Similarly, we sometimes hear it argued that we should accept a<br/>
specification for Proposed Standard unchanged because it has<br/>
been extensively developed and reviewed elsewhere. That may be<br/>
reasonable in some cases although I&#39;d hope we wouldn&#39;t make it<br/>
a common practice. But, if a specification adopted for<br/>
Proposed Standard on that basis is then proposed for<br/>
advancement to Internet Standard, I think the review should be<br/>
comprehensive --perhaps even more comprehensive than the usual<br/>
such review-- because the Internet Standard is unambiguously an<br/>
IETF product and recommendation not that of the other body. If<br/>
we allow a specification to advance to Proposed Standard<br/>
without an open and critical review because it was developed<br/>
and reviewed comprehensively by outside expert organizations<br/>
and then allow the Last Call review for Internet Standard to be<br/>
constrained by existing deployment, we would have gone into the<br/>
rubber stamping business that we regularly say is incompatible<br/>
with our standardization model. That doesn&#39;t mean, of course,<br/>
that changes during review for Internet Standard are likely to<br/>
be a good idea. Those who propose changes to the spec, and<br/>
especially to the protocol, should have to convince the<br/>
community that those changes are important enough to overcome<br/>
the costs, including those of incompatibility with deployed<br/>
versions. But I don&#39;t think we can reasonably exclude them<br/>
from raising the issues and making those arguments.<br/>
<br/>
thanks,<br/>
john<br/>
&nbsp;</div>
</div>
</div></div></body></html>

From adrian@olddog.co.uk  Thu May 30 00:17:15 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E441021F9579 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:17:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCizP+0GCLrH for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:17:10 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 4502321F96DB for <ietf@ietf.org>; Thu, 30 May 2013 00:17:07 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4U7H0UY002857;  Thu, 30 May 2013 08:17:00 +0100
Received: from 950129200 (HKRnf12760.tokyo-ip.dti.ne.jp [27.120.235.10]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4U7Gs11002817 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 May 2013 08:16:56 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Melinda Shore'" <melinda.shore@gmail.com>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com>
In-Reply-To: <51A6FA7A.30100@gmail.com>
Subject: RE: When to adopt a WG I-D
Date: Thu, 30 May 2013 08:16:51 +0100
Message-ID: <035101ce5d05$aba61110$02f23330$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH8VFWFOMOF4T7j3iZi6HwvX6jttQHGZrOZAstJnqoBa2jBHQHGsb/BAxhMqLwB4mbI6AMFuGGZArMqGx0CUsD2yAMJu6HqmALCHYA=
Content-Language: en-gb
Cc: dcrocker@bbiw.net, 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: Thu, 30 May 2013 07:17:16 -0000

Hi Melinda,

Funny, but I agree.

> To be honest at this point I'm sort of reflexively
> anti-process-documents, unless there's an actual problem
> that needs actual solution.

Which is why this isn't a process document.

The origin is a WG chairs Edu session. Turns out there was not a lot of =
clarity among a bunch of WG chairs about what they did and why. My =
assumption is that if the chairs needed some time to discuss this, the =
community might need that as well.

The problem I am now hearing is that "the document lifecycle is not =
described coherently in one place." That wasn't the problem I was aiming =
to solve, but maybe enough others consider it is a problem.

> Is this a tutorial?

Mainly. To quote...

      NOTE:    This draft is intentionally non-normative.  It is meant =
as a
      guide to common practice, rather than as a formal definition of
      what is permissible.

Adrian


From melinda.shore@gmail.com  Thu May 30 00:19:10 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4422F21F9696 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:19:10 -0700 (PDT)
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.200,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BUZgcg9z28bW for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:19:09 -0700 (PDT)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id E325821F9579 for <ietf@ietf.org>; Thu, 30 May 2013 00:19:09 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id wz12so10584562pbc.17 for <ietf@ietf.org>; Thu, 30 May 2013 00:19:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=t/Qars33PQlJI148TO8kc8svBM4p71wQB8QskkcNx/8=; b=S52wriXeNf7EJUObxUiq805m3ZzhWITsqqopHALdIH3TTzMGNfbG0QD0aS2DSMSi8C nUjrMbmCq0HRfqzLQ9K9HNMt2rRYyJV4w9UssH6PKlFohH7zfUpfxQRzbyXrtfUc6dag zTmSjSBeUciB+UUcFx0rnsbpFc3Ak3gyyeWT973QM0P5wCdgq9ftKN3W9HPEBlEBtajT l+pF6LYjFlOYrWX2Y5zBom+d52IBvJXVzrh0yuVPmCNMCL02lKE5U+QAecBDK+aKqQKH bsZrkI0r5+9OxXaU93z1ylmHoMlbikbahdiPpXsv3DEWy4y76Bo1tKkxqZYXMnBg55dL ZVQg==
X-Received: by 10.66.226.233 with SMTP id rv9mr7099331pac.155.1369898349683; Thu, 30 May 2013 00:19:09 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id iq2sm6234688pbb.19.2013.05.30.00.19.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 00:19:08 -0700 (PDT)
Message-ID: <51A6FD6A.3030608@gmail.com>
Date: Wed, 29 May 2013 23:19:06 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com> <035101ce5d05$aba61110$02f23330$@olddog.co.uk>
In-Reply-To: <035101ce5d05$aba61110$02f23330$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 30 May 2013 07:19:10 -0000

On 5/29/13 11:16 PM, Adrian Farrel wrote:
> Which is why this isn't a process document.

Are you sure?

Melinda



From dhc@dcrocker.net  Thu May 30 00:24:28 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7074121F942B for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vr4kh8avoofa for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:24:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 83A9B21F882A for <ietf@ietf.org>; Thu, 30 May 2013 00:24:23 -0700 (PDT)
Received: from [173.255.178.219] (219.178.255.173.client.dyn.strong-mf8.as54203.net [173.255.178.219]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4U7ODTF025071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 May 2013 00:24:19 -0700
Message-ID: <51A6FE97.4010708@dcrocker.net>
Date: Thu, 30 May 2013 09:24:07 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com>
In-Reply-To: <51A6FA7A.30100@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 30 May 2013 00:24:20 -0700 (PDT)
Cc: adrian@olddog.co.uk, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 07:24:28 -0000

On 5/30/2013 9:06 AM, Melinda Shore wrote:
> On 5/29/13 10:53 PM, Adrian Farrel wrote:
>> I see a wedge :-)
>> The problem is where to stop.
>
> Well, I don't know.  Maybe the problem is where to
> start.  That is to say, I don't know what problem
> this document is trying to solve, or if there even
> is a problem.


Like you, I think we need to be very careful about creating stray 
process documents or... stray processes.

That said, we have processes and we need to do them well.

The IETF permits an extraordinary degree of flexibility in much of the 
detail for doing the actual work. The main benefit is that it lets a 
group adjust its style of work according to the nature of the work and 
the preferences of the workers.

A small, well-integrated group that is focusing on a narrow, 
well-understood topic can reasonably use a very different daily style 
than a large, highly heterogeneous group that is working on a difficult, 
poorly understood topic.

Currently, that tends to mean that folk invent things on the fly, often 
importing models from other groups.  Both the spontaneous invention and 
the importation risk assorted problems ranging from serious inefficiency 
to outright mismatch with the culture.

What we've lacked is much effort to capture 25+ years of experience of 
doing the grunt work of IETF daily management.  We don't really pass on 
the culture very well, beyond some clever catch phrases and formal 
process structure and criteria specifications.

So the intent of the current draft is to capture one aspect of the 
collective wisdom and pass it on to others.  It is "us" -- all of us -- 
speaking to "them", as if sitting around the bar, talking about how to 
get things done.

The document is quite explicit that it has no force other than 
representing some collective wisdom.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From adrian@olddog.co.uk  Thu May 30 00:56:36 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 203B421F8825 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7RUXrbswOlru for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:56:30 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 176D821F88A9 for <ietf@ietf.org>; Thu, 30 May 2013 00:56:29 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4U7uLKD023702;  Thu, 30 May 2013 08:56:22 +0100
Received: from 950129200 (HKRnf12760.tokyo-ip.dti.ne.jp [27.120.235.10]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4U7uGGa023612 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 May 2013 08:56:18 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Melinda Shore'" <melinda.shore@gmail.com>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com> <035101ce5d05$aba61110$02f23330$@olddog.co.uk> <51A6FD6A.3030608@gmail.com>
In-Reply-To: <51A6FD6A.3030608@gmail.com>
Subject: RE: When to adopt a WG I-D
Date: Thu, 30 May 2013 08:56:12 +0100
Message-ID: <000001ce5d0b$2ad63d70$8082b850$@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: AQH8VFWFOMOF4T7j3iZi6HwvX6jttQHGZrOZAstJnqoBa2jBHQHGsb/BAxhMqLwB4mbI6AMFuGGZArMqGx0CUsD2yAMJu6HqAxkcUrkClD7oGJfVWkbg
Content-Language: en-gb
Cc: dcrocker@bbiw.net, 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: Thu, 30 May 2013 07:56:36 -0000

> > Which is why this isn't a process document.
> 
> Are you sure?

Oooh, a quiz. I like quizzes.

Let me see. Yes or no. Hmmm.

Yes, I'm sure.

Your turn now.

Are you sure?

Ciao,
Adrian


From melinda.shore@gmail.com  Thu May 30 00:58:43 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97EDE21F97D7 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:58:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzKrXBhj4BJb for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 00:58:43 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 2175A21F97C7 for <ietf@ietf.org>; Thu, 30 May 2013 00:58:43 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ro12so10602633pbb.27 for <ietf@ietf.org>; Thu, 30 May 2013 00:58:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=F+lxRdxjtYxUQsyjttyz0Yj0mLJoNuz2Yd2fV0gPlcU=; b=SlwXuewRgvH7BLJczyIKqv7z6FATRJ45WbKJAX4n4Kn6uDeiezXwqNWGI7pGE2eQ6R 96CG9q2RVNAGMlyE1qS7tyQL68S6IX6BUC/gnu1YzWlkckOL9r/+jHqbJr9iYJPzpynP odA7m1qL+MzgmBU9G+wJAj+O/Nt9ySytc9XUE9UkEn2P/CDExOGZkeuRd0iGunLob4D8 a96RSr20hzuhZOTlXt1B9SnZpL+iZcwAlnOMqXakrBz1D3LAqFJiqGMXwn6ffALSxpyZ 9xlDv6VKo/NQx9kBN3QHZ+stlovkLQqctaXSyeXauKhD1qob1mky3ONFetcX7pZc/c2V xVQQ==
X-Received: by 10.68.232.67 with SMTP id tm3mr6585891pbc.204.1369900722917; Thu, 30 May 2013 00:58:42 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id q18sm43653338pao.4.2013.05.30.00.58.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 00:58:42 -0700 (PDT)
Message-ID: <51A706AF.50200@gmail.com>
Date: Wed, 29 May 2013 23:58:39 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com> <035101ce5d05$aba61110$02f23330$@olddog.co.uk> <51A6FD6A.3030608@gmail.com> <000001ce5d0b$2ad63d70$8082b850$@olddog.co.uk>
In-Reply-To: <000001ce5d0b$2ad63d70$8082b850$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Thu, 30 May 2013 07:58:43 -0000

On 5/29/13 11:56 PM, Adrian Farrel wrote:
> Yes, I'm sure.
> Your turn now.
> Are you sure?

No, not at all.

Melinda



From dhc@dcrocker.net  Thu May 30 01:06:18 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B9821F93E6 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 01:06:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bw25CtnNdqdg for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 01:06:13 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 95B7121F8266 for <ietf@ietf.org>; Thu, 30 May 2013 01:06:13 -0700 (PDT)
Received: from [173.255.178.219] (219.178.255.173.client.dyn.strong-mf8.as54203.net [173.255.178.219]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4U864JM025809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 May 2013 01:06:09 -0700
Message-ID: <51A70865.3070605@dcrocker.net>
Date: Thu, 30 May 2013 10:05:57 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: When to adopt a WG I-D
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com> <035101ce5d05$aba61110$02f23330$@olddog.co.uk> <51A6FD6A.3030608@gmail.com> <000001ce5d0b$2ad63d70$8082b850$@olddog.co.uk> <51A706AF.50200@gmail.com>
In-Reply-To: <51A706AF.50200@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 30 May 2013 01:06:10 -0700 (PDT)
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 08:06:18 -0000

On 5/30/2013 9:58 AM, Melinda Shore wrote:
> On 5/29/13 11:56 PM, Adrian Farrel wrote:
>> Yes, I'm sure.
>> Your turn now.
>> Are you sure?
>
> No, not at all.


Let me try to help...

A process document is a normative statement of structure and sequence 
for a process.  It is the organization's means of saying how things must 
be done.  That 'must' might include degrees of freedom, of course, but 
they key point is that whatever it specifies has formal authority within 
the organization.

The current draft is quite explicitly not that.

The current draft is a kindly mentor, sitting around the bar, imparting 
sage advice for how something can be reasonably done, within the formal 
bounds of IETF rules and culture.

It's only 'force' is whatever credibility the individual reader choose 
to assign to the text, as is true for any "Informational" RFC...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From sm@resistor.net  Thu May 30 01:34:18 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D34A21F96A0 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 01:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.274
X-Spam-Level: 
X-Spam-Status: No, score=-102.274 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y7qGl5iVsgsx for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 01:34:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A26D921F89D5 for <ietf@ietf.org>; Thu, 30 May 2013 01:34:17 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4U8Y5qp013719; Thu, 30 May 2013 01:34:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369902851; bh=rL04XnE47JWMS2JqdVkax3A5HB3riC8L+ZvcIvpL2Zk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1jzUFuGjNYbkI6SbLjVEzjory6ZiGef+mWz9PEwT4v1SU7itO1/znNsCfNvDUhz0I T5OnGgvN8JA312tXDkhDz6cwrCW4nxRAmwxKVFZyBTwX3c7AEKXuV9bK35RxIVtdi3 NBFYgefSAn3+kGR3J8lbuyKkaI+OTlNZ1jZvQqoI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369902851; i=@resistor.net; bh=rL04XnE47JWMS2JqdVkax3A5HB3riC8L+ZvcIvpL2Zk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lOfSa93FaIgbokQ+BWlpquBni4Q/BW3bxIukkJLfNvY8NgO2SE5Bafwkda2P4kk4k Mlb4l+VSgHXsTNUKcE5bIV2pANWyt/QYJD0D3loBBibO24vspa0kL3lyjlWNPdidl8 r8BNp5AZUCV54Icgt/XsP48kECAfRGcX3n1DWDek=
Message-Id: <6.2.5.6.2.20130529225754.0bd431a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 30 May 2013 01:10:35 -0700
To: Ted Lemon <Ted.Lemon@nominum.com>, Joe Abley <jabley@hopcount.ca>
From: SM <sm@resistor.net>
Subject: Re: Last  Call:	<draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource  R	ecords for EUI-48 and EUI-64 Addresses in the DNS)	to	Proposed Standard
In-Reply-To: <8D23D4052ABE7A4490E77B1A012B6307751BA3A0@mbx-01.win.nominu m.com>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com> <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net> <8D23D4052ABE7A4490E77B1A012B6307751BA3A0@mbx-01.win.nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 08:34:18 -0000

At 15:21 29-05-2013, Ted Lemon wrote:
>I didn't say that I support the draft; just what I think could be 
>done to somewhat mitigate its scope.   My personal (non-hat) feeling 
>about the draft is that if there is

I did not read those messages as meaning that you support the draft 
or that there was anything negative.

At 18:34 29-05-2013, Joe Abley wrote:
>The original motivation for requesting code-point assignments for 
>new RRTypes which would facilitate a clean encoding of EUI-48 and 
>EUI-64 addresses in the DNS resulted from my distaste for the 
>evident lack of consistency in approach taken in response to the 
>CRTC's general requirement that cable operators publish this kind of 
>data in the DNS, for internal, authenticated access by resellers of 
>their access networks in Canada.
>
>It's not at all certain or even likely that the CRTC-mandated 
>systems will ever use these RRTypes. That ship has surely sailed. 
>The reason for requesting the code-points was to make future such 
>situations less messy, and more likely to result in DNS schemas (if 
>that's a phrase) that were consistent and parseable.
>
>Code-points were assigned following the documented process, which 
>relies upon expert review. To support that review, I wrote a 
>specification for their use as an I-D (intended status: 
>experimental). Note that by specification I mean a technical 
>description of the encoding and protocol considerations associated 
>with EUI48 and EUI64, and not any kind of applicability statement or 
>guidance for how the RRTypes should be used.
>
>I've had feedback from a small number of people who are already in 
>the habit of publishing MAC addresses in the DNS as part of (as I 
>understand it) inventory management and internal troubleshooting. I 
>take no position here on whether that's a good idea, but I conclude 
>that publishing such data in the DNS happens today, regardless of 
>the availability of the EUI48 or EUI64 RRTypes.
>
>The new RRTypes have since been implemented in the code base of 
>BIND9, NSD, Knot DNS and PowerDNS based on that specification.
>
>After some discussion in dnsext, directly with individual 
>contributors and with Joel as Ops Area AD, the draft was revised. 
>Text was added, including the general use case for storage of this 
>data in the DNS mandated by the CRTC (requested by Joel). The 
>intended status was changed to standards track, since I was told 
>that made sense.
>
>After last-call discussions on this list the intended status was 
>changed to informational, and more textual changes were made.
>
>The stated reason for publishing this draft in the RFC series (I'm 
>stating it now!) is that the RFC series is the most obvious place 
>for anybody to look for a specification about the implementation of 
>these RRTypes. That's it.

The above is what I understood.

>So, in summary:
>
>1. There is, I would suggest, a stable specification.
>
>2. Code points are assigned.
>
>3. There are multiple implementations.
>
>4. There are multiple use-cases, and multiple examples of these data 
>types being published in the DNS today (note, I am not suggesting 
>that widespread use is likely or sensible.)
>
>5. It would be useful (I would assert) that the specification can 
>actually be found by people in the future who care about it.
>
>In my mind, this suggests publication of the spec in the RFC series, 
>where it can join other specifications for the encoding of IPv4, 
>IPv6, NSAP, E.164, X.25, ISDN, ATM, NIMROD, HIP, and ILNP addresses. 
>I may have missed some.

There was once a case of a specification which had seven 
implementations and the publication path hit the IETF heavy tail.  In 
the current case publication has been requested in the IETF 
Stream.  There are some differences between the IETF Stream and other 
Streams (in my opinion).

On a different thread and obviously in a different context John 
Klensin mentioned that:

   "For example, if we agree on a relaxed registration procedure
    for some protocol parameters, it is not reasonable to later
    turn around and ask that that those parameters be standardized,
    unchanged, because they are already registered (and maybe
    deployed).  For standardization, the IETF generally needs not
    only change control but an opportunity to comment on and affect
    the actual design and specification of whatever is being
    standardized."

RFC 6895 was reviewed by the IETF community.  RFC 6195 was reviewed 
by the IETF community.  I won't claim that I did not read them or 
that I did not have the time to review and comment about the proposals.

How does privacy fit into all this?  Well, that's what the IAB has 
been talking about.

The following objection was posted to the mailing list:

   "- The IETF, an international standards body, believes itself to be
      the wrong forum for designing protocol or equipment features that
      address needs arising from the laws of individual countries,
      because these laws vary widely across the areas that IETF standards
      are deployed in.  Bodies whose scope of authority correspond to a
      single regime of jurisdiction are more appropriate for this task.

    - The IETF sets standards for communications that pass across
      networks that may be owned, operated and maintained by people from
      numerous jurisdictions with numerous requirements for privacy.  In
      light of these potentially divergent requirements, the IETF
      believes that the operation of the Internet and the needs of its
      users are best served by making sure the security properties of
      connections across the Internet are as well known as possible.  At
      the present stage of our ignorance this means making them as free
      from security loopholes as possible."

The text I suggested was based on my reading of the above.

Regards,
-sm 


From rogaglia@cisco.com  Thu May 30 04:15:59 2013
Return-Path: <rogaglia@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 3712621F93DE for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 04:15:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHf+Ql5KoR9D for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 04:15:54 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id D1C9621F938E for <ietf@ietf.org>; Thu, 30 May 2013 04:15:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13756; q=dns/txt; s=iport; t=1369912554; x=1371122154; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=B/hVisRqGK0b9WxU3IAGuwAxFuF0qS0y87VfMUC4zhc=; b=ITJKdMHFiAdCwnudk/+9nHbwE1upPvoQ9wYpx/ucqSJNa8xWKYxZFjbb //5uFlLrxbz+K9NlXMab1v+aX9n9P8IiN7f2YKJIxFUVSRgjD4FOZbUKQ 7d/GShNMszaXE4q5fNZU7snBph8bXQdUoYsseIaC8zJow2aCqImKj8mW9 Y=;
X-Files: smime.p7s : 4459
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0GAII0p1GtJXG+/2dsb2JhbABZgwkwwgt8FnSCIwEBAQMBaAEBBQoFCwIBCA4KCiQCHxElAgQOBQgGh20DCQYMsGQNiQCMPIImMQIFCYJtYQOPfoErhCyDD4p0hSODD4In
X-IronPort-AV: E=Sophos;i="4.87,770,1363132800";  d="p7s'?scan'208";a="216752892"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-4.cisco.com with ESMTP; 30 May 2013 11:15:47 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r4UBFlQq014176 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 May 2013 11:15:47 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.15]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Thu, 30 May 2013 06:15:46 -0500
From: "Roque Gagliano (rogaglia)" <rogaglia@cisco.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Participation per Region of Authoring IETF documents vs Marketing
Thread-Topic: Participation per Region of Authoring IETF documents vs Marketing
Thread-Index: AQHOXScHKeBrZD5rPkaql1AskBF6ZQ==
Date: Thu, 30 May 2013 11:15:45 +0000
Message-ID: <EF4348D391D0334996EE9681630C83F0220E641E@xmb-rcd-x02.cisco.com>
References: <CADnDZ88O3-VeMZ1Gr4WeSLQg54Ppdus58AHkU0+khuPejzxKZw@mail.gmail.com> <862C9338-9741-4B69-96A2-9C432D0CE82C@netapp.com> <CADnDZ8-EtXKKEDy7Csr6cs_VXtMUeZfjDRt7E909s__zZqFxxA@mail.gmail.com> <9808B94E-20F8-4F92-9101-10EFE31A8F9D@netapp.com> <CADnDZ8-oBZCjiSSmdrjUwyQzw-wF27rOUBdUCosYa_1uAxF2kg@mail.gmail.com> <7D6BB4F3-5F8C-47CA-83D8-F05577D09F34@netapp.com> <CADnDZ8-TjoJBRi1giTESNSp_c3ygdOPUcP+rAV6vP4gtNh2+sA@mail.gmail.com> <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
In-Reply-To: <124BC3D5-D4C0-4769-8134-91838D586A74@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [144.254.17.107]
Content-Type: multipart/signed; boundary="Apple-Mail=_11F4BCBF-B0CE-45FD-A1E0-F30536E97C89"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
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: Thu, 30 May 2013 11:15:59 -0000

--Apple-Mail=_11F4BCBF-B0CE-45FD-A1E0-F30536E97C89
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On May 30, 2013, at 2:45 AM, Mark Nottingham <mnot@mnot.net> wrote:

> I would take those numbers with a HUGE grain of salt (as Jari =
documents).

I appreciate Jari's effort and use his page extensively. However, I =
agree taht geography data should be taken with a grain of salt.

In my case I created several document while living in South America but =
moved to Europe just before the RFC was published with my current =
european address. So, even if I worked on it for 3+ years from LATAM, =
those document show me as european. You also have to consider all the =
native people from one region that move to another one.

My proposal to the "diversity working group" was to add a request from =
the RFC editor to the authors to establish the geography they would like =
to be associated with and add that information to the document metadata =
at publication time.

If we want to tackle the cause of this problem and not the consequences, =
we need to look at the macro-economical issues mentioned by Joel. That =
said, I am optimistic that we will see improvements sooner than later =
thanks to new research/development centres been established in LATAM but =
these processes take time.

Referring to what the impact of hosting a meeting in LATAM would have on =
participation, we need to consider that IETF meetings are not conference =
but working meeting. We get there (or online) to get work done. =
Presentations last only around 5-10 mins they are not marketing-sexy and =
they normally start with "difference from last meeting". What I want to =
say is that engagement needs to happen much earlier and while having a =
meeting in a location will always have a positive effect on local =
participation (as stated by Michael), we need to set expectations right.

Personally, I believe we should spend more energies from now to that =
date working on mentoring and improving the fellowship program. I was =
involved in the first 3 years of the program and I recommended the =
creation of the "recurrent" fellows (initially fellows could only attend =
one meeting). Although I  am still in contact with my past mentees, I =
think there is still room for improvement and we could think on a =
long-distance volunteering program. =20

Referring to the chosen location (Buenos Aires), I think it is an =
excellent choice from the point of view of our traditional requirements =
to get job done. However, the comments about the current exchange and =
import limitations are relevant and should be evaluated by the IAOC when =
establish the current risks or running the meeting there from an =
operational perspective. Typical business operations such as the =
possibility of charging local sponsorships or local attendees in USD, =
been able to wire the hotel IETF fees back to the US in USD (and at a =
reasonable exchange rate) or importing devices to run the meeting should =
not be taking for granted but should be discussed with our local =
contact.=20

Roque


> For example, I've lived in Australia since 2006, and yet am only =
listed as producing RFCs in the USA.
>=20
> Regards,
>=20
>=20
> On 30/05/2013, at 10:39 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
>=20
>> Hi Lars,
>>=20
>> It was for Asia region, I thought its rate is between (5 - 50)
>> rfc/year for last 3 years. Basing on; The first figure of RFCs is the
>> Comparison of countries over the year [1], the second, is the
>> Distribution of number of RFCs per continent [2], the third is
>> publication rate per year [3]. For the I-Ds going in IETF is seen =
from
>> the distribution of drafts according to the countries of their =
authors
>> [4] and [5]. All figures make together the below conclusions, even
>> though some of them need more details for readers to understand.
>>=20
>> As from Figure [1] always one region (North America) is doing about
>> 200 rfc/year and the each of others may do between 5 - 50 rfc/year or
>> 50-100, but all together other regions do 150 rfc/year, so total
>> ietf-participation can be about 350 rfc/year. The Figure [2] is not
>> reasonable, not showing of years or period of such numbers.
>>=20
>> So my understanding is that for Europe-region and Asia-region, the
>> number of I-Ds rates are high compared to North America, but not the
>> rate of RFCs. I see that the total RFCs ietf-output rate (RFC/year) =
as
>> in Figure [3] for the last three years is about 350 rfc/year, so if
>> North America is having 200, the all others only will have about 150
>> rfc/year. The total RFCs produced per countries is in Figure [6] is
>> reasonable but if compared with Figure [2] I get lost.
>>=20
>> =46rom Figure [5] (also [4]) the number of I-Ds (now currently 2013
>> outstanding) from Asia and Europe are about 600 and 1200 respectively
>> (let us add them up so =3D1800 ids), which I think only about 150 =
will
>> succeed (non-North America drafts). Furthermore, for North America =
the
>> I-Ds are 1500 ids and only 200 ids will succeed to become RFCs. I
>> think that Asia and Europe should have together about 250/year rfc =
not
>> 150 rfc/year. If we do more MARKETING effort we can make that =
rfc-rate
>> of other regions increase, but we already tried to increase North
>> America rate but it is stable for about 200 rfc/years.
>>=20
>> [1] http://www.arkko.com/tools/rfcstats/countrydistrhist.html
>> [2] http://www.arkko.com/tools/recrfcstats/d-contdistr.html
>> [3] http://arkko.com/tools/rfcstats/pubdistr.html
>> [4] http://www.arkko.com/tools/stats/d-countrydistr.html
>> [5] http://www.arkko.com/tools/stats/d-countryeudistr.html
>> [6] http://www.arkko.com/tools/rfcstats/d-countrydistr.html
>>=20
>> This lower participation from regions like Asia will continue because
>> most meeting are in North America, or most participants from North
>> America prefer to have face-face meeting locally, than to be remote =
to
>> other regions (not reasonable because they are writers in English =
very
>> well). Also other regions participants prefer to participate in
>> meetings not remotely (but that is reasonable because they are not
>> good in English Language Writting). It is also important that some
>> IETF management visit the other region participants for the progress
>> of their I-Ds.
>>=20
>> Please note that I don't claim that my analysis is all correct, but
>> trying to discuss it and get others to analyse as well or comment on
>> the figures/statistics. If you disagree or have any comment please
>> reply/advise. Thanking you,
>>=20
>> AB
>>=20
>>=20
>> On Wed, May 29, 2013 at 10:53 AM, Eggert, Lars <lars@netapp.com> =
wrote:
>>>=20
>>> Hi,
>>>=20
>>> On May 28, 2013, at 19:46, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
>>>> by looking into the statistics of I-Ds and RFCs, it is strange that =
we get
>>>> sometimes high rate in the I-D going in IETF from some regions but =
the
>>>> success rate of I-Ds to become RFCs is very low (5- 50).
>>>=20
>>> which IDs and RFCs are you basing this statement on?
>>>=20
>>> Thanks,
>>> Lars
>=20
> --
> Mark Nottingham   http://www.mnot.net/
>=20
>=20
>=20


--Apple-Mail=_11F4BCBF-B0CE-45FD-A1E0-F30536E97C89
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSTCCBkIw
ggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0aG9yaXplZCB1c2Ug
b25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJpbWFyeSBDZXJ0aWZpY2F0
aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIxMDgzMTIzNTk1OVowgaYxCzAJ
BgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UECxMWU3ltYW50
ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQD
Ey5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn/R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEi
VzAhJZCao/SsKsaIF4ZhchN2LuwDyyebjyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+Dey
xtmSSq5937hEH5u6P4wG/tgjT0hRI2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/
xhR7DtryBeTTgwKmxWlwtKnkVunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28
ODC7iCbDZ2ZmtLR3+cChxw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQAB
o4ICRDCCAkAwOAYIKwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVy
aXNpZ24uY29tMBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBS
MCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpo
dHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl
cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAY
BgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXECl4aATCB
8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIElu
Yy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZl
cmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWdu
IENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItb
dVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaPwdqbiPKzbE0fWC+6AVFddMFG6MO4
e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKMYJsrnGVJlMSiOCRIpVylUEto6WIip5Po
mSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBiTe/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP9
5WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26tlcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4
OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXi
dE0HbYQwggb/MIIF56ADAgECAhAYf+/XztcT+E2kExj0ut5oMA0GCSqGSIb3DQEBBQUAMIGmMQsw
CQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFu
dGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UE
AxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzA1
MTQwMDAwMDBaFw0xNDA1MTUyMzU5NTlaMIHEMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0
ZWQgLSAxMzY4NTI0MDEwMDczMSEwHwYJKoZIhvcNAQkBFhJyb2dhZ2xpYUBjaXNjby5jb20xDzAN
BgNVBAsMBlMvTUlNRTEeMBwGA1UECwwVUGVyc29uYSBOb3QgVmFsaWRhdGVkMR8wHQYDVQQLDBZT
eW1hbnRlYyBUcnVzdCBOZXR3b3JrMR0wGwYDVQQKDBRTeW1hbnRlYyBDb3Jwb3JhdGlvbjCCASIw
DQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL/aDENz/1kQVeEyPK5cHw3n9c4ErU13WONPXjL7
fHYj0Yr/DSGbdyiWZ001bkIMPxvJbxv4r5EaTq72gHxhTF/frLoM5+sEKAErBPuOqpAAYlxo4uyK
U1pQzPy+3rtlVRStNUAJZHVN4kYtHRghGoBCkqh2JoSBMCgc41Mr1UvS3dI4kp5lKEqutKjoDtdc
/O4Kee/CLzEy0D8QNOF7OSjrPmed1jsAxxqsv9EHMJvG9z/CIXF2Q/kYf24ozeujCPZVaOTjWVsd
BsZSNUaD9LyeGQBtGCXq7e0rUEFPZfsdxUoBoVeTYRYIcloFuiG4QQsvjr6rlFZDbXEhOWOJnRsC
AwEAAaOCAwcwggMDMAwGA1UdEwEB/wQCMAAwDgYDVR0PAQH/BAQDAgWgMCAGA1UdJQEB/wQWMBQG
CCsGAQUFBwMEBggrBgEFBQcDAjAdBgNVHQ4EFgQU+K3xGZv+qs21HN5cJGWwMOyfwHcwHQYDVR0R
BBYwFIEScm9nYWdsaWFAY2lzY28uY29tMB8GA1UdIwQYMBaAFK35w5NyLbW5KGHkpNdg1cQKXhoB
MIIBKwYIKwYBBQUHAQEEggEdMIIBGTCCARUGCCsGAQUFBzAChoIBB2xkYXA6Ly9kaXJlY3Rvcnku
dmVyaXNpZ24uY29tL0NOJTIwJTNEJTIwU3ltYW50ZWMlMjBDbGFzcyUyMDElMjBJbmRpdmlkdWFs
JTIwU3Vic2NyaWJlciUyMENBJTIwLSUyMEc0JTJDJTIwT1UlMjAlM0QlMjBQZXJzb25hJTIwTm90
JTIwVmFsaWRhdGVkJTJDJTIwT1UlMjAlM0QlMjBTeW1hbnRlYyUyMFRydXN0JTIwTmV0d29yayUy
QyUyME8lMjAlM0QlMjBTeW1hbnRlYyUyMENvcnBvcmF0aW9uJTJDJTIwQyUyMCUzRCUyMFVTP2NB
Q2VydGlmaWNhdGU7YmluYXJ5MF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9wa2ktY3JsLnN5bWF1
dGguY29tL2NhXzU2MWMxMDM2OTBjOTdhNjkyNDdhMGVmMDcxYWM4MWFmL0xhdGVzdENSTC5jcmww
bAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsGAQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1
dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRwOi8vd3d3LnN5bWF1dGguY29tL3JwYTArBgpg
hkgBhvhFARADBB0wGwYSYIZIAYb4RQEQAQICBAGGx85vFgUxMDkyMjA5BgpghkgBhvhFARAFBCsw
KQIBABYkYUhSMGNITTZMeTl3YTJrdGNtRXVjM2x0WVhWMGFDNWpiMjA9MA0GCSqGSIb3DQEBBQUA
A4IBAQA9KvHI6pN0/W4MJl3cATuTU0cdkjZBvfztljunVmn72rij+hJKzSg8lGawguiccFWVqqEl
sMIAinuB1zqFe1ILchliltXEj5vPI+HyGxn5akhQuzk7/hmAfs00CC1hbC1HB8r+b7R2s/bkJ7YY
fpE0lMd7exB62MccwKh5yFCgxIvxG/irFLjNicpW/C6ixzmuPoKQO9Rs5H9oBnYVxtGpORPt6H5+
DINZOpsbDcnNgi3mIpSK0lapSzVUueOWBJwS5sfjOLe5pBbpvarrZp0zs0gADupX5u1bH0DpSwj1
zN5wP/p5f2h0L2i4rpaU05LLgBzh0JTy+zidLpU8NgAhMYID5DCCA+ACAQEwgbswgaYxCzAJBgNV
BAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UECxMWU3ltYW50ZWMg
VHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5T
eW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEc0AhAYf+/XztcT+E2k
Exj0ut5oMAkGBSsOAwIaBQCgggH9MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEzMDUzMDExMTU0N1owIwYJKoZIhvcNAQkEMRYEFMxxzt+l2bcb9hTz03pY4scqhoRC
MIHMBgkrBgEEAYI3EAQxgb4wgbswgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBD
b3Jwb3JhdGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVy
c29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg
U3Vic2NyaWJlciBDQSAtIEc0AhAYf+/XztcT+E2kExj0ut5oMIHOBgsqhkiG9w0BCRACCzGBvqCB
uzCBpjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBvcmF0aW9uMR8wHQYDVQQL
ExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQx
NzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzQC
EBh/79fO1xP4TaQTGPS63mgwDQYJKoZIhvcNAQEBBQAEggEAjVKrpSwROhvm7AMYnpwVTQpPMMdW
8BHjG9540SMb6Nv6bZI494zbsgzAlkgnye4J8rG77aloVdrlZ5ge7438j/KZvHkB7ZOIaT5tLVs9
LDvCQbNYILZjJOYsGNAcEkNvZur98QYJdx2tJ00Z/bZ4KMtKLzpJvzlKGWhqOuXlMTwrF2hUTaHw
DDdIRnzZujt5+A6aLZGbRuQrhb8PkktcOW/F3H1CNhN84acNKxHK1aIELE/xHI0FnqfIQOnPsBjk
TtzVjFB/L+rOcBnoZ+9yNsZn86xNhUrJFHAiyt8SNCyxsvcrt1m4vfW9KUsw6h7W+r99nhiiJ3C0
Ix2n7wiTkAAAAAAAAA==

--Apple-Mail=_11F4BCBF-B0CE-45FD-A1E0-F30536E97C89--

From mcr@sandelman.ca  Thu May 30 06:11:24 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 010C121F85BF for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 06:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.143
X-Spam-Level: 
X-Spam-Status: No, score=-3.143 tagged_above=-999 required=5 tests=[AWL=1.456,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQ-otWGJfZYD for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 06:11:18 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id EC08621F90CD for <ietf@ietf.org>; Thu, 30 May 2013 06:11:17 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 8972720184; Thu, 30 May 2013 09:23:50 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id E084363A8C; Thu, 30 May 2013 09:09:58 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id CA409639DF; Thu, 30 May 2013 09:09:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Joe Abley <jabley@hopcount.ca>, iab@iab.org
Subject: Re: Last Call: <draft-jabley-dnsext-eui48-eui64-rrtypes-03.txt> (Resource R ecords for EUI-48 and EUI-64 Addresses in the DNS) to Proposed Standard
In-Reply-To: <9EF99F12-AD4D-4BDB-81A9-12D6E9DF3965@hopcount.ca>
References: <51A37E8A.9010506@bogus.com> <m2sj18dln6.wl%randy@psg.com> <CAF4+nEG=JGUcM3_QA+rW-B163dZf4Bx_yPKJOr9J+vuQFOuhMQ@mail.gmail.com> <m27gij61wi.wl%randy@psg.com> <DFE3023D474039B828B19D6D@JcK-HP8200.jck.com> <m2ehcr48pa.wl%randy@psg.com> <AC453FD4F3816FEF077618EE@JcK-HP8200.jck.com> <m2ppwb2kvj.wl%randy@psg.com> <20130528160803.GC28387@mx1.yitter.info> <m27gii3c1j.wl%randy@psg.com> <20130529162539.GJ34296@mx1.yitter.info> <8EB27539FAE94CBE5EB8A0D9@JcK-HP8200.jck.com> <8D23D4052ABE7A4490E77B1A012B6307751B8EB2@mbx-01.win.nominum.com> <6.2.5.6.2.20130529140524.0ed3d9a8@resistor.net> <62037E40-A130-41F0-A0D5-0B2A1B89AABA@nominum.com> <8D23D4052ABE7A4490E77B1A012B6307751BA488@mbx-01.win.nominum.com> <9EF99F12-AD4D-4BDB-81A9-12D6E9DF3965@hopcount.ca>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 30 May 2013 09:09:58 -0400
Message-ID: <14320.1369919398@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 13:11:24 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Joe" =3D=3D Joe Abley <jabley@hopcount.ca> writes:
    >> Okay, I felt a bit embarrassed about having said this, so I went
    >> back and reviewed the justification for bringing this forth as an
    >> IETF document.   The stated reason for publishing the document as
    >> an IETF document is that there is a regulatory requirement in
    >> Canada to implement something like this.=20

    Joe> No, that's not right (and really, if that's how you read the
    Joe> document at hand then clearly I need to re-write it). Let's
    Joe> review.=20

    Joe> The original motivation for requesting code-point assignments
    Joe> for new RRTypes which would facilitate a clean encoding of
    Joe> EUI-48 and EUI-64 addresses in the DNS resulted from my
    Joe> distaste for the evident lack of consistency in approach taken
    Joe> in response to the CRTC's general requirement that cable
    Joe> operators publish this kind of data in the DNS, for internal,
    Joe> authenticated access by resellers of their access networks in
    Joe> Canada.=20

okay, fair enough.
Given that the CRTC mandated them, why wasn't the IETF involved earlier?
The regulator really should have reached out to the IETF here.  I'll be
the first to swear at my government for continuing to have ISO think
here.

This seems like a place for the IAB to respond to this regulator, and
in this case, point towards your document and ask why there isn't
someone from the regulator speaking for this.

    Joe> It's not at all certain or even likely that the CRTC-mandated
    Joe> systems will ever use these RRTypes. That ship has surely
    Joe> sailed. The reason for requesting the code-points was to make
    Joe> future such situations less messy, and more likely to result in
    Joe> DNS schemas (if that's a phrase) that were consistent and
    Joe> parseable.=20

Then that's even more a reason for the IAB to send the CRTC a letter.
Maybe it's time for a Canadian liason (but then every country will want
one...?), or maybe it is time for a "regulatory liason" to be
created... I dunno.

    Joe> I've had feedback from a small number of people who are already
    Joe> in the habit of publishing MAC addresses in the DNS as part of
    Joe> (as I understand it) inventory management and internal
    Joe> troubleshooting. I take no position here on whether that's a
    Joe> good idea, but I conclude that publishing such data in the DNS
    Joe> happens today, regardless of the availability of the EUI48 or
    Joe> EUI64 RRTypes.=20

Did they like the scheme?

    Joe> In my mind, this suggests publication of the spec in the RFC
    Joe> series, where it can join other specifications for the encoding
    Joe> of IPv4, IPv6, NSAP, E.164, X.25, ISDN, ATM, NIMROD, HIP, and
    Joe> ILNP addresses. I may have missed some.=20

I agree.


=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUAUadPpoqHRg3pndX9AQLbogP8CFn9HINoIm87GV00GuILZ6xEm8cdsSab
EFjpMGBtNQBoPQGVX7LZ58dCep4bBygCMqz8gZ1QQR6kbH+3h7ojjIdcPGtpNZzn
uSbA6/3jStM0ae01f3DEVWwRwhf0cRFOp1wbFVLDH2305MyAkcdI/6oqdYIUFrAf
YbLH2pzX3ew=
=ZJoR
-----END PGP SIGNATURE-----
--=-=-=--

From randy@psg.com  Thu May 30 06:17:33 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76AF321F90F4 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 06:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SRgK6J8rjOeZ for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 06:17:33 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 13CC621F8616 for <ietf@ietf.org>; Thu, 30 May 2013 06:17:33 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Ui2jU-000GB4-2Y; Thu, 30 May 2013 13:17:32 +0000
Date: Thu, 30 May 2013 06:17:31 -0700
Message-ID: <m2ppw8zjx0.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: When to adopt a WG I-D
In-Reply-To: <51A706AF.50200@gmail.com>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com> <035101ce5d05$aba61110$02f23330$@olddog.co.uk> <51A6FD6A.3030608@gmail.com> <000001ce5d0b$2ad63d70$8082b850$@olddog.co.uk> <51A706AF.50200@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: Thu, 30 May 2013 13:17:33 -0000

>> Yes, I'm sure.
>> Your turn now.
>> Are you sure?
> No, not at all.

did you somehow miss the pdu data formats and exchange ladder diagram?

if this is not a process document, then what the heck is it, chopped
liver?

randy

From randy@psg.com  Thu May 30 06:30:56 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82CAF21F93BC for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 06:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PRxE3r6Yhx+P for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 06:30:56 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2389921F92F5 for <ietf@ietf.org>; Thu, 30 May 2013 06:30:55 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Ui2wR-000GD8-ND; Thu, 30 May 2013 13:30:55 +0000
Date: Thu, 30 May 2013 06:30:55 -0700
Message-ID: <m2mwrczjao.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Issues in wider geographic participation
In-Reply-To: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>
References: <08A2F698F28D9ED6B4AAE099@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: Thu, 30 May 2013 13:30:56 -0000

> (2) As far as I can tell, the operators in most regions are
> generally well represented in, and collaborate using, the
> various *NOGs.

the first derivative is generally positive.  a lot of fluff, machismo,
and posturing, but that seems to come with any endeavor involving us
funny monkeys.

> We are not a user group either.

from the ops' pov, this is not exactly true.  it is notable that there
are almost no .*vendor user groups (ejk's xr-ug being a rare and useful
exception).  the ietf is one of the few formal leverage points where we
can get change from the vendors.

> To the extent to which there is a need for more user groups or more
> effective ones, I hope that the ISOC Chapter structure is at least
> making useful contributions in the area.

the isoc does not attract operators.  it is social/political.  if we
fear the roi to an operator of ietf participation is low, the roi of
participation in isoc is vastly lower.  but this is not a bug, it's a
feature.  

we do not need more poly/soc folk helping us run our networks.  we
desperately need them doing the critically needed, and far more
difficult, work of providing the socio-political front for the internet.
and their talents and achievements in these areas are pretty darned good
and getting better every year.

randy

From paul.hoffman@vpnc.org  Thu May 30 07:59:43 2013
Return-Path: <paul.hoffman@vpnc.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 4443D21F9318 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 07:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MM3PaBTfXYJG for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 07:59:38 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA1B21F9347 for <ietf@ietf.org>; Thu, 30 May 2013 07:59:36 -0700 (PDT)
Received: from [10.20.30.90] (50-1-98-173.dsl.dynamic.sonic.net [50.1.98.173]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r4UExYcF062444 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 30 May 2013 07:59:35 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: When to adopt a WG I-D
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <034f01ce5d02$64068630$2c139290$@olddog.co.uk>
Date: Thu, 30 May 2013 07:59:34 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD94EB85-010E-4295-8500-75108F93C4C3@vpnc.org>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1503)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 14:59:47 -0000

On May 29, 2013, at 11:53 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

> I can also see potential for adding some info to the Tao, but the =
danger there is that document becomes too big and too detailed to be of =
use.

Many would claim it already is. We discussed that here a few years ago, =
and informally decided "too long" was better than "too short and with a =
lot of pointers to other documents that needed to be read".

> Is this a tutorial?

Mainly. To quote...

     NOTE:    This draft is intentionally non-normative.  It is meant as =
a
     guide to common practice, rather than as a formal definition of
     what is permissible.

Proposal: maybe don't do this as an Internet Draft, but do it as a =
tutorial.

--Paul Hoffman=

From john-ietf@jck.com  Thu May 30 10:24:50 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB2621F9349 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 10:24:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzfmhp3xR8zr for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 10:24:44 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 350A221F93FF for <ietf@ietf.org>; Thu, 30 May 2013 10:24:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Ui6af-0004Mx-3o; Thu, 30 May 2013 13:24:41 -0400
Date: Thu, 30 May 2013 13:24:30 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Eliot Lear (elear)" <elear@cisco.com>
Subject: Re: Issues in wider geographic participation
Message-ID: <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>
In-Reply-To: <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 May 2013 17:24:50 -0000

Forwarding a discussion that started offlist for operational
reasons with permission.  I've tried to elide some irrelevant
material; I hope that, if Eliot thinks it was relevant after
all, he will add it back in once he gets to an appropriate
machine.

--On Thursday, May 30, 2013 09:20 -0400 John C Klensin
<john-ietf@jck.com> wrote:

> --On Thursday, May 30, 2013 08:03 +0000 "Eliot Lear (elear)"
> <elear@cisco.com> wrote:
> 
>> If we subscribe wholly to this then to borrow from Darth
>> Vader, our failure is complete. As you and I have discussed
>> and debated, our engineering choices make certain assumptions
>> about what problems are high order and which ones we can
>> safely ignore.  An example is bandwidth.
> 
> Eliot, I think --or at least hope-- that either you have
> misunderstood me or that I have misunderstood your response.
> 
> I'm not talking about bandwidth.  I'm talking about protocols
> that don't work well under less than optimal circumstances.
> And I'm arguing for awareness and case-by-case understanding of
> tradeoffs, not somehow designing for the bottom.   We've seen
> implementations that appear to be in full conformance to IETF
> specifications that simply die with packet timeouts and
> retransmissions.  Perhaps that is just failure to document the
> use cases and limitations, perhaps it is failure to describe
> the edge cases and what to do about them.  I'm disinclined to
> entirely blame implementers who make a good-faith effort to
> follow IETF specs carefully: if our documents don't permit them
> to get things right, I think at least part of the failure is
> ours for failure to cover those cases in specifications.  
> 
> We have recognized the issues with some specs and work areas,
> including trying to promote delay-tolerant efforts -- whether
> the environments be Mars or reindeer-based mobile stations in
> areas considerably north of Jari.  In others, we have waved
> them off.  

 
>> The IETF was formed in part to have rapid impact, and by
>> necessity that required operators and even some users who we
>> later decided to call application developers.
> 
> Sure.  I'm not suggesting pushing either out.  I am suggesting
> that more diversity in those groups would be of benefit.   I'm
> also suggesting that, while including people and review
> processes who can speak with good experience from operator
> perspectives would be of huge benefit, that we don't want to
> expand into an operator forum.  That means that the operational
> folks we want are operational folks who can also speak usefully
> to protocol issues.  As what I think is a corollary, I think
> that beating the bushes in developing countries to try to get
> more operators and end users to attend the IETF as an end in
> itself is not a productive activity from an IETF standpoint.
> And, yes, I think we should be seeking reviewer partnerships
> with the NOGs (and maybe others) for certain classes of
> protocol specifications rather than expecting people who
> frequent those groups to participate actively in the IETF...
> and excluding whatever valuable input they might have if they
> don't.  We have tried the latter model and, IMO, failed.

[...]

>> To be sure, the ecosystem is different, and yet we have blind
>> spots like spam. Put in the vernacular some of us need to get
>> out a bit more. 
> 
> As you know, I disagree with you about where the spam-related
> blind spots are and what to do about them.  But I think that is
> a separate issue.  We probably agree about getting out more
> too.

Eliot then responded...


--On Thursday, May 30, 2013 15:24 +0200 Eliot Lear
<elear@cisco.com> wrote:

> John,
> 
> On this one point:
> 
> On 5/30/13 3:20 PM, John C Klensin wrote:
>> And, yes, I think we should be seeking reviewer partnerships
>> with the NOGs (and maybe others) for certain classes of
>> protocol specifications rather than expecting people who
>> frequent those groups to participate actively in the IETF..
> 
> Expectations of participation aside, how would you suggest
> proceeding wrt NOGs?

As you know, I'm opposed to inventing organizational structure
unless it is clearly necessary.   I would like to ass some
IETF-NOG discussions about whether it would be appropriate to
announce Last Calls for particularly relevant protocols on their
mailing lists and provide a way for relevant operations folks to
respond without subjecting themselves to the noise level
associated with a subscription to the IETF list.   If some NOG
wanted to put institutional positions together, I don't think we
should object, but I don't think that is either necessary or
particularly desirable.

If getting good reviews from broader perspectives that way
required that we sometimes extend Last Calls to four weeks when
RFC 2026 allows two, I think that would be a good tradeoff.

I hope we can trust the IESG to make sound decisions about what
protocols are particularly relevant and to use feedback from the
recipients of those notifications to adjust those decisions if
necessary.

None of the above is a broad solution to a broad class of
problems.  But I think it would increase opportunities for
quality reviews and would allow some relevant people
--especially from areas with little IETF involvement-- to help
themselves and us out without signing up for "IETF
participation".  If we could then suck them in gradually, so
much the better.

Finally, fwiw, I wasn't part of the discussions that created the
IETF (I was "getting out" into some work that did not involve
Internet protocol design but that definitely involved
resource-poor communities), so I can't judge whether "The IETF
was formed in part to have rapid impact".  But, to the extent to
which it is the case, I think we gave up any claim we had to
needing to shortcut either reviews or openness in the interest
of speed when our minimum time to get almost anything
standards-related done passed a year and kept climbing.   YMMD,
of course.

    best,
    john




From narten@us.ibm.com  Thu May 30 10:40:43 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA3421F9660 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 10:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSVd9IS6V512 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 10:40:36 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 7177B21F963A for <ietf@ietf.org>; Thu, 30 May 2013 10:40:36 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 30 May 2013 11:40:36 -0600
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 30 May 2013 11:40:34 -0600
Received: from d01relay03.pok.ibm.com (d01relay03.pok.ibm.com [9.56.227.235]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 1BFCD6E8040 for <ietf@ietf.org>; Thu, 30 May 2013 13:40:30 -0400 (EDT)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay03.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4UHeXID309296 for <ietf@ietf.org>; Thu, 30 May 2013 13:40:33 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4UHeWIF027216 for <ietf@ietf.org>; Thu, 30 May 2013 13:40:33 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-65-152-149.mts.ibm.com [9.65.152.149]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4UHeUJn027088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 May 2013 13:40:32 -0400
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id r4UHePTC001324; Thu, 30 May 2013 13:40:26 -0400
Message-Id: <201305301740.r4UHePTC001324@cichlid.raleigh.ibm.com>
To: adrian@olddog.co.uk
Subject: Re: When to adopt a WG I-D
In-reply-to: <035101ce5d05$aba61110$02f23330$@olddog.co.uk>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk> <51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu> <51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu> <51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu> <51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu> <034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com> <035101ce5d05$aba61110$02f23330$@olddog.co.uk>
Comments: In-reply-to "Adrian Farrel" <adrian@olddog.co.uk> message dated "Thu, 30 May 2013 08:16:51 +0100."
Date: Thu, 30 May 2013 13:40:25 -0400
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13053017-3620-0000-0000-000002CE2109
Cc: 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: Thu, 30 May 2013 17:40:43 -0000

> > To be honest at this point I'm sort of reflexively
> > anti-process-documents, unless there's an actual problem
> > that needs actual solution.

> Which is why this isn't a process document.

Watching this thread, I sense the authors trying hard not to make a
process document, presumably because that would be hard, contentious,
low probability of success, or something.

But this idea that this ID is just a random collection of thoughts
that folk might find interesting and therefore is informative is also
pretty silly.

Melinda has it right. First decide on what problem you are solving. If
you can't do that, no solution (or document) will be satisfactory.

IMO, this document absolutely needs to be a "process" document if it
is to have any value. It is presumably trying to collect experience
and wisdom. Presumably folk should make use of that experience and
wisdom. If that is not a best practices document, what is?

If this document doesn't provide guidance, in the "should" sense, with
an explanation of why a particular practice makes sense and what can
go wrong if that advice is not followed... then what good is it?

> The origin is a WG chairs Edu session. Turns out there was not a lot
>  of clarity among a bunch of WG chairs about what they did and
>  why. My assumption is that if the chairs needed some time to
>  discuss this, the community might need that as well.

If this document is clarifying, isn't that "updating" an existing
document and charting new ground? I.e, how can this not be normative?

>       NOTE:    This draft is intentionally non-normative.  It is meant as a
>       guide to common practice, rather than as a formal definition of
>       what is permissible.

What is the difference between a "guide to common practice" and a BCP?
Is attempting to find a difference a case of hair splitting?

Thomas


From sm@resistor.net  Thu May 30 10:45:27 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20CA21F8F12 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 10:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.339
X-Spam-Level: 
X-Spam-Status: No, score=-102.339 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGMbVDjYha5C for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 10:45:26 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F7421F9608 for <ietf@ietf.org>; Thu, 30 May 2013 10:45:25 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r4UHjI0X017561; Thu, 30 May 2013 10:45:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1369935925; bh=WWTMFPjQk1u0LVui2EtQLZ0JLzoojVilMmH8rqHhU64=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qu13zRJ0h19BVgy7SPADvtBO3RMoqEAwlKfiGGP8D+WGLq76ZqDg/l/RD2AOPbwTf +KVG0P/hc//Vsm9hH7jiqrNCvhv9pA6YDS8loPQM51KBcwbS63d2UHrtxbVnnxTBF0 I8Yd937TR2z5Y63Xoj1ji3AoHcfBPZA6W4G1AerQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1369935925; i=@resistor.net; bh=WWTMFPjQk1u0LVui2EtQLZ0JLzoojVilMmH8rqHhU64=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TVwOMvttonmBi6SVqaPiMM6cOXIEb3j11i2vplGcpGPqi9kzvvW0/jy7rwXZdm0BP JIvSM6d2S+AH5uXZ2Dxi/wJGPD6Fr2vs/9eJng33SW9IUOlYCdulBbButOlOgejVl4 XuVWdxgL5af/H0YqvgDo7dP7mulSglPe8HZuaGrA=
Message-Id: <6.2.5.6.2.20130530091537.0d2928a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 30 May 2013 10:43:46 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: What do we mean when we standardize something?
In-Reply-To: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com>
References: <06C09216C9E0FAC3D737938E@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: Thu, 30 May 2013 17:45:27 -0000

Hi John,
At 10:23 29-05-2013, John C Klensin wrote:
>The IETF has traditionally chosen the first model and a great
>deal of our thinking and public rhetoric are based on it. Even
>when we have adopted proposals, sometimes implemented ones,
>from elsewhere, we have insisted on change control and usually
>taken that seriously.  One could claim that an adaptation of
>the second model would make the Internet more uniform, but a
>consensus of existing practice cannot aspire to "working
>better" except in the narrow sense of substitutability of
>conforming products.

The note is thoughtful.  It's the first time I see a message where 
the "working better" angle is discussed.

>If we are not going to move significantly in the direction of
>"consensus of industry practice", then it seems to me that we
>need to be careful about the arguments that are made (or at
>least those that are considered legitimate) in support of
>advancement into or on the standards track.

If the IETF were to move in the direction of "consensus of industry 
practice" it would be moving towards consensus of industry practice 
based on the opinions of people in the industry who are active in the 
IETF.  Michael Richardson asked the following question:

   "Given that the [Country X] mandated them, why wasn't the IETF involved
    earlier?  The regulator really should have reached out to the IETF here.

If people from Country X do not come to the IETF with the problem the 
IETF won't know about the problem.  If people from Country X do not 
provide input about their industry practice the IETF will know about it.

>For example, if we agree on a relaxed registration procedure
>for some protocol parameters, it is not reasonable to later
>turn around and ask that that those parameters be standardized,
>unchanged, because they are already registered (and maybe
>deployed).  For standardization, the IETF generally needs not
>only change control but an opportunity to comment on and affect
>the actual design and specification of whatever is being
>standardized.

Country X would also have to allow the IETF to have change control on 
the specification or else it is like asking the IETF to rubber-stamp 
the specification.

If I am not mistaken the relaxed registration procedure is so that 
there can be a registry of what is being used on the Internet.  The 
difference here is that the IETF does not review the design, or it 
may set some minimal criteria for the review before allocating the code point.

>Similarly, we sometimes hear it argued that we should accept a
>specification for Proposed Standard unchanged because it has
>been extensively developed and reviewed elsewhere.  That may be
>reasonable in some cases although I'd hope we wouldn't make it
>a common practice.  But, if a specification adopted for
>Proposed Standard on that basis is then proposed for
>advancement to Internet Standard, I think the review should be
>comprehensive --perhaps even more comprehensive than the usual
>such review-- because the Internet Standard is unambiguously an
>IETF product and recommendation not that of the other body.  If
>we allow a specification to advance to Proposed Standard
>without an open and critical review because it was developed
>and reviewed comprehensively by outside expert organizations
>and then allow the Last Call review for Internet Standard to be
>constrained by existing deployment, we would have gone into the
>rubber stamping business that we regularly say is incompatible
>with our standardization model.  That doesn't mean, of course,
>that changes during review for Internet Standard are likely to
>be a good idea.  Those who propose changes to the spec, and
>especially to the protocol, should have to convince the
>community that those changes are important enough to overcome
>the costs, including those of incompatibility with deployed
>versions.  But I don't think we can reasonably exclude them
>from raising the issues and making those arguments.

If an intended Proposed Standard has actually been developed and 
reviewed elsewhere the Last Call and IESG Evaluation is not a 
problem, i.e. any problem in the specification has already been 
identified and addressed.  One of the issues here is the rhetoric 
(the undue use of exaggeration, or from an IETF perspective, making 
unpleasant comments to discourage people from identifying problems).

It is difficult to have an open and critical review of an Internet 
Standard.  There is a significant cost for any change made at that 
level as it may cause interoperability issues.  What "we" mean when 
we standardize something is that "we" will think carefully before 
making a change as "we" would like the specification to be stable 
even if that means not fixing some minor errors.  Internet Standard 
could have been used to say "we" are not going to tinker with this 
specification and it is your best bet if you want to deploy the code 
and forget about it for a few years.

As an unrelated comment, what could "we" mean?  It could mean:

  1. doing what is right to make you look good
  2. doing what is right for your company
  3. doing what is right for a country
  4. doing what is right for the IETF

Regards,
-sm 


From warren@kumari.net  Thu May 30 12:31:27 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8289A21F911B for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 12:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25L4vp+EDqcF for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 12:31:22 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47B1B21F9052 for <ietf@ietf.org>; Thu, 30 May 2013 12:31:22 -0700 (PDT)
Received: from [192.168.1.153] (unknown [66.84.81.127]) by vimes.kumari.net (Postfix) with ESMTPSA id BAE321B40A6B; Thu, 30 May 2013 15:31:21 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Re: Issues in wider geographic participation
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>
Date: Thu, 30 May 2013 15:31:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
Cc: ietf@ietf.org, "Eliot Lear \(elear\)" <elear@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: Thu, 30 May 2013 19:31:27 -0000

On May 30, 2013, at 1:24 PM, John C Klensin <john-ietf@jck.com> wrote:

> Forwarding a discussion that started offlist for operational
> reasons with permission.  I've tried to elide some irrelevant
> material; I hope that, if Eliot thinks it was relevant after
> all, he will add it back in once he gets to an appropriate
> machine.
>=20
> --On Thursday, May 30, 2013 09:20 -0400 John C Klensin
> <john-ietf@jck.com> wrote:
>=20
>> --On Thursday, May 30, 2013 08:03 +0000 "Eliot Lear (elear)"
>> <elear@cisco.com> wrote:
>>=20
>>> If we subscribe wholly to this then to borrow from Darth
>>> Vader, our failure is complete. As you and I have discussed
>>> and debated, our engineering choices make certain assumptions
>>> about what problems are high order and which ones we can
>>> safely ignore.  An example is bandwidth.
>>=20
>> Eliot, I think --or at least hope-- that either you have
>> misunderstood me or that I have misunderstood your response.
>>=20
>> I'm not talking about bandwidth.  I'm talking about protocols
>> that don't work well under less than optimal circumstances.
>> And I'm arguing for awareness and case-by-case understanding of
>> tradeoffs, not somehow designing for the bottom.   We've seen
>> implementations that appear to be in full conformance to IETF
>> specifications that simply die with packet timeouts and
>> retransmissions.  Perhaps that is just failure to document the
>> use cases and limitations, perhaps it is failure to describe
>> the edge cases and what to do about them.  I'm disinclined to
>> entirely blame implementers who make a good-faith effort to
>> follow IETF specs carefully: if our documents don't permit them
>> to get things right, I think at least part of the failure is
>> ours for failure to cover those cases in specifications. =20
>>=20
>> We have recognized the issues with some specs and work areas,
>> including trying to promote delay-tolerant efforts -- whether
>> the environments be Mars or reindeer-based mobile stations in
>> areas considerably north of Jari.  In others, we have waved
>> them off. =20
>=20
>=20
>>> The IETF was formed in part to have rapid impact, and by
>>> necessity that required operators and even some users who we
>>> later decided to call application developers.
>>=20
>> Sure.  I'm not suggesting pushing either out.  I am suggesting
>> that more diversity in those groups would be of benefit.   I'm
>> also suggesting that, while including people and review
>> processes who can speak with good experience from operator
>> perspectives would be of huge benefit, that we don't want to
>> expand into an operator forum.  That means that the operational
>> folks we want are operational folks who can also speak usefully
>> to protocol issues.  As what I think is a corollary, I think
>> that beating the bushes in developing countries to try to get
>> more operators and end users to attend the IETF as an end in
>> itself is not a productive activity from an IETF standpoint.
>> And, yes, I think we should be seeking reviewer partnerships
>> with the NOGs (and maybe others) for certain classes of
>> protocol specifications rather than expecting people who
>> frequent those groups to participate actively in the IETF...
>> and excluding whatever valuable input they might have if they
>> don't.  We have tried the latter model and, IMO, failed.

The below is not a direct response to John, it is more my general views =
on IETF interaction with operators.

So, I've been a long time participant in some NOG's and still (perhaps =
incorrectly) view myself as an operator.
I've spent significant time thinking about / discussing the issue of =
insufficient operator involvement in the IETF, trying to understand some =
of the causes.
I've tried to summarize some of the operators' views below, and also =
some thoughts on how we might be able to work better / get more operator =
input.=20

I think that at the root of much of the problem is cultural differences =
-- if we want more operator involvement / feedback there needs to be =
some attention paid (by both the operators and the IETF folk) to =
understanding these differences, and taking care to respect / =
accommodate the other side's culture.=20

Please note: I am discussing the "operator" and "IETF participant" as =
stereotypes, obviously the reality is much more nuanced than I'm =
presenting. These stereotypes probably don't include you -- they are =
simply generalizations to try and present the different sides of the =
issue.


These are some of the concerns I have heard from operators:

1: The work in the IETF simply takes too long.
"I actually operate a network, and so I need results *soon*. I really =
don't want to spend months debating if requiring foo is a 'should' or a =
'SHOULD', I just want my feature NOW."
"I give $vendor large amounts of money each year -- if I actually want a =
feature I just wave cash at them / threaten to move to $other_vendor and =
they'll add it for me."

I saw this for myself in DANE. During the time it took us to get =
chartered, write a use case document, have endless navel-gazing =
exercises, meet a few times, and then finally publish a document, a set =
of folk implemented a few alternate solutions in the real world, got =
some useful understanding of what works and what doesn't, iterated, and =
moved on to other things. Sure, we chairs could have moved thing along =
faster, but the IETF cycles *is* long.


2: Ivory towerism / academics.
"The work that the IETF is doing is not actually relevant to what I =
need."
A large number of drafts don't really explain what issue they are trying =
to address (poor problem statement) and / or are trying to address =
issues that don't actually exist in the real world. Often drafts try to =
address an issue that only exists in one small corner case on one =
participant's network, or issues that *used* to be important, but have =
now becomes less so as networks have evolved.

The DHCPv6 discussions spring to mind here -- the IETF view (hey,  I =
mentioned generalization above!)  on DHCP / SLAAC were grounded in one =
view of how the world worked / elegance, but the operator's view was =
that they simply wanted something that works like it does in V4.

This is somewhat of a vicious cycle -- operators participate less, and =
so the IETF understands less about how their networks run. This leads to =
solutions that don't understand the real world, and so operators lose =
faith/interest in IETF, and participate even less.

Many of the drafts written are either being pushed for commercial =
reasons, or because it is someone's pet project, not because they solve =
a critical issue for others.
Randy's article on "Testing Spaghetti =97 A Wall=92s Point of View" =
(http://archive.psg.com/051000.sigcomm-ivtf.pdf) speaks mainly to the =
commercial interests, but Jon also had this to say:
"It's perfectly appropriate to be upset. I thought of it in a slightly =
different way--like a space that we were exploring and, in the early =
days, we figured out this consistent path through the space: IP, TCP, =
and so on. What's been happening over the last few years is that the =
IETF is filling the rest of the space with every alternative approach, =
not necessarily any better. Every possible alternative is now being =
written down. And it's not useful."
I know that I for one am guilty of this -- I wrote and have been slowly =
pushing a draft on Omniscient AS112 servers =
(draft-wkumari-dnsop-omniscient-as112) -- this is by far not the most =
important issue in DNS, nor in the Internet. It *does* solve an (IMO) =
important issue, but there are more important issues that *should* be =
worked on -- this one however is interesting / important *to me*, and so =
that's where I spent some cycles.=20


3: I have real work to do -- I simply don't have the cycles to read a =
few thousand mails about some tiny unimportant detail.
This is related to items 1 and 2.=20
Related to this is the fact that most operators can only justify =
attending a small number of conferences -- attending 3 IETFs and 3 NANOG =
/ RIPE / whatever is simply too much.
=20
I don't really know if this is an problems that can (or should) be =
solved. Often operators are more pragmatic than IETF folk, and simply =
want a good solution, not necessarily a perfect solution. "The perfect =
is the enemy of the good" -- this often leads is to create a solutions =
that is overly complex,  and / or solves a problem too late=85
This is (IMO) a cultural difference / an artifact that protocol design =
*needs* more precision / rigor than operations, as it is much harder to =
change once baked.

4: I tried participating, but I got ignored / attacked.
Unfortunately I think that this is one of the bigger cultural issues, =
and one of the harder ones to address.=20
The IETF is in many ways a debating society -- you present an idea / =
draft, and folk challenge (in what could often be interpreted as a =
confrontational manner) what you've said.
This is simply part, and a much needed part, of the IETF culture -- if =
you've said something and no-one is challenging it, chances are is was =
not very interesting / novel. The purpose of saying something in the =
IETF context (should be) to get critical feedback so you can improve it.=20=

If, however, you are not expecting this / are not used to it, this =
interaction can come across as rude  / antagonistic. Folk can feel as =
though they are being attacked personally, and not simply being =
presented with an opportunity to better explain their ideas / improve =
them.=20
I realize that this is all touchy-feely / some folk will think that =
everyone just needs to wear their big boy pants, but if you are willing =
to take a step back and consider how different cultures interpret =
interactions=85

There are some other cultural issues at play here.
I have seen instances where an operator comes along to try and =
participate, but doesn't understand that, while they have credibility / =
standing in their own community, they are an unknown entity in the IETF =
community. When entering a new community one needs to learn the norms, =
and it takes time to establish your reputation / credibility. This can =
lead to frustration with item 4.

A large number of IETF participants are also senior within their =
organizations, and migrated up though operations to their current =
position, often managing operates along the way. Sometimes it is hard to =
admit to oneself that one has lost touch with one's roots, and so =
operates can come across as "upstarts" and be looked down upon by IETF =
participants. This causes friction.
This is partly reflected in some of the discussions one hears in threads =
like this / general hallway discussions -- we often hear about how the =
IETF would like more operators to be involved / attend, but one very =
seldom hears IETF participants trying to become more involved in =
operations / participate in their local NOGs, etc.


Anyway, these are simply my (much simplified) views on a complex topic, =
much more complex than can be easily captured in a single mail. But =
somebody is demanding their soapbox back, so I will end here.

W

>=20
> [...]
>=20
>>> To be sure, the ecosystem is different, and yet we have blind
>>> spots like spam. Put in the vernacular some of us need to get
>>> out a bit more.=20
>>=20
>> As you know, I disagree with you about where the spam-related
>> blind spots are and what to do about them.  But I think that is
>> a separate issue.  We probably agree about getting out more
>> too.
>=20
> Eliot then responded...
>=20
>=20
> --On Thursday, May 30, 2013 15:24 +0200 Eliot Lear
> <elear@cisco.com> wrote:
>=20
>> John,
>>=20
>> On this one point:
>>=20
>> On 5/30/13 3:20 PM, John C Klensin wrote:
>>> And, yes, I think we should be seeking reviewer partnerships
>>> with the NOGs (and maybe others) for certain classes of
>>> protocol specifications rather than expecting people who
>>> frequent those groups to participate actively in the IETF..
>>=20
>> Expectations of participation aside, how would you suggest
>> proceeding wrt NOGs?
>=20
> As you know, I'm opposed to inventing organizational structure
> unless it is clearly necessary.   I would like to ass some
> IETF-NOG discussions about whether it would be appropriate to
> announce Last Calls for particularly relevant protocols on their
> mailing lists and provide a way for relevant operations folks to
> respond without subjecting themselves to the noise level
> associated with a subscription to the IETF list.   If some NOG
> wanted to put institutional positions together, I don't think we
> should object, but I don't think that is either necessary or
> particularly desirable.
>=20
> If getting good reviews from broader perspectives that way
> required that we sometimes extend Last Calls to four weeks when
> RFC 2026 allows two, I think that would be a good tradeoff.
>=20
> I hope we can trust the IESG to make sound decisions about what
> protocols are particularly relevant and to use feedback from the
> recipients of those notifications to adjust those decisions if
> necessary.
>=20
> None of the above is a broad solution to a broad class of
> problems.  But I think it would increase opportunities for
> quality reviews and would allow some relevant people
> --especially from areas with little IETF involvement-- to help
> themselves and us out without signing up for "IETF
> participation".  If we could then suck them in gradually, so
> much the better.
>=20
> Finally, fwiw, I wasn't part of the discussions that created the
> IETF (I was "getting out" into some work that did not involve
> Internet protocol design but that definitely involved
> resource-poor communities), so I can't judge whether "The IETF
> was formed in part to have rapid impact".  But, to the extent to
> which it is the case, I think we gave up any claim we had to
> needing to shortcut either reviews or openness in the interest
> of speed when our minimum time to get almost anything
> standards-related done passed a year and kept climbing.   YMMD,
> of course.
>=20
>    best,
>    john
>=20
>=20
>=20

--
Don't be impressed with unintelligible stuff said condescendingly.
    -- Radia Perlman.






From john-ietf@jck.com  Thu May 30 17:37:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3ECB21F9701 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 17:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tq8rVtV3i4nJ for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 17:37:40 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1484521F96E9 for <ietf@ietf.org>; Thu, 30 May 2013 17:37:39 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UiDLe-0004zP-15; Thu, 30 May 2013 20:37:38 -0400
Date: Thu, 30 May 2013 20:37:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: Issues in wider geographic participation
Message-ID: <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
In-Reply-To: <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, "Eliot Lear \(elear\)" <elear@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: Fri, 31 May 2013 00:37:46 -0000

--On Thursday, May 30, 2013 15:31 -0400 Warren Kumari
<warren@kumari.net> wrote:

> The below is not a direct response to John, it is more my
> general views on IETF interaction with operators.
> 
> So, I've been a long time participant in some NOG's and still
> (perhaps incorrectly) view myself as an operator. I've spent
> significant time thinking about / discussing the issue of
> insufficient operator involvement in the IETF, trying to
> understand some of the causes. I've tried to summarize some of
> the operators' views below, and also some thoughts on how we
> might be able to work better / get more operator input. 
> 
> I think that at the root of much of the problem is cultural
> differences -- if we want more operator involvement / feedback
> there needs to be some attention paid (by both the operators
> and the IETF folk) to understanding these differences, and
> taking care to respect / accommodate the other side's culture. 
>...

Warren,

I think these notes are very helpful, at least insofar as I have
enough knowledge to evaluate.   Some of your comments,
including...
 
> This is somewhat of a vicious cycle -- operators participate
> less, and so the IETF understands less about how their
> networks run. This leads to solutions that don't understand
> the real world, and so operators lose faith/interest in IETF,
> and participate even less.

ultimately call the IETF's legitimacy and long-term future into
question.  As you suggest, we may have good vendor participation
but the operators are ultimately the folks who pay the vendor's
bills.

>...

As I told someone in another thread, I threw the NOG idea out as
an example without thinking through all of the possible
dynamics.  It may be a terrible idea... or even a good idea that
won't work usefully.  

Part of that discussion included an observation that is probably
a corollary to one of yours.  Many operators, either
individually or in groups, don't perceive that they have much
incentive to review IETF documents, much less get dragged into
the document development and consensus-forming process.
Certainly, we are unlikely to get very many people who are not
active IETF participants to do work for the good of the IETF.
>From that perspective, the very best incentive for reviewing a
document pre-standardization is the perceived risk that it will
make one's life worse if it goes through without input from your
perspective.  If we throw documents over the wall without clear
motivation as to why people on the other side of the wall should
care,... well, that is as much a setup for failure as the model
in some other Internet bodies of soliciting input and then not
paying any attention to it.   (In the latter case, there may be
organizational advantages to being able to say "we received NN
comments", but that does not apply to the IETF.)

More generally, and borrowing (but altered somewhat) from
another thread:  The real point I'm trying to make is that, if
our goal is really to do outreach to other communities to get
better input or reviews with broader perspective, then we better
start thinking more creatively than trying to persuade people
(and their organizations and budgets) to sign up for the IETF,
three extra week-long meetings a year, reading mailing lists
that contain dozens of messages a day on topics that may be of
no interest at all, etc.   Instead, in your terminology, Warren,
we should be looking for ways in which they can do what
simultaneously benefits them, us, and the Internet as much as
possible within their own cultural framework.   At least we need
to distinguish between the goals of "better input and review
from affected communities" and "increasing IETF active
participation".   

And, coming back to the supposed topic of this thread, dragging
circa 1000 people to a place that doesn't have a lot of
participation already is unlikely to accomplish either goal.
There may be, and probably are, perfectly good reasons why more
geographic diversity would be a good idea, but justifying doing
so on the basis that it is a good investment in growing
long-term active IETF participation just doesn't, IMO, fly.

    john








From adrian@olddog.co.uk  Thu May 30 18:19:22 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C20621F9926 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 18:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Y6MaqHKCkp5 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 18:19:16 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 01B3B21F9928 for <ietf@ietf.org>; Thu, 30 May 2013 18:19:15 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4V1JExa011367;  Fri, 31 May 2013 02:19:14 +0100
Received: from 950129200 (HKRnf12760.tokyo-ip.dti.ne.jp [27.120.235.10]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id r4V1JAw4011353 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 May 2013 02:19:12 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John C Klensin'" <john-ietf@jck.com>, "'Warren Kumari'" <warren@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
In-Reply-To: <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
Subject: RE: [IETF] Re: Issues in wider geographic participation
Date: Fri, 31 May 2013 02:19:06 +0100
Message-ID: <022d01ce5d9c$dade82e0$909b88a0$@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: AQG+ChTeuPXiC51bVyuRmJpf5/xNTgGVbblLAopoibsB+8HmVwG/qVVNAw6TNgyY59ZMoA==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 01:19:22 -0000

Hi,

This thread is helpful to me.

> > This is somewhat of a vicious cycle -- operators participate
> > less, and so the IETF understands less about how their
> > networks run. This leads to solutions that don't understand
> > the real world, and so operators lose faith/interest in IETF,
> > and participate even less.
> 
> ultimately call the IETF's legitimacy and long-term future into
> question.  As you suggest, we may have good vendor participation
> but the operators are ultimately the folks who pay the vendor's
> bills.

I agree so far.

But who pays the operators' bills, and do we need to encourage participation at
that level as well?

Adrian


From melinda.shore@gmail.com  Thu May 30 19:09:15 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3021E21F96E4 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:09:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qiFxhuUcmhcQ for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:09:09 -0700 (PDT)
Received: from mail-pd0-f177.google.com (mail-pd0-f177.google.com [209.85.192.177]) by ietfa.amsl.com (Postfix) with ESMTP id 7F83021F901A for <ietf@ietf.org>; Thu, 30 May 2013 19:09:02 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id u11so1367312pdi.22 for <ietf@ietf.org>; Thu, 30 May 2013 19:09:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qeydYbXkf4GfV77X1r7ELzujP/7wW4k92PjS9T+c0Ic=; b=BuB6mB4yynnNxubRuxfVw5nXZplRsw4BycL959B8kH3wHe863pFdZc1x1qvS8VgqCZ sW/blDtuegfipeVyr6/rPnzpwsTQ6GH1trtHqljkNW8IMloAcrGsEV7S5iF+OGvMNKxp mfTQzJ2y8nsBH0QwDWbOaymBlcYGDw0i8nH8aBAWSS+cXAE6ozDHFfKOC2GS5I5OV3Wc ST/dMLTHkspeuMKmrEh1iIvVr0nHgudfUhvmdhCiTBdyuQpcg2/Tmq7LRqbMnDHCNbCT AceEfu1ZRlqOT+6z5QAT4/tx0rWQnJLMV1x6QTRRcemHETAlkqF/QO8mZa5ZpqMJyV3R Pa5A==
X-Received: by 10.68.132.101 with SMTP id ot5mr10741814pbb.11.1369966142205; Thu, 30 May 2013 19:09:02 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id aj2sm44356731pbc.1.2013.05.30.19.09.00 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 19:09:01 -0700 (PDT)
Message-ID: <51A8063A.7030302@gmail.com>
Date: Thu, 30 May 2013 18:08:58 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: Issues in wider geographic participation
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
In-Reply-To: <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 02:09:15 -0000

On 5/30/13 4:37 PM, John C Klensin wrote:
> ultimately call the IETF's legitimacy and long-term future into
> question.  As you suggest, we may have good vendor participation
> but the operators are ultimately the folks who pay the vendor's
> bills.

Here in Alaska was the first time I'd worked in an environment
that had technologists at a considerably less than elite skill
level, and I'd previously had no idea the extent to which
average operators/data centers rely on vendors (worse: VARs
and consultants) to solve their technical problems.  The only
time I'd seen someone from an Alaskan operator participate in
anything to do with the IETF was when one person "voted" on
the transitional address space allocation.  I think Warren is
correct to identify this as an issue with operator participation.

Perhaps we should be thinking about some alternative to
engaging operators by trying to get them to schlep to meetings.
Something along the lines of a liaison process or creating
a pipeline between us and NOGs.

Melinda


From randy_presuhn@mindspring.com  Thu May 30 19:16:25 2013
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1B921F9946 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.185
X-Spam-Level: 
X-Spam-Status: No, score=-100.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-ZqD0y-04MR for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:16:18 -0700 (PDT)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id 88B7E21F9943 for <ietf@ietf.org>; Thu, 30 May 2013 19:16:18 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=uIHU6sR5Sg3TTcAUAAmEk3+uk71+BQKUwkcstgbbeMhHsd0DYpWpn4SWo8NN4UoJ; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.187.237.79] (helo=oemcomputer) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1UiEt7-00067h-U1 for ietf@ietf.org; Thu, 30 May 2013 22:16:18 -0400
Message-ID: <000b01ce5da5$644bcf80$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <ietf@ietf.org>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net><44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>
Subject: Re: [IETF] Re: Issues in wider geographic participation
Date: Thu, 30 May 2013 19:20:15 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88880ff2f3e23ebe9464d084773d901ba87f3116c971cc09ba7350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.187.237.79
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 02:16:25 -0000

Hi -

> From: "Adrian Farrel" <adrian@olddog.co.uk>
...
> But who pays the operators' bills, and do we need to encourage participation at
> that level as well?

Participation as:
    RFC uptake:
        - using something based on an RFC?
        - deploying something based on an RFC?
        - implementing something based on an RFC?
        - providing useful feedback based on usage/deployment/implementation experience?
    I-D uptake:
        - providing I-D reviews?
        - implementation of something based on an I-D?
        - providing useful feedback based on usage/deployment/implementation experience?
    WG participation:
        - lurking on mailing list(s)?
        - useful contribution to email conversation?
        - participation in meetings?
        - volunteering as scribe?
        - volunteer as editor?
        - design team work?
        - mentoring newcomers?
    ...

For each of the possible target populations, what would be the realistic motivations
to do one or more of these?  I think factors to consider would include:
    - tradeoff between time investment required and hoped-for outcome
    - perceived likelihood that one's participation would make a difference
    - perceived extent to which this time investment or contribution (not the
      same thing!) would be favorably recognized by:
        + one's peers
        + one's employer
        + potential future employers
        + one's customers / clients
    - whether there would be any personal satisfaction derived from participation
    - others?

Thinking about the cross-product of these lists and the target populations that have
been mentioned, it seems a minor miracle that the IETF has had been able to get
as much participation and diversity as it has.  Particularly when we get to the "user"
level, the time investment / payoff ratio seems all wrong unless that user is highly
altruistic or has a generous sponsor with "big picture" motivations.

It also seems that for specific target populations, it might be useful to identify (1) the
specific ways in which that population might have the most positive impact on
the IETF and more importantly (2) identify the ways in which IETF participation
might have the biggest positive impact on those types participants, their employers,
or other constituencies with whom they identify.  Not quite a marketing strategy, but until
this conversation is centered around learning the needs, gifts, and motivations
of these "other" people, it's not going to accomplish much to increase participation.

Randy


From l.wood@surrey.ac.uk  Thu May 30 19:24:06 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F68721F9947 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.598
X-Spam-Level: 
X-Spam-Status: No, score=-5.598 tagged_above=-999 required=5 tests=[AWL=1.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NnNUs1nJUCQn for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:24:00 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.113]) by ietfa.amsl.com (Postfix) with ESMTP id BCD8321F910D for <ietf@ietf.org>; Thu, 30 May 2013 19:23:51 -0700 (PDT)
Received: from [193.109.255.147:56330] by server-9.bemta-14.messagelabs.com id 5B/C5-15694-6B908A15; Fri, 31 May 2013 02:23:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-72.messagelabs.com!1369967029!7575414!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1373 invoked from network); 31 May 2013 02:23:49 -0000
Received: from unknown (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-9.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 31 May 2013 02:23:49 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 31 May 2013 03:23:49 +0100
From: <l.wood@surrey.ac.uk>
To: <melinda.shore@gmail.com>, <ietf@ietf.org>
Date: Fri, 31 May 2013 03:21:56 +0100
Subject: RE: [IETF] Re: Issues in wider geographic participation
Thread-Topic: [IETF] Re: Issues in wider geographic participation
Thread-Index: Ac5do+/Rzo9lGNpcQoyW2vHjNWOWPgAAa/p8
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E98@EXMB01CMS.surrey.ac.uk>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>, <51A8063A.7030302@gmail.com>
In-Reply-To: <51A8063A.7030302@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 02:24:06 -0000

Melinda Shore, all at sea:
> Here in Alaska was the first time I'd worked in an environment
> that had technologists at a considerably less than elite skill
> level, and I'd previously had no idea the extent to which
> average operators/data centers rely on vendors (worse: VARs
> and consultants) to solve their technical problems.

You'd love the Pacific.

Few IETFers get exposed to these kinds of environments.

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

From melinda.shore@gmail.com  Thu May 30 19:41:27 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A257021F901F for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.466
X-Spam-Level: 
X-Spam-Status: No, score=-2.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m01Qw3DGR+Uq for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:41:27 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD6521F8FA3 for <ietf@ietf.org>; Thu, 30 May 2013 19:41:27 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id un4so1415007pbc.26 for <ietf@ietf.org>; Thu, 30 May 2013 19:41:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/IObD4H2YlcBc+nue8oWb2Y28mMaFXtuhKaVTXLvCJw=; b=k33ES1GXw24dba1ET/qmiDAZai/IOd84EVA3Thhaxq03p3fPzvHlFt4Md4l4qc6dkq pln+i9KQhe1lNvIAR8tmoDMJy7JpMaj6Mcn1wA0EDv0MMO82ODX8Iaavt+I1uepBC+CT BZwTei26dXkxrpO0LPDhlFecnsauUwfqXmhdUTmUncFvheqMy4+Sb3PYt4eNmuy4uNIl gmG++B/bCX6/fpBSORf8mVqM5HJaT+eXWMXxFKlDLRMXIj7qysZpiY5clm+o0wtoxFBQ ndVRgRylEMn6UxzX9cxm/8okBrxD3pZdEvRL+YQEi2kZV/Vgdp5RTp5+LpZDZTF3pRjA eQSQ==
X-Received: by 10.66.216.198 with SMTP id os6mr11178136pac.145.1369968086949;  Thu, 30 May 2013 19:41:26 -0700 (PDT)
Received: from spandex.local (66-230-82-15-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.82.15]) by mx.google.com with ESMTPSA id ve6sm7760345pbc.21.2013.05.30.19.41.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 19:41:25 -0700 (PDT)
Message-ID: <51A80DD2.2020609@gmail.com>
Date: Thu, 30 May 2013 18:41:22 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: [IETF] Re: Issues in wider geographic participation
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>, <51A8063A.7030302@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E98@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E98@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 02:41:27 -0000

On 5/30/13 6:21 PM, l.wood@surrey.ac.uk wrote:
> You'd love the Pacific.
> Few IETFers get exposed to these kinds of environments.

I'd had no idea.  The point here isn't to derogate techies
working in this kind of environment, but that because the
sorts of informal technology and skills transfer mechanisms
that exist in tech centers don't exist here (people stay in
jobs forever, not many new people come in, there's no elite
university), there's heavy reliance among operators and
enterprise data centers on the people who sell them stuff.
I think that this is probably more common than we realize,
and might go towards answering questions about where the
operators are.

Melinda


From doug.mtview@gmail.com  Thu May 30 19:52:56 2013
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75FE521F8EF7 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MX6q3zddrdHV for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 19:52:55 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 424A021F8CB4 for <ietf@ietf.org>; Thu, 30 May 2013 19:52:55 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id z20so283728yhz.39 for <ietf@ietf.org>; Thu, 30 May 2013 19:52:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=wRH3PMJpYHNr58AERi/r2SOLnVFOsBfab0e5YUVpU6c=; b=NX6qRTtVdWI5bMRqoLxx8SNfqn5J008evmbVJXViNqzfXn+8rdQIodxL+JVIrTUP00 wutWkkW+9uUfjKzjGgdyBN8QxmMKlNtUI9mz25NPv0SqztvLnI3mCblnHgMnFokMg87P ehi6ZByfoGnMrQg9TpwH5vALWZDZ7XlpfB9PC91FsnDnv7LmUCcd2275Y7GEQ38cYn23 Vid3AJUJRHZVlgaKwje3w1eMt5mqbMrT7kmAL/Wem7BuyyQLmaZ147kfWIANTIDwjdb/ x7McxJX0PM8TcE68COoQLfRanF9duKi+7zeVIipzr9OUgcJP2LfXYbdtTo5rHk+txT1M qLnA==
X-Received: by 10.236.68.232 with SMTP id l68mr5731760yhd.24.1369968772054; Thu, 30 May 2013 19:52:52 -0700 (PDT)
Received: from [192.168.2.115] (c-98-207-206-162.hsd1.ca.comcast.net. [98.207.206.162]) by mx.google.com with ESMTPSA id d91sm64573732yhq.16.2013.05.30.19.52.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 May 2013 19:52:51 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Issues in wider geographic participation
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <51A8063A.7030302@gmail.com>
Date: Thu, 30 May 2013 19:52:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <62828F5D-2FC8-4E01-A8FC-208FA77E60EE@gmail.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <51A8063A.7030302@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1503)
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, 31 May 2013 02:52:56 -0000

On May 30, 2013, at 7:08 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> On 5/30/13 4:37 PM, John C Klensin wrote:
>> ultimately call the IETF's legitimacy and long-term future into
>> question.  As you suggest, we may have good vendor participation
>> but the operators are ultimately the folks who pay the vendor's
>> bills.
>=20
> Here in Alaska was the first time I'd worked in an environment
> that had technologists at a considerably less than elite skill
> level, and I'd previously had no idea the extent to which
> average operators/data centers rely on vendors (worse: VARs
> and consultants) to solve their technical problems.  The only
> time I'd seen someone from an Alaskan operator participate in
> anything to do with the IETF was when one person "voted" on
> the transitional address space allocation.  I think Warren is
> correct to identify this as an issue with operator participation.
>=20
> Perhaps we should be thinking about some alternative to
> engaging operators by trying to get them to schlep to meetings.
> Something along the lines of a liaison process or creating
> a pipeline between us and NOGs.

Dear Melinda,

Perhaps something to also consider is that many installations operate at =
minimal compliance levels even within advanced regions.  The IETF is =
blessed with many very smart people (at least from my perspective) who =
also seem overly optimistic of the impact of non-normative language on =
outcome.  Specifications provide better outcomes when function is =
ensured at minimal levels.  In other words, it is better not to make =
assumptions.

Regards,
Douglas Otis =20



From abdussalambaryun@gmail.com  Thu May 30 21:37:14 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8D2521F8E2C for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 21:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nf+ECpXesYid for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 21:37:14 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 4796321F8CB7 for <ietf@ietf.org>; Thu, 30 May 2013 21:37:14 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id un4so1538637pbc.26 for <ietf@ietf.org>; Thu, 30 May 2013 21:37:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2EluSCMFoNNcIPZ1b/9go3J/Ho9JwBy3+BszD1c2LBk=; b=dfgCMY7j5Rhnq0YYIwUvPo9gxXRVCvMixXImsCEIVkFgybUg1Nhbt5I9qAxpyUmYEv FjXT6Jlk1FPRbuqd4jLpLQkw4/k+7K/JVvS60rdJsPPD3Dn0V6hSWVkB6Vnc2LkuWDXX OQku3DtnI5Lj+d22sq4i6IEYp98oje4r7I8N4Ea8dZb2mb/wBaDpBdaA5HNwXG6CBm5f ieNV3ogGYhxSS9gov+6Gf9dnbrBPe9zQxwbbhQuSW1+ztGPIEAcxhSkxxn1nKzCOZkoR 6qjL/xvCuGsYMtu6GlvCIIjZI0K+tbwyiXDq/j/m7sgO57VKdgIzKOgsp0u+ISnBAlj+ piAA==
MIME-Version: 1.0
X-Received: by 10.66.17.137 with SMTP id o9mr3741396pad.142.1369975034014; Thu, 30 May 2013 21:37:14 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 30 May 2013 21:37:13 -0700 (PDT)
In-Reply-To: <5420793214639E162E9EEC23@JcK-HP8200.jck.com>
References: <06C09216C9E0FAC3D737938E@JcK-HP8200.jck.com> <51A63D08.8080406@gmail.com> <5420793214639E162E9EEC23@JcK-HP8200.jck.com>
Date: Fri, 31 May 2013 06:37:13 +0200
Message-ID: <CADnDZ8-k4VH4qFUFkTAMECqamFXNoNOuUx4Ad_gP08TPt+v79w@mail.gmail.com>
Subject: Re: "Fixing: the standards track or RFC series (was: Re: What do we mean when we standardize something?)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 04:37:14 -0000

On 5/30/13, John C Klensin <john-ietf@jck.com> wrote:
> difficult problems arise when someone comes to us with a spec
> that might be ok but isn't how we would do it and tries to say
> "you can have this and we will turn over change control as long
> as you don't really want to make any changes".  When a statement
> equivalent to that is justified on the basis of either being in
> a hurry or not invalidating existing implementations, we find
> ourselves in the middle of the contradiction between "consensus
> of industry practice" and "best engineering solution" for
> standardization.

If the standards proposed are reviewed well I don't think there will
be contradiction, I don't recommending always sticking to best
engineering solutions, because it is difficult to guarantee best
solutions in present/future (best practices ok). For industry request
work, IMO its better that our standards get into between *best
engineering practices* and *good engineering practices*, that will not
contradict with *consensus* and  *industry practices*.

AB

From narten@us.ibm.com  Thu May 30 21:53:14 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73F1921F9814 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 21:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xApD19vYaMLm for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 21:53:07 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 97D9221F994C for <ietf@ietf.org>; Thu, 30 May 2013 21:53:07 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 30 May 2013 22:53:06 -0600
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 30 May 2013 22:53:05 -0600
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id F41EA38C8042 for <ietf@ietf.org>; Fri, 31 May 2013 00:53:03 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r4V4r4uV65405006 for <ietf@ietf.org>; Fri, 31 May 2013 00:53:04 -0400
Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r4V4r4YM009785 for <ietf@ietf.org>; Fri, 31 May 2013 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r4V4r3Lk009755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 31 May 2013 01:53:04 -0300
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id r4V4r2Rb003509 for <ietf@ietf.org>; Fri, 31 May 2013 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id r4V4r2s2003468 for ietf@ietf.org; Fri, 31 May 2013 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201305310453.r4V4r2s2003468@rotala.raleigh.ibm.com>
Date: Fri, 31 May 2013 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13053104-3620-0000-0000-000002D21ABD
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 04:53:14 -0000

Total of 283 messages in the last 7 days.
 
script run at: Fri May 31 00:53:02 EDT 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.71% |   19 |  6.76% |   149502 | abdussalambaryun@gmail.com
  5.30% |   15 |  4.74% |   104777 | juliao@braga.eti.br
  4.59% |   13 |  4.81% |   106323 | john-ietf@jck.com
  4.95% |   14 |  4.05% |    89568 | melinda.shore@gmail.com
  4.24% |   12 |  4.09% |    90539 | sm@resistor.net
  3.53% |   10 |  3.01% |    66505 | dhc@dcrocker.net
  3.53% |   10 |  2.90% |    64207 | joelja@bogus.com
  3.18% |    9 |  2.48% |    54808 | aservin@lacnic.net
  2.83% |    8 |  2.49% |    54963 | arturo.servin@gmail.com
  1.77% |    5 |  3.36% |    74410 | rlb@ipv.sx
  2.47% |    7 |  2.53% |    56045 | jmamodio@gmail.com
  2.47% |    7 |  2.32% |    51295 | johnl@taugh.com
  2.47% |    7 |  2.09% |    46177 | jari.arkko@piuha.net
  2.47% |    7 |  2.00% |    44270 | adrian@olddog.co.uk
  2.47% |    7 |  1.73% |    38288 | randy@psg.com
  1.77% |    5 |  1.71% |    37897 | ted.lemon@nominum.com
  1.77% |    5 |  1.47% |    32493 | scott.brim@gmail.com
  1.41% |    4 |  1.47% |    32458 | ynir@checkpoint.com
  1.41% |    4 |  1.40% |    30991 | christian.oflaherty@gmail.com
  1.41% |    4 |  1.37% |    30267 | l.wood@surrey.ac.uk
  1.41% |    4 |  1.21% |    26655 | lars@netapp.com
  1.41% |    4 |  1.09% |    24055 | fernando@gont.com.ar
  0.71% |    2 |  1.77% |    39031 | cb.list6@gmail.com
  1.41% |    4 |  1.04% |    22973 | touch@isi.edu
  1.06% |    3 |  1.18% |    26094 | jabley@hopcount.ca
  0.71% |    2 |  1.45% |    32059 | hgs@cs.columbia.edu
  0.71% |    2 |  1.31% |    28905 | rumbiles@gmail.com
  1.06% |    3 |  0.93% |    20651 | mnot@mnot.net
  0.71% |    2 |  1.18% |    26191 | ted.ietf@gmail.com
  1.06% |    3 |  0.76% |    16908 | paul.hoffman@vpnc.org
  1.06% |    3 |  0.75% |    16616 | dougb@dougbarton.us
  0.71% |    2 |  1.03% |    22840 | aeopare@gmail.com
  0.71% |    2 |  0.94% |    20854 | jmpolk@cisco.com
  0.71% |    2 |  0.91% |    20202 | ggm@algebras.org
  0.71% |    2 |  0.87% |    19276 | tjc@ecs.soton.ac.uk
  0.71% |    2 |  0.81% |    17837 | sistopefuni@gmail.com
  0.71% |    2 |  0.79% |    17395 | amankin@verisign.com
  0.71% |    2 |  0.78% |    17242 | mariainesrobles@googlemail.com
  0.71% |    2 |  0.78% |    17142 | narten@us.ibm.com
  0.71% |    2 |  0.72% |    15959 | mcr+ietf@sandelman.ca
  0.71% |    2 |  0.69% |    15241 | fred@cisco.com
  0.71% |    2 |  0.68% |    15102 | loa@pi.nu
  0.71% |    2 |  0.65% |    14361 | lberger@labn.net
  0.71% |    2 |  0.64% |    14208 | npule@lca.org.ls
  0.71% |    2 |  0.64% |    14122 | alejandroacostaalamo@gmail.com
  0.71% |    2 |  0.64% |    14066 | randy_presuhn@mindspring.com
  0.71% |    2 |  0.62% |    13706 | brian.e.carpenter@gmail.com
  0.71% |    2 |  0.60% |    13351 | paf@frobbit.se
  0.71% |    2 |  0.60% |    13325 | d3e3e3@gmail.com
  0.71% |    2 |  0.58% |    12859 | sm+ietf@elandsys.com
  0.71% |    2 |  0.56% |    12400 | stpeter@stpeter.im
  0.35% |    1 |  0.90% |    19792 | rogaglia@cisco.com
  0.71% |    2 |  0.53% |    11788 | swmike@swm.pp.se
  0.71% |    2 |  0.53% |    11742 | ajs@anvilwalrusden.com
  0.35% |    1 |  0.85% |    18711 | warren@kumari.net
  0.35% |    1 |  0.84% |    18507 | yaojk@cnnic.cn
  0.35% |    1 |  0.69% |    15151 | medel@globetel.com.ph
  0.35% |    1 |  0.59% |    13137 | ron.even.tlv@gmail.com
  0.35% |    1 |  0.59% |    13110 | hannes.tschofenig@gmx.net
  0.35% |    1 |  0.59% |    12940 | andy@yumaworks.com
  0.35% |    1 |  0.53% |    11618 | stbryant@cisco.com
  0.35% |    1 |  0.50% |    11052 | yi.jiazi@gmail.com
  0.35% |    1 |  0.48% |    10556 | jgunn6@csc.com
  0.35% |    1 |  0.45% |    10043 | vinayakh@gmail.com
  0.35% |    1 |  0.43% |     9556 | daedulus@btconnect.com
  0.35% |    1 |  0.43% |     9519 | stephen.farrell@cs.tcd.ie
  0.35% |    1 |  0.40% |     8855 | jiangsheng@huawei.com
  0.35% |    1 |  0.40% |     8845 | moreiras@nic.br
  0.35% |    1 |  0.38% |     8490 | eburger@standardstrack.com
  0.35% |    1 |  0.38% |     8360 | rsouza.rjo@gmail.com
  0.35% |    1 |  0.37% |     8092 | bmanning@isi.edu
  0.35% |    1 |  0.36% |     7895 | dromasca@avaya.com
  0.35% |    1 |  0.35% |     7799 | marka@isc.org
  0.35% |    1 |  0.34% |     7595 | tnadeau@lucidvision.com
  0.35% |    1 |  0.34% |     7555 | pthaler@broadcom.com
  0.35% |    1 |  0.33% |     7406 | ole@cisco.com
  0.35% |    1 |  0.33% |     7386 | doug.mtview@gmail.com
  0.35% |    1 |  0.33% |     7316 | dave@cridland.net
  0.35% |    1 |  0.29% |     6466 | spencer@wonderhamster.org
  0.35% |    1 |  0.29% |     6439 | fgont@si6networks.com
  0.35% |    1 |  0.29% |     6435 | carlosm3011@gmail.com
  0.35% |    1 |  0.29% |     6383 | hsantos@isdg.net
  0.35% |    1 |  0.28% |     6274 | ben@nostrum.com
  0.35% |    1 |  0.28% |     6247 | jmh@joelhalpern.com
  0.35% |    1 |  0.28% |     6131 | lear@cisco.com
  0.35% |    1 |  0.27% |     5889 | ajs@crankycanuck.ca
  0.35% |    1 |  0.25% |     5494 | michal@krsek.cz
  0.35% |    1 |  0.24% |     5329 | dwm@xpasc.com
--------+------+--------+----------+------------------------
100.00% |  283 |100.00% |  2211312 | Total


From abdussalambaryun@gmail.com  Thu May 30 21:59:03 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5D221F8E9A for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 21:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-rDpC44y8Y7 for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 21:59:02 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6A91421F871D for <ietf@ietf.org>; Thu, 30 May 2013 21:59:02 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id wy17so1569308pbc.9 for <ietf@ietf.org>; Thu, 30 May 2013 21:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=53xGc/3EMLoCAuC9UTnuDeUAV8FMDJRltf961z3tS7w=; b=DploBlDUshI9+a/cJ5DJximoLH+4IXL8LAXEwvfdNXcSsJI3yHkSR+5xSENqBdPjo3 AOd0BC4vpM+k/fyuEKKyZAIKIaL4cJnZ2lI9HtGTOOU3cbuSBJIqEhyBsUaDi+Ku55D5 YcZTTZpV+jivsrAimZVXxwiXvDPHUsNXJId2n3heVyX14LpO+DpqR1yr8ATbAgmx8phY +hTMeSS1OkVufFCxlxmU250lbQZUhw0yOxvPYa9wBvPyjpAL5ocMvUf2o6echCu4JJxM hq5lfWa46rMJF61W4z8QtgvPiodb1WGLpXCySZu+7yLSEcFlZPeMi8LFDAWSSDBz/js8 eHqA==
MIME-Version: 1.0
X-Received: by 10.66.122.8 with SMTP id lo8mr11462324pab.165.1369976342111; Thu, 30 May 2013 21:59:02 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 30 May 2013 21:59:01 -0700 (PDT)
In-Reply-To: <CAKr6gn1VhNpW9C49hkH1=-rxWU8YkK5wCXaHEiBG1Lp3yA8VLQ@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <51A56C53.7070709@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk> <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@mail.gmail.com> <08CA5DA78C79446B431AC8B6@JcK-HP8200.jck.com> <CAKr6gn1VhNpW9C49hkH1=-rxWU8YkK5wCXaHEiBG1Lp3yA8VLQ@mail.gmail.com>
Date: Fri, 31 May 2013 06:59:01 +0200
Message-ID: <CADnDZ89C+ozDkYT+QdPwYSTR9qiz5+i4bXtGwwcMH51+NS_3Qw@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: George Michaelson <ggm@algebras.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 04:59:03 -0000

On 5/30/13, George Michaelson <ggm@algebras.org> wrote:
> At risk of alienating my comrades from locations seeking to attract an IETF
> for local development/inclusiveness and the like reasons, I think John gets
> to the nub of the matter: the wider community cost, borne by all attendees
> as a 'silent tax' is really very high, for this outcome. We need to be
> explicit this is what we're doing. The ISOC grants are probably a more cost
> effective way of boosting participation from outlier economies right now.

Yes, let's be explicit, what is the meeting values or goals? Why we
are considering cost now when we are looking into the IETF future
challenges, or when we are looking into developing IETF activities
(i.e. better outcome change)

> So lets be explicit. This is a standards-setting body, which is discussing
> outreach, inclusiveness, wider participation outcomes, and the cost
> consequences on attendance where the core motivation is standards setting.

Yes, let's be explicit, we need to discuss the IETF meeting not
discuss the IETF business, IMHO, meetings are for establishing better
connection between the IETF and the Internet-Community. IMHO, IETF is
not just a standards-setting body, please read what it says about
itself:

IETF> The mission of the IETF is to make the Internet work better by
producing high quality, relevant technical documents that influence
the way people design, use, and manage the Internet.
IETF> The IETF is a Large open international community of network
designers, operators, vendors, and researchers concerned with the
evolution of the Internet architecture and the and the smooth
operation of the Internet. It is open to any interested individual.

AB> so interested individuals are welcomed in the IETF meetings and business.

> If the core motivations are changing, maybe that drives things in a
> different way?
>

Don't forget that the Internet is changing and that the Internet
Community is changing, the IETF SHOULD follow thoes changes :-)

AB

From abdussalambaryun@gmail.com  Thu May 30 23:36:02 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3212C21F8EFE for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 23:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_37=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nmkGnXBZzOke for <ietf@ietfa.amsl.com>; Thu, 30 May 2013 23:36:01 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id EE3A321F8EC2 for <ietf@ietf.org>; Thu, 30 May 2013 23:36:00 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id rp8so1687649pbb.36 for <ietf@ietf.org>; Thu, 30 May 2013 23:36:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gbqXPRoIbfx44tZgKS87bhBz98KvdK11ftJXCat9Ai0=; b=Tcwp4rS0apR/pJFXYNEQMFc+l7SjWo4uCy/XpK5Oq0utfdWUW/66D+gkSvz7ejw2ww i0G1oKP36CMBLcY3Yb/3yEv0cbS8xp74hIGJgw/1xkAT4NSUlp88yt2+saIP/ASX+VNN N5tDaCwNI3xLBqqYixK+pzVsZ90WY36Ll29XfCtJBeqYBugV7kvlP141mmrJPppUdXkK an5ZcKF5arxMrZylhG8SSHJZmWrIxOAusyArvUlQh7StUXUw2fNjZCUT/weV6QqRCXY4 SMDdjXDAC438HGFTYFBumNAf3CMz/tSK54afrLMJGWEx8gIRmxwlnPgxd1OBffSeMiEW BZ2Q==
MIME-Version: 1.0
X-Received: by 10.66.158.234 with SMTP id wx10mr12063655pab.43.1369982160511;  Thu, 30 May 2013 23:36:00 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Thu, 30 May 2013 23:36:00 -0700 (PDT)
In-Reply-To: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>
Date: Fri, 31 May 2013 08:36:00 +0200
Message-ID: <CADnDZ89Htog4iaxCb0ye86Ongu6sH+zG0kGr+UR508qu9dvPvg@mail.gmail.com>
Subject: Re: Issues in wider geographic participation
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 06:36:02 -0000

Hi John,

Thanks for your comments/proposals, I always know that your
discussions are important for my progress in IETF. I reply some
comments as below,

On 5/30/13, John C Klensin <john-ietf@jck.com> wrote:
> Jari,
>
> Inspired by two of your recent notes and Dave Crocker's long
> one last weekend (with which I almost completely agree should
> that be notable), let me make a few observations:
>
> (1) To the extent to which the IETF's focus is on protocols that
> we hope vendors and others ("producers" in the vocabulary of
> some other SDOs) will implement and try to get deployed, lines
> of argument that start with "they use the Internet there,
> therefore they should be participating in the IETF" may just be
> irrelevant.  If there is a major vendor design presence in a
> region, then we should be very concerned if we don't have
> significant presence from that region in the IETF as well.  But,
> if the vendor presence is limited to marketing, sales, and
> perhaps implementation, then, if that is a problem, it is one
> that doesn't lie easily within IETF scope... and probably
> shouldn't.

Yes, let's be explicit, we need to discuss the IETF meeting not
discuss the IETF business, IMHO, meetings are for establishing better
connection between the IETF and the Internet-Community. Does the IETF
have a buildings or locations it is reside in? I see no location,
because it is for the world to participate business remotely.
IMHO, IETF is not just a standards-setting body, please read what it
says about itself:

I disagree, the IETF is not only for protocol-standards, IMHO, it is
for the Internet and its community, please read;

IETF> The mission of the IETF is to make the Internet work better by
producing high quality, relevant technical documents that influence
the way people design, use, and manage the Internet.
IETF> The IETF is a Large open international community of network
designers, operators, vendors, and researchers concerned with the
evolution of the Internet architecture and the and the smooth
operation of the Internet. It is open to any interested individual.

>
> (2) As far as I can tell, the operators in most regions are
> generally well represented in, and collaborate using, the
> various *NOGs.  If those groups aren't serving their needs, it
> is probably not a problem for the IETF.  If they are, then the
> IETF should no more be trying to invade that turf than a certain
> Geneva-based organization should be invading ours.  We are not a
> user group either.  To the extent to which there is a need for
> more user groups or more effective ones, I hope that the ISOC
> Chapter structure is at least making useful contributions in the
> area.

I don't know why you exclude users, and separate their participation
to Chapters. The problem of IETF is to give opportunity to regions to
use IETF.

>
> (3) Our Operations and Management Area is mostly about protocols
> and tools (just as the Applications area really isn't about
> applications as user/purchasers normally understand that term)
> and therefore those with the most skin in the game are, again,
> producers, vendors, and designers, not users or even operators.
> The latter are important for figuring out whether a particular
> facility will meet identified needs, but that is typically more
> of a review function than a design one.

The user and operator are mentioned to be part in IETF, please read again;

IETF> The mission of the IETF is to make the Internet work better by
producing high quality, relevant technical documents that influence
the way people design, use, and manage the Internet.
IETF> The IETF is a Large open international community of network
designers, operators, vendors, and researchers concerned with the
evolution of the Internet architecture and the and the smooth
operation of the Internet. It is open to any interested individual.

>   If we need more input
> about such specs, we might ask the various *NOGs or similar
> groups to formally review proposed specifications rather than
> depending on people to come to f2f IETF meetings or even to
> follow our mailing lists.  So, while closer contact with
> operator communities is always good (and not just for that
> Area), we may need to adjust our expectations to the reality of
> what we can do effectively, rather than forcing on broadening
> participation for its own sake.

Let's make IETF give opportunity to all parts (mentioned in its
mission statement) to participate,

>
> (4) There are some areas of work in the IETF in which very broad
> geographic input --more accurately, broad cultural and
> linguistic input-- are absolutely essential.  For example, the
> more we move into internationalization or make decisions that
> dictate or constrain user interfaces, the more danger we get
> into of making really stupid decisions if we don't have broad
> and diverse participation and input.  To a degree, the same
> issue shows up in lower layers of the stack.  For example, the
> vast majority of us spend our time using current-technology
> hardware, fast and high-capacity connections to the public
> Internet, and even faster LANs.  We often subconsciously design
> for that sort of environment because we don't encounter the
> other kinds on a regular basis. I contend that we have a
> relatively poor history of protocol decisions when people are
> affected whose day-to-day technology is a decade or two behind
> our current experience.

I agree, but I prefare to say all areas of work need geographic input,
because you never know what will be needed in the future by the
Internet Community.

>
> (5) There are a lot of non-vendor participants in the IETF and
> even ones whose days as producers of implementations are mostly
> over, but it is still a relatively small minority (and, as far
> as I can tell, getting smaller).  As a member of that group, I
> wish it were larger, both for balance and because I think that
> we may have an easier time maintaining focus on the overall
> well-being of the Internet as a complete system than people
> whose focus is getting the next product specified, implemented,
> and into the hands of users (or marketing organizations).  But,
> if we contribute usefully, it is mostly because we bring
> considerable experience or perspective of one sort or another to
> the table.  With rare (and occasionally very important)
> exceptions that include people from the research side of the
> community, a newly-minted engineer who has no producer
> organization affiliation to provide context is unlikely to be
> useful to us (and is reasonably likely to have a frustrating
> experience no matter what we do about "newcomers" or recruiting).

I disagree, please read in the IETF it mentions below as open to
individuals, so why you make them must have affiliations.

IETF> The IETF is a Large open international community of network
designers, operators, vendors, and researchers concerned with the
evolution of the Internet architecture and the and the smooth
operation of the Internet. It is open to any interested individual.

>
> (6) The IETF is (or has become) primarily an engineering and
> protocol design and standardization organization, something that
> was recognized over two decades ago when the community kept the
> IRTF separate but got rid of all the other non-IETF task forces.
> While we could try to "diversify" to include a much broader base
> of experience and interests that do not focus directly on our
> current range of activities, it is likely that doing so would
> increase noise without adding much to the signal.

Again, I think you maybe suggesting to change the IETF mission or the
type of participants the IETF needs.
IMHO, the Internet-community individuals are the important focus of
the IETF, so no one can become noise only if he/she gets out of
IETF-procedure. Noise is out of the system-procedure of the signal
communication, so it is noise, so your example is not correct when you
refer to IETF's diverse parts.

>
> One thing that all of those observations have in common is that
> none of them are likely to be affected by a single meeting in a
> single location.  Probably holding a whole year or two of
> meetings in the same general vicinity wouldn't make any
> significant difference either, at least after we moved on.

I disagree, please read statistics, the most participants are from
North America, and the most meetings held are in North America. I
think if we ask a business men/women of if there is an affect or not,
they will say there are affects, humans are sensitive but different
way than machines.

> Borrowing from some of the discussions about mentoring during
> and after IETF 86, I suggest that, if we really want to
> encourage active participation from places where we now have
> very little, we would:
>
> (i) Try to increase awareness of the IETF and what it does in
> those areas, via ISOC chapters, lectures, and other forms of
> contact.  Variations on this have been suggested by others.
> Note that doing this for a given location would require putting,
> at most, one or two people on airplanes (possibly at IETF or
> ISOC expense),

I have no objection only if the new-comer agrees to such mentoring.

>not order 1000 of us at individual or company
> expense.  (See George Michaelson's most recent note in the "IETF
> Meeting in South America" thread.)

No one is forced to attend or spend time/money, we always have remote
facilities to do the job in all IETF activities. Please read my reply
to that post of sub;meeting in South America that you refered to.

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

>
> (ii) Try to assign a document process advisor to each newcomer
> the first time that person posts an I-D (or earlier if we can
> determine that an I-D is in progress or should be generated from
> other discussions).  This is a little different from a mentor
> (see Iiii)) in that the role would be to specifically advise on
> the process of getting a document through the system, what
> obstacles are likely to be encountered, etc., and could be
> pretty aggressive if that were necessary.   The process advisor
> could recommend that that author seek out other resources,
> including a mentor or editorial help, when necessary.  The
> IETF's curmudgeon component, many of whom would make lousy
> mentors, might still be good document process advisors.

Disagree, that is discriminating between participants, all
participants should be equal don't you think,

>
> (iii) Allow new participants who intend to participate remotely
> and by mailing list to request and be assigned mentors, ideally
> mentors who speak the participant's primary language.  Focusing
> our efforts only on people who show up at meetings means that we
> leave the folks who could be among our more productive
> participants in the cold and, for most regions where we have
> little penetration and resources are a problem, pretty much
> guarantees that it will stay that way.

Again that is discrimination of focus-of-efforts, the IETF does not do
that. However, if the some new-participant agrees with that, then it
can be ok, otherwise, no. So it should be after the agreement of
participant and with no excluding if disagreed.
>
> (iv) Encourage ISOC to redesign the IETF Fellows program so that
> people who were reasonable candidates for long-term
> participation were tracked differently from the
> observer-tourists.   In the potential participant track, the
> assumption should be that Fellows might have participated
> remotely (including by mailing list) already, that such
> participation would give a candidate Fellow some extra priority
> or points in the selection process, and that activities during
> IETF should include explicit and focused discussions of optimal
> ways to participate without attending meetings.  If we (or ISOC,
> or other organizations) later get the Fellows to more meetings,
> that would be great, but the goal should be to make a good
> remote participant, not people who can be effective only if they
> attend a lot of face to face meetings.

I agree that IETF management discuss this point with ISOCs (or each
region ISOC), and each ISOC feedback should be considered as well.
>
> The above would not be easy.

Nothing is easy when it involves alot of people's lives/times/money.
However, IMO, your proposal will not be encouraging all
new-participants but maybe only yung-new-participants.

>  It would require a large number of
> experienced members of the community to make a major commitment
> to working with new authors and non-attendee newcomers.

I support this point as well, but without making new-participant feel
that he/she discriminated from others. If it is only saying you are in
level 1 of participating, fine but not saying; well you are in level 1
so please don't make noise (such behavior is not acceptable), or you
are in level 1 so no one in the community wants to know your thoughts
(such behavior is not acceptable), or you did not write an I-D so
people will not listen to you until you do, etc.

>  But it
> would help significantly to bridge the gap between "interested
> in the IETF and its work" and "contributing participant".

Only if there is mutual respect and equal opportunities,

> Flying a thousand person-weeks worth of folks into an area where
> we have little participation and attracting a few local tourists
> won't have the same effect --with or without a few hours of
> "newcomer" sessions-- and will still leave people with the need
> to make that transition if they are going to be effective.

Regarding region attraction/effects, I may agree and disagree.
Agreeing because I want to meet some authors of excellent RFCs, but I
mostly disagree with the point for some reasons. Your point here is
assuming many things which are not always true. You assume that
majority of Internet-community are represented by current IETF
participation, and that if new participating they mostly may not be
affective. You assume that all IETF f2f participants are all affective
and will continue that way. You assume that other regions that are not
participating in IETF because they are not aware of the IETF. You
assume that being effective mostly-means that you have to f2f attend
meeting. You assume that new-comers will be encouraged by
special-sessions, and assume that the thousand persons need to make
transition to such region. IMHO, the IETF work and *business* is
mostly done *remotely* on its lists not in f2f meetings, but community
interconnections are done in *meetings*. Therefore recommend a Wider
Geographic Participation Diversified and not discriminated.

Please note that the above is my opinion and believe, but if the
comments are wrong, feel free to comment on them.

Regards

Abdussalam Baryun
University of Glamorgan, UK

- I worked on four new I-Ds so far and doing my best to renew them shortly.
- I never attended an IETF meeting so far, because not able to, but I
will do in future, because want to meet most of the IETF ADs which are
encouraging, and to meet some participants that done excellent RFCs.
- I beleive that I am always affective and following procedure. I am
active to remote participate in IETF business as long as no manager in
IETF informed me to stop (relating to legal procedure), or informed me
that I am out-of-procedure (with reference/reason).

From mnot@mnot.net  Fri May 31 02:59:32 2013
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 BE54721F8EC1 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 02:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.51
X-Spam-Level: 
X-Spam-Status: No, score=-103.51 tagged_above=-999 required=5 tests=[AWL=-4.111, BAYES_50=0.001, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36AxPQTgI+aB for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 02:59:27 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 963E221F8EDF for <ietf@ietf.org>; Fri, 31 May 2013 02:59:27 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.184.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 224B822E1F3 for <ietf@ietf.org>; Fri, 31 May 2013 05:59:20 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Time in the Air
Message-Id: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
Date: Fri, 31 May 2013 19:59:16 +1000
To: ietf Discussion <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 09:59:32 -0000

In an attempt to inject some data into the discussion, I wrote a bit of =
code that figures out how much time, given your home city, you would =
have spent in the air if you'd attended all IETF meetings since IETF74 =
(i.e., from 2009 onwards).

The first column is the "home" airport.

The second column is the great circle time between the home airport and =
the nearest large airport to the IETF meeting, hhh:mm. This doesn't =
count things like transit time, taxiing, takeoff and landing overhead, =
indirect routing, etc. As such, this is an ideal number; the only way to =
achieve anything close to it is to have a private jet (with exceptional =
range).

The third column is the time (hhh:mm) using the shortest-time routing on =
a travel booking engine. This is first-takeoff-to-last-landing time.

Both numbers assume round trip between "home" and the IETF airports.

SFO  204:10  282:04  // San Francisco
BOS  197:42  297:38  // Boston
ATL  205:44  297:28  // Atlanta
ANC  197:12  345:54  // Anchorage
LHR  198:02  249:44  // London
FRA  202:10  255:22  // Frankfurt
FCO  223:52  283:04  // Rome
SVO  211:28  287:14  // Moscow
TLV  264:12  334:22 // Israel
DXB  293:26  344:34 // Dubai
NRT  259:00  314:38  // Tokyo
HKG  296:38  359:22  // Hong Kong
BLR  332:28  448:24  // Bangalore
MEL  450:28  556:04  // Melbourne
AKL  442:24  569:04  // Auckland
JNB  414:30  498:22  // Johannesburg
EZE  411:10  522:56  // Buenos Aires
GIG  381:56  488:32  // Rio de Janeiro

Draw your own conclusions, of course.=20

One observation is that there's a 3+ days-in-the-air per year variance =
if you're a full-time participant, depending on where you live. I.e., =
more than one day-per-meeting difference, on average. In the air alone.

Another is that, perhaps surprisingly, the "closest" homes to all =
meetings are in Europe, not the US (at least by shortest-time routing).

I can run other airports upon request, as well as make source available, =
but will do so conservatively, so as not to incur the ire of the =
services I'm (ab)using.

Regards,

P.S. The IETF airports chosen were:

  IETF_airports: [
    "ORL",
    "ATL",
    "YVR",
    "CDG",
    "TPE",
    "YQB",
    "PRG",
    "PEK",
    "AMS",
    "LAX",
    "HIJ",
    "ARN",
    "SFO"
  ],

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




From daedulus@btconnect.com  Fri May 31 03:25:12 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FEA821F8FA9 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 03:25:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EswHs5dd2Psp for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 03:25:06 -0700 (PDT)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id DC48B21F92FC for <ietf@ietf.org>; Fri, 31 May 2013 03:25:03 -0700 (PDT)
Received: from mail93-co1-R.bigfish.com (10.243.78.247) by CO1EHSOBE029.bigfish.com (10.243.66.94) with Microsoft SMTP Server id 14.1.225.23; Fri, 31 May 2013 10:25:02 +0000
Received: from mail93-co1 (localhost [127.0.0.1])	by mail93-co1-R.bigfish.com (Postfix) with ESMTP id DDB768C01DD; Fri, 31 May 2013 10:25:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ah1fc6hzz8275ch1033IL8275bh8275dhz2dh2a8h5a9h668h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah1d0ch1d2eh1d3fh1dfeh1dffh304l1d11m1155h)
Received: from mail93-co1 (localhost.localdomain [127.0.0.1]) by mail93-co1 (MessageSwitch) id 136999590036937_29637; Fri, 31 May 2013 10:25:00 +0000 (UTC)
Received: from CO1EHSMHS014.bigfish.com (unknown [10.243.78.251])	by mail93-co1.bigfish.com (Postfix) with ESMTP id 065BD700052; Fri, 31 May 2013 10:25:00 +0000 (UTC)
Received: from DBXPRD0711HT004.eurprd07.prod.outlook.com (157.56.254.181) by CO1EHSMHS014.bigfish.com (10.243.66.24) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 31 May 2013 10:24:59 +0000
Received: from DBXPRD0611HT002.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.178.37) with Microsoft SMTP Server (TLS) id 14.16.311.1; Fri, 31 May 2013 10:24:42 +0000
Message-ID: <01b601ce5de8$44a84f80$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Melinda Shore <melinda.shore@gmail.com>, <adrian@olddog.co.uk>
References: <014801ce5b86$55a476b0$00ed6410$@olddog.co.uk><51A512E8.6000801@gmail.com> <51A63B63.1090309@isi.edu><51A63C85.7000604@dcrocker.net> <51A63E15.8070704@isi.edu><51A6403F.8010206@dcrocker.net> <51A64196.4030100@isi.edu><51A64F68.10401@dcrocker.net> <51A65BDD.8040304@isi.edu><034f01ce5d02$64068630$2c139290$@olddog.co.uk> <51A6FA7A.30100@gmail.com>
Subject: Re: When to adopt a WG I-D
Date: Fri, 31 May 2013 11:08:08 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
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.254.85]
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, 31 May 2013 10:25:12 -0000

---- Original Message -----
From: "Melinda Shore" <melinda.shore@gmail.com>
To: <adrian@olddog.co.uk>
Cc: <dcrocker@bbiw.net>; <ietf@ietf.org>
Sent: Thursday, May 30, 2013 8:06 AM
> On 5/29/13 10:53 PM, Adrian Farrel wrote:
> > I see a wedge :-)
> > The problem is where to stop.
>
> Well, I don't know.  Maybe the problem is where to
> start.  That is to say, I don't know what problem
> this document is trying to solve, or if there even
> is a problem.

So don't start!

I-D adoption is in the gift of the WG Chairs and some do an excellent
job, others make a hash of it (which in turn increases the workload on
other parts of the IETF).

Question is, can we do anything to reduce the hashes without at the same
time impairing excellence (short of improving the quality of WG Chairs,
which I suspect is not realistic)?

I note that this discussion last surfaced on this list six months ago,
almost to the day; my sense then was that that most thought that this
should not become a process but perhaps, like European referenda, the
question will go on being put until the acceptable answer emerges:-)

Tom Petch


                             I know that we've had some major
> document quality issues in opsawg and Benoit has
> provided some needed guidance on document adoption,
> but this doesn't seem to be dealing with that sort
> of issue.  Is it that people are confused about when
> to adopt a document (or not)?  Is this intended to
> provide some sort of context to resolve complaints?
> Is this a tutorial?
>
> To be honest at this point I'm sort of reflexively
> anti-process-documents, unless there's an actual problem
> that needs actual solution.
>
> Melinda
>
>



From fgont@si6networks.com  Fri May 31 03:28:34 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1F9A21F92FC for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 03:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[AWL=-0.300,  BAYES_00=-2.599, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8umvNRgMjq2 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 03:28:32 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 1C74721F9123 for <ietf@ietf.org>; Fri, 31 May 2013 03:28:32 -0700 (PDT)
Received: from b00150.krakowskiinternet.pl ([91.231.45.150] helo=[192.168.1.160]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UiMZR-0001m8-6v; Fri, 31 May 2013 12:28:29 +0200
Message-ID: <51A87B4C.3020805@si6networks.com>
Date: Fri, 31 May 2013 12:28:28 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Time in the Air
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
In-Reply-To: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.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: Fri, 31 May 2013 10:28:34 -0000

On 05/31/2013 11:59 AM, Mark Nottingham wrote:
> In an attempt to inject some data into the discussion, I wrote a bit
> of code that figures out how much time, given your home city, you
> would have spent in the air if you'd attended all IETF meetings since
> IETF74 (i.e., from 2009 onwards).
> 
> The first column is the "home" airport.
> 
> The second column is the great circle time between the home airport
> and the nearest large airport to the IETF meeting, hhh:mm. This
> doesn't count things like transit time, taxiing, takeoff and landing
> overhead, indirect routing, etc. As such, this is an ideal number;
> the only way to achieve anything close to it is to have a private jet
> (with exceptional range).

Could you please elaborate a bit more on the meaning of the second column?

Thanks!

-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From fgont@si6networks.com  Fri May 31 03:52:45 2013
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 784C821F949D for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 03:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ehOp6B6lnH-g for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 03:52:45 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id E15F521F9385 for <ietf@ietf.org>; Fri, 31 May 2013 03:52:44 -0700 (PDT)
Received: from b00150.krakowskiinternet.pl ([91.231.45.150] helo=[192.168.1.160]) by web01.jbserver.net with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.80.1) (envelope-from <fgont@si6networks.com>) id 1UiMwr-0002KV-VR; Fri, 31 May 2013 12:52:42 +0200
Message-ID: <51A87D42.9010603@si6networks.com>
Date: Fri, 31 May 2013 12:36:50 +0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Issues in wider geographic participation
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>
In-Reply-To: <08A2F698F28D9ED6B4AAE099@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: Fri, 31 May 2013 10:52:45 -0000

John,

On 05/30/2013 08:04 AM, John C Klensin wrote:
> irrelevant.  If there is a major vendor design presence in a
> region, then we should be very concerned if we don't have
> significant presence from that region in the IETF as well.  But,
> if the vendor presence is limited to marketing, sales, and
> perhaps implementation, then, if that is a problem, it is one
> that doesn't lie easily within IETF scope... and probably
> shouldn't.

Do open source developers count? -- With Android and the like, they end
up producing more deployed implementations than anyone else.

And they generally also keep the spirit of "open" more than anyone else.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From mnot@mnot.net  Fri May 31 04:02:15 2013
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 2E08921F8930 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 04:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.604
X-Spam-Level: 
X-Spam-Status: No, score=-104.604 tagged_above=-999 required=5 tests=[AWL=-2.605, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6MXLgxT2z0SP for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 04:02:10 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 122ED21F85C3 for <ietf@ietf.org>; Fri, 31 May 2013 04:02:09 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.184.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4C16C22E1FA; Fri, 31 May 2013 07:02:02 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Time in the Air
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <51A87B4C.3020805@si6networks.com>
Date: Fri, 31 May 2013 21:01:58 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <12DB74A3-7A95-4DC1-9230-BB70E25D6EC2@mnot.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <51A87B4C.3020805@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1503)
Cc: ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 11:02:15 -0000

On 31/05/2013, at 8:28 PM, Fernando Gont <fgont@si6networks.com> wrote:

> On 05/31/2013 11:59 AM, Mark Nottingham wrote:
>> In an attempt to inject some data into the discussion, I wrote a bit
>> of code that figures out how much time, given your home city, you
>> would have spent in the air if you'd attended all IETF meetings since
>> IETF74 (i.e., from 2009 onwards).
>>=20
>> The first column is the "home" airport.
>>=20
>> The second column is the great circle time between the home airport
>> and the nearest large airport to the IETF meeting, hhh:mm. This
>> doesn't count things like transit time, taxiing, takeoff and landing
>> overhead, indirect routing, etc. As such, this is an ideal number;
>> the only way to achieve anything close to it is to have a private jet
>> (with exceptional range).
>=20
> Could you please elaborate a bit more on the meaning of the second =
column?

It's the duration given by a reputable travel search engine for the =
end-to-end trip, from when the first plane takes off until when the last =
plane lands, including transit time, etc., and a fixed buffer for =
getting to the airport, etc.=20

Still not really accurate, but it helps factor in indirect routing and =
the like. The shortest available current routing is chosen; that routing =
may not actually be available during the meeting, etc.

Cheers,

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




From cabo@tzi.org  Fri May 31 05:39:05 2013
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 8EC5A21F898B for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 05:39:05 -0700 (PDT)
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_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id agFCymz2MuWD for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 05:38:59 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id A0E2A21F9473 for <ietf@ietf.org>; Fri, 31 May 2013 05:38:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r4VCcpLP020279; Fri, 31 May 2013 14:38:51 +0200 (CEST)
Received: from [192.168.217.105] (p5489322F.dip0.t-ipconnect.de [84.137.50.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 922573D11; Fri, 31 May 2013 14:38:50 +0200 (CEST)
Subject: Re: Time in the Air
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
Date: Fri, 31 May 2013 14:38:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC324F37-6F05-463A-B537-AEB7C6CC08BA@tzi.org>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.1503)
Cc: ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 12:39:05 -0000

Wow, that's real science at work...

Sorting by the relevant column (I don't own a private jet):

> LHR  249:44  // London
> FRA  255:22  // Frankfurt
> SFO  282:04  // San Francisco
> FCO  283:04  // Rome
> SVO  287:14  // Moscow
> ATL  297:28  // Atlanta
> BOS  297:38  // Boston
> NRT  314:38  // Tokyo
> TLV  334:22  // Israel
> DXB  344:34  // Dubai
> ANC  345:54  // Anchorage
> HKG  359:22  // Hong Kong
> BLR  448:24  // Bangalore
> GIG  488:32  // Rio de Janeiro
> JNB  498:22  // Johannesburg
> EZE  522:56  // Buenos Aires
> MEL  556:04  // Melbourne
> AKL  569:04  // Auckland

I'll use this list when planning my next relocation :-)

Of course, this doesn't include time-to-airport, so you can immediately =
discount London.

It's clear that you want to live in or near Frankfurt.

San Francisco, Rome, and Moscow (!) come in as a second cluster.
The fact that both SFO and SVO are in there (and Tokyo, Boston aren't =
half bad either) shows that we are getting close to properly covering =
the belt between ~30=B0N (Taipei @ 25=B0N) and ~50=B0N (the Stockholm =
IETF being the northernmost recent exception, I think).  It gets very =
thin to the south of that...

Gr=FC=DFe, Carsten


From scott.brim@gmail.com  Fri May 31 05:53:18 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B48C421F9385 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 05:53:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LZGBu8hie4sz for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 05:53:18 -0700 (PDT)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 6E4B421F9455 for <ietf@ietf.org>; Fri, 31 May 2013 05:53:14 -0700 (PDT)
Received: by mail-ea0-f170.google.com with SMTP id f15so1552423eak.29 for <ietf@ietf.org>; Fri, 31 May 2013 05:53:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=eevcTzZCBr4dRp7Q8ZMrqsf5PnJAcoRtq3fEXVkEBiQ=; b=XgUTYSbvf+qmiMgFQLZAr09IAUSjyaHKz0zJ9AamJXaFerd2dai7IGh8jAFRM1Mrem HxvkEib+E7SVSpw4Q+ljLJlhB4XtD3AmndjEdRe7FWnsG7jihngILSW7zcekDUTnJnnf fde+ckYNPRiFrkdWBVd9xMxJNjKx7anwR/IJLvi8RHzI3lCP2eR1xqnGoiYItMWM6cgO K4Bpuhkxmv2dn8CWS34hDBI8rsqsDqgi8F2KvUgpyoY6f8WZocf3SzYgcYj/ywJLOhKa lHgJ1Ip7I6dWH6/di3ZZLMCjHSgbRYbFa8gmVBMmEjWzPuTe/oszL+A6c9TtdwLQu73A Dd9g==
MIME-Version: 1.0
X-Received: by 10.14.94.193 with SMTP id n41mr13191807eef.122.1370004785873; Fri, 31 May 2013 05:53:05 -0700 (PDT)
Received: by 10.14.117.12 with HTTP; Fri, 31 May 2013 05:53:05 -0700 (PDT)
In-Reply-To: <CADnDZ89C+ozDkYT+QdPwYSTR9qiz5+i4bXtGwwcMH51+NS_3Qw@mail.gmail.com>
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <519FA6B4.3020007@dougbarton.us> <519FAB64.6030007@bogus.com> <CAL02cgTAgOpHks9PUw-jnYVcHJ82qhVdr+jEVh_3RzkPAtY3EA@mail.gmail.com> <519FAFAF.3060008@bogus.com> <519FB068.9050503@dougbarton.us> <519FB1A0.40208@bogus.com> <519FB37D.3060604@dougbarton.us> <519FBFCF.5020202@bogus.com> <alpine.OSX.2.01.1305241253050.44324@rabdullah.local> <51A2D4E8.5050605@dcrocker.net> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <51A56C53.7070709@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk> <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@mail.gmail.com> <08CA5DA78C79446B431AC8B6@JcK-HP8200.jck.com> <CAKr6gn1VhNpW9C49hkH1=-rxWU8YkK5wCXaHEiBG1Lp3yA8VLQ@mail.gmail.com> <CADnDZ89C+ozDkYT+QdPwYSTR9qiz5+i4bXtGwwcMH51+NS_3Qw@mail.gmail.com>
Date: Fri, 31 May 2013 08:53:05 -0400
Message-ID: <CAPv4CP_ZSpw85pmJa81tQVxV4CiRcyZgo_eJvouU2o7LHcYSsw@mail.gmail.com>
Subject: Re: IETF Meeting in South America
From: Scott Brim <scott.brim@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a1133d3249a759c04de03186e
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 12:53:18 -0000

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

On Friday, May 31, 2013, Abdussalam Baryun wrote:

> > So lets be explicit. This is a standards-setting body, which is
> discussing
> > outreach, inclusiveness, wider participation outcomes, and the cost
> > consequences on attendance where the core motivation is standards
> setting.
>
> Yes, let's be explicit, we need to discuss the IETF meeting not
> discuss the IETF business, IMHO, meetings are for establishing better
> connection between the IETF and the Internet-Community.


The primary purpose of meetings is to solve problems that cannot be solved
by e-mail.


> IMHO, IETF is
> not just a standards-setting body, please read what it says about
> itself:
>
> IETF> The mission of the IETF is to make the Internet work better by
> producing high quality, relevant technical documents that influence
> the way people design, use, and manage the Internet.
> IETF> The IETF is a Large open international community of network
> designers, operators, vendors, and researchers concerned with the
> evolution of the Internet architecture and the and the smooth
> operation of the Internet. It is open to any interested individual.
>

Yes and the way that concern is expressed is through technical problem
solving and documentation.  The IETF also _assists_ in outreach but that is
not the primary mission of making the Internet work better.

Don't forget that the Internet is changing and that the Internet
> Community is changing, the IETF SHOULD follow thoes changes :-)
>

I don't know what the smiley is supposed to connote, but the IETF responds
to changes in the community by changing its engineering goals and the
problems it works on.

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

On Friday, May 31, 2013, Abdussalam Baryun  wrote:<br><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">&gt; So lets be explicit. This is a standards-setting body, which=
 is discussing<br>

&gt; outreach, inclusiveness, wider participation outcomes, and the cost<br=
>
&gt; consequences on attendance where the core motivation is standards sett=
ing.<br>
<br>
Yes, let&#39;s be explicit, we need to discuss the IETF meeting not<br>
discuss the IETF business, IMHO, meetings are for establishing better<br>
connection between the IETF and the Internet-Community. </blockquote><div><=
br></div><div>The primary purpose of meetings is to solve problems that can=
not be solved by e-mail.</div><div>=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
IMHO, IETF is<br>
not just a standards-setting body, please read what it says about<br>
itself:<br>
<br>
IETF&gt; The mission of the IETF is to make the Internet work better by<br>
producing high quality, relevant technical documents that influence<br>
the way people design, use, and manage the Internet.<br>
IETF&gt; The IETF is a Large open international community of network<br>
designers, operators, vendors, and researchers concerned with the<br>
evolution of the Internet architecture and the and the smooth<br>
operation of the Internet. It is open to any interested individual.<br></bl=
ockquote><div><br></div><div>Yes and the way that concern is expressed is t=
hrough technical problem solving and documentation. =A0The IETF also _assis=
ts_ in outreach but that is not the primary mission of making the Internet =
work better.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
Don&#39;t forget that the Internet is changing and that the Internet<br>
Community is changing, the IETF SHOULD follow thoes changes :-)<br></blockq=
uote><div><br></div><div>I don&#39;t know what the smiley is supposed to co=
nnote, but the IETF responds to changes in the community by changing its en=
gineering goals and the problems it works on.</div>

--001a1133d3249a759c04de03186e--

From dave@cridland.net  Fri May 31 05:55:19 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8412021F962A for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 05:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 275+OWKR1qYc for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 05:55:19 -0700 (PDT)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id D7C2421F93DA for <ietf@ietf.org>; Fri, 31 May 2013 05:55:18 -0700 (PDT)
Received: by mail-ob0-f179.google.com with SMTP id xk17so2938802obc.10 for <ietf@ietf.org>; Fri, 31 May 2013 05:55:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Wms+3MB/AxB2v8lwKf5CxiadaSbkXIQ8VYR/zAkLtC8=; b=XWjYA12z9xZ3FYAgHuY9Jn0lJmsyvHHy660LtTLx7BFt8uDIUJjewWwyTdp1X1Pjly 0AesEC7/DDbZXsWIZrWc0KxRQt+A9ltEdxD443mIxQC8pU+uDN8CoSLjqjnfVOiHnYbg T2Wl2y3oajk8sqH1NpcjE1Kz8Sz+ZXoHOmXZo=
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=Wms+3MB/AxB2v8lwKf5CxiadaSbkXIQ8VYR/zAkLtC8=; b=Dtk4S09ujK452TxmGE1IIqdGYMVL5zOSOdHsOyFbhSBDS4TX7o55iWO9mbpgAjjv8q c0a4Iu8HpcasIyuhWnbSm4AaT4UNFpHo6JcBdxwTr1iONtg8R/+kdivNKRys6+PsMSqM CHJXcJqfwSkHPmGZpY5BX1+ixUdExyAWoRjwkcxPne3IsgtaE0BPG2pri/+mZFrQJk8b /TUMJlWBHx8281VMF5OsCjJ5/mlz9+1ZppYSpZ6Uzq9uDXusp4Gd/tdS4CJ3wX9Fy9H9 JjwVITNvjYRnNV5yyMLqZvDWqypAaNFxez4MAXItZ3v56W/icpotZw4AcRHav8enFNwy VmxA==
MIME-Version: 1.0
X-Received: by 10.60.37.133 with SMTP id y5mr5939117oej.123.1370004914608; Fri, 31 May 2013 05:55:14 -0700 (PDT)
Received: by 10.60.62.146 with HTTP; Fri, 31 May 2013 05:55:14 -0700 (PDT)
In-Reply-To: <BC324F37-6F05-463A-B537-AEB7C6CC08BA@tzi.org>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <BC324F37-6F05-463A-B537-AEB7C6CC08BA@tzi.org>
Date: Fri, 31 May 2013 13:55:14 +0100
Message-ID: <CAKHUCzxj5CkvQg7GEb_5U1U5TfVg1+TqFgQM0TeQbv9rZah0pg@mail.gmail.com>
Subject: Re: Time in the Air
From: Dave Cridland <dave@cridland.net>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=089e013c6e9047112a04de0320de
X-Gm-Message-State: ALoCoQmsi09kaskcQDVD2KwEfL/rLRnDRaSdke0QobhQTFCiTDbXHzQxYMVCnppXPxIco8fqkHBS
Cc: Mark Nottingham <mnot@mnot.net>, ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 12:55:19 -0000

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

On Fri, May 31, 2013 at 1:38 PM, Carsten Bormann <cabo@tzi.org> wrote:

> Of course, this doesn't include time-to-airport, so you can immediately
> discount London.
>

Well, you say that, but I now know why Alexey moved from Moscow to Kingston
(40 minutes to LHR on the X26).

Dave.

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

<div dir=3D"ltr">On Fri, May 31, 2013 at 1:38 PM, Carsten Bormann <span dir=
=3D"ltr">&lt;<a href=3D"mailto:cabo@tzi.org" target=3D"_blank">cabo@tzi.org=
</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
Of course, this doesn&#39;t include time-to-airport, so you can immediately=
 discount London.<br></blockquote><div><br></div><div style>Well, you say t=
hat, but I now know why Alexey moved from Moscow to Kingston (40 minutes to=
 LHR on the X26).</div>
<div style><br></div><div style>Dave.</div></div></div></div>

--089e013c6e9047112a04de0320de--

From arturo.servin@gmail.com  Fri May 31 06:01:16 2013
Return-Path: <arturo.servin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B707821F9691 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 06:01:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YJzthPKwJPVx for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 06:01:11 -0700 (PDT)
Received: from mail-ye0-f171.google.com (mail-ye0-f171.google.com [209.85.213.171]) by ietfa.amsl.com (Postfix) with ESMTP id D962E21F967F for <ietf@ietf.org>; Fri, 31 May 2013 06:01:10 -0700 (PDT)
Received: by mail-ye0-f171.google.com with SMTP id l2so343485yen.16 for <ietf@ietf.org>; Fri, 31 May 2013 06:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=sNE8/9c4VT8k9Utpb8+JdwnR0o9Dc2o2bgnYnJDuEus=; b=il1vQ3/o0HvO3EVHY4hAILQajMzYzKeif7NgrIy9CfNQTMS3a/QJF3pLX0Kgudn/u5 nEfWWV0JMcC1VRqeaDzyabb3UR9U+wkDGDt2BFdm+PrJIO/YHl9I9I3QP0KeipOGCpay deIiVBlgFoOTgeIANmrALAzcc93RkWPRnETFcU0xqQHF1wvO4kbE4hzgDNpOh1LP8Dn6 fk7HmfASFNhSzl0nWyqh89lxhoP04J/wnHCeXZ+1KEVTiNGH1WYmq00zotfkY7lJVrCq QXtw9VVICzww5eKUFDYqzGtXEn+LFPQmuzmP8bZZp71WO6m8Hb6VlCcSBK7aA28XeP4L uMxg==
X-Received: by 10.236.87.44 with SMTP id x32mr6726595yhe.117.1370005270444; Fri, 31 May 2013 06:01:10 -0700 (PDT)
Received: from Arturos-MacBook-Pro.local ([200.7.87.33]) by mx.google.com with ESMTPSA id l39sm16703111yhn.26.2013.05.31.06.01.08 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 06:01:09 -0700 (PDT)
Message-ID: <51A89F1C.3090503@gmail.com>
Date: Fri, 31 May 2013 10:01:16 -0300
From: Arturo Servin <arturo.servin@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF Meeting in South America
References: <20130523155412.29158.24895.idtracker@ietfa.amsl.com> <D41CEA8B-FC1A-4752-8375-4C68ACEF8793@piuha.net> <CAKfZcEuUC0f_xaNiRHUuDSc2zvbuSq+OsKVGXsU+0Gu5jHyYpA@mail.gmail.com> <51A44EC9.7080100@dcrocker.net> <F88F6DBF-49FD-4556-A544-5AD12F6BCA6E@standardstrack.com> <8D23D4052ABE7A4490E77B1A012B6307751B6352@mbx-01.win.nominum.com> <CAKfZcEsdKbfk4NueGz0oLivATpZ-yS3SazG4aw+TJjoDup4Rdw@mail.gmail.com> <51A4E625.3020406@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E90@EXMB01CMS.surrey.ac.uk> <51A5634B.4000707@gmail.com> <51A56797.2050208@lacnic.net> <51A56C53.7070709@gmail.com> <290E20B455C66743BE178C5C84F12408223F494E92@EXMB01CMS.surrey.ac.uk> <CAKr6gn1vDzd-LjO+dPKvzQdvy+=9dUg4maT3m+h4Onx5DYm7gQ@mail.gmail.com> <08CA5DA78C79446B431AC8B6@JcK-HP8200.jck.com> <CAKr6gn1VhNpW9C49hkH1=-rxWU8YkK5wCXaHEiBG1Lp3yA8VLQ@mail.gmail.com> <CADnDZ89C+ozDkYT+QdPwYSTR9qiz5+i4bXtGwwcMH51+NS_3Qw@mail.gmail.com> <CAPv4CP_ZSpw85pmJa81tQVxV4CiRcyZgo_eJvouU2o7LHcYSsw@mail.gmail.com>
In-Reply-To: <CAPv4CP_ZSpw85pmJa81tQVxV4CiRcyZgo_eJvouU2o7LHcYSsw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 13:01:16 -0000

On 5/31/13 9:53 AM, Scott Brim wrote:
> I don't know what the smiley is supposed to connote, but the IETF
> responds to changes in the community by changing its engineering goals
> and the problems it works on.

	I would add that the IETF should change the way we solve those problems
as another way to change.

	So in summary:

	- Change engineering goals
	- Change problems
	- Evolve the process to solve those problems



/as

From randy@psg.com  Fri May 31 06:34:58 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9458221F9425 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 06:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BLNBv2g1C5-8 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 06:34:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE1521F93F8 for <ietf@ietf.org>; Fri, 31 May 2013 06:34:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UiPTo-000LI7-Va; Fri, 31 May 2013 13:34:53 +0000
Date: Fri, 31 May 2013 06:34:52 -0700
Message-ID: <m2d2s7w9vn.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: [IETF] Re: Issues in wider geographic participation
In-Reply-To: <51A8063A.7030302@gmail.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <51A8063A.7030302@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: Fri, 31 May 2013 13:34:58 -0000

melinda,

i assure you that operations being 'owned' by vendors is not restricted
to the geographically isolated.  one small example.  i was asked to
consult on a global deployment by a global fortune whatever company
whose name you would all recognize.  there was no real management, and
the decisions were all done by a mid-level IT tech who was 'owned' by a
vendor.  when it was clear to me that i was there just to rubber-stamp
an ill-considered and ridiculously over-built solution, i walked.

otoh, i have worked in some pretty darned isolated environments where
the engineers worked very hard to get clue, participated in operator
fora, ...  come to the afnog workshops in two weeks.

> Perhaps we should be thinking about some alternative to engaging
> operators by trying to get them to schlep to meetings.  Something
> along the lines of a liaison process or creating a pipeline between us
> and NOGs.

actually this has become a popular sport in some segments of the ietf
community.  a bunch of ietfers come to nog meetings and participate on
nog lists.  after they got whacked for talking down to operators (the
two classics i loved were multiple cases of explainng what the ietf was,
and then one arrogant ipv6 ivory tower bigot "the HD ration is a hard
problem because operators do not know what a logarithm is"), the
interaction has been very useful.  i know a highly reputed security
researcher who took a year sabbatical and actually worked in ops.  some
iesg members have been very persistent about gaining ops clue.  all in
all, there is much more transfer across the membrane in both directions
than there was 15 years ago.  of course, as most things in life, we
could do better.

randy

From l.wood@surrey.ac.uk  Fri May 31 07:07:48 2013
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DF121F96EF for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.465
X-Spam-Level: 
X-Spam-Status: No, score=-5.465 tagged_above=-999 required=5 tests=[AWL=0.533,  BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fA0HSCuau3gj for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:07:44 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.112]) by ietfa.amsl.com (Postfix) with ESMTP id 52EEE21F883B for <ietf@ietf.org>; Fri, 31 May 2013 07:07:32 -0700 (PDT)
Received: from [193.109.255.147:7735] by server-8.bemta-14.messagelabs.com id 25/75-04364-2AEA8A15; Fri, 31 May 2013 14:07:30 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-72.messagelabs.com!1370009250!12162021!2
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17089 invoked from network); 31 May 2013 14:07:30 -0000
Received: from unknown (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-4.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 31 May 2013 14:07:30 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.180]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 31 May 2013 15:06:30 +0100
From: <l.wood@surrey.ac.uk>
To: <mnot@mnot.net>, <ietf@ietf.org>
Date: Fri, 31 May 2013 15:03:17 +0100
Subject: RE: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: Ac5d5Z6Vsp6OZUc2QgKk8+z6PNmtfQAIfsj8
Message-ID: <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
In-Reply-To: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 14:07:48 -0000

clearly, all IETF meetings should be in Cape Town, Wellington, or Perth, be=
cause more time in the air means more time without interruption where draft=
s can be read before the meeting.

quiet time on a plane can be productive time.

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


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mark Notti=
ngham [mnot@mnot.net]
Sent: 31 May 2013 10:59
To: ietf Discussion
Subject: Time in the Air

In an attempt to inject some data into the discussion, I wrote a bit of cod=
e that figures out how much time, given your home city, you would have spen=
t in the air if you'd attended all IETF meetings since IETF74 (i.e., from 2=
009 onwards).

The first column is the "home" airport.

The second column is the great circle time between the home airport and the=
 nearest large airport to the IETF meeting, hhh:mm. This doesn't count thin=
gs like transit time, taxiing, takeoff and landing overhead, indirect routi=
ng, etc. As such, this is an ideal number; the only way to achieve anything=
 close to it is to have a private jet (with exceptional range).

The third column is the time (hhh:mm) using the shortest-time routing on a =
travel booking engine. This is first-takeoff-to-last-landing time.

Both numbers assume round trip between "home" and the IETF airports.

SFO  204:10  282:04  // San Francisco
BOS  197:42  297:38  // Boston
ATL  205:44  297:28  // Atlanta
ANC  197:12  345:54  // Anchorage
LHR  198:02  249:44  // London
FRA  202:10  255:22  // Frankfurt
FCO  223:52  283:04  // Rome
SVO  211:28  287:14  // Moscow
TLV  264:12  334:22 // Israel
DXB  293:26  344:34 // Dubai
NRT  259:00  314:38  // Tokyo
HKG  296:38  359:22  // Hong Kong
BLR  332:28  448:24  // Bangalore
MEL  450:28  556:04  // Melbourne
AKL  442:24  569:04  // Auckland
JNB  414:30  498:22  // Johannesburg
EZE  411:10  522:56  // Buenos Aires
GIG  381:56  488:32  // Rio de Janeiro

Draw your own conclusions, of course.

One observation is that there's a 3+ days-in-the-air per year variance if y=
ou're a full-time participant, depending on where you live. I.e., more than=
 one day-per-meeting difference, on average. In the air alone.

Another is that, perhaps surprisingly, the "closest" homes to all meetings =
are in Europe, not the US (at least by shortest-time routing).

I can run other airports upon request, as well as make source available, bu=
t will do so conservatively, so as not to incur the ire of the services I'm=
 (ab)using.

Regards,

P.S. The IETF airports chosen were:

  IETF_airports: [
    "ORL",
    "ATL",
    "YVR",
    "CDG",
    "TPE",
    "YQB",
    "PRG",
    "PEK",
    "AMS",
    "LAX",
    "HIJ",
    "ARN",
    "SFO"
  ],

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




From framefritti@gmail.com  Fri May 31 07:18:48 2013
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 2888621F91BC for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_32=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDtyfKkNKrdk for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:18:46 -0700 (PDT)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 561E021F9123 for <ietf@ietf.org>; Fri, 31 May 2013 07:18:46 -0700 (PDT)
Received: by mail-la0-f51.google.com with SMTP id lx15so1430354lab.10 for <ietf@ietf.org>; Fri, 31 May 2013 07:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=qXsb40kJKV7sjDBHNp6wKY0UVkEpbbeSkhVG3g0yWWI=; b=bjw4mm98nXy7UW8deIQekY79XgwDlr6Y45mKchVPz5ruYI9MfbQk2IwTBwJsRX4TXp 1WNaUl7EGoq6A+aRR1dGzTfpTyaukdtd6RBMmJzV5yAZld5WXj6e5nt/CAYV1wOL+hxE ALpUecdCEGttWqcevm9G+2HHQfArPEm7jlGg4PMSFam4ozGjZiW6WstCIYZ3Gvc8jrQy d9gyd6oq/M+eCwrmAT589sjsPiLy2abizDVQi5OMWIZdRi5k7OegXSkMHA2rMiqceV5G xpbuWT/5DMyH7T5jbIp3zFRz25uAUToQEiDxazR3VVKNCkINdBAB01m0Ju/K69tOyxhX g3GQ==
MIME-Version: 1.0
X-Received: by 10.112.139.101 with SMTP id qx5mr6012808lbb.101.1370009925092;  Fri, 31 May 2013 07:18:45 -0700 (PDT)
Received: by 10.112.143.165 with HTTP; Fri, 31 May 2013 07:18:45 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
Date: Fri, 31 May 2013 16:18:45 +0200
Message-ID: <CABSMSPWfknR0X9kW49KLRnvRNZ3_=eXMbjka8pSMoeRD0cVoew@mail.gmail.com>
Subject: Re: Time in the Air
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 14:18:48 -0000

On Fri, May 31, 2013 at 4:03 PM,  <l.wood@surrey.ac.uk> wrote:
> clearly, all IETF meetings should be in Cape Town, Wellington, or Perth, =
because more time in the air means more time without interruption where dra=
fts can be read before the meeting.
>
> quiet time on a plane can be productive time.

Then I would suggest Antarctica as permanent location for future IETF
meetings.  :-) Maybe the only drawback is hotel availability, but
nothing that a handful of tents and sleeping bags cannot cure...
Also, penguins are cute :-)

>
> Lloyd Wood
> http://sat-net.com/L.Wood/
>
>
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mark Not=
tingham [mnot@mnot.net]
> Sent: 31 May 2013 10:59
> To: ietf Discussion
> Subject: Time in the Air
>
> In an attempt to inject some data into the discussion, I wrote a bit of c=
ode that figures out how much time, given your home city, you would have sp=
ent in the air if you'd attended all IETF meetings since IETF74 (i.e., from=
 2009 onwards).
>
> The first column is the "home" airport.
>
> The second column is the great circle time between the home airport and t=
he nearest large airport to the IETF meeting, hhh:mm. This doesn't count th=
ings like transit time, taxiing, takeoff and landing overhead, indirect rou=
ting, etc. As such, this is an ideal number; the only way to achieve anythi=
ng close to it is to have a private jet (with exceptional range).
>
> The third column is the time (hhh:mm) using the shortest-time routing on =
a travel booking engine. This is first-takeoff-to-last-landing time.
>
> Both numbers assume round trip between "home" and the IETF airports.
>
> SFO  204:10  282:04  // San Francisco
> BOS  197:42  297:38  // Boston
> ATL  205:44  297:28  // Atlanta
> ANC  197:12  345:54  // Anchorage
> LHR  198:02  249:44  // London
> FRA  202:10  255:22  // Frankfurt
> FCO  223:52  283:04  // Rome
> SVO  211:28  287:14  // Moscow
> TLV  264:12  334:22 // Israel
> DXB  293:26  344:34 // Dubai
> NRT  259:00  314:38  // Tokyo
> HKG  296:38  359:22  // Hong Kong
> BLR  332:28  448:24  // Bangalore
> MEL  450:28  556:04  // Melbourne
> AKL  442:24  569:04  // Auckland
> JNB  414:30  498:22  // Johannesburg
> EZE  411:10  522:56  // Buenos Aires
> GIG  381:56  488:32  // Rio de Janeiro
>
> Draw your own conclusions, of course.
>
> One observation is that there's a 3+ days-in-the-air per year variance if=
 you're a full-time participant, depending on where you live. I.e., more th=
an one day-per-meeting difference, on average. In the air alone.
>
> Another is that, perhaps surprisingly, the "closest" homes to all meeting=
s are in Europe, not the US (at least by shortest-time routing).
>
> I can run other airports upon request, as well as make source available, =
but will do so conservatively, so as not to incur the ire of the services I=
'm (ab)using.
>
> Regards,
>
> P.S. The IETF airports chosen were:
>
>   IETF_airports: [
>     "ORL",
>     "ATL",
>     "YVR",
>     "CDG",
>     "TPE",
>     "YQB",
>     "PRG",
>     "PEK",
>     "AMS",
>     "LAX",
>     "HIJ",
>     "ARN",
>     "SFO"
>   ],
>
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>

From Ted.Lemon@nominum.com  Fri May 31 07:36:24 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E838121F918C for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.563
X-Spam-Level: 
X-Spam-Status: No, score=-106.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OdvFo4-i9ANu for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:36:18 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 3422721F8B64 for <ietf@ietf.org>; Fri, 31 May 2013 07:36:15 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUai1XqaVQ7ctNwIC5ysHVv2q2s3ec4uN@postini.com; Fri, 31 May 2013 07:36:15 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 962811B81BF for <ietf@ietf.org>; Fri, 31 May 2013 07:36:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 844F7190052; Fri, 31 May 2013 07:36:14 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 31 May 2013 07:36:14 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Riccardo Bernardini <framefritti@gmail.com>
Subject: Re: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXeWSjFUui2nP5UiSlIvtTtrKp5kfyMCAgAAEUoCAAAThgA==
Date: Fri, 31 May 2013 14:36:13 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BEE64@mbx-01.win.nominum.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <CABSMSPWfknR0X9kW49KLRnvRNZ3_=eXMbjka8pSMoeRD0cVoew@mail.gmail.com>
In-Reply-To: <CABSMSPWfknR0X9kW49KLRnvRNZ3_=eXMbjka8pSMoeRD0cVoew@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <5C989957BE37984E92363FDBD06F7A1C@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 14:36:25 -0000

On May 31, 2013, at 10:18 AM, Riccardo Bernardini <framefritti@gmail.com> w=
rote:
> Then I would suggest Antarctica as permanent location for future IETF
> meetings.  :-) Maybe the only drawback is hotel availability, but
> nothing that a handful of tents and sleeping bags cannot cure...
> Also, penguins are cute :-)

This would also eliminate the July IETF, since it's too cold to travel to A=
ntarctica then.   So the savings in air travel time would no doubt be subst=
antial.


From spencerdawkins.ietf@gmail.com  Fri May 31 07:54:08 2013
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9CA21F96EA for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:54:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xygGH6jbRO6x for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 07:54:07 -0700 (PDT)
Received: from mail-vb0-x231.google.com (mail-vb0-x231.google.com [IPv6:2607:f8b0:400c:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 71A2821F947C for <ietf@ietf.org>; Fri, 31 May 2013 07:54:07 -0700 (PDT)
Received: by mail-vb0-f49.google.com with SMTP id q13so1094245vbe.22 for <ietf@ietf.org>; Fri, 31 May 2013 07:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=YkQOAxpT47ZLIZqSwJZhB72mldE3SNNhJoMLXtTbzLc=; b=tyzMa3CCMWrbKs1CMpFaxT+CoUBzDGpB2yWDLRHUG2pzh5JHBicT80zD30tT/d3+LO 4LtkbmGHS2CEZJhlJxSRdrvDjGk9ViBMXTnergOQZ3I/KX+W54K5eteL8981LARwYZkp cfMCGeIPx/2e70pYfkiojDTUd9X0vJ4lv18HU7/0YedbvH8n7dMLRhpQOLonulHcLz3J 4bl6FA3Gn3AjW1Tl2JMoSsswuEXwpRZjddYFwJCOLTzTwkJagZMn8Aj5oiiIE6atBME7 77n23AqPnHpEq2bVSmi0fyhQpofHoliZk0IJQ1jrhrxPtd9BcJlFkbKa2ROmest7hKgf sXcQ==
X-Received: by 10.220.188.201 with SMTP id db9mr10384953vcb.30.1370012045403;  Fri, 31 May 2013 07:54:05 -0700 (PDT)
Received: from [192.168.1.77] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net. [99.108.174.213]) by mx.google.com with ESMTPSA id kz18sm36013044vdb.13.2013.05.31.07.54.03 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 07:54:03 -0700 (PDT)
Message-ID: <51A8B961.9060801@gmail.com>
Date: Fri, 31 May 2013 09:53:21 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf Discussion <ietf@ietf.org>
Subject: "Hands across the water/hands across the sky"
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 14:54:08 -0000

For those of you looking at where I-D and RFC authors are from, I'd like 
to suggest one other thing to look at - the extent that participants are 
co-authoring with folks outside their region.

It's pretty tempting for new participants to submit drafts that they 
like, and maybe reaching out to their office mates as co-authors, but to 
be effective in the IETF, participants have to learn how to collaborate 
with folks from other IETF sponsors (including "other IETF sponsors who 
compete head-to-head with your IETF sponsor"), other countries, and 
other regions. "Collaboration" covers many activities, but I'm curious 
what we might learn from looking at this specific kind of collaboration.

<personal self-reveal> I say this to a lot of people who don't believe 
me, but I have been shy for most of my life, and it's still not easy for 
me to have conversations with total strangers. That's not a cultural 
challenge, and it's not a language challenge, but it is a challenge I've 
faced in the IETF as *I* was learning to collaborate. For anyone who is 
also learning how to do this - for me, it's been worth it. And anyone is 
welcome to join us for drumming at IETF meetings - I bring extra drums, 
and there's no telling who else you'll meet. </personal self-reveal>

Thanks,

Spencer

p.s. I apologize for the obscure reference in the Subject line to Paul & 
Linda McCartney's "Uncle Albert / Admiral Halsey" - it's from about 2:30 
into http://www.youtube.com/watch?v=XI6C7L66zq8.

From ke-oogaki@kddi.com  Fri May 31 02:35:20 2013
Return-Path: <ke-oogaki@kddi.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28C921F9701 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 02:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF4VcasOWmgx for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 02:35:16 -0700 (PDT)
Received: from UTMC1102.kddi.com (athena.kddi.com [210.141.112.39]) by ietfa.amsl.com (Postfix) with ESMTP id 7388221F96FB for <ietf@ietf.org>; Fri, 31 May 2013 02:35:15 -0700 (PDT)
Received: from UTMC1132 (unknown [10.5.16.195]) by UTMC1102.kddi.com (Postfix) with SMTP id 1A2E41C7B; Fri, 31 May 2013 18:35:14 +0900 (JST)
Received: from UTMC1123.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id DE2B91C15; Fri, 31 May 2013 18:35:05 +0900 (JST)
Received: from LTMC1005.kddi.com (unknown [10.5.16.216]) by UTMC1123.kddi.com (Postfix) with ESMTP id C4B811A7A; Fri, 31 May 2013 18:35:05 +0900 (JST)
Received: from LTMC1005.kddi.com (localhost.localdomain [127.0.0.1]) by LTMC1005.kddi.com  with ESMTP id r4V9Z5ha024411; Fri, 31 May 2013 18:35:05 +0900
Received: from LTMC1005.kddi.com.mid_18289012 (localhost.localdomain [127.0.0.1]) by LTMC1005.kddi.com  with ESMTP id r4V9P37L017168; Fri, 31 May 2013 18:25:03 +0900
Received: from KDDI0802PC0412 ([10.200.132.0] [10.200.132.0]) by post-zip.kddi.com with ESMTPA; Fri, 31 May 2013 18:25:03 +0900
From: "Ogaki, Kenichi" <ke-oogaki@kddi.com>
To: <adrian@olddog.co.uk>, <ietf@ietf.org>
References: <20130525012629.27814.9963.idtracker@ietfa.amsl.com> <07b701ce5931$6c93acd0$45bb0670$@olddog.co.uk>
In-Reply-To: <07b701ce5931$6c93acd0$45bb0670$@olddog.co.uk>
Subject: RE: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>	(Requirements for	GMPLS applications of PCE) to Informational RFC
Date: Fri, 31 May 2013 18:25:03 +0900
Message-Id: <00cf01ce5de0$bb29f670$317de350$@kddi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFqCM6wK8Jj72Y/bcq1okRvzWE3YQMMXeZImc9JbqA=
Content-Language: ja
X-SA-MID: 18289012
X-WAuditID: 1305311835060000229983
X-Mailman-Approved-At: Fri, 31 May 2013 08:18:17 -0700
Cc: draft-ietf-pce-gmpls-aps-req.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, 31 May 2013 09:35:20 -0000

Dear Adrian,

Thank you for your comments.

We will address your comments after this last call as follows.

> idnits shows a couple of issues with your references
> 
>   == Unused Reference: 'RFC3945' is defined on line 373, but no explicit
>      reference was found in the text
> 
>   == Unused Reference: 'RFC4927' is defined on line 402, but no explicit
>      reference was found in the text
> 
> These both seem like relevant references and I suggest that you find a
place
> in the text to point to them.

RFC3945 shall be referred in section 1, paragraph 2, sentence 2 as follows:
As the same case with MPLS, service providers (SPs) have also come up with
requirements for path computation in GMPLS-controlled networks [RFC3945]
such as wavelength, TDM-based or Ethernet-based networks as well.

RFC4927 shall be referred in section 1 paragraph 3 as follows:
Note that the requirements for inter-layer and inter-area traffic
engineering described in [RFC6457] and [RFC4927] are outside of the scope of
this document.


> Some work on acronyms, please.
> 
> PCE needs to be expanded on first use in the Abstract and the main text
> (not on the second use :-)
> 
> OTOH, MPLS and GMPLS do not need to be expanded.
> 
> PCC shows up in section 2.1
> PCReq and PCRep are in 2.1 (but expanded a little later) P2MP is in
section
> 2.2 ERO and XRO show in section 3.1 PCEP shows in section 3.2

All acronyms indicated above shall be correctly expanded or not expanded.


> Section 1 para 4 seems to say that SRLG is covered in RFC 3473. Are you
> sure? Or do you need a different reference?

SRLG shall be moved to the previous sentence and refer RFC 4202 as follows:
Constraint-based shortest path first (CSPF) computation within a domain or
over domains for signaling GMPLS Label Switched Paths (LSPs) is usually more
stringent than that of MPLS TE LSPs [RFC4216], because the additional
constraints, e.g., interface switching capability, link encoding, link
protection capability, SRLG (Shared Risk Link Group) [RFC4202] and so forth
need to be considered to establish GMPLS LSPs. 


> In Section 3.1 reqs (1), (2) and (3) you appear to be limiting the
supported
> values to only those listed or those in the referenced RFCs.
> 
> You may do better to say less. Just point at the base definition of the
> signaling fields (in RFC 3473?) and then say "all current and future
values".

reqs (1), (2) and (3) shall be rewritten as follows:
(1) Switching capability/type: as defined in [RFC3471], [RFC4203] and, all
current and future values.
(2) Encoding type: as defined in [RFC3471], [RFC4203] and, all current and
future values.
(3) Signal Type: as defined in [RFC4606] and, all current and future values.


> Section 6
> 
> Julien Meuric not Meulic

Sorry Julien, we shall correct this typo.

Thanks,
Kenichi

--
Kenichi Ogaki
KDDI | IP Transport Network Development Dept.
+81-(0)80-5945-9138 | www.kddi.com


> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Saturday, May 25, 2013 7:20 PM
> To: ietf@ietf.org
> Cc: draft-ietf-pce-gmpls-aps-req.all@tools.ietf.org
> Subject: RE: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>
> (Requirements for GMPLS applications of PCE) to Informational RFC
> 
> Hi,
> 
> Here are my review comments as responsible AD. Because they are minor
> comments, I am entering them as part of IETF last call rather than getting
> them fixed before last call. That should expedite the publication a
little.
> 
> Thanks,
> Adrian
> 
> ===
> 
> idnits shows a couple of issues with your references
> 
>   == Unused Reference: 'RFC3945' is defined on line 373, but no explicit
>      reference was found in the text
> 
>   == Unused Reference: 'RFC4927' is defined on line 402, but no explicit
>      reference was found in the text
> 
> These both seem like relevant references and I suggest that you find a
place
> in the text to point to them.
> 
> ---
> 
> Some work on acronyms, please.
> 
> PCE needs to be expanded on first use in the Abstract and the main text
> (not on the second use :-)
> 
> OTOH, MPLS and GMPLS do not need to be expanded.
> 
> PCC shows up in section 2.1
> PCReq and PCRep are in 2.1 (but expanded a little later) P2MP is in
section
> 2.2 ERO and XRO show in section 3.1 PCEP shows in section 3.2
> 
> 
> ---
> 
> Section 1 para 4 seems to say that SRLG is covered in RFC 3473. Are you
> sure? Or do you need a different reference?
> 
> ---
> 
> In Section 3.1 reqs (1), (2) and (3) you appear to be limiting the
supported
> values to only those listed or those in the referenced RFCs.
> 
> You may do better to say less. Just point at the base definition of the
> signaling fields (in RFC 3473?) and then say "all current and future
values".
> 
> ---
> 
> Section 6
> 
> Julien Meuric not Meulic
> 
> > -----Original Message-----
> > From: pce-bounces@ietf.org [mailto:pce-bounces@ietf.org] On Behalf Of
> > The IESG
> > Sent: 25 May 2013 02:26
> > To: IETF-Announce
> > Cc: pce@ietf.org
> > Subject: [Pce] Last Call: <draft-ietf-pce-gmpls-aps-req-07.txt>
> > (Requirements
> for
> > GMPLS applications of PCE) to Informational RFC
> >
> >
> > The IESG has received a request from the Path Computation Element WG
> > (pce) to consider the following document:
> > - 'Requirements for GMPLS applications of PCE'
> >   <draft-ietf-pce-gmpls-aps-req-07.txt> as Informational RFC
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2013-06-07. Exceptionally, comments may
> > be sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >    The initial effort of the PCE WG is specifically focused on MPLS
> >    (Multi-protocol label switching).  As a next step, this draft
> >    describes functional requirements for GMPLS (Generalized MPLS)
> >    application of PCE (Path computation element).
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-pce-gmpls-aps-req/ballot/
> >
> >
> > The following IPR Declarations may be related to this I-D:
> >
> >    http://datatracker.ietf.org/ipr/1869/
> > _______________________________________________
> > Pce mailing list
> > Pce@ietf.org
> > https://www.ietf.org/mailman/listinfo/pce



From Simo.Veikkolainen@nokia.com  Fri May 31 03:13:12 2013
Return-Path: <Simo.Veikkolainen@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE34521F85D1; Fri, 31 May 2013 03:13:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8BCmrkxiRN-3; Fri, 31 May 2013 03:13:07 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id CDA6821F8899; Fri, 31 May 2013 03:13:05 -0700 (PDT)
Received: from vaebh102.NOE.Nokia.com (vaebh102.europe.nokia.com [10.160.244.23]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r4VACawC026103; Fri, 31 May 2013 13:13:03 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.49]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 31 May 2013 13:13:11 +0300
Received: from 008-AM1MPN1-026.mgdnok.nokia.com ([169.254.6.223]) by 008-AM1MMR2-015.mgdnok.nokia.com ([65.54.30.49]) with mapi id 14.02.0328.011; Fri, 31 May 2013 10:14:03 +0000
From: <Simo.Veikkolainen@nokia.com>
To: <ron.even.tlv@gmail.com>, <draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Thread-Topic: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05
Thread-Index: Ac5cmCWECo5bIU14RKqGyok1y70zYABS86Tw
Date: Fri, 31 May 2013 10:14:03 +0000
Message-ID: <D09DAE6B636851459F7575D146EFB54B2405E4B4@008-AM1MPN1-026.mgdnok.nokia.com>
References: <000301ce5c98$278d0220$76a70660$@gmail.com>
In-Reply-To: <000301ce5c98$278d0220$76a70660$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-version: 3.5.9.3
x-tituslabs-classifications-30: TLPropertyRoot=Nokia;Confidentiality=Nokia Internal Use Only;Project=None;
x-headerinfofordlp: None
x-tituslabs-classificationhash-30: VgNFIFU9Hx+/nZJb9Kg7IieUVVR+P20VDCzpg3HHXu3iIt34TClchC1lFMW65RFpQIjYqffJgrmfD1cpNgGbjtK8fB7f+0feePD/3lFuEnnkEez1dWv4zZaxFseCBqz9vmPplcQguUY4aymB6E2FlXKMnVmqGMRGGOklYWAKTXB+mqjHKxFjyTSbRvCSq9ZSlLCqmfs3bpHtpJ6E8hoghaVDC0dozB9AWOU7rGBrPnu/tUoAuQ7hJg97r0tWFsJFeIUou2s76WJFRrdIzzPW2JgXZ1J8xbVDQ7xySsJFM8s=
x-originating-ip: [172.21.81.112]
Content-Type: multipart/alternative; boundary="_000_D09DAE6B636851459F7575D146EFB54B2405E4B4008AM1MPN1026mg_"
MIME-Version: 1.0
X-OriginalArrivalTime: 31 May 2013 10:13:11.0764 (UTC) FILETIME=[74BC2940:01CE5DE7]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Fri, 31 May 2013 08:18:29 -0700
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 10:13:12 -0000

--_000_D09DAE6B636851459F7575D146EFB54B2405E4B4008AM1MPN1026mg_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Roni,
Please see my answer below prefixed with [SV].

From: ext Roni Even [mailto:ron.even.tlv@gmail.com]
Sent: 29. toukokuuta 2013 21:13
To: draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-caps-05

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.
Please resolve these comments along with any other Last Call comments you m=
ay receive.

Document: draft-ietf-mmusic-sdp-miscellaneous-caps-05

Reviewer: Roni Even

Review Date:2013-5-29

IETF LC End Date: 2013-6-4

IESG Telechat date:



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





Major issues:



Minor issues:

1.       I can understand from the draft that when you have IP and PSTN net=
type it is requires that the ccap will be for the PSTN. What happens if you=
 want to have the ccap nettype as ATM to be used with IP in the c=3D



[SV] If either endpoint does not support ATM, the "c=3D" line with the ATM =
address would not get used (either it is not offered, or the Answerer remov=
es that from the SDP configurations). In case both endpoints actually suppo=
rt and want to use ATM as alternative to IP based bearer, the conventions i=
n RFC3108 would need to be followed when crafting the SDP configurations. T=
hat said, I haven't taken a detailed look at RFC3108 to see if the ATM base=
d media can be negotiated using the SDP Capability Negotiation framework an=
d its current extensions.



Simo


Nits/editorial comments:


--_000_D09DAE6B636851459F7575D146EFB54B2405E4B4008AM1MPN1026mg_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@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:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1745645097;
	mso-list-type:hybrid;
	mso-list-template-ids:-1464020766 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hello Roni,<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Please see my answer b=
elow prefixed with [SV].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<a name=3D"_____replyseparator"></a><b><span style=3D"font-size:10.0pt;font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span st=
yle=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quo=
t;"> ext Roni Even [mailto:ron.even.tlv@gmail.com]
<br>
<b>Sent:</b> 29. toukokuuta 2013 21:13<br>
<b>To:</b> draft-ietf-mmusic-sdp-miscellaneous-caps.all@tools.ietf.org<br>
<b>Cc:</b> ietf@ietf.org; gen-art@ietf.org<br>
<b>Subject:</b> Gen-ART LC review of draft-ietf-mmusic-sdp-miscellaneous-ca=
ps-05<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<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=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Document:
</span><span style=3D"font-family:&quot;Courier New&quot;">draft-ietf-mmusi=
c-sdp-miscellaneous-caps-05</span><span style=3D"font-size:11.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Reviewer: Roni Even<o:p></o:p></span=
></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Review Date:2013&#8211;5&#8211;29<o:=
p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">IETF LC End Date: 2013-6&#8211;4<o:p=
></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">IESG Telechat date:
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Summary: This draft is almost ready =
for publication as Standard track RFC.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Major issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">Minor issues:<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt;text-indent:-18.0pt;m=
so-list:l0 level1 lfo2">
<![if !supportLists]><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;"><span style=3D"mso-list:Ignore">1.<span s=
tyle=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;
</span></span></span><![endif]><span style=3D"font-size:11.0pt;font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;">I can understand from the draft=
 that when you have IP and PSTN nettype it is requires that the ccap will b=
e for the PSTN. What happens if you want to have the ccap
 nettype as ATM to be used with IP in the c=3D<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">[SV] If either endpoin=
t does not support ATM, the &#8220;c=3D&#8221; line with the ATM address wo=
uld not get used (either it is not offered, or the Answerer removes that
 from the SDP configurations). In case both endpoints actually support and =
want to use ATM as alternative to IP based bearer, the conventions in RFC31=
08 would need to be followed when crafting the SDP configurations. That sai=
d, I haven&#8217;t taken a detailed look
 at RFC3108 to see if the ATM based media can be negotiated using the SDP C=
apability Negotiation framework and its current extensions.<o:p></o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Simo<o:p></o:p></span>=
</p>
<p class=3D"MsoPlainText"><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_D09DAE6B636851459F7575D146EFB54B2405E4B4008AM1MPN1026mg_--

From amankin@verisign.com  Fri May 31 08:24:09 2013
Return-Path: <amankin@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 13EAC21F9455 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 08:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-Recl7r8IQx for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 08:24:00 -0700 (PDT)
Received: from exprod6og114.obsmtp.com (exprod6og114.obsmtp.com [64.18.1.33]) by ietfa.amsl.com (Postfix) with ESMTP id 301FB21F910D for <ietf@ietf.org>; Fri, 31 May 2013 08:24:00 -0700 (PDT)
Received: from peregrine.verisign.com ([216.168.239.74]) (using TLSv1) by exprod6ob114.postini.com ([64.18.5.12]) with SMTP ID DSNKUajAiiNluquXeyknsnUmudCO08gC4cBh@postini.com; Fri, 31 May 2013 08:24:00 PDT
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01.vcorp.ad.vrsn.com [10.173.152.255]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id r4VFNpco027090 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Fri, 31 May 2013 11:23:54 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.02.0342.003; Fri, 31 May 2013 11:23:51 -0400
From: "Mankin, Allison" <amankin@verisign.com>
To: IETF Discuss <ietf@ietf.org>
Subject: NOMCOM 2013 - validated volunteers so far
Thread-Topic: NOMCOM 2013 - validated volunteers so far
Thread-Index: AQHOXhLarsagX8xl8U+cZbwUrxVCEQ==
Date: Fri, 31 May 2013 15:23:51 +0000
Message-ID: <98E1DB20-30F2-4E1A-8BF8-654904ED81F7@verisign.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="utf-8"
Content-ID: <7712D9770DBFA7459B515376D2FBC765@verisign.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Mankin, Allison" <amankin@verisign.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 15:24:13 -0000

DQpIZXJlIGlzIHRoZSBjdXJyZW50IGxpc3Qgb2YgbmFtZXMgb2YgZWxpZ2libGUgdm9sdW50ZWVy
cyBmb3IgTm9tY29tIDIwMTMtMjAxNC4gIA0KDQpJZiB5b3VyIG5hbWUgaXMgbm90ICBhbHJlYWR5
IG9uIHRoaXMgbGlzdCwgd2hhdCBhcmUgeW91IHdhaXRpbmcgZm9yPyAgVGhhbmtzIHRvIHRob3Nl
IHdobyBoYXZlIGFscmVhZHkgdm9sdW50ZWVyZWQgYW5kIGFsbCBvZiB5b3Ugd2hvIGFyZSANCmFi
b3V0IHRvIHZvbHVudGVlciA6RA0KDQpJZiB5b3Ugdm9sdW50ZWVyZWQgYW5kIHdlcmVuJ3QgZWxp
Z2libGUsIEkndmUgc2VudCB5b3UgYSBtZXNzYWdlLiAgSWYgeW91J3JlIHN1cmUgeW91IGRpZCBh
dHRlbmQgMyBvdXQgb2YgSUVURnMgODIsIDgzLCA4NCwgODUgYW5kIDg2LCANCmFuZCBJIHNhaWQg
bm8sIGRpZyBhcm91bmQgYW5kIHNlbmQgc29tZSBtb3JlIGVtYWlsIGFkZHJlc3NlcyB5b3UgbWF5
IGhhdmUgdXNlZCB0byByZWdpc3Rlci4NCg0KQWxsaXNvbiBNYW5raW4gKDIwMTMgTm9tY29tIENo
YWlyKQ0KDQoNCkpvaG4gU2N1ZGRlcg0KU3RlcGhlbiBIYW5uYQ0KV2Fzc2ltIEhhZGRhZA0KUnVz
cyBXaGl0ZQ0KU3RlcGhhbiBXZW5nZXINClpIQU8gWWkNCkVyaWMgR3JheQ0KU3RldmUgS2VudA0K
VG9lcmxlc3MgRWNrZXJ0DQpBbGlhIEF0bGFzDQpWaWN0b3IgS3VhcnNpbmdoDQpZaXpob3UgTEkN
CkdvbnphbG8gU2FsZ3VlaXJvDQpHYW5nIENIRU4NCk5pbmcgS09ORw0KTWFyY2VsbyBCYWdudWxv
DQpTSEVOIFNodW8g5rKI54OBIChTZWFuKQ0KRmVybmFuZG8gR29udA0KR2xlbiBab3JuDQpSZWlu
YWxkbyBQZW5ubw0KS2xhYXMgV2llcmVuZ2ENClBhc2NhbCBUaHViZXJ0DQpNZWhtZXQgRXJzdWUN
Ck9sZSBUcm9hbg0KSm91bmkgS29yaG9uZW4NCkdpbGVzIEhlcm9uDQpHdW50ZXIgVmFuIGRlIFZl
bGRlDQpBcnR1cm8gU2VydmluDQpFcmljIFZ5bmNrZQ0KQ3VsbGVuIEplbm5pbmdzDQpUaW5hIFRz
b3UNCkRocnV2IERob2R5DQpIb25neXUgTEkgKEp1bGlvKQ0KU2NvdHQgTWFuc2ZpZWxkDQpKb2hu
IERyYWtlDQpBbmRyZXcgTWNMYWNobGFuDQpEZXJlayBBdGtpbnMNClN1aGFzIE5hbmRha3VtYXIN
CkVyaWMgUmVzY29ybGENCkthcmVuIFNlbw0KU3RpZyBWZW5hYXMNClN0YW4gUmF0bGlmZg0KSWdu
YXMgQmFnZG9uYXMNClBldGVyIFllZQ0KRG9uYWxkIEVhc3RsYWtlDQpaSE9VIFFpYW4gKENhdGh5
KQ0KU2FtIEhhcnRtYW4NCkxpeGlhIFpoYW5nDQpUZWVtdSBTYXZvbGFpbmVuDQpBbHZhcm8gUmV0
YW5hDQpUZXJyeSBNYW5kZXJzb24NCkJpbGwgVmVyU3RlZWcNCk1lbGluZGEgU2hvcmUNCklKc2Jy
YW5kIFdpam5hbmRzDQpLYXJlbiBPJ0Rvbm9naHVlDQpCZW5zb24gU2NobGllc3Nlcg0KQXJpIEtl
csOkbmVuDQpGYW5nd2VpIEhVDQpNYWNoIENIRU4NCkh1aSBEZW5nDQpMSVUgRGFwZW5nDQpKYWFw
IEFra2VyaHVpcw0KTWFnbnVzIFdlc3Rlcmx1bmQNClplaG4gQ0FPDQpaYWhlZHV6emFtYW4gU2Fy
a2VyDQpCaHVtaXAgS2hhc25hYmlzaA0KQW5kcmV3IENoaQ0KVGhvbWFzIE5hZGVhdQ0KU3RldmVu
IEMgKENyYWlnKSBXaGlsdGUNCk9yaXQgTGV2aW4NClNhbSBBbGRyaW4NClBhdWwgRWJlcnNtYW4N
CkNocmlzdG9waGVyIExpbGplbnN0b2xwZQ0KVW1hIENodW5kdXJpDQpTdXJlc2ggS3Jpc2huYW4N
ClZhcnVuIFNpbmdoDQpSb24gQm9uaWNhDQpCaWxsIChXaWxsaWFtKSBNYW5uaW5nDQpSYWRpYSBQ
ZXJsbWFuDQpEYW5pZWxlIENlY2NhcmVsbGkNCkRlYm9yYWggQnJ1bmdhcmQNCktvc3RhcyBQZW50
aWtvdXNpcw0KR3JlZ29yeSBNaXJza3kNCkRhdmUgU2luaWNyb3BlDQpUaG9tYXMgV2Fsc2gNClpo
YW9odWkgKEplZmZyZXkpIFpIQU5HDQpYaWFuIFpIQU5HDQoNCg==

From john-ietf@jck.com  Fri May 31 09:36:28 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E478021F9622 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 09:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100
X-Spam-Level: 
X-Spam-Status: No, score=-100 tagged_above=-999 required=5 tests=[USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEScioEp8NgO for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 09:36:23 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1152D21F9611 for <ietf@ietf.org>; Fri, 31 May 2013 09:36:23 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UiSJL-0006G4-PQ; Fri, 31 May 2013 12:36:15 -0400
Date: Fri, 31 May 2013 12:36:03 -0400
From: John C Klensin <john-ietf@jck.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Issues in wider geographic participation
Message-ID: <06F3F685960B0132E0BC1AAC@JcK-HP8200.jck.com>
In-Reply-To: <51A87D42.9010603@si6networks.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <51A87D42.9010603@si6networks.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, 31 May 2013 16:36:29 -0000

--On Friday, May 31, 2013 12:36 +0200 Fernando Gont
<fgont@si6networks.com> wrote:

>> if the vendor presence is limited to marketing, sales, and
>> perhaps implementation, then, if that is a problem, it is one
>> that doesn't lie easily within IETF scope... and probably
>> shouldn't.
> 
> Do open source developers count? -- With Android and the like,
> they end up producing more deployed implementations than
> anyone else.

Sure  they count.  What they often don't do is have the support
to attend expensive f2f IETF meetings in far-away places.  

Holding meetings closer to them might well make everyone feel
warm and fuzzy, and that might justify such meeting locations
(as I have said more generally all along).  But, if we want
increased participation from that community, we need to address
participation issues and the economics of the way we do business
and not think that locating a meeting or two close to people or
organizations who don't already participate will make a huge
difference.

    john


From warren@kumari.net  Fri May 31 10:47:49 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F6D021F8FEB for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 10:47:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.7
X-Spam-Level: 
X-Spam-Status: No, score=-99.7 tagged_above=-999 required=5 tests=[AWL=-0.300,  J_CHICKENPOX_32=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uDEIVDIL7qj4 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 10:47:43 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3111B21F8F83 for <ietf@ietf.org>; Fri, 31 May 2013 10:47:42 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 1AA3C1B40A6B; Fri, 31 May 2013 13:47:42 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] RE: Time in the Air
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
Date: Fri, 31 May 2013 13:47:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1503)
Cc: mnot@mnot.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: Fri, 31 May 2013 17:47:49 -0000

On May 31, 2013, at 10:03 AM, <l.wood@surrey.ac.uk> wrote:

> clearly, all IETF meetings should be in Cape Town, Wellington, or =
Perth, because more time in the air means more time without interruption =
where drafts can be read before the meeting.
>=20
> quiet time on a plane can be productive time.

Until more airlines start offering in-flight Internets=85

I treasure my time on a plane, as it mean I can actually write some =
draft, etc. Once there is Internet -- yes, I *could* always just turn =
off my Wifi / not sign up for the in-flight bits, but I'm not =
disciplined enough.
I end up deciding I quickly need to look up some reference and then: =
http://xkcd.com/214/

W=20

>=20
> Lloyd Wood
> http://sat-net.com/L.Wood/
>=20
>=20
> ________________________________________
> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mark =
Nottingham [mnot@mnot.net]
> Sent: 31 May 2013 10:59
> To: ietf Discussion
> Subject: [IETF] Time in the Air
>=20
> In an attempt to inject some data into the discussion, I wrote a bit =
of code that figures out how much time, given your home city, you would =
have spent in the air if you'd attended all IETF meetings since IETF74 =
(i.e., from 2009 onwards).
>=20
> The first column is the "home" airport.
>=20
> The second column is the great circle time between the home airport =
and the nearest large airport to the IETF meeting, hhh:mm. This doesn't =
count things like transit time, taxiing, takeoff and landing overhead, =
indirect routing, etc. As such, this is an ideal number; the only way to =
achieve anything close to it is to have a private jet (with exceptional =
range).
>=20
> The third column is the time (hhh:mm) using the shortest-time routing =
on a travel booking engine. This is first-takeoff-to-last-landing time.
>=20
> Both numbers assume round trip between "home" and the IETF airports.
>=20
> SFO  204:10  282:04  // San Francisco
> BOS  197:42  297:38  // Boston
> ATL  205:44  297:28  // Atlanta
> ANC  197:12  345:54  // Anchorage
> LHR  198:02  249:44  // London
> FRA  202:10  255:22  // Frankfurt
> FCO  223:52  283:04  // Rome
> SVO  211:28  287:14  // Moscow
> TLV  264:12  334:22 // Israel
> DXB  293:26  344:34 // Dubai
> NRT  259:00  314:38  // Tokyo
> HKG  296:38  359:22  // Hong Kong
> BLR  332:28  448:24  // Bangalore
> MEL  450:28  556:04  // Melbourne
> AKL  442:24  569:04  // Auckland
> JNB  414:30  498:22  // Johannesburg
> EZE  411:10  522:56  // Buenos Aires
> GIG  381:56  488:32  // Rio de Janeiro
>=20
> Draw your own conclusions, of course.
>=20
> One observation is that there's a 3+ days-in-the-air per year variance =
if you're a full-time participant, depending on where you live. I.e., =
more than one day-per-meeting difference, on average. In the air alone.
>=20
> Another is that, perhaps surprisingly, the "closest" homes to all =
meetings are in Europe, not the US (at least by shortest-time routing).
>=20
> I can run other airports upon request, as well as make source =
available, but will do so conservatively, so as not to incur the ire of =
the services I'm (ab)using.
>=20
> Regards,
>=20
> P.S. The IETF airports chosen were:
>=20
>  IETF_airports: [
>    "ORL",
>    "ATL",
>    "YVR",
>    "CDG",
>    "TPE",
>    "YQB",
>    "PRG",
>    "PEK",
>    "AMS",
>    "LAX",
>    "HIJ",
>    "ARN",
>    "SFO"
>  ],
>=20
> --
> Mark Nottingham   http://www.mnot.net/
>=20
>=20
>=20

--=20
Do not meddle in the affairs of wizards, for they are subtle and quick =
to anger. =20
    -- J.R.R. Tolkien



From carlosm3011@gmail.com  Fri May 31 10:55:04 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE25C21F8E79 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 10:55:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.292
X-Spam-Level: *
X-Spam-Status: No, score=1.292 tagged_above=-999 required=5 tests=[BAYES_50=0.001, MISSING_HEADERS=1.292, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XJs2PVezQ2ju for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 10:55:03 -0700 (PDT)
Received: from mail-ve0-x22b.google.com (mail-ve0-x22b.google.com [IPv6:2607:f8b0:400c:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 9F79921F89FF for <ietf@ietf.org>; Fri, 31 May 2013 10:54:59 -0700 (PDT)
Received: by mail-ve0-f171.google.com with SMTP id b10so1356123vea.16 for <ietf@ietf.org>; Fri, 31 May 2013 10:54:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=H3lkDiP8wnGbSfeTkGl0WE7kJCNulwmI6NxyFefFFiM=; b=GgSMIGQPTNWZcUpW6l0o1sB0P3/oL1Ualun4Zp1cRMcl4tem67sDYMsoSUCznO3XI+ TkDKYijWqXqMFXBEnZiID9wRcupMWkfx2l9l1rScT0huw3icOtLtdpOMxrsyrofZYhB5 IgcfgTU8t2Kklo03u2BfHExtFXHjpRavc6BH3xDdnsSR/ZSzWm2PAc+u1fohmdFr+/nl 0xHByJHbT02MvOxSUrrld/bbk7Lw0y53BirYS8htwsYKeiDhshxGdu61kgVxZ+jyT3hQ KoBkjbDd89CsFJVVrl44xSxXa5PvjtKf3dceeiEzcCXKXQqVIC1fL2c68bflrjY4ONEX SpQQ==
X-Received: by 10.52.89.234 with SMTP id br10mr9509110vdb.103.1370022899060; Fri, 31 May 2013 10:54:59 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:2187:37f7:dbe9:e921]) by mx.google.com with ESMTPSA id io3sm36693494vdb.12.2013.05.31.10.54.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 10:54:58 -0700 (PDT)
Message-ID: <51A8E3EE.5060807@gmail.com>
Date: Fri, 31 May 2013 14:54:54 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com>
In-Reply-To: <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 17:55:04 -0000

Jorge,

I seriously believe you're overreacting and overrepresenting the actual
view of the people in Argentina. Few, if any, members of the Internet
community in Argentina and neighboring countries share this view, and
almost all of us can't help laughing at the ironic situation where some
people use 'the secret weapon of the imperialist establishment' to
distribute their 'anti-imperialist' message :D. So much for secret weapons.

Not only that. In addition, the Internet and social networks have had a
key role in the recent protests against the government. And since the
electoral vote is split in almost identical 'halves', there are as many
people likely to be against the view described in your URL as there are
likely to be in favour of it.

And since, as Oscar Wilde put it, 'the only worse thing than being
talked about is not being talked about', if our meeting there is public
enough to warrant a public demonstration, it would in the end be a
positive thing for us. We'll have something to remember, like the
flooding in Dallas in '06 :D

But don't brace for it. Those who are into this kind of political
wrangling there have other, of much higher visibility, opportunities to
get their 'message' out than stand outside some hotel protesting against
an obscure gathering of engineers.

regards

~Carlos

On 5/27/13 3:16 AM, Jorge Amodio wrote:
> 
> The financial and political current situation is more complex than just
> the manipulation and restrictions on currency exchange and payment of
> obligations.
> 
> I feel that is totally OT but for example we have supporters of the
> current government like this one, claiming to be a writer, that if you
> are able to read in Spanish or helped by a translator to read his
> article, you will learn that he is propagating a message that says
> "Internet is the secret weapon of the imperialism." 
> 
> http://sumateacristina.net/m/blogpost?id=6438092%3ABlogPost%3A524963
> 
> His view is shared by many, so in the event IETF gets to meet in Buenos
> Aires, if the meeting becomes public, don't be surprised to see some
> coordinated political manifestation.
> 
> Funny thing, does he realize what is he using to propagate his message ?
> 
> I'd really love to see folks from my country become more involved with
> IETF, the opportunity for more outreach and engagement, and also visit
> my country, but as Dave said IETF is not in the tourism business and
> there could be more effective ways to develop some program with long
> term effects to drive more regional participation.
> 
> As I said before, just a meeting won't do.
> 
> Regards,
> 
> -Jorge
> 

From aeopare@gmail.com  Fri May 31 11:06:00 2013
Return-Path: <aeopare@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC1D521F9051 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4KqHj7nhh5X8 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:06:00 -0700 (PDT)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 048A321F904B for <ietf@ietf.org>; Fri, 31 May 2013 11:05:56 -0700 (PDT)
Received: by mail-ob0-f171.google.com with SMTP id dn14so3601668obc.2 for <ietf@ietf.org>; Fri, 31 May 2013 11:05:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=vidhUrOZy+GaGr11r1dPR8xIGlrInA2lqyCspvU4YbM=; b=nESloPBigCAXzbdKvb1hiPniD1DLDskO4BBYzeni+M+Da1rRP8gq54UKUYc9xUYUpx H3gJkJSxAJyNmNpwlozpBuT/yd4wz2MWaWp7twDvZXxNdygIgI87WU0FjtqYQ7iHQxJV CC9zaythVHWkcyAjjj5nWNBdBLQiYWFkJQhOBQS7mCsTcOl0RWJnigfM19jVbn1TAFrS wEbO8VwMg43XbZxgjQtmnSeDh5WPUFDBD7rNqi3vcx+CvLZ1B9gJM78JoeTpYRxzFDiq QOK0no6O7gTFFiDirxBVqBWHLAeLuFDQrFujv21P0B8nm6ixJWr2xXQpbMQGbDCdArgK Fcyw==
MIME-Version: 1.0
X-Received: by 10.60.134.71 with SMTP id pi7mr6349829oeb.107.1370023554557; Fri, 31 May 2013 11:05:54 -0700 (PDT)
Received: by 10.60.144.7 with HTTP; Fri, 31 May 2013 11:05:54 -0700 (PDT)
Date: Fri, 31 May 2013 18:05:54 +0000
Message-ID: <CANeGSFn7JEvgbsQHTWYM5sAam_KW+EbE_dC2T-dhm0sJHTwq+g@mail.gmail.com>
Subject: Congratulations Bob Hinden!
From: "Edwin A. Opare" <aeopare@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=047d7b4720764db33604de0777c6
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:06:01 -0000

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

Dear All,

The Internet Society has just completed its Board of Trustees Elections and
appointments.The  IAB  re-appointed Bob Hinden as the IETF appointee to the
ISOC Board.

Folks, let us join hands in congratulating Bob for his re-appointment to
the ISOC Board.

Congratulations to you Bob on behalf of myself.

Best,

EAO

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

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:13px=
">Dear All,</span><div><span style=3D"font-family:arial,sans-serif;font-siz=
e:13px"><br></span></div><div><span style=3D"font-family:arial,sans-serif;f=
ont-size:13px">The Internet Society has just completed its Board of Trustee=
s Elections and appointments.The =A0IAB =A0re-appointed Bob Hinden as the I=
ETF appointee to the ISOC Board.</span><br>

</div><div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Folks, let us join hands in congratulating Bob for his re-appointm=
ent to the ISOC Board.=A0</span></div>
<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Congratulations to you Bob on behalf of myself.</span></div><div><=
span style=3D"font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Best,</span></div><div style><span style=3D"font-family:arial,sans=
-serif;font-size:13px"><br></span></div><div style><span style=3D"font-fami=
ly:arial,sans-serif;font-size:13px">EAO</span></div>
</div>

--047d7b4720764db33604de0777c6--

From jmamodio@gmail.com  Fri May 31 11:07:26 2013
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 F24D021F9123 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:07:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjvcPM6Xo9y9 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:07:25 -0700 (PDT)
Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [IPv6:2607:f8b0:400c:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5921121F904B for <ietf@ietf.org>; Fri, 31 May 2013 11:07:25 -0700 (PDT)
Received: by mail-vb0-f42.google.com with SMTP id w15so1266271vbf.15 for <ietf@ietf.org>; Fri, 31 May 2013 11:07:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JTeo6max+ynvAda+LqUN4nSCcy9+9tjpIWo3Ck+I2ms=; b=WIjfat1GakJ1IP20vxzhqtEKeevIeh9jbsg3AXRmC2mJvtB9mSGfGOhNuZ5vGjOmNp y6kI2cKLywjh84dCdbTGXQqQruXDRg5aW1KL4E7VLvmikFvfzaE7eqxj8sI5dDQf0vKy SBPn6pjScvlVKFwvda7hyU5ndpLCI23xdiP2pSUdObTQg1YnmSx2G+AnEUWVHecc+GDN SZR4WEHi/ct7qnqkjZiSM6oodgianXmW0elco2GYrRTDTExN+Mk7oFFk215Sa2XolS1h LP3oViljmJagVQNRoN1FoqHU7/AmpkmAZUTMaMVYnR/B4l13PmvNszrshZEYf1eAdAfT uc0A==
MIME-Version: 1.0
X-Received: by 10.220.192.3 with SMTP id do3mr11304353vcb.16.1370023644811; Fri, 31 May 2013 11:07:24 -0700 (PDT)
Received: by 10.58.2.138 with HTTP; Fri, 31 May 2013 11:07:24 -0700 (PDT)
In-Reply-To: <51A8E3EE.5060807@gmail.com>
References: <20130527041505.7301.qmail@joyce.lan> <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com> <51A8E3EE.5060807@gmail.com>
Date: Fri, 31 May 2013 13:07:24 -0500
Message-ID: <CAMzo+1Z2UZm1tA3qu00EFbrfTOUSowwwX3qDkv9O3fnh==+xnQ@mail.gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
From: Jorge Amodio <jmamodio@gmail.com>
To: carlos@lacnic.net
Content-Type: multipart/alternative; boundary=001a11c1ed3eaf0b2c04de077cb3
Cc: "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <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: Fri, 31 May 2013 18:07:26 -0000

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

Carlos, I clearly stated that the comment was OT, ie didn't have to much
relation with the discussion. I'm not overreacting or misrepresenting
anything, it was just an OT comment about a blog article which IMHO I
consider really stupid and completely out of lalaland.

I didn't say a protest WILL happen, I said "don't get surprised" if some of
these characters show up waiving the flags against the oppressing
imperialism.

Anyway this dialog will not contribute anything,  the only point I keep
making is while I consider a meeting in Buenos Aires a good idea, a better
planned and thought approach may drive more long term participation, like
finding the way to ensure that people that are already active participants
in the IETF process and those who have the skills and motivation can go to
the meetings wherever they take place without worrying too much about how
to obtain the resources to do so.

-J

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

<div dir=3D"ltr"><br><div style>Carlos, I clearly stated that the comment w=
as OT, ie didn&#39;t have to much relation with the discussion. I&#39;m not=
 overreacting or misrepresenting anything, it was just an OT comment about =
a blog article which IMHO I consider really stupid and completely out of la=
laland.</div>
<div style><br></div><div style>I didn&#39;t say a protest WILL happen, I s=
aid &quot;don&#39;t get surprised&quot; if some of these characters show up=
 waiving the flags against the oppressing imperialism.</div><div style>
<br></div><div style>Anyway this dialog will not contribute anything, =A0th=
e only point I keep making is while I consider a meeting in Buenos Aires a =
good idea, a better planned and thought approach may drive more long term p=
articipation, like finding the way to ensure that people that are already a=
ctive participants in the IETF process and those who have the skills and mo=
tivation can go to the meetings wherever they take place without worrying t=
oo much about how to obtain the resources to do so.</div>
<div style><br></div><div style>-J</div><div style><br></div></div>

--001a11c1ed3eaf0b2c04de077cb3--

From scott.brim@gmail.com  Fri May 31 11:12:08 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDA1C21F8FEB for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id va7M3bqwPG1U for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:12:07 -0700 (PDT)
Received: from mail-ea0-x22e.google.com (mail-ea0-x22e.google.com [IPv6:2a00:1450:4013:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 1990221F8E2C for <ietf@ietf.org>; Fri, 31 May 2013 11:12:06 -0700 (PDT)
Received: by mail-ea0-f174.google.com with SMTP id z7so1921589eaf.33 for <ietf@ietf.org>; Fri, 31 May 2013 11:12:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=lq3q0s6ay04yoQ7VUMUuKLQoIDfzsywnD2XgS5UYmww=; b=aejmiK5QTef9io6p97GSeHOAJ+niCi8DCWaW9wKlfDVAo4nsK4gDqoF75ConYXEO86 tnanb7gKziF38Yl0NqNI30lP8IzpprrlmjhJE+lct6r58U6Y0d3zcpPJ9JbtWtHb3cTV iCc0gmtIr6xhSIbPf+6AaqrY3cpL4wNhFJlGev8e3LYtgBllmMLHBVfT9NLOXfQoyO8E giVwWD1zBqgCP5emUrYJXi7vY/5MBOUIhvFcA1+FLLTqFaPO4p0UVhfhT8WLSw6Qy5nn S83xjZHMauHbWtf7WrDakkCD5bZ1SKiBDzy0TWTadqTt7j41n7xECvxa1ZmABVFuiHvY tmPA==
MIME-Version: 1.0
X-Received: by 10.15.21.65 with SMTP id c41mr13958413eeu.3.1370023926230; Fri, 31 May 2013 11:12:06 -0700 (PDT)
Received: by 10.14.117.12 with HTTP; Fri, 31 May 2013 11:12:06 -0700 (PDT)
In-Reply-To: <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net>
Date: Fri, 31 May 2013 14:12:06 -0400
Message-ID: <CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com>
Subject: Re: Time in the Air
From: Scott Brim <scott.brim@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=089e0158c67475139404de078d10
Cc: "mnot@mnot.net" <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:12:08 -0000

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

If people are interested, we could launch a new service: dirigible tours
with Internet access.  We'll have multiple airships, one for each set of
related meeting rooms.  Of course we'll have audio, jabber and all the
virtualization tools we have today.  We'll amble along at some moderate
speed, docking every night in order to take on supplies and allow people to
switch airships, and docking for a full week in some major city three times
each year.  The IETF will slowly work its way around the world, following
the winds and weather.

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

If people are interested, we could launch a new service: dirigible tours wi=
th Internet access. =A0We&#39;ll have multiple airships, one for each set o=
f related meeting rooms. =A0Of course we&#39;ll have audio, jabber and all =
the virtualization tools we have today. =A0We&#39;ll amble along at some mo=
derate speed, docking every night in order to take on supplies and allow pe=
ople to switch airships, and docking for a full week in some major city thr=
ee times each year. =A0The IETF will slowly work its way around the world, =
following the winds and weather. =A0

--089e0158c67475139404de078d10--

From carlosm3011@gmail.com  Fri May 31 11:13:38 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7540F21F8FDD for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.354
X-Spam-Level: 
X-Spam-Status: No, score=-0.354 tagged_above=-999 required=5 tests=[AWL=1.646,  BAYES_00=-2.599, J_CHICKENPOX_32=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVmXHUjInXWr for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:13:34 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1C0B121F85E8 for <ietf@ietf.org>; Fri, 31 May 2013 11:13:34 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id pa12so1366501veb.25 for <ietf@ietf.org>; Fri, 31 May 2013 11:13:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=hvjB7LxOEiWcbauwg56uNdbQYvBnT+bam9XdN0eMYEI=; b=ZskMK7ZFmLLVG5CUtmE5xTvBtZLYMuAvc2lgIDHlKAyfIpU4tEAtRHuLao+5kIFUwY 6pLgLqlIJ/I/JKh/BhmrJLgpGRbjcw1RE9F7DGtBjkIAAA+S9hsgW2SLBgSrfcCqgltC g6XYM++EOSA2aBxlWtzjvzz5RxBJ8Phg3AHALZubP5Ak4u3xQkecWAPJD9EFYhld8Nyi W7S17pkrd1fsjENxbKySCw8B4kp8L5XdrKbVVJ2ilqg8eFC2a+f+3Wp0AmRo1d9qEABw Fjj2b28Kkxq96oi6mQbC6B6mMiPJ6aGve1haxGeZaW4qlM3ISu1qISm+FI0rLhVYujfA Jf3A==
X-Received: by 10.52.34.70 with SMTP id x6mr9955367vdi.53.1370024013559; Fri, 31 May 2013 11:13:33 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:14e7:ee34:f855:da9b]) by mx.google.com with ESMTPSA id nr3sm36176812veb.4.2013.05.31.11.13.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 11:13:32 -0700 (PDT)
Message-ID: <51A8E847.9020804@gmail.com>
Date: Fri, 31 May 2013 15:13:27 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] RE: Time in the Air
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net>
In-Reply-To: <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: mnot@mnot.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:13:38 -0000

We now live in a blessed, sort-of, time, where you perhaps have
in-flight Internet but no-one presumes you do, so you get the Internet
and its benefits without the constant distraction of other people
calling, emailing and expecting immediate answers and all that :D

Completely off-topic too, but since I live in the southernmost capital
city of the world, and certainly not the best served by airlines, I use
*a lot* the services of the Great Circle Mapper, http://gcmap.com in
order to estimate flight times and shortest routes.

To estimate flight times, you need to enter your speed. Completely
unscientific experimenting on my part yielded that for short flights
(less than 2.5 hours) you should use 750 km/h and for longer flights
either 800, 850 or even 900. This is good enough for getting quite
accurate results. This takes into account the low speeds phases of
flight (climb out and landing approach).

Oh... and your results are fully bookmark-able, so you don't need to
reenter data to revisit a previously analyzed route.

E.g. two possible routes for my next IETF trip:

http://www.gcmap.com/dist?P=MVD-CDG%2CCDG-TXL&DU=km&DM=&SG=850&SU=kph
http://www.gcmap.com/dist?DU=km&P=MVD-GRU,+GRU-FRA,+FRA-TXL&SG=850&SU=kph

( I haven't really checked whether the FRA-TXL flight actually exists,
just an example )


The guy is going to completely hate me for the traffic he is going to get :D

cheers!

~Carlos

On 5/31/13 2:47 PM, Warren Kumari wrote:
> 
> On May 31, 2013, at 10:03 AM, <l.wood@surrey.ac.uk> wrote:
> 
>> clearly, all IETF meetings should be in Cape Town, Wellington, or Perth, because more time in the air means more time without interruption where drafts can be read before the meeting.
>>
>> quiet time on a plane can be productive time.
> 
> Until more airlines start offering in-flight Internets…
> 
> I treasure my time on a plane, as it mean I can actually write some draft, etc. Once there is Internet -- yes, I *could* always just turn off my Wifi / not sign up for the in-flight bits, but I'm not disciplined enough.
> I end up deciding I quickly need to look up some reference and then: http://xkcd.com/214/
> 
> W 
> 
>>
>> Lloyd Wood
>> http://sat-net.com/L.Wood/
>>
>>
>> ________________________________________
>> From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] On Behalf Of Mark Nottingham [mnot@mnot.net]
>> Sent: 31 May 2013 10:59
>> To: ietf Discussion
>> Subject: [IETF] Time in the Air
>>
>> In an attempt to inject some data into the discussion, I wrote a bit of code that figures out how much time, given your home city, you would have spent in the air if you'd attended all IETF meetings since IETF74 (i.e., from 2009 onwards).
>>
>> The first column is the "home" airport.
>>
>> The second column is the great circle time between the home airport and the nearest large airport to the IETF meeting, hhh:mm. This doesn't count things like transit time, taxiing, takeoff and landing overhead, indirect routing, etc. As such, this is an ideal number; the only way to achieve anything close to it is to have a private jet (with exceptional range).
>>
>> The third column is the time (hhh:mm) using the shortest-time routing on a travel booking engine. This is first-takeoff-to-last-landing time.
>>
>> Both numbers assume round trip between "home" and the IETF airports.
>>
>> SFO  204:10  282:04  // San Francisco
>> BOS  197:42  297:38  // Boston
>> ATL  205:44  297:28  // Atlanta
>> ANC  197:12  345:54  // Anchorage
>> LHR  198:02  249:44  // London
>> FRA  202:10  255:22  // Frankfurt
>> FCO  223:52  283:04  // Rome
>> SVO  211:28  287:14  // Moscow
>> TLV  264:12  334:22 // Israel
>> DXB  293:26  344:34 // Dubai
>> NRT  259:00  314:38  // Tokyo
>> HKG  296:38  359:22  // Hong Kong
>> BLR  332:28  448:24  // Bangalore
>> MEL  450:28  556:04  // Melbourne
>> AKL  442:24  569:04  // Auckland
>> JNB  414:30  498:22  // Johannesburg
>> EZE  411:10  522:56  // Buenos Aires
>> GIG  381:56  488:32  // Rio de Janeiro
>>
>> Draw your own conclusions, of course.
>>
>> One observation is that there's a 3+ days-in-the-air per year variance if you're a full-time participant, depending on where you live. I.e., more than one day-per-meeting difference, on average. In the air alone.
>>
>> Another is that, perhaps surprisingly, the "closest" homes to all meetings are in Europe, not the US (at least by shortest-time routing).
>>
>> I can run other airports upon request, as well as make source available, but will do so conservatively, so as not to incur the ire of the services I'm (ab)using.
>>
>> Regards,
>>
>> P.S. The IETF airports chosen were:
>>
>>  IETF_airports: [
>>    "ORL",
>>    "ATL",
>>    "YVR",
>>    "CDG",
>>    "TPE",
>>    "YQB",
>>    "PRG",
>>    "PEK",
>>    "AMS",
>>    "LAX",
>>    "HIJ",
>>    "ARN",
>>    "SFO"
>>  ],
>>
>> --
>> Mark Nottingham   http://www.mnot.net/
>>
>>
>>
> 

From carlosm3011@gmail.com  Fri May 31 11:15:35 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE1C21F85E8 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.477
X-Spam-Level: 
X-Spam-Status: No, score=-1.477 tagged_above=-999 required=5 tests=[AWL=1.123,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRejZ4cgLNKg for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:15:34 -0700 (PDT)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB5B21F9301 for <ietf@ietf.org>; Fri, 31 May 2013 11:15:28 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id da11so1377880veb.20 for <ietf@ietf.org>; Fri, 31 May 2013 11:15:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=8ygushoez6W+7kqeiAG/bcOLC6v2Zn+oUeII4JxkjbI=; b=TsqNW7cUF7Qy0ZK6lX+byl9hA30dmPVr3cPEAF/OSGzyZxXmyhL8S1hrKBfyeuOSmW 0DlI3KP17sJzeal3GmsOve8SP/92W3rwnOU+R7zqRsQ+OrXukwa+V+BWn5qFUKN1a6I/ 2lhjdJOgglHe3PClq414ghvU77XUuhVcI6OLcVgtMux+ee7hKuhKEhKT/ts1S0kYZWZx gCP32KqgLDsjoIZ2F4m3gO567/K6tdCDhJYxv9yXSxTsuwQeK6Fpw1tmhPd0vayOud3g 3GXwJ/bD92FMA3dDCB/ot2k4tUHLRsOR53sLjLw408O8kzPIQTrBjLrvwI6lySLpokVc /yTg==
X-Received: by 10.220.248.137 with SMTP id mg9mr11278329vcb.38.1370024127805;  Fri, 31 May 2013 11:15:27 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:14e7:ee34:f855:da9b]) by mx.google.com with ESMTPSA id tn7sm36679219vdc.8.2013.05.31.11.15.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 11:15:26 -0700 (PDT)
Message-ID: <51A8E8BB.7050300@gmail.com>
Date: Fri, 31 May 2013 15:15:23 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
References: <20130527041505.7301.qmail@joyce.lan> <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com> <51A8E3EE.5060807@gmail.com> <CAMzo+1Z2UZm1tA3qu00EFbrfTOUSowwwX3qDkv9O3fnh==+xnQ@mail.gmail.com>
In-Reply-To: <CAMzo+1Z2UZm1tA3qu00EFbrfTOUSowwwX3qDkv9O3fnh==+xnQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: carlos@lacnic.net, "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:15:35 -0000

Whether OT or not you actively contribute to the mood of the discussion.
And to have a fruitful discussion on the topic I believe we MUST
accurately represent the facts, again, regardless of being OT or not.

~Carlos

On 5/31/13 3:07 PM, Jorge Amodio wrote:
> 
> Carlos, I clearly stated that the comment was OT, ie didn't have to much
> relation with the discussion. I'm not overreacting or misrepresenting
> anything, it was just an OT comment about a blog article which IMHO I
> consider really stupid and completely out of lalaland.
> 
> I didn't say a protest WILL happen, I said "don't get surprised" if some
> of these characters show up waiving the flags against the oppressing
> imperialism.
> 
> Anyway this dialog will not contribute anything,  the only point I keep
> making is while I consider a meeting in Buenos Aires a good idea, a
> better planned and thought approach may drive more long term
> participation, like finding the way to ensure that people that are
> already active participants in the IETF process and those who have the
> skills and motivation can go to the meetings wherever they take place
> without worrying too much about how to obtain the resources to do so.
> 
> -J
> 

From jmamodio@gmail.com  Fri May 31 11:24:44 2013
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 DF1B121F9133 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:24:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0AHOwAms-TJ for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:24:43 -0700 (PDT)
Received: from mail-vb0-x235.google.com (mail-vb0-x235.google.com [IPv6:2607:f8b0:400c:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 01E3E21F9050 for <ietf@ietf.org>; Fri, 31 May 2013 11:24:42 -0700 (PDT)
Received: by mail-vb0-f53.google.com with SMTP id p13so1249976vbe.26 for <ietf@ietf.org>; Fri, 31 May 2013 11:24:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=07fPGa6Vu6gKO1Fvaq32dwpIOZDTgEaL++YrovqoAPo=; b=jEUpYMWt/9yEO0aVNtUEYJJKgTP95wjpDak9DH8iUboA4abwxQSp5A6XwTBpwojr3b vFQdyAA/sXktvGj2whrTfnGyXU3jdmNOpoALg/KTu32qxABNEzXjF1KIZJX3euarJ4Ea hVUB/WrLz5q9V+Yqny41dNzngchjbZUfck2i4zBnAgkjp4dAK5Yfeq/AMbV+uPtPUMPH aYfvpdhGCjv6mpE1izp7AoULb6ubG0di7etdv+m+vJz+UBzyUthXgNTqersWYuILMW6f D7IFCTtin6HQ6xDvTgO6Fh/6Ck9R15AL1t1DiSlhYg/365LYC53ui28b00OhGaISvpPh ufSQ==
X-Received: by 10.58.180.196 with SMTP id dq4mr11507556vec.10.1370024682459; Fri, 31 May 2013 11:24:42 -0700 (PDT)
Received: from [10.0.10.101] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id l5sm23624668vev.1.2013.05.31.11.24.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 11:24:42 -0700 (PDT)
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <51A8E847.9020804@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51A8E847.9020804@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <EF3FB01A-FBEC-4B24-AD7E-9F62B710D709@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: [IETF] RE: Time in the Air
Date: Fri, 31 May 2013 13:24:41 -0500
To: "carlos@lacnic.net" <carlos@lacnic.net>
Cc: "mnot@mnot.net" <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:24:44 -0000

> Completely off-topic too, but since I live in the southernmost capital
> city of the world, and certainly not the best served by airlines

When you moved to NZ ?  ;-)

-J

From jmamodio@gmail.com  Fri May 31 11:25:57 2013
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 2009E21F9017 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:25:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U+HSx-vzlrvF for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:25:56 -0700 (PDT)
Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC0E21F8FCB for <ietf@ietf.org>; Fri, 31 May 2013 11:25:56 -0700 (PDT)
Received: by mail-ve0-f179.google.com with SMTP id d10so1384592vea.38 for <ietf@ietf.org>; Fri, 31 May 2013 11:25:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=zUMYKyOYm7S3CEEBMhMZZpsBlJJS3w8F7w8WKMPgPPU=; b=VmK1DwLCCTdgl6aJeEMULZ9+/GWiv20Siskreb4Do7WDtefcfSZQAoEystvxh5jHC/ kN2ndVgTGk5liNcO6sHLnmhspbqE2ID8l9oRFq4gm3rczkq28IIzH/1NVjO29blATibL Fte0wJvoelDw3o4nWGp3n0NjjgH3Ozna+VEr0CK1RpVYEkkcrOZgYcOpukD+fcOR6Xj7 WW7H23FYRr3r8UvUtnAx2ueG3rvTv0qMazvbBjE0NnD7HL/5NIvaDZDxIWzWYCOa1Lbv +/GgYAXSXy6OyYnbwE4Izf6FeSx6QCvGdCzfnKNQ1r+ZVCpdegDVz7L4vWT1fgW0fA29 nLaQ==
X-Received: by 10.220.84.8 with SMTP id h8mr1681646vcl.0.1370024752401; Fri, 31 May 2013 11:25:52 -0700 (PDT)
Received: from [10.0.10.101] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id s6sm31652565vdj.5.2013.05.31.11.25.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 11:25:52 -0700 (PDT)
References: <20130527041505.7301.qmail@joyce.lan> <9CFD7763-6C60-4E6A-80E4-55A531D7FF92@gmail.com> <51A8E3EE.5060807@gmail.com> <CAMzo+1Z2UZm1tA3qu00EFbrfTOUSowwwX3qDkv9O3fnh==+xnQ@mail.gmail.com> <51A8E8BB.7050300@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <51A8E8BB.7050300@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <70BA90E9-12E8-4754-91F3-8F1802B5BAA9@gmail.com>
X-Mailer: iPad Mail (10B329)
From: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: financial fun with an IETF Meeting in South America
Date: Fri, 31 May 2013 13:25:51 -0500
To: "carlos@lacnic.net" <carlos@lacnic.net>
Cc: "carlos@lacnic.net" <carlos@lacnic.net>, "ietf@ietf.org" <ietf@ietf.org>, "dcrocker@bbiw.net" <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: Fri, 31 May 2013 18:25:57 -0000

The existence of that article IS a fact

-Jorge

On May 31, 2013, at 1:15 PM, "Carlos M. Martinez" <carlosm3011@gmail.com> wr=
ote:

> Whether OT or not you actively contribute to the mood of the discussion.
> And to have a fruitful discussion on the topic I believe we MUST
> accurately represent the facts, again, regardless of being OT or not.
>=20
> ~Carlos


From iab-chair@iab.org  Fri May 31 11:33:19 2013
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C34A21F85B8; Fri, 31 May 2013 11:33:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGIKlKdaGMIt; Fri, 31 May 2013 11:33:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 8928921F852A; Fri, 31 May 2013 11:33:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7FF95124269; Fri, 31 May 2013 11:33:18 -0700 (PDT)
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 VuUvD-6xGsGk; Fri, 31 May 2013 11:33:18 -0700 (PDT)
Received: from [192.168.2.109] (pool-96-241-156-29.washdc.fios.verizon.net [96.241.156.29]) by c8a.amsl.com (Postfix) with ESMTPSA id D851C124264; Fri, 31 May 2013 11:33:17 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Appointment of Bob Hinden to Another Term on the ISOC Board of Trustees
From: IAB Chair <iab-chair@iab.org>
Date: Fri, 31 May 2013 14:33:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BE441FD-33AC-4245-ABD6-C90C0A2D14DF@iab.org>
To: ietf-announce@ietf.org
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:33:19 -0000

The Internet Society (ISOC) provides organizational and financial =
support for the IETF.  As part of the arrangements between ISOC and the =
IETF, the IETF is called upon to name three Trustees to its Board, with =
staggered 3 year terms. This requires that the IETF select one Trustee =
each year.  The IAB does this selection following the process in RFC =
3677.
=20
I am pleased to announce that the IAB has selected Bob Hinden for =
another term on the ISOC BoT.  His term will end in mid-2016.

On behalf of the IAB,
Russ Housley
IAB Chair=

From warren@kumari.net  Fri May 31 11:44:11 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A3721F8899 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.849
X-Spam-Level: 
X-Spam-Status: No, score=-99.849 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_50=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CAhRwKykkgEB for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:44:06 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109A921F8B64 for <ietf@ietf.org>; Fri, 31 May 2013 11:44:04 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 0D26E1B40A6B; Fri, 31 May 2013 14:44:03 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Re: Issues in wider geographic participation
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
Date: Fri, 31 May 2013 14:44:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <11B378FD-CADE-49CA-BAC5-814B6E2E07C7@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1503)
Cc: ietf@ietf.org, "Eliot Lear \(elear\)" <elear@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: Fri, 31 May 2013 18:44:11 -0000

On May 30, 2013, at 8:37 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Thursday, May 30, 2013 15:31 -0400 Warren Kumari
> <warren@kumari.net> wrote:
>=20
>> The below is not a direct response to John, it is more my
>> general views on IETF interaction with operators.
>>=20
>> So, I've been a long time participant in some NOG's and still
>> (perhaps incorrectly) view myself as an operator. I've spent
>> significant time thinking about / discussing the issue of
>> insufficient operator involvement in the IETF, trying to
>> understand some of the causes. I've tried to summarize some of
>> the operators' views below, and also some thoughts on how we
>> might be able to work better / get more operator input.=20
>>=20
>> I think that at the root of much of the problem is cultural
>> differences -- if we want more operator involvement / feedback
>> there needs to be some attention paid (by both the operators
>> and the IETF folk) to understanding these differences, and
>> taking care to respect / accommodate the other side's culture.=20
>> ...
>=20
> Warren,
>=20
> I think these notes are very helpful, at least insofar as I have
> enough knowledge to evaluate.   Some of your comments,
> including...
>=20
>> This is somewhat of a vicious cycle -- operators participate
>> less, and so the IETF understands less about how their
>> networks run. This leads to solutions that don't understand
>> the real world, and so operators lose faith/interest in IETF,
>> and participate even less.
>=20
> ultimately call the IETF's legitimacy and long-term future into
> question.  As you suggest, we may have good vendor participation
> but the operators are ultimately the folks who pay the vendor's
> bills.
>=20
>> ...
>=20
> As I told someone in another thread, I threw the NOG idea out as
> an example without thinking through all of the possible
> dynamics.  It may be a terrible idea... or even a good idea that
> won't work usefully. =20
>=20
> Part of that discussion included an observation that is probably
> a corollary to one of yours.  Many operators, either
> individually or in groups, don't perceive that they have much
> incentive to review IETF documents, much less get dragged into
> the document development and consensus-forming process.

Yup. And some operators have decided that the IETF document development =
and consensus-forming process is sufficiently annoying that they are =
standing up their own forum for Best Common Practice docs:=20

http://www.ipbcop.org/ -- "Documented best practices for Engineers by =
Engineers"

Some more info:
=
http://www.internetsociety.org/deploy360/wp-content/uploads/2012/09/Hughes=
-BCOP.pdf

There are BCOPs groups forming / within RIPE, NANOG, etc. This is still =
early days, but there have been discussions on how these should actually =
be published, etc. Various ideas have been floated, including bringing =
them to the IETF once baked, but the IETF stamp, a separate rfc-editor =
stream, simply publishing them under their own banner, etc.

There is a NANOG meeting in New Orleans next week, where more =
discussions about this will be happening. If I make it to the session =
I'll try provide some feedback=85

Out of interest, who all from here will be attending NANOG? Who all =
attended RIPE in Dublin a few weeks ago?=20

One (IMO) good idea that was mentioned recently (sorry, I cannot =
remember by whom, may have been Jim Martin) was for someone from the =
IETF to present a short summary of interesting work at NOG meetings.=20

Someone "from the IETF" could collect short summaries from various WG's =
and present them at the various NOGs -- these should (IMO) be teaser =
style summaries, with the most interesting / dynamic bits highlighted. =
Ideally each WGs would provide a short, concise summary, and then the WG =
chairs (and folk who wear the smily faced dots on badges) could be =
designated as contact points, to help take input from operators, provide =
more detail, info on how you join the WG and participate, etc..

W

> Certainly, we are unlikely to get very many people who are not
> active IETF participants to do work for the good of the IETF.
>> =46rom that perspective, the very best incentive for reviewing a
> document pre-standardization is the perceived risk that it will
> make one's life worse if it goes through without input from your
> perspective.  If we throw documents over the wall without clear
> motivation as to why people on the other side of the wall should
> care,... well, that is as much a setup for failure as the model
> in some other Internet bodies of soliciting input and then not
> paying any attention to it.   (In the latter case, there may be
> organizational advantages to being able to say "we received NN
> comments", but that does not apply to the IETF.)
>=20
> More generally, and borrowing (but altered somewhat) from
> another thread:  The real point I'm trying to make is that, if
> our goal is really to do outreach to other communities to get
> better input or reviews with broader perspective, then we better
> start thinking more creatively than trying to persuade people
> (and their organizations and budgets) to sign up for the IETF,
> three extra week-long meetings a year, reading mailing lists
> that contain dozens of messages a day on topics that may be of
> no interest at all, etc.   Instead, in your terminology, Warren,
> we should be looking for ways in which they can do what
> simultaneously benefits them, us, and the Internet as much as
> possible within their own cultural framework.   At least we need
> to distinguish between the goals of "better input and review
> from affected communities" and "increasing IETF active
> participation".  =20
>=20
> And, coming back to the supposed topic of this thread, dragging
> circa 1000 people to a place that doesn't have a lot of
> participation already is unlikely to accomplish either goal.
> There may be, and probably are, perfectly good reasons why more
> geographic diversity would be a good idea, but justifying doing
> so on the basis that it is a good investment in growing
> long-term active IETF participation just doesn't, IMO, fly.
>=20
>    john
>=20
>=20
>=20
>=20
>=20
>=20
>=20

--
The duke had a mind that ticked like a clock and, like a clock, it =
regularly went cuckoo.

    -- (Terry Pratchett, Wyrd Sisters)



From dhc@dcrocker.net  Fri May 31 11:55:07 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C34D21F92FC for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xZ+bVINe4Tom for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 11:55:02 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0FAC921F92E3 for <ietf@ietf.org>; Fri, 31 May 2013 11:55:02 -0700 (PDT)
Received: from [192.168.1.7] (chello080108132236.14.wu-wien.teleweb.at [80.108.132.236] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r4VIssxA018509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 31 May 2013 11:54:59 -0700
Message-ID: <51A8F1F4.4040800@dcrocker.net>
Date: Fri, 31 May 2013 20:54:44 +0200
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Time in the Air
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 31 May 2013 11:55:00 -0700 (PDT)
Cc: "mnot@mnot.net" <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 18:55:07 -0000

On 5/31/2013 8:12 PM, Scott Brim wrote:
> We'll have multiple airships, one for each set of related meeting rooms.


is dirigible a new term of endearment for an AD?

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Fri May 31 12:18:48 2013
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9865B21F898B for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hUex82atikY9 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:18:48 -0700 (PDT)
Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id EB78921F894E for <ietf@ietf.org>; Fri, 31 May 2013 12:18:47 -0700 (PDT)
Received: by mail-ea0-f176.google.com with SMTP id k11so1973365eaj.35 for <ietf@ietf.org>; Fri, 31 May 2013 12:18:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PyniN7eeXjhiSyG8eG2GX7yW9ffsAxfzd0TCMqOCH14=; b=JhFElg7e9MWUUAqb3RkAvahaLp5SMWHN8gsQt0eGkE26SB1cpcYQE7g7aqJwFC6+fz S8fF3KXaFhVyq2D4C7rfTRC3Qp5zK6wX/UkPp0VNTj4LEJ7JQxErun6fA029jpuftt4I pTJU4E/lm/+eAac/r6wKz4T+IhdqZj0a/hBmF3BesVm1GSz1hEz6qdFoW1Aghb+u27TE XexqbuI/0n7uf3hYzXtRbUPMWfOW0Aqd1giKcC4bHqBxvciT6Nxi4J4qkYyuqRJ/oc8C eR+8oEYE4PmDB1xiAXckY2bBCJlkRDyhu4JBLdw/eQbnsLNwJivSWvywmrOm/bPm6gt8 osRQ==
MIME-Version: 1.0
X-Received: by 10.15.108.141 with SMTP id cd13mr14606023eeb.46.1370027927000;  Fri, 31 May 2013 12:18:47 -0700 (PDT)
Received: by 10.14.117.12 with HTTP; Fri, 31 May 2013 12:18:46 -0700 (PDT)
In-Reply-To: <51A8F1F4.4040800@dcrocker.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com> <51A8F1F4.4040800@dcrocker.net>
Date: Fri, 31 May 2013 15:18:46 -0400
Message-ID: <CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@mail.gmail.com>
Subject: Re: Time in the Air
From: Scott Brim <scott.brim@gmail.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0160c9f4ec19b304de087b0f
Cc: "mnot@mnot.net" <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 19:18:48 -0000

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

On Friday, May 31, 2013, Dave Crocker wrote:

> On 5/31/2013 8:12 PM, Scott Brim wrote:
>
>> We'll have multiple airships, one for each set of related meeting rooms.
>>
>
>
> is dirigible a new term of endearment for an AD?
>

Obviously the ADs have a small helicopter so they can get between
dirigibles.

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

<span style=3D"font-size:15.454545021057129px">On Friday, May 31, 2013, Dav=
e Crocker </span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 5/31/2013 8:1=
2 PM, Scott Brim wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We&#39;ll have multiple airships, one for each set of related meeting rooms=
.<br>
</blockquote>
<br>
<br>
is dirigible a new term of endearment for an AD?<br></blockquote><div><br><=
/div><div>Obviously the ADs have a small helicopter so they can get between=
 dirigibles.=A0</div>

--089e0160c9f4ec19b304de087b0f--

From abdussalambaryun@gmail.com  Fri May 31 12:24:04 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE2C221F8E89 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:24:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Df6Ct2c2txK for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:23:59 -0700 (PDT)
Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA5621F8ECB for <ietf@ietf.org>; Fri, 31 May 2013 12:23:59 -0700 (PDT)
Received: by mail-pd0-f171.google.com with SMTP id z11so2701486pdj.30 for <ietf@ietf.org>; Fri, 31 May 2013 12:23:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5Z0oVPbSXZOT5gfEWPrG/NZLsbxL4plKYMaxLVtrujQ=; b=MFneEEpsAd1nKc9AsEoc/zvrqxGYbbcHXzZAuf5nxXZUrUdgSbexb5guuJkgx9T/UO riAMFkm6SxDCCxYL2952CnWpyzwit3ywfdlKtg9BMpRKZbxRQKHr+4uc0MX5cFK/+Wf7 kMvnzedikrr9V+sbhg4j7rBOl+i4u4wYllzSjfGy0lqimP8lGl1o12CBRCibLPdMqcV9 dCqK4dfhevgzDmWDYTXLzDD5Ub+auFcDq4VIuulqW9rmJutfungk6QYYJ2Q+z8IGvK2N rwgr2dGEIjxj4zDzXG4LFXujXIpeYB1sZal6h/po88yLDRyg8Hkr6/L83ixsilVTwvKh wH7Q==
MIME-Version: 1.0
X-Received: by 10.68.176.197 with SMTP id ck5mr14059277pbc.165.1370028238950;  Fri, 31 May 2013 12:23:58 -0700 (PDT)
Received: by 10.68.78.164 with HTTP; Fri, 31 May 2013 12:23:58 -0700 (PDT)
In-Reply-To: <51A8B961.9060801@gmail.com>
References: <51A8B961.9060801@gmail.com>
Date: Fri, 31 May 2013 21:23:58 +0200
Message-ID: <CADnDZ8_RiW+d8vNBsPKzsoA_R00mRJpLg1CtRN4v3QG99DdLNw@mail.gmail.com>
Subject: Re: "Hands across the water/hands across the sky"
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 19:24:04 -0000

Hi Spencer.

I like your point. I think it is correct that collaboration is needed
between all regions for many I-Ds or related I-Ds to the region
participants interest. Cross-participation co-authoring between
regions may make better results than co-authors from same region.
Comments below,

On 5/31/13, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
> For those of you looking at where I-D and RFC authors are from, I'd like
> to suggest one other thing to look at - the extent that participants are
> co-authoring with folks outside their region.

There are some I-Ds like that which was a result of meetings of an
author team of different regions and same interest. I will add another
interesting point, IMO, each region has different interests, so if you
ask in diff-region meetings of the community interest you mostly get
different responds but not if the attendance are the same persons.
>
> It's pretty tempting for new participants to submit drafts that they
> like, and maybe reaching out to their office mates as co-authors, but to
> be effective in the IETF, participants have to learn how to collaborate
> with folks from other IETF sponsors (including "other IETF sponsors who
> compete head-to-head with your IETF sponsor"), other countries, and
> other regions. "Collaboration" covers many activities, but I'm curious
> what we might learn from looking at this specific kind of collaboration.

I agree totaly,

>
> <personal self-reveal> I say this to a lot of people who don't believe
> me, but I have been shy for most of my life, and it's still not easy for
> me to have conversations with total strangers. That's not a cultural
> challenge, and it's not a language challenge, but it is a challenge I've
> faced in the IETF as *I* was learning to collaborate. For anyone who is
> also learning how to do this - for me, it's been worth it.

I encourage you to continue your efforts for your progress (all have
their special issues), which I think it is what IETF is about to make
all learn for better Internet. I am experiencing a different situation
while I am trying to have discussions with people I don't know in
IETF, I get bad responses, and getting to know good people before I
meet them. I am collaborating (in reviewing ideas not authoring, and a
plan with one in future of authoring I-D) already with some that I
never met but only remotely discussed in IETF.

> And anyone is
> welcome to join us for drumming at IETF meetings - I bring extra drums,
> and there's no telling who else you'll meet. </personal self-reveal>
>

I will join, we actually can plan to co-author an I-D while drumming
so we don't waste time, thanks :-)

AB

From joelja@bogus.com  Fri May 31 12:25:39 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7955521F86E9 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SNeHdiT1FTae for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:25:39 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0F60021F8E89 for <ietf@ietf.org>; Fri, 31 May 2013 12:25:39 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r4VJPWUc055842 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 31 May 2013 19:25:32 GMT (envelope-from joelja@bogus.com)
Message-ID: <51A8F926.70803@bogus.com>
Date: Fri, 31 May 2013 12:25:26 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:21.0) Gecko/20100101 Thunderbird/21.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: Time in the Air
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>	<290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>	<BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net>	<CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com>	<51A8F1F4.4040800@dcrocker.net> <CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@mail.gmail.com>
In-Reply-To: <CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@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.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 31 May 2013 19:25:32 +0000 (UTC)
Cc: "mnot@mnot.net" <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 19:25:39 -0000

On 5/31/13 12:18 PM, Scott Brim wrote:
> On Friday, May 31, 2013, Dave Crocker wrote:
>
>     On 5/31/2013 8:12 PM, Scott Brim wrote:
>
>         We'll have multiple airships, one for each set of related
>         meeting rooms.
>
>
>
>     is dirigible a new term of endearment for an AD?
>
>
> Obviously the ADs have a small helicopter so they can get between 
> dirigibles.
It's more like Icarus...

From cabo@tzi.org  Fri May 31 12:55:24 2013
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 1C45B21F911B for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:55:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.95
X-Spam-Level: 
X-Spam-Status: No, score=-104.95 tagged_above=-999 required=5 tests=[AWL=1.299, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M4e9h6c8J7kB for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:55:18 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id F3CCA21F90AC for <ietf@ietf.org>; Fri, 31 May 2013 12:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.4/8.14.4) with ESMTP id r4VJtF1t001041; Fri, 31 May 2013 21:55:15 +0200 (CEST)
Received: from [192.168.217.105] (p5489322F.dip0.t-ipconnect.de [84.137.50.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id F0B203EDA; Fri, 31 May 2013 21:55:14 +0200 (CEST)
Subject: Re: "Hands across the water/hands across the sky"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <51A8B961.9060801@gmail.com>
Date: Fri, 31 May 2013 21:55:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECBC02C1-95E2-45F9-8225-E3D3AF9D2737@tzi.org>
References: <51A8B961.9060801@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1503)
Cc: ietf Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 19:55:24 -0000

On May 31, 2013, at 16:53, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:

> co-authoring with folks outside their region.

Very good point.

Significant advantage comes from any kind of co-authoring with someone =
who is able to bring another perspective.  By region, by =
academic/commercial interest, by vendor/operator role, by amount of time =
you have been around in the IETF, by IETF area focus, etc.  (Fostering =
diversity is a lot about adding perspectives, and getting that right =
into the author team will allow it to make early impact.)

Now, if you come from a region sparsely populated with IETFers, that may =
make co-authoring with people outside your region a particularly good =
idea.

Gr=FC=DFe, Carsten


From randy@psg.com  Fri May 31 12:56:43 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4CA21F91CA for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:56:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cqijEdal-pUm for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:56:43 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 25A6F21F90AC for <ietf@ietf.org>; Fri, 31 May 2013 12:56:43 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UiVRJ-000Mdr-Rt; Fri, 31 May 2013 19:56:41 +0000
Date: Fri, 31 May 2013 12:56:41 -0700
Message-ID: <m2ehcmvs7a.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: Issues in wider geographic participation
In-Reply-To: <11B378FD-CADE-49CA-BAC5-814B6E2E07C7@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <11B378FD-CADE-49CA-BAC5-814B6E2E07C7@kumari.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, 31 May 2013 19:56:43 -0000

> Yup. And some operators have decided that the IETF document
> development and consensus-forming process is sufficiently annoying
> that they are standing up their own forum for Best Common Practice
> docs:
> http://www.ipbcop.org/ -- "Documented best practices for Engineers by Engineers"
> Some more info:
> http://www.internetsociety.org/deploy360/wp-content/uploads/2012/09/Hughes-BCOP.pdf

actually, that is not operators acting for operators at all.  it is yet
another non-ops group trying to colonize ops.  documentd best practices
for engineers by policy folk.  mission creep on their part, imiho.  it
would be amusing if they did not already have a mission that is critical
for all of us.

> There are BCOPs groups forming / within RIPE, NANOG, etc. 

ripe has published ops practice and even protocol docs for a many years.
as one example, route flap damping came from the ripe doc series.  nanog
may get serious, time will tell.

> Out of interest, who all from here will be attending NANOG? 

i will be.  and saw you at ripe.  will you be in lusaka in a week?

> One (IMO) good idea that was mentioned recently (sorry, I cannot
> remember by whom, may have been Jim Martin) was for someone from the
> IETF to present a short summary of interesting work at NOG meetings.

this has been done many times.  imiho, it has not stirred up much useful
interaction unless the ietfer says something really st00pid.  then it
gets amusing.

randy

From carlosm3011@gmail.com  Fri May 31 12:56:55 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD5921F9349 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:56:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level: 
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[AWL=0.749,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAeGFwfzXc+5 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 12:56:55 -0700 (PDT)
Received: from mail-vb0-x22a.google.com (mail-vb0-x22a.google.com [IPv6:2607:f8b0:400c:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id DA2C021F9344 for <ietf@ietf.org>; Fri, 31 May 2013 12:56:54 -0700 (PDT)
Received: by mail-vb0-f42.google.com with SMTP id w15so1345217vbf.15 for <ietf@ietf.org>; Fri, 31 May 2013 12:56:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:reply-to:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xE6jhh3btY9kkHbVEU722R1ipd8R8vu7pD08DuDtvKw=; b=ksbkjG/swyUqHydnD3L0AOcb3zjSHaJX/7UM/Umqdy3zrAMW6LQLMJsDQCQocaJjeB TXKyMaFZw0MvrhrqIP/6CdFtKweZDN+4dBlZG3qojLQ01CfY2Yd0V1yZVNJedwJn8RlI x3OTh4hiTkPsUIJfgVsmCa7Ctayhfl7zq9egPzFCz/erS2QF83XrjPL+vrXJUBCiijiU EB+cE2yuhlbmqQOIrBHTNWK3GqvvSOoFF4XLtlEa/yrc+E3cQcBQy/xUqeki01cC9+tQ KSSXqOoSdL/4w5YfVWg4SGbYdSyRHapc8KnHsQH3F29rML1fHENkfwUWlqmTZxffiBD1 TLvw==
X-Received: by 10.52.103.2 with SMTP id fs2mr9848525vdb.15.1370030214342; Fri, 31 May 2013 12:56:54 -0700 (PDT)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:5f1:e320:3923:7889]) by mx.google.com with ESMTPSA id kz18sm37306487vdb.13.2013.05.31.12.56.51 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 12:56:53 -0700 (PDT)
Message-ID: <51A90081.4070804@gmail.com>
Date: Fri, 31 May 2013 16:56:49 -0300
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: [IETF] RE: Time in the Air
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <51A8E847.9020804@gmail.com> <EF3FB01A-FBEC-4B24-AD7E-9F62B710D709@gmail.com>
In-Reply-To: <EF3FB01A-FBEC-4B24-AD7E-9F62B710D709@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "mnot@mnot.net" <mnot@mnot.net>, "carlos@lacnic.net" <carlos@lacnic.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 19:56:55 -0000

You are right, Wellington is almost 7 degrees south of Montevideo,
although I hope it's better served by airlines :D

cheers!

~C.

On 5/31/13 3:24 PM, Jorge Amodio wrote:
> 
>> Completely off-topic too, but since I live in the southernmost capital
>> city of the world, and certainly not the best served by airlines
> 
> When you moved to NZ ?  ;-)
> 
> -J
> 

From elwynd@dial.pipex.com  Fri May 31 13:32:28 2013
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4C621F89EB for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 13:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ey64cEtSmX-8 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 13:32:22 -0700 (PDT)
Received: from mk-outboundfilter-6.mail.uk.tiscali.com (mk-outboundfilter-6.mail.uk.tiscali.com [212.74.114.14]) by ietfa.amsl.com (Postfix) with ESMTP id D09E121F9050 for <ietf@ietf.org>; Fri, 31 May 2013 13:32:21 -0700 (PDT)
X-Trace: 573278092/mk-outboundfilter-6.mail.uk.tiscali.com/PIPEX/$OFF_NET_AUTH_ACCEPTED/None/81.187.254.249/None/elwynd@dial.pipex.com
X-SBRS: None
X-RemoteIP: 81.187.254.249
X-IP-MAIL-FROM: elwynd@dial.pipex.com
X-SMTP-AUTH: elwynd@dial.pipex.com
X-Originating-Country: GB/UNITED KINGDOM
X-MUA: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
X-IP-BHB: Once
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8EAGgIqVFRu/75/2dsb2JhbABZgkWKDrJugm2BGYMXAQEFeAEQCwQBEwkWDwkDAgECAUUGDQEHAQGIDbl8jyEHg1cDlz6GC4s1gxA
X-IronPort-AV: E=Sophos;i="4.87,781,1363132800";  d="scan'208,217";a="573278092"
X-IP-Direction: OUT
Received: from weee-pc2.folly.org.uk (HELO [81.187.254.249]) ([81.187.254.249]) by smtp.pipex.tiscali.co.uk with ESMTP; 31 May 2013 21:32:14 +0100
Message-ID: <51A908CB.9070605@dial.pipex.com>
Date: Fri, 31 May 2013 21:32:11 +0100
From: Elwyn Davies <elwynd@dial.pipex.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Time in the Air
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com> <51A8F1F4.4040800@dcrocker.net> <CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@mail.gmail.com>
In-Reply-To: <CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030700070008070608010804"
Cc: "mnot@mnot.net" <mnot@mnot.net>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 20:32:28 -0000

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

On 31/05/13 20:18, Scott Brim wrote:
> On Friday, May 31, 2013, Dave Crocker wrote:
>
>     On 5/31/2013 8:12 PM, Scott Brim wrote:
>
>         We'll have multiple airships, one for each set of related
>         meeting rooms.
>
>
>
>     is dirigible a new term of endearment for an AD?
>
>
> Obviously the ADs have a small helicopter so they can get between 
> dirigibles.
Don't they use the ADs (Area Drones) controlled from the IESG bunker?


--------------030700070008070608010804
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 31/05/13 20:18, Scott Brim wrote:<br>
    </div>
    <blockquote
cite="mid:CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@mail.gmail.com"
      type="cite"><span style="font-size:15.454545021057129px">On
        Friday, May 31, 2013, Dave Crocker </span> wrote:<br>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex">On 5/31/2013
        8:12 PM, Scott Brim wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          We'll have multiple airships, one for each set of related
          meeting rooms.<br>
        </blockquote>
        <br>
        <br>
        is dirigible a new term of endearment for an AD?<br>
      </blockquote>
      <div><br>
      </div>
      <div>Obviously the ADs have a small helicopter so they can get
        between dirigibles.&nbsp;</div>
    </blockquote>
    Don't they use the ADs (Area Drones) controlled from the IESG
    bunker?<br>
    <br>
  </body>
</html>

--------------030700070008070608010804--

From john-ietf@jck.com  Fri May 31 16:51:13 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E25821F8E93 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 16:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.3
X-Spam-Level: 
X-Spam-Status: No, score=-101.3 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AcHR5YurpTw6 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 16:51:07 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 27E3821F8EC6 for <ietf@ietf.org>; Fri, 31 May 2013 16:50:58 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1UiZ5u-0006s4-9q; Fri, 31 May 2013 19:50:50 -0400
Date: Fri, 31 May 2013 19:50:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, 'Warren Kumari' <warren@kumari.net>
Subject: RE: [IETF] Re: Issues in wider geographic participation
Message-ID: <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>
In-Reply-To: <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2013 23:51:13 -0000

(I think what Warren, Randy, and others have to say is more
relevant to most of this than my opinion - unless you count a
handful of end networks with VPN connections among a subset of
them, I haven't had either ops responsibility or even direct or
indirect management responsibility for those who do for a very
long time.  I haven't been to a NOG meeting for even longer.
And I have absolutely no delusion that I'm current.  So the
following comments are observations about general principles
only.)

--On Friday, May 31, 2013 02:19 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> Hi,
> 
> This thread is helpful to me.
>...
>> ultimately call the IETF's legitimacy and long-term future
>> into question.  As you suggest, we may have good vendor
>> participation but the operators are ultimately the folks who
>> pay the vendor's bills.
> 
> I agree so far.
> 
> But who pays the operators' bills, and do we need to encourage
> participation at that level as well?

The customers of the ISPs.  The technical sophistication of
those folks and their (non-ISP, non-operator) support structure
differs hugely, but most of them neither speak network nor have
any desire to learn.  That is not necessarily bad.

Let me suggest an analogy.  The electrical distribution industry
has its own standards and standards development processes.  In
most countries, those standards body attract engineers and
designers, but very few of the actual operators who run the
power plants and worry about the mains.  You presumably pay
utility bills (directly or indirectly) and thereby support the
whole process.  But your ability or mine to plug something into
a mains socket and take advantage of the stuff that comes out
does not, in general, qualify us to participate in the process
of defining transmission standards.  And that standards body
should probably not lose much sleep over the fact that we aren't
showing up.  Indeed, if we did show up, we would probably be out
of place, wouldn't speak the technical language, and might not
understand the culture. At least in my case, if I made a
suggestion, it would probably be stupid enough that people would
either feel that my presence was wasting their time or would
feel obligated to try to explain basic principles to me in the
interest of outreach (or both).

There are certainly engineers with protocol design background
who have ended up with operations responsibilities and acquired
a good deal of additional perspective as a result.  Several of
them have made significant contributions to the IETF and, at
least IMO, that dual perspective has helped.  But I'm pretty
sure that the majority of ops people don't have that background.
For those who don't, who needs to know that the equipment 
and configurations they use will work but who may not have
strong preferences about the details of how, and, when things
don't work, are a lot more likely to blame vendors (or other
ISPs) than us, maybe "how do we get more of them to come to the
IETF and participate in the ways that those of us on this list
participate" is just not the right question.  

   best,
   john


From mnot@mnot.net  Fri May 31 17:02:13 2013
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 1858621F8F38 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W6TTyLPC19+p for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:02:07 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 861EC21F8B3D for <ietf@ietf.org>; Fri, 31 May 2013 17:02:07 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.184.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 8A99722E200 for <ietf@ietf.org>; Fri, 31 May 2013 20:02:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Time in the Air
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
Date: Sat, 1 Jun 2013 10:01:55 +1000
Content-Transfer-Encoding: 7bit
Message-Id: <93885882-81B5-47B8-A7F9-E0B82FBEF5D1@mnot.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
To: ietf Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2013 00:02:13 -0000

On 31/05/2013, at 7:59 PM, Mark Nottingham <mnot@mnot.net> wrote:

> SFO  204:10  282:04  // San Francisco
> BOS  197:42  297:38  // Boston
> ATL  205:44  297:28  // Atlanta
> ANC  197:12  345:54  // Anchorage
> LHR  198:02  249:44  // London
> FRA  202:10  255:22  // Frankfurt
> FCO  223:52  283:04  // Rome
> SVO  211:28  287:14  // Moscow
> TLV  264:12  334:22 // Israel
> DXB  293:26  344:34 // Dubai
> NRT  259:00  314:38  // Tokyo
> HKG  296:38  359:22  // Hong Kong
> BLR  332:28  448:24  // Bangalore
> MEL  450:28  556:04  // Melbourne
> AKL  442:24  569:04  // Auckland
> JNB  414:30  498:22  // Johannesburg
> EZE  411:10  522:56  // Buenos Aires
> GIG  381:56  488:32  // Rio de Janeiro

... and upon request:

PEK   249:56   308:40  // Beijing
LAX  209:30  284:42  // Los Angeles
JFK  199:04  272:14  // New York
ORD  194:08  277:26  // Chicago

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




From randy@psg.com  Fri May 31 17:23:27 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1010B21F89A5 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yXCXMwpc-FUX for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:23:26 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 7A29721F896D for <ietf@ietf.org>; Fri, 31 May 2013 17:23:26 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UiZbR-000NiC-38; Sat, 01 Jun 2013 00:23:25 +0000
Date: Fri, 31 May 2013 17:23:24 -0700
Message-ID: <m2vc5yu1ab.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Not Listening to the Ops Customer (was Re: Issues in wider geographic participation)
In-Reply-To: <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@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: Sat, 01 Jun 2013 00:23:27 -0000

< rant >

the sad fact is that the ietf culture is often not very good at
listening to the (ops) customer.  look at the cf we have made out of
ipv6.  the end user, and the op, want the absolute minimal change and
cost, let me get an ipv6 allocation from the integer rental monopoly,
flip a switch or two, and get 96 more bits no magic.  15 years later,
dhcp is still a cf, i have to run a second server (why the hell does
isc not merge them?), i can not use it for finding my gateway or vrrp
exit, ...  at least we got rid of the tla/nla classful insanity.  but
u/g?  puhleeze.

at ripe/dublin, olaf gave a really nice but somewhat glib talk about
technology adoption, using dnssec and ipv6 as the positive examples.  as
some curmudgeonly schmuck pointed out at the mic, dnssec is forward
compatible and there are no alternatives, so it is being adopted despite
its complexity and warts.  ipv6 is not forward compatible, we put
unnecessary obstacles in the deployment path, and there are
alternatives.  d o o m.

if we had wanted ipng deployed, we would have done everything we could
to make it simple and easy for net-ops and end users to turn it on.
instead, we made it complex and hard and then blame everyone else for
not instantly adopting it en masse.  the ietf did not listen to or
consider the customer.  this is fatal.  and the arrogance is taking what
is left of the e2e internet down the drain with it.

randy

From bmanning@isi.edu  Fri May 31 17:27:44 2013
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0C921F8956 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QaiQND4OEHpH for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:27:38 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 85E2321F8ADF for <ietf@ietf.org>; Fri, 31 May 2013 17:27:38 -0700 (PDT)
Received: from [192.168.0.4] (cpe-24-24-228-167.socal.res.rr.com [24.24.228.167]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r510RLVd015059 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 31 May 2013 17:27:31 -0700 (PDT)
Subject: Re: Not Listening to the Ops Customer (was Re: Issues in wider geographic participation)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: manning bill <bmanning@isi.edu>
In-Reply-To: <m2vc5yu1ab.wl%randy@psg.com>
Date: Fri, 31 May 2013 17:27:07 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <41110EB1-5FEE-492C-BB5A-1BB446774490@isi.edu>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1283)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: John C Klensin <john-ietf@jck.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 00:27:44 -0000

amen!  :)

On 31May2013Friday, at 17:23, Randy Bush wrote:

> < rant >
> 
> the sad fact is that the ietf culture is often not very good at
> listening to the (ops) customer.  look at the cf we have made out of
> ipv6.  the end user, and the op, want the absolute minimal change and
> cost, let me get an ipv6 allocation from the integer rental monopoly,
> flip a switch or two, and get 96 more bits no magic.  15 years later,
> dhcp is still a cf, i have to run a second server (why the hell does
> isc not merge them?), i can not use it for finding my gateway or vrrp
> exit, ...  at least we got rid of the tla/nla classful insanity.  but
> u/g?  puhleeze.
> 
> at ripe/dublin, olaf gave a really nice but somewhat glib talk about
> technology adoption, using dnssec and ipv6 as the positive examples.  as
> some curmudgeonly schmuck pointed out at the mic, dnssec is forward
> compatible and there are no alternatives, so it is being adopted despite
> its complexity and warts.  ipv6 is not forward compatible, we put
> unnecessary obstacles in the deployment path, and there are
> alternatives.  d o o m.
> 
> if we had wanted ipng deployed, we would have done everything we could
> to make it simple and easy for net-ops and end users to turn it on.
> instead, we made it complex and hard and then blame everyone else for
> not instantly adopting it en masse.  the ietf did not listen to or
> consider the customer.  this is fatal.  and the arrogance is taking what
> is left of the e2e internet down the drain with it.

</rant>
> 
> randy


From mnot@mnot.net  Fri May 31 17:33:43 2013
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 D01C321F8E8F for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:33:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FS7SAHmqaT0a for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:33:38 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id D56D321F89A6 for <ietf@ietf.org>; Fri, 31 May 2013 17:33:35 -0700 (PDT)
Received: from [192.168.1.80] (unknown [118.209.184.230]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 874C722E253 for <ietf@ietf.org>; Fri, 31 May 2013 20:33:28 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Time in the Air
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
Date: Sat, 1 Jun 2013 10:33:23 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <86DAEB76-5314-4C3F-9B5F-8AA1F239F688@mnot.net>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net>
To: ietf Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1503)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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 Jun 2013 00:33:43 -0000

... and now, looking forward to our announced upcoming meeting locations =
(just the shortest route numbers, not great circle):

LHR  145:30  // London
JFK  150:20  // New York
SFO  155:54  // San Francisco
FRA  156:08  // Frankfurt
ATL  158:10  // Atlanta
BOS  159:34  // Boston
ANC  181:56  // Anchorage
FCO  183:18  // Rome
NRT  186:40  // Tokyo
SVO  188:00  // Moscow
PEK  205:34  // Beijing
TLV  223:20  // Israel
DXB  225:30 // Dubai
HKG  236:20  // Hong Kong
BLR  286:30 // Bangalore
GIG  286:32  // Rio de Janeiro
EZE  306:00  // Buenos Aires
JNB  322:38  // Johannesburg
AKL 323:58  // Auckland
MEL  326:06  // Melbourne


  IETF_airports: [
    "TXL",
    "YVR",
    "LHR",
    "YYZ",
    "HNL",
    "DFW",
    "PRG",
    "NRT"
  ]

Cheers,


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




From fred@cisco.com  Fri May 31 17:44:26 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A96321F8DE4 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kq2cas-Durn for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:44:17 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5D921F85C3 for <ietf@ietf.org>; Fri, 31 May 2013 17:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=359; q=dns/txt; s=iport; t=1370047457; x=1371257057; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=PHoQrz3WTieyJP9/xTiCoos/DqSJddTfVFqtwQFp+BQ=; b=RIX7MgXgNJ7++4xC2/jGaiEwrM2VaZU9fi21VAj9LeS25YpwRbK0bIbp +0WVC0OEbk2H75bhb13aAe5kwE0sGX71r9xCns9rDSAWLnLcbDqQUuKXK R4XcQH3lKImaf0w8I95ifxILF4nuHRl7xvF9LCnxB4QK4d7O0O1H0ACld Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQGAIVDqVGtJV2Y/2dsb2JhbABZDoJ7gyW8DIECFm0HgiMBAQEDATo/BQsCAQgiFBAyJQIEDgUIh38GugSObgIxB4J2YQOofoJRPoIn
X-IronPort-AV: E=Sophos;i="4.87,782,1363132800"; d="scan'208";a="217449745"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-8.cisco.com with ESMTP; 01 Jun 2013 00:44:17 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r510iHOD022232 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 1 Jun 2013 00:44:17 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.02.0318.004; Fri, 31 May 2013 19:44:16 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXeWY91qtTTAv6ki4r3l9ayfrepkfpzmAgACzFYA=
Date: Sat, 1 Jun 2013 00:44:16 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B900110@xmb-rcd-x09.cisco.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3BC37547511107468537986DB44E1954@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<mnot@mnot.net>" <mnot@mnot.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 00:44:27 -0000

On May 31, 2013, at 7:03 AM, l.wood@surrey.ac.uk wrote:

> clearly, all IETF meetings should be in Cape Town, Wellington, or Perth, =
because more time in the air means more time without interruption where dra=
fts can be read before the meeting.

Heavens no. All meetings should be in Santa Barbara, so I don't have to boa=
rd an airplane at all.=

From randy@psg.com  Fri May 31 17:49:47 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 635A021F8F41 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LtwH0Cb90xHX for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 17:49:46 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEC521F8EF7 for <ietf@ietf.org>; Fri, 31 May 2013 17:49:46 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1Uia0v-000OIE-Rt; Sat, 01 Jun 2013 00:49:45 +0000
Date: Fri, 31 May 2013 17:49:45 -0700
Message-ID: <m2obbqu02e.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Fred Baker <fred@cisco.com>
Subject: Re: Time in the Air
In-Reply-To: <8C48B86A895913448548E6D15DA7553B900110@xmb-rcd-x09.cisco.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <8C48B86A895913448548E6D15DA7553B900110@xmb-rcd-x09.cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 00:49:47 -0000

> Heavens no. All meetings should be in Santa Barbara, so I don't have
> to board an airplane at all.

i too, but tokyo.  induce.  answer, remote participation.  i hope that a
decade from now many of us will not need to fly.

randy

From warren@kumari.net  Fri May 31 18:13:42 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E849621F8916 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 18:13:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.199
X-Spam-Level: 
X-Spam-Status: No, score=-101.199 tagged_above=-999 required=5 tests=[AWL=1.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DxbIuPtLs9FL for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 18:13:37 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7198A21F8904 for <ietf@ietf.org>; Fri, 31 May 2013 18:13:35 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 645521B40A41; Fri, 31 May 2013 21:13:34 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Not Listening to the Ops Customer (was Re: Issues in wider geographic participation)
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <m2vc5yu1ab.wl%randy@psg.com>
Date: Fri, 31 May 2013 21:13:32 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2F8830E-DCBB-48CD-9161-73C56DDA2DE9@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1503)
Cc: John C Klensin <john-ietf@jck.com>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 01:13:42 -0000

On May 31, 2013, at 8:23 PM, Randy Bush <randy@psg.com> wrote:

> < rant >
>=20
> the sad fact is that the ietf culture is often not very good at
> listening to the (ops) customer.  look at the cf we have made out of
> ipv6.  the end user, and the op, want the absolute minimal change and
> cost, let me get an ipv6 allocation from the integer rental monopoly,
> flip a switch or two, and get 96 more bits no magic. =20
Unfortunatly
Yup, the "issue" with v4 was simply a lack of addresses -- more address =
bits was what ops wanted, this probably needed a new protocol number, =
but that's about all.

Unfortunately the was a bad case of creeping featuritis and we got:
A new, and unfortunately very complex way of resolving L2 addresses.
Magic IPSec, which then went away again.
Extension headers that make it so you cannot actually forward packets in =
modern hardware ( =
http://tools.ietf.org/html/draft-wkumari-long-headers-00)
SLAAC, which then required privacy addressing and then fun that that =
entails / the DHCP debacle.
RA instead of VRRP
Countless transition strategies.
The list goes on and on, but gets depressing really fast.

Operators learnt a number of lessons (the hard way) while operating IPv4 =
networks that reoccured in new ways in IPv6.=20
For example, operators learnt that having a large subnet behind a router =
makes the router fall over (doing all the ARP processing) during an IP =
scan. This is almost identical to the issue described in RFC 6583 =
("Operational Neighbor Discovery Problems")

Operators learnt (a long time back) that allowing source-routing is a =
really bad idea, and so a: devices disable it by default and / or b: the =
standard templates all have "no ip source-route" (or equivalent). This =
is almost identical to the Routing Header issues in V6 (see RFC 5095 - =
"Deprecation of Type 0 Routing Headers in IPv6" )

Most operators address ptp Ethernet links with a /30 or /31 in V4. Took =
a long time to get this in V6 (RFC 6164 - "Using 127-Bit IPv6 Prefixes =
on Inter-Router Link") and it is still controversial.

We ended up in a space where perceived elegance and shiny features =
overshadowed what folk actually wanted -- 96 more bits, no magic.

> 15 years later,
> dhcp is still a cf, i have to run a second server (why the hell does
> isc not merge them?), i can not use it for finding my gateway or vrrp
> exit, ...  at least we got rid of the tla/nla classful insanity.  but
> u/g?  puhleeze.

Yup

>=20
> at ripe/dublin, olaf gave a really nice but somewhat glib talk about
> technology adoption, using dnssec and ipv6 as the positive examples.

Yes, this was a great talk -- I think that it was somewhat glib for the =
audience, but having a longer, more in depth version of it at an IETF =
would (IMO) be valuable. I think that Olaf has a few versions of that =
talk=85. For folk who'd like to see the RIPE version - =
https://ripe66.ripe.net/archives/video/7/ - Innovation at the Waist


>  as
> some curmudgeonly schmuck pointed out at the mic, dnssec is forward
> compatible and there are no alternatives, so it is being adopted =
despite
> its complexity and warts.  ipv6 is not forward compatible, we put
> unnecessary obstacles in the deployment path, and there are
> alternatives.  d o o m.
>=20
> if we had wanted ipng deployed, we would have done everything we could
> to make it simple and easy for net-ops and end users to turn it on.
> instead, we made it complex and hard and then blame everyone else for
> not instantly adopting it en masse.
>  the ietf did not listen to or
> consider the customer.  this is fatal.  and the arrogance is taking =
what
> is left of the e2e internet down the drain with it.
>=20

+1.
w

> randy
>=20

--
Don't be impressed with unintelligible stuff said condescendingly.
    -- Radia Perlman.






From warren@kumari.net  Fri May 31 18:21:32 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB67221F8AD5 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 18:21:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.549
X-Spam-Level: 
X-Spam-Status: No, score=-101.549 tagged_above=-999 required=5 tests=[AWL=1.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bq3yBHuQzvh6 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 18:21:27 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1EE921F89A6 for <ietf@ietf.org>; Fri, 31 May 2013 18:21:26 -0700 (PDT)
Received: from [192.168.0.187] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 5DADA1B40A41; Fri, 31 May 2013 21:21:25 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: [IETF] Re: Issues in wider geographic participation
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <m2ehcmvs7a.wl%randy@psg.com>
Date: Fri, 31 May 2013 21:21:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <268EFFD5-BA4A-48D8-99E1-0EE8BC5AAA8C@kumari.net>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <11B378FD-CADE-49CA-BAC5-814B6E2E07C7@kumari.net> <m2ehcmvs7a.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1503)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 01:21:32 -0000

On May 31, 2013, at 3:56 PM, Randy Bush <randy@psg.com> wrote:

>> Yup. And some operators have decided that the IETF document
>> development and consensus-forming process is sufficiently annoying
>> that they are standing up their own forum for Best Common Practice
>> docs:
>> http://www.ipbcop.org/ -- "Documented best practices for Engineers by =
Engineers"
>> Some more info:
>> =
http://www.internetsociety.org/deploy360/wp-content/uploads/2012/09/Hughes=
-BCOP.pdf
>=20
> actually, that is not operators acting for operators at all.

Yup, Randy is 100% correct, this was started, and has gotten much =
thrust,  from non-ops / policy folk.

But, the fact that it has gotten some traction / the comments that one =
hears from ops folk re: how hard it would be to do this in the IETF =
context is (IMO) telling.

>  it is yet
> another non-ops group trying to colonize ops.  documentd best =
practices
> for engineers by policy folk.  mission creep on their part, imiho.  it
> would be amusing if they did not already have a mission that is =
critical
> for all of us.
>=20
>> There are BCOPs groups forming / within RIPE, NANOG, etc.=20
>=20
> ripe has published ops practice and even protocol docs for a many =
years.
> as one example, route flap damping came from the ripe doc series. =20
> nanog
> may get serious, time will tell.
>=20
>> Out of interest, who all from here will be attending NANOG?=20
>=20
> i will be.  and saw you at ripe.  will you be in lusaka in a week?

Unfortunately not -- I had some conflict thing...

>=20
>> One (IMO) good idea that was mentioned recently (sorry, I cannot
>> remember by whom, may have been Jim Martin) was for someone from the
>> IETF to present a short summary of interesting work at NOG meetings.
>=20
> this has been done many times.  imiho, it has not stirred up much =
useful
> interaction unless the ietfer says something really st00pid. =20

Yes, I may be tilting at windmills, but I think that, if it were done =
right (short summaries, just enough to pique interest, and then "These =
are the bits we'd like feedback on, and here is how you can provide it =
(without joining yet another navel-having mailing list)" it could be =
really useful. But, doing it right would be the key...

> then it
> gets amusing.

Yes. Maybe it should be designed to present the contentious bits?
W


>=20
> randy
>=20

--=20
Militant Agnostic -- I don't know and you don't either...




From mohta@necom830.hpcl.titech.ac.jp  Fri May 31 18:46:52 2013
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 9FAED21F8793 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 18:46:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpyHZbwqGAzo for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 18:46:48 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 51F6021F8556 for <ietf@ietf.org>; Fri, 31 May 2013 18:46:47 -0700 (PDT)
Received: (qmail 37236 invoked from network); 1 Jun 2013 01:43:51 -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; 1 Jun 2013 01:43:51 -0000
Message-ID: <51A95263.80105@necom830.hpcl.titech.ac.jp>
Date: Sat, 01 Jun 2013 10:46:11 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Not Listening to the Ops Customer (was Re: Issues in wider geographic participation)
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <A2F8830E-DCBB-48CD-9161-73C56DDA2DE9@kumari.net>
In-Reply-To: <A2F8830E-DCBB-48CD-9161-73C56DDA2DE9@kumari.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 01:46:52 -0000

Warren Kumari wrote:

> Unfortunately the was a bad case of creeping featuritis and we got:
> A new, and unfortunately very complex way of resolving L2 addresses.

You may use ARP (and DHCP) with IPv6.

> Extension headers that make it so you cannot actually forward
 > packets in modern hardware
 > ( http://tools.ietf.org/html/draft-wkumari-long-headers-00)

True.

> SLAAC, which then required privacy addressing and then fun that
 > that entails / the DHCP debacle.

The problem of SLAAC is that it is stateful in fully distributed
manner. That is all the nodes have their own states on address
assignment

> Most operators address ptp Ethernet links with a /30 or /31 in V4. Took a long time to get this in V6 (RFC 6164 - "Using 127-Bit IPv6 Prefixes on Inter-Router Link") and it is still controversial.
> We ended up in a space where perceived elegance and shiny
 > features overshadowed what folk actually wanted
 > -- 96 more bits, no magic.

Maybe. But the folk actually needed 8 (or 16 at most) more bits.

 >> 15 years later,
 >> dhcp is still a cf, i have to run a second server (why the hell does
 >> isc not merge them?), i can not use it for finding my gateway or vrrp
 >> exit, ...  at least we got rid of the tla/nla classful insanity.  but
 >> u/g?  puhleeze.
 >
 > Yup

TLA/NLA is a good thing, *IF*  multiple addresses of a node
and automatic renumbering including routers and DNS were
properly supported. It is not very difficult to have done so.

						Masataka Ohta



From Ted.Lemon@nominum.com  Fri May 31 19:10:18 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54EA121F89FF for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 19:10:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.598
X-Spam-Level: 
X-Spam-Status: No, score=-106.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMtYeStJltrj for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 19:10:11 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 738EE21F8C20 for <ietf@ietf.org>; Fri, 31 May 2013 19:10:10 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUalYAcOgFKWbZnjocC8VuaM0drt4nZej@postini.com; Fri, 31 May 2013 19:10:10 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A83E91B81D1 for <ietf@ietf.org>; Fri, 31 May 2013 19:10:09 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 9BEF2190052; Fri, 31 May 2013 19:10:09 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.02.0318.004; Fri, 31 May 2013 19:10:10 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
Subject: Re: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXipkaROXudiBbkq0i42yTrUUB5kgGaQAgAAGtwCAABSDgIAAXm6A
Date: Sat, 1 Jun 2013 02:10:09 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BFCF1@mbx-01.win.nominum.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <BD183393-A8DD-4884-AC30-A3877EE51BF6@kumari.net> <CAPv4CP_gONKe3A+h9MmoYyT8bveA-tPpSHq6wFE880iVZ_kJkQ@mail.gmail.com> <51A8F1F4.4040800@dcrocker.net> <CAPv4CP-ZAPeUXnPWK3y1abiDr+vCQ=vAjq76Fww98RwRYjBrfA@mail.gmail.com> <51A908CB.9070605@dial.pipex.com>
In-Reply-To: <51A908CB.9070605@dial.pipex.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: multipart/alternative; boundary="_000_8D23D4052ABE7A4490E77B1A012B6307751BFCF1mbx01winnominum_"
MIME-Version: 1.0
Cc: "mnot@mnot.net" <mnot@mnot.net>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 02:10:18 -0000

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

On May 31, 2013, at 4:32 PM, Elwyn Davies <elwynd@dial.pipex.com<mailto:elw=
ynd@dial.pipex.com>> wrote:
Don't they use the ADs (Area Drones) controlled from the IESG bunker?

Nope, ADs are autonomous.


--_000_8D23D4052ABE7A4490E77B1A012B6307751BFCF1mbx01winnominum_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <B9FB900658318F4EA0153B607DC9E140@nominum.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; ">
<div>
<div>On May 31, 2013, at 4:32 PM, Elwyn Davies &lt;<a href=3D"mailto:elwynd=
@dial.pipex.com">elwynd@dial.pipex.com</a>&gt; wrote:</div>
<blockquote type=3D"cite"><span style=3D"font-family: Optima; font-size: me=
dium; 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; w=
ord-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width=
: 0px; background-color: rgb(255, 255, 255); display: inline !important; fl=
oat: none; ">Don't
 they use the ADs (Area Drones) controlled from the IESG bunker?</span><br =
style=3D"font-family: Optima; font-size: medium; font-style: normal; font-v=
ariant: normal; font-weight: normal; letter-spacing: normal; line-height: n=
ormal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transfo=
rm: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-s=
ize-adjust: auto; -webkit-text-stroke-width: 0px; ">
</blockquote>
</div>
<br>
<div>Nope, ADs are autonomous.&nbsp;</div>
<div><br>
</div>
</body>
</html>

--_000_8D23D4052ABE7A4490E77B1A012B6307751BFCF1mbx01winnominum_--

From Ted.Lemon@nominum.com  Fri May 31 19:17:36 2013
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCBD821F8B3D for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 19:17:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id emCmeL6iRzkM for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 19:17:29 -0700 (PDT)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id F04AE21F88FB for <ietf@ietf.org>; Fri, 31 May 2013 19:17:28 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUalZuMAXh2SMXnOY4H1eGTGIJvLsHbqn@postini.com; Fri, 31 May 2013 19:17:29 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 27FAC1B81D0 for <ietf@ietf.org>; Fri, 31 May 2013 19:17:28 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 1E304190052; Fri, 31 May 2013 19:17:28 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 31 May 2013 19:17:21 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Time in the Air
Thread-Topic: Time in the Air
Thread-Index: AQHOXeWSjFUui2nP5UiSlIvtTtrKp5kfyMCAgACzFgCAAAGJgIAAGHmA
Date: Sat, 1 Jun 2013 02:17:20 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751BFDA8@mbx-01.win.nominum.com>
References: <E9F19D69-19CD-4B00-975E-D1C21D65BDA2@mnot.net> <290E20B455C66743BE178C5C84F12408223F494E9B@EXMB01CMS.surrey.ac.uk> <8C48B86A895913448548E6D15DA7553B900110@xmb-rcd-x09.cisco.com> <m2obbqu02e.wl%randy@psg.com>
In-Reply-To: <m2obbqu02e.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4C4F8CEE2AF19F45BF0845FCC4C1321B@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 02:17:37 -0000

On May 31, 2013, at 8:49 PM, Randy Bush <randy@psg.com> wrote:
> i too, but tokyo.  induce.  answer, remote participation.  i hope that a
> decade from now many of us will not need to fly.

We could just always meet in Tokyo.   I'd be down with that...

:)


From john-ietf@jck.com  Fri May 31 20:00:56 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8441921F84CD for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 20:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.949
X-Spam-Level: 
X-Spam-Status: No, score=-101.949 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2VJwBgGzmLLV for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 20:00:50 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9F33F21F855F for <ietf@ietf.org>; Fri, 31 May 2013 20:00:50 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Uic3j-00078P-SF; Fri, 31 May 2013 23:00:47 -0400
Date: Fri, 31 May 2013 23:00:34 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>
Subject: Re: Not Listening to the Ops Customer (was Re: Issues in wider geographic participation)
Message-ID: <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com>
In-Reply-To: <m2vc5yu1ab.wl%randy@psg.com>
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.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: Sat, 01 Jun 2013 03:00:56 -0000

--On Friday, May 31, 2013 17:23 -0700 Randy Bush <randy@psg.com>
wrote:

> < rant >
> 
> the sad fact is that the ietf culture is often not very good at
> listening to the (ops) customer.  look at the cf we have made
> out of ipv6.  the end user, and the op, want the absolute
> minimal change and cost, let me get an ipv6 allocation from
> the integer rental monopoly, flip a switch or two, and get 96
> more bits no magic.  15 years later, dhcp is still a cf, i
> have to run a second server (why the hell does isc not merge
> them?), i can not use it for finding my gateway or vrrp exit,
> ...  at least we got rid of the tla/nla classful insanity.  but
> u/g?  puhleeze.

Randy,

I suggest that characterizing that set of issues as IETF versus
Ops is probably not completely right either.  For example, with
IPv6, the IETF has proposed multiple transition solutions with
no roadmap as to which one to apply under what circumstances and
growing evidence that some of those solutions are unworkable in
practice and others are incompatible with what are claimed to be
fundamental and important features of the Internet.  It doesn't
take a skilled operations person to understand that is a
problem; someone with a pointy head and barely enough clue to
figure out what a "bit" is much less how many of them are in
various addresses can derive a "don't be the first person on the
block" or "don't migrate if you can figure out an alternative"
lesson from that.  

Similarly, various applications folks within the IETF have
pointed out repeatedly that any approach that assigns multiple
addresses, associated with different networks and different
policies and properties, either requires the applications to
understand those policies, properties, and associated routing
(and blows up all of the historical application-layer APIs in
the process) or requires request/response negotiation that TCP
doesn't allow for (and blows up most of the historical
application-layer APIs).  One of the original promises about
IPv6 was no need for changes to TCP and consequent transparency
to most applications.  Ha!

I have never been convinced that "longer addresses and nothing
else" was the only viable solution for IPng, but I don't think
it requires an advanced degree in economics to understand that,
if the incentives to do something don't exceed the costs and
risks of doing it, one shouldn't expect a lot of rational folks
to charge off and do it.  A complex system with high deployment
costs and risks and a dubious set of advantages is not a story
that is going to sell itself.  And, again, it doesn't require a
sophisticated operator to figure that out.

None of this takes away from your rant (or Warren's).  But I
suggest that, on several of the dimensions you identify, the
operators are not being singled out for abusive treatment
because we don't listen to each other or elementary
decision-making or economic realities either... at least where
broad issues, rather than fine-tuning of a spec are concerned.

   john




From brian.e.carpenter@gmail.com  Fri May 31 21:35:38 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDB121F85B4 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 21:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hB3lUveIBLCd for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 21:35:38 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 442B421F859A for <ietf@ietf.org>; Fri, 31 May 2013 21:35:37 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id xa12so3208168pbc.39 for <ietf@ietf.org>; Fri, 31 May 2013 21:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IGV9Qa5PB3Lv85D217Fxv3WM/wCShO3H9on65XMtXeo=; b=DqnqZewTpEwz0PfCzYwIyWoa6d8I644RUs9G5F1HgjmiOf6LUvBc0kIS3dRyG7Xm4D vau0PRFzMTzupV8YwACV0BMVLG1g+lYOEKb+wac2R0oyUZP6UTWvizarNxWQxbxTtTX1 UyeZyEEQH+nZda0r18/8iDnZ6m4vJVud/y2SlXM8z8QWTokV1Q2XwEzMiK533cxG0CqM vIdEBrzfNnUv1iQRj11+6ilA3pYdYp1bS7sz2qMsKVTDwSNu6lg6u4040BBXTBwZuDtE Hc3fv6bvDBMAwW4CKi+qhXgFR8rOt5sU8vgl80BOoa3C9GvARfBG1TuB3Vw50xiA0QX6 zzqA==
X-Received: by 10.68.13.199 with SMTP id j7mr5907941pbc.17.1370061337637; Fri, 31 May 2013 21:35:37 -0700 (PDT)
Received: from [192.168.1.2] (224.171.252.27.dyn.cust.vf.net.nz. [27.252.171.224]) by mx.google.com with ESMTPSA id q18sm52789370pao.4.2013.05.31.21.35.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 21:35:36 -0700 (PDT)
Message-ID: <51A97A21.2060001@gmail.com>
Date: Sat, 01 Jun 2013 16:35:45 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Not Listening to the Ops Customer 
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com>
In-Reply-To: <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 04:35:39 -0000

On 01/06/2013 15:00, John C Klensin wrote:
> 
> --On Friday, May 31, 2013 17:23 -0700 Randy Bush <randy@psg.com>
> wrote:
> 
>> < rant >
>>
>> the sad fact is that the ietf culture is often not very good at
>> listening to the (ops) customer.  look at the cf we have made
>> out of ipv6.  the end user, and the op, want the absolute
>> minimal change and cost, let me get an ipv6 allocation from
>> the integer rental monopoly, flip a switch or two, and get 96
>> more bits no magic.  15 years later, dhcp is still a cf, i
>> have to run a second server (why the hell does isc not merge
>> them?), i can not use it for finding my gateway or vrrp exit,
>> ...  at least we got rid of the tla/nla classful insanity.  but
>> u/g?  puhleeze.
> 
> Randy,
> 
> I suggest that characterizing that set of issues as IETF versus
> Ops is probably not completely right either.  

It was more complicated. I was actually running a team that ran site
network ops at the time, and (since DHCP was not yet deployable),
IPv4 was then a serious nuisance to manage, compared say to Novell
Netware and, even, Appletalk. There were good reasons we wanted
stateless auto-configuration and unlimited subnet size, to mention
two IPv6 bells and whistles. If DHCP had already been deployed,
our opinion might have been different.

> For example, with
> IPv6, the IETF has proposed multiple transition solutions with
> no roadmap as to which one to apply under what circumstances and
> growing evidence that some of those solutions are unworkable in
> practice and others are incompatible with what are claimed to be
> fundamental and important features of the Internet.  

It turns out that as soon as you envisage a network in which some
nodes only support 32 bit addresses and other nodes can't get
a globally unique 32 bit address, you are forced into a world
of hurt that requires some combination of NAT, tunnels and
dual-stack. That is completely independent of the design of
IPng, and we knew it 1994.

So while your criticism is valid that we collectively came up
with too many such combinations, that collective mistake was
(IMHO) not a result of the design of IPv6 as such. It was more
caused by the design of human beings.

> It doesn't
> take a skilled operations person to understand that is a
> problem; someone with a pointy head and barely enough clue to
> figure out what a "bit" is much less how many of them are in
> various addresses can derive a "don't be the first person on the
> block" or "don't migrate if you can figure out an alternative"
> lesson from that.  
> 
> Similarly, various applications folks within the IETF have
> pointed out repeatedly that any approach that assigns multiple
> addresses, associated with different networks and different
> policies and properties, either requires the applications to
> understand those policies, properties, and associated routing
> (and blows up all of the historical application-layer APIs in
> the process) or requires request/response negotiation that TCP
> doesn't allow for (and blows up most of the historical
> application-layer APIs).  

It's true, but to avoid that, I think we'd have to abolish
cellular telecommunications, Wi-Fi, and competition between
providers.

> One of the original promises about
> IPv6 was no need for changes to TCP and consequent transparency
> to most applications.  Ha!

Right, but again - only part of that is due to the change of
address size and socket API details. Most of it is due to
multiple connectivity. That was going to happen anyway.

> 
> I have never been convinced that "longer addresses and nothing
> else" was the only viable solution for IPng, 

Don't forget, BTW, that even "just" changing address size
from 32 to 64 would have blown up almost every app written to
BSD sockets (since Real Programmers Don't Use Structures and
almost everybody used to stick addresses into uint_32).
There never was a free lunch on the table.

   Brian

> but I don't think
> it requires an advanced degree in economics to understand that,
> if the incentives to do something don't exceed the costs and
> risks of doing it, one shouldn't expect a lot of rational folks
> to charge off and do it.  A complex system with high deployment
> costs and risks and a dubious set of advantages is not a story
> that is going to sell itself.  And, again, it doesn't require a
> sophisticated operator to figure that out.
> 
> None of this takes away from your rant (or Warren's).  But I
> suggest that, on several of the dimensions you identify, the
> operators are not being singled out for abusive treatment
> because we don't listen to each other or elementary
> decision-making or economic realities either... at least where
> broad issues, rather than fine-tuning of a spec are concerned.
> 
>    john
> 
> 
> 
> 

From mohta@necom830.hpcl.titech.ac.jp  Fri May 31 21:45:31 2013
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 9FEE321F8EF2 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 21:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78f+QDMWXW6U for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 21:45:25 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 6079521F8EEA for <ietf@ietf.org>; Fri, 31 May 2013 21:45:23 -0700 (PDT)
Received: (qmail 40177 invoked from network); 1 Jun 2013 04:42:27 -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; 1 Jun 2013 04:42:27 -0000
Message-ID: <51A97C20.9010809@necom830.hpcl.titech.ac.jp>
Date: Sat, 01 Jun 2013 13:44:16 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Not Listening to the Ops Customer (was Re: Issues in wider geographic participation)
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com> <ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com> <84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com> <6ED62F96CF93330166E41F07@JcK-HP8200.jck.com> <0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net> <44F8C31F2483ECB745E44928@JcK-HP8200.jck.com> <022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk> <19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com> <m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com>
In-Reply-To: <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.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, 01 Jun 2013 04:45:31 -0000

John C Klensin wrote:

> Similarly, various applications folks within the IETF have
> pointed out repeatedly that any approach that assigns multiple
> addresses, associated with different networks and different
> policies and properties, either requires the applications to
> understand those policies, properties, and associated routing
> (and blows up all of the historical application-layer APIs in
> the process) or requires request/response negotiation that TCP
> doesn't allow for (and blows up most of the historical
> application-layer APIs).  One of the original promises about

That is a very old problem of IPv4, except that DNS takes care
of multiple addresses of name servers at IP level and SMTP
(and some TELNET implementation, though it is not very useful)
supports multiple addresses of mail servers at TCP level.

Thus, API of IPv4 must change.

> IPv6 was no need for changes to TCP and consequent transparency
> to most applications.  Ha!

There is no need for IPv6 specific changes.

						Masataka Ohta



From dougb@dougbarton.us  Fri May 31 23:05:38 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58DA521F86F0 for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 23:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WOQqS9cUGCwK for <ietf@ietfa.amsl.com>; Fri, 31 May 2013 23:05:37 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id B3E1521F86DC for <ietf@ietf.org>; Fri, 31 May 2013 23:05:37 -0700 (PDT)
Received: from [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b] (unknown [IPv6:2001:470:d:5e7:224:e8ff:fe30:109b]) by dougbarton.us (Postfix) with ESMTPSA id EA7A822B14 for <ietf@ietf.org>; Sat,  1 Jun 2013 06:05:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1370066737; bh=SLeOsDjXY30rPfiLYgaW6hz068bCtc7xLT9ivL4dq2I=; h=Date:From:To:Subject:References:In-Reply-To; b=JSSLkVoAGvPc/yNTs2MpWDXEZOf9bAL8kVTBb62V1OEksa2uQh/JCxfJzgOubLXPb ihg3OuBp8uerZH5+dFsk9dfIMiZp1Pzp3R8LAbA5JXJe2X7qs87rdxoU1N6I97sJaB L956d552wgyvbr2UtLrnNTnre1v4mxYWukO+FIBE=
Message-ID: <51A98F30.3040508@dougbarton.us>
Date: Fri, 31 May 2013 23:05:36 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Not Listening to the Ops Customer
References: <08A2F698F28D9ED6B4AAE099@JcK-HP8200.jck.com>	<ACA9DF14-FD2C-4262-93A9-1EB75E348404@cisco.com>	<84AD30F562AC6B09F2497C92@JcK-HP8200.jck.com>	<6ED62F96CF93330166E41F07@JcK-HP8200.jck.com>	<0EDA10CD-C693-45E6-9E8C-D32A065A931F@kumari.net>	<44F8C31F2483ECB745E44928@JcK-HP8200.jck.com>	<022d01ce5d9c$dade82e0$909b88a0$@olddog.co.uk>	<19EFB71AD450605EC3569CE4@JcK-HP8200.jck.com>	<m2vc5yu1ab.wl%randy@psg.com> <C64459F0B754590B9B7E88ED@JcK-HP8200.jck.com> <51A97A21.2060001@gmail.com>
In-Reply-To: <51A97A21.2060001@gmail.com>
X-Enigmail-Version: 1.5.1
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Jun 2013 06:05:38 -0000

On 05/31/2013 09:35 PM, Brian E Carpenter wrote:
> It was more complicated. I was actually running a team that ran site
> network ops at the time, and (since DHCP was not yet deployable),
> IPv4 was then a serious nuisance to manage, compared say to Novell
> Netware and, even, Appletalk. There were good reasons we wanted
> stateless auto-configuration

Brian,

Not picking on you here, in fact I'm agreeing with you regarding the 
early days. In '94 SLAAC/RA was a good idea, and remains a good idea for 
"dumb" devices that only need to know their network and gateway to be 
happy.

What continues to astonish however is that 15 years after DHCP took off 
for IPv4 the IPv6 luminati are still singing the 2-verse song, "You must 
use SLAAC," and "You may not have full-featured DHCPv6."

Whatever good intentions were in place 20 years ago (and I do not doubt 
that they were good intentions), the situation right now is beyond 
absurd, and serves as an excellent example of why a non-trivial number 
of operators don't take the IETF seriously.

Doug
